Skip to content

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 remaining toolkit FAQs as questions and clean up answers

Sushmithamalleshcf52fbc8f6de
diff --git a/docs/content/toolkit-faq/one_drive.md b/docs/content/toolkit-faq/one_drive.md
index 2c4a49574..bf0852d82 100644
--- a/docs/content/toolkit-faq/one_drive.md
+++ b/docs/content/toolkit-faq/one_drive.md
@@ -1,11 +1,7 @@
-## OneDrive Toolkit — FAQ
+## Why am I getting 404 on `ONE_DRIVE_DOWNLOAD_FILE` for a shared file?
-## Why am I getting 404 on `ONE_DRIVE_DOWNLOAD_FILE` for my shared file?
-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.
+Items in "Shared" may be references to files stored in SharePoint, not actual files in the user's OneDrive. These references can't be downloaded via OneDrive endpoints.
-Fix:
-- Open the file's location in OneDrive/SharePoint and choose **Copy to → My files** to create a real copy in the user's OneDrive.
-- After the copy completes, download the copied file with `ONE_DRIVE_DOWNLOAD_FILE`.
-
-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.
+To fix this, open the file's location in OneDrive or SharePoint, choose "Copy to" then "My files" to create a copy in the user's OneDrive, and download the copy. If you need programmatic access to SharePoint files, use the SharePoint APIs instead.
+---
diff --git a/docs/content/toolkit-faq/outlook.md b/docs/content/toolkit-faq/outlook.md
index 6f90f6bfe..0111f46f1 100644
--- a/docs/content/toolkit-faq/outlook.md
+++ b/docs/content/toolkit-faq/outlook.md
@@ -2,12 +2,16 @@
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).
-## Outlook new message trigger only sends the message ID
-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.
+## Why does the Outlook new message trigger only return a message ID?
-## I cannot see the sent message details while using OUTLOOK_SEND_EMAIL
-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.
-Reference: https://learn.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http
+Outlook's webhooks send only the message ID on trigger events. To get the full message (subject, body, headers), call the `OUTLOOK_GET_MESSAGE` tool with that message ID.
+
+## Why doesn't `OUTLOOK_SEND_EMAIL` return message details?
+
+Microsoft Graph's send endpoint returns an HTTP 202 with no message details. To get the message ID and conversation ID, create a draft first with `OUTLOOK_CREATE_DRAFT`, then send it with `OUTLOOK_SEND_DRAFT`. See [Microsoft Graph docs](https://learn.microsoft.com/en-us/graph/api/user-sendmail?view=graph-rest-1.0&tabs=http).
## What's the @odata.context / @odata URL?
+
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.
+
+---
diff --git a/docs/content/toolkit-faq/pipedrive.md b/docs/content/toolkit-faq/pipedrive.md
index 18b595817..0777791d3 100644
--- a/docs/content/toolkit-faq/pipedrive.md
+++ b/docs/content/toolkit-faq/pipedrive.md
@@ -2,5 +2,8 @@
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).
-## App not found
-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.
+## Why am I seeing "App not found" when connecting Pipedrive?
+
+Composio's default Pipedrive OAuth credentials may have expired. Use your own OAuth app credentials until the default is restored.
+
+---
diff --git a/docs/content/toolkit-faq/quickbooks.md b/docs/content/toolkit-faq/quickbooks.md
index ab5333ea9..e5fe8416d 100644
--- a/docs/content/toolkit-faq/quickbooks.md
+++ b/docs/content/toolkit-faq/quickbooks.md
@@ -1,9 +1,5 @@
-## QuickBooks Toolkit — FAQ
+## Why am I seeing a DNS error while connecting my QuickBooks account?
-## Why am I seeing a DNS error while connecting my account?
-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.
-
-Fix:
-- Remove the `com.intuit.quickbooks.payment` scope from the `authConfig` and reconnect, or
-- Enable/complete the Payments module in the QuickBooks account you’re connecting, then retry the connection.
+This usually happens when the `com.intuit.quickbooks.payment` scope is included in your auth config but the QuickBooks account hasn't enabled the Payments module. Either remove that scope from your auth config and reconnect, or enable the Payments module in QuickBooks first.
+---
diff --git a/docs/content/toolkit-faq/salesforce.md b/docs/content/toolkit-faq/salesforce.md
index e13781410..71e477f46 100644
--- a/docs/content/toolkit-faq/salesforce.md
+++ b/docs/content/toolkit-faq/salesforce.md
@@ -2,19 +2,26 @@
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).
-## Can’t find created items?
-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).
+## Why can't I find items I created in Salesforce?
+
+Created records may not appear in a given Salesforce view. Use search to confirm they exist.
+
+## How do I query relationships like Pricebooks and Opportunities?
+
+Use SOQL subqueries to traverse relationships. For example, Products → Pricebooks → Opportunities:
-## Relationships: Pricebooks and Opportunities
-Salesforce relationships example: Products → Pricebooks → Opportunities. Example query:
```sql
SELECT Id, Name,
(SELECT Id, Quantity, UnitPrice, TotalPrice, PricebookEntry.Product2.Name FROM OpportunityLineItems)
FROM Opportunity
```
-## Connection initiation
-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.
+## What fields are required when connecting Salesforce?
+
+You need your subdomain (e.g., `your-company.my`) and instance endpoint `/services/data/v61.0`. If you see `URL_NOT_RESET`, replace the `login` subdomain with your organization's subdomain.
+
+## What happens to deprecated Salesforce tools?
-## Deprecated tools
Deprecated tools continue to work until removed. Check tool descriptions for "DEPRECATED:" markers.
+
+---
diff --git a/docs/content/toolkit-faq/shopify.md b/docs/content/toolkit-faq/shopify.md
index 0c58f340b..7274ba8d2 100644
--- a/docs/content/toolkit-faq/shopify.md
+++ b/docs/content/toolkit-faq/shopify.md
@@ -2,5 +2,8 @@
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).
-## Shopify — App not found
-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.
+## Why am I seeing "App not found" when connecting Shopify?
+
+The default Shopify OAuth app may be under review or expired. Use your own OAuth app or API authentication method until the default is restored.
+
+---
diff --git a/docs/content/toolkit-faq/slack.md b/docs/content/toolkit-faq/slack.md
index a8183ca66..6f24f5398 100644
--- a/docs/content/toolkit-faq/slack.md
+++ b/docs/content/toolkit-faq/slack.md
@@ -2,34 +2,32 @@
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).
-## Slack vs Slackbot — key differences
-- Scope: Slack = workspace-level API (channels, files, users); Slackbot = bot-centric messaging/interactivity.
-- Triggers: Slack = workspace events; Slackbot = bot entry points (app_mention, DMs, slash commands).
-- Actions: Slack can manage channels/files/users; Slackbot focuses on messaging, ephemeral messages, and modals.
-- Message identity: Slack can post as app; Slackbot posts as the bot user.
-- Use cases: Slack for workspace management; Slackbot for conversational UX and bot flows.
+## What is the difference between Slack and Slackbot toolkits?
-## Docs & Scopes
-See Slack Developer Docs: https://docs.slack.dev/reference/scopes/
+Slack is for workspace-level API access (channels, files, users) while Slackbot is bot-centric (messaging, interactivity). Slack triggers cover workspace events; Slackbot covers bot entry points like app mentions, DMs, and slash commands. Slack can post as the app; Slackbot posts as the bot user.
-## Redirect URI mismatch
-Update in Slack App → OAuth & Permissions → Redirect URLs.
+## Where can I find Slack's available scopes?
-## Using Webhooks (Events)
-1. Enable Event Subscriptions in your Slack app.
-2. Set Request URL to: `https://backend.composio.dev/api/v3/trigger_instances/slack/default/handle`
-3. Add `reaction_added` (and other events) to Subscribe to Bot Events and save.
-- If using Composio Slack app: you're all set.
-- If using Slackbot integration: add the bot to channels you want to monitor (or use /add to add Composio App).
+See the [Slack scopes reference](https://docs.slack.dev/reference/scopes/).
-## Scope Errors
-1. Missing bot scope → add a bot scope under OAuth & Permissions.
-2. "Insufficient scopes" → ensure all scopes from your Auth Config are configured in the Slack app.
+## Why am I getting a redirect URI mismatch error?
-## Action-specific notes
-- `as_user` parameter: Slack API — set `as_user=True`; Slackbot — leave blank (defaults False).
-- `missing_charset` error: usually due to invalid `as_user`, wrong channel ID, or missing required fields.
+Update the redirect URL in your Slack App under OAuth & Permissions → Redirect URLs.
-## Cannot use Triggers
-Provide the Verification Token (or signing secret) in the Auth Config so Composio can validate incoming events.
+## How do I set up Slack event webhooks?
+Enable Event Subscriptions in your Slack app. Set the Request URL to `https://backend.composio.dev/api/v3/trigger_instances/slack/default/handle`. Add events (e.g., `reaction_added`) to Subscribe to Bot Events and save. If using the Slackbot integration, add the bot to the channels you want to monitor.
+
+## Why am I getting scope errors on Slack?
+
+Either you're missing a bot scope (add one under OAuth & Permissions) or you have "Insufficient scopes" (ensure all scopes from your auth config are configured in the Slack app).
+
+## What does the `as_user` parameter do in Slack tools?
+
+For the Slack toolkit, set `as_user=True` to post as the authenticated user. For Slackbot, leave it blank (defaults to false). A `missing_charset` error usually means invalid `as_user`, wrong channel ID, or missing required fields.
+
+## Why aren't my Slack triggers working?
+
+Provide the Verification Token or signing secret in the auth config so Composio can validate incoming events.
+
+---
diff --git a/docs/content/toolkit-faq/snowflake.md b/docs/content/toolkit-faq/snowflake.md
index 9505198df..be4d2c8dd 100644
--- a/docs/content/toolkit-faq/snowflake.md
+++ b/docs/content/toolkit-faq/snowflake.md
@@ -2,8 +2,10 @@
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).
-## Create Snowflake OAuth app (example)
+## How do I create a Snowflake OAuth app?
+
Example Snowflake SQL to create a security integration for OAuth:
+
```sql
CREATE SECURITY INTEGRATION oauth_custom_all_roles
TYPE = oauth
@@ -13,8 +15,12 @@ CREATE SECURITY INTEGRATION oauth_custom_all_roles
OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;
```
-## Roles and config
-Ensure the OAuth app and Snowflake roles/databases/schemas are configured correctly for the integration.
+## How do I configure roles and permissions for Snowflake?
+
+Ensure the OAuth app and Snowflake roles, databases, and schemas are configured correctly for the integration.
+
+## Does Snowflake require per-customer OAuth credentials?
+
+Yes. Snowflake typically requires per-customer OAuth credentials. Customers often supply their own credentials when integrating with Composio.
-## Customer integration notes
-Snowflake requires per-customer OAuth credentials; customers often supply their own credentials when integrating with Composio.
+---
diff --git a/docs/content/toolkit-faq/spotify.md b/docs/content/toolkit-faq/spotify.md
index d1ae9bfce..c4a78b1e9 100644
--- a/docs/content/toolkit-faq/spotify.md
+++ b/docs/content/toolkit-faq/spotify.md
@@ -1,5 +1,5 @@
-## Spotify Toolkit — FAQ
+## Why is there no default OAuth app for Spotify?
-## No default OAuth app
-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.
+Composio does not provide a default OAuth app for Spotify. Create your own OAuth app in the [Spotify Developer Dashboard](https://developer.spotify.com/dashboard) to use the Spotify toolkit.
+---
diff --git a/docs/content/toolkit-faq/twitter.md b/docs/content/toolkit-faq/twitter.md
index 23d15c109..98480b49e 100644
--- a/docs/content/toolkit-faq/twitter.md
+++ b/docs/content/toolkit-faq/twitter.md
@@ -1,15 +1,13 @@
-## Twitter Toolkit — FAQ
+## Why am I getting rate limit or "UsageCapExceeded" errors on Twitter?
-## Twitter rate limiting
-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.
-Example error(for ref only):
-```bash
-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"}"
-```
+The default OAuth app is shared across users and has strict rate limits. It works for testing, but for production use your own OAuth app.
-## Twitter plan-based API access
-Twitter enforces plan-based access tiers. Check your project's product/plan for required permissions: https://developer.x.com/en/portal/products
+## Why can't I access certain Twitter API endpoints?
-## Twitter 403s on API calls
-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.
+Twitter enforces plan-based access tiers. Check your project's product and plan for the required permissions at the [Twitter Developer Portal](https://developer.x.com/en/portal/products).
+## Why am I getting 403 errors on Twitter API calls?
+
+Your developer account or project may not have the required access level for the endpoint. Check your enrollment and access tier in the Twitter Developer Portal.
+
+---
diff --git a/docs/content/toolkit-faq/whatsapp.md b/docs/content/toolkit-faq/whatsapp.md
index a1d36baee..95b3d1945 100644
--- a/docs/content/toolkit-faq/whatsapp.md
+++ b/docs/content/toolkit-faq/whatsapp.md
@@ -1,8 +1,9 @@
-## WhatsApp Toolkit — FAQ
+## Why isn't my WhatsApp message being delivered?
-## Sending messages
-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.
+WhatsApp has a 24-hour customer service window. Recipients only receive messages within 24 hours of their last message to you. To message outside this window, use a template message.
-## Connection initiation fail
-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
+## Why is my WhatsApp connection failing with "Missing required fields"?
+Ensure all required fields are provided when initiating the connection. See the [WhatsApp authentication details](https://docs.composio.dev/toolkits/whatsapp#authentication-details).
+
+---
diff --git a/docs/content/toolkit-faq/youtube.md b/docs/content/toolkit-faq/youtube.md
index cf4365777..101440264 100644
--- a/docs/content/toolkit-faq/youtube.md
+++ b/docs/content/toolkit-faq/youtube.md
@@ -1,15 +1,9 @@
-## YouTube Toolkit — FAQ
-
## How do I set up custom Google OAuth credentials for YouTube?
+
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).
-## YouTube rate limit
-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:
-```bash
-{
- "error": {
- "code": 403,
- "message": "The request cannot be completed because you have exceeded your quota",
- }
-}
-```
+## Why am I getting quota errors on YouTube?
+
+The default OAuth app is shared and has strict quota limits. For production, create your own OAuth app to get a dedicated quota.
+
+---