Triggers

Unable to create trigger

Check the error message — the connected account might not have sufficient permissions or the required OAuth scopes. Ensure the user has authenticated with the necessary scopes for the trigger.

For Slack trigger types such as SLACK_CHANNEL_MESSAGE_RECEIVED, SLACK_DIRECT_MESSAGE_RECEIVED, and SLACK_MESSAGE_REACTION_ADDED, create a Slack webhook endpoint before creating the trigger. If the endpoint is missing for the OAuth app in the current project, trigger creation fails with 400. See Creating triggers.

Not receiving payloads

• Polling triggers (e.g., Gmail): These check for new events on an interval you configure. For Composio managed auth, intervals below 15 minutes are not supported.
• Webhook URL: Ensure your URL is publicly accessible and returns a 2xx status code.
• Provider webhook endpoint: For trigger types that require a provider-facing endpoint, ensure the provider dashboard is using the Composio webhook_url, the signing secret is stored on the endpoint, and the endpoint belongs to the same project as the trigger.
• Trigger status: Verify the trigger is enabled, not disabled.
• Logs: Check the trigger logs in the dashboard for delivery attempts and errors.

Type errors with trigger payloads

Use getType() / get_type() to inspect the exact payload schema for a trigger type. This shows you the fields and types you should expect.

Reporting issues

When contacting support, include:

• Trigger ID and connected account ID — find these under Active Triggers in the dashboard:

  

• Error message and reproduction steps

Getting help

• Email: support@composio.dev
• Discord: #support-form