Skip to main content
A trigger watches for one event (like GITHUB_COMMIT_EVENT) on one user’s connected account. Create one, and events start flowing to your subscription or webhook URL. For the bigger picture, see Triggers. The user needs a connected account for the toolkit you want to monitor. See Authentication if you haven’t set that up.

Inspect the trigger type

To connect trigger setup to a working agent, follow Run an agent when an email arrives. Each trigger type declares the config it needs. Check it before you create, so you pass the right fields.

Create the trigger

Pass the user, the trigger slug, and the config the type requires.
You only pass a user_id. Composio resolves that user’s connected account for the toolkit automatically.

Targeting a specific connected account

If a user has more than one connected account for the toolkit, Composio uses the first active connection for the user and the trigger’s toolkit. Pass a connected account ID to pick exactly which account the trigger watches.
Trigger instances default to the 'latest' toolkit version. If you parse payloads against a fixed schema, pin a version at SDK initialization. The trigger instance is created. Next, receive its events and test with a new matching event in the provider. If nothing arrives, follow Troubleshooting triggers.

Next

Receiving events