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: update documentation for new changelog entries

github-actions[bot]22ed82c0de3d
diff --git a/docs/content/docs/custom-app-vs-managed-app.mdx b/docs/content/docs/custom-app-vs-managed-app.mdx
index e0ab5db5b..1af5e9ace 100644
--- a/docs/content/docs/custom-app-vs-managed-app.mdx
+++ b/docs/content/docs/custom-app-vs-managed-app.mdx
@@ -24,6 +24,7 @@ Bring your own credentials when any of these apply:
- **Your users see OAuth consent screens.** In production, users should see your app name, not "Composio." This is the most common reason to switch.
- **You need custom scopes.** Composio's default scopes may not include everything you need (e.g., write access to a specific Google API).
- **You're hitting rate limits.** Managed apps share quota across all Composio users. Your own app gets a dedicated quota.
+- **You need faster polling triggers.** Managed auth enforces a 15-minute minimum polling interval; your own app can use shorter polling intervals where supported.
- **You're connecting to a custom instance.** Self-hosted or regional variants (e.g., a private Salesforce subdomain) need their own OAuth app.
- **Enterprise customers require your branding end-to-end.**
diff --git a/docs/content/docs/triggers.mdx b/docs/content/docs/triggers.mdx
index 79fd90c15..93c3a3724 100644
--- a/docs/content/docs/triggers.mdx
+++ b/docs/content/docs/triggers.mdx
@@ -11,7 +11,7 @@ When events occur in apps, like a new Slack message, a GitHub commit, or an inco
There are two delivery types:
- **Webhook triggers**: Apps like GitHub and Slack push events to Composio in real time. When an event fires, Composio forwards the payload to your webhook endpoint.
-- **Polling triggers**: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data every minute. Expect small delays between the event and delivery.
+- **Polling triggers**: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data on a schedule. For Composio managed auth, polling intervals have a minimum of 15 minutes. Expect delays between the source event and delivery.
## Working with triggers
diff --git a/docs/content/docs/troubleshooting/triggers.mdx b/docs/content/docs/troubleshooting/triggers.mdx
index 629bc2d7a..28f60003d 100644
--- a/docs/content/docs/troubleshooting/triggers.mdx
+++ b/docs/content/docs/troubleshooting/triggers.mdx
@@ -9,7 +9,7 @@ Check the error message — the connected account might not have sufficient perm
## Not receiving payloads
-- **Polling triggers** (e.g., Gmail): These check for new events at intervals (~1 min for Gmail). Expect small delays.
+- **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.
- **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.
diff --git a/docs/content/docs/using-custom-auth-configuration.mdx b/docs/content/docs/using-custom-auth-configuration.mdx
index 69ee5e41d..c369971a3 100644
--- a/docs/content/docs/using-custom-auth-configuration.mdx
+++ b/docs/content/docs/using-custom-auth-configuration.mdx
@@ -9,6 +9,7 @@ You create a custom auth config when you need to provide your own credentials fo
- **Toolkit has no managed auth**: PostHog, Tavily, Perplexity, etc. require your own credentials
- **White-labeling**: Show your app name on OAuth consent screens instead of "Composio". See [White-labeling authentication](/docs/white-labeling-authentication)
- **Rate limits**: Composio's default OAuth app shares quota across all users. Your own app gets a dedicated quota
+- **Faster polling triggers**: Composio managed auth enforces a 15-minute minimum polling interval. Your own OAuth app can use shorter polling intervals where supported
- **Custom scopes**: You need permissions beyond what Composio's default app has approved
- **Custom instance**: Connecting to a self-hosted or regional variant (e.g., custom Salesforce subdomain)