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: rewrite toolkit FAQ headings as questions and clean up answers
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 17, 2026 at 15:37 UTC
2a7e80e05a60397ebe79a7ac396253b4ed117100
13 files changed
+222
-183
docs/content/docs/common-faq.mdx
+7
-9
@@ -142,18 +142,12 @@ Composio does not have fixed IP ranges. Traffic is routed through Cloudflare and
142
<Accordion title="How do I increase my quota?">
143
Upgrade your plan. See [pricing](https://composio.dev/pricing) for available plans and limits.
144
</Accordion>
145
-
146
-<Accordion title="Can Composio be self-hosted?">
147
-Yes, Composio supports self-hosting on the Enterprise plan. See [pricing](https://composio.dev/pricing) for details or [talk to us](https://calendly.com/composiohq/enterprise).
148
-</Accordion>
149
-
145
<Accordion title="How do I configure sessions with custom auth configs?">
151
-Some toolkits require your own OAuth credentials or API keys. Create an auth config in the dashboard by selecting the toolkit, choosing the auth scheme, and entering your credentials. Then pass the auth config ID when creating a session using the `auth_configs` (or `auth_config_id`) parameter so the session uses your developer credentials instead of Composio‑managed auth.
152
-See: https://docs.composio.dev/docs/using-custom-auth-configuration
146
+Some toolkits require your own OAuth credentials or API keys. Create an auth config in the dashboard by selecting the toolkit, choosing the auth scheme, and entering your credentials. Then pass the auth config ID when creating a session using the `auth_configs` (or `auth_config_id`) parameter so the session uses your developer credentials instead of Composio-managed auth. See [Using custom auth configuration](/docs/using-custom-auth-configuration).
147
</Accordion>
148
149
<Accordion title="How do I check complete logs / API calls from the SDK?">
156
-Enable debug logging to view all API calls and network requests made by the SDK — this helps troubleshoot issues and provides request IDs for support.
150
+Enable debug logging to view all API calls and network requests made by the SDK.
151
152
Python:
153
```bash
@@ -165,7 +159,11 @@ TypeScript:
159
COMPOSIO_LOG_LEVEL=debug
160
```
161
168
-See: https://docs.composio.dev/docs/troubleshooting/sdks
162
+See [Troubleshooting SDKs](/docs/troubleshooting/sdks).
163
+</Accordion>
164
+
165
+<Accordion title="Can Composio be self-hosted?">
166
+Yes, Composio supports self-hosting on the Enterprise plan. See [pricing](https://composio.dev/pricing) for details or [talk to us](https://calendly.com/composiohq/enterprise).
167
</Accordion>
168
169
</Accordions>
docs/content/toolkit-faq/calendly.md
+1
-3
@@ -1,5 +1,3 @@
1
-## Calendly Toolkit — FAQ
2
-
3
-## Calendly has no scopes
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.
3
docs/content/toolkit-faq/gmail.md
+23
-18
@@ -2,29 +2,34 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client is requesting scopes Google hasn't verified for that client (often when extra granular scopes are added).
7
-Fix: remove the extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Gmail?
6
9
-## "Gmail API has not been used in project <ID> before or it is disabled"
10
-Why it happens: when using custom OAuth credentials the Gmail API must be enabled in the Cloud project that owns those credentials.
11
-Fix: enable the Gmail API in Google Cloud Console → APIs & Services, wait a few minutes for propagation, then retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid, unsupported, or misformatted in the auth URL.
15
-Fix: verify scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Gmail API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token limits (~50 tokens). Reauthorization typically resolves 401s.
13
+When using custom OAuth credentials, the Gmail API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
-## Gmail trigger is slow
24
-Gmail triggers poll every ~1 minute by default (configurable); expect up to ~1 minute delay. If you need lower latency consider webhooks or Google pub/sub integrations.
15
+## Why am I getting "Error 400: invalid_scope"?
16
26
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
27
-Google enforces request quotas (per‑minute and daily) to protect its APIs. If many clients share the same OAuth app, the shared quota can be exhausted and you may see quota errors.
28
-Fixes: implement exponential backoff and retries, batch/cache requests to reduce rate, or use your own OAuth app credentials to avoid shared limits.
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
26
+
27
+## Why is my Gmail trigger slow?
28
+
29
+Gmail triggers poll roughly every minute by default. If you need lower latency, consider using webhooks or Google Pub/Sub integrations.
30
+
31
+## Why am I getting "Quota Exhausted" or "rate limit exhausted"?
32
+
33
+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.
34
35
---
docs/content/toolkit-faq/google_classroom.md
+20
-14
@@ -1,21 +1,27 @@
1
-# Google Toolkits — FAQ
1
+## How do I set up custom Google OAuth credentials for Google Classroom?
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client is requesting scopes Google hasn't verified for that client (often when extra granular scopes are added).
7
-Fix: remove the extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Classroom?
6
9
-## "Gmail API has not been used in project <ID> before or it is disabled"
10
-Why it happens: when using custom OAuth credentials the Gmail API must be enabled in the Cloud project that owns those credentials.
11
-Fix: enable the Gmail API in Google Cloud Console → APIs & Services, wait a few minutes for propagation, then retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid, unsupported, or misformatted in the auth URL.
15
-Fix: verify scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Classroom API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token limits (~50 tokens). Reauthorization typically resolves 401s.
13
+When using custom OAuth credentials, the Google Classroom API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
+
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
26
+
27
+---
docs/content/toolkit-faq/google_maps.md
+20
-14
@@ -1,21 +1,27 @@
1
-## Google Toolkits — FAQ
1
+## How do I set up custom Google OAuth credentials for Google Maps?
2
3
-## "App is blocked" warning while connecting to Google apps
4
-Why it happens: the OAuth client requests scopes Google hasn't verified for that client (often because extra granular scopes were added).
5
-Fix: remove the extra scopes or create and use your own OAuth app and submit scopes for verification — see the [Create OAuth app guide](https://composio.dev/auth/googleapps).
3
+For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
7
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
8
-Why it happens: the specific Google API (Sheets, Drive, Gmail, Slides, etc.) is not enabled for the Cloud project tied to your OAuth credentials.
9
-Fix: open Google Cloud Console → APIs & Services → enable the required API, then wait a few minutes and retry.
5
+## Why am I seeing "App is blocked" when connecting Google Maps?
6
11
-## Access blocked: Authorization Error (Error 400: invalid_scope)
12
-Why it happens: requested scopes are invalid, unsupported, or misformatted in the authorization URL.
13
-Fix: verify scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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.
8
15
-## Composio name shown on the OAuth consent screen
16
-To white‑label the consent screen, create and use your own OAuth app and configure a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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).
10
18
-## 401 errors for tool calls
19
-Common causes: user revoked access, password/2FA change, Workspace admin policy changes, or refresh‑token limits (~50 tokens). Reauthorization generally resolves 401s.
11
+## Why am I getting "Google Maps API has not been used in project" error?
12
+
13
+When using custom OAuth credentials, the Google Maps API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
+
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
26
27
---
docs/content/toolkit-faq/googlecalendar.md
+17
-14
@@ -2,23 +2,26 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client requests scopes that aren't verified for that client (common when adding extra scopes).
7
-Fix: remove extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Calendar?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Calendar API is not enabled for the Cloud project tied to your OAuth credentials.
11
-Fix: enable the Calendar API in Google Cloud Console → APIs & Services, then wait a few minutes and retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid or misformatted.
15
-Fix: verify scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Calendar API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, admin policy, or refresh‑token limits (~50). Reauthorization typically resolves 401s.
13
+When using custom OAuth credentials, the Google Calendar API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
+
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
26
27
---
24
----
\ No newline at end of file
docs/content/toolkit-faq/googledocs.md
+20
-17
@@ -2,27 +2,30 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client is requesting scopes Google hasn't verified for that client (often due to extra granular scopes).
7
-Fix: remove the extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Docs?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Docs API isn't enabled for the Cloud project tied to your OAuth credentials.
11
-Fix: enable the Docs API in Google Cloud Console → APIs & Services, then wait a few minutes and retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid, unsupported, or misformatted.
15
-Fix: validate scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Docs API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token limits (~50). Reauthorization usually resolves 401s.
13
+When using custom OAuth credentials, the Google Docs API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
----
24
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
25
-Google enforces request quotas (per‑minute and daily) to protect its APIs. Shared/default OAuth apps can hit these quotas under load, causing quota errors.
26
-Fixes: use exponential backoff with retries, batch or cache requests to reduce the call rate, or use your own OAuth app credentials to avoid shared limits.
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
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/toolkit-faq/googledrive.md
+17
-14
@@ -2,23 +2,26 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client is requesting scopes Google hasn't verified (often after adding extra scopes).
7
-Fix: remove the additional scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Drive?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Drive API is not enabled for the Cloud project tied to your OAuth credentials.
11
-Fix: enable the Drive API in Google Cloud Console → APIs & Services; wait a few minutes and retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: scopes are invalid, unsupported, or misformatted in the auth URL.
15
-Fix: validate scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Drive API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, admin policy, or refresh‑token limits (~50). Reauthorization typically resolves the issue.
13
+When using custom OAuth credentials, the Google Drive API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
+
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
26
23
----
27
---
docs/content/toolkit-faq/googlemeet.md
+20
-17
@@ -2,27 +2,30 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client requests scopes that aren't verified for that app (often due to added granular scopes).
7
-Fix: remove the extra scopes or use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Meet?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Meet API is not enabled for the Cloud project tied to your OAuth credentials.
11
-Fix: enable the Meet API in Google Cloud Console → APIs & Services, then wait a few minutes and retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid or misformatted in the auth URL.
15
-Fix: verify scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Meet API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token limits (~50). Reauthorize when needed.
13
+When using custom OAuth credentials, the Google Meet API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
----
24
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
25
-Google enforces request quotas (per‑minute and daily) to protect its APIs. When many clients use the same OAuth app, shared quotas can be exhausted and cause these errors.
26
-Fixes: implement exponential backoff and retries, batch/cache requests to reduce the rate, or use your own OAuth app credentials to avoid shared limits.
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
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/toolkit-faq/googlesheets.md
+20
-17
@@ -2,27 +2,30 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client requests scopes Google hasn't verified for that client (often due to added granular scopes).
7
-Fix: remove the extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Sheets?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Google Sheets API isn't enabled for the Cloud project tied to your OAuth credentials.
11
-Fix: enable the Sheets API in Google Cloud Console → APIs & Services, then wait a few minutes and retry.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid or misformatted in the auth URL.
15
-Fix: verify scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Sheets API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy changes, or refresh‑token limits (~50 tokens). Reauthorization typically resolves 401s.
13
+When using custom OAuth credentials, the Google Sheets API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
----
24
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
25
-Google enforces request quotas (per‑minute and daily) to protect its APIs. Shared default OAuth apps can reach those limits under high traffic, causing quota errors.
26
-Fixes: add exponential backoff and retries, batch or cache requests to lower the rate, or use your own OAuth app credentials to avoid shared quotas.
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
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/toolkit-faq/googleslides.md
+20
-17
@@ -2,27 +2,30 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client requests scopes Google hasn't verified for that client (common when extra granular scopes are added).
7
-Fix: remove extra scopes or create/use your own OAuth app and submit scopes for verification (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)).
5
+## Why am I seeing "App is blocked" when connecting Google Slides?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: the Cloud project that owns your OAuth credentials doesn't have the required API enabled.
11
-Fix: enable the API (Google Cloud Console → APIs & Services) and wait a few minutes for propagation.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: requested scopes are invalid or misformatted in the auth URL.
15
-Fix: validate scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label, create and use your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Slides API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token limits (~50). Reauthorize when needed.
13
+When using custom OAuth credentials, the Google Slides API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
----
24
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
25
-Google enforces quotas to limit request rates (per‑minute and daily). Shared default OAuth apps can hit these quotas under heavy use, causing "Quota Exhausted" errors.
26
-Fixes: add exponential backoff/retries, reduce request frequency (batch/cache), or use your own OAuth app credentials to avoid shared limits.
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
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/toolkit-faq/googlesuper.md
+17
-12
@@ -1,18 +1,23 @@
1
-## Google Toolkits — FAQ
1
+## How do I set up custom Google OAuth credentials for Google Super?
2
3
-## "App is blocked" warning while connecting to Google apps
4
-Why it happens: the OAuth client requests scopes Google hasn't verified for that client (often because extra granular scopes were added).
5
-Fix: remove the extra scopes or create and use your own OAuth app and submit scopes for verification — see the [Create OAuth app guide](https://composio.dev/auth/googleapps).
3
+For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
7
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
8
-Why it happens: the specific Google API (Sheets, Drive, Gmail, Slides, etc.) is not enabled for the Cloud project tied to your OAuth credentials.
9
-Fix: open Google Cloud Console → APIs & Services → enable the required API, then wait a few minutes and retry.
5
+## Why am I seeing "App is blocked" when connecting Google Super?
6
11
-## Access blocked: Authorization Error (Error 400: invalid_scope)
12
-Why it happens: requested scopes are invalid, unsupported, or misformatted in the authorization URL.
13
-Fix: verify scopes against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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.
8
15
-## Composio name shown on the OAuth consent screen
16
-To white‑label the consent screen, create and use your own OAuth app and configure a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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).
10
+
11
+## Why am I getting the "API has not been used in project" error?
12
+
13
+When using custom OAuth credentials, the required Google API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
+
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
22
23
---
docs/content/toolkit-faq/googletasks.md
+20
-17
@@ -2,27 +2,30 @@
2
3
For a step-by-step guide on creating and configuring your own Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
4
5
-## "App is blocked" warning while connecting to Google apps
6
-Why it happens: the OAuth client is requesting scopes Google hasn't verified for that app. If you're using Composio's default OAuth client this usually means you added extra scopes beyond the defaults.
7
-Fix: either remove the extra scope(s) or create and use your own OAuth app (see the [Create OAuth app guide](https://composio.dev/auth/googleapps)) and submit scopes for verification.
5
+## Why am I seeing "App is blocked" when connecting Google Tasks?
6
9
-## "<Google App Name> API has not been used in project <ID> before or it is disabled"
10
-Why it happens: when using your own OAuth credentials the corresponding Google API (Sheets, Drive, Gmail, etc.) must be enabled in the Cloud project.
11
-Fix: open Google Cloud Console → APIs & Services → Enable the required API, then wait a few minutes for propagation.
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.
8
13
-## Access blocked: Authorization Error (Error 400: invalid_scope)
14
-Why it happens: scopes are invalid, unsupported, or misformatted in the auth URL.
15
-Fix: verify scopes against Google's docs (see the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2)) and follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
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).
10
17
-## Composio name shown on the OAuth consent screen
18
-To white‑label the consent screen, create your own OAuth app and set a custom redirect URL. See the [white‑label OAuth guide](https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
11
+## Why am I getting "Google Tasks API has not been used in project" error?
12
20
-## 401 errors for tool calls
21
-Common causes: user revoked access, password/2FA change, Workspace admin policy, or refresh‑token rotation/limits (~50 tokens). If a connection fails, ask the user to reauthorize.
13
+When using custom OAuth credentials, the Google Tasks API must be enabled in the Google Cloud project that owns those credentials. Enable it in Google Cloud Console under APIs & Services, wait a few minutes, and retry.
14
23
----
24
-## Why am I getting "Quota Exhausted" or "rate limit exhausted" on the service <SERVICE>.googleapis.com?
25
-Google enforces request quotas to protect its services (per‑minute and daily limits). If many users share the default OAuth client, you may hit a shared quota and see "Quota Exhausted" errors.
26
-Fixes: implement exponential backoff and retries, reduce request rates (batch/cache), or use your own OAuth app credentials to avoid shared quotas.
15
+## Why am I getting "Error 400: invalid_scope"?
16
+
17
+The requested scopes are invalid or incorrectly formatted in the authorization URL. Verify your scope values against the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2). If you're creating auth configs programmatically, see the [programmatic auth config guide](/docs/programmatic-auth-configs).
18
+
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 the OAuth consent screen](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
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.
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
---