Playbooks
Ask for a playbook by what it does, run it, and build a new one from a description.
list_playbooksget_playbookrun_playbookcreate_playbookupdate_playbook
Reach your whole Ballet workspace by asking
The connector exposes 31 tools. Claude picks the ones it needs, so you describe the outcome rather than naming them.
Agents
The agents a playbook calls on, each with its own instructions and tools.
list_agentsget_agentcreate_agentupdate_agent
Runs
Read a run back step by step — what each one returned and where it stopped.
list_runsget_runget_run_steps
MCP servers
Connect the systems a playbook works across, and see what each server exposes.
connect_mcp_serverlist_mcp_serverslist_mcp_toolscreate_mcp_server
Tools and skills
The building blocks a playbook composes, created and edited from the conversation.
list_toolscreate_toollist_skillscreate_skillupdate_skill
Come back later and just ask it to run
Once a playbook exists, a conversation is one of the ways to start it. Ask by what it does — Claude finds it, runs it, and reads the result back.
Ask for it the way you'd ask a colleague
You don't need the playbook's name or its id. Claude searches what your workspace has and picks the one that fits.
The answer comes back in plain language
Not a run id to go and look up. What ran, what it did, and the one thing that needs a person.
It's still a governed run
The gate held because the workflow says it should. Asking from a conversation doesn't route around it.
Build it in a conversation, then let it run without one
A playbook built from Claude is a playbook like any other. It doesn't need a prompt to start, and it doesn't need Claude to be open.
- A schedule
- A webhook
- A Slack command
- A form submission
- Manually, from Claude
The same reviewed playbook
What Claude runs is the version your engineers approved, and the gates they set still hold.
Your workspace, your sign-in
The connector authenticates against your own Ballet workspace, so Claude sees what you see.
Every run still logged
A run started from a conversation is logged and replayable like any other.
Pick the door your team already uses
The playbooks and the governance are the same in all of them.
Platform
Build and run the workflow
Where a workflow gets written, reviewed, and watched once it's live.
Platform →
Chrome extension
Run playbooks beside the tab you're in
A side panel next to your CRM or helpdesk. Ask for something, or type / and pick a playbook.
Chrome extension →
Claude connector
Build and run playbooks inside Claude
Connect Ballet in Claude and ask it to run a playbook, read what happened, or build a new one.
You're here
Slack agent
Tag Ballet where the work already happens
Mention Ballet on a message, or send it a DM. The result posts back in the thread.
Slack agent →Add Ballet to Claude
The connector is in the directory. Adding it takes a sign-in, and Claude can reach your playbooks from the next message.