Embedded triggers
The Trigger Inbox API lets your product subscribe to events from any of Zapier’s 9,000+ connected apps and process them in your own backend. Zapier handles authentication, webhook subscriptions, and polling infrastructure. Your backend leases and processes events at its own pace. This use case is a good fit if you are:- Building an AI agent or automation engine that reacts to events across multiple apps
- Processing events programmatically without exposing public webhook endpoints
- Covering a long tail of app integrations without building per-app infrastructure
How it works
- The user connects their app account via Connect UI.
- Your backend creates a trigger inbox — a named queue subscribed to a specific app event (for example, new Slack messages in a channel).
- Zapier delivers incoming events to the inbox.
- Your backend leases, processes, and acknowledges messages.
Get started
- What is the Trigger Inbox API? — overview, core concepts, and limits
- Trigger Inbox onboarding — run the full message lifecycle in minutes using a webhook trigger
- Create a trigger inbox for an app — connect to Slack, Gmail, and 9,000+ other apps
Related guides
- Token exchange — get an access token
- Connection flow — connect a user’s app account
- Embedded actions — run one-off actions via the Action Runs API