Overview & Trigger Types
Watch a connected app or an incoming webhook and run an agent automatically when something happens.
Overview
A trigger watches for an event and runs one of your agents automatically when it happens — no one has to open a chat and ask. You tell the trigger which event to listen for, which agent should run, and what that agent should do each time.
Trigger Types
There are two distinct ways to fire a trigger, depending on where the event comes from:
| Type | Fires When… | Learn More |
|---|---|---|
| Connected-app event | Something happens in a connected app — a new email arrives, a new Slack message posts, a form gets submitted, a row gets added. | Creating a Trigger |
| Custom webhook | An HTTP request hits a URL Pushable gives you, authenticated with a secret key. Any system that can send a POST request can fire it. | Custom Webhook Triggers |
Both types run an agent the same way once fired — the difference is only in what wakes the trigger up. The rest of this page, and Creating a Trigger, cover the connected-app-event type; see Custom Webhook Triggers for the webhook type.
Where to Find It
Open Triggers in the sidebar, under More. There are two tabs: Triggers (your list, where you create and manage them) and Triggers Runs (a history of every time a trigger fired — see Trigger Runs).
For a connected-app-event trigger, you need a connected integration before you can create one. Connect one first from Integrations, then assign it to the agent you want the trigger to run from that agent's Integrations settings.