Triggers
When events occur in apps, like a new Slack message, a GitHub commit, or an incoming email, triggers send event data to your application as structured payloads.
There are two delivery types:
- Webhook triggers: Apps like GitHub and Slack push events to Composio in real time. When an event fires, Composio forwards the payload to your webhook endpoint.
- Polling triggers: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data every minute. Expect small delays between the event and delivery.
Working with triggers
- Configure your webhook endpoint so Composio knows where to deliver events
- Discover available trigger types for a toolkit (e.g.,
GITHUB_COMMIT_EVENT) - Create an active trigger scoped to a user's connected account
- Receive events: Composio sends payloads to your endpoint
- Manage: enable, disable, or delete triggers as needed
Triggers are scoped to a connected account. If you haven't set up authentication yet, see Authentication.
Next steps
Creating triggers
Create trigger instances via the dashboard or SDK
Subscribing to events
Receive trigger events via webhooks or SDK subscriptions
Verifying webhooks
Verify webhook signatures and understand payload versions
Managing triggers
Discover, list, enable, disable, and delete triggers
Example: Gmail labeler
Build an automated email labeling agent using triggers