Point a trigger at an agent, a tool or an orchestration and say what starts it. Every firing is recorded with what it produced, so an automation is auditable, not a cron line you hope ran.
Fire on a cron in UTC, on an event the platform emits, or by hand through the API.
Each attempt records what started it, whether it succeeded and the run it created.
Chain agents into a graph with branches, loops and waits, or a workflow of states with a human review in the middle.
A playbook keeps one case per client and runs each step once its inputs are filled, and again only when one of them changes.
Schedules stop once the balance goes negative, so a debt stays small; you restore each one when it is paid.
Triggers per account: 3 on Free (hourly at most), 30 on Pro (every 5 min), 500 on Business (every minute). Compare plans
By the end you will have an agent that runs on its own every morning, proven by one fire you start by hand and a generation that names the trigger behind it. Every step is one call, shown for the CLI, the SDK and curl.
Start the tutorialSign in, connect your assistant or open the quickstart, and run your first agent.
Free plan · 2,000 runs a month · no card
