Skip to content

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: restore triggers troubleshooting as standalone page

Sushmithamallesh803fe0e35d01
diff --git a/docs/content/docs/setting-up-triggers/managing-triggers.mdx b/docs/content/docs/setting-up-triggers/managing-triggers.mdx
index ed1d4e296..020390fa6 100644
--- a/docs/content/docs/setting-up-triggers/managing-triggers.mdx
+++ b/docs/content/docs/setting-up-triggers/managing-triggers.mdx
@@ -1,7 +1,7 @@
---
title: Managing triggers
description: Discover, list, enable, disable, and delete trigger instances
-keywords: [manage triggers, enable, disable, delete, discover, troubleshooting]
+keywords: [manage triggers, enable, disable, delete, discover]
---
## Discovering available triggers
@@ -225,34 +225,4 @@ await composio.triggers.delete('ti_abcd123');
Deleting a trigger is permanent. If you want to temporarily stop receiving events, use `disable()` instead.
</Callout>
-## Troubleshooting
-
-### 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.
-
-### Not receiving payloads
-
-- **Polling triggers** (e.g., Gmail): These check for new events at intervals (~1 min for Gmail). Expect small delays.
-- **Webhook URL**: Ensure your URL is publicly accessible and returns a `2xx` status code.
-- **Trigger status**: Verify the trigger is enabled, not disabled.
-- **Logs**: Check the [trigger logs](https://platform.composio.dev?next_page=/logs/triggers) 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:
-
- <Figure src="/images/troubleshooting/troubleshooting-trigger-id.png" alt="Trigger ID and connected account ID in the dashboard" size="lg" />
-
-- **Error message** and **reproduction steps**
-
-### Getting help
-
-- **Email**: [email protected]
-- **Discord**: [#support-form](https://discord.com/channels/1170785031560646836/1268871288156323901)
+<Card icon={<Wrench />} title="Troubleshooting triggers" href="/docs/troubleshooting/triggers" description="Common issues and how to resolve them" />
diff --git a/docs/content/docs/troubleshooting/meta.json b/docs/content/docs/troubleshooting/meta.json
index 4964f71c3..ab36ebb3c 100644
--- a/docs/content/docs/troubleshooting/meta.json
+++ b/docs/content/docs/troubleshooting/meta.json
@@ -8,6 +8,7 @@
"dashboard",
"mcp",
"sdks",
- "tools"
+ "tools",
+ "triggers"
]
}
diff --git a/docs/content/docs/troubleshooting/triggers.mdx b/docs/content/docs/troubleshooting/triggers.mdx
new file mode 100644
index 000000000..629bc2d7a
--- /dev/null
+++ b/docs/content/docs/troubleshooting/triggers.mdx
@@ -0,0 +1,34 @@
+---
+title: Triggers
+description: Troubleshooting trigger issues
+---
+
+## 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.
+
+## Not receiving payloads
+
+- **Polling triggers** (e.g., Gmail): These check for new events at intervals (~1 min for Gmail). Expect small delays.
+- **Webhook URL**: Ensure your URL is publicly accessible and returns a `2xx` status code.
+- **Trigger status**: Verify the trigger is enabled, not disabled.
+- **Logs**: Check the [trigger logs](https://platform.composio.dev?next_page=/logs/triggers) 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:
+
+ <Figure src="/images/troubleshooting/troubleshooting-trigger-id.png" alt="Trigger ID and connected account ID in the dashboard" size="lg" />
+
+- **Error message** and **reproduction steps**
+
+## Getting help
+
+- **Email**: [email protected]
+- **Discord**: [#support-form](https://discord.com/channels/1170785031560646836/1268871288156323901)