Triggering an agent from events
Wake an agent the instant something happens — a new email, a webhook, or an event in a connected tool — so it reacts in real time.
Last updated July 14, 2026
A trigger runs your agent in response to something happening, rather than on a clock. When the event fires, the agent starts working right away — perfect for reacting to new email, incoming form submissions, or updates in a connected tool.
Triggers live under the Automations tab of your agent, next to schedules.
Kinds of triggers
| Trigger | Fires when | Example |
|---|---|---|
| A message arrives | New support email lands in a connected inbox | |
| Webhook | Another system posts to a URL | A form tool notifies your agent of a new submission |
| Integration event | Something changes in a connected app | A new deal, task, message, or record appears |
Set up a trigger
Go to your agent's Automations tab and add a trigger.
Pick the source — an inbox, a webhook, or an event from a connected integration like your CRM or Slack.
Describe how it should respond to each event, for example "Read the incoming email and draft a reply."
Once enabled, the agent runs automatically every time the event happens.
Each event is its own run
When a trigger fires, the details of the event — the email, the record, the webhook payload — are handed to the agent for that run. The agent has what it needs to act on that specific item without you copying anything over.
Keep volume in mind
High-traffic sources can fire often. Since every run uses credits, it's worth narrowing a trigger to the events that truly need an agent — for example, only emails to a specific address, rather than everything in the inbox.
Watching triggered runs
Every triggered run appears in Activity, outputs are saved to Deliveries, and failures show up in Errors. If a trigger seems quiet, check that it's toggled on and the source app is still connected.