---
title: "Conductor integration for LuumenAI"
url: "https://www.luumen.ai/integrations/conductor/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Conductor integration for LuumenAI

Read Conductor workspaces and transcripts, then open sessions with approval

## What LuumenAI can do with Conductor

LuumenAI connects to Conductor with an API token and exposes 17 tools (10 read-only · 5 write · 2 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 17 tools (10 read-only · 5 write · 2 destructive)
- Plan: available on all plans
- Category: AI & automation

## About Conductor with LuumenAI

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.

## Example tools

Read-only (10 in total):

- `CONDUCTOR_GET_CURRENT_USER` — Return the user and organization represented by the connected Conductor API key.
- `CONDUCTOR_GET_MESSAGE` — Get one transcript message by id.
- `CONDUCTOR_GET_PROJECT` — Get one Conductor project and its repository remote by project id.
- `CONDUCTOR_GET_SESSION` — Get one agent session's configuration and current idle, working, or error status in one read.
- `CONDUCTOR_GET_WORKSPACE` — Get a workspace's metadata and current lifecycle status in one read, including initialization progress or errors.
- `CONDUCTOR_LIST_MESSAGES` — Read one page of a session transcript or incrementally read messages after a known message ID.
- `CONDUCTOR_LIST_PROJECTS` — List repositories available to the connected account for creating Conductor workspaces.
- `CONDUCTOR_LIST_SESSIONS` — List one page of agent chat sessions in a Conductor workspace.

Write and destructive (7 in total, approval required by default):

- `CONDUCTOR_CHANGE_WORKSPACE_STATE` — Put a workspace to sleep or archive it.
- `CONDUCTOR_CREATE_SESSION` — Create another agent chat session in an existing workspace.
- `CONDUCTOR_CREATE_WORKSPACE` — Create a cloud workspace and its first agent session.
- `CONDUCTOR_RENAME_SESSION` — Change an existing Conductor session's display name without stopping its agent.
- `CONDUCTOR_RENAME_WORKSPACE` — Change the display name of an existing Conductor workspace without changing its lifecycle state.
- `CONDUCTOR_SEND_MESSAGE` — Send a prompt to a Conductor session agent.
- `CONDUCTOR_STOP_SESSION` — Cancel only the current turn and queued messages, or archive the entire session.

## Frequently asked questions

### How does LuumenAI connect to Conductor?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Conductor on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Conductor — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/conductor/