Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 09:30 UTC
update: common-faqs
Uday-sidagana committed
Feb 13, 2026 at 20:15 UTC
a012cf8f6ea64443e149d47abec252d7e7efa31b
2 files changed
+61
docs/content/docs/common-faq.mdx
+61
@@ -147,4 +147,65 @@ Upgrade your plan. See [pricing](https://composio.dev/pricing) for available pla
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
150
+<Accordion title=""App is blocked" warning while connecting to Google apps">
151
+When connecting Google apps (Gmail, Sheets, Slides, Docs, Drive, etc.) you may see a "This app is blocked" OAuth error. It means the scopes you're requesting aren't verified for the OAuth client being used. Two common fixes:
152
+
153
+### Using the default OAuth app
154
+- Cause: you added extra scopes beyond the default Composio-managed scopes.
155
+- Fix: remove the additional scopes from your authConfig and retry, or create your own OAuth app and use its credentials (see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps)).
156
+
157
+<Figure src="/images/troubleshooting/troubleshooting-auth-app-blocked.png" alt="App blocked screenshot" size="md" />
158
+
159
+### Using your own OAuth app
160
+- Cause: you're requesting scopes not yet verified for your OAuth app. Google requires verification for some sensitive scopes.
161
+- Fix: submit the scopes for verification in Google Cloud Console; to change the domain shown on the consent screen, configure a custom redirect URL. See Google verification docs: https://support.google.com/cloud/answer/13463073 and our guide: https://docs.composio.dev/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen
162
+</Accordion>
163
+
164
+<Accordion title=""<Google App Name> API has not been used in project <ID> before or it is disabled">
165
+This error occurs when the Google API for the toolkit (Sheets, Drive, Gmail, Slides, etc.) is not enabled for the Cloud project that owns your OAuth credentials. Example error:
166
+
167
+```bash
168
+<Google App Name> API has not been used in project <ID> before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/... then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry
169
+```
170
+
171
+How to resolve:
172
+- If using your own OAuth app, enable the required API in Google Cloud Console → APIs & Services, then wait a few minutes and retry.
173
+- See step 2.1 in our guide: https://composio.dev/auth/googleapps
174
+</Accordion>
175
+
176
+<Accordion title="Access blocked: Authorization Error (Error 400: invalid_scope)">
177
+This error means the requested scopes are invalid or formatted incorrectly in the authorization URL.
178
+
179
+How to resolve:
180
+- Verify scope formatting and validity (see the [Google OAuth scopes docs](https://developers.google.com/identity/protocols/oauth2)).
181
+- If creating authConfigs programmatically, follow the [programmatic authConfig guide](https://docs.composio.dev/docs/programmatic-auth-configs).
182
+
183
+<Figure src="/images/invalid_scope-error.png" alt="Invalid scope screenshot" size="md" />
184
+
185
+</Accordion>
186
+
187
+</Accordions>
188
+
189
+<Accordions>
190
+<Accordion title="How do I configure sessions with custom auth configs?">
191
+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.
192
+See: https://docs.composio.dev/docs/using-custom-auth-configuration
193
+</Accordion>
194
+
195
+<Accordion title="How do I check complete logs / API calls from the SDK?">
196
+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.
197
+
198
+Python:
199
+```bash
200
+COMPOSIO_LOGGING_LEVEL=debug
201
+```
202
+
203
+TypeScript:
204
+```bash
205
+COMPOSIO_LOG_LEVEL=debug
206
+```
207
+
208
+See: https://docs.composio.dev/docs/troubleshooting/sdks
209
+</Accordion>
210
+
211
</Accordions>
docs/public/images/invalid_scope-error.png
Binary files /dev/null and b/docs/public/images/invalid_scope-error.png differ