Conductor
for LuumenAI
Read Conductor workspaces and transcripts, then open sessions with approval
Connect Conductor and Luumen can see which workspaces exist, which agent sessions are idle, working, or in error, and what was said in any transcript. Ask for a new workspace, another session, or a prompt sent to a running agent, and Luumen shows the plan first and waits for your approval before it writes.
The Conductor toolbox
17 tools: 10 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Current UserReturn the user and organization represented by the connected Conductor API key.
- ReadGet MessageGet one transcript message by id.
- ReadGet ProjectGet one Conductor project and its repository remote by project id.
- ReadGet SessionGet one agent session's configuration and current idle, working, or error status in one read.
- ReadGet WorkspaceGet a workspace's metadata and current lifecycle status in one read, including initialization progress or errors.
- ReadList MessagesRead one page of a session transcript or incrementally read messages after a known message ID.
- ReadList ProjectsList repositories available to the connected account for creating Conductor workspaces.
- ReadList SessionsList one page of agent chat sessions in a Conductor workspace.
- ReadList WorkspacesList one page of workspaces belonging to a Conductor project, including deep links and recent activity.
- ReadQuery TranscriptsRun one read-only SQL SELECT against the organization's session_transcripts_view.
- WriteChange Workspace StatePut a workspace to sleep or archive it. Approval by default
- WriteCreate SessionCreate another agent chat session in an existing workspace. Approval by default
- WriteCreate WorkspaceCreate a cloud workspace and its first agent session. Approval by default
- WriteRename SessionChange an existing Conductor session's display name without stopping its agent. Approval by default
- WriteRename WorkspaceChange the display name of an existing Conductor workspace without changing its lifecycle state. Approval by default
- WriteSend MessageSend a prompt to a Conductor session agent. Approval by default
- WriteStop SessionCancel only the current turn and queued messages, or archive the entire session. Approval by default
One prompt, start to finish
What a governed Conductor run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as change workspace state, create session, create workspace, rename session, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Conductor — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
Adobe Marketing Agent MCPAdobe Experience Platform context, sandbox switches, and async task status
AffindaRead parsed documents, collections, and annotations — change them with approval
Agent MailGive the agent its own mailbox for reading threads and sending updates
AI/ML APIInspect assistants, threads, and runs — and change them as approved stepsPut Conductor to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.