Find a playbook
Search by what a playbook does. You don't need to remember what someone named it.
You don't need to know the playbook's name
Or that one exists. Describe the job and Ballet works out which one fits.
See team playbooks
Look at what the workspace has already built, before you do it by hand again.
Get something done
Describe the job. Ballet picks a playbook, asks for whatever it's missing, and runs it.
One person builds it. The team runs it.
The panel is how everyone else gets at the work someone already automated, at the rate the queue actually arrives.
The same reviewed playbook
What runs from the panel is the version your engineers approved. The gates come with it.
It can read the tab
The panel picks up the record on screen, so you're not copying a ticket number into a form.
Still logged
A run started here is logged like any other. The audit trail doesn't care where it came from.
Nothing to roll out
New playbooks show up for the whole workspace once they're approved.
There are two other ways in
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.
You're here
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.
Claude connector →
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 →See it running on your systems
Pick something your team does by hand today. We'll build it and put it in the panel next to the tool you already use.