React to events with triggers
Run work automatically when something happens in a connected app.
Advanced · ~15 min · Prerequisites: a connected app
What you'll do
Subscribe to an event in a connected app — like a new important email or a new GitHub issue — and define what the assistant does every time that event fires.
See available triggers
Open Integrations → Triggers in the sidebar, or ask the assistant: "What triggers are available for Gmail?"
Each connector exposes a set of named event types. Gmail offers triggers like New important email and New email from sender. GitHub offers New issue opened, PR review requested, and more. See Triggers for the complete reference and polling intervals.
Triggers poll the connected app on a schedule — they don't use webhooks unless the connector specifically supports push events. Check the connector's reference page for the polling interval.
Subscribe to a trigger
Click Add trigger in the Triggers panel and choose a connector and event type. Configure the filter fields for that event — for example, a Gmail trigger lets you filter by sender domain or label.
You can also ask the assistant: "Notify me when a GitHub issue is labeled 'critical' in the web repo." It opens the trigger creation form pre-filled with your criteria.
Define the response
The response is what the assistant does each time the trigger fires. Write it as a natural-language instruction:
- "Summarize the email and add a task titled 'Follow up: {sender}' with high priority."
- "Post the issue title and URL to #alerts in Slack."
- "Draft a reply acknowledging receipt and save it as a draft — don't send."
The assistant executes this instruction once per matching event. It has access to the event payload — sender, subject, body, timestamps — so you can reference those fields in your instructions with {'{field_name}'} placeholders or plain English.
Unsubscribe / manage
To pause, edit, or delete a trigger, go to Integrations → Triggers, find the row, and use the ⋯ menu. You can toggle a trigger off temporarily without losing its configuration.
To see recent trigger runs and debug a response that didn't fire as expected, click the trigger row to expand its run history.