Change Workspace State
Put a workspace to sleep or archive it. Both actions stop active workspace use; archive is a stronger transition but is documented as restorable. Confirm the intended target and state before calling.
ActionTry it
Integrate Conductor
with your AI CRM
Conductor is a cloud development platform for creating workspaces, running coding-agent sessions, exchanging messages, and searching session transcripts.
Explore Triggers and Actions
Create Session
Create another agent chat session in an existing workspace. This may start agent/model resources and incur charges; call only when the user explicitly intends a new session.
ActionTry it
Create Workspace
Create a cloud workspace and its first agent session. This launches compute and may incur cloud or model charges; call only when the user explicitly intends to create a new workspace.
ActionTry it
Get Current User
Return the user and organization represented by the connected Conductor API key. Use this to verify which account the connection acts as.
ActionTry it
Get Message
Get one transcript message by id. The content may contain sensitive prompts, agent output, configuration, or provider-specific events.
ActionTry it
Get Project
Get one Conductor project and its repository remote by project id.
ActionTry it
Get Session
Get one agent session's configuration and current idle, working, or error status in one read. The tool fails unless both records are retrieved and refer to the requested session.
ActionTry it
Get Workspace
Get a workspace's metadata and current lifecycle status in one read, including initialization progress or errors. The tool fails unless both records are retrieved and refer to the requested workspace.
ActionTry it
List Messages
Read one page of a session transcript or incrementally read messages after a known message ID. Returned content may contain sensitive user prompts, agent output, configuration, or provider events; request and expose it only when needed.
ActionTry it
List Projects
List repositories available to the connected account for creating Conductor workspaces.
ActionTry it
List Sessions
List one page of agent chat sessions in a Conductor workspace.
ActionTry it
List Workspaces
List one page of workspaces belonging to a Conductor project, including deep links and recent activity.
ActionTry it
Query Transcripts
Run one read-only SQL SELECT against the organization's session_transcripts_view. Results can expose sensitive transcript text across many sessions: select only necessary columns, constrain rows with LIMIT, and use this only for deliberate organization-wide analysis. Conductor limits queries to 5 seconds and responses to 500 rows, so results may be truncated.
ActionTry it
Rename Session
Change an existing Conductor session's display name without stopping its agent.
ActionTry it
Rename Workspace
Change the display name of an existing Conductor workspace without changing its lifecycle state.
ActionTry it
Send Message
Send a prompt to a Conductor session agent. This can start external agent/model execution and incur charges; it is not a passive transcript append. Call only when the user intends the agent to act.
ActionTry it
Stop Session
Cancel only the current turn and queued messages, or archive the entire session. Both can discard queued work; archive also stops the agent and leaves the session read-only. Confirm the intended action before calling.
ActionTry it
How the Conductor integration works
The Conductor integration connects your Dench AI CRM directly to Conductor, so agents can read and act on your Conductor data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
17 actions are available for agents to invoke on your behalf. Every call runs through Conductor's own authorization, scoped to the account you connect.
Set up Conductor in Dench
- 1
Sign in to your Dench workspace and open Integrations.
- 2
Find Conductor and click Connect — you'll authorize access through Conductor's own sign-in flow. No API keys or code required.
- 3
Ask an agent to use Conductor in chat, or call it from an automation.
- 4
Manage or disconnect the connection any time from workspace settings.
Frequently asked questions
How does the Conductor integration work with Dench?
The Dench Conductor integration connects your AI CRM to Conductor, so AI agents can work with your Conductor data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
What actions can AI agents perform with Conductor via Dench?
The Conductor integration currently exposes 17 actions, including Change Workspace State, Create Session, Create Workspace, Get Current User, Get Message, and Get Project. Agents invoke them on your behalf from chat or from automations.
Do I need to write code to connect Conductor to Dench?
No. You connect Conductor from your Dench workspace using Conductor's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Is the Conductor integration secure?
Connections are authorized through Conductor's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Conductor connection from your workspace settings at any time.