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
toolkit-faqs
Uday-sidagana committed
Feb 13, 2026 at 17:40 UTC
0ff328d3875d90bb1d1981140de80b78dde6d290
29 files changed
+472
docs/content/toolkit-faq/calendly.md
new
+5
@@ -0,0 +1,5 @@
1
+## Calendly Toolkit — FAQ
2
+
3
+## Calendly has no scopes
4
+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.
5
+
docs/content/toolkit-faq/gmail.md
+27
@@ -1,3 +1,30 @@
1
## How do I set up custom Google OAuth credentials for Gmail?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
25
+
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.
29
+
30
+---
docs/content/toolkit-faq/google_classroom.md
new
+21
@@ -0,0 +1,21 @@
1
+# Google Toolkits — FAQ
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
docs/content/toolkit-faq/google_maps.md
new
+21
@@ -0,0 +1,21 @@
1
+## Google Toolkits — FAQ
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).
6
+
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.
10
+
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).
14
+
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).
17
+
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.
20
+
21
+---
docs/content/toolkit-faq/googlecalendar.md
+21
@@ -1,3 +1,24 @@
1
## How do I set up custom Google OAuth credentials for Google Calendar?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
23
+---
24
+---
\ No newline at end of file
docs/content/toolkit-faq/googledocs.md
+25
@@ -1,3 +1,28 @@
1
## How do I set up custom Google OAuth credentials for Google Docs?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
27
+
28
+---
docs/content/toolkit-faq/googledrive.md
+21
@@ -1,3 +1,24 @@
1
## How do I set up custom Google OAuth credentials for Google Drive?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
23
+---
24
+---
docs/content/toolkit-faq/googlemeet.md
+25
@@ -1,3 +1,28 @@
1
## How do I set up custom Google OAuth credentials for Google Meet?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
27
+
28
+---
docs/content/toolkit-faq/googlesheets.md
+25
@@ -1,3 +1,28 @@
1
## How do I set up custom Google OAuth credentials for Google Sheets?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
27
+
28
+---
docs/content/toolkit-faq/googleslides.md
+25
@@ -1,3 +1,28 @@
1
## How do I set up custom Google OAuth credentials for Google Slides?
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)).
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
27
+
28
+---
docs/content/toolkit-faq/googlesuper.md
new
+18
@@ -0,0 +1,18 @@
1
+## Google Toolkits — FAQ
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).
6
+
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.
10
+
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).
14
+
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).
17
+
18
+---
docs/content/toolkit-faq/googletasks.md
+25
@@ -1,3 +1,28 @@
1
## How do I set up custom Google OAuth credentials for Google Tasks?
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.
8
+
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.
12
+
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).
16
+
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).
19
+
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.
22
+
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.
27
+
28
+---
docs/content/toolkit-faq/hubspot.md
+6
@@ -1,3 +1,9 @@
1
## How do I set up custom OAuth credentials for HubSpot?
2
3
For a step-by-step guide on creating and configuring your own HubSpot OAuth credentials with Composio, see [How to create OAuth credentials for HubSpot](https://composio.dev/auth/hubspot).
4
+
5
+## Query limits
6
+Use `limit <= 100` for `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` and `HUBSPOT_LIST_CONTACTS_PAGE` endpoints to avoid errors.
7
+
8
+## Webhooks
9
+Webhooks require public apps (AppId + Developer API Key). Private/internal apps cannot receive HubSpot webhooks.
docs/content/toolkit-faq/jira.md
+7
@@ -1,3 +1,10 @@
1
## How do I set up custom OAuth credentials for Jira?
2
3
For a step-by-step guide on creating and configuring your own Jira OAuth credentials with Composio, see [How to create OAuth credentials for Jira](https://composio.dev/auth/jira).
4
+
5
+## JQL GET vs POST and Search Issues
6
+- JQL GET and POST target the same search functionality but use different HTTP methods. POST supports complex queries in the request body.
7
+- Use the `fields` parameter to request specific fields; responses may include empty values if fields are undefined. Use `["*all"]` to request all fields.
8
+
9
+## Difference: JQL GET vs POST vs Search Issues
10
+Search Issues uses JQL POST under the hood and supports extra parameters/filters. For consistent results prefer POST when submitting complex queries.
docs/content/toolkit-faq/linkedin.md
+9
@@ -1,3 +1,12 @@
1
## How do I set up custom OAuth credentials for LinkedIn?
2
3
For a step-by-step guide on creating and configuring your own LinkedIn OAuth credentials with Composio, see [How to create OAuth credentials for LinkedIn](https://composio.dev/auth/linkedin).
4
+
5
+## LinkedIn rate limiting
6
+LinkedIn's default OAuth app is shared across users and has strict rate limits. Use a custom OAuth app for production to avoid shared quotas. Example error:
7
+```bash
8
+429 Client Error: Too Many Requests
9
+```
10
+
11
+## LinkedIn scope issue
12
+LinkedIn restricts certain scope combinations (e.g., `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.
docs/content/toolkit-faq/monday.md
+25
@@ -17,3 +17,28 @@ No. The admin only needs to install the app once per workspace. After that, any
17
## How do I set up custom OAuth credentials for Monday.com?
18
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
+## Monday has no scopes
22
+Note: Monday's authConfig does not accept scopes in the same way Google does. Scopes are configured on the OAuth app itself. When using the default OAuth app, ensure the required app-level scopes are configured for full toolkit access. If creating a custom app, add these scopes as needed:
23
+
24
+```bash
25
+me:read
26
+boards:read
27
+boards:write
28
+docs:read
29
+docs:write
30
+workspaces:read
31
+workspaces:write
32
+users:read
33
+users:write
34
+account:read
35
+notifications:write
36
+updates:read
37
+updates:write
38
+assets:read
39
+tags:read
40
+teams:read
41
+teams:write
42
+webhooks:write
43
+webhooks:read
44
+```
docs/content/toolkit-faq/notion.md
new
+21
@@ -0,0 +1,21 @@
1
+## Notion Toolkit — FAQ
2
+
3
+## Notion Operations show Composio instead of user’s name
4
+Why it happens: Notion attributes actions to the Integration itself (name/logo set in the Integration configuration), so operations and comments show the integration identity rather than the individual user.
5
+Fix: create and use your own Notion integration if you need a custom name/logo. See: https://developers.notion.com/docs/create-a-notion-integration
6
+
7
+## Granting access to more pages
8
+If you initially granted access to specific pages and later need to add more:
9
+1. Open Notion → Settings & Members → Connections
10
+2. Select the integration (Composio or your custom integration)
11
+3. Click "Select pages" (or "Manage access") and add/remove pages as required
12
+
13
+## Notion has no scopes
14
+Notion does not use OAuth scopes. Instead, integrations are granted access to specific resources (pages/databases) during the authorization flow or via integration settings. You do not need to pass scopes when creating an authConfig.
15
+
16
+## Configuring Scopes / Access model
17
+Notion access is controlled by the integration type:
18
+- OAuth app (public): access selection happens at authorization time.
19
+- Internal integration (API key): page access is managed in the Integration settings.
20
+Choose the integration model that matches your deployment and permissions needs.
21
+
docs/content/toolkit-faq/one_drive.md
new
+11
@@ -0,0 +1,11 @@
1
+## OneDrive Toolkit — FAQ
2
+
3
+## Why am I getting 404 on `ONE_DRIVE_DOWNLOAD_FILE` for my shared file?
4
+Cause: items shown in "Shared" may be references to files that live in a SharePoint site (not actual files in the user's OneDrive). Those referenced items cannot be downloaded via the OneDrive item endpoints.
5
+
6
+Fix:
7
+- Open the file's location in OneDrive/SharePoint and choose **Copy to → My files** to create a real copy in the user's OneDrive.
8
+- After the copy completes, download the copied file with `ONE_DRIVE_DOWNLOAD_FILE`.
9
+
10
+Note: if you need programmatic access to files stored in SharePoint sites, use the SharePoint APIs or ensure the file is copied into the user's OneDrive first.
11
+
docs/content/toolkit-faq/outlook.md
+10
@@ -1,3 +1,13 @@
1
## How do I set up custom OAuth credentials for Microsoft (Outlook)?
2
3
For a step-by-step guide on creating and configuring your own Microsoft (Outlook) OAuth credentials with Composio, see [How to create OAuth credentials for Microsoft (Outlook)](https://composio.dev/auth/outlook).
4
+
5
+## Outlook new message trigger only sends the message ID
6
+Outlook's official webhooks send only the message payload ID on trigger events. To fetch the full message (subject, body, headers), call the `OUTLOOK_GET_MESSAGE` tool with that message ID.
7
+
8
+## I cannot see the sent message details while using OUTLOOK_SEND_EMAIL
9
+Why: Microsoft Graph's send endpoint returns an HTTP 202 with no message details. Workaround: create a draft first with `OUTLOOK_CREATE_DRAFT` (this returns conversationID and messageID), then send the draft using `OUTLOOK_SEND_DRAFT` to obtain those IDs.
10
+Reference: https://learn.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http
11
+
12
+## What's the @odata.context / @odata URL?
13
+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.
docs/content/toolkit-faq/pipedrive.md
+3
@@ -1,3 +1,6 @@
1
## How do I set up custom OAuth credentials for Pipedrive?
2
3
For a step-by-step guide on creating and configuring your own Pipedrive OAuth credentials with Composio, see [How to create OAuth credentials for Pipedrive](https://composio.dev/auth/pipedrive).
4
+
5
+## App not found
6
+If you see "App is not found" when connecting, Composio's default Pipedrive OAuth credentials may have expired. Use your own OAuth app credentials until the default is restored.
docs/content/toolkit-faq/quickbooks.md
new
+9
@@ -0,0 +1,9 @@
1
+## QuickBooks Toolkit — FAQ
2
+
3
+## Why am I seeing a DNS error while connecting my account?
4
+Cause: this commonly happens when the `com.intuit.quickbooks.payment` scope is included in your `authConfig` but the connected QuickBooks account hasn't enabled the Payments module. The Payments scope requires the Payments feature to be active on the QuickBooks side.
5
+
6
+Fix:
7
+- Remove the `com.intuit.quickbooks.payment` scope from the `authConfig` and reconnect, or
8
+- Enable/complete the Payments module in the QuickBooks account you’re connecting, then retry the connection.
9
+
docs/content/toolkit-faq/salesforce.md
+17
@@ -1,3 +1,20 @@
1
## How do I set up custom OAuth credentials for Salesforce?
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
+## Can’t find created items?
6
+If created items don't appear in Salesforce UI, use search to confirm they exist (records may be present but not visible in a given view).
7
+
8
+## Relationships: Pricebooks and Opportunities
9
+Salesforce relationships example: Products → Pricebooks → Opportunities. Example query:
10
+```sql
11
+SELECT Id, Name,
12
+ (SELECT Id, Quantity, UnitPrice, TotalPrice, PricebookEntry.Product2.Name FROM OpportunityLineItems)
13
+FROM Opportunity
14
+```
15
+
16
+## Connection initiation
17
+Required fields for connection: subdomain (your-company.my) and instance endpoint `/services/data/v61.0`. If you see `URL_NOT_RESET`, replace `login` subdomain with your organization’s subdomain.
18
+
19
+## Deprecated tools
20
+Deprecated tools continue to work until removed. Check tool descriptions for "DEPRECATED:" markers.
docs/content/toolkit-faq/shopify.md
+3
@@ -1,3 +1,6 @@
1
## How do I set up custom OAuth credentials for Shopify?
2
3
For a step-by-step guide on creating and configuring your own Shopify OAuth credentials with Composio, see [How to create OAuth credentials for Shopify](https://composio.dev/auth/shopify).
4
+
5
+## Shopify — App not found
6
+Our default Shopify OAuth app may be under review or expired. If you see "App not found" when connecting, use your own OAuth app or API authentication method. We're working with Shopify to restore the default app.
docs/content/toolkit-faq/slack.md
+32
@@ -1,3 +1,35 @@
1
## How do I set up custom OAuth credentials for Slack?
2
3
For a step-by-step guide on creating and configuring your own Slack OAuth credentials with Composio, see [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
4
+
5
+## Slack vs Slackbot — key differences
6
+- Scope: Slack = workspace-level API (channels, files, users); Slackbot = bot-centric messaging/interactivity.
7
+- Triggers: Slack = workspace events; Slackbot = bot entry points (app_mention, DMs, slash commands).
8
+- Actions: Slack can manage channels/files/users; Slackbot focuses on messaging, ephemeral messages, and modals.
9
+- Message identity: Slack can post as app; Slackbot posts as the bot user.
10
+- Use cases: Slack for workspace management; Slackbot for conversational UX and bot flows.
11
+
12
+## Docs & Scopes
13
+See Slack Developer Docs: https://docs.slack.dev/reference/scopes/
14
+
15
+## Redirect URI mismatch
16
+Update in Slack App → OAuth & Permissions → Redirect URLs.
17
+
18
+## Using Webhooks (Events)
19
+1. Enable Event Subscriptions in your Slack app.
20
+2. Set Request URL to: `https://backend.composio.dev/api/v3/trigger_instances/slack/default/handle`
21
+3. Add `reaction_added` (and other events) to Subscribe to Bot Events and save.
22
+- If using Composio Slack app: you're all set.
23
+- If using Slackbot integration: add the bot to channels you want to monitor (or use /add to add Composio App).
24
+
25
+## Scope Errors
26
+1. Missing bot scope → add a bot scope under OAuth & Permissions.
27
+2. "Insufficient scopes" → ensure all scopes from your Auth Config are configured in the Slack app.
28
+
29
+## Action-specific notes
30
+- `as_user` parameter: Slack API — set `as_user=True`; Slackbot — leave blank (defaults False).
31
+- `missing_charset` error: usually due to invalid `as_user`, wrong channel ID, or missing required fields.
32
+
33
+## Cannot use Triggers
34
+Provide the Verification Token (or signing secret) in the Auth Config so Composio can validate incoming events.
35
+
docs/content/toolkit-faq/snowflake.md
+17
@@ -1,3 +1,20 @@
1
## How do I set up custom OAuth credentials for Snowflake?
2
3
For a step-by-step guide on creating and configuring your own Snowflake OAuth credentials with Composio, see [How to create OAuth credentials for Snowflake](https://composio.dev/auth/snowflake).
4
+
5
+## Create Snowflake OAuth app (example)
6
+Example Snowflake SQL to create a security integration for OAuth:
7
+```sql
8
+CREATE SECURITY INTEGRATION oauth_custom_all_roles
9
+ TYPE = oauth
10
+ ENABLED = true
11
+ OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
12
+ OAUTH_REDIRECT_URI = 'https://your-app.com/oauth/callback'
13
+ OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;
14
+```
15
+
16
+## Roles and config
17
+Ensure the OAuth app and Snowflake roles/databases/schemas are configured correctly for the integration.
18
+
19
+## Customer integration notes
20
+Snowflake requires per-customer OAuth credentials; customers often supply their own credentials when integrating with Composio.
docs/content/toolkit-faq/spotify.md
new
+5
@@ -0,0 +1,5 @@
1
+## Spotify Toolkit — FAQ
2
+
3
+## No default OAuth app
4
+We do not provide a default OAuth app for Spotify. You can use your own OAuth app for production. We're in contact with Spotify for approval but recommend creating your own app in the meantime.
5
+
docs/content/toolkit-faq/twitter.md
new
+15
@@ -0,0 +1,15 @@
1
+## Twitter Toolkit — FAQ
2
+
3
+## Twitter rate limiting
4
+Why it happens: the default OAuth app is shared across users and subject to strict rate limits. Good for testing; for production use your own OAuth app.
5
+Example error(for ref only):
6
+```bash
7
+error: 'Request failed error: "{"account_id": <ID>, "product_name": "standard-basic" ',"title" : "UsageCapExceeded", "period" : "Monthly", "scope" : "Product", "detail": "Usage cap exceeded: Monthly product cap", "type": "https://api.twitter.com/2/problems/usage-capped"}"
8
+```
9
+
10
+## Twitter plan-based API access
11
+Twitter enforces plan-based access tiers. Check your project's product/plan for required permissions: https://developer.x.com/en/portal/products
12
+
13
+## Twitter 403s on API calls
14
+Why it happens: your developer account/project may not have the required access level for the endpoint. Example 403 response explains missing enrollment or required level.
15
+
docs/content/toolkit-faq/whatsapp.md
new
+8
@@ -0,0 +1,8 @@
1
+## WhatsApp Toolkit — FAQ
2
+
3
+## Sending messages
4
+The `WHATSAPP_SEND_MESSAGE` tool follows the customer service window: recipients only receive messages within 24 hours of their last message, unless you use a template message which can be sent outside the window.
5
+
6
+## Connection initiation fail
7
+If integration initiation fails with errors like `Missing required fields: generic_id`, ensure required fields are provided. See integration docs: https://docs.composio.dev/toolkits/whatsapp#authentication-details
8
+
docs/content/toolkit-faq/youtube.md
new
+15
@@ -0,0 +1,15 @@
1
+## YouTube Toolkit — FAQ
2
+
3
+## How do I set up custom Google OAuth credentials for YouTube?
4
+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).
5
+
6
+## YouTube rate limit
7
+YouTube's default OAuth app is shared and subject to strict quota limits. For production use, create and use your own OAuth app to avoid shared quotas. Typical error when quota is exceeded:
8
+```bash
9
+{
10
+ "error": {
11
+ "code": 403,
12
+ "message": "The request cannot be completed because you have exceeded your quota",
13
+ }
14
+}
15
+```