Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 06:00 UTC
| 1 | ## Find every toolkit that currently supports triggers |
| 2 | |
| 3 | Do not rely on a dashboard count as the complete trigger catalog because availability changes and list views can be partial. |
| 4 | |
| 5 | - Call `GET /api/v3.1/triggers_types` to list trigger types and their parent toolkits. Use `toolkit_slugs` to narrow the result when needed. |
| 6 | - Or call `GET /api/v3.1/toolkits` and select toolkits whose `triggers_count` is greater than zero. |
| 7 | - Follow pagination through every result page before calculating a total or claiming the list is complete. |
| 8 | - Each trigger type declares its required configuration and may be webhook/event-driven or polling-based. |
| 9 | |
| 10 | References: [trigger types API](https://docs.composio.dev/reference/api-reference/triggers/getTriggersTypes), [toolkits API](https://docs.composio.dev/reference/api-reference/toolkits/getToolkits), and [creating triggers](https://docs.composio.dev/docs/setting-up-triggers/creating-triggers). |
| 11 | |
| 12 | ## Trigger webhook delivery is at-least-once |
| 13 | |
| 14 | A receiver can occasionally see the same trigger webhook more than once, including the same `log_id` or provider event/message ID, when an outbound delivery attempt is retried. This does not necessarily mean Composio ingested the provider event twice. |
| 15 | |
| 16 | Webhook handlers should be idempotent and deduplicate on a stable identifier such as `log_id`, the provider message/event ID, or the webhook event ID. If duplicates continue beyond normal retry behavior, contact Composio support with the relevant IDs and receipt timestamps. |