@devries-cameron20 / composio Mirror · read-only / commits / 22ed82c0d
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, 03:15 UTC

docs: update documentation for new changelog entries

github-actions[bot] committed Mar 12, 2026 at 04:44 UTC 22ed82c0de3d067d1fe74b58fac914048bb55214
4 files changed +4 -2
docs/content/docs/custom-app-vs-managed-app.mdx
+1
@@ -24,6 +24,7 @@ Bring your own credentials when any of these apply:
24 - **Your users see OAuth consent screens.** In production, users should see your app name, not "Composio." This is the most common reason to switch.
25 - **You need custom scopes.** Composio's default scopes may not include everything you need (e.g., write access to a specific Google API).
26 - **You're hitting rate limits.** Managed apps share quota across all Composio users. Your own app gets a dedicated quota.
27 +- **You need faster polling triggers.** Managed auth enforces a 15-minute minimum polling interval; your own app can use shorter polling intervals where supported.
28 - **You're connecting to a custom instance.** Self-hosted or regional variants (e.g., a private Salesforce subdomain) need their own OAuth app.
29 - **Enterprise customers require your branding end-to-end.**
30
docs/content/docs/triggers.mdx
+1 -1
@@ -11,7 +11,7 @@ When events occur in apps, like a new Slack message, a GitHub commit, or an inco
11 There are two delivery types:
12
13 - **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.
14 -- **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.
14 +- **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.
15
16 ## Working with triggers
17
docs/content/docs/troubleshooting/triggers.mdx
+1 -1
@@ -9,7 +9,7 @@ Check the error message — the connected account might not have sufficient perm
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.
12 +- **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.
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.
docs/content/docs/using-custom-auth-configuration.mdx
+1
@@ -9,6 +9,7 @@ You create a custom auth config when you need to provide your own credentials fo
9 - **Toolkit has no managed auth**: PostHog, Tavily, Perplexity, etc. require your own credentials
10 - **White-labeling**: Show your app name on OAuth consent screens instead of "Composio". See [White-labeling authentication](/docs/white-labeling-authentication)
11 - **Rate limits**: Composio's default OAuth app shares quota across all users. Your own app gets a dedicated quota
12 +- **Faster polling triggers**: Composio managed auth enforces a 15-minute minimum polling interval. Your own OAuth app can use shorter polling intervals where supported
13 - **Custom scopes**: You need permissions beyond what Composio's default app has approved
14 - **Custom instance**: Connecting to a self-hosted or regional variant (e.g., custom Salesforce subdomain)
15