Triggers
Triggers run your agents in response to something happening — a system event or an inbound webhook — rather than on a clock. Use them to react automatically: kick off a job when a PR merges, when a deploy finishes, or when an external service calls in. Access via Automate → Triggers in the sidebar.
What it is
A trigger is a saved routine that fires one or more agents when a condition is met. Where a Schedule runs on a timetable, a trigger runs on an event.
How it works
Create a trigger, choose its type, give it the event or webhook to listen for, pick the agents to run, and activate it. Triggers appear in a table showing their type, what they fire on, status, and when they last fired.
Creating a trigger
- Name — a clear label for the routine.
- Type — how it fires:
- Event — when a named system event is emitted (for example
pr.merged). - Webhook — when an HTTP request arrives at a path you define (for example
/hooks/my-routine). - Manual — only when you run it by hand.
- Event — when a named system event is emitted (for example
- Fires on — the event name or webhook path (required unless the type is Manual).
- Description (optional) — what it’s for; an AI helper can refine it.
- Agents — which agents to run when it fires.
- Status — Active (enabled), Paused (disabled but kept), or Draft (not live yet).
Managing triggers
- Search and filter by name, description, or value.
- Stats at the top show totals along with how many are event- versus webhook-based.
- Row actions — enable/disable, edit, or delete any trigger.
- Last fired tells you when each one most recently ran — handy for debugging.
Tip: Like schedules, you can create a trigger directly from an agent’s detail page with that agent pre-filled.