Use Conductor with
Sokko.
Connect Conductor and tell Sokko what to do. It runs the actions you ask for and reacts to what happens. No workflows, no code.
Works with 1,000+ tools · No code required
Actions
Everything Sokko can do in Conductor
Every Conductor action Sokko can run. Ask for one in a sentence and it's done.
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.
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.
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.
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.
Get Message
Get one transcript message by id. The content may contain sensitive prompts, agent output, configuration, or provider-specific events.
Get Project
Get one Conductor project and its repository remote by project id.
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.
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.
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.
List Projects
List repositories available to the connected account for creating Conductor workspaces.
List Sessions
List one page of agent chat sessions in a Conductor workspace.
List Workspaces
List one page of workspaces belonging to a Conductor project, including deep links and recent activity.
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.
Rename Session
Change an existing Conductor session's display name without stopping its agent.
Rename Workspace
Change the display name of an existing Conductor workspace without changing its lifecycle state.
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.
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.
Get connected
Live in your Slack in two minutes.
No workflows to wire up. Turn on the tools you already use, and your agent gets to work.
Add to Slack
1
Add Sokko to Slack
One click from the Slack marketplace. Your whole team gets Sokko at once.
2
Connect your tools
Sokko works with 1,000+ apps and any MCP server.
Martin
9:53 AM
@Sokko
What can you do with Conductor?
3
Put Sokko to work
@mention Sokko in any channel and it gets going. Minutes, not a weekend.
Questions, answered.
Sokko is an AI assistant that lives in your Slack. Connect your apps, ask for what you need in plain language, and Sokko takes the work off your plate.
Sign up to Sokko, ask Sokko to connect to Conductor, and approve the connection when prompted. From then on you can ask Sokko to do things in Conductor whenever you need.
No. There's nothing to build or configure. You ask Sokko in Slack the same way you'd ask a colleague, and Sokko handles the rest.
Yes. Ask once and tell Sokko when to repeat it, like every Monday at 9am, and it becomes a routine that runs without you.
Read and act on data in Conductor, and trigger workflows when something changes there. Tell Sokko the outcome you want and it handles the rest.
Yes. Sokko connects to 1,000+ apps and any MCP server, so you can ask for tasks that span Conductor and the rest of your stack in a single request.