@devries-cameron20 / composio-1 / commits / 71862b8f9
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.

docs: add support-informed toolkit FAQs (#3692)

## Summary - Ports support-workflows toolkit KB into public toolkit FAQ docs for 85 toolkit FAQ files. - Creates 46 new toolkit FAQ files for toolkits that had KB but no FAQ file yet. - Updates existing toolkit FAQ files without deleting current public answers. ## General docs updates - Clarifies connected-account credential redaction and reconnect/refresh semantics. - Documents Proxy Execute scoped-key and v3.1/current-SDK requirements. - Adds retry risk guidance for non-idempotent direct tool executions. - Adds remote sandbox temporary state/file retention guidance. - Adds Composio Connect vs developer project boundary guidance for MCP app connections. ## Verification - Hygiene grep passed on changed files: `Plain|T-|SUP-|PRO-|Linear|plain.com|linear.app|/Users/|support-workflows|TODO|FIXME|\[eng:|customer`. - `git diff --check` passed. - `bun run lint:links` passed: 0 errored files, 0 errors. - `bun run build` passed. Build emitted the existing Turbopack NFT warning plus toolkit-detail fetch skips because `COMPOSIO_API_KEY` is not set locally. - Render spot checks passed for Gmail, Apollo, SharePoint, Google Calendar, connected accounts, and remote sandbox pages. ## Deferred - PowerPoint KB was not added because the current docs toolkit catalog has no `powerpoint` toolkit slug/page. The KB describes a possible future file-operations toolkit rather than an existing public toolkit page. --------- Co-authored-by: Sarah Simionescu <sarah@composio.dev> Co-authored-by: Alberto Schiabel <jkomyno@users.noreply.github.com>

Abhishek Patil committed Jul 13, 2026 at 15:48 UTC 71862b8f973533e8dd191e63dac50e53c1fd55d2
53 files changed +296 -107
docs/content/toolkits/faq/apollo.md new
+7
@@ -0,0 +1,7 @@
1 +## Why can Apollo search or enrichment tools return HTTP 403?
2 +
3 +Apollo API keys can be limited to specific endpoint groups. A tool can return HTTP 403 or `Forbidden` when the underlying Apollo API rejects the key for that operation, even if the same key works for other Apollo tools.
4 +
5 +This can affect gated search, enrichment, usage, and outreach tools such as `APOLLO_PEOPLE_SEARCH`, `APOLLO_ORGANIZATION_SEARCH`, `APOLLO_SEARCH_ACCOUNTS`, `APOLLO_SEARCH_OUTREACH_EMAILS`, `APOLLO_PEOPLE_ENRICHMENT`, `APOLLO_BULK_PEOPLE_ENRICHMENT`, `APOLLO_ORGANIZATION_ENRICHMENT`, `APOLLO_BULK_ORGANIZATION_ENRICHMENT`, and `APOLLO_VIEW_API_USAGE_STATS`.
6 +
7 +In Apollo, make sure the API key has access to the relevant endpoint group or has **Set as master key** turned on. If the Apollo plan does not include the requested API feature, the tool can still return 403 until that access is enabled in Apollo.
docs/content/toolkits/faq/calendly.md
+3 -1
@@ -1,3 +1,5 @@
1 ## Why can't I configure individual scopes for Calendly?
2 -Calendly's OAuth model grants the access token for all requested scopes at once during authorization; users cannot selectively approve individual scopes. Configure scopes when creating your OAuth app — the resulting access token will include all requested permissions.
2
3 +Calendly does not let end users selectively approve individual scopes during the OAuth connection flow. The scopes configured in your Calendly OAuth app are the scopes that will be requested during authorization, and the resulting access token will include that configured permission set.
4 +
5 +To change Calendly permissions, update the scopes in your OAuth app/auth config and reconnect the account so a new token is issued with the updated scopes.
docs/content/toolkits/faq/discordbot.md new
+5
@@ -0,0 +1,5 @@
1 +## Why can DiscordBot return 401 on the default app?
2 +
3 +DiscordBot tool calls can return `401 {"message":"401: Unauthorized","code":0}` even when the connected account is active if the connection uses the default DiscordBot app.
4 +
5 +The default app currently has a managed bot-token issue: Discord is rejecting the shared bot token behind that app, so the connection flow can complete while bot API calls still fail. Use your own Discord app credentials in a custom DiscordBot auth config for now. Reconnect through that custom config before retrying the DiscordBot tool call.
docs/content/toolkits/faq/docusign.md new
+3
@@ -0,0 +1,3 @@
1 +## How do I create my own DocuSign OAuth app?
2 +
3 +Create and configure your own DocuSign OAuth app when you want to use your own DocuSign credentials with Composio. For the setup steps, see [How to create OAuth credentials for DocuSign](https://composio.dev/auth/docusign).
docs/content/toolkits/faq/figma.md new
+11
@@ -0,0 +1,11 @@
1 +## Why can `FIGMA_EXTRACT_DESIGN_TOKENS` fail when `include_variables` is enabled?
2 +
3 +When `include_variables` is enabled, the tool calls Figma's local variables endpoint and the connected account must have the `file_variables:read` scope. If Figma returns a 403 saying the endpoint requires `file_variables:read`, reconnect with Figma credentials that can grant that scope. Figma exposes this scope only for Enterprise organization members.
4 +
5 +If you do not need Figma variables, set `include_variables` to `false`. The tool can still extract tokens from local styles and nodes without calling the variables endpoint.
6 +
7 +## What can cause Figma 429s?
8 +
9 +A 429 means Figma rate limited the request. Confirm the response is coming from Figma, reduce request volume, add backoff, and retry after the provider limit resets.
10 +
11 +Default Figma auth is useful for quick testing. For production traffic, use your own Figma credentials so your app controls its scopes, traffic pattern, and rate-limit exposure.
docs/content/toolkits/faq/firecrawl.md new
+3
@@ -0,0 +1,3 @@
1 +## Batch fewer URLs or raise timeout for long Firecrawl scrape jobs
2 +
3 +For Firecrawl scrape timeouts, reduce the number of links per request, such as batching 1-2 links at a time for complex pages, or increase the scrape timeout if the tool call supports it. A useful starting timeout is `120000` milliseconds for roughly a 2-minute timeout.
docs/content/toolkits/faq/gemini.md new
+9
@@ -0,0 +1,9 @@
1 +## How does Gemini shared quota work?
2 +
3 +Gemini no-auth toolkit calls use Composio-managed Gemini credentials at execution time, so provider quota is shared across usage on that runtime key. If you see Gemini 429 or `RESOURCE_EXHAUSTED` errors, reduce concurrency and retry with exponential backoff.
4 +
5 +Bring-your-own-key or custom-key quota isolation is not currently supported for this Gemini no-auth path. Support for custom Gemini API keys is being worked on.
6 +
7 +## How is Gemini no-auth toolkit usage logged?
8 +
9 +Gemini no-auth toolkit calls are logged like other toolkit calls and can be tracked in Composio tool logs. Treat Gemini usage as regular toolkit usage based on tool calls.
docs/content/toolkits/faq/github.md new
+7
@@ -0,0 +1,7 @@
1 +## Does Composio support GitHub Apps?
2 +
3 +Yes. You can bring your own GitHub App by configuring its client ID and client secret in the GitHub auth config.
4 +
5 +The GitHub App installation step is separate from the OAuth credential setup. The user still needs to install the GitHub App on the relevant account or organization and grant repository access before GitHub App based tool calls can work. GitHub App permissions come from the app's GitHub settings and installation grant, not from auth config scopes.
6 +
7 +Composio does not currently provide the GitHub App installation link automatically during this flow. Provide your GitHub App installation link to the user, have them install the app, then complete the connection. Built-in installation-link handling is being worked on.
docs/content/toolkits/faq/gmail.md
+9 -1
@@ -51,4 +51,12 @@ result = composio.tools.execute(
51
52 This approach works for any tool whose parameters accept file uploads. See [Automatic File Handling](/docs/tools-direct/executing-tools#automatic-file-handling) for more details.
53
54 ----
54 +## Why can Gmail filter setup show an app-blocked error?
55 +
56 +If a user on Composio-managed Gmail auth hits Google's "app is blocked" / unverified-app screen after adding `gmail.settings.basic`, use your own Google OAuth app verified for `https://www.googleapis.com/auth/gmail.settings.basic`, then reconnect.
57 +
58 +## When should I avoid `gmail.metadata` when fetching full Gmail email content?
59 +
60 +Use `https://www.googleapis.com/auth/gmail.metadata` only when the app needs message metadata such as labels and headers, not message bodies or payload content. Gmail treats `gmail.metadata` as a restricted metadata-only scope, and it is not compatible with broader content-access scopes such as `gmail.readonly`, `gmail.modify`, or `mail.google.com` in the same OAuth request.
61 +
62 +If a tool needs full email content, remove `gmail.metadata` from the auth config and request a Gmail scope that allows message content access. Then reconnect the account so the new scope set is granted.
docs/content/toolkits/faq/google_classroom.md
-2
@@ -23,5 +23,3 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
23 ## Why am I getting 401 errors on tool calls?
24
25 The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
26 -
27 ----
docs/content/toolkits/faq/google_maps.md
+5 -1
@@ -24,4 +24,8 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
24
25 The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
26
27 ----
27 +## What is required for the Maps Embed API?
28 +
29 +`GOOGLE_MAPS_MAPS_EMBED_API` is API-key based. Google's Maps Embed API requires an API key on each request; OAuth2 is not the auth path for this tool.
30 +
31 +You must use an API-key connection to use this tool.
docs/content/toolkits/faq/googleads.md
+30 -4
@@ -1,7 +1,33 @@
1 -## Why am I getting Google Ads quota errors after a successful login?
1 +## Google Ads developer token now belongs on the auth config, not connection initiation
2
3 -Google Ads API requests use both an OAuth access token and a Google Ads developer token. A successful OAuth connection only confirms that the user granted access; it does not mean the developer-token quota is dedicated to your project.
3 +Google Ads was changed so the developer token lives on the auth config itself, not on each connection initiation request. Older auth configs created before this change do not have the developer token field, and new connections through those auth configs can fail because the token is no longer accepted at the connection level. Create a new Google Ads authConfig with the developer token included, then create a fresh connection through that authConfig.
4
5 -If you use Composio's managed Google Ads connector, requests may use Composio's shared Google Ads developer token. Errors like `RESOURCE_EXHAUSTED`, `rateScope: DEVELOPER`, or `Number of operations for basic access` mean Google is throttling that developer-token quota, even when your connected Google Ads account has low usage.
5 +![Google Ads auth config form showing the developer token field under custom developer credentials.](/images/kb/toolkits/googleads/google-ads-developer-token-auth-config.png)
6
7 -For a short-term retry, wait for the retry window returned by Google. For production workloads, create a custom Google Ads auth config with your own OAuth client credentials and Google Ads developer token, so quota and access limits are isolated to your Google Ads setup. See [custom auth configs](/docs/auth-configuration/custom-auth-configs).
7 +## What can cause Google Ads 429s?
8 +
9 +A Google Ads 429 / `RESOURCE_EXHAUSTED` is an upstream Google Ads API limit, not a Composio billing-plan or tool-call quota. Google Ads enforces limits on the underlying developer token, account, request pattern, service, and resource usage.
10 +
11 +This can happen with Composio-managed credentials or with custom Google Ads credentials. Reduce request volume, add backoff, simplify expensive queries, and use an owned Google Ads OAuth app/developer token for production isolation where possible.
12 +
13 +## Google Ads MCC/sub-account targeting
14 +
15 +For Google Ads manager-account (MCC) setups, `GOOGLEADS_LIST_ACCESSIBLE_CUSTOMERS` can succeed while GAQL/reporting or campaign calls against a child account fail. Two common Google errors are:
16 +
17 +- 403 `USER_PERMISSION_DENIED` with guidance that, when accessing a client customer, the manager customer ID must be set in the `login-customer-id` header.
18 +- `REQUESTED_METRICS_FOR_MANAGER` when metric fields are queried directly from the MCC manager account instead of a child/customer account.
19 +
20 +Treat this as MCC targeting/account-context, not OAuth. Reconnecting alone does not fix it unless the user had connected the wrong account context.
21 +
22 +Correct call shape:
23 +
24 +- target child/customer account ID in the request path, for example `/customers/{child_customer_id}/googleAds:searchStream`
25 +- manager/MCC customer ID in the `login-customer-id` header
26 +
27 +## Google Ads OAuth callback token-exchange failures usually point to bad credentials
28 +
29 +The `OAuth callback failed during token exchange` error usually means the credentials used to complete the auth flow are incorrect, most often the client secret. Re-enter or update the client secret in the Google Ads auth config, make sure there are no leading/trailing spaces, and initiate a new connection.
30 +
31 +## What do custom Google OAuth apps need for white-label consent?
32 +
33 +For Google toolkits, creating a new authConfig with the user's OAuth app credentials is not enough for full white-label consent. They also need to route the callback through their own domain using their own redirect URI so Google displays the configured consent screen for that OAuth app.
docs/content/toolkits/faq/googlebigquery.md new
+7
@@ -0,0 +1,7 @@
1 +## Why do I see "This app is blocked" when connecting Google BigQuery?
2 +
3 +Google can show "This app is blocked" during the BigQuery OAuth flow when the OAuth app requests Google scopes that are not approved or verified for that app.
4 +
5 +For managed Google BigQuery OAuth, this can happen because Composio's managed OAuth app does not yet have the required BigQuery scope approved. That scope is still under verification, which is why Google can block the connection.
6 +
7 +To unblock production usage, use your own verified Google OAuth app in a custom auth config with the BigQuery scopes your workflow needs, then reconnect the account. If your setup can use service-account auth for BigQuery, that can also avoid the user-consent OAuth screen.
docs/content/toolkits/faq/googlecalendar.md
-2
@@ -23,5 +23,3 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
23 ## Why am I getting 401 errors on tool calls?
24
25 The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
26 -
27 ----
docs/content/toolkits/faq/googledocs.md
+1 -3
@@ -22,10 +22,8 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
22
23 ## Why am I getting 401 errors on tool calls?
24
25 -The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
25 +The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit was exceeded. Re-authenticating the user typically resolves this.
26
27 ## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
28
29 Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
30 -
31 ----
docs/content/toolkits/faq/googledrive.md
-2
@@ -23,5 +23,3 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
23 ## Why am I getting 401 errors on tool calls?
24
25 The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
26 -
27 ----
docs/content/toolkits/faq/googlemeet.md
+5 -1
@@ -28,4 +28,8 @@ The user's access token is no longer valid. Common causes: the user revoked acce
28
29 Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
30
31 ----
31 +## Why do Google Meet calls return 403 on conference records or artifacts?
32 +
33 +Google Meet conference records and artifacts are provider-side resources. If a tool returns an error such as "Permission denied on resource Conference (or it might not exist)", verify that the conference record exists, the connected Google account can access that meeting or artifact, and the workspace edition supports the artifact being requested.
34 +
35 +For recordings specifically, Google only makes recording available on supported Google Workspace editions such as Business Standard/Plus, Enterprise Standard/Plus, Education Plus, Essentials, Enterprise Essentials, and Enterprise Essentials Plus. Recording also has to be enabled by the Workspace admin, and artifacts are saved to the meeting organizer's Drive.
docs/content/toolkits/faq/googlesheets.md
+2 -4
@@ -22,10 +22,8 @@ By default, the consent screen uses Composio's OAuth app. To show your own app n
22
23 ## Why am I getting 401 errors on tool calls?
24
25 -The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit (~50 per account) was exceeded. Re-authenticating the user typically resolves this.
25 +The user's access token is no longer valid. Common causes: the user revoked access, changed their password or 2FA, a Workspace admin policy changed, or Google's refresh token limit was exceeded. Re-authenticating the user typically resolves this.
26
27 ## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
28
29 -Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
30 -
31 ----
29 +Google enforces per-minute and daily request quotas. These errors may also appear as a 429. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
docs/content/toolkits/faq/googleslides.md
-2
@@ -27,5 +27,3 @@ The user's access token is no longer valid. Common causes: the user revoked acce
27 ## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
28
29 Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
30 -
31 ----
docs/content/toolkits/faq/googlesuper.md
+2 -4
@@ -4,9 +4,9 @@ For a step-by-step guide on creating and configuring your own Google OAuth crede
4
5 ## Why am I seeing "App is blocked" when connecting Google Super?
6
7 -The OAuth client is requesting scopes that Google hasn't verified for that client. This usually happens when you add extra scopes beyond the defaults.
7 +Google Super requires broad Google Workspace scopes for some cross-product workflows, and some of those scopes are not available on Composio-managed Google Super auth today. If users see Google's "App is blocked" or unverified-app screen with managed Google Super auth, use your own verified Google OAuth app and reconnect through a custom auth config.
8
9 -Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification. See [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
9 +Composio is working on getting the managed Google Super app approved for the needed scopes, but until that is complete, custom Google OAuth is the workaround for production usage. See [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
10
11 ## Why am I getting the "API has not been used in project" error?
12
@@ -19,5 +19,3 @@ The requested scopes are invalid or incorrectly formatted in the authorization U
19 ## Why does the OAuth consent screen show "Composio" instead of my app?
20
21 By default, the consent screen uses Composio's OAuth app. To show your own app name and logo, create your own OAuth app and set a custom redirect URL. See [White-labeling authentication](/docs/white-labeling-authentication#using-your-own-oauth-apps).
22 -
23 ----
docs/content/toolkits/faq/googletasks.md
-2
@@ -27,5 +27,3 @@ The user's access token is no longer valid. Common causes: the user revoked acce
27 ## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
28
29 Google enforces per-minute and daily request quotas. If you're using Composio's default OAuth app, you share that quota with other users, which can cause limits to be hit faster. Use your own OAuth app credentials to get a dedicated quota, and add exponential backoff and retries to handle transient rate limits.
30 -
31 ----
docs/content/toolkits/faq/hubspot.md
+11 -5
@@ -1,10 +1,10 @@
1 ## Why do users see a "Connecting an unverified app" warning?
2
3 -HubSpot shows this warning when the OAuth app being installed has not been approved by HubSpot's ecosystem review process. The OAuth connection can still work, but HubSpot asks the user to explicitly accept the risk before continuing.
3 +HubSpot shows this warning because the default Composio-managed HubSpot OAuth app is still awaiting HubSpot approval. The connection can still work, but HubSpot asks the user to explicitly accept the warning before continuing.
4
5 -For Composio-managed HubSpot auth, this depends on Composio's HubSpot app approval status. We are actively working through HubSpot's approval process and expect this to be resolved in the near future. Once the Composio HubSpot app is approved by HubSpot, this warning should stop appearing for new installs that use the approved app.
5 +Composio is working on getting the default HubSpot OAuth app approved, but there is no concrete ETA because the final review timeline depends on HubSpot.
6
7 -For custom auth, the warning depends on your own HubSpot developer app. If your users see this warning with custom credentials, submit your HubSpot app for the relevant HubSpot approval or listing flow.
7 +If this warning blocks your rollout, use your own HubSpot OAuth app credentials in a custom Composio auth config. That lets you control the app identity, review status, and consent screen shown to your users.
8
9 ## Should I use Composio-managed auth or my own HubSpot OAuth app?
10
@@ -16,7 +16,7 @@ You cannot add new scopes to the managed app, and you cannot remove scopes that
16
17 Use your own HubSpot OAuth app when you need a different scope set, your own app name and branding on the consent screen, tighter control over app review and rollout, or a production setup owned by your team. For setup steps, see [How to create OAuth credentials for HubSpot](https://composio.dev/auth/hubspot).
18
19 -## How do HubSpot scopes work in Composio?
19 +## How do scopes work in HubSpot?
20
21 The scope category must match between Composio and your HubSpot developer app.
22
@@ -89,4 +89,10 @@ After changing scopes, reconnect affected HubSpot accounts. Existing connected a
89 - **Webhook setup errors:** HubSpot webhooks require a public app with an App ID and Developer API Key. Private or internal apps cannot receive webhooks.
90 - **Refresh or expiry errors:** Common causes include the user revoking the app in HubSpot, HubSpot app credentials changing, the refresh token being invalidated, or the connected account being reauthorized with a different app configuration. After rotating custom OAuth credentials or changing the HubSpot developer app, reconnect affected HubSpot accounts.
91
92 ----
92 +## HubSpot auth loops can be caused by HubSpot-side workspace/login state
93 +
94 +If the HubSpot flow loops while Composio works on its side, retry while logged into the correct HubSpot workspace and confirm the OAuth app is public/configured correctly.
95 +
96 +## HubSpot triggers require each user’s own app ID and developer API key
97 +
98 +HubSpot webhook APIs need the specific HubSpot app that should receive webhook notifications. For user HubSpot triggers, `app_id` and developer API key are required because each user needs their own HubSpot app for webhook delivery.
docs/content/toolkits/faq/instagram.md new
+9
@@ -0,0 +1,9 @@
1 +## Instagram requires a Business or Creator account
2 +
3 +Instagram toolkit support is for Instagram Business/Creator account flows. If a user is using a personal Instagram account, convert or connect a Business/Creator account linked through Meta/Facebook as required by Instagram's API.
4 +
5 +## Why can Instagram reply-to-comment fail with the managed OAuth app?
6 +
7 +Instagram comment tools can require Meta's comment-management permission, such as `instagram_manage_comments` for Facebook Login or `instagram_business_manage_comments` for Instagram Business Login. Those permissions must be configured on the Meta app and approved by Meta before the OAuth flow can grant them.
8 +
9 +If a reply-to-comment flow fails because the managed OAuth app does not currently have the required comment permission, use your own Meta OAuth app with that permission configured and approved. Composio is working on managed-app approval for the missing permission, but an owned Meta app is the current unblock path for production usage.
docs/content/toolkits/faq/jira.md
-2
@@ -5,5 +5,3 @@ For a step-by-step guide on creating and configuring your own Jira OAuth credent
5 ## What is the difference between JQL GET, JQL POST, and Search Issues?
6
7 JQL GET and POST target the same search functionality but use different HTTP methods. POST supports complex queries in the request body. Search Issues uses JQL POST under the hood with extra parameters and filters. For consistent results, prefer POST for complex queries. Use the `fields` parameter to request specific fields, or `["*all"]` to request all fields.
8 -
9 ----
docs/content/toolkits/faq/linkedin.md
-2
@@ -9,5 +9,3 @@ The default OAuth app is shared across users and has strict rate limits. Use you
9 ## Why can't I use certain LinkedIn scope combinations?
10
11 LinkedIn restricts certain scope combinations. For example, `w_member_social` and `r_organization_admin` cannot be used together. If you need conflicting scopes, create your own OAuth app with the required permissions.
12 -
13 ----
docs/content/toolkits/faq/mailchimp.md new
+3
@@ -0,0 +1,3 @@
1 +## Some Mailchimp tools require at least the Mailchimp Essentials plan
2 +
3 +If Mailchimp tools fail despite the connection looking correct, check the user's Mailchimp plan. Some Mailchimp API/tool capabilities require at least the Mailchimp Essentials plan. A free Mailchimp account may not be enough for the requested tool flow.
docs/content/toolkits/faq/monday.md
+14 -38
@@ -1,47 +1,23 @@
1 -## Why is Monday.com OAuth2 not working for my users?
1 +## Why do I see "App is not installed" when connecting Monday?
2
3 -Monday.com requires a workspace admin to install the OAuth2 app before any user in that workspace can authorize their account. If the app is not installed, users will see an authorization error when trying to connect.
3 +Monday requires the OAuth app to be installed in the target workspace before users can authorize their accounts. If the app is not installed, Monday can stop the connection flow with an "App is not installed" message.
4
5 -## How do I install the Composio OAuth2 app for Monday.com?
5 +![Monday authorization screen showing that the app is not installed before authorization can continue.](/images/kb/toolkits/monday/monday-app-not-installed.png)
6
7 -A workspace admin needs to visit the following URL and approve the app installation:
7 +A Monday workspace admin only needs to install the app once per workspace. After the admin approves the installation, users in that workspace can connect their Monday accounts normally.
8
9 -`https://auth.monday.com/oauth2/authorize?client_id=96b038435fc029e045f9ba800e66fefa&response_type=install`
9 +If you are using the Composio-managed Monday app, ask a Monday workspace admin to install it with this link: `https://auth.monday.com/oauth2/authorize?client_id=96b038435fc029e045f9ba800e66fefa&response_type=install`.
10
11 -Once the admin has installed the app, users in that workspace can authorize their accounts using OAuth2 as usual.
11 +We are working on making this flow smoother so developers do not need to manually share the install link.
12
13 -## Do I need to install the app for each user?
13 +## How do I set up custom OAuth credentials for Monday.com?
14
15 -No. The admin only needs to install the app once per workspace. After that, any user in the workspace can connect their Monday.com account through Composio's OAuth2 flow.
15 +For a step-by-step guide on creating and configuring your own Monday.com OAuth credentials, see [How to create OAuth2 credentials for Monday](https://composio.dev/auth/monday).
16
17 -## How do I set up custom OAuth credentials for Monday.com?
17 +For a custom Monday OAuth app, add the Composio redirect URL/callback URL to the Monday app settings. After the OAuth flow completes, the access token is populated automatically.
18 +
19 +## How do Monday scopes work?
20 +
21 +Monday scopes are configured on the Monday OAuth app and picked up during authorization. For the common connection flow, you do not need to configure scopes separately in the auth config.
22
19 -For a step-by-step guide on creating and configuring your own Monday.com OAuth credentials with Composio, see [How to create OAuth2 credentials for Monday](https://composio.dev/auth/monday).
20 -
21 -## How do I configure scopes for Monday.com?
22 -
23 -Monday.com doesn't accept scopes in the auth config the way Google does. Scopes are configured on the OAuth app itself. If you're using the default OAuth app, the required scopes are already configured. If creating your own app, add the scopes you need:
24 -
25 -```bash
26 -me:read
27 -boards:read
28 -boards:write
29 -docs:read
30 -docs:write
31 -workspaces:read
32 -workspaces:write
33 -users:read
34 -users:write
35 -account:read
36 -notifications:write
37 -updates:read
38 -updates:write
39 -assets:read
40 -tags:read
41 -teams:read
42 -teams:write
43 -webhooks:write
44 -webhooks:read
45 -```
46 -
47 ----
23 +If you are using the Composio-managed Monday app, use the default scope setup. If you are creating your own Monday OAuth app, configure the scopes you need in Monday. If you intentionally want to request only a subset of the OAuth app's scopes, configure that subset in the auth config; otherwise, leave the auth config scope field alone.
docs/content/toolkits/faq/notion.md
+4 -2
@@ -22,7 +22,7 @@ It depends on the integration type. OAuth apps (public) let users select which p
22
23 ## How do I set up the Notion webhook ingress endpoint?
24
25 -With Composio-managed Notion credentials, the webhook ingress endpoint is already provisioned — just create the trigger. If you bring your own Notion OAuth app, the verification flow runs in reverse from Slack's: Notion sends a verification token to the ingress endpoint, and you paste that token back into Notion to finalize.
25 +With Composio-managed Notion credentials, the webhook ingress endpoint is already provisioned, so just create the trigger. If you bring your own Notion OAuth app, the verification flow runs in reverse from Slack's: Notion sends a verification token to the ingress endpoint, and you paste that token back into Notion to finalize.
26
27 1. **Create the endpoint.**
28
@@ -48,4 +48,6 @@ With Composio-managed Notion credentials, the webhook ingress endpoint is alread
48
49 4. **Paste the token back into Notion's verify field** to complete setup. Continue with [Creating triggers](https://docs.composio.dev/docs/setting-up-triggers/creating-triggers#create-the-trigger).
50
51 ----
51 +## Notion database trigger fires for new pages, not updates
52 +
53 +In manual testing, the Notion trigger fired when pages were added to the watched database, but not for updates. Test by adding a new page to the target database.
docs/content/toolkits/faq/one_drive.md
-2
@@ -3,5 +3,3 @@
3 Items in "Shared" may be references to files stored in SharePoint, not actual files in the user's OneDrive. These references can't be downloaded via OneDrive endpoints.
4
5 To fix this, open the file's location in OneDrive or SharePoint, choose "Copy to" then "My files" to create a copy in the user's OneDrive, and download the copy. If you need programmatic access to SharePoint files, use the SharePoint APIs instead.
6 -
7 ----
docs/content/toolkits/faq/outlook.md
+15 -2
@@ -12,6 +12,19 @@ Microsoft Graph's send endpoint returns an HTTP 202 with no message details. To
12
13 ## What's the @odata.context / @odata URL?
14
15 -The `@odata.context` URL provides metadata about the response (entity set, service version, and schema info) to help clients interpret the payload structure. It's primarily used for pagination and data parsing — not as a direct URL to the resource itself.
15 +The `@odata.context` URL provides metadata about the response (entity set, service version, and schema info) to help clients interpret the payload structure. It's primarily used for pagination and data parsing, not as a direct URL to the resource itself.
16
17 ----
17 +## Why do Outlook connections show "Needs Admin Approval" or "admin approval required"?
18 +
19 +Microsoft/Outlook admin-consent issues are Microsoft 365 tenant-level approval problems, not something fixed by changing only the Composio connection. Adding delegated permissions to an Azure app registration is not the same as granting tenant admin consent. Once a tenant admin grants consent for the requested permissions, affected users should start a fresh normal Outlook connection flow with their own accounts; the admin does not need to connect every user individually.
20 +
21 +Two concrete ways an admin can approve are:
22 +
23 +1. **App Registration / OAuth app level:** in Microsoft Entra / Azure Portal, go to **App registrations**, open the OAuth app, go to **API permissions**, click **Grant admin consent for [Tenant Name]**, then confirm/save.
24 +2. **Enterprise Applications / org level:** in Microsoft Entra / Azure Portal, go to **Enterprise applications**, find the Composio/Outlook app or the user's own service principal, open **Permissions** / admin-consent controls, then grant admin consent for the organization.
25 +
26 +![Microsoft Entra API permissions page showing the Grant admin consent action](/images/kb/toolkits/outlook/outlook-admin-consent-api-permissions.png)
27 +
28 +Microsoft may also show an in-flow `sign in as an admin` / `Connectez-vous avec ce compte` option on the OAuth screen. Treat that as a secondary path, not the first recommendation. If an admin signs in through the same OAuth attempt, that attempt may connect the admin's mailbox instead of the original user's mailbox. After tenant-wide consent is granted, the original user should start a fresh Outlook connection flow with their own account.
29 +
30 +For custom Microsoft OAuth apps, a verified publisher can improve branding and may reduce consent friction in tenants that allow user consent for verified publishers and the requested delegated permissions. It does not remove the admin-consent requirement in every tenant; each Microsoft 365 tenant's user-consent policy and the exact scopes requested still decide whether admin approval is needed.
docs/content/toolkits/faq/pipedrive.md
+10 -2
@@ -4,6 +4,14 @@ For a step-by-step guide on creating and configuring your own Pipedrive OAuth cr
4
5 ## Why am I seeing "App not found" when connecting Pipedrive?
6
7 -Composio's default Pipedrive OAuth credentials may have expired. Use your own OAuth app credentials until the default is restored.
7 +Pipedrive usually shows "App not found" when the OAuth app used for the connection is not approved or available for that user/workspace.
8
9 ----
9 +If you are using managed Pipedrive OAuth, this means the managed OAuth app is still under Pipedrive review/verification. If you are using your own Pipedrive OAuth app, check the app's approval/verification status in Pipedrive and make sure the user is authorizing the same app configured in the auth config. After the app is approved or corrected, start a fresh connection.
10 +
11 +## How should I connect with my own Pipedrive OAuth app?
12 +
13 +Create the OAuth app in Pipedrive Developer Hub, then use that app's client ID and client secret in a Pipedrive custom OAuth auth config.
14 +
15 +Do not start the user connection by clicking **Install and Test** inside Pipedrive's OAuth app settings. That button starts Pipedrive's own test/install flow, not the Composio connection flow, and can send the user to the callback URL without the Composio auth config context.
16 +
17 +After saving the custom auth config, start the connection from Composio and enter the Pipedrive subdomain when prompted. If Pipedrive shows "App not found", verify that the client ID and secret match the same Pipedrive OAuth app, that the app is approved/available for the user, and that the redirect URI matches the Pipedrive auth setup guide.
docs/content/toolkits/faq/posthog.md
+8
@@ -1,3 +1,11 @@
1 ## How do I set up custom OAuth credentials for PostHog?
2
3 For a step-by-step guide on creating and configuring your own PostHog OAuth credentials with Composio, see [How to create OAuth credentials for PostHog](https://composio.dev/auth/posthog).
4 +
5 +## How do I configure the PostHog region for US or EU Cloud?
6 +
7 +Set the PostHog region on the connection. Use `us` for US Cloud or `eu` for EU Cloud. Do not pass a full URL such as `https://eu.posthog.com`; the toolkit builds the host as `<region>.posthog.com` from the region value.
8 +
9 +This matters because the PostHog API host is different for US and EU Cloud, and region is connection-specific rather than one fixed auth-config value for every connected account. A connection that should call `eu.posthog.com` but is left on the default `us` region can fail or return data from the wrong PostHog environment.
10 +
11 +In the Link flow, the user sees a prefilled Region field while connecting and can choose the correct region. In the Initiate flow, set the region during connected-account creation. Existing connections were migrated to keep their current region, so they do not need to reconnect only because of this field change.
docs/content/toolkits/faq/quickbooks.md
+11 -3
@@ -1,5 +1,13 @@
1 -## Why am I seeing a DNS error while connecting my QuickBooks account?
1 +## Why can QuickBooks OAuth show Cloudflare Error 1016 (Origin DNS error)?
2
3 -This usually happens when the `com.intuit.quickbooks.payment` scope is included in your auth config but the QuickBooks account hasn't enabled the Payments module. Either remove that scope from your auth config and reconnect, or enable the Payments module in QuickBooks first.
3 +If this appears while connecting QuickBooks and the auth config includes the `com.intuit.quickbooks.payment` scope, check whether the QuickBooks Payments module is enabled for the selected QuickBooks company.
4
5 ----
5 +That scope requires payment-module access in QuickBooks. If you do not need payment tools, remove `com.intuit.quickbooks.payment` from the auth config and reconnect. If you do need payment tools, enable QuickBooks Payments for that company/account, then start a fresh connection.
6 +
7 +## Why can Claude block QuickBooks in consumer MCP sessions?
8 +
9 +This behavior is intentional on Claude's side. QuickBooks has tools that can process payments, so Claude can classify it under Payment Processing and block execution in consumer MCP sessions. Use Claude Code or Claude Cowork with Composio through the CLI/developer path where the agent can still access QuickBooks through Composio.
10 +
11 +## When should I use the sandbox QuickBooks API base URL for sandbox connections?
12 +
13 +For QuickBooks sandbox accounts, pass `https://sandbox-quickbooks.api.intuit.com` as the URL/base URL when initiating the connection. Production connections should use the production Intuit API base URL.
docs/content/toolkits/faq/salesforce.md
+19 -3
@@ -2,9 +2,23 @@
2
3 For a step-by-step guide on creating and configuring your own Salesforce OAuth credentials with Composio, see [How to create OAuth credentials for Salesforce](https://composio.dev/auth/salesforce).
4
5 -## Why can't I find items I created in Salesforce?
5 +## `URL_NOT_RESET` usually means Salesforce subdomain was not configured and defaulted to `login`
6
7 -Created records may not appear in a given Salesforce view. Use search to confirm they exist.
7 +`URL_NOT_RESET` can happen when the Salesforce org requires a specific My Domain value but the connection is using the generic `login` default or an incomplete subdomain. The default `login` value is fine for most Salesforce flows, but for org-specific failures recheck the Salesforce domain/subdomain values on the connection, pass the correct My Domain subdomain, and retry on the latest toolkit version if the issue was seen on an older pinned version.
8 +
9 +## Why do I see `OAUTH_APPROVAL_ERROR_GENERIC` or `app must be installed into org` in Salesforce OAuth?
10 +
11 +These errors usually mean Salesforce is blocking OAuth because the connected app has not been installed or approved for the org. The user may see `OAUTH_APPROVAL_ERROR_GENERIC`, or the callback URL may include `error=invalid_client&error_description=app+must+be+installed+into+org`.
12 +
13 +Ask a Salesforce org admin to approve or install the connected app. In Salesforce Setup, search for **External Client App Settings** or **OAuth Connected App Usage**, find the app, and use the install/approval action shown by Salesforce. After the admin approves the app, the user should retry the OAuth connection.
14 +
15 +![Salesforce OAuth approval error showing OAUTH_APPROVAL_ERROR_GENERIC and app must be installed into org.](/images/kb/toolkits/salesforce/salesforce-oauth-approval-error.png)
16 +
17 +![Salesforce Setup search showing External Client App Settings for connected app approval.](/images/kb/toolkits/salesforce/salesforce-external-client-app-settings.png)
18 +
19 +## Salesforce allows only five active refresh tokens per user per app
20 +
21 +Salesforce allows only five active refresh tokens per user per connected app. When the same Salesforce user connects a sixth time, Salesforce can revoke the oldest refresh token, which makes older Composio connected accounts fail with token errors. Also check whether the user changed their password, revoked the app, changed connected app refresh-token policy away from `valid until revoked`, or has org-level session policies that invalidate tokens.
22
23 ## How do I query relationships like Pricebooks and Opportunities?
24
@@ -24,4 +38,6 @@ You need your subdomain (e.g., `your-company.my`) and instance endpoint `/servic
38
39 Deprecated tools continue to work until removed. Check tool descriptions for "DEPRECATED:" markers.
40
27 ----
41 +## Why can't I find items I created in Salesforce?
42 +
43 +Created records may not appear in a given Salesforce view. Use search to confirm they exist.
docs/content/toolkits/faq/share_point.md new
+5
@@ -0,0 +1,5 @@
1 +## Why does my SharePoint `/teams/...` site resolve as `/sites/...`?
2 +
3 +If a user's SharePoint site URL is under `/teams/<site>` instead of `/sites/<site>`, do not tell them to pass only `<site>` in the SharePoint Subsite field. A bare subsite value is interpreted as `/sites/<site>` by the toolkit.
4 +
5 +Re-initiate or reconnect the SharePoint account and set SharePoint Subsite to the full server-relative path, for example `/teams/<site>`. For per-call overrides, pass `site_name: "/teams/<site>"`.
docs/content/toolkits/faq/shopify.md
+3 -1
@@ -6,4 +6,6 @@ For a step-by-step guide on creating and configuring your own Shopify OAuth cred
6
7 The default Shopify OAuth app may be under review or expired. Use your own OAuth app or API authentication method until the default is restored.
8
9 ----
9 +## Shopify order update 403s can be caused by missing `read_all_orders` scope
10 +
11 +Check the scopes on the Shopify connection. If order reads or updates require access beyond the default order scope set, reconnect with the needed order scopes such as `read_all_orders` before retrying.
docs/content/toolkits/faq/slack.md
+12 -6
@@ -18,10 +18,6 @@ When a member of a Slack workspace tries to install a non-Marketplace app.
18
19 `Settings → Apps & Workflows → App Management Settings`
20
21 -## Do I have to be a Workspace Owner to install the app?
22 -
23 -In some cases — yes. For example, when installing non-Marketplace apps, you'll need to be an owner to install directly and complete the connection. As a member, you'd need to either request approval, or ask the owner to disable **Require approved apps**.
24 -
21 ## Why am I being asked to submit a request during auth?
22
23 Because **Require approved apps** is enabled in the workspace's **App Management Settings**. Slack is asking for admin/owner approval before completing the install.
@@ -31,7 +27,7 @@ Because **Require approved apps** is enabled in the workspace's **App Management
27 Two ways:
28
29 - Disable both **Require apps from Slack Marketplace** and **Require approved apps** in the workspace's app management settings.
34 -- Use the workspace's own OAuth app — recommended and safest. See [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
30 +- Use the workspace's own OAuth app, which is recommended and safest. See [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
31
32 ## What is the difference between Slack and Slackbot toolkits?
33
@@ -61,4 +57,14 @@ For the Slack toolkit, set `as_user=True` to post as the authenticated user. For
57
58 See [Triggers](/docs/triggers).
59
64 ----
60 +## Slack Marketplace warnings during OAuth
61 +
62 +Slack may show a Marketplace warning when the OAuth app is not listed or approved in Slack Marketplace. The OAuth flow can still work if the workspace allows non-Marketplace apps, but workspaces with stricter app policies may require admin approval before the connection can complete.
63 +
64 +Composio is working on Marketplace review for the managed Slack app. Until that review is complete, use the workspace's own Slack OAuth app or ask a workspace admin to approve the app if the warning blocks users.
65 +
66 +![Slack OAuth consent warning stating that the app is not approved by Slack.](/images/kb/toolkits/slack/slack-marketplace-warning.png)
67 +
68 +## Do I have to be a Workspace Owner to install the app?
69 +
70 +In some cases — yes. For example, when installing non-Marketplace apps, you'll need to be an owner to install directly and complete the connection. As a member, you'd need to either request approval, or ask the owner to disable **Require approved apps**.
docs/content/toolkits/faq/slackbot.md new
+9
@@ -0,0 +1,9 @@
1 +## Slackbot triggers require a verification token or subscription ID in custom auth
2 +
3 +For Slackbot triggers with custom auth, put the Slack app verification token in the Slackbot auth config, then create a fresh connection.
4 +
5 +## Why can repeated Slackbot connections make older connections expire?
6 +
7 +If Slack token rotation is enabled on the Slack app, repeated connections for the same user/app can invalidate older tokens. Slack documents a two-active-token limit for token rotation: when more than two active tokens exist after a refresh, Slack revokes the oldest extra token.
8 +
9 +This can look like older Slackbot connections expiring after a third connection or after another connection refreshes. Avoid creating multiple active Slackbot connections for the same Slack user and OAuth app unless the product is designed to handle older connections expiring. See Slack's [token rotation documentation](https://docs.slack.dev/authentication/using-token-rotation/).
docs/content/toolkits/faq/snowflake.md
+3 -3
@@ -19,8 +19,8 @@ CREATE SECURITY INTEGRATION oauth_custom_all_roles
19
20 Ensure the OAuth app and Snowflake roles, databases, and schemas are configured correctly for the integration.
21
22 -## Does Snowflake require per-customer OAuth credentials?
22 +## Does Snowflake require per-user OAuth credentials?
23
24 -Yes. Snowflake typically requires per-customer OAuth credentials. Customers often supply their own credentials when integrating with Composio.
24 +Yes. Snowflake OAuth is tied to the user's Snowflake account and security integration. There is not a single generic Snowflake OAuth app that can safely cover every account, role setup, redirect URI, and security policy.
25
26 ----
26 +For a production integration, each Snowflake user should bring the OAuth client credentials from the security integration configured in their own Snowflake account. Create a Composio auth config with those credentials, then let the user connect with the account identifier and permissions for that Snowflake account. This keeps the connection aligned with the user's Snowflake roles, databases, schemas, and refresh-token policy.
docs/content/toolkits/faq/spotify.md
-2
@@ -1,5 +1,3 @@
1 ## Why is there no default OAuth app for Spotify?
2
3 Composio does not provide a default OAuth app for Spotify. Create your own OAuth app in the [Spotify Developer Dashboard](https://developer.spotify.com/dashboard) to use the Spotify toolkit.
4 -
5 ----
docs/content/toolkits/faq/strava.md
+16
@@ -1,3 +1,19 @@
1 ## How do I set up custom OAuth credentials for Strava?
2
3 For a step-by-step guide on creating and configuring your own Strava OAuth credentials with Composio, see [How to create OAuth credentials for Strava](https://composio.dev/auth/strava).
4 +
5 +## Why can Strava OAuth fail with "Athlete limit exceeded" or `Application.Status.Inactive`?
6 +
7 +Strava can reject authorization or tool execution when the Strava OAuth app behind the connection has not been fully approved/activated by Strava or has hit its athlete limit.
8 +
9 +If you are using managed Strava OAuth, you may see either "Athlete limit exceeded" during authorization or a 403 response from Strava with `Application.Status.Inactive` during tool execution.
10 +
11 +We are working with Strava on approval and capacity for the managed Strava app. Since this depends on Strava's approval process, we do not have a concrete date to share yet.
12 +
13 +For production use or dedicated capacity, use your own Strava OAuth app with a custom auth config, then reconnect users through that config.
14 +
15 +## Why are private Strava activities missing?
16 +
17 +The managed Strava OAuth scope set currently includes `read`, `activity:read`, and `profile:read_all`.
18 +
19 +`activity:read` can read activities visible to the authenticated athlete based on Strava visibility rules, but private activities require `activity:read_all`. If private activities are missing, use your own Strava OAuth app with `activity:read_all` configured, then reconnect the account so the new scope is granted.
docs/content/toolkits/faq/stripe.md
+6
@@ -1,3 +1,9 @@
1 ## How do I set up custom OAuth credentials for Stripe?
2
3 For a step-by-step guide on creating and configuring your own Stripe OAuth credentials with Composio, see [How to create OAuth credentials for Stripe](https://composio.dev/auth/stripe).
4 +
5 +## Why is my Stripe trigger enabled but not receiving events?
6 +
7 +One possible cause is that the Stripe webhook destination was deleted in Stripe while the trigger still appears enabled. In that state, the trigger can look active, but Stripe has no active destination to send matching events to.
8 +
9 +Check the Stripe Dashboard for the webhook destination associated with the trigger. If it is missing or disabled, recreate the trigger so the Stripe webhook destination is created again, then verify new Stripe events are delivered.
docs/content/toolkits/faq/supabase.md new
+3
@@ -0,0 +1,3 @@
1 +## Limit Supabase scopes in the user's OAuth app, not through Composio's default app
2 +
3 +For Supabase permission scoping, configure the desired permissions in the user's own OAuth app and create the Composio auth config with that app. The default Composio OAuth app may be configured with broader permissions.
docs/content/toolkits/faq/twitter.md
+7 -1
@@ -19,4 +19,10 @@ Twitter enforces plan-based access tiers. Check your project's product and plan
19
20 Your developer account or project may not have the required access level for the endpoint. Check your enrollment and access tier in the Twitter Developer Portal.
21
22 ----
22 +## What length limits apply to Twitter/X posts?
23 +
24 +Twitter/X enforces strict post length limits. For normal posts, keep the content under 280 characters and follow X's official character-counting behavior, since URLs, Unicode, and special characters may be counted by provider-specific rules.
25 +
26 +## `client-not-enrolled` and `App not linked to project` usually point to Twitter developer app/project setup issues
27 +
28 +These errors usually mean the Twitter/X developer app is not correctly connected to a Twitter developer project, or the OAuth app configuration is stale after X's API model changes. Verify the app is linked to a project, configured according to the Twitter setup guide, and aligned with the current X API requirements. If the connected account is already `EXPIRED`, recreate the connection after fixing the app configuration.
docs/content/toolkits/faq/whatsapp.md
+14 -2
@@ -2,8 +2,20 @@
2
3 WhatsApp has a 24-hour customer service window. Recipients only receive messages within 24 hours of their last message to you. To message outside this window, use a template message.
4
5 +## Can I use a personal WhatsApp account with the WhatsApp toolkit?
6 +
7 +No. The WhatsApp toolkit is for WhatsApp Business API flows, so the connected account needs to be backed by a WhatsApp Business Account (WABA). Personal WhatsApp accounts are not supported for these API flows.
8 +
9 +If you need to send or receive WhatsApp messages through the toolkit, set up or connect the relevant WABA-backed business account in Meta first.
10 +
11 +## What is a WABA ID?
12 +
13 +The WABA ID, or WhatsApp Business Account ID, is required because the WhatsApp Business API needs it to identify the business account. Users can find it in Meta Developers under the app's WhatsApp API Setup section, or fetch it programmatically by calling `GET /me/businesses` and then `GET /{business_id}/owned_whatsapp_business_accounts` with an access token.
14 +
15 +## WhatsApp template messages require an existing template before sending
16 +
17 +Sending a WhatsApp template message requires a template to already exist in WhatsApp/Meta. The send-template tool sends an existing template by name/language and parameters; it does not remove the need to create and approve the template first.
18 +
19 ## Why is my WhatsApp connection failing with "Missing required fields"?
20
21 Ensure all required fields are provided when initiating the connection. See the [WhatsApp authentication details](https://docs.composio.dev/toolkits/whatsapp#authentication-details).
8 -
9 ----
docs/content/toolkits/faq/youtube.md
+2 -2
@@ -4,6 +4,6 @@ For a step-by-step guide on creating and configuring your own Google OAuth crede
4
5 ## Why am I getting quota errors on YouTube?
6
7 -The default OAuth app is shared and has strict quota limits. For production, create your own OAuth app to get a dedicated quota.
7 +YouTube enforces strict API quotas. If you use the managed/default OAuth app, that quota can be shared across users, so production workloads can hit provider quota limits faster than expected.
8
9 ----
9 +For production, create your own Google Cloud OAuth app and use those credentials in the YouTube auth config. That gives your project its own YouTube API quota and lets you control scopes, branding, and quota increase requests in Google Cloud.
docs/content/toolkits/faq/zoho_mail.md new
+3
@@ -0,0 +1,3 @@
1 +## What should I pass for the correct Zoho region when connecting Zoho Mail?
2 +
3 +For Zoho Mail connection issues, verify the region passed during connection initiation. Zoho accounts can be region-specific, so an EU or other regional account may fail if the default/wrong region is used. Retry the connection with the correct Zoho region.
docs/public/images/kb/toolkits/googleads/google-ads-developer-token-auth-config.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/googleads/google-ads-developer-token-auth-config.png differ
docs/public/images/kb/toolkits/monday/monday-app-not-installed.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/monday/monday-app-not-installed.png differ
docs/public/images/kb/toolkits/outlook/outlook-admin-consent-api-permissions.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/outlook/outlook-admin-consent-api-permissions.png differ
docs/public/images/kb/toolkits/salesforce/salesforce-external-client-app-settings.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/salesforce/salesforce-external-client-app-settings.png differ
docs/public/images/kb/toolkits/salesforce/salesforce-oauth-approval-error.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/salesforce/salesforce-oauth-approval-error.png differ
docs/public/images/kb/toolkits/slack/slack-marketplace-warning.png
Binary files /dev/null and b/docs/public/images/kb/toolkits/slack/slack-marketplace-warning.png differ