@devries-cameron20 / composio Mirror · read-only / commits / 803fe0e35
Fork 0

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 22, 10:45 UTC

docs: restore triggers troubleshooting as standalone page

Move troubleshooting content out of managing-triggers.mdx back into its own page at troubleshooting/triggers.mdx. Add a cross-reference card in managing-triggers instead. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmithamallesh committed Feb 9, 2026 at 15:14 UTC 803fe0e35d013b27ecb5e1bdf4fe2837493ecbc5
3 files changed +38 -33
docs/content/docs/setting-up-triggers/managing-triggers.mdx
+2 -32
@@ -1,7 +1,7 @@
1 ---
2 title: Managing triggers
3 description: Discover, list, enable, disable, and delete trigger instances
4 -keywords: [manage triggers, enable, disable, delete, discover, troubleshooting]
4 +keywords: [manage triggers, enable, disable, delete, discover]
5 ---
6
7 ## Discovering available triggers
@@ -225,34 +225,4 @@ await composio.triggers.delete('ti_abcd123');
225 Deleting a trigger is permanent. If you want to temporarily stop receiving events, use `disable()` instead.
226 </Callout>
227
228 -## Troubleshooting
229 -
230 -### Unable to create trigger
231 -
232 -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.
233 -
234 -### Not receiving payloads
235 -
236 -- **Polling triggers** (e.g., Gmail): These check for new events at intervals (~1 min for Gmail). Expect small delays.
237 -- **Webhook URL**: Ensure your URL is publicly accessible and returns a `2xx` status code.
238 -- **Trigger status**: Verify the trigger is enabled, not disabled.
239 -- **Logs**: Check the [trigger logs](https://platform.composio.dev?next_page=/logs/triggers) in the dashboard for delivery attempts and errors.
240 -
241 -### Type errors with trigger payloads
242 -
243 -Use `getType()` / `get_type()` to inspect the exact payload schema for a trigger type. This shows you the fields and types you should expect.
244 -
245 -### Reporting issues
246 -
247 -When contacting support, include:
248 -
249 -- **Trigger ID** and **connected account ID** — find these under Active Triggers in the dashboard:
250 -
251 - <Figure src="/images/troubleshooting/troubleshooting-trigger-id.png" alt="Trigger ID and connected account ID in the dashboard" size="lg" />
252 -
253 -- **Error message** and **reproduction steps**
254 -
255 -### Getting help
256 -
257 -- **Email**: support@composio.dev
258 -- **Discord**: [#support-form](https://discord.com/channels/1170785031560646836/1268871288156323901)
228 +<Card icon={<Wrench />} title="Troubleshooting triggers" href="/docs/troubleshooting/triggers" description="Common issues and how to resolve them" />
docs/content/docs/troubleshooting/meta.json
+2 -1
@@ -8,6 +8,7 @@
8 "dashboard",
9 "mcp",
10 "sdks",
11 - "tools"
11 + "tools",
12 + "triggers"
13 ]
14 }
docs/content/docs/troubleshooting/triggers.mdx new
+34
@@ -0,0 +1,34 @@
1 +---
2 +title: Triggers
3 +description: Troubleshooting trigger issues
4 +---
5 +
6 +## Unable to create trigger
7 +
8 +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.
9 +
10 +## Not receiving payloads
11 +
12 +- **Polling triggers** (e.g., Gmail): These check for new events at intervals (~1 min for Gmail). Expect small delays.
13 +- **Webhook URL**: Ensure your URL is publicly accessible and returns a `2xx` status code.
14 +- **Trigger status**: Verify the trigger is enabled, not disabled.
15 +- **Logs**: Check the [trigger logs](https://platform.composio.dev?next_page=/logs/triggers) in the dashboard for delivery attempts and errors.
16 +
17 +## Type errors with trigger payloads
18 +
19 +Use `getType()` / `get_type()` to inspect the exact payload schema for a trigger type. This shows you the fields and types you should expect.
20 +
21 +## Reporting issues
22 +
23 +When contacting support, include:
24 +
25 +- **Trigger ID** and **connected account ID** — find these under Active Triggers in the dashboard:
26 +
27 + <Figure src="/images/troubleshooting/troubleshooting-trigger-id.png" alt="Trigger ID and connected account ID in the dashboard" size="lg" />
28 +
29 +- **Error message** and **reproduction steps**
30 +
31 +## Getting help
32 +
33 +- **Email**: support@composio.dev
34 +- **Discord**: [#support-form](https://discord.com/channels/1170785031560646836/1268871288156323901)