Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
TypeScript agentic-aiagentsaiai-agentsaiagentsdeveloper-toolsfunction-callinggpt-4javascriptjsllmllmopsmcppythonremote-mcp-serverssetypescript
docs: polling interval grace period for existing customers
Palash Kala1f6a5b448ebc
diff --git a/docs/content/changelog/03-11-26-polling-interval-changes.mdx b/docs/content/changelog/03-11-26-polling-interval-changes.mdxindex deb00fc32..75be0edee 100644--- a/docs/content/changelog/03-11-26-polling-interval-changes.mdx+++ b/docs/content/changelog/03-11-26-polling-interval-changes.mdx@@ -4,6 +4,10 @@ description: "Default polling interval increasing from 1 minute to 15 minutes, wdate: "2026-03-11"---+<Callout type="warn">+**Update (March 13, 2026):** Existing customers have a grace period until May 1, 2026. See [updated changelog](/docs/changelog/2026/03/13).+</Callout>+We're updating **polling trigger intervals** to improve platform reliability and avoid rate limiting. This change affects how frequently polling triggers execute.## What's Changing?diff --git a/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx b/docs/content/changelog/03-13-26-polling-interval-grace-period.mdxnew file mode 100644index 000000000..8086e33be--- /dev/null+++ b/docs/content/changelog/03-13-26-polling-interval-grace-period.mdx@@ -0,0 +1,37 @@+---+title: "Polling Intervals: Grace Period for Existing Customers"+description: "Existing customers keep 1-minute polling until May 1. New triggers default to 15 minutes."+date: "2026-03-13"+---++We're introducing a **grace period** for existing customers to transition to the new polling interval limits.++## Timeline++| Customer Type | Polling Interval | Until When |+|---------------|------------------|------------|+| **Existing** (triggers before today) | 1 minute | May 1, 2026 |+| **New** (triggers from today) | 15 minutes minimum | Now |++If any of your triggers were affected by the recent changes, we've restored them to their original intervals.++## Why 15 Minutes?++Composio-managed OAuth apps share rate limits across all users. At scale, 1-minute polling causes rate limiting and service degradation. The 15-minute minimum ensures reliability for everyone.++## How to Keep 1-Minute Polling++Set up **your own OAuth app**. With custom auth:+- Intervals as low as 1 minute+- Your own rate limits+- No platform limits, ever++<Callout type="warn">+OAuth approval from Google, Microsoft, etc. takes **days to weeks**. Start now.+</Callout>++→ [Set up your own OAuth app](/docs/custom-app-vs-managed-app)++## Alternatives++For real-time events, use **webhook triggers** — instant delivery, no polling limits.diff --git a/docs/content/docs/custom-app-vs-managed-app.mdx b/docs/content/docs/custom-app-vs-managed-app.mdxindex 1af5e9ace..8cdd62caf 100644--- a/docs/content/docs/custom-app-vs-managed-app.mdx+++ b/docs/content/docs/custom-app-vs-managed-app.mdx@@ -24,7 +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 need faster polling triggers.** New triggers with managed auth have a 15-minute minimum (existing triggers until May 1, 2026). Your own OAuth app can use intervals as low as 1 minute — now and always.- **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.mdxindex 93c3a3724..00bc04618 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 incoThere 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 on a schedule. For Composio managed auth, polling intervals have a minimum of 15 minutes. Expect delays between the source event and delivery.+- **Polling triggers**: For apps that don't support outgoing webhooks (e.g., Gmail), Composio polls for new data on a schedule. New triggers with Composio-managed auth have a 15-minute minimum interval; existing triggers (before March 13, 2026) keep current intervals until May 1, 2026. [Use your own OAuth app](/docs/custom-app-vs-managed-app) for shorter intervals.## Working with triggersdiff --git a/docs/content/docs/troubleshooting/triggers.mdx b/docs/content/docs/troubleshooting/triggers.mdxindex 28f60003d..be7dc5357 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 on an interval you configure. For Composio managed auth, intervals below 15 minutes are not supported.+- **Polling triggers** (e.g., Gmail): These check for new events on an interval you configure. New triggers with Composio-managed auth have a 15-minute minimum. Existing triggers keep current intervals until May 1, 2026. [Use your own OAuth app](/docs/custom-app-vs-managed-app) for shorter intervals.- **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.mdxindex c369971a3..891ae973e 100644--- a/docs/content/docs/using-custom-auth-configuration.mdx+++ b/docs/content/docs/using-custom-auth-configuration.mdx@@ -9,7 +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+- **Faster polling triggers**: New triggers with Composio-managed auth have a 15-minute minimum. Your own OAuth app can use intervals as low as 1 minute- **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)