← Back to connectors

Conductor connector for Okou

Connect Conductor to create and manage cloud workspaces, run coding-agent sessions, exchange messages, and search session transcripts.

Engineering · API Key

Use Conductor in Okou

Use Conductor (conductor.build) to create and manage cloud workspaces, run coding-agent sessions, send prompts, read transcripts, inspect status, and query session history.

Once connected, supported Conductor actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.

What you can do with Conductor

  • Read the authenticated Conductor user and organization identity.
  • Read repositories available for creating Conductor workspaces.
  • Read workspace metadata, workspace sessions, and workspace lifecycle status.
  • Read coding-agent sessions, transcript messages, and session status.
  • Send prompts to coding-agent sessions; requests can start model work and consume provider-side usage.
  • Run Conductor's read-only transcript SQL query against the approved session view.
  • Create, rename, sleep, archive, or restore cloud workspaces.
  • Create, rename, archive, or cancel coding-agent sessions and queued work.

How the Conductor connector works

A connected service becomes one permissioned step in the work you hand off.

  1. 1

    Connect Conductor

    Choose API Key.

  2. 2

    Choose the work

    Use only the supported actions your workflow needs.

  3. 3

    Run it your way

    Start it once, schedule it, or attach an event trigger.

Connect Conductor securely

Use the connection method that fits your account and grant only the access the workflow needs.

  • API Key

Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.

Conductor connector questions

What can Okou do with Conductor?
Connect Conductor to create and manage cloud workspaces, run coding-agent sessions, exchange messages, and search session transcripts. Documented actions include: Read the authenticated Conductor user and organization identity. Read repositories available for creating Conductor workspaces.
How do I connect Conductor to Okou?
Connect Conductor using API Key. The connection controls which supported actions a workflow can use.
Can Conductor run in an automated workflow?
Yes. After it is connected, supported Conductor actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.

More engineering connectors

Explore other connectors in the same product category.