TL;DR: A playbook can start four ways: Manual (you click Run), Schedule (at recurring times), Webhook (another system sends Ballet a message), or a Trigger (Ballet watches an app such as Zendesk and starts the playbook for each new item that matches). Manual, Schedule and Webhook are set in the playbook's Trigger panel. Triggers are shared between playbooks, set up by asking the agent, and managed from Triggers in the sidebar.
Builders deciding how and when a playbook should run on its own.
| You want to… | Use |
|---|---|
| Test a playbook or run it on demand | Manual |
| Run at fixed times, like a daily report | Schedule |
| Let another system tell Ballet when something happens | Webhook |
| Run once for every new or changed item in an app, such as each new ticket or updated deal | Trigger |
The default. Open the playbook and click Run, or run it over the REST API. Use Manual for on-demand work and for testing before you automate anything.
Runs the playbook on a recurring schedule: hourly, daily, weekly or custom. Set it in the playbook's Trigger panel, or manage every schedule from Schedules in the sidebar. A scheduled run happens whether or not anything has changed. See How do I manage Schedules?.
Gives the playbook its own web address. Another system sends a message to that address whenever something happens, and each message starts a run. You register the address in the other system. For step-by-step setup, see How do I trigger and react to playbooks with webhooks? and How do I connect CRM and support tools?.
Yes. First-party integrations like Freshdesk can start a playbook when a ticket is created or updated. Pick the app on the Integration tab of the playbook's Trigger panel.
A Trigger watches one app for one kind of change, for example "when a ticket is created in Zendesk". It checks every 5 minutes by default. When it finds something new, it hands each item to the playbooks that use it, and each playbook runs once for each item.
If you don't see Triggers in the sidebar, it isn't switched on for your workspace yet.
A new Trigger starts from now. Anything that changed before it went live is skipped.
When you publish a change to a Trigger that playbooks already use, you choose:
Some Triggers can't look back, because the way they read from the app doesn't go back to a time. The dialog says so when that's the case.
You can also use Look again from… on a Trigger's page at any time.
A Trigger that no live playbook uses sits idle and doesn't check the app. A playbook that starts using it later only gets items from that point on.
Open Triggers in the sidebar and pick a Trigger. At the top you see what it watches, how often it checks and how it is doing, with controls to switch it Active or Paused, Run now, Look again from…, and Delete trigger. Under that:
| Label | What it means |
|---|---|
| Working | It is checking and nothing is wrong. |
| Not live yet | It is saved but not published, so it isn't checking. Publish it to start. |
| Paused | Switched off. Switch it back to Active to carry on. |
| No playbook uses it yet | It is live, but nothing is attached to it, so nothing runs. |
| The last check failed, or Failed N checks in a row | The page says why under the header. If the app needs reconnecting, there's a link to connect it. |
| Waiting: the app asked us to slow down | The app asked Ballet to wait. The page says until when, and it carries on by itself. |
| The last check was stopped | The check ended early, for example because it was paused or reached its limit for one check. It keeps its progress and carries on at the next check. |
| Skipping items it can't tell apart | Some items had no way to be told apart, so no playbook ran on them. Ask the agent to fix how it reads from the app. |
You may also see a notice that a playbook's rule couldn't check some items, with the reason. Those items aren't dropped.
If your workspace has reached its spending limit, you can still pause a Trigger, but you can't switch it on or use Run now until the limit is lifted.
Open the playbook and find Triggers in its Trigger panel. Each Trigger it runs on is listed with its rule. Choose Remove next to the one to drop. Like any change, it takes effect when you publish the playbook. Until then the Trigger keeps sending it items, and items still waiting are closed as never run when you publish.
Triggers are for builders. Editors and owners can create, change, test, publish, pause, check and delete them. People with view-only access can look but not change.