> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> React to events in connected apps. Composio delivers them to your app as structured payloads.

When something happens in a connected app (a new Slack message, a GitHub commit, an incoming email), a **trigger** sends that event to your app as a structured payload. You write the handler. Composio handles the connection to the provider, delivery, retries, and signing.

triggers.delivery

one webhook URL

Connected apps

<ul />

![Composio](</Composio Logo.svg>)

Your application

Your webhook URL

POST /webhooks/composio

One URL receives every event.

app event
→ Composio
→ your
webhook URL

## Where events arrive

Composio delivers every event to one destination you control: your webhook URL. You register it once per project, and Composio `POST`s every trigger event there, signed so you can verify it.

## Realtime vs polling

Under the hood, Composio learns about events in one of two ways. You don't configure this. It's a property of the trigger type, and it only affects how quickly an event reaches you.

| Kind | How Composio learns about the event | Latency | Examples |
| - | - | - | - |
| **Realtime** | The provider pushes the event to Composio the moment it happens. | Near-instant | Slack, Asana, Notion, Outlook |
| **Polling** | Composio checks the provider on a schedule. | Up to the trigger's polling interval. On Composio-managed auth, the shortest allowed interval is 2 min | Gmail, Google Calendar |

Either way, the event lands in the same place: your subscription or webhook URL, in the same payload shape.

> [!NOTE]
>
> If you **bring your own OAuth app**, some providers only deliver to URLs registered on that app, so you register Composio's ingress URL there once. See [Custom OAuth webhooks](https://composio-preview.mintlify.site/docs/setting-up-triggers/custom-oauth-webhooks.md).

## Trigger types and instances

A **trigger type** is a kind of event you can listen for, like `GITHUB_COMMIT_EVENT` or a new Slack message. Each toolkit has its own set.

A **trigger instance** is a trigger type you've activated for one [user's connected account](https://composio-preview.mintlify.site/docs/how-composio-works.md). It has its own `ti_*` ID that you can enable, disable, or delete independently.

## Working with triggers

0. **Authenticate** the user for the toolkit: an [auth config](https://composio-preview.mintlify.site/docs/authentication#behind-the-scenes) and a [connected account](https://composio-preview.mintlify.site/docs/authentication). See [Authentication](https://composio-preview.mintlify.site/docs/authentication).
1. **Create** a trigger for the user's connected account. See [Creating triggers](https://composio-preview.mintlify.site/docs/setting-up-triggers/creating-triggers.md).
2. **Receive** its events: locally with `subscribe()`, or in production at your webhook URL. See [Receiving events](https://composio-preview.mintlify.site/docs/setting-up-triggers/subscribing-to-events.md).
3. **Manage** triggers: enable, disable, or delete. See [Managing triggers](https://composio-preview.mintlify.site/docs/setting-up-triggers/managing-triggers.md).

## Next

> [card] [Creating triggers](https://composio-preview.mintlify.site/docs/setting-up-triggers/creating-triggers.md)
>
> Activate a trigger for a user so events start flowing
