@devries-cameron20 / composio-1 / commits / 65f5b4719
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

docs: move composio.dev/auth setup guides into toolkit pages (#5416)

The setup guides at `composio.dev/auth/<slug>` (96 pages on the landing site) are being removed. A separate landing PR redirects each one to docs. Most docs toolkit pages only linked out to those guides ("see How to create OAuth credentials for X"), so once the redirects land, the link would point back at the docs page itself and the setup steps would be lost. This PR moves the steps into the docs. ## What changed - **Toolkit FAQs (`docs/content/toolkits/faq/*.md`)**: each toolkit page now has a setup question with the full steps from its landing guide: provider console, redirect URI, scopes, API enablement, consent and verification, credentials, the Composio auth config steps, how to confirm the account is Active, and provider gotchas. 94 files: 53 updated, 41 new. Every docs pointer to `composio.dev/auth` is gone. - **`custom-app-vs-managed-app.mdx`**: the "Step-by-step OAuth guides" links now point to toolkit pages. - **Screenshots (`docs/public/images/toolkits/`)**: 611 screenshots from the landing guides, converted to WebP at 1400 px max (19 MB in total, down from 78 MB of originals), placed 868 times under the steps they illustrate. Images used by several toolkits live once in `shared/`. The landing guides had 1,341 image references. The rest were left out because they showed one of: - a redirect URI other than the v1 default; - a flow or field the docs correct (manual Trello tokens, Google Ads developer token, managed-auth walkthroughs on custom-OAuth pages); - a step the docs don't have; - near-duplicates; - personal data: staff names and usernames (including inside org slugs and auth config names), emails, and unredacted client, account, tenant, `ac_`/`ca_`/`lk_` or test-user IDs. Five header avatars with real faces were blurred. Every kept image was opened and checked. Supabase and Daytona have no screenshots, because every one of theirs showed personal data. ## Redirect mapping The landing PR reads this block. It covers 96 guides plus `/auth`, and every target returned 200 when checked. ```json { "/auth": "https://docs.composio.dev/toolkits", "/auth/airtable": "https://docs.composio.dev/toolkits/airtable", "/auth/apollo": "https://docs.composio.dev/toolkits/apollo", "/auth/asana": "https://docs.composio.dev/toolkits/asana", "/auth/azure_monitor_activity_log": "https://docs.composio.dev/toolkits/azure_monitor_activity_log", "/auth/bitbucket": "https://docs.composio.dev/toolkits/bitbucket", "/auth/calendly": "https://docs.composio.dev/toolkits/calendly", "/auth/canva": "https://docs.composio.dev/toolkits/canva", "/auth/confluence": "https://docs.composio.dev/toolkits/confluence", "/auth/daytona": "https://docs.composio.dev/toolkits/daytona", "/auth/docusign": "https://docs.composio.dev/toolkits/docusign", "/auth/dropbox": "https://docs.composio.dev/toolkits/dropbox", "/auth/dynamics365": "https://docs.composio.dev/toolkits/dynamics365", "/auth/excel": "https://docs.composio.dev/toolkits/excel", "/auth/facebook": "https://docs.composio.dev/toolkits/facebook", "/auth/fathomai": "https://docs.composio.dev/toolkits/fathom", "/auth/github": "https://docs.composio.dev/toolkits/github", "/auth/gitlab": "https://docs.composio.dev/toolkits/gitlab", "/auth/gmail": "https://docs.composio.dev/toolkits/gmail", "/auth/gong": "https://docs.composio.dev/toolkits/gong", "/auth/google-analytics": "https://docs.composio.dev/toolkits/google_analytics", "/auth/google-search-console": "https://docs.composio.dev/toolkits/google_search_console", "/auth/google_admin": "https://docs.composio.dev/toolkits/google_admin", "/auth/google_adsense": "https://docs.composio.dev/toolkits/google_adsense", "/auth/google_business_profile": "https://docs.composio.dev/toolkits/google_business_profile", "/auth/google_chat": "https://docs.composio.dev/toolkits/google_chat", "/auth/google_classroom": "https://docs.composio.dev/toolkits/google_classroom", "/auth/google_data_studio": "https://docs.composio.dev/toolkits/google_data_studio", "/auth/google_maps": "https://docs.composio.dev/toolkits/google_maps", "/auth/google_merchant": "https://docs.composio.dev/toolkits/google_merchant", "/auth/googleads": "https://docs.composio.dev/toolkits/googleads", "/auth/googleapps": "https://docs.composio.dev/toolkits/googlesuper", "/auth/googlebigquery": "https://docs.composio.dev/toolkits/googlebigquery", "/auth/googlecalendar": "https://docs.composio.dev/toolkits/googlecalendar", "/auth/googlecontacts": "https://docs.composio.dev/toolkits/googlecontacts", "/auth/googledocs": "https://docs.composio.dev/toolkits/googledocs", "/auth/googledrive": "https://docs.composio.dev/toolkits/googledrive", "/auth/googleforms": "https://docs.composio.dev/toolkits/googleforms", "/auth/googlemeet": "https://docs.composio.dev/toolkits/googlemeet", "/auth/googlephotos": "https://docs.composio.dev/toolkits/googlephotos", "/auth/googlesheets": "https://docs.composio.dev/toolkits/googlesheets", "/auth/googleslides": "https://docs.composio.dev/toolkits/googleslides", "/auth/googlesuper": "https://docs.composio.dev/toolkits/googlesuper", "/auth/googletasks": "https://docs.composio.dev/toolkits/googletasks", "/auth/gorgias": "https://docs.composio.dev/toolkits/gorgias", "/auth/highlevel_location": "https://docs.composio.dev/toolkits/highlevel_location", "/auth/hubspot": "https://docs.composio.dev/toolkits/hubspot", "/auth/instantly": "https://docs.composio.dev/toolkits/instantly", "/auth/jira": "https://docs.composio.dev/toolkits/jira", "/auth/linear": "https://docs.composio.dev/toolkits/linear", "/auth/linkedin": "https://docs.composio.dev/toolkits/linkedin", "/auth/microsoft_advertising": "https://docs.composio.dev/toolkits/microsoft_advertising", "/auth/microsoft_bookings": "https://docs.composio.dev/toolkits/microsoft_bookings", "/auth/microsoft_entra_id": "https://docs.composio.dev/toolkits/microsoft_entra_id", "/auth/microsoft_power_bi": "https://docs.composio.dev/toolkits/microsoft_power_bi", "/auth/microsoft_teams": "https://docs.composio.dev/toolkits/microsoft_teams", "/auth/microsoft_todo": "https://docs.composio.dev/toolkits/microsoft_todo", "/auth/monday": "https://docs.composio.dev/toolkits/monday", "/auth/notebook_lm": "https://docs.composio.dev/toolkits/notebook_lm", "/auth/notion": "https://docs.composio.dev/toolkits/notion", "/auth/one_drive": "https://docs.composio.dev/toolkits/one_drive", "/auth/onenote": "https://docs.composio.dev/toolkits/onenote", "/auth/outlook": "https://docs.composio.dev/toolkits/outlook", "/auth/pagerduty": "https://docs.composio.dev/toolkits/pagerduty", "/auth/pipedrive": "https://docs.composio.dev/toolkits/pipedrive", "/auth/plaid": "https://docs.composio.dev/toolkits/plaid", "/auth/posthog": "https://docs.composio.dev/toolkits/posthog", "/auth/powerpoint": "https://docs.composio.dev/toolkits/microsoft_powerpoint", "/auth/ramp": "https://docs.composio.dev/toolkits/ramp", "/auth/rocketlane": "https://docs.composio.dev/toolkits/rocketlane", "/auth/salesforce": "https://docs.composio.dev/toolkits/salesforce", "/auth/servicem8": "https://docs.composio.dev/toolkits/servicem8", "/auth/share_point": "https://docs.composio.dev/toolkits/share_point", "/auth/sharepoint_graph": "https://docs.composio.dev/toolkits/sharepoint_graph", "/auth/shopify": "https://docs.composio.dev/toolkits/shopify", "/auth/slack": "https://docs.composio.dev/toolkits/slack", "/auth/slack_custom": "https://docs.composio.dev/toolkits/slack", "/auth/snowflake": "https://docs.composio.dev/toolkits/snowflake", "/auth/stripe": "https://docs.composio.dev/toolkits/stripe", "/auth/supabase": "https://docs.composio.dev/toolkits/supabase", "/auth/telegram": "https://docs.composio.dev/toolkits/telegram", "/auth/ticktick": "https://docs.composio.dev/toolkits/ticktick", "/auth/trello": "https://docs.composio.dev/toolkits/trello", "/auth/twitter": "https://docs.composio.dev/toolkits/twitter", "/auth/word": "https://docs.composio.dev/toolkits/microsoft_word", "/auth/workday": "https://docs.composio.dev/toolkits/workday", "/auth/xero": "https://docs.composio.dev/toolkits/xero", "/auth/youtube": "https://docs.composio.dev/toolkits/youtube", "/auth/zendesk": "https://docs.composio.dev/toolkits/zendesk", "/auth/zoho": "https://docs.composio.dev/toolkits/zoho", "/auth/zoho_bigin": "https://docs.composio.dev/toolkits/zoho_bigin", "/auth/zoho_books": "https://docs.composio.dev/toolkits/zoho_books", "/auth/zoho_desk": "https://docs.composio.dev/toolkits/zoho_desk", "/auth/zoho_inventory": "https://docs.composio.dev/toolkits/zoho_inventory", "/auth/zoho_invoice": "https://docs.composio.dev/toolkits/zoho_invoice", "/auth/zoho_mail": "https://docs.composio.dev/toolkits/zoho_mail", "/auth/zoom": "https://docs.composio.dev/toolkits/zoom" } ``` Mapping notes: each slug maps to its toolkit page, with these exceptions: - `googleapps` (the generic Google guide) maps to `googlesuper`, the all-Google toolkit. - `slack_custom` maps to `slack`. - `word` maps to `microsoft_word`. - `powerpoint` maps to `microsoft_powerpoint`. - `fathomai` maps to `fathom`. - `google-analytics` maps to `google_analytics`. - `google-search-console` maps to `google_search_console`. - `/auth` itself maps to the toolkits index. ## Evidence - `GITHUB_ACTIONS=true bun run build` in `docs/`: exit 0. - `bun test tests/static/`: 835 pass, 0 fail. The first run caught a Composio API curl in the Plaid FAQ that broke the code-example contract (which requires SDK tabs). That curl is now prose with a link to the API reference. - `bun run lint:links`: 0 errors. That linter doesn't scan the FAQ `.md` files, so every `/docs/...` and `/toolkits/...` link and anchor added in them was also checked by hand against `content/docs`. - Every FAQ file was run through `parseToolkitFaq` (the renderer's parser): 261 items, none empty, no tables. The renderer has no GFM support, so tables wouldn't render. It also produced all 873 `<img>` tags (868 new ones plus 5 earlier screenshots on the salesforce, slack, outlook and monday pages), and no numbered list restarts after an image. Every image path resolves, and no image file is unreferenced. - Facts were checked against the live auth config schema for each toolkit (`GET /api/v3/toolkits/<slug>`): default `oauth_redirect_uri`, default scopes, and required auth config and connection fields. ## Where the landing guides were wrong Where a landing guide disagreed with the live product, the docs follow the product: - **Redirect URI:** about 20 guides said `https://backend.composio.dev/api/v3/toolkits/auth/callback`, and gitlab and snowflake said `/api/v3/auth-apps/add`. Every toolkit's auth config defaults to `https://backend.composio.dev/api/v1/auth-apps/add`, so the docs use that and say it must match the auth config's `oauth_redirect_uri`. The v3 callback is still documented in `custom-auth-configs` for anyone who sets it explicitly. - **Google Ads:** the old FAQ item said to put the developer token on the auth config. The live schema marks that field deprecated and not sent to Google, so that item is replaced. - **Scope lists:** the guides' scope lists were dropped where they didn't match the defaults (snowflake, pipedrive, linear, zoom, ticktick). The docs list the actual default scopes instead. - **Stripe:** the guide said Stripe generates a client secret. Stripe Connect OAuth actually uses the platform's secret API key as `client_secret`, so the docs say that. - **Wrong auth type:** instantly, posthog and telegram had guides or FAQ questions describing OAuth or bearer auth. The live auth mode is an API key, and the docs now say so. - **Trello:** the guide is API key plus a manual token. The toolkit's only mode is OAuth1, so the API key and secret are documented as the consumer key and secret. ## Not in this PR - The KB files (`docs/content/kb`, `docs/kb`, `docs/lib/knowledge`) still link to `composio.dev/auth`. #5388 deletes them, so they're left alone here. - `docs/public/openapi*.json` has `composio.dev/auth/...` as example values. Those files are generated from the backend. - The SDK tests use `composio.dev/auth/redirect` as a mock callback URL. It isn't a guide. ## Per-slug changes | Landing page | Docs target | Change | |---|---|---| | `/auth` | [/toolkits](https://docs.composio.dev/toolkits) | none (index page) | | `/auth/airtable` | [/toolkits/airtable](https://docs.composio.dev/toolkits/airtable) | added: OAuth integration, redirect URI, scopes, base selection | | `/auth/apollo` | [/toolkits/apollo](https://docs.composio.dev/toolkits/apollo) | added: API key creation, master key, connect steps | | `/auth/asana` | [/toolkits/asana](https://docs.composio.dev/toolkits/asana) | added: app, redirect URI, granular scopes | | `/auth/azure_monitor_activity_log` | [/toolkits/azure_monitor_activity_log](https://docs.composio.dev/toolkits/azure_monitor_activity_log) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; Subscription ID, RBAC | | `/auth/bitbucket` | [/toolkits/bitbucket](https://docs.composio.dev/toolkits/bitbucket) | added (new file): workspace OAuth consumer, scopes | | `/auth/calendly` | [/toolkits/calendly](https://docs.composio.dev/toolkits/calendly) | added: OAuth app, sandbox vs production, redirect URI | | `/auth/canva` | [/toolkits/canva](https://docs.composio.dev/toolkits/canva) | added: integration type, redirect URI, scopes, review | | `/auth/confluence` | [/toolkits/confluence](https://docs.composio.dev/toolkits/confluence) | added: Atlassian 3LO app, permissions, distribution, subdomain, scopes, offline_access | | `/auth/daytona` | [/toolkits/daytona](https://docs.composio.dev/toolkits/daytona) | added (new file): API key, organization ID | | `/auth/docusign` | [/toolkits/docusign](https://docs.composio.dev/toolkits/docusign) | added: Apps and Keys, secret key, redirect URI, dev vs prod auth URL, consent, go-live | | `/auth/dropbox` | [/toolkits/dropbox](https://docs.composio.dev/toolkits/dropbox) | added: scoped app, access type, redirect URI, permissions | | `/auth/dynamics365` | [/toolkits/dynamics365](https://docs.composio.dev/toolkits/dynamics365) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; environment scope, subdomain and region fields | | `/auth/excel` | [/toolkits/excel](https://docs.composio.dev/toolkits/excel) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; app-only mode | | `/auth/facebook` | [/toolkits/facebook](https://docs.composio.dev/toolkits/facebook) | added: Meta app, redirect allow list, scopes, App Review | | `/auth/fathomai` | [/toolkits/fathom](https://docs.composio.dev/toolkits/fathom) | added (new file): managed-auth connect steps, API key option | | `/auth/github` | [/toolkits/github](https://docs.composio.dev/toolkits/github) | added: OAuth App setup, scopes, org approval | | `/auth/gitlab` | [/toolkits/gitlab](https://docs.composio.dev/toolkits/gitlab) | added: application setup, scopes, self-managed base URL fields | | `/auth/gmail` | [/toolkits/gmail](https://docs.composio.dev/toolkits/gmail) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Gmail API, restricted-scope verification | | `/auth/gong` | [/toolkits/gong](https://docs.composio.dev/toolkits/gong) | added: integration setup, scopes, API base URL | | `/auth/google-analytics` | [/toolkits/google_analytics](https://docs.composio.dev/toolkits/google_analytics) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Data and Admin APIs | | `/auth/google-search-console` | [/toolkits/google_search_console](https://docs.composio.dev/toolkits/google_search_console) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification | | `/auth/google_admin` | [/toolkits/google_admin](https://docs.composio.dev/toolkits/google_admin) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Admin SDK, admin privileges | | `/auth/google_adsense` | [/toolkits/google_adsense](https://docs.composio.dev/toolkits/google_adsense) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification | | `/auth/google_business_profile` | [/toolkits/google_business_profile](https://docs.composio.dev/toolkits/google_business_profile) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; API access approval | | `/auth/google_chat` | [/toolkits/google_chat](https://docs.composio.dev/toolkits/google_chat) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Chat app configuration | | `/auth/google_classroom` | [/toolkits/google_classroom](https://docs.composio.dev/toolkits/google_classroom) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification | | `/auth/google_data_studio` | [/toolkits/google_data_studio](https://docs.composio.dev/toolkits/google_data_studio) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; domain-wide delegation | | `/auth/google_maps` | [/toolkits/google_maps](https://docs.composio.dev/toolkits/google_maps) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Places and Routes APIs, billing, API key option | | `/auth/google_merchant` | [/toolkits/google_merchant](https://docs.composio.dev/toolkits/google_merchant) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Merchant API registration | | `/auth/googleads` | [/toolkits/googleads](https://docs.composio.dev/toolkits/googleads) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; API access levels, Customer ID; replaced the outdated developer-token item | | `/auth/googleapps` | [/toolkits/googlesuper](https://docs.composio.dev/toolkits/googlesuper) | added: generic Google OAuth setup, merged into the Google Super section | | `/auth/googlebigquery` | [/toolkits/googlebigquery](https://docs.composio.dev/toolkits/googlebigquery) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; IAM note, service account scheme | | `/auth/googlecalendar` | [/toolkits/googlecalendar](https://docs.composio.dev/toolkits/googlecalendar) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Calendar API | | `/auth/googlecontacts` | [/toolkits/googlecontacts](https://docs.composio.dev/toolkits/googlecontacts) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; People API | | `/auth/googledocs` | [/toolkits/googledocs](https://docs.composio.dev/toolkits/googledocs) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Docs and Drive APIs | | `/auth/googledrive` | [/toolkits/googledrive](https://docs.composio.dev/toolkits/googledrive) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Drive API, narrower scopes | | `/auth/googleforms` | [/toolkits/googleforms](https://docs.composio.dev/toolkits/googleforms) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Forms and Drive APIs | | `/auth/googlemeet` | [/toolkits/googlemeet](https://docs.composio.dev/toolkits/googlemeet) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Meet REST API | | `/auth/googlephotos` | [/toolkits/googlephotos](https://docs.composio.dev/toolkits/googlephotos) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Photos Library API, appcreateddata scopes | | `/auth/googlesheets` | [/toolkits/googlesheets](https://docs.composio.dev/toolkits/googlesheets) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Sheets and Drive APIs | | `/auth/googleslides` | [/toolkits/googleslides](https://docs.composio.dev/toolkits/googleslides) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Slides and Drive APIs | | `/auth/googlesuper` | [/toolkits/googlesuper](https://docs.composio.dev/toolkits/googlesuper) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; enable each product's API | | `/auth/googletasks` | [/toolkits/googletasks](https://docs.composio.dev/toolkits/googletasks) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Tasks API | | `/auth/gorgias` | [/toolkits/gorgias](https://docs.composio.dev/toolkits/gorgias) | added (new file): managed flow via App Store, custom app via Partner Portal, subdomain | | `/auth/highlevel_location` | [/toolkits/highlevel_location](https://docs.composio.dev/toolkits/highlevel_location) | added (new file): Marketplace app, sub-account target, client keys, scopes | | `/auth/hubspot` | [/toolkits/hubspot](https://docs.composio.dev/toolkits/hubspot) | added: developer app setup; links existing scope items | | `/auth/instantly` | [/toolkits/instantly](https://docs.composio.dev/toolkits/instantly) | added: API key (v2) and scopes, replacing the wrong OAuth question | | `/auth/jira` | [/toolkits/jira](https://docs.composio.dev/toolkits/jira) | added: Atlassian 3LO app, permissions, distribution, subdomain, scopes | | `/auth/linear` | [/toolkits/linear](https://docs.composio.dev/toolkits/linear) | added (new file): OAuth app, scopes, API key option | | `/auth/linkedin` | [/toolkits/linkedin](https://docs.composio.dev/toolkits/linkedin) | added: OAuth app, redirect URI, scopes | | `/auth/microsoft_advertising` | [/toolkits/microsoft_advertising](https://docs.composio.dev/toolkits/microsoft_advertising) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; developer token | | `/auth/microsoft_bookings` | [/toolkits/microsoft_bookings](https://docs.composio.dev/toolkits/microsoft_bookings) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes | | `/auth/microsoft_entra_id` | [/toolkits/microsoft_entra_id](https://docs.composio.dev/toolkits/microsoft_entra_id) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; app-only mode | | `/auth/microsoft_power_bi` | [/toolkits/microsoft_power_bi](https://docs.composio.dev/toolkits/microsoft_power_bi) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; Power BI Service permissions | | `/auth/microsoft_teams` | [/toolkits/microsoft_teams](https://docs.composio.dev/toolkits/microsoft_teams) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; work or school accounts only, app-only mode | | `/auth/microsoft_todo` | [/toolkits/microsoft_todo](https://docs.composio.dev/toolkits/microsoft_todo) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes | | `/auth/monday` | [/toolkits/monday](https://docs.composio.dev/toolkits/monday) | added: OAuth app, signing secret, OAuth 2.1 field, install requirement | | `/auth/notebook_lm` | [/toolkits/notebook_lm](https://docs.composio.dev/toolkits/notebook_lm) | added (new file): Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; Discovery Engine API, license and IAM role | | `/auth/notion` | [/toolkits/notion](https://docs.composio.dev/toolkits/notion) | added: public integration, capabilities, internal integration token option | | `/auth/one_drive` | [/toolkits/one_drive](https://docs.composio.dev/toolkits/one_drive) | added: Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; app-only mode | | `/auth/onenote` | [/toolkits/onenote](https://docs.composio.dev/toolkits/onenote) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; revoke access | | `/auth/outlook` | [/toolkits/outlook](https://docs.composio.dev/toolkits/outlook) | added: Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; personal-account caveat, app-only mode | | `/auth/pagerduty` | [/toolkits/pagerduty](https://docs.composio.dev/toolkits/pagerduty) | added (new file): OAuth app, permissions, account selection | | `/auth/pipedrive` | [/toolkits/pipedrive](https://docs.composio.dev/toolkits/pipedrive) | added: Developer Hub app, callback, scopes; merged old item | | `/auth/plaid` | [/toolkits/plaid](https://docs.composio.dev/toolkits/plaid) | added (new file): keys, environments, connection fields, Sandbox token steps, Production checklist, common errors | | `/auth/posthog` | [/toolkits/posthog](https://docs.composio.dev/toolkits/posthog) | added: personal API key, region hosts, replacing the wrong OAuth question | | `/auth/powerpoint` | [/toolkits/microsoft_powerpoint](https://docs.composio.dev/toolkits/microsoft_powerpoint) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes | | `/auth/ramp` | [/toolkits/ramp](https://docs.composio.dev/toolkits/ramp) | added (new file): developer app, grant types, scopes, demo vs production URLs | | `/auth/rocketlane` | [/toolkits/rocketlane](https://docs.composio.dev/toolkits/rocketlane) | added (new file): API key, role-based access | | `/auth/salesforce` | [/toolkits/salesforce](https://docs.composio.dev/toolkits/salesforce) | added: External Client App and Connected App, scopes, IP allowlist, refresh token notes | | `/auth/servicem8` | [/toolkits/servicem8](https://docs.composio.dev/toolkits/servicem8) | added (new file): add-on setup, activation URL, scopes | | `/auth/share_point` | [/toolkits/share_point](https://docs.composio.dev/toolkits/share_point) | added: SharePoint API permissions, .default scope, tenant and subsite fields, certificate app-only mode | | `/auth/sharepoint_graph` | [/toolkits/sharepoint_graph](https://docs.composio.dev/toolkits/sharepoint_graph) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes; app-only mode | | `/auth/shopify` | [/toolkits/shopify](https://docs.composio.dev/toolkits/shopify) | added: Dev Dashboard app, scopes, release, store subdomain | | `/auth/slack` | [/toolkits/slack](https://docs.composio.dev/toolkits/slack) | added: managed-auth note, revoke access | | `/auth/slack_custom` | [/toolkits/slack](https://docs.composio.dev/toolkits/slack) | added: Slack app setup, redirect URL, scopes, verification token for triggers | | `/auth/snowflake` | [/toolkits/snowflake](https://docs.composio.dev/toolkits/snowflake) | added: security integration SQL, credentials, account field, scopes; replaced old item | | `/auth/stripe` | [/toolkits/stripe](https://docs.composio.dev/toolkits/stripe) | added: Connect OAuth app, secret key as client secret, scopes, API key option | | `/auth/supabase` | [/toolkits/supabase](https://docs.composio.dev/toolkits/supabase) | added: OAuth app, scopes, personal access token option | | `/auth/telegram` | [/toolkits/telegram](https://docs.composio.dev/toolkits/telegram) | added (new file): BotFather token, permissions | | `/auth/ticktick` | [/toolkits/ticktick](https://docs.composio.dev/toolkits/ticktick) | added (new file): developer app, scopes | | `/auth/trello` | [/toolkits/trello](https://docs.composio.dev/toolkits/trello) | added (new file): Power-Up API key and secret as OAuth1 consumer key and secret, allowed origins | | `/auth/twitter` | [/toolkits/twitter](https://docs.composio.dev/toolkits/twitter) | added: X app, bearer token field, scopes, troubleshooting | | `/auth/word` | [/toolkits/microsoft_word](https://docs.composio.dev/toolkits/microsoft_word) | added (new file): Entra app registration, redirect URI, client secret, delegated permissions and admin consent, scopes | | `/auth/workday` | [/toolkits/workday](https://docs.composio.dev/toolkits/workday) | added (new file): API client registration, tenant URLs, ISU and security group | | `/auth/xero` | [/toolkits/xero](https://docs.composio.dev/toolkits/xero) | added: developer portal app, scopes | | `/auth/youtube` | [/toolkits/youtube](https://docs.composio.dev/toolkits/youtube) | added: Cloud project, API enablement, consent screen and test users, Web client and redirect URI, scopes, publishing and verification; YouTube Data API v3, channel choice | | `/auth/zendesk` | [/toolkits/zendesk](https://docs.composio.dev/toolkits/zendesk) | added: OAuth client, subdomain, scopes | | `/auth/zoho` | [/toolkits/zoho](https://docs.composio.dev/toolkits/zoho) | added: Zoho API console server-based client, redirect URI, data center field, scopes | | `/auth/zoho_bigin` | [/toolkits/zoho_bigin](https://docs.composio.dev/toolkits/zoho_bigin) | added (new file): Zoho API console server-based client, redirect URI, data center field, scopes | | `/auth/zoho_books` | [/toolkits/zoho_books](https://docs.composio.dev/toolkits/zoho_books) | added (new file): Zoho API console server-based client, redirect URI, data center field, scopes | | `/auth/zoho_desk` | [/toolkits/zoho_desk](https://docs.composio.dev/toolkits/zoho_desk) | added (new file): Zoho API console server-based client, redirect URI, data center field, scopes | | `/auth/zoho_inventory` | [/toolkits/zoho_inventory](https://docs.composio.dev/toolkits/zoho_inventory) | added (new file): Zoho API console server-based client, redirect URI, data center field, scopes; Organization ID | | `/auth/zoho_invoice` | [/toolkits/zoho_invoice](https://docs.composio.dev/toolkits/zoho_invoice) | added (new file): Zoho API console server-based client, redirect URI, data center field, scopes | | `/auth/zoho_mail` | [/toolkits/zoho_mail](https://docs.composio.dev/toolkits/zoho_mail) | added: Zoho API console server-based client, redirect URI, data center field, scopes; merged region item | | `/auth/zoom` | [/toolkits/zoom](https://docs.composio.dev/toolkits/zoom) | added: General app, redirect URI, granular scopes | ## ELI5 The marketing site had how-to pages for connecting each app to Composio, and those pages are going away. This copies the useful steps and screenshots onto the matching docs page for each app, and fixes the places where the old steps were out of date. --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Brendan O'Leary committed Nov 19, 2026 at 02:50 UTC 65f5b4719bdd86deb8cc269d862ba21e8766489a
716 files changed +5479 -164
docs/components/toolkits/faq-section.tsx
+31 -21
@@ -1,7 +1,6 @@
1 'use client';
2
3 import { HelpCircle } from 'lucide-react';
4 -import { Accordion, Accordions } from '@/mdx-components';
4 import { Tabs, Tab } from 'fumadocs-ui/components/tabs';
5 import type { FaqItem } from '@/lib/toolkit-faq';
6
@@ -20,28 +19,39 @@ export function FaqSection({ faq }: FaqSectionProps) {
19 <HelpCircle className="h-4 w-4" />
20 Frequently Asked Questions
21 </h2>
23 - <Accordions type="single">
22 + <div className="divide-y divide-fd-border overflow-hidden rounded-lg border bg-fd-card">
23 {faq.map((item) => (
25 - <Accordion key={item.question} title={item.question}>
26 - {item.answer.map((part, index) => part.type === 'html' ? (
27 - <div key={index}
28 - className="prose prose-sm prose-fd max-w-none text-fd-muted-foreground"
29 - dangerouslySetInnerHTML={{ __html: part.html }}
30 - />
31 - ) : (
32 - <Tabs key={index} groupId="language" items={part.tabs.map((tab) => tab.value)} persist>
33 - {part.tabs.map((tab) => (
34 - <Tab key={tab.value} value={tab.value}>
35 - <div className="prose prose-sm prose-fd max-w-none overflow-x-auto"
36 - dangerouslySetInnerHTML={{ __html: tab.html }}
37 - />
38 - </Tab>
39 - ))}
40 - </Tabs>
41 - ))}
42 - </Accordion>
24 + <details key={item.question}>
25 + <summary
26 + className="cursor-pointer px-3 py-2.5 text-sm font-medium focus-visible:outline focus-visible:outline-2 focus-visible:outline-fd-ring"
27 + >
28 + {item.question}
29 + </summary>
30 + {/* Target the answer so native fragment navigation opens its details. */}
31 + <div
32 + id={item.question.toLowerCase().replace(/[^a-z0-9]+/g, '-').replace(/(^-|-$)/g, '')}
33 + className="scroll-m-24 px-4 pb-2"
34 + >
35 + {item.answer.map((part, index) => part.type === 'html' ? (
36 + <div key={index}
37 + className="prose prose-sm prose-fd max-w-none text-fd-muted-foreground"
38 + dangerouslySetInnerHTML={{ __html: part.html }}
39 + />
40 + ) : (
41 + <Tabs key={index} groupId="language" items={part.tabs.map((tab) => tab.value)} persist>
42 + {part.tabs.map((tab) => (
43 + <Tab key={tab.value} value={tab.value}>
44 + <div className="prose prose-sm prose-fd max-w-none overflow-x-auto"
45 + dangerouslySetInnerHTML={{ __html: tab.html }}
46 + />
47 + </Tab>
48 + ))}
49 + </Tabs>
50 + ))}
51 + </div>
52 + </details>
53 ))}
44 - </Accordions>
54 + </div>
55 </div>
56 );
57 }
docs/content/docs/authentication/custom-app-vs-managed-app.mdx
+1 -1
@@ -69,7 +69,7 @@ For OAuth toolkits, register an app in the provider's developer portal and add t
69
70 For API key, bearer token, basic auth, or other auth schemes, collect the credential fields the toolkit requires and enter them in the dashboard.
71
72 -Step-by-step OAuth guides: [Google](https://composio.dev/auth/googleapps) | [GitHub](https://composio.dev/auth/github) | [Slack](https://composio.dev/auth/slack) | [HubSpot](https://composio.dev/auth/hubspot) | [All toolkits](https://composio.dev/auth)
72 +Each toolkit page has setup steps for its provider: [Google](/toolkits/googlesuper) | [GitHub](/toolkits/github) | [Slack](/toolkits/slack) | [HubSpot](/toolkits/hubspot) | [All toolkits](/toolkits)
73 </Step>
74
75 <Step>
docs/content/toolkits/faq/airtable.md
+28 -1
@@ -1,3 +1,30 @@
1 ## How do I set up custom OAuth credentials for Airtable?
2
3 -For a step-by-step guide on creating and configuring your own Airtable OAuth credentials with Composio, see [How to create OAuth credentials for Airtable](https://composio.dev/auth/airtable).
3 +Use your own Airtable OAuth integration when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Airtable OAuth integration
6 +
7 +1. Sign in to Airtable and open the [Airtable developer hub](https://airtable.com/developers/web/api).
8 +2. In the left menu, under **Guide**, click **OAuth integrations**, then click **+ New OAuth Integration** in the top-right corner.
9 +
10 + ![Airtable Builder Hub OAuth integrations page with the register button](/images/toolkits/airtable/oauth-integrations-list.webp)
11 +3. Enter a name and description. The website field is optional. Users see these details when they authorize your app.
12 +4. Under **Redirect URLs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config, with `https` and no trailing slash.
13 +5. Save the integration and copy the **Client ID** and **Client Secret**.
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Airtable**.
18 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
19 +
20 + ![Use your own developer credentials toggle turned on in the auth config form](/images/toolkits/shared/SzVC6OY8pTVVwlrOjHLuhuv0u3Y.webp)
21 +3. Paste the **Client ID** and **Client Secret**, then click **Create Airtable Auth Config**.
22 +4. Click **Connect Account**. On the Airtable consent screen, select the bases or workspaces to grant and click **Approve**. Confirm the account shows as **Active**.
23 +
24 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
25 +
26 +### Scopes
27 +
28 +The default auth config requests `data.records:read`, `data.records:write`, `data.recordComments:read`, `data.recordComments:write`, `schema.bases:read`, `schema.bases:write`, and `user.email:read`. Change the **Scopes** field on the auth config if your integration needs fewer.
29 +
30 +If the connection fails, check that the redirect URL in Airtable matches the auth config's `oauth_redirect_uri` exactly.
docs/content/toolkits/faq/apollo.md
+33
@@ -1,3 +1,36 @@
1 +## How do I connect Apollo with an API key?
2 +
3 +Apollo uses API key authentication. There's no OAuth flow and no scopes; Apollo enforces access based on your plan and the key's settings.
4 +
5 +### Create the Apollo API key
6 +
7 +1. Sign in to [Apollo](https://app.apollo.io/) with an account that has admin access.
8 +2. Go to **Admin Settings** > **Integrations**, then open **API** > **API Keys**.
9 +
10 + ![Apollo Admin Settings menu with Integrations](/images/toolkits/apollo/admin-settings-menu.webp)
11 +
12 + ![Apollo Integrations settings with the API integration](/images/toolkits/apollo/integrations-api.webp)
13 +3. Click **Create a new key** and give it a name.
14 +4. Turn on **Set as master key** so the key can reach every endpoint Composio's tools call.
15 +5. Copy the key and store it somewhere safe. You may not be able to view it again.
16 +
17 +### Create the auth config in Composio
18 +
19 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Apollo**.
20 +
21 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
22 +
23 + ![Create Auth Config drawer searching for Apollo](/images/toolkits/apollo/select-apollo.webp)
24 +2. Make sure the authentication type is **API Key**, then create the auth config.
25 +
26 + ![Apollo auth config form with API Key as the authentication method](/images/toolkits/apollo/auth-config-api-key.webp)
27 +3. Click **Connect Account**, paste your Apollo API key, and click **Connect Account**.
28 +
29 + ![Composio connection form asking for the Apollo API key](/images/toolkits/apollo/paste-api-key.webp)
30 +4. Confirm the account shows as **Active**. To test it, run a search tool such as `APOLLO_ORGANIZATION_SEARCH` from the playground.
31 +
32 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
33 +
34 ## Why can Apollo search or enrichment tools return HTTP 403?
35
36 Apollo API keys can be limited to specific endpoint groups. A tool can return HTTP 403 or `Forbidden` when the underlying Apollo API rejects the key for that operation, even if the same key works for other Apollo tools.
docs/content/toolkits/faq/asana.md
+29 -1
@@ -1,3 +1,31 @@
1 ## How do I set up custom OAuth credentials for Asana?
2
3 -For a step-by-step guide on creating and configuring your own Asana OAuth credentials with Composio, see [How to create OAuth credentials for Asana](https://composio.dev/auth/asana).
3 +Use your own Asana app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Asana app
6 +
7 +1. Sign in to Asana and open the [Asana developer console](https://app.asana.com/0/my-apps).
8 +2. Click **+ New App** and enter an app name, such as `Composio Integration`. The app website is optional.
9 +
10 + ![Asana Create new app dialog with the app name filled in](/images/toolkits/asana/create-app.webp)
11 +3. In the app's OAuth settings, add the redirect URL `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
12 +4. Save the app and copy the **Client ID** and **Client Secret**.
13 +
14 + ![Asana app Basic information page showing the Client ID and Client secret fields](/images/toolkits/asana/client-credentials.webp)
15 +
16 +### Create the auth config in Composio
17 +
18 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Asana**.
19 +
20 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/asana/create-auth-config.webp)
21 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
22 +3. Paste the **Client ID** and **Client Secret**, add any scopes you need, then click **Create Asana Auth Config**.
23 +4. Click **Connect Account**, sign in to Asana, and approve access to your workspace. Confirm the account shows as **Active**.
24 +
25 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
26 +
27 +### Scopes
28 +
29 +The default auth config doesn't request specific scopes. To request granular scopes such as `tasks:read`, `projects:read`, or `workspaces:read`, enable them in the Asana app's OAuth settings and add the same values to the auth config's **Scopes** field. Request only what your integration uses.
30 +
31 +![Asana app OAuth settings with scope checkboxes](/images/toolkits/asana/oauth-scopes.webp)
docs/content/toolkits/faq/azure_monitor_activity_log.md new
+81
@@ -0,0 +1,81 @@
1 +## How do I set up custom OAuth credentials for Azure Monitor Activity Log?
2 +
3 +Azure Monitor Activity Log has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). The account you connect must belong to a tenant the app allows.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Azure Service Management** under **Microsoft APIs**, and choose **Delegated permissions**. Select `user_impersonation`, then click **Add permissions**. This permission lets the app act with the signed-in user's existing Azure rights. It doesn't create a log-reading role or narrow those rights.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/azure_monitor_activity_log/add-a-permission.webp)
25 +
26 + ![Request API permissions panel with Azure Service Management under Microsoft APIs](/images/toolkits/azure_monitor_activity_log/azure-service-management-api.webp)
27 +
28 + ![Azure Service Management delegated permissions with user_impersonation selected](/images/toolkits/azure_monitor_activity_log/user-impersonation-permission.webp)
29 +
30 + ![Configured user_impersonation permission details for Azure Service Management](/images/toolkits/azure_monitor_activity_log/user-impersonation-details.webp)
31 +
32 +8. Keep **Allow public client flows** disabled on the **Authentication** page. This is a confidential Web client.
33 +9. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
34 +
35 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
36 +
37 +### Create the auth config in Composio
38 +
39 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Azure Monitor Activity Log**. Enter a config name and click **Next**.
40 +
41 + ![Composio Auth Configs page with the Create button](/images/toolkits/azure_monitor_activity_log/composio-auth-configs.webp)
42 +
43 + ![Create Auth Config dialog with Azure Monitor Activity Log selected](/images/toolkits/azure_monitor_activity_log/composio-toolkit-picker.webp)
44 +
45 + ![Auth config name field with the Next button](/images/toolkits/azure_monitor_activity_log/composio-config-name.webp)
46 +
47 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
48 +
49 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/azure_monitor_activity_log/composio-oauth-credentials.webp)
50 +
51 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
52 +
53 + ![Composio auth config with the v1 redirect URI and the user_impersonation and offline_access scopes](/images/toolkits/azure_monitor_activity_log/composio-scopes.webp)
54 +
55 +4. Open the auth config and click **Connect Account**. Enter the **Azure Subscription ID** (`generic_id`) and click **Connect Account**. Sign in with a Microsoft account that can read that subscription's Activity Log and accept the consent prompt. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
56 +
57 + ![Azure Monitor auth config page with the Connect Account button](/images/toolkits/azure_monitor_activity_log/composio-connect-account.webp)
58 +
59 + ![Composio connection form with the Azure Subscription ID field censored](/images/toolkits/azure_monitor_activity_log/subscription-id-field.webp)
60 +
61 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/WyfUBqcv3KROYF9jYs3rIFcs.webp)
62 +
63 + ![Microsoft consent prompt for Azure Resource Manager access with organization consent unchecked](/images/toolkits/azure_monitor_activity_log/microsoft-consent.webp)
64 +
65 + ![Composio page confirming the Azure Monitor Activity Log connection](/images/toolkits/azure_monitor_activity_log/connection-success.webp)
66 +
67 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
68 +
69 + ![Connected Accounts tab with the account showing Active](/images/toolkits/azure_monitor_activity_log/connected-account-active.webp)
70 +
71 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
72 +
73 +### Scopes
74 +
75 +The default auth config requests `https://management.azure.com/user_impersonation` (Azure Resource Manager) and `offline_access` (refresh tokens). Azure RBAC still decides which subscription logs the account can read. See Microsoft's [Activity Logs - List](https://learn.microsoft.com/en-us/rest/api/monitor/activity-logs/list?view=rest-monitor-2015-04-01) reference.
76 +
77 +### Find the subscription ID
78 +
79 +In the Azure portal, open **Subscriptions**, select the subscription whose Activity Log you want, and copy **Subscription ID** from **Overview**. The signed-in user needs the `Microsoft.Insights/eventtypes/values/read` permission on that subscription, for example through the **Monitoring Reader** role.
80 +
81 +![Azure Subscriptions list with the subscription ID and billing details censored](/images/toolkits/azure_monitor_activity_log/azure-subscriptions.webp)
docs/content/toolkits/faq/bitbucket.md new
+63
@@ -0,0 +1,63 @@
1 +## How do I set up custom OAuth credentials for Bitbucket?
2 +
3 +Use your own Bitbucket OAuth client when you want the consent screen to show your app name and to control which permissions the token gets.
4 +
5 +### Create the Bitbucket OAuth client
6 +
7 +1. Sign in to [Bitbucket Cloud](https://bitbucket.org/) and open the workspace you want to use. From the settings menu, select **Workspace settings**.
8 +
9 + ![Bitbucket Workspace settings page](/images/toolkits/bitbucket/workspace-settings.webp)
10 +
11 +2. Expand **Apps and features** and select **OAuth clients** (older screens call these **OAuth consumers**). Click **Create OAuth client**.
12 +
13 + ![Bitbucket Workspace settings sidebar with Apps and features expanded to OAuth clients](/images/toolkits/bitbucket/oauth-clients-nav.webp)
14 +
15 + ![Bitbucket OAuth clients page with the Create OAuth client button](/images/toolkits/bitbucket/create-oauth-client.webp)
16 +
17 +3. On **Details**, enter a name and description. Fill in the optional application URLs if your deployment needs them.
18 +
19 + ![Bitbucket Create OAuth client Details tab with name, description, and optional URLs](/images/toolkits/bitbucket/oauth-client-details.webp)
20 +
21 +4. On **Authorisation**, enable **Authorisation code** and set the callback URL to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field. Bitbucket enables refresh tokens along with the authorization code grant.
22 +
23 + ![Bitbucket Authorisation tab with Authorisation code enabled and the Composio callback URL](/images/toolkits/bitbucket/authorisation-callback.webp)
24 +
25 +5. On **Scopes**, select the permissions your integration needs and click **Save**.
26 +
27 + ![Bitbucket Scopes tab with permission checkboxes for each resource](/images/toolkits/bitbucket/scopes.webp)
28 +
29 +6. Copy the generated **Client ID** and **Client secret**. Keep the secret out of frontend code.
30 +
31 + ![Bitbucket OAuth client created dialog with the Client ID and Secret (redacted)](/images/toolkits/bitbucket/client-credentials.webp)
32 +
33 +### Create the auth config in Composio
34 +
35 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-bitbucket), go to **Auth Configs** → **Create** and select **Bitbucket**.
36 +
37 + ![Composio Auth Configs page with the Create button](/images/toolkits/bitbucket/auth-configs.webp)
38 +
39 + ![Composio Create Auth Config dialog with Bitbucket selected](/images/toolkits/bitbucket/select-toolkit.webp)
40 +
41 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client secret. Leave the redirect URI as the value you registered in Bitbucket.
42 +
43 + ![Bitbucket auth config with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/bitbucket/own-credentials.webp)
44 +
45 + ![Bitbucket auth config credential fields with the Composio redirect URI](/images/toolkits/bitbucket/redirect-uri.webp)
46 +
47 +3. Click **Create Auth Config**, then click **Connect Account**.
48 +
49 + ![Bitbucket auth config page with the Connect Account button](/images/toolkits/bitbucket/connect-account.webp)
50 +
51 +4. Sign in to Bitbucket, review the app name and permissions, and approve access. Check that the account shows **Active** on the auth config's **Connected Accounts** tab.
52 +
53 + ![Atlassian consent screen listing the permissions the Bitbucket OAuth client requests](/images/toolkits/bitbucket/consent-screen.webp)
54 +
55 + ![Bitbucket auth config Connected Accounts tab with the account Active](/images/toolkits/bitbucket/account-active.webp)
56 +
57 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
58 +
59 +### Scopes
60 +
61 +Bitbucket assigns permissions on the OAuth client, not per request. Requesting fewer scopes in the auth config doesn't reduce what the token can do, so change the client's **Scopes** when you need less access. See Atlassian's [OAuth on Bitbucket Cloud](https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/) guide.
62 +
63 +For reference, `account` covers account and profile access, `repository` covers repository reads, and `pullrequest` covers pull request reads. Write, admin, and delete operations need the matching higher permission. The default auth config requests write or admin access across account, repositories, pull requests, issues, projects, snippets, pipelines, runners, webhooks, and wiki, so select those on the client if you want every tool to work.
docs/content/toolkits/faq/calendly.md
+33
@@ -1,3 +1,36 @@
1 +## How do I set up custom OAuth credentials for Calendly?
2 +
3 +Use your own Calendly OAuth app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Calendly app
6 +
7 +1. Sign in to the [Calendly developer portal](https://developer.calendly.com/) and click **My Apps**.
8 +
9 + ![Calendly developer portal My Apps page with the Create new app button](/images/toolkits/calendly/my-apps.webp)
10 +2. Click **Create New App** and fill in the form:
11 + - **Name of app**: for example, `Composio-Calendly`.
12 + - **Kind of app**: **Web**.
13 + - **Environment type**: **Sandbox** for development and testing. Switch to **Production** when you go live.
14 + - **Redirect URI**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must use `https`, have no trailing slash, and exactly match the `oauth_redirect_uri` field in your Composio auth config.
15 +3. Save the app and copy the **Client ID** and **Client Secret**.
16 +
17 + ![Calendly app created page showing the Client ID and Client secret](/images/toolkits/calendly/client-credentials.webp)
18 +
19 +### Create the auth config in Composio
20 +
21 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Calendly**.
22 +
23 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
24 +
25 + ![Create Auth Config drawer searching for Calendly](/images/toolkits/calendly/select-calendly.webp)
26 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
27 +
28 + ![Calendly auth config form with OAuth2 selected and Use your own developer credentials turned on](/images/toolkits/calendly/auth-config-oauth2.webp)
29 +3. Paste the **Client ID** and **Client Secret**, then click **Create Calendly Auth Config**.
30 +4. Click **Connect Account**, approve access in Calendly, and confirm the account shows as **Active**.
31 +
32 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
33 +
34 ## Why can't I configure individual scopes for Calendly?
35
36 Calendly does not let end users selectively approve individual scopes during the OAuth connection flow. The scopes configured in your Calendly OAuth app are the scopes that will be requested during authorization, and the resulting access token will include that configured permission set.
docs/content/toolkits/faq/canva.md
+33 -1
@@ -1,3 +1,35 @@
1 ## How do I set up custom OAuth credentials for Canva?
2
3 -For a step-by-step guide on creating and configuring your own Canva OAuth credentials with Composio, see [How to create OAuth credentials for Canva](https://composio.dev/auth/canva).
3 +Use your own Canva integration when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Canva integration
6 +
7 +1. Sign in to the [Canva developer portal](https://www.canva.com/developers/), open [Your integrations](https://www.canva.com/developers/integrations), and click **Create an integration**.
8 +
9 + ![Canva developer portal Your integrations page with the Create an integration button](/images/toolkits/canva/your-integrations.webp)
10 +2. Choose the integration type:
11 + - **Public**: anyone on Canva can use it, but Canva must review and approve it first.
12 + - **Private**: only your team can use it. Requires a Canva Enterprise plan.
13 +
14 + ![Canva dialog to choose a Public or Private integration](/images/toolkits/canva/integration-type.webp)
15 +3. Open the integration. On the **Configuration** tab, under **Credentials**, copy the **Client ID** and **Client Secret**.
16 +
17 + ![Canva integration Configuration tab with the Credentials section](/images/toolkits/canva/credentials.webp)
18 +4. On the **Authentication** tab, under **Authorized redirects**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
19 +5. On the **Scopes** tab, enable the scopes your auth config will request (see below).
20 +6. For a public integration, submit it for review.
21 +
22 + ![Canva integration Submit for review checklist](/images/toolkits/canva/submit-for-review.webp)
23 +
24 +### Create the auth config in Composio
25 +
26 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Canva**.
27 +2. Keep the authentication type as **OAuth2** and choose to use your own developer credentials.
28 +3. Paste the **Client ID** and **Client Secret**, then click **Create Canva Auth Config**.
29 +4. Click **Connect Account**, approve access in Canva, and confirm the account shows as **Active**.
30 +
31 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
32 +
33 +### Scopes
34 +
35 +The default auth config requests `asset:read`, `asset:write`, `brandtemplate:content:read`, `brandtemplate:meta:read`, `comment:read`, `comment:write`, `design:content:read`, `design:content:write`, `design:meta:read`, `folder:read`, `folder:write`, `folder:permission:write`, and `profile:read`. Edit the **Scopes** field on the auth config to request fewer, and keep it in line with the scopes enabled on the Canva integration.
docs/content/toolkits/faq/confluence.md
+40 -1
@@ -1,3 +1,42 @@
1 ## How do I set up custom OAuth credentials for Confluence?
2
3 -For a step-by-step guide on creating and configuring your own Confluence OAuth credentials with Composio, see [How to create OAuth credentials for Confluence](https://composio.dev/auth/confluence).
3 +Use your own Atlassian OAuth 2.0 (3LO) app when you want the consent screen to show your app name and to control which scopes it can grant.
4 +
5 +### Create the Atlassian app
6 +
7 +1. Sign in to the [Atlassian developer console](https://developer.atlassian.com/console/myapps) (create a developer account if you don't have one).
8 +2. Click **Create** → **OAuth 2.0 integration**, name the app, and click **Create**.
9 +
10 + ![Atlassian developer console form to create a new OAuth 2.0 (3LO) integration](/images/toolkits/confluence/create-oauth-integration.webp)
11 +
12 +3. Open **Authorization** in the sidebar and click **Configure** next to OAuth 2.0 (3LO). Set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add` and click **Save changes**. It must exactly match the auth config's `oauth_redirect_uri` field.
13 +
14 + ![Atlassian OAuth 2.0 (3LO) Callback URL set to the Composio redirect URI](/images/toolkits/shared/kvxWqV89dZHkBHkJJGy5XQdhGko.webp)
15 +
16 +4. Open **Permissions**. Click **Add** next to the **Confluence API**, then **Configure**, and add every classic or granular scope your auth config will request (see below). Add the **User Identity API** too if you need user profile scopes. Click **Save**.
17 +
18 + ![Atlassian app Permissions page listing APIs, including the Confluence API](/images/toolkits/confluence/permissions-apis.webp)
19 +
20 + ![Confluence API scope page with Classic scopes, Granular scopes, and Edit Scopes](/images/toolkits/confluence/api-scopes.webp)
21 +
22 +5. Open **Distribution** and set the status to **Sharing** if users outside your own Atlassian account will connect. Atlassian asks for a vendor name, privacy policy URL, and a personal data declaration.
23 +6. Open **Settings** and copy the **Client ID** and **Secret** under **Authentication details**.
24 +
25 +### Create the auth config in Composio
26 +
27 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-confluence), go to **Auth Configs** → **Create** and select **Confluence**.
28 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Secret.
29 +
30 +3. Remove any scopes you didn't add on the app's **Permissions** tab, then click **Create Auth Config**.
31 +4. Click **Connect Account** and enter your site's **subdomain**: the part before `.atlassian.net` in your browser's address bar. For `https://acme.atlassian.net`, enter `acme`.
32 +5. Approve the consent screen and check that the account shows **Active**.
33 +
34 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
35 +
36 +### Scopes
37 +
38 +The default auth config requests granular Confluence scopes for pages, blog posts, content, comments, whiteboards, inline tasks, tasks, content restrictions and metadata, space details, and the audit log (for example `read:page:confluence`, `write:page:confluence`, `read:comment:confluence`, `read:space-details:confluence`), plus `offline_access`. The full list is in the auth config's scope picker. See Atlassian's [Confluence scopes reference](https://developer.atlassian.com/cloud/confluence/scopes-for-oauth-2-3LO-and-forge-apps/).
39 +
40 +Every scope the auth config requests, apart from `offline_access`, must also be added on the app's **Permissions** tab. If one is missing, the connection fails with a "Something went wrong" error. Keep `offline_access` in the auth config's scopes: Atlassian only issues a refresh token when it's requested, and without one the connection stops working when the access token expires.
41 +
42 +![Atlassian "Something went wrong" page listing Confluence scopes that haven't been added to the app](/images/toolkits/confluence/missing-scopes-error.webp)
docs/content/toolkits/faq/daytona.md new
+18
@@ -0,0 +1,18 @@
1 +## How do I connect Daytona with an API key?
2 +
3 +Use an API key when you want to connect with your own Daytona credentials. Daytona's OAuth runs through Auth0 without self-serve client credentials, so you can't bring your own OAuth app; the alternative is Composio-managed OAuth.
4 +
5 +### Create the Daytona API key
6 +
7 +1. Sign in and open the [Daytona API keys page](https://app.daytona.io/dashboard/keys).
8 +2. Create a new key. Give it a name and set permissions or an expiry if the form offers them.
9 +3. Copy the key and store it somewhere safe. Daytona usually shows it only once.
10 +
11 +### Create the auth config in Composio
12 +
13 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Daytona**.
14 +2. Choose the **API Key** authentication type and create the auth config.
15 +3. Click **Connect Account** and paste your API key. If the key has access to more than one Daytona organization, also enter the organization ID, found on the [Daytona settings page](https://app.daytona.io/dashboard/settings).
16 +4. Confirm the account shows as **Active**.
17 +
18 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
docs/content/toolkits/faq/docusign.md
+50 -1
@@ -1,3 +1,52 @@
1 ## How do I create my own DocuSign OAuth app?
2
3 -Create and configure your own DocuSign OAuth app when you want to use your own DocuSign credentials with Composio. For the setup steps, see [How to create OAuth credentials for DocuSign](https://composio.dev/auth/docusign).
3 +Create your own DocuSign app (Integration Key) when you want users to see your app's name on the consent screen and control the credentials yourself. DocuSign calls the client ID an **Integration Key**.
4 +
5 +You need a DocuSign account with the Admin role. Developer accounts are free at [developers.docusign.com](https://developers.docusign.com/) and use `account-d.docusign.com`; production uses `account.docusign.com`.
6 +
7 +### Create the DocuSign app
8 +
9 +1. Sign in to DocuSign and click **Admin** in the top navigation. If you don't see it, ask your account owner for the Admin role.
10 +
11 + ![DocuSign home page with Admin in the top navigation](/images/toolkits/docusign/admin-nav.webp)
12 +2. In the left sidebar, under **Integrations**, click **Apps and Keys**. (Not **App Center**, which lists third-party apps.)
13 +
14 + ![DocuSign Admin sidebar with Apps and Keys under Integrations](/images/toolkits/docusign/apps-and-keys-sidebar.webp)
15 +3. Click **Add App and Integration Key**, enter an app name such as `composio-docusign-connector`, and click **Create App**. Users see this name on the consent screen.
16 +
17 + ![DocuSign Add Integration Key dialog with the app name](/images/toolkits/docusign/create-app.webp)
18 +4. Under **General Info**, copy the **Integration Key**. This is your client ID.
19 +5. Under **Authentication** > **User Application**, answer **Yes** to "Is your application able to securely store a client secret?". This sets the method to **Authorization Code Grant**. You can leave **Require Proof Key for Code Exchange (PKCE)** unchecked.
20 +
21 + ![DocuSign User Application settings with Yes selected and Authorization Code Grant](/images/toolkits/docusign/user-application.webp)
22 +6. Under **Secret Keys**, click **+ Add Secret Key** and copy the secret right away. DocuSign masks it once you leave the page. If you lose it, generate a new one and update your auth config.
23 +
24 + ![DocuSign Secret Keys section with a generated secret key](/images/toolkits/docusign/secret-key.webp)
25 +7. Under **Additional Settings** > **Redirect URIs**, click **+ Add URI** and enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
26 +
27 + ![DocuSign Additional settings with the Composio redirect URI](/images/toolkits/docusign/redirect-uri.webp)
28 +8. Leave the CORS settings at their defaults and click **Save**. The app shows **Environment: Development** and **Go Live Status: Ready to Submit**, which is enough for the developer environment.
29 +
30 + ![DocuSign CORS settings with the Save button](/images/toolkits/docusign/cors-save.webp)
31 +
32 +### Create the auth config in Composio
33 +
34 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **DocuSign**.
35 +2. Paste the Integration Key as the **Client ID** and the secret key as the **Client Secret**.
36 +3. Set the authorization URL field (`full`) to match where your app is registered: `https://account-d.docusign.com` for the developer environment, or `https://account.docusign.com` (the default) for production.
37 +
38 + ![DocuSign auth config Authorization URL set to the developer environment](/images/toolkits/docusign/authorization-url.webp)
39 +4. Create the auth config, click **Connect Account**, and click **Allow Access** on the DocuSign consent screen. The screen notes that the app isn't provided by DocuSign; that's expected for your own app.
40 +
41 + ![DocuSign consent screen with the Allow Access button](/images/toolkits/docusign/consent-screen.webp)
42 +5. Confirm the account shows as **Active** under the auth config's connected accounts.
43 +
44 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
45 +
46 +### Scopes
47 +
48 +The default auth config requests `signature` and `impersonation`.
49 +
50 +### Going to production
51 +
52 +Keep development and production separate. When you go live, promote the DocuSign app to production and create a second auth config with your production Integration Key and `https://account.docusign.com`. If you rotate credentials or change scopes, update both DocuSign and Composio, then reconnect affected accounts.
docs/content/toolkits/faq/dropbox.md
+40 -1
@@ -1,3 +1,42 @@
1 ## How do I set up custom OAuth credentials for Dropbox?
2
3 -For a step-by-step guide on creating and configuring your own Dropbox OAuth credentials with Composio, see [How to create OAuth credentials for Dropbox](https://composio.dev/auth/dropbox).
3 +Use your own Dropbox app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Dropbox app
6 +
7 +1. Sign in to Dropbox and open the [Dropbox App Console](https://www.dropbox.com/developers/apps).
8 +2. Click **Create app** and choose **Scoped access**.
9 +
10 + ![Dropbox App Console My apps page with the Create app button](/images/toolkits/dropbox/create-app.webp)
11 +
12 + ![Dropbox create app form with Scoped access and the access type options](/images/toolkits/dropbox/scoped-access.webp)
13 +3. Choose the access type: **App folder** (one dedicated folder) or **Full Dropbox** (all files).
14 +4. Enter an app name, such as `Composio-Dropbox`, and click **Create app**.
15 +
16 + ![Dropbox create app form with the app name and Create app button](/images/toolkits/dropbox/name-app.webp)
17 +5. On the **Settings** tab, copy the **App key** (client ID) and **App secret** (client secret).
18 +6. In the **OAuth 2** section, under **Redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config, or Dropbox rejects the OAuth flow.
19 +7. On the **Permissions** tab, check the scopes your auth config will request (see below) and save.
20 +
21 + ![Dropbox app Permissions tab with scope checkboxes](/images/toolkits/dropbox/permissions.webp)
22 +
23 +### Create the auth config in Composio
24 +
25 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Dropbox**.
26 +
27 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
28 +
29 + ![Create Auth Config drawer searching for Dropbox](/images/toolkits/dropbox/select-dropbox.webp)
30 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
31 +
32 + ![Dropbox auth config form with OAuth2 selected and Use your own developer credentials turned on](/images/toolkits/dropbox/auth-config-oauth2.webp)
33 +3. Paste the **App key** as the **Client ID** and the **App secret** as the **Client Secret**, then click **Create Dropbox Auth Config**.
34 +
35 + ![Dropbox auth config form with Client id and Client secret fields](/images/toolkits/dropbox/auth-config-credentials.webp)
36 +4. Click **Connect Account**, approve access in Dropbox, and confirm the account shows as **Active**.
37 +
38 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
39 +
40 +### Scopes
41 +
42 +The default auth config requests `openid`, `email`, `profile`, and the read and write scopes for `account_info`, `files.metadata`, `files.content`, `file_requests`, `sharing`, and `contacts` (for example `files.content.read` and `files.content.write`). Enable the same permissions on the Dropbox app, or trim the auth config's **Scopes** field to the ones you enabled.
docs/content/toolkits/faq/dynamics365.md new
+76
@@ -0,0 +1,76 @@
1 +## How do I set up custom OAuth credentials for Dynamics 365?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Dynamics 365 requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). Dynamics 365 requires a work or school account.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Dynamics CRM**, and choose **Delegated permissions**. Select `user_impersonation`, then click **Add permissions**. The signed-in user's Dynamics security roles still decide which records they can access.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
25 +
26 + ![Request API permissions panel with Dynamics CRM under Microsoft APIs](/images/toolkits/dynamics365/dynamics-crm-api.webp)
27 +
28 + ![Dynamics CRM delegated permissions with user_impersonation selected](/images/toolkits/dynamics365/user-impersonation-permission.webp)
29 +
30 + ![Configured permissions list with the Dynamics CRM user_impersonation permission](/images/toolkits/dynamics365/configured-permissions.webp)
31 +
32 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
33 +
34 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
35 +
36 +### Create the auth config in Composio
37 +
38 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Dynamics 365**. Enter a config name and click **Next**.
39 +
40 + ![Composio Auth Configs page with the Create button](/images/toolkits/dynamics365/composio-auth-configs.webp)
41 +
42 + ![Create Auth Config dialog with Dynamics 365 selected](/images/toolkits/dynamics365/composio-toolkit-picker.webp)
43 +
44 + ![Auth config name field with the Next button](/images/toolkits/dynamics365/composio-config-name.webp)
45 +
46 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
47 +
48 + ![Composio auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/dynamics365/composio-own-credentials.webp)
49 +
50 +3. Under **Scopes**, keep `offline_access` and use **Add scope** to add the environment-specific Dynamics scope, which uses your full environment URL (for example, `https://yourorg.crm.dynamics.com/user_impersonation`). Click **Create Auth Config**.
51 +
52 + ![Composio scopes list with offline_access selected and a censored environment-specific scope added](/images/toolkits/dynamics365/composio-scopes.webp)
53 +
54 +4. Open the auth config and click **Connect Account**. Enter the organization name (`subdomain`) and environment host (`region`) from your Dynamics URL: for `https://yourorg.crm8.dynamics.com`, enter `yourorg` and `crm8.dynamics.com`. Sign in with a work or school account that has access to the environment, review the **Access Common Data Service as you** permission, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
55 +
56 + ![Composio connection form with the Dynamics 365 organization name and environment host fields](/images/toolkits/dynamics365/connection-fields.webp)
57 +
58 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/1dBnBBEYr17c671yWVLvqnS4k.webp)
59 +
60 + ![Microsoft consent prompt with Access Common Data Service as you and organization consent unchecked](/images/toolkits/dynamics365/microsoft-consent.webp)
61 +
62 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
63 +
64 + ![Connected Accounts tab with the Dynamics account showing Active](/images/toolkits/dynamics365/connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default auth config requests only `offline_access`, so add the environment's `user_impersonation` scope yourself. See Microsoft's [OAuth with Dataverse](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/authenticate-oauth) reference.
71 +
72 +### Connection fields
73 +
74 +- `subdomain` (required): the organization name from your environment URL, such as `myorg` in `https://myorg.crm8.dynamics.com`.
75 +- `region`: the host suffix, such as `crm8.dynamics.com`. Keep `crm.dynamics.com` for the default public cloud. Use `crm.microsoftdynamics.us` for GCC High or `crm.dynamics.cn` for China.
76 +- The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
docs/content/toolkits/faq/excel.md new
+77
@@ -0,0 +1,77 @@
1 +## How do I set up custom OAuth credentials for Excel?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Excel requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +
11 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/shared/1iIDmPCxFpXJP7zt73rUtnOLkxc.webp)
12 +
13 +4. On the app's **Overview** page, copy the **Application (client) ID**.
14 +
15 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
16 +
17 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
18 +
19 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
20 +
21 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
22 +
23 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
24 +
25 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Files.ReadWrite`, `Sites.ReadWrite.All`, `offline_access`, and `User.Read`, then click **Add permissions**. If you reuse an existing app, keep the permissions its other integrations rely on.
26 +
27 + ![API permissions page with the Add a permission button](/images/toolkits/excel/add-a-permission.webp)
28 +
29 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp)
30 +
31 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp)
32 +
33 + ![Microsoft Graph delegated permissions with Files.ReadWrite selected](/images/toolkits/excel/files-readwrite-permission.webp)
34 +
35 + ![Configured Files.ReadWrite delegated permission details](/images/toolkits/excel/files-readwrite-details.webp)
36 +
37 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
38 +
39 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
40 +
41 +### Create the auth config in Composio
42 +
43 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Excel**. Enter a config name and click **Next**.
44 +
45 + ![Composio Auth Configs page with the Create button](/images/toolkits/excel/composio-auth-configs.webp)
46 +
47 + ![Create Auth Config dialog with Excel selected](/images/toolkits/excel/composio-toolkit-picker.webp)
48 +
49 + ![Auth config name field with the Next button](/images/toolkits/excel/composio-config-name.webp)
50 +
51 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
52 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
53 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account that can access your workbooks and accept the consent prompt. The request grants file read and write access; it isn't read-only. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
54 +
55 + ![Excel auth config page with the Connect Account button](/images/toolkits/excel/composio-connect-account.webp)
56 +
57 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/excel/microsoft-account-picker.webp)
58 +
59 + ![Microsoft consent prompt for file access with organization consent unchecked](/images/toolkits/excel/microsoft-consent.webp)
60 +
61 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
62 +
63 + ![Connected Accounts tab with the Excel account showing Active](/images/toolkits/excel/connected-account-active.webp)
64 +
65 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
66 +
67 +### Scopes
68 +
69 +The default auth config requests `Files.ReadWrite`, `Sites.ReadWrite.All`, `offline_access`, and `User.Read`. Microsoft requires `Files.ReadWrite` for workbook operations, even read operations such as listing worksheets. See Microsoft's [list worksheets](https://learn.microsoft.com/en-us/graph/api/workbook-list-worksheets?view=graph-rest-1.0) reference.
70 +
71 +### Restrict sign-in to one tenant
72 +
73 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
74 +
75 +### App-only access (client credentials)
76 +
77 +Excel also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`generic_id`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent.
docs/content/toolkits/faq/facebook.md
+30 -1
@@ -1,3 +1,32 @@
1 ## How do I set up custom OAuth credentials for Meta (Facebook)?
2
3 -For a step-by-step guide on creating and configuring your own Meta (Facebook) OAuth credentials with Composio, see [How to create OAuth credentials for Meta (Facebook)](https://composio.dev/auth/facebook).
3 +Use your own Meta app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Meta app
6 +
7 +1. Sign in to [Meta for Developers](https://developers.facebook.com/) and register as a developer if you haven't. Your app must be linked to a [business portfolio](https://business.facebook.com/).
8 +2. Click **Create App**. Enter the app details, select the use cases your workflow needs, and on the business step select your business portfolio. Complete the remaining fields and create the app.
9 +
10 + ![Meta for Developers Apps page with the Create App button](/images/toolkits/facebook/create-app.webp)
11 +
12 + ![Meta Create an app business step for choosing a business portfolio](/images/toolkits/facebook/business-portfolio.webp)
13 +3. In **App settings** > **Basic**, copy the **App ID** (client ID) and **App Secret** (client secret).
14 +
15 + ![Meta App settings Basic page with App ID and App secret](/images/toolkits/facebook/app-settings-basic.webp)
16 +4. Add `https://backend.composio.dev/api/v1/auth-apps/add` to the app's OAuth redirect allow list (in **App settings** > **Advanced**, or **Valid OAuth Redirect URIs** in the Facebook Login settings). It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
17 +5. Publish the app.
18 +
19 +### Create the auth config in Composio
20 +
21 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Facebook**.
22 +2. Keep the authentication type as **OAuth2** and choose **Use your own developer authentication**.
23 +
24 + ![Use your own developer credentials toggle turned on in the Facebook auth config form](/images/toolkits/facebook/own-credentials-toggle.webp)
25 +3. Paste the **App ID** as the **Client ID** and the **App Secret** as the **Client Secret**, then click **Create Facebook Auth Config**.
26 +4. Click **Connect Account**, approve access in Facebook, and confirm the account shows as **Active**.
27 +
28 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
29 +
30 +### Scopes
31 +
32 +The default auth config requests `public_profile`, `email`, `business_management`, `pages_show_list`, `pages_read_engagement`, `pages_manage_posts`, `pages_manage_engagement`, `pages_read_user_content`, `pages_manage_metadata`, `pages_messaging`, and `read_insights`. Edit the **Scopes** field on the auth config to request only what you use. Meta requires App Review before people without a role on your app can grant most of these permissions.
docs/content/toolkits/faq/fathom.md new
+31
@@ -0,0 +1,31 @@
1 +## How do I connect Fathom with Composio-managed auth?
2 +
3 +Composio-managed OAuth needs no Fathom OAuth app or API key.
4 +
5 +1. In the Composio dashboard, open **Toolkits**, search for **Fathom**, and click **Add to Project**.
6 +
7 + ![Composio Toolkits page](/images/toolkits/fathom/toolkits-page.webp)
8 +
9 + ![Toolkits search results for Fathom](/images/toolkits/fathom/search-fathom.webp)
10 +
11 + ![Fathom toolkit panel with the Add to Project button](/images/toolkits/fathom/add-to-project.webp)
12 +2. Enter a **Config Name** and click **Next**.
13 +
14 + ![Fathom auth config Config Name step](/images/toolkits/fathom/config-name.webp)
15 +3. Select **OAuth 2.0**, choose **Composio Managed** under **Credentials**, keep the `public_api` scope selected, and click **Create Auth Config**.
16 +
17 + ![Fathom auth config with OAuth 2.0, Composio Managed, and the public_api scope selected](/images/toolkits/fathom/composio-managed-oauth.webp)
18 +4. Open the auth config and click **Connect Account**. In Fathom, check that the right account is signed in (click **Change** to switch), then click **Allow Access**.
19 +
20 + ![Fathom auth config panel with the Connect Account button](/images/toolkits/fathom/connect-account.webp)
21 +
22 + ![Fathom authorization screen with the Allow Access button](/images/toolkits/fathom/allow-access.webp)
23 +5. Under **Accounts**, confirm the connected account shows as **Active**. The auth config's **Enabled** status alone doesn't mean an account is connected.
24 +
25 + ![Fathom auth config Accounts tab with an Active connected account](/images/toolkits/fathom/active-account.webp)
26 +
27 +## Can I connect Fathom with an API key instead?
28 +
29 +Yes. Create a key in Fathom under **Settings** > **API Access**, create a Fathom auth config with the **API Key** authentication type, and paste the key when you click **Connect Account**. The same **API Access** section is where Fathom offers its own OAuth app setup; see the [Fathom developer documentation](https://developers.fathom.ai/).
30 +
31 +![Fathom Settings page with the API Access section](/images/toolkits/fathom/api-access-settings.webp)
docs/content/toolkits/faq/github.md
+42
@@ -1,3 +1,45 @@
1 +## How do I set up custom OAuth credentials for GitHub?
2 +
3 +Use your own GitHub OAuth App when you want users to see your app's name on the consent screen and control scopes and credential rotation yourself. These steps cover OAuth Apps; for GitHub Apps, see the next question.
4 +
5 +### Create the GitHub OAuth App
6 +
7 +1. Sign in to [GitHub](https://github.com/) with the account that should own the app. To keep the app with a team, register it under an organization you can manage apps for.
8 +2. Click your avatar, then **Settings**. In the sidebar, click **Developer settings** > **OAuth Apps** > **New OAuth App** (or **Register a new application** if it's the first one).
9 +
10 + ![GitHub Developer settings sidebar with OAuth Apps](/images/toolkits/github/oauth-apps-sidebar.webp)
11 +3. Fill in the form:
12 + - **Application name**: a name users will recognize on the consent screen.
13 + - **Homepage URL**: the public site for your product.
14 + - **Application description**: optional, but helps users understand the request.
15 + - **Authorization callback URL**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
16 +
17 + These fields are public, so don't put secrets or internal URLs in them. Leave **Enable Device Flow** off; the browser flow doesn't need it.
18 +
19 + ![GitHub Register a new OAuth app form](/images/toolkits/github/register-oauth-app.webp)
20 +
21 + ![GitHub OAuth app form with the Composio authorization callback URL](/images/toolkits/github/callback-url.webp)
22 +4. Click **Register application**, copy the **Client ID**, then click **Generate a new client secret** and copy it right away. GitHub shows it only once.
23 +
24 +### Create the auth config in Composio
25 +
26 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **GitHub**.
27 +2. Confirm the authentication method is **OAuth2**, review the scopes, and turn on **Use your own developer credentials**.
28 +3. Paste the **Client ID** and **Client Secret**, then create the auth config.
29 +
30 + ![GitHub auth config form with Your Own Credentials selected and Client id and Client secret fields](/images/toolkits/github/own-credentials.webp)
31 +4. Click **Connect Account**, enter a user ID, and click **Authorize** on the GitHub consent screen. Confirm the account shows as **Active**.
32 +
33 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
34 +
35 +### Scopes
36 +
37 +The default auth config requests `repo`, `user`, `gist`, `notifications`, `project`, `workflow`, and `codespace`. Remove any your tools don't need. If you support several permission levels, create a separate auth config for each.
38 +
39 +### Organization access
40 +
41 +If the consent screen shows an organization with a **Request** button, the user can still authorize for their personal account, but an organization owner may need to approve the app before it can reach the organization's private resources.
42 +
43 ## Does Composio support GitHub Apps?
44
45 Yes. You can bring your own GitHub App by configuring its client ID and client secret in the GitHub auth config.
docs/content/toolkits/faq/gitlab.md
+40 -1
@@ -1,3 +1,42 @@
1 ## How do I set up custom OAuth credentials for GitLab?
2
3 -For a step-by-step guide on creating and configuring your own GitLab OAuth credentials with Composio, see [How to create OAuth credentials for GitLab](https://composio.dev/auth/gitlab).
3 +Use your own GitLab OAuth application when you want users to see your app's name on the consent screen, or when you connect to a self-managed GitLab instance.
4 +
5 +### Create the GitLab app
6 +
7 +1. Sign in to GitLab, click your avatar in the top-right corner, and select **Edit profile**.
8 +2. In the left sidebar, click **Applications** (direct link on GitLab.com: `https://gitlab.com/-/profile/applications`). On a self-managed instance, use the same path on your own host.
9 +
10 + ![GitLab user settings Applications page with the Add new application button](/images/toolkits/gitlab/applications-page.webp)
11 +3. Click **New application** and enter a name, such as `Composio GitLab Integration`.
12 +4. In **Redirect URI**, paste `https://backend.composio.dev/api/v1/auth-apps/add` with no trailing `/`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
13 +
14 + ![GitLab Add new application form with the Composio redirect URI and the api scope selected](/images/toolkits/gitlab/new-application-form.webp)
15 +5. Select the scopes your integration needs, then click **Save application**.
16 +6. Copy the **Application ID** (your Client ID) and the **Secret** (your Client Secret). GitLab shows the secret only once.
17 +
18 + ![GitLab application page with a redacted Application ID, hidden Secret and the Composio callback URL](/images/toolkits/gitlab/application-credentials.webp)
19 +
20 +### Create the auth config in Composio
21 +
22 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **GitLab**.
23 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
24 +
25 + ![Composio GitLab auth config form with OAUTH2 selected and the default scopes listed](/images/toolkits/gitlab/composio-auth-config-scopes.webp)
26 +3. Paste the Application ID as **Client ID** and the Secret as **Client Secret**. Add the same scopes you selected in GitLab, then click **Create GitLab Auth Config**.
27 +4. Click **Connect Account**, approve the permissions on the GitLab consent screen, and confirm the account shows as **Active**.
28 +
29 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
30 +
31 +### Scopes
32 +
33 +The default auth config requests `api`, `read_api`, `read_user`, `read_repository`, `write_repository`, `profile`, and `email`. `api` grants full read/write API access; use `read_api` instead for read-only access. Select only the scopes you need in the GitLab app and use the same list in the auth config.
34 +
35 +### Self-managed GitLab
36 +
37 +The OAuth2 auth config has two URL fields:
38 +
39 +- `full`: your GitLab server URL with `/api/v4` appended. The default is `https://gitlab.com/api/v4`.
40 +- `authorizationUrl`: your GitLab server URL without the API path. The default is `https://gitlab.com`.
41 +
42 +For a self-managed instance, create the OAuth application on that instance and set both fields to your instance's URL, for example `https://gitlab.example.com/api/v4` and `https://gitlab.example.com`.
docs/content/toolkits/faq/gmail.md
+81 -2
@@ -1,12 +1,91 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Gmail API**, and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Gmail API page in the Google Cloud API Library with the Enable button](/images/toolkits/gmail/enable-gmail-api.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the gmail.readonly scope selected](/images/toolkits/gmail/data-access-scopes.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-gmail), go to **Auth Configs** → **Create** and select **Gmail**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Gmail in the toolkit search results](/images/toolkits/gmail/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Gmail auth config](/images/toolkits/gmail/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Gmail auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/gmail/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen asking to view email messages and settings](/images/toolkits/gmail/google-consent-screen.webp)
63 +
64 + ![Gmail auth config details with an Active connected account](/images/toolkits/gmail/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default Gmail auth config requests `https://mail.google.com/` (full mailbox access), `userinfo.email`, `userinfo.profile`, and People API read scopes such as `contacts.readonly`, `contacts.other.readonly`, and `user.emails.read`. Request only what your tools need. For example, `gmail.readonly` reads messages and settings but can't send or modify mail. See Google's [Gmail scope reference](https://developers.google.com/workspace/gmail/api/auth/scopes).
71 +
72 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
73 +
74 +If you change the scopes later, reconnect the account so the user grants the new access.
75 +
76 +### Testing, publishing, and verification
77 +
78 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
79 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
80 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
81 +- `https://mail.google.com/` and `gmail.readonly` are restricted scopes. A public app that requests them needs restricted-scope verification, which can include a security assessment if your servers store or transmit Gmail data.
82 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
83
84 ## Why am I seeing "App is blocked" when connecting Gmail?
85
86 Google can block consent when the OAuth client requests scopes that Google hasn't approved for that client. This can happen after you add scopes beyond the defaults.
87
9 -Follow [Google scope approvals and blocked-app troubleshooting](/docs/authentication/controlling-scopes#google-scope-approvals). Toolkit defaults and scope recommendations don't establish the managed app's approved scopes. If you need your own OAuth app, see [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and [Google OAuth setup](https://composio.dev/auth/googleapps).
88 +Follow [Google scope approvals and blocked-app troubleshooting](/docs/authentication/controlling-scopes#google-scope-approvals). Toolkit defaults and scope recommendations don't establish the managed app's approved scopes. If you need your own OAuth app, see [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and the setup steps above.
89
90 ## Why am I getting "Gmail API has not been used in project" error?
91
docs/content/toolkits/faq/gong.md
+36
@@ -1,3 +1,39 @@
1 +## How do I set up custom OAuth credentials for Gong?
2 +
3 +Use your own Gong OAuth integration when you want users to see your integration's name on the consent screen and control the credentials yourself. You need a Gong account with access to the **Admin center**; if you don't see it, ask your Gong workspace admin.
4 +
5 +### Create the Gong integration
6 +
7 +1. Sign in to Gong, expand the left sidebar, and click **Admin center** at the bottom.
8 +2. In the **Ecosystem** section, click **API**, then switch from the **API Keys** tab to the **Integrations** tab. OAuth apps live under **Integrations**.
9 +
10 + ![Gong Admin center with API highlighted in the Ecosystem section](/images/toolkits/gong/admin-center-api.webp)
11 +3. Click **Create Integration** and fill in the name, description, short description, and logos.
12 +
13 + ![Gong Create Integration form with name, description, short description and logo fields](/images/toolkits/gong/integration-basic-details.webp)
14 +4. Under **Required authorization scopes**, select the scopes your integration needs (see Scopes below).
15 +
16 + ![Gong Required authorization scopes list with scopes checked](/images/toolkits/gong/integration-scopes.webp)
17 +5. In **Redirect URI**, enter `https://backend.composio.dev/api/v1/auth-apps/add` with no trailing slash. It must exactly match the `oauth_redirect_uri` field in your Composio auth config. Fill in the remaining required fields (privacy and terms links, help article, contact email, domain).
18 +6. Click **Save**. Back on the **Integrations** list, copy the **Client ID** from the table, then click **Show secret** in the **Client Secret** column and copy the secret. Store it now; if you lose it, regenerate it from the integration's menu and update your auth config.
19 +7. Add Composio's IP addresses to the integration's trusted IP lists, as described in the IP allowlist question below.
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Gong**.
24 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
25 +3. Paste the **Client ID** and **Client Secret**, enter the same scopes you selected in Gong, then create the auth config.
26 +4. Click **Connect Account**. When asked for the API base URL, keep `https://api.gong.io` unless your Gong admin gives you a tenant-specific address such as `https://company-17.api.gong.io`. Don't use the web app URL from your browser (for example `us-12345.app.gong.io`).
27 +
28 + ![Composio connect screen with https://api.gong.io in the API Base URL field](/images/toolkits/gong/api-base-url.webp)
29 +5. Review the permissions on Gong's consent screen, click **Allow**, and confirm the account shows as **Active**.
30 +
31 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
32 +
33 +### Scopes
34 +
35 +The scopes in the auth config must match the scopes selected in the Gong integration. If they differ, authorization fails or tools return permission errors; add any missing scope to both places and reconnect. The default auth config requests a broad set covering calls, meetings, CRM, users, flows, and stats. Common choices include `api:calls:read:transcript`, `api:calls:create`, `api:users:read`, `api:meetings:user:create`, and `api:workspaces:read`. Request only what your integration uses, since users see the full list on the consent screen.
36 +
37 ## Which IP addresses should I allowlist for Gong OAuth?
38
39 Gong now requires every OAuth integration to have trusted IP addresses configured. Gong's [release notes](https://help.gong.io/docs/release-notes#planned-change-management) list this change as announced in September 2026, with release in October 2026. If Gong gave your integration an October 15, 2026 deadline, add these IPs before that date.
docs/content/toolkits/faq/google_admin.md
+55 -1
@@ -1,3 +1,57 @@
1 ## How do I set up custom Google OAuth credentials for Google Admin?
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).
3 +Composio doesn't provide a managed OAuth app for Google Admin, so you need your own Google OAuth app to connect it.
4 +
5 +Connect with a Google Workspace administrator account that has the Directory privileges your workflow needs. Your organization may also need to allow the OAuth app under its app-access policy.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Admin SDK API** (`admin.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. The toolkit uses its Directory API.
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_admin), open **Auth Configs** → **Create** and select **Google Admin**.
38 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
39 +3. Open the auth config, select **Connect Account**, and sign in with the Workspace administrator account. If Google returns an access error, check the account's Directory privileges and your organization's app-access policy. A valid OAuth grant doesn't add admin privileges.
40 +
41 + ![Google consent screen asking to see info about users on your domain](/images/toolkits/google_admin/google-consent-screen.webp)
42 +
43 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
44 +
45 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
46 +
47 +### Scopes
48 +
49 +The default auth config requests read and write Directory API scopes for users, user aliases, groups, group members, org units, and domains, such as `https://www.googleapis.com/auth/admin.directory.user` and `https://www.googleapis.com/auth/admin.directory.user.readonly`. To only list users, `https://www.googleapis.com/auth/admin.directory.user.readonly` is enough. Remove group, member, or write scopes your workflow doesn't use. See the [users.list reference](https://developers.google.com/workspace/admin/directory/reference/rest/v1/users/list).
50 +
51 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
52 +
53 +### Publish and verify the app
54 +
55 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
56 +
57 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_adsense.md new
+59
@@ -0,0 +1,59 @@
1 +## How do I set up custom Google OAuth credentials for Google AdSense?
2 +
3 +Composio doesn't provide a managed OAuth app for Google AdSense, so you need your own Google OAuth app to connect it.
4 +
5 +Connect with a Google account that has access to an existing AdSense publisher account.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **AdSense Management API** (`adsense.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. See Google's [AdSense Management API setup](https://developers.google.com/adsense/management/getting_started).
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_adsense), open **Auth Configs** → **Create** and select **Google AdSense**.
38 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
39 +3. Open the auth config, select **Connect Account**, and sign in with the Google account that can access the AdSense publisher account. If the connection succeeds but the account list is empty, check that account's access in AdSense.
40 +
41 + ![Google consent screen asking to view your AdSense data](/images/toolkits/google_adsense/google-consent-screen.webp)
42 +
43 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
44 +
45 + ![Composio auth config panel with the Google AdSense connected account shown as Active](/images/toolkits/google_adsense/connected-account-active.webp)
46 +
47 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
48 +
49 +### Scopes
50 +
51 +The default auth config requests `https://www.googleapis.com/auth/adsense`, which can manage AdSense resources. If your workflow only reads accounts and reports, use `https://www.googleapis.com/auth/adsense.readonly` instead. See the [accounts.list reference](https://developers.google.com/adsense/management/reference/rest/v2/accounts/list).
52 +
53 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
54 +
55 +### Publish and verify the app
56 +
57 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
58 +
59 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_analytics.md new
+78
@@ -0,0 +1,78 @@
1 +## How do I set up custom Google OAuth credentials for Google Analytics?
2 +
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4 +
5 +The Google account you connect needs a role on the Analytics property. Use a GA4 property ID for GA4 reports.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Google Analytics Data API**, and select **Enable**. If the page shows **Manage**, the API is already enabled.
14 +
15 + ![Google Analytics Data API page in the API Library with the Enable button](/images/toolkits/google_analytics/enable-analytics-data-api.webp)
16 +
17 +3. If your workflow lists accounts or manages properties, enable **Google Analytics Admin API** too. See Google's [Data API quickstart](https://developers.google.com/analytics/devguides/reporting/data/v1/quickstart).
18 +4. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
19 +
20 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
21 +
22 +5. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
23 +
24 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
25 +
26 +6. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
27 +
28 + ![Data Access scope picker with the analytics.readonly scope selected](/images/toolkits/google_analytics/data-access-analytics-scope.webp)
29 +
30 +7. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
31 +
32 + ![Create OAuth client ID form with Web application selected and a client name](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
33 +
34 +8. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
35 +
36 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
37 +
38 +9. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
39 +
40 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
41 +
42 +### Create the auth config in Composio
43 +
44 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_analytics), open **Auth Configs** → **Create** and select **Google Analytics**.
45 +
46 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
47 +
48 + ![Create Auth Config dialog with Google Analytics in the search results](/images/toolkits/google_analytics/select-google-analytics-toolkit.webp)
49 +
50 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
51 +
52 + ![Google Analytics auth config form with Client ID, Client secret, Redirect URI, and the analytics.readonly scope](/images/toolkits/google_analytics/auth-config-credentials.webp)
53 +
54 +3. Open the auth config, select **Connect Account**, and sign in with the Google account you want to connect. Review the requested permissions before you continue.
55 +
56 + ![Google sign-in screen asking to share your name and profile picture](/images/toolkits/google_analytics/google-sign-in-profile.webp)
57 +
58 + ![Google consent screen asking to see and download your Google Analytics data](/images/toolkits/google_analytics/google-consent-screen.webp)
59 +
60 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
61 +
62 + ![Composio auth config panel with the Google Analytics connected account shown as Active](/images/toolkits/google_analytics/connected-account-active.webp)
63 +
64 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
65 +
66 +### Scopes
67 +
68 +The default auth config requests `https://www.googleapis.com/auth/analytics.readonly`, `https://www.googleapis.com/auth/analytics`, `https://www.googleapis.com/auth/userinfo.profile`. `analytics.readonly` is enough to read reports. Editing configuration or managing users needs broader scopes and the matching Analytics role. See the [runReport reference](https://developers.google.com/analytics/devguides/reporting/data/v1/rest/v1beta/properties/runReport).
69 +
70 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
71 +
72 +### Publish and verify the app
73 +
74 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
75 +
76 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
77 +
78 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_business_profile.md new
+58
@@ -0,0 +1,58 @@
1 +## How do I set up custom Google OAuth credentials for Google Business Profile?
2 +
3 +Composio doesn't provide a managed OAuth app for Google Business Profile, so you need your own Google OAuth app to connect it.
4 +
5 +Connect with a Google account that owns or manages the Business Profile. Your Google Cloud project also needs Business Profile API access, which Google approves separately. Google lists a verified profile that has been active for at least 60 days and a matching business website among the [application requirements](https://developers.google.com/my-business/content/prereqs).
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Request Business Profile API access for your Cloud project and wait for Google's approval.
14 +3. After approval, open **APIs & Services** → **Library**, search for **My Business Account Management API** (`mybusinessaccountmanagement.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. Composio uses it to list accounts and check the connection. Enable any other Business Profile APIs your actions use. See Google's [basic setup](https://developers.google.com/my-business/content/basic-setup).
15 +4. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
18 +
19 +5. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
20 +
21 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
22 +
23 +6. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
24 +7. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
25 +
26 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
27 +
28 +8. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
29 +
30 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
31 +
32 +9. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
33 +
34 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
35 +
36 +### Create the auth config in Composio
37 +
38 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_business_profile), open **Auth Configs** → **Create** and select **Google Business Profile**.
39 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
40 +3. Open the auth config, select **Connect Account**, and sign in with the Google account that manages the profile. If the Account Management API is unavailable or shows a quota of zero, the project's Business Profile API access hasn't been approved. OAuth app verification and Business Profile API approval are separate.
41 +
42 + ![Google consent screen asking to manage your Google business listings](/images/toolkits/google_business_profile/google-consent-screen.webp)
43 +
44 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
45 +
46 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
47 +
48 +### Scopes
49 +
50 +The default auth config requests `https://www.googleapis.com/auth/business.manage`. Account listing requires it, and it can authorize changes to any profile the signed-in user can manage.
51 +
52 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
53 +
54 +### Publish and verify the app
55 +
56 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
57 +
58 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_chat.md new
+68
@@ -0,0 +1,68 @@
1 +## How do I set up custom Google OAuth credentials for Google Chat?
2 +
3 +Composio doesn't provide a managed OAuth app for Google Chat, so you need your own Google OAuth app to connect it.
4 +
5 +Connect with a Business or Enterprise Google Workspace account that has Google Chat access.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Google Chat API** (`chat.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. You don't need to request manual approval for this API.
14 +
15 + ![API Library search results for Google Chat API](/images/toolkits/google_chat/search-chat-api.webp)
16 +
17 + ![Google Chat API product page with the Enable button and the chat.googleapis.com service name](/images/toolkits/google_chat/enable-chat-api.webp)
18 +
19 +3. If your workflow creates, updates, or deletes Chat resources, open **Google Chat API** → **Configuration** and enter an app name, avatar URL, and description. Leave interactive features off for an API-only app. You don't need a Cloud Run deployment. Read-only calls don't need this step. See Google's [Chat API setup](https://developers.google.com/workspace/chat/configure-chat-api).
20 +4. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
21 +
22 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
23 +
24 +5. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
25 +
26 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
27 +
28 +6. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
29 +
30 + ![Data Access scope picker with the chat.spaces.readonly scope selected](/images/toolkits/google_chat/data-access-chat-scope.webp)
31 +
32 +7. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
33 +
34 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
35 +
36 +8. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
37 +
38 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
39 +
40 +9. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
41 +
42 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
43 +
44 +### Create the auth config in Composio
45 +
46 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_chat), open **Auth Configs** → **Create** and select **Google Chat**.
47 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
48 +3. Open the auth config, select **Connect Account**, and sign in with the Google account you want to connect. Review the requested permissions before you continue.
49 +
50 + ![Google consent screen asking to view chat and spaces in Google Chat](/images/toolkits/google_chat/google-consent-screen.webp)
51 +
52 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
53 +
54 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default auth config requests `chat.spaces`, `chat.messages`, `chat.messages.create`, `chat.memberships`, and `chat.users`, plus read-only variants of spaces, messages, and memberships, all under `https://www.googleapis.com/auth/`. For read-only use, `https://www.googleapis.com/auth/chat.spaces.readonly` is enough to view the spaces the user belongs to. Remove scopes you don't need. See Google's [Chat scope reference](https://developers.google.com/workspace/chat/authenticate-authorize).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +### Publish and verify the app
63 +
64 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
65 +
66 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
67 +
68 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_classroom.md
+64 -2
@@ -1,12 +1,74 @@
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).
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4 +
5 +Connect with a Google account that has Classroom access. Course access follows the user's Classroom role, and some advanced features need specific Education licenses.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Google Classroom API** (`classroom.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. See Google's [Classroom API setup](https://developers.google.com/workspace/classroom/guides/get-started).
14 +
15 + ![Google Classroom API product page with the Enable button](/images/toolkits/google_classroom/enable-classroom-api.webp)
16 +
17 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
22 +
23 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with Classroom courses and rosters read-only scopes selected](/images/toolkits/google_classroom/data-access-classroom-scopes.webp)
28 +
29 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
30 +
31 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
32 +
33 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
34 +
35 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
36 +
37 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
38 +
39 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
40 +
41 +### Create the auth config in Composio
42 +
43 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_classroom), open **Auth Configs** → **Create** and select **Google Classroom**.
44 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
45 +3. Open the auth config, select **Connect Account**, and sign in with the Google account you want to connect. Review the requested permissions before you continue.
46 +
47 + ![Google consent screen asking to view your Google Classroom classes and class rosters](/images/toolkits/google_classroom/google-consent-screen.webp)
48 +
49 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
50 +
51 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
52 +
53 +### Scopes
54 +
55 +The default auth config requests these scopes under `https://www.googleapis.com/auth/`: `classroom.courses.readonly`, `classroom.coursework.students`, `classroom.courseworkmaterials`, `classroom.topics`, `classroom.rosters.readonly`, `classroom.announcements`, and `classroom.course-work`. Keep `classroom.rosters.readonly`: Composio uses it to check the signed-in Classroom profile. It lets the app view rosters but not change them. For read-only use, `classroom.courses.readonly` plus `classroom.rosters.readonly` is enough. See Google's [Classroom scope reference](https://developers.google.com/workspace/classroom/guides/auth).
56 +
57 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
58 +
59 +### Publish and verify the app
60 +
61 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
62 +
63 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
64 +
65 +If you change the requested scopes later, reconnect the account so the user grants the new access.
66
67 ## Why am I seeing "App is blocked" when connecting Google Classroom?
68
69 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.
70
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).
71 +Remove the additional scopes from your auth config, or use your own OAuth app and submit those scopes for Google verification. The setup and verification steps are under **How do I set up custom Google OAuth credentials for Google Classroom?** above.
72
73 ## Why am I getting "Google Classroom API has not been used in project" error?
74
docs/content/toolkits/faq/google_data_studio.md new
+54
@@ -0,0 +1,54 @@
1 +## How do I set up custom Google OAuth credentials for Google Data Studio?
2 +
3 +Composio doesn't provide a managed OAuth app for Google Data Studio, so you need your own Google OAuth app to connect it.
4 +
5 +You need a Google Workspace or Cloud Identity organization. A Workspace administrator has to authorize your OAuth client for the Data Studio API.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Data Studio API** (`datastudio.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled.
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Leave the Data Studio scopes out of **Data Access**. Google's instructions keep them out of the OAuth client's Data Access setup, because your Workspace administrator authorizes them in the Admin console instead (step 9).
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +9. Have a Workspace administrator open the [Google Admin console](https://admin.google.com/) → **Security** → **Access and data control** → **API controls** → **Manage Domain Wide Delegation**. Under **API clients**, select **Add new**, enter the OAuth client ID, add the Data Studio scopes your app needs, and authorize the client. Follow Google's [Data Studio API instructions](https://developers.google.com/data-studio/integrate/api) for this grant.
36 +
37 +### Create the auth config in Composio
38 +
39 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_data_studio), open **Auth Configs** → **Create** and select **Google Data Studio**.
40 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
41 +3. Open the auth config, select **Connect Account**, and sign in with a Google account in the authorized organization. If Google reports `invalid_scope`, ask the administrator to check the authorized client ID and scope list.
42 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
43 +
44 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
45 +
46 +### Scopes
47 +
48 +The default auth config requests `https://www.googleapis.com/auth/datastudio`, `openid`, `email`, and `profile`. Composio uses the OpenID scopes to identify the account. If you only search reports and data sources, `https://www.googleapis.com/auth/datastudio.readonly` is enough. Request only scopes your administrator has authorized.
49 +
50 +### Publish and verify the app
51 +
52 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
53 +
54 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_maps.md
+61 -2
@@ -1,12 +1,71 @@
1 ## How do I set up custom Google OAuth credentials for Google Maps?
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).
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4 +
5 +Use a Google Cloud project with Maps billing enabled, and confirm your team is allowed to use that project's Maps quota.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Places API (New)** (`places.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. Composio uses it to check the connection.
14 +3. If your workflow computes routes, also enable **Routes API** (`routes.googleapis.com`). Check Google's [authentication requirements](https://developers.google.com/maps/documentation/places/web-service/get-api-key) for each Maps endpoint you use.
15 +4. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
18 +
19 +5. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
20 +
21 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
22 +
23 +6. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
24 +7. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
25 +
26 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
27 +
28 +8. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
29 +
30 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
31 +
32 +9. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
33 +
34 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
35 +
36 +### Create the auth config in Composio
37 +
38 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_maps), open **Auth Configs** → **Create** and select **Google Maps**.
39 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
40 +3. Open the auth config, select **Connect Account**, and sign in. The connection check looks up a place through Places API (New), which can count toward Maps usage. Google requires a billing-enabled quota project for OAuth requests, so if Google rejects the connection, check API enablement, quota-project permissions, and billing.
41 +
42 + ![Google consent screen asking to manage your Google Cloud data and see your email address](/images/toolkits/google_maps/google-consent-screen.webp)
43 +
44 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
45 +
46 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
47 +
48 +### Scopes
49 +
50 +The default auth config requests `https://www.googleapis.com/auth/cloud-platform`. Google requires it for OAuth requests to Places API (New) and Routes API. It can grant broad access to any Google Cloud resources the signed-in user can reach, so review that user's project permissions before you connect.
51 +
52 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
53 +
54 +### Use an API key instead
55 +
56 +Google Maps also supports an API key connection. Create a key in Google Cloud Console under **APIs & Services** → **Credentials** in a project with the Maps APIs and billing enabled, then paste it (it starts with `AIza`) when you connect the account. Some tools, such as the Maps Embed API, work only with an API key (see below).
57 +
58 +### Publish and verify the app
59 +
60 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
61 +
62 +If you change the requested scopes later, reconnect the account so the user grants the new access.
63
64 ## Why am I seeing "App is blocked" when connecting Google Maps?
65
66 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.
67
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).
68 +Remove the additional scopes from your auth config, or use your own OAuth app and submit those scopes for Google verification. The setup and verification steps are under **How do I set up custom Google OAuth credentials for Google Maps?** above.
69
70 ## Why am I getting "Google Maps API has not been used in project" error?
71
docs/content/toolkits/faq/google_merchant.md new
+59
@@ -0,0 +1,59 @@
1 +## How do I set up custom Google OAuth credentials for Google Merchant Center?
2 +
3 +Composio doesn't provide a managed OAuth app for Google Merchant Center, so you need your own Google OAuth app to connect it.
4 +
5 +Connect with a Google account that has Merchant Center access. For first-time developer registration, Google requires an existing production Merchant Center account with a verified homepage and an authorized admin.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Merchant API** (`merchantapi.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled.
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +9. Complete Google's one-time [developer registration](https://developers.google.com/merchant/api/guides/quickstart/registration) for the Cloud project that owns your OAuth client. An authorized Merchant Center admin links the project to the Merchant Center account.
36 +
37 +### Create the auth config in Composio
38 +
39 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_merchant), open **Auth Configs** → **Create** and select **Google Merchant Center**.
40 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
41 +3. Open the auth config, select **Connect Account**, and sign in with a Google account that has Merchant Center access. If the connection check reports that the Google Cloud project is unregistered, finish developer registration for that project and try again.
42 +
43 + ![Google consent screen asking to manage your product listings and accounts for Google Shopping](/images/toolkits/google_merchant/google-consent-screen.webp)
44 +
45 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
46 +
47 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
48 +
49 +### Scopes
50 +
51 +The default auth config requests `https://www.googleapis.com/auth/content`. Merchant API account listing requires it, and it also allows any write operations the user's Merchant Center role permits. See the [accounts.list reference](https://developers.google.com/merchant/api/reference/rest/accounts_v1/accounts/list).
52 +
53 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
54 +
55 +### Publish and verify the app
56 +
57 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
58 +
59 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/google_search_console.md new
+75
@@ -0,0 +1,75 @@
1 +## How do I set up custom Google OAuth credentials for Google Search Console?
2 +
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4 +
5 +The Google account you connect needs access to the Search Console property. OAuth consent doesn't grant ownership of a site.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Google Search Console API**, and select **Enable**. If the page shows **Manage**, the API is already enabled. See Google's [API prerequisites](https://developers.google.com/webmaster-tools/v1/prereqs).
14 +
15 + ![Google Search Console API page in the API Library](/images/toolkits/google_search_console/enable-search-console-api.webp)
16 +
17 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
20 +
21 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
22 +
23 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
24 +
25 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the webmasters.readonly scope selected](/images/toolkits/google_search_console/data-access-webmasters-scope.webp)
28 +
29 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
30 +
31 + ![Create OAuth client ID form with Web application selected and a client name](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
32 +
33 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
34 +
35 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
36 +
37 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
38 +
39 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
40 +
41 +### Create the auth config in Composio
42 +
43 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-google_search_console), open **Auth Configs** → **Create** and select **Google Search Console**.
44 +
45 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
46 +
47 + ![Create Auth Config dialog with Google Search Console in the search results](/images/toolkits/google_search_console/select-google-search-console-toolkit.webp)
48 +
49 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
50 +
51 + ![Google Search Console auth config form with Client ID, Client secret, Redirect URI, and the webmasters.readonly scope](/images/toolkits/google_search_console/auth-config-credentials.webp)
52 +
53 +3. Open the auth config, select **Connect Account**, and sign in with the Google account you want to connect. Review the requested permissions before you continue.
54 +
55 + ![Google consent screen asking to view Search Console data for your verified sites](/images/toolkits/google_search_console/google-consent-screen.webp)
56 +
57 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
58 +
59 + ![Composio auth config panel with the Google Search Console connected account shown as Active](/images/toolkits/google_search_console/connected-account-active.webp)
60 +
61 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
62 +
63 +### Scopes
64 +
65 +The default auth config requests `https://www.googleapis.com/auth/webmasters`, `https://www.googleapis.com/auth/webmasters.readonly`, `https://www.googleapis.com/auth/userinfo.profile`, `https://www.googleapis.com/auth/userinfo.email`. `webmasters.readonly` is enough to read search performance data. Site-management operations need `webmasters` and the matching property access. See Google's [authorization guide](https://developers.google.com/webmaster-tools/v1/how-tos/authorizing).
66 +
67 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
68 +
69 +### Publish and verify the app
70 +
71 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
72 +
73 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
74 +
75 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/googleads.md
+80 -3
@@ -1,8 +1,85 @@
1 -## Google Ads developer token now belongs on the auth config, not connection initiation
1 +## How do I set up custom Google OAuth credentials for Google Ads?
2
3 -Google Ads was changed so the developer token lives on the auth config itself, not on each connection initiation request. Older auth configs created before this change do not have the developer token field, and new connections through those auth configs can fail because the token is no longer accepted at the connection level. Create a new Google Ads authConfig with the developer token included, then create a fresh connection through that authConfig.
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4
5 -![Google Ads auth config form showing the developer token field under custom developer credentials.](/images/kb/toolkits/googleads/google-ads-developer-token-auth-config.png)
5 +You need a Google Ads account you can access and its 10-digit Customer ID. Live-account API access is controlled by the Google Cloud project that owns the OAuth client, not by a developer token on the auth config.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Google Ads API**, and select **Enable**. If the page shows **Manage**, the API is already enabled.
14 +
15 + ![Google Ads API page in the API Library with the Enable button](/images/toolkits/googleads/enable-google-ads-api.webp)
16 +
17 +3. Enabling the Google Ads API grants **Test** access only. To use production Ads accounts, open the Google Ads API **Overview** page for your Cloud project and apply for **Explorer** access. Higher usage or extra features can require **Basic** or **Standard** access. See Google's [access levels](https://developers.google.com/google-ads/api/docs/api-policy/access-levels) and [Cloud project setup](https://developers.google.com/google-ads/api/docs/oauth/cloud-project).
18 +4. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
19 +
20 + ![Google Auth Platform Branding page with app name, support email, and developer contact fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
21 +
22 +5. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
23 +
24 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
25 +
26 +6. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
27 +
28 + ![Data Access scope picker with the Google Ads adwords scope selected](/images/toolkits/googleads/data-access-adwords-scope.webp)
29 +
30 +7. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
31 +
32 + ![Create OAuth client ID form with Web application selected and a client name](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
33 +
34 +8. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
35 +
36 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
37 +
38 +9. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
39 +
40 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
41 +
42 +### Create the auth config in Composio
43 +
44 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googleads), open **Auth Configs** → **Create** and select **Google Ads**.
45 +
46 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
47 +
48 + ![Create Auth Config dialog with Google Ads in the search results](/images/toolkits/googleads/select-google-ads-toolkit.webp)
49 +
50 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
51 +
52 + ![Google Ads auth config form with Client ID, Client secret, Redirect URI, an empty Developer Token field, and the adwords scope](/images/toolkits/googleads/auth-config-credentials.webp)
53 +
54 +3. Open the auth config, select **Connect Account**, and enter the Customer ID of the Google Ads account or manager (MCC) account you want to use, for example `123-456-7890`. This is not your Google Cloud project ID. Then sign in with a Google account that can access that Ads account.
55 +
56 + ![Composio Connect Account form asking for the Google Ads Customer ID](/images/toolkits/googleads/enter-customer-id.webp)
57 +
58 + ![Google consent screen asking to manage your Google Ads accounts and data](/images/toolkits/googleads/google-consent-screen.webp)
59 +
60 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
61 +
62 + ![Composio auth config panel with the Google Ads connected account shown as Active](/images/toolkits/googleads/connected-account-active.webp)
63 +
64 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
65 +
66 +### Scopes
67 +
68 +The default auth config requests `https://www.googleapis.com/auth/adwords`. It's the only Google Ads API scope and includes account-management access, so it isn't read-only. The user's Google Ads account role still limits what they can do. See Google's [OAuth overview for Google Ads](https://developers.google.com/google-ads/api/docs/oauth/overview).
69 +
70 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
71 +
72 +### Developer token
73 +
74 +If the auth config form shows a **Developer Token** field, you can leave it empty. It's a legacy field kept for older auth configs, and Composio no longer sends it to Google. API access comes from the Google Cloud project that owns your OAuth client.
75 +
76 +### Publish and verify the app
77 +
78 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
79 +
80 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
81 +
82 +If you change the requested scopes later, reconnect the account so the user grants the new access.
83
84 ## What can cause Google Ads 429s?
85
docs/content/toolkits/faq/googlebigquery.md
+68
@@ -1,3 +1,71 @@
1 +## How do I set up custom Google OAuth credentials for Google BigQuery?
2 +
3 +Use your own Google OAuth app for production BigQuery connections. Composio's managed OAuth app is still waiting on Google verification for the BigQuery scope, so Google can block it (see the next question).
4 +
5 +The Google account you connect needs IAM access to the BigQuery projects and datasets your workflow uses. For basic exploration, Google offers a limited [BigQuery sandbox](https://docs.cloud.google.com/bigquery/docs/sandbox) that doesn't need a billing account.
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **BigQuery API** (`bigquery.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled.
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlebigquery), open **Auth Configs** → **Create** and select **Google BigQuery**.
38 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
39 +3. Open the auth config, select **Connect Account**, and sign in with the Google account you want to connect. Review the requested permissions before you continue.
40 +
41 + ![Google consent screen asking to view your data in Google BigQuery](/images/toolkits/googlebigquery/google-consent-screen.webp)
42 +
43 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
44 +
45 + ![Composio auth config panel with the Google BigQuery connected account shown as Active](/images/toolkits/googlebigquery/connected-account-active.webp)
46 +
47 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
48 +
49 +### Scopes
50 +
51 +The default auth config requests `https://www.googleapis.com/auth/cloud-platform`, `https://www.googleapis.com/auth/userinfo.email`. Composio uses `userinfo.email` to identify the connected account, so keep it. To list projects with less access, you can use `https://www.googleapis.com/auth/bigquery.readonly` with `userinfo.email` instead. Add job or data-write scopes only if your workflow runs queries or loads data. See Google's [projects.list reference](https://docs.cloud.google.com/bigquery/docs/reference/rest/v2/projects/list) for the required permissions.
52 +
53 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
54 +
55 +### IAM, billing, and missing projects
56 +
57 +OAuth scopes and Google Cloud IAM both apply. If a project or dataset is missing after you connect, check the signed-in user's IAM roles. Review BigQuery pricing and job permissions before you run queries or load data.
58 +
59 +### Use a service account instead
60 +
61 +BigQuery also supports the **Google Service Account** auth scheme, which skips the user consent screen. Create an auth config with that scheme, then paste the service account's credentials JSON in the `credentials_json` field when you connect the account.
62 +
63 +### Publish and verify the app
64 +
65 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
66 +
67 +If you change the requested scopes later, reconnect the account so the user grants the new access.
68 +
69 ## Why do I see "This app is blocked" when connecting Google BigQuery?
70
71 Google can show "This app is blocked" during the BigQuery OAuth flow when the OAuth app requests Google scopes that are not approved or verified for that app.
docs/content/toolkits/faq/googlecalendar.md
+81 -2
@@ -1,12 +1,91 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Calendar API**, and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Calendar API page in the Google Cloud API Library with the Enable button](/images/toolkits/googlecalendar/enable-calendar-api.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the calendar.events.readonly scope selected](/images/toolkits/googlecalendar/data-access-scopes.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlecalendar), go to **Auth Configs** → **Create** and select **Google Calendar**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Google Calendar in the toolkit search results](/images/toolkits/googlecalendar/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Google Calendar auth config](/images/toolkits/googlecalendar/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Google Calendar auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/googlecalendar/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen asking to view events on all calendars](/images/toolkits/googlecalendar/google-consent-screen.webp)
63 +
64 + ![Google Calendar auth config details with an Active connected account](/images/toolkits/googlecalendar/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default Google Calendar auth config requests `https://www.googleapis.com/auth/calendar` and `https://www.googleapis.com/auth/calendar.events`. For read-only event access, `calendar.events.readonly` is enough. Calendar discovery, availability, and event changes need other scopes. See Google's [Calendar scope reference](https://developers.google.com/workspace/calendar/api/auth).
71 +
72 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
73 +
74 +If you change the scopes later, reconnect the account so the user grants the new access.
75 +
76 +### Testing, publishing, and verification
77 +
78 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
79 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
80 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
81 +- **Data Access** shows which of your scopes Google treats as sensitive or restricted.
82 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
83
84 ## Why am I seeing "App is blocked" when connecting Google Calendar?
85
86 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.
87
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).
88 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
89
90 ## Why am I getting "Google Calendar API has not been used in project" error?
91
docs/content/toolkits/faq/googlecontacts.md new
+70
@@ -0,0 +1,70 @@
1 +## How do I set up custom Google OAuth credentials for Google Contacts?
2 +
3 +Google Contacts has no Composio-managed OAuth app, so you need your own Google OAuth app to connect it.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **People API**, and click **Enable**. Google Contacts tools use the People API, not the retired Contacts API. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![People API page in the Google Cloud API Library with the Enable button](/images/toolkits/googlecontacts/enable-people-api.webp)
14 +
15 + ![People API details page showing the API is enabled](/images/toolkits/googlecontacts/people-api-enabled.webp)
16 +
17 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
22 +
23 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the contacts.readonly scope selected](/images/toolkits/googlecontacts/data-access-scopes.webp)
28 +
29 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30 +
31 + ```
32 + https://backend.composio.dev/api/v1/auth-apps/add
33 + ```
34 +
35 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36 +
37 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38 +
39 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40 +
41 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlecontacts), go to **Auth Configs** → **Create** and select **Google Contacts**.
46 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
47 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
49 +
50 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51 +
52 + ![Google consent screen asking to see and download contacts](/images/toolkits/googlecontacts/google-consent-screen.webp)
53 +
54 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default Google Contacts auth config requests `https://www.googleapis.com/auth/contacts`, `contacts.other.readonly`, `directory.readonly`, `user.emails.read`, `userinfo.email`, and `userinfo.profile`. For read-only access to the user's own contacts, `contacts.readonly` is enough. `directory.readonly` searches the Workspace directory, and whether it returns results depends on your organization's policy. See Google's [People API reference](https://developers.google.com/people/api/rest/v1/people.connections/list).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +If you change the scopes later, reconnect the account so the user grants the new access.
63 +
64 +### Testing, publishing, and verification
65 +
66 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
67 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
69 +- **Data Access** shows which of your scopes Google treats as sensitive or restricted.
70 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
docs/content/toolkits/faq/googledocs.md
+81 -2
@@ -1,12 +1,91 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Docs API**, and click **Enable**. The default scopes include Drive access, so enable the **Google Drive API** too if your tools search or manage documents through Drive. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Docs API page in the Google Cloud API Library with the Enable button](/images/toolkits/googledocs/enable-docs-api.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the documents.readonly scope selected](/images/toolkits/googledocs/data-access-scopes.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googledocs), go to **Auth Configs** → **Create** and select **Google Docs**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Google Docs in the toolkit search results](/images/toolkits/googledocs/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Google Docs auth config](/images/toolkits/googledocs/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Google Docs auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/googledocs/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen asking to see all Google Docs documents](/images/toolkits/googledocs/google-consent-screen.webp)
63 +
64 + ![Google Docs auth config details with an Active connected account](/images/toolkits/googledocs/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default Google Docs auth config requests `https://www.googleapis.com/auth/documents`, `https://www.googleapis.com/auth/drive`, and `userinfo.email`. To only read documents by ID, `documents.readonly` is enough. Editing needs `documents`, and finding documents through Drive needs a Drive scope. See Google's [Docs scope reference](https://developers.google.com/workspace/docs/api/auth).
71 +
72 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
73 +
74 +If you change the scopes later, reconnect the account so the user grants the new access.
75 +
76 +### Testing, publishing, and verification
77 +
78 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
79 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
80 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
81 +- The default `drive` scope is restricted. A public app that requests it needs restricted-scope verification, which can include a security assessment.
82 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
83
84 ## Why am I seeing "App is blocked" when connecting Google Docs?
85
86 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.
87
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).
88 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
89
90 ## Why am I getting "Google Docs API has not been used in project" error?
91
docs/content/toolkits/faq/googledrive.md
+81 -2
@@ -1,12 +1,91 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Drive API**, and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Drive API page in the Google Cloud API Library with the Enable button](/images/toolkits/shared/VNt0egQy2o9O5i6LMd4JFpNcmAU.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the drive.metadata.readonly scope selected](/images/toolkits/shared/ch2L6hWRPSOigltUpRF7r9hyA.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googledrive), go to **Auth Configs** → **Create** and select **Google Drive**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Google Drive in the toolkit search results](/images/toolkits/googledrive/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Google Drive auth config](/images/toolkits/googledrive/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Google Drive auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/googledrive/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen asking to see information about Google Drive files](/images/toolkits/googledrive/google-consent-screen.webp)
63 +
64 + ![Google Drive auth config details with an Active connected account](/images/toolkits/googledrive/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default Google Drive auth config requests `https://www.googleapis.com/auth/drive` (full Drive access) and `userinfo.email`. Narrower scopes exist: `drive.metadata.readonly` lists file metadata but can't download content, and `drive.file` covers only files your app creates or the user opens with it. See Google's [Drive scope reference](https://developers.google.com/workspace/drive/api/guides/api-specific-auth).
71 +
72 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
73 +
74 +If you change the scopes later, reconnect the account so the user grants the new access.
75 +
76 +### Testing, publishing, and verification
77 +
78 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
79 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
80 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
81 +- `drive` and `drive.metadata.readonly` are restricted scopes. A public app that requests them needs restricted-scope verification, which can include a security assessment if your servers store or transmit Drive data.
82 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
83
84 ## Why am I seeing "App is blocked" when connecting Google Drive?
85
86 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.
87
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).
88 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
89
90 ## Why am I getting "Google Drive API has not been used in project" error?
91
docs/content/toolkits/faq/googleforms.md new
+70
@@ -0,0 +1,70 @@
1 +## How do I set up custom Google OAuth credentials for Google Forms?
2 +
3 +Google Forms has no Composio-managed OAuth app, so you need your own Google OAuth app to connect it.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Forms API**, and click **Enable**. The default scopes include Drive access, so enable the **Google Drive API** too. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Forms API page in the Google Cloud API Library with the Enable button](/images/toolkits/googleforms/enable-forms-api.webp)
14 +
15 + ![Google Forms API details page showing the API is enabled](/images/toolkits/googleforms/forms-api-enabled.webp)
16 +
17 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
22 +
23 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the forms.body.readonly scope selected](/images/toolkits/googleforms/data-access-scopes.webp)
28 +
29 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30 +
31 + ```
32 + https://backend.composio.dev/api/v1/auth-apps/add
33 + ```
34 +
35 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36 +
37 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38 +
39 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40 +
41 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googleforms), go to **Auth Configs** → **Create** and select **Google Forms**.
46 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
47 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
49 +
50 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51 +
52 + ![Google consent screen asking to see all Google Forms forms](/images/toolkits/googleforms/google-consent-screen.webp)
53 +
54 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default Google Forms auth config requests `https://www.googleapis.com/auth/forms.body`, `forms.body.readonly`, `forms.responses.readonly`, `drive`, `drive.file`, and `drive.readonly`. Reading form definitions needs `forms.body.readonly`, reading submitted responses needs `forms.responses.readonly`, and creating or editing forms needs `forms.body`. Keep the Drive scopes only if your tools search or manage form files through Drive. See Google's [Forms scope reference](https://developers.google.com/workspace/forms/api/reference/rest/v1/forms/get).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +If you change the scopes later, reconnect the account so the user grants the new access.
63 +
64 +### Testing, publishing, and verification
65 +
66 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
67 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
69 +- The default `drive` and `drive.readonly` scopes are restricted. A public app that requests them needs restricted-scope verification, which can include a security assessment.
70 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
docs/content/toolkits/faq/googlemeet.md
+69 -2
@@ -1,12 +1,79 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Meet REST API** (`meet.googleapis.com`), and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Meet REST API page in the Google Cloud API Library with the Enable button](/images/toolkits/googlemeet/enable-meet-api.webp)
14 +
15 + ![Google Meet API details page showing the API is enabled](/images/toolkits/googlemeet/meet-api-enabled.webp)
16 +
17 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
22 +
23 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the meetings.space.readonly scope selected](/images/toolkits/googlemeet/data-access-scopes.webp)
28 +
29 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30 +
31 + ```
32 + https://backend.composio.dev/api/v1/auth-apps/add
33 + ```
34 +
35 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36 +
37 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38 +
39 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40 +
41 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlemeet), go to **Auth Configs** → **Create** and select **Google Meet**.
46 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
47 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
49 +
50 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51 +
52 + ![Google consent screen asking to read information about Google Meet conferences](/images/toolkits/googlemeet/google-consent-screen.webp)
53 +
54 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default Google Meet auth config requests `https://www.googleapis.com/auth/meetings.space.created` and `https://www.googleapis.com/auth/meetings.space.settings`. For read-only access to meeting spaces and conference information, `meetings.space.readonly` is enough; it can't create meetings or change settings. Downloading recordings and transcripts can also need Drive scopes. See Google's [Meet scope reference](https://developers.google.com/workspace/meet/api/guides/authenticate-authorize).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +If you change the scopes later, reconnect the account so the user grants the new access.
63 +
64 +### Testing, publishing, and verification
65 +
66 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
67 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
69 +- **Data Access** shows which of your scopes Google treats as sensitive or restricted.
70 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
71
72 ## Why am I seeing "App is blocked" when connecting Google Meet?
73
74 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.
75
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).
76 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
77
78 ## Why am I getting "Google Meet API has not been used in project" error?
79
docs/content/toolkits/faq/googlephotos.md new
+62
@@ -0,0 +1,62 @@
1 +## How do I set up custom Google OAuth credentials for Google Photos?
2 +
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Photos Library API** (`photoslibrary.googleapis.com`), and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
13 +
14 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
15 +
16 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
17 +
18 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
19 +
20 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
21 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
22 +
23 + ```
24 + https://backend.composio.dev/api/v1/auth-apps/add
25 + ```
26 +
27 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
28 +
29 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
30 +
31 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
32 +
33 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlephotos), go to **Auth Configs** → **Create** and select **Google Photos**.
38 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
39 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
40 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
41 +
42 + ![Google consent screen asking to manage photos added by the app](/images/toolkits/googlephotos/google-consent-screen.webp)
43 +
44 + ![Google Photos auth config details with an Active connected account](/images/toolkits/googlephotos/composio-connected-account-active.webp)
45 +
46 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
47 +
48 +### Scopes
49 +
50 +The default Google Photos auth config requests `https://www.googleapis.com/auth/photoslibrary.readonly.appcreateddata` and `https://www.googleapis.com/auth/photoslibrary.edit.appcreateddata`. Google removed the library-wide read and sharing scopes in March 2025, so the Library API only sees albums and media your app created. A new OAuth app returns an empty album list until it creates content. To let users pick items from their whole library, Google offers the separate Photos Picker API. See Google's [Photos scope reference](https://developers.google.com/photos/overview/authorization) and [API changes](https://developers.google.com/photos/support/updates).
51 +
52 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
53 +
54 +If you change the scopes later, reconnect the account so the user grants the new access.
55 +
56 +### Testing, publishing, and verification
57 +
58 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
59 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
60 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
61 +- **Data Access** shows which of your scopes Google treats as sensitive or restricted.
62 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
docs/content/toolkits/faq/googlesheets.md
+81 -2
@@ -1,12 +1,91 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Sheets API**, and click **Enable**. The default scopes include Drive access, so enable the **Google Drive API** too if your tools search or manage spreadsheets through Drive. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Sheets API page in the Google Cloud API Library with the Enable button](/images/toolkits/googlesheets/enable-sheets-api.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the spreadsheets.readonly scope selected](/images/toolkits/googlesheets/data-access-scopes.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlesheets), go to **Auth Configs** → **Create** and select **Google Sheets**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Google Sheets in the toolkit search results](/images/toolkits/googlesheets/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Google Sheets auth config](/images/toolkits/googlesheets/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Google Sheets auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/googlesheets/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen asking to see all Google Sheets spreadsheets](/images/toolkits/googlesheets/google-consent-screen.webp)
63 +
64 + ![Google Sheets auth config details with an Active connected account](/images/toolkits/googlesheets/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +### Scopes
69 +
70 +The default Google Sheets auth config requests `https://www.googleapis.com/auth/spreadsheets`, `https://www.googleapis.com/auth/drive`, and `userinfo.email`. To only read spreadsheets by ID, `spreadsheets.readonly` is enough. Editing needs `spreadsheets`, and finding files through Drive needs a Drive scope. See Google's [Sheets scope reference](https://developers.google.com/workspace/sheets/api/scopes).
71 +
72 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
73 +
74 +If you change the scopes later, reconnect the account so the user grants the new access.
75 +
76 +### Testing, publishing, and verification
77 +
78 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
79 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
80 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
81 +- The default `drive` scope is restricted. A public app that requests it needs restricted-scope verification, which can include a security assessment.
82 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
83
84 ## Why am I seeing "App is blocked" when connecting Google Sheets?
85
86 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.
87
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).
88 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
89
90 ## Why am I getting "Google Sheets API has not been used in project" error?
91
docs/content/toolkits/faq/googleslides.md
+69 -2
@@ -1,12 +1,79 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Slides API**, and click **Enable**. The default scopes include Drive access, so enable the **Google Drive API** too if your tools search or manage presentations through Drive. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Slides API page in the Google Cloud API Library with the Enable button](/images/toolkits/googleslides/enable-slides-api.webp)
14 +
15 + ![Google Slides API details page showing the API is enabled](/images/toolkits/googleslides/slides-api-enabled.webp)
16 +
17 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
22 +
23 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the presentations.readonly scope selected](/images/toolkits/googleslides/data-access-scopes.webp)
28 +
29 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30 +
31 + ```
32 + https://backend.composio.dev/api/v1/auth-apps/add
33 + ```
34 +
35 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36 +
37 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38 +
39 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40 +
41 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googleslides), go to **Auth Configs** → **Create** and select **Google Slides**.
46 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
47 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
49 +
50 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51 +
52 + ![Google consent screen asking to see all Google Slides presentations](/images/toolkits/googleslides/google-consent-screen.webp)
53 +
54 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default Google Slides auth config requests `https://www.googleapis.com/auth/presentations`, `https://www.googleapis.com/auth/drive`, and `userinfo.email`. To only read presentations, `presentations.readonly` is enough. Reading a presentation you know the ID of doesn't need full Drive access. See Google's [Slides scope reference](https://developers.google.com/workspace/slides/api/scopes).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +If you change the scopes later, reconnect the account so the user grants the new access.
63 +
64 +### Testing, publishing, and verification
65 +
66 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
67 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
69 +- The default `drive` scope is restricted. A public app that requests it needs restricted-scope verification, which can include a security assessment.
70 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
71
72 ## Why am I seeing "App is blocked" when connecting Google Slides?
73
74 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.
75
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).
76 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
77
78 ## Why am I getting "Google Slides API has not been used in project" error?
79
docs/content/toolkits/faq/googlesuper.md
+83 -2
@@ -1,12 +1,93 @@
1 ## How do I set up custom Google OAuth credentials for Google Super?
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).
3 +Use your own Google OAuth app when you need scopes that Composio's managed Google Super app doesn't have approved, your app's name on Google's consent screen, or a dedicated API quota. One OAuth client in one Google Cloud project can serve Google Super and the single-product Google toolkits.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Go to **APIs & Services** → **Library** and enable the API for each Google product your tools use. There is no separate Google Super API. The default scopes cover the **Gmail API**, **Google Drive API**, **Google Docs API**, **Google Sheets API**, **Google Slides API**, **Google Calendar API**, **Google Tasks API**, **People API** (contacts), **Photos Library API**, **Google Analytics** APIs, and **Google Ads API**. If an API page shows **Manage**, it's already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Drive API page in the Google Cloud API Library with the Enable button](/images/toolkits/shared/VNt0egQy2o9O5i6LMd4JFpNcmAU.webp)
14 +
15 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
20 +
21 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the drive.metadata.readonly scope selected](/images/toolkits/shared/ch2L6hWRPSOigltUpRF7r9hyA.webp)
26 +
27 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
28 +
29 + ```
30 + https://backend.composio.dev/api/v1/auth-apps/add
31 + ```
32 +
33 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
34 +
35 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
36 +
37 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
38 +
39 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
40 +
41 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googlesuper), go to **Auth Configs** → **Create** and select **Google Super**. Enter a config name and click **Next**.
46 +
47 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
48 +
49 + ![Create Auth Config dialog with Google Super in the toolkit search results](/images/toolkits/googlesuper/composio-select-toolkit.webp)
50 +
51 + ![Config Name field for the new Google Super auth config](/images/toolkits/googlesuper/composio-config-name.webp)
52 +
53 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
54 +
55 + ![Google Super auth config form with Client ID, Client secret, the Composio redirect URI, and a selected scope](/images/toolkits/googlesuper/composio-auth-config-form.webp)
56 +
57 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
58 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**. The auth config's **Enabled** label doesn't mean an account is connected.
59 +
60 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
61 +
62 + ![Google consent screen for the Google Super connection](/images/toolkits/googlesuper/google-consent-screen.webp)
63 +
64 + ![Google Super auth config details with an Active connected account](/images/toolkits/googlesuper/composio-connected-account-active.webp)
65 +
66 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
67 +
68 +To add another Google toolkit later, enable its API in the same project and reuse this OAuth client in a new auth config.
69 +
70 +### Scopes
71 +
72 +The default Google Super auth config requests broad scopes across products: `https://mail.google.com/`, `drive`, `documents`, `spreadsheets`, `presentations`, `calendar`, `tasks`, `contacts.readonly`, `analytics`, `analytics.readonly`, `adwords`, the Photos `appcreateddata` read and edit scopes, `userinfo.email`, and `userinfo.profile`. Remove the ones for products you don't use, and prefer narrower scopes where they cover your tools. For example, listing Drive file metadata only needs `drive.metadata.readonly`. See Google's [OAuth 2.0 scope list](https://developers.google.com/identity/protocols/oauth2/scopes).
73 +
74 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
75 +
76 +If you change the scopes later, reconnect the account so the user grants the new access.
77 +
78 +### Testing, publishing, and verification
79 +
80 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
81 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
82 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
83 +- Several default scopes, including `https://mail.google.com/` and `drive`, are restricted. A public app that requests them needs restricted-scope verification, which can include a security assessment if your servers store or transmit that data.
84 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
85
86 ## Why am I seeing "App is blocked" when connecting Google Super?
87
88 Google can block consent when the OAuth client requests scopes that Google hasn't approved for that client. Follow [Google scope approvals and blocked-app troubleshooting](/docs/authentication/controlling-scopes#google-scope-approvals) to check the auth config and requested scopes. Toolkit defaults and scope recommendations don't establish the managed app's approved scopes.
89
9 -If a required scope isn't approved for the managed app, use your own Google OAuth app with the required verification and reconnect through a custom auth config. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and [Google OAuth setup](https://composio.dev/auth/googleapps).
90 +If a required scope isn't approved for the managed app, use your own Google OAuth app with the required verification and reconnect through a custom auth config. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and the setup steps above.
91
92 ## Why am I getting the "API has not been used in project" error?
93
docs/content/toolkits/faq/googletasks.md
+69 -2
@@ -1,12 +1,79 @@
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).
3 +Use your own Google OAuth app when you want your app's name on Google's consent screen, a dedicated API quota, or scopes that Composio's managed app doesn't cover.
4 +
5 +### Create the Google OAuth app
6 +
7 +1. Open the [Google Cloud console](https://console.cloud.google.com/) and select the project that will own the OAuth app, or create one.
8 +
9 + ![Google Cloud project picker with the OAuth app's project selected](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
10 +
11 +2. Go to **APIs & Services** → **Library**, search for **Google Tasks API**, and click **Enable**. If the API page shows **Manage**, the API is already enabled. Enabling an API needs project permissions; ask your project admin if you can't.
12 +
13 + ![Google Tasks API page in the Google Cloud API Library with the Enable button](/images/toolkits/googletasks/enable-tasks-api.webp)
14 +
15 + ![Google Tasks API details page showing the API is enabled](/images/toolkits/googletasks/tasks-api-enabled.webp)
16 +
17 +3. Go to **Google Auth Platform** → **Branding**. If you see **Get started**, enter the app name, user support email, and developer contact email, then save.
18 +
19 + ![Google Auth Platform Branding page with the app name and user support email fields](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
20 +
21 +4. Under **Audience**, choose the user type. **Internal** limits sign-in to accounts in your Google Workspace organization. **External** allows any Google account. An External app starts in **Testing**; add every account that will connect under **Test users**.
22 +
23 + ![Google Auth Platform Audience page showing Testing status, the External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
24 +
25 +5. Under **Data Access**, click **Add or remove scopes** and add the scopes your auth config will request (see **Scopes** below). Paste any scope missing from the list under **Manually add scopes** and click **Add to table**. Click **Update**, then **Save**.
26 +
27 + ![Data Access scope picker with the tasks.readonly scope selected](/images/toolkits/googletasks/data-access-scopes.webp)
28 +
29 +6. Under **Clients**, click **Create client**. Set **Application type** to **Web application**, name the client, and add this URI under **Authorized redirect URIs**:
30 +
31 + ```
32 + https://backend.composio.dev/api/v1/auth-apps/add
33 + ```
34 +
35 + It must exactly match the `oauth_redirect_uri` field of your Composio auth config.
36 +
37 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
38 +
39 + ![Create OAuth client ID form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
40 +
41 +7. Click **Create**. Copy the **Client ID** and **Client secret** before you close the dialog, and store the secret privately.
42 +
43 +### Create the auth config in Composio
44 +
45 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-googletasks), go to **Auth Configs** → **Create** and select **Google Tasks**.
46 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the **Client ID** and **Client secret**, and leave **Redirect URI** set to `https://backend.composio.dev/api/v1/auth-apps/add`.
47 +3. Choose the scopes your tools need, matching the ones you added under **Data Access**, then click **Create Auth Config**.
48 +4. Click **Connect Account**, sign in with a Google account that can use the app (a test user while the app is in **Testing**), and approve the consent screen. Under **Accounts**, confirm the connection shows **Active**.
49 +
50 + ![Google's unverified-app notice for an app in Testing](/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp)
51 +
52 + ![Google consent screen asking to view tasks](/images/toolkits/googletasks/google-consent-screen.webp)
53 +
54 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
55 +
56 +### Scopes
57 +
58 +The default Google Tasks auth config requests `https://www.googleapis.com/auth/tasks`. If your tools only read task lists and tasks, use `tasks.readonly` instead; it can't create, complete, change, or delete tasks. See Google's [Tasks scope reference](https://developers.google.com/workspace/tasks/auth).
59 +
60 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
61 +
62 +If you change the scopes later, reconnect the account so the user grants the new access.
63 +
64 +### Testing, publishing, and verification
65 +
66 +- While an External app is in **Testing**, only test users can connect, and Google can show them an unverified-app notice. Google generally expires their authorizations after seven days, so they need to reconnect.
67 +- To let any Google account connect, publish the app under **Audience**. Publishing doesn't verify the app.
68 +- Public apps that request sensitive or restricted scopes generally need Google's OAuth verification. Check **Google Auth Platform** → **Verification Center**. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
69 +- **Data Access** shows which of your scopes Google treats as sensitive or restricted.
70 +- If Google blocks sign-in, check the app's audience, the test user list, the requested scopes, and your Workspace admin's app access policy.
71
72 ## Why am I seeing "App is blocked" when connecting Google Tasks?
73
74 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.
75
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).
76 +Remove the additional scopes from your auth config, or create your own OAuth app and submit the scopes for verification, as described in the setup steps above.
77
78 ## Why am I getting "Google Tasks API has not been used in project" error?
79
docs/content/toolkits/faq/gorgias.md new
+56
@@ -0,0 +1,56 @@
1 +## How do I connect Gorgias with Composio-managed OAuth?
2 +
3 +With managed OAuth you don't need your own Gorgias app or client credentials. The flow starts in Gorgias and finishes in Composio.
4 +
5 +1. In Gorgias, go to **Settings** > **App Store** > **All Apps**, search for **Composio**, open it, and click **Authorize**.
6 +
7 + ![Gorgias All apps search results showing Composio](/images/toolkits/gorgias/app-store-search.webp)
8 +
9 + ![Composio app page in the Gorgias App Store with the Authorize button](/images/toolkits/gorgias/composio-app-authorize.webp)
10 +2. In the Composio dashboard, open your project's **Toolkits** page, search for **Gorgias**, and click **Add to Project**.
11 +
12 + ![Composio Toolkits page with the Gorgias panel and Add to Project button](/images/toolkits/gorgias/add-to-project.webp)
13 +3. Name the auth config, click **Next**, choose **OAuth 2.0** > **Composio Managed**, and click **Create Gorgias Auth Config**.
14 +
15 + ![Gorgias auth config Config Name field with the Next button](/images/toolkits/gorgias/config-name.webp)
16 +
17 + ![Gorgias auth config with OAuth 2.0 and Composio Managed selected](/images/toolkits/gorgias/managed-oauth.webp)
18 +4. Open the auth config and click **Connect Account**. Enter your Gorgias subdomain: for `acme.gorgias.com`, enter `acme`.
19 +
20 + ![Composio connect screen asking for the Gorgias subdomain](/images/toolkits/gorgias/enter-subdomain.webp)
21 +5. Review the Gorgias permission screen, click **Authorize**, and confirm the account shows as **Active** in Composio.
22 +
23 +## How do I set up custom OAuth credentials for Gorgias?
24 +
25 +Use your own Gorgias OAuth app only if your organization must use its own client credentials. This requires a [Gorgias Partner Portal](https://partners.gorgias.com/login) account, which is separate from your Gorgias helpdesk login.
26 +
27 +### Create the Gorgias app
28 +
29 +1. In the Partner Portal, click **Create New App**.
30 +
31 + ![Gorgias Partner Portal My Apps page with the Create New App button](/images/toolkits/gorgias/partner-portal-my-apps.webp)
32 +2. Enter an app name (such as `Composio Integration`), an app tagline, an app icon (required), and your app URL.
33 +3. In **Redirect URLs**, paste `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
34 +
35 + ![Gorgias Create New App form with the Composio redirect URL](/images/toolkits/gorgias/create-app-redirect-url.webp)
36 +4. Select the OAuth scopes your integration needs, then click **Create**.
37 +5. Open the app in the Partner Portal and copy the **Client ID** and **Client Secret**.
38 +
39 + ![Gorgias app OAuth2 section with redacted Client ID and Client Secret](/images/toolkits/gorgias/oauth-credentials.webp)
40 +
41 +### Create the auth config in Composio
42 +
43 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Gorgias**.
44 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
45 +3. Paste the **Client ID** and **Client Secret**, enter the same scopes you selected in the Gorgias app, then click **Create Gorgias Auth Config**.
46 +4. Click **Connect Account**, enter your Gorgias subdomain (`acme` for `acme.gorgias.com`), authorize, and confirm the account shows as **Active**.
47 +
48 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
49 +
50 +### Scopes
51 +
52 +The default auth config requests read and write scopes for account, users, customers, tickets, custom fields, events, integrations, jobs, macros, rules, satisfaction surveys, tags, and apps, plus `statistics:read`, `openid`, `email`, `profile`, and `offline`. Keep the scopes in the Gorgias app and the auth config the same, and request only what your integration uses.
53 +
54 +### API base URL
55 +
56 +Composio sends Gorgias API calls to `https://{subdomain}.gorgias.com/api/`, using the subdomain you enter when you connect.
docs/content/toolkits/faq/highlevel_location.md new
+73
@@ -0,0 +1,73 @@
1 +## How do I set up OAuth credentials for HighLevel Location?
2 +
3 +HighLevel Location has no Composio-managed OAuth app, so to connect with OAuth you create your own app in the HighLevel Marketplace. The Location toolkit connects to a single sub-account (HighLevel calls these locations). For agency-wide access, use the HighLevel Agency toolkit instead.
4 +
5 +### Create the HighLevel Marketplace app
6 +
7 +1. Sign in to the [HighLevel Marketplace](https://marketplace.gohighlevel.com/) with a developer account, click **My apps**, then click **Create app**.
8 +
9 + ![HighLevel Marketplace My apps page with the Create app button](/images/toolkits/highlevel_location/my-apps-create-app.webp)
10 +2. In the **Start from scratch** window, set:
11 + - **App name**: any name you'll recognize, such as `Composio Location`.
12 + - **App type**: **Private** for testing and small pilots, or **Public** if you plan to list the app.
13 + - **Who is the target user of the app?**: **Sub-Account**. The Location toolkit requires this.
14 + - **Who can install the app?**: **Everyone**.
15 + - **Listing type**: **White-label**.
16 +
17 + ![Start from scratch form with Private, Sub-Account, Everyone and White-label selected](/images/toolkits/highlevel_location/start-from-scratch.webp)
18 +3. Click **Create app**.
19 +4. Open **Advanced Settings** > **Auth**. In **Redirect URL**, paste `https://backend.composio.dev/api/v1/auth-apps/add` and click **+ Add**. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
20 +
21 + ![HighLevel Auth settings with the Composio redirect URL under Added redirect URLs](/images/toolkits/highlevel_location/redirect-url-added.webp)
22 +5. On the same page, under **Scopes**, search for and tick each scope you need, such as `locations.readonly`. A note like "8 scopes unavailable" is expected: Agency-only scopes are hidden for Sub-Account apps.
23 +
24 + ![HighLevel Scopes section with locations.readonly selected](/images/toolkits/highlevel_location/select-scopes.webp)
25 +6. Open **Manage** > **Secrets**. Under **Client keys**, click **+ Add**, name the key, and click **Add**.
26 +
27 + ![HighLevel Client keys section under Manage, Secrets](/images/toolkits/highlevel_location/client-keys.webp)
28 +
29 + ![HighLevel Add a client key dialog](/images/toolkits/highlevel_location/add-client-key.webp)
30 +7. Copy the **Client ID** and **Client secret** from the new row.
31 +
32 +A private app active in more than 5 external agencies can't be installed again until you publish it.
33 +
34 +### Create the auth config in Composio
35 +
36 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **HighLevel Location** (not HighLevel Agency or HighLevel MCP).
37 +
38 + ![Composio Auth Configs page with the Create button](/images/toolkits/highlevel_location/composio-auth-configs.webp)
39 +
40 + ![Create Auth Config search results showing HighLevel Location](/images/toolkits/highlevel_location/composio-search-highlevel.webp)
41 +2. Name the config, click **Next**, and choose **OAuth 2.0**.
42 +
43 + ![HighLevel Location auth config Config Name field](/images/toolkits/highlevel_location/config-name.webp)
44 +
45 + ![HighLevel Location auth config with OAuth 2.0 selected and redacted Client id and Client secret](/images/toolkits/highlevel_location/oauth-credentials.webp)
46 +3. Paste the **Client id** and **Client secret**, select the same scopes you chose in HighLevel, and click **Create Auth Config**.
47 +
48 + ![HighLevel Location auth config with the Composio redirect URI and locations.readonly scope](/images/toolkits/highlevel_location/redirect-uri-and-scopes.webp)
49 +4. Click **Connect Account** and open the generated link. Sign in to HighLevel, tick the sub-account to connect in **Select Sub-Account**, click **Continue**, then click **Allow & install**. Confirm the account shows as **Active**.
50 +
51 + ![HighLevel Location auth config with the Connect Account button](/images/toolkits/highlevel_location/connect-account.webp)
52 +
53 + ![HighLevel sign-in page](/images/toolkits/highlevel_location/sign-in.webp)
54 +
55 + ![HighLevel Select Sub-Account window with a sub-account ticked and Continue enabled](/images/toolkits/highlevel_location/select-sub-account.webp)
56 +
57 + ![HighLevel Install confirmation page with the Allow & install button](/images/toolkits/highlevel_location/install-confirmation.webp)
58 +
59 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
60 +
61 +### Scopes
62 +
63 +The default auth config requests `locations.readonly`. Customers approve every scope at install time, so request only what your integration uses. If an action fails with insufficient permissions, add the missing scope in both HighLevel and the auth config, then reconnect.
64 +
65 +### Troubleshooting
66 +
67 +- **No sub-accounts listed when connecting**: check that the app's target user is **Sub-Account** and that the HighLevel user you signed in with can access at least one sub-account.
68 +- **Redirect URI mismatch**: the URL in HighLevel and in the auth config must be identical.
69 +
70 +### Revoke access
71 +
72 +- In Composio, delete the connected account from the auth config, or disable the auth config.
73 +- In HighLevel, uninstall the app from the sub-account's installed Marketplace apps. This revokes access immediately.
docs/content/toolkits/faq/hubspot.md
+31 -1
@@ -14,7 +14,37 @@ With Composio-managed HubSpot auth, you can only remove optional scopes that are
14
15 You cannot add new scopes to the managed app, and you cannot remove scopes that are non-optional for that managed auth config. If you need a different scope set, create a custom HubSpot OAuth app and configure those scopes there.
16
17 -Use your own HubSpot OAuth app when you need a different scope set, your own app name and branding on the consent screen, tighter control over app review and rollout, or a production setup owned by your team. For setup steps, see [How to create OAuth credentials for HubSpot](https://composio.dev/auth/hubspot).
17 +Use your own HubSpot OAuth app when you need a different scope set, your own app name and branding on the consent screen, tighter control over app review and rollout, or a production setup owned by your team. Setup steps are in the next question.
18 +
19 +## How do I set up custom OAuth credentials for HubSpot?
20 +
21 +Use your own HubSpot app when you need your own scope set, app name, or consent screen, or when the unverified-app warning blocks your rollout.
22 +
23 +### Create the HubSpot app
24 +
25 +1. Create a developer account in the [HubSpot developer portal](https://developers.hubspot.com/get-started). HubSpot public apps must belong to a developer account.
26 +2. In the developer account, open **Apps** and click **Create App**.
27 +
28 + ![HubSpot Apps page with the Create app button](/images/toolkits/hubspot/create-app.webp)
29 +3. Enter the app name, description, logo, and support information. Users see these details when they authorize the app.
30 +
31 + ![HubSpot app App Info tab with name, logo and description fields](/images/toolkits/hubspot/app-info.webp)
32 +4. Open the **Auth** tab and copy the **Client ID** and **Client Secret**.
33 +5. In **Redirect URLs**, below the credentials, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
34 +6. Enable the scopes your integration needs, marking each as required or optional to match how you'll list it in Composio (see the scope questions below).
35 +
36 +### Create the auth config in Composio
37 +
38 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **HubSpot**.
39 +2. Set the authentication type to **OAuth2** (not Bearer Token) and choose **Use your own developer authentication**.
40 +
41 + ![Use your own developer credentials toggle turned on in the Composio auth config](/images/toolkits/hubspot/use-own-credentials.webp)
42 +3. Paste the **Client ID** and **Client Secret**. Set `scopes` and `optional_scopes` to match the required and optional scopes in your HubSpot app, then click **Create HubSpot Auth Config**.
43 +
44 + ![Composio auth config Client id and Client secret fields](/images/toolkits/hubspot/composio-client-fields.webp)
45 +4. Click **Connect Account**, authorize the app in HubSpot, and confirm the account shows as **Active**.
46 +
47 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. The default auth config requests a broad CRM scope set in `scopes` and `transactional-email automation marketing.campaigns.read marketing.campaigns.write` in `optional_scopes`. Every requested scope must be enabled in your HubSpot app, or HubSpot rejects the authorization. See HubSpot's [scopes reference](https://developers.hubspot.com/docs/apps/developer-platform/build-apps/authentication/scopes) for the full list.
48
49 ## How do scopes work in HubSpot?
50
docs/content/toolkits/faq/instantly.md
+32 -2
@@ -1,3 +1,33 @@
1 -## How do I set up custom OAuth credentials for Instantly?
1 +## How do I connect Instantly with an API key?
2
3 -For a step-by-step guide on creating and configuring your own Instantly OAuth credentials with Composio, see [How to create OAuth credentials for Instantly](https://composio.dev/auth/instantly).
3 +Instantly doesn't support OAuth, so you connect with an Instantly API key. You don't need a client ID, client secret, redirect URL, or OAuth scopes.
4 +
5 +### Create the API key in Instantly
6 +
7 +1. Sign in to Instantly and go to **Settings** > **Integrations** > **API Keys**.
8 +
9 + ![Instantly Settings, Integrations, API Keys page with the Create API Key button](/images/toolkits/instantly/api-keys-page.webp)
10 +2. Create a new API key and select its scopes (see Scopes below). Use a v2 key; v1 keys no longer work.
11 +
12 + ![Instantly Create API Key form with a name and scopes](/images/toolkits/instantly/create-api-key.webp)
13 +3. Copy the key and store it in a secret manager.
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Instantly**.
18 +
19 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
20 +
21 + ![Create Auth Config search results showing Instantly with API_KEY](/images/toolkits/instantly/composio-search-instantly.webp)
22 +2. Keep the authentication type as **API Key** and create the auth config.
23 +
24 + ![Instantly auth config form with API KEY as the authentication method](/images/toolkits/instantly/api-key-auth-config.webp)
25 +3. Click **Connect Account**, paste your Instantly API key, and confirm the account shows as **Active**.
26 +
27 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. Composio sends the key as a bearer token to `https://api.instantly.ai`.
28 +
29 +### Scopes
30 +
31 +Instantly API keys are scoped when you create them, and you can't change a key's scopes afterward. To change permissions, create a new key and reconnect the account with it.
32 +
33 +Scopes follow a `resource:action` pattern, such as `campaigns:read`, `leads:create`, or `analytics:read`. Resources include `campaigns`, `leads`, `lead_lists`, `accounts`, `ai_agents`, `inbox_tests`, `webhooks`, and `api_keys`. `all:all` grants full read, create, update, and delete access to every endpoint. Prefer resource-level scopes, and use `all:all` only if your integration needs everything.
docs/content/toolkits/faq/jira.md
+41 -1
@@ -1,6 +1,46 @@
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).
3 +Use your own Atlassian OAuth 2.0 (3LO) app when you want the consent screen to show your app name and to control which scopes it can grant.
4 +
5 +### Create the Atlassian app
6 +
7 +1. Sign in to the [Atlassian developer console](https://developer.atlassian.com/console/myapps) (create a developer account if you don't have one).
8 +2. Click **Create** → **OAuth 2.0 integration**, name the app, and click **Create**.
9 +
10 + ![Atlassian developer console form to create a new OAuth 2.0 (3LO) integration](/images/toolkits/jira/create-oauth-integration.webp)
11 +
12 +3. Open **Authorization** in the sidebar and click **Configure** next to OAuth 2.0 (3LO). Set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add` and click **Save changes**. It must exactly match the auth config's `oauth_redirect_uri` field.
13 +
14 + ![Atlassian OAuth 2.0 (3LO) Callback URL set to the Composio redirect URI](/images/toolkits/shared/kvxWqV89dZHkBHkJJGy5XQdhGko.webp)
15 +
16 +4. Open **Permissions**. Click **Add** next to the **Jira API**, then **Configure**, and add every classic or granular scope your auth config will request (see below). Add the **User Identity API** too if you need user profile scopes. Click **Save**.
17 +
18 + ![Atlassian app Permissions page listing APIs, including the Jira API](/images/toolkits/jira/permissions-apis.webp)
19 +
20 + ![Jira API scope page with Classic scopes, Granular scopes, and Edit Scopes](/images/toolkits/jira/api-scopes.webp)
21 +
22 +5. Open **Distribution** and set the status to **Sharing** if users outside your own Atlassian account will connect. Atlassian asks for a vendor name, privacy policy URL, and a personal data declaration.
23 +6. Open **Settings** and copy the **Client ID** and **Secret** under **Authentication details**.
24 +
25 +### Create the auth config in Composio
26 +
27 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-jira), go to **Auth Configs** → **Create** and select **Jira**.
28 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Secret.
29 +
30 +3. Remove any scopes you didn't add on the app's **Permissions** tab, then click **Create Auth Config**.
31 +4. Click **Connect Account** and enter your site's **subdomain**: the part before `.atlassian.net` in your browser's address bar. For `https://acme.atlassian.net`, enter `acme`.
32 +
33 +5. Approve the consent screen and check that the account shows **Active**.
34 +
35 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
36 +
37 +### Scopes
38 +
39 +The default auth config requests the classic scopes `read:jira-work`, `write:jira-work`, `read:jira-user`, `manage:jira-project`, `manage:jira-configuration`, `manage:jira-webhook`, and `manage:jira-data-provider`; Jira Service Management scopes (`read:servicedesk-request`, `write:servicedesk-request`, `manage:servicedesk-customer`, `read:servicemanagement-insight-objects`); Jira Software granular scopes for sprints and boards; `read:project:jira` and `read:issue-type-scheme:jira`; and `offline_access`. The service management scopes live under the **Jira Service Management API** on the **Permissions** tab, so add that API too or remove those scopes from the auth config. See Atlassian's [Jira scopes reference](https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/).
40 +
41 +Every scope the auth config requests, apart from `offline_access`, must also be added on the app's **Permissions** tab. If one is missing, the connection fails with a "Something went wrong" error. Keep `offline_access` in the auth config's scopes: Atlassian only issues a refresh token when it's requested, and without one the connection stops working when the access token expires.
42 +
43 +![Atlassian "Something went wrong" page listing Jira scopes that haven't been added to the app](/images/toolkits/jira/missing-scopes-error.webp)
44
45 ## What is the difference between JQL GET, JQL POST, and Search Issues?
46
docs/content/toolkits/faq/linear.md new
+30
@@ -0,0 +1,30 @@
1 +## How do I set up custom OAuth credentials for Linear?
2 +
3 +Use your own Linear OAuth application when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Linear app
6 +
7 +1. Sign in to [Linear](https://linear.app/) and open your workspace's [API settings](https://linear.app/settings/api).
8 +2. Create a new OAuth application and give it a name.
9 +
10 + ![Linear API settings page with the New OAuth application button](/images/toolkits/linear/api-settings.webp)
11 +3. In **Callback URLs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
12 +4. Fill in the remaining required fields and create the application.
13 +5. On the application page that opens, copy the **Client ID** and **Client Secret**.
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Linear**.
18 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
19 +3. Paste the **Client ID** and **Client Secret**, adjust the scopes if needed, then click **Create Linear Auth Config**.
20 +4. Click **Connect Account**, click **Authorize** on Linear's consent screen, and confirm the account shows as **Active**.
21 +
22 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
23 +
24 +### Scopes
25 +
26 +The default auth config requests `read`, `write`, `issues:create`, and `comments:create`. Remove any you don't need from the auth config's **Scopes** field. Linear also offers an `admin` scope; add it only if your integration needs admin access.
27 +
28 +## Can I connect Linear with an API key?
29 +
30 +Yes. Create an auth config with the **API Key** auth type. Each user creates a personal API key in Linear under **Settings** > **Security & access** > **Personal API keys** and pastes it when connecting. Keys start with `lin_api_`.
docs/content/toolkits/faq/linkedin.md
+27 -1
@@ -1,6 +1,32 @@
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).
3 +Use your own LinkedIn app for production, to avoid the shared app's rate limits and to show your own app name and logo on the consent screen.
4 +
5 +### Create the LinkedIn app
6 +
7 +1. Go to [LinkedIn Developers](https://developer.linkedin.com/) and click **Create app**.
8 +
9 + ![LinkedIn Developers home page with the Create app button](/images/toolkits/linkedin/create-app.webp)
10 +2. Enter the app name, your company's LinkedIn page URL, and the logo users see when they authorize. Agree to the legal terms and click **Create app**.
11 +
12 + ![LinkedIn Create an app form with app name, LinkedIn Page, logo and legal agreement](/images/toolkits/linkedin/app-details.webp)
13 +3. Open the app's **Auth** tab. Under **Application credentials**, copy the **Client ID** and **Client Secret**.
14 +
15 + ![LinkedIn app Auth tab with Application credentials showing Client ID and Primary Client Secret](/images/toolkits/linkedin/auth-credentials.webp)
16 +4. In the same tab, under **OAuth 2.0 settings**, add the authorized redirect URL `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
17 +
18 +### Create the auth config in Composio
19 +
20 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **LinkedIn**.
21 +2. Keep the authentication type as **OAuth2** and choose **Use your own developer authentication**.
22 +3. Paste the **Client ID** and **Client Secret**, then click **Create LinkedIn Auth Config**.
23 +4. Click **Connect Account**, approve access in LinkedIn, and confirm the account shows as **Active**.
24 +
25 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
26 +
27 +### Scopes
28 +
29 +The default auth config requests `openid`, `profile`, `email`, and `w_member_social`. Your LinkedIn app must have access to every scope you request. LinkedIn restricts some scope combinations; see the scope question below.
30
31 ## Why am I getting 429 rate limit errors on LinkedIn?
32
docs/content/toolkits/faq/microsoft_advertising.md new
+72
@@ -0,0 +1,72 @@
1 +## How do I set up custom OAuth credentials for Microsoft Advertising?
2 +
3 +Microsoft Advertising has no Composio-managed app, so you need your own Microsoft Entra ID app registration and a production developer token to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**). Microsoft's Advertising app registration guide calls for this option, and Advertising accepts both work or school and personal Microsoft identities.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +
11 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/shared/1iIDmPCxFpXJP7zt73rUtnOLkxc.webp)
12 +
13 +4. On the app's **Overview** page, copy the **Application (client) ID**.
14 +
15 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
16 +
17 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
18 +
19 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
20 +
21 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
22 +
23 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
24 +
25 +7. Keep **Allow public client flows** disabled on the **Authentication** page. This is a confidential Web client.
26 +8. Sign in to [Microsoft Advertising developer settings](https://ads.microsoft.com/cc/Settings/DevSettings) with a Super Admin account and copy the production **Developer token** (request one if you don't have it). It is separate from the client secret. Sandbox tokens don't work with this toolkit. Don't regenerate a working token just to add another connection.
27 +
28 + ![Microsoft Advertising Developer settings page with the developer token censored](/images/toolkits/microsoft_advertising/developer-settings.webp)
29 +
30 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
31 +
32 +### Create the auth config in Composio
33 +
34 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Advertising**. Enter a config name and click **Next**.
35 +
36 + ![Composio Auth Configs page with the Create button](/images/toolkits/microsoft_advertising/composio-auth-configs.webp)
37 +
38 + ![Create Auth Config dialog with Microsoft Advertising selected](/images/toolkits/microsoft_advertising/composio-toolkit-picker.webp)
39 +
40 + ![Auth config name field with the Next button](/images/toolkits/microsoft_advertising/composio-config-name.webp)
41 +
42 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
43 +
44 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_advertising/composio-oauth-credentials.webp)
45 +
46 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
47 +
48 + ![Composio auth config with the v1 redirect URI and the msads.manage and offline_access scopes](/images/toolkits/microsoft_advertising/composio-scopes.webp)
49 +
50 +4. Open the auth config and click **Connect Account**. Paste the production developer token (`generic_secret`), not the client secret, and click **Connect Account**. Sign in with the Microsoft identity that is already a user of the advertising account, complete any MFA, and review the consent prompt before accepting.
51 +
52 + ![Microsoft Advertising auth config page with the Connect Account button](/images/toolkits/microsoft_advertising/composio-connect-account.webp)
53 +
54 + ![Composio connection form with an empty Developer Token field](/images/toolkits/microsoft_advertising/developer-token-field.webp)
55 +
56 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/microsoft_advertising/microsoft-account-picker.webp)
57 +
58 + ![Microsoft consent prompt for Microsoft Advertising API access and continued access](/images/toolkits/microsoft_advertising/microsoft-consent.webp)
59 +
60 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
61 +
62 + ![Connected Accounts tab with the Microsoft Advertising account showing Active](/images/toolkits/microsoft_advertising/connected-account-active.webp)
63 +
64 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
65 +
66 +### Scopes
67 +
68 +The default auth config requests `https://ads.microsoft.com/msads.manage` and `offline_access`. The connected identity's Advertising account roles still decide what it can view or change. See Microsoft's [OAuth consent](https://learn.microsoft.com/en-us/advertising/guides/authentication-oauth-consent?view=bingads-13) guide.
69 +
70 +### Why do I get `AADSTS650052`?
71 +
72 +For an organizational identity, Microsoft can require tenant-admin setup before Advertising authorization works. Ask the tenant admin to review the **Application behavior** section of Microsoft's Advertising app registration guide.
docs/content/toolkits/faq/microsoft_bookings.md new
+74
@@ -0,0 +1,74 @@
1 +## How do I set up custom OAuth credentials for Microsoft Bookings?
2 +
3 +Microsoft Bookings has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). Bookings doesn't support personal Microsoft accounts.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Bookings.Read.All`, `BookingsAppointment.ReadWrite.All`, `Bookings.ReadWrite.All`, `Bookings.Manage.All`, `offline_access`, and `User.Read`, or only the subset your workflow uses, then click **Add permissions**.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
25 +
26 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp)
27 +
28 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp)
29 +
30 + ![Microsoft Graph delegated permissions with Bookings.Read.All selected](/images/toolkits/microsoft_bookings/bookings-read-all-permission.webp)
31 +
32 + ![Configured permissions list with the Bookings.Read.All delegated permission](/images/toolkits/microsoft_bookings/configured-permissions.webp)
33 +
34 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
35 +
36 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
37 +
38 +### Create the auth config in Composio
39 +
40 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Bookings**. Enter a config name and click **Next**.
41 +
42 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/SKmiRvkpLj1fiXUXAPnkjJ2Ug.webp)
43 +
44 + ![Create Auth Config dialog with Microsoft Bookings selected](/images/toolkits/microsoft_bookings/composio-toolkit-picker.webp)
45 +
46 + ![Auth config name field with the Next button](/images/toolkits/microsoft_bookings/composio-config-name.webp)
47 +
48 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
49 +
50 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_bookings/composio-oauth-credentials.webp)
51 +
52 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
53 +
54 + ![Composio auth config with the v1 redirect URI and the Bookings.Read.All, offline_access and User.Read scopes](/images/toolkits/microsoft_bookings/composio-scopes.webp)
55 +
56 +4. Open the auth config and click **Connect Account**. Keep **Microsoft Tenant** (`issuer`) as `organizations` to allow any work or school account, or enter your **Directory (tenant) ID** or a verified domain to restrict sign-in to one tenant. Click **Connect Account**, sign in with a work or school account that has Bookings enabled, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
57 +
58 + ![Microsoft Bookings auth config panel with the Connect Account button](/images/toolkits/microsoft_bookings/composio-connect-account.webp)
59 +
60 + ![Composio connection form with Microsoft Tenant set to organizations](/images/toolkits/microsoft_bookings/microsoft-tenant-field.webp)
61 +
62 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/microsoft_bookings/microsoft-account-picker.webp)
63 +
64 + ![Microsoft consent prompt for reading bookings information with organization consent unchecked](/images/toolkits/microsoft_bookings/microsoft-consent.webp)
65 +
66 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
67 +
68 + ![Connected Accounts tab with the Microsoft Bookings account showing Active](/images/toolkits/microsoft_bookings/connected-account-active.webp)
69 +
70 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
71 +
72 +### Scopes
73 +
74 +The default auth config requests `Bookings.Read.All`, `BookingsAppointment.ReadWrite.All`, `Bookings.ReadWrite.All`, `Bookings.Manage.All`, `offline_access`, and `User.Read`. Listing booking businesses needs only `Bookings.Read.All`; appointment changes need more. See Microsoft's [list bookingBusinesses](https://learn.microsoft.com/en-us/graph/api/bookingbusiness-list?view=graph-rest-1.0) reference.
docs/content/toolkits/faq/microsoft_entra_id.md new
+77
@@ -0,0 +1,77 @@
1 +## How do I set up custom OAuth credentials for Microsoft Entra ID?
2 +
3 +Microsoft Entra ID has no Composio-managed app, so you need your own app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant).
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `User.Read` and `offline_access`, plus the directory permissions your workflow needs, then click **Add permissions**.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
25 +
26 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp)
27 +
28 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp)
29 +
30 + ![Configured Microsoft Graph permissions with the User.Read delegated permission details](/images/toolkits/microsoft_entra_id/user-read-details.webp)
31 +
32 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
33 +
34 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
35 +
36 +### Create the auth config in Composio
37 +
38 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Entra ID**. Enter a config name and click **Next**.
39 +
40 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/jkkvkcA7QbpyHuUXzLJNP0lvxLo.webp)
41 +
42 + ![Create Auth Config dialog with Microsoft Entra ID selected](/images/toolkits/microsoft_entra_id/composio-toolkit-picker.webp)
43 +
44 + ![Auth config name field with the Next button](/images/toolkits/microsoft_entra_id/composio-config-name.webp)
45 +
46 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
47 +
48 + ![Composio auth config form with OAuth 2.0 selected and empty Client id and Client secret fields](/images/toolkits/microsoft_entra_id/composio-oauth-credentials.webp)
49 +
50 + ![Composio auth config with the v1 redirect URI, Microsoft cloud environment set to global, and the User.Read and offline_access scopes](/images/toolkits/microsoft_entra_id/composio-cloud-and-scopes.webp)
51 +
52 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
53 +4. Open the auth config and click **Connect Account**. Sign in to the tenant that holds the directory you want to use and review the consent prompt. Directory administration also needs the matching Entra roles on the signed-in account. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
54 +
55 + ![Microsoft Entra ID auth config panel with the Connect Account button](/images/toolkits/microsoft_entra_id/composio-connect-account.webp)
56 +
57 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/19hfD30iOecyW2OUu49tHoR7H4.webp)
58 +
59 + ![Composio page confirming the Microsoft Entra ID connection](/images/toolkits/microsoft_entra_id/connection-success.webp)
60 +
61 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
62 +
63 + ![Connected Accounts tab with the Microsoft Entra ID account showing Active](/images/toolkits/microsoft_entra_id/connected-account-active.webp)
64 +
65 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
66 +
67 +### Scopes
68 +
69 +The default auth config requests `User.Read` and `offline_access`. Directory operations need operation-specific Graph permissions and roles. See Microsoft's [get user](https://learn.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0) reference.
70 +
71 +### Restrict sign-in to one tenant
72 +
73 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
74 +
75 +### App-only access (client credentials)
76 +
77 +Microsoft Entra ID also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`issuer`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent. In this mode the tenant field also accepts a verified tenant domain.
docs/content/toolkits/faq/microsoft_power_bi.md new
+72
@@ -0,0 +1,72 @@
1 +## How do I set up custom OAuth credentials for Microsoft Power BI?
2 +
3 +Microsoft Power BI has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant).
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Power BI Service**, and choose **Delegated permissions**. Add `Dataset.Read.All`, `Report.Read.All`, `Dashboard.Read.All`, `Workspace.Read.All`, `Content.Create`, and `Dataflow.Read.All`, or only the subset your workflow uses. Click **Add permissions**.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
25 +
26 + ![Request API permissions panel with Power BI Service under Microsoft APIs](/images/toolkits/microsoft_power_bi/power-bi-service-api.webp)
27 +
28 + ![Power BI Service delegated permissions with Workspace.Read.All selected](/images/toolkits/microsoft_power_bi/workspace-read-all-permission.webp)
29 +
30 + ![Configured permissions list on the app's API permissions page](/images/toolkits/microsoft_power_bi/configured-permissions.webp)
31 +
32 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
33 +
34 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
35 +
36 +![Entra Authentication page listing the Composio Web redirect URI](/images/toolkits/microsoft_power_bi/registered-redirect-uri.webp)
37 +
38 +### Create the auth config in Composio
39 +
40 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Power BI**. Enter a config name and click **Next**.
41 +
42 + ![Composio Auth Configs page with the Create button](/images/toolkits/microsoft_power_bi/composio-auth-configs.webp)
43 +
44 + ![Create Auth Config dialog with Microsoft Power BI selected](/images/toolkits/microsoft_power_bi/composio-toolkit-picker.webp)
45 +
46 + ![Auth config name field with the Next button](/images/toolkits/microsoft_power_bi/composio-config-name.webp)
47 +
48 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
49 +
50 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_power_bi/composio-oauth-credentials.webp)
51 +
52 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
53 +
54 + ![Composio auth config with the v1 redirect URI and the Workspace.Read.All and offline_access scopes](/images/toolkits/microsoft_power_bi/composio-scopes.webp)
55 +
56 +4. Open the auth config and click **Connect Account**. Sign in with the work or school account you use for Power BI; its license and workspace access still apply. Review the consent prompt and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
57 +
58 + ![Microsoft Power BI auth config panel with the Connect Account button](/images/toolkits/microsoft_power_bi/composio-connect-account.webp)
59 +
60 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/1dBnBBEYr17c671yWVLvqnS4k.webp)
61 +
62 + ![Microsoft consent prompt to view all workspaces with organization consent unchecked](/images/toolkits/microsoft_power_bi/microsoft-consent.webp)
63 +
64 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
65 +
66 + ![Connected Accounts tab with the Power BI account showing Active](/images/toolkits/microsoft_power_bi/connected-account-active.webp)
67 +
68 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
69 +
70 +### Scopes
71 +
72 +The default auth config requests the Power BI scopes `Dataset.Read.All`, `Report.Read.All`, `Dashboard.Read.All`, `Workspace.Read.All`, `Content.Create`, and `Dataflow.Read.All`, each prefixed with `https://analysis.windows.net/powerbi/api/` (for example, `https://analysis.windows.net/powerbi/api/Workspace.Read.All`), plus `offline_access`. Listing workspaces needs only `Workspace.Read.All`. See Microsoft's [get groups](https://learn.microsoft.com/en-us/rest/api/power-bi/groups/get-groups) reference.
docs/content/toolkits/faq/microsoft_powerpoint.md new
+91
@@ -0,0 +1,91 @@
1 +## How do I set up custom OAuth credentials for Microsoft PowerPoint?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Microsoft PowerPoint requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +
14 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/microsoft_powerpoint/register-application.webp)
15 +
16 +4. On the app's **Overview** page, copy the **Application (client) ID**.
17 +
18 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/microsoft_powerpoint/app-overview.webp)
19 +
20 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
21 +
22 + ![Certificates & secrets page with the New client secret button](/images/toolkits/microsoft_powerpoint/certificates-and-secrets.webp)
23 +
24 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/microsoft_powerpoint/add-client-secret.webp)
25 +
26 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
27 +
28 + ![Client secrets list with the Value and Secret ID censored](/images/toolkits/microsoft_powerpoint/client-secret-value.webp)
29 +
30 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Files.ReadWrite.All` (create, read, and edit presentations) and `offline_access` (refresh tokens). `User.Read` is already listed by default, then click **Add permissions**.
31 +
32 + ![API permissions page with the Add a permission button](/images/toolkits/microsoft_powerpoint/api-permissions.webp)
33 +
34 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/microsoft_powerpoint/microsoft-graph-api.webp)
35 +
36 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/microsoft_powerpoint/delegated-permissions.webp)
37 +
38 + ![Microsoft Graph delegated permissions with Files.ReadWrite.All selected](/images/toolkits/microsoft_powerpoint/files-readwrite-all-permission.webp)
39 +
40 + ![Microsoft Graph delegated permissions with offline_access selected](/images/toolkits/microsoft_powerpoint/offline-access-permission.webp)
41 +
42 + ![Configured permissions list with Files.ReadWrite.All, offline_access and User.Read](/images/toolkits/microsoft_powerpoint/configured-permissions.webp)
43 +
44 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
45 +
46 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
47 +
48 +![Entra Authentication page listing the Composio Web redirect URI](/images/toolkits/microsoft_powerpoint/registered-redirect-uri.webp)
49 +
50 +### Create the auth config in Composio
51 +
52 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft PowerPoint**. Enter a config name and click **Next**.
53 +
54 + ![Composio Auth Configs page with the Create button](/images/toolkits/microsoft_powerpoint/composio-auth-configs.webp)
55 +
56 + ![Create Auth Config dialog with Microsoft PowerPoint selected](/images/toolkits/microsoft_powerpoint/composio-toolkit-picker.webp)
57 +
58 + ![Auth config name field with the Next button](/images/toolkits/microsoft_powerpoint/composio-config-name.webp)
59 +
60 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
61 +
62 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_powerpoint/composio-oauth-credentials.webp)
63 +
64 + ![Composio auth config with censored credentials and the v1 redirect URI](/images/toolkits/microsoft_powerpoint/composio-credentials-entered.webp)
65 +
66 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
67 +
68 + ![Composio scopes list with Files.ReadWrite.All and offline_access selected](/images/toolkits/microsoft_powerpoint/composio-scopes.webp)
69 +
70 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account you want to connect and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
71 +
72 + ![Microsoft PowerPoint auth config panel with the Connect Account button](/images/toolkits/microsoft_powerpoint/composio-connect-account.webp)
73 +
74 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/Ad4GMrYjKLi22dWKFlwp1NGTs.webp)
75 +
76 + ![Microsoft consent prompt for file access with organization consent unchecked](/images/toolkits/microsoft_powerpoint/microsoft-consent.webp)
77 +
78 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
79 +
80 + ![Auth config Accounts tab with the PowerPoint account showing Active](/images/toolkits/microsoft_powerpoint/connected-account-active.webp)
81 +
82 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
83 +
84 +### Scopes
85 +
86 +The default auth config requests `Files.ReadWrite.All` and `offline_access`. PowerPoint calls go through Microsoft Graph at `https://graph.microsoft.com/v1.0/`.
87 +
88 +### Revoke access
89 +
90 +- In Composio, delete the connected account from the auth config, or disable the auth config.
91 +- In Microsoft, work or school users remove the app at [myapps.microsoft.com](https://myapps.microsoft.com/), and personal account users remove it at [account.microsoft.com/privacy/app-access](https://account.microsoft.com/privacy/app-access). This revokes PowerPoint's access.
docs/content/toolkits/faq/microsoft_teams.md new
+83
@@ -0,0 +1,83 @@
1 +## How do I set up custom OAuth credentials for Microsoft Teams?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Microsoft Teams requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). Teams connections require a work or school account; a personal Microsoft account can't connect.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +4. On the app's **Overview** page, copy the **Application (client) ID**.
14 +
15 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/m3IgMHHfNa8gv1av1yK5u8y47Pg.webp)
16 +
17 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
18 +
19 + ![Certificates & secrets page with the New client secret button](/images/toolkits/shared/nDFU25pH9BfPuJzceax2NoFVzIw.webp)
20 +
21 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/Ea7qmGPRdmtbyoxbuXiKG7bct1Q.webp)
22 +
23 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
24 +
25 + ![Client secrets list with the Value and Secret ID censored](/images/toolkits/shared/wl7JybvARU75U43YShwhxk1Pgxk.webp)
26 +
27 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add the delegated permissions that match the scopes you'll select in Composio (see **Scopes** below), then click **Add permissions**.
28 +
29 + ![API permissions page with the Add a permission button](/images/toolkits/shared/BOmH98f2n8W8w0fbYP6WUJ1mFII.webp)
30 +
31 + ![Request API permissions panel with Microsoft Graph selected](/images/toolkits/shared/J4V5TpgIBuXDk4prikxhduGZQxM.webp)
32 +
33 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/9cVvSnHVsreVO2KBW80wvMy50Bo.webp)
34 +
35 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
36 +
37 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
38 +
39 +### Create the auth config in Composio
40 +
41 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Teams**. Enter a config name and click **Next**.
42 +
43 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/10qkqAzadRISRYZhaXXdhXA.webp)
44 +
45 + ![Create Auth Config dialog with Microsoft Teams selected](/images/toolkits/microsoft_teams/composio-toolkit-picker.webp)
46 +
47 + ![Auth config name field with the Next button](/images/toolkits/microsoft_teams/composio-config-name.webp)
48 +
49 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
50 +
51 + ![Composio auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/microsoft_teams/composio-own-credentials.webp)
52 +
53 + ![Composio auth config with censored credentials, the v1 redirect URI and Microsoft cloud environment set to global](/images/toolkits/microsoft_teams/composio-credentials-cloud.webp)
54 +
55 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
56 +
57 + ![Composio scopes list with Chat.ReadWrite, offline_access and User.Read selected](/images/toolkits/microsoft_teams/composio-scopes.webp)
58 +
59 +4. Open the auth config and click **Connect Account**. Sign in with a work or school account, check that the consent prompt shows your app's name, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
60 +
61 + ![Microsoft Teams auth config panel with the Connect Account button](/images/toolkits/microsoft_teams/composio-connect-account.webp)
62 +
63 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/microsoft_teams/microsoft-account-picker.webp)
64 +
65 + ![Microsoft consent prompt for the unverified custom app with organization consent unchecked](/images/toolkits/microsoft_teams/microsoft-consent.webp)
66 +
67 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
68 +
69 + ![Auth config Accounts tab with the Microsoft Teams account showing Active](/images/toolkits/microsoft_teams/connected-account-active.webp)
70 +
71 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
72 +
73 +### Scopes
74 +
75 +The default auth config requests `Channel.Create`, `Channel.ReadBasic.All`, `ChannelMessage.Read.All`, `ChannelMessage.ReadWrite`, `ChannelMessage.Send`, `ChannelSettings.ReadWrite.All`, `Chat.Create`, `Chat.Read`, `Chat.ReadBasic`, `Chat.ReadWrite`, `Chat.ReadWrite.All`, `ChatMessage.Read`, `ChatMessage.Send`, `Directory.ReadWrite.All`, `Group.ReadWrite.All`, `offline_access`, `People.Read.All`, `Presence.ReadWrite`, `Team.Create`, `Team.ReadBasic.All`, `TeamMember.ReadWrite.All`, `TeamsActivity.Read`, `TeamsActivity.Send`, `User.Read`, `OnlineMeetings.ReadWrite`. Several of these, including `Directory.ReadWrite.All`, `Group.ReadWrite.All`, and `ChannelMessage.Read.All`, need admin consent. Request only what your workflow uses: updating chat properties, for example, needs only `Chat.ReadWrite`. See Microsoft's [update chat](https://learn.microsoft.com/en-us/graph/api/chat-patch?view=graph-rest-1.0) reference.
76 +
77 +### Restrict sign-in to one tenant
78 +
79 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
80 +
81 +### App-only access (client credentials)
82 +
83 +Microsoft Teams also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`generic_id`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent.
docs/content/toolkits/faq/microsoft_todo.md new
+75
@@ -0,0 +1,75 @@
1 +## How do I set up custom OAuth credentials for Microsoft To Do?
2 +
3 +Microsoft To Do has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +
11 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/shared/1iIDmPCxFpXJP7zt73rUtnOLkxc.webp)
12 +
13 +4. On the app's **Overview** page, copy the **Application (client) ID**.
14 +
15 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
16 +
17 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
18 +
19 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
20 +
21 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
22 +
23 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
24 +
25 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Tasks.ReadWrite`, `User.Read`, `offline_access`, `openid`, and `profile`, then click **Add permissions**.
26 +
27 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
28 +
29 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp)
30 +
31 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp)
32 +
33 + ![Microsoft Graph delegated permissions with Tasks.ReadWrite selected](/images/toolkits/microsoft_todo/tasks-readwrite-permission.webp)
34 +
35 + ![Configured permissions list after saving the Microsoft Graph permissions](/images/toolkits/microsoft_todo/configured-permissions.webp)
36 +
37 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
38 +
39 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
40 +
41 +### Create the auth config in Composio
42 +
43 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft To Do**. Enter a config name and click **Next**.
44 +
45 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/jkkvkcA7QbpyHuUXzLJNP0lvxLo.webp)
46 +
47 + ![Create Auth Config dialog with Microsoft To Do selected](/images/toolkits/microsoft_todo/composio-toolkit-picker.webp)
48 +
49 + ![Auth config name field with the Next button](/images/toolkits/microsoft_todo/composio-config-name.webp)
50 +
51 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
52 +
53 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_todo/composio-oauth-credentials.webp)
54 +
55 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
56 +
57 + ![Composio scopes list with Tasks.ReadWrite, User.Read, offline_access, openid and profile selected](/images/toolkits/microsoft_todo/composio-scopes.webp)
58 +
59 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account you use for To Do (work, school, or personal), review the requested task access, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
60 +
61 + ![Microsoft To Do auth config panel with the Connect Account button](/images/toolkits/microsoft_todo/composio-connect-account.webp)
62 +
63 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/19hfD30iOecyW2OUu49tHoR7H4.webp)
64 +
65 + ![Microsoft consent prompt for task access with organization consent unchecked](/images/toolkits/microsoft_todo/microsoft-consent.webp)
66 +
67 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
68 +
69 + ![Connected Accounts tab with the Microsoft To Do account showing Active](/images/toolkits/microsoft_todo/connected-account-active.webp)
70 +
71 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
72 +
73 +### Scopes
74 +
75 +The default auth config requests `Tasks.ReadWrite`, `User.Read`, `offline_access`, `openid`, and `profile`. For read-only access, use `Tasks.Read` instead of `Tasks.ReadWrite`. See Microsoft's [update todoTask](https://learn.microsoft.com/en-us/graph/api/todotask-update?view=graph-rest-1.0) reference.
docs/content/toolkits/faq/microsoft_word.md new
+91
@@ -0,0 +1,91 @@
1 +## How do I set up custom OAuth credentials for Microsoft Word?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Microsoft Word requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +
14 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/microsoft_word/register-application.webp)
15 +
16 +4. On the app's **Overview** page, copy the **Application (client) ID**.
17 +
18 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/microsoft_word/app-overview.webp)
19 +
20 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
21 +
22 + ![Certificates & secrets page with the New client secret button](/images/toolkits/microsoft_word/certificates-and-secrets.webp)
23 +
24 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/microsoft_word/add-client-secret.webp)
25 +
26 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
27 +
28 + ![Client secrets list with the Value and Secret ID censored](/images/toolkits/microsoft_word/client-secret-value.webp)
29 +
30 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Files.ReadWrite.All` (create, read, and edit documents), `Sites.Read.All` (read documents in SharePoint sites), and `offline_access` (refresh tokens). `User.Read` is already listed by default, then click **Add permissions**.
31 +
32 + ![API permissions page with the Add a permission button](/images/toolkits/microsoft_word/api-permissions.webp)
33 +
34 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/microsoft_word/microsoft-graph-api.webp)
35 +
36 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/microsoft_word/delegated-permissions.webp)
37 +
38 + ![Microsoft Graph delegated permissions with Files.ReadWrite.All selected](/images/toolkits/microsoft_word/files-readwrite-all-permission.webp)
39 +
40 + ![Microsoft Graph delegated permissions with Sites.Read.All selected](/images/toolkits/microsoft_word/sites-read-all-permission.webp)
41 +
42 + ![Microsoft Graph delegated permissions with offline_access selected](/images/toolkits/microsoft_word/offline-access-permission.webp)
43 +
44 + ![Configured permissions list with Files.ReadWrite.All, offline_access, Sites.Read.All and User.Read](/images/toolkits/microsoft_word/configured-permissions.webp)
45 +
46 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
47 +
48 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
49 +
50 +![Entra Authentication page listing the Composio Web redirect URI](/images/toolkits/microsoft_word/registered-redirect-uri.webp)
51 +
52 +### Create the auth config in Composio
53 +
54 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Microsoft Word**. Enter a config name and click **Next**.
55 +
56 + ![Composio Auth Configs page with the Create button](/images/toolkits/microsoft_word/composio-auth-configs.webp)
57 +
58 + ![Create Auth Config dialog with Microsoft Word selected](/images/toolkits/microsoft_word/composio-toolkit-picker.webp)
59 +
60 + ![Auth config name field with the Next button](/images/toolkits/microsoft_word/composio-config-name.webp)
61 +
62 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
63 +
64 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/microsoft_word/composio-oauth-credentials.webp)
65 +
66 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
67 +
68 + ![Composio scopes list with offline_access, User.Read, Files.ReadWrite.All and Sites.Read.All selected](/images/toolkits/microsoft_word/composio-scopes.webp)
69 +
70 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account you want to connect and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
71 +
72 + ![Microsoft Word auth config panel with the Connect Account button](/images/toolkits/microsoft_word/composio-connect-account.webp)
73 +
74 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/microsoft_word/microsoft-account-picker.webp)
75 +
76 + ![Microsoft consent prompt for file and site access with organization consent unchecked](/images/toolkits/microsoft_word/microsoft-consent.webp)
77 +
78 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
79 +
80 + ![Auth config Accounts tab with the Word account showing Active](/images/toolkits/microsoft_word/connected-account-active.webp)
81 +
82 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
83 +
84 +### Scopes
85 +
86 +The default auth config requests `offline_access`, `User.Read`, `Files.ReadWrite.All`, and `Sites.Read.All`. Word calls go through Microsoft Graph at `https://graph.microsoft.com/v1.0/`.
87 +
88 +### Revoke access
89 +
90 +- In Composio, delete the connected account from the auth config, or disable the auth config.
91 +- In Microsoft, work or school users remove the app at [myapps.microsoft.com](https://myapps.microsoft.com/), and personal account users remove it at [account.microsoft.com/privacy/app-access](https://account.microsoft.com/privacy/app-access). This revokes Word's access.
docs/content/toolkits/faq/monday.md
+24 -2
@@ -12,9 +12,31 @@ We are working on making this flow smoother so developers do not need to manuall
12
13 ## How do I set up custom OAuth credentials for Monday.com?
14
15 -For a step-by-step guide on creating and configuring your own Monday.com OAuth credentials, see [How to create OAuth2 credentials for Monday](https://composio.dev/auth/monday).
15 +Use your own Monday app when you want users to see your app's name on the consent screen and control the credentials yourself.
16
17 -For a custom Monday OAuth app, add the Composio redirect URL/callback URL to the Monday app settings. After the OAuth flow completes, the access token is populated automatically.
17 +### Create the Monday app
18 +
19 +1. Sign in to the [Monday developer center](https://monday.com/developers/apps) and click **Create App**.
20 +2. Give the app a name, such as `Composio-Monday`. Monday generates a **Client ID**, **Client Secret**, and **Signing Secret** at the bottom of the page. Copy all three.
21 +
22 + ![Monday app General settings with the app name Composio-Monday](/images/toolkits/monday/general-settings.webp)
23 +
24 + ![Monday App Credentials with redacted Client ID and hidden Client Secret and Signing Secret](/images/toolkits/monday/app-credentials.webp)
25 +3. In the app's **Redirect URLs** section, add `https://backend.composio.dev/api/v1/auth-apps/add` with `https` and no trailing slash. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
26 +4. Select the scopes your integration needs, such as `boards:read`, `boards:write`, `workspaces:read`, `users:read`, and `me:read`.
27 +
28 + ![Monday OAuth & permissions Scopes tab listing OAuth scopes](/images/toolkits/monday/oauth-scopes.webp)
29 +
30 +### Create the auth config in Composio
31 +
32 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Monday**.
33 +
34 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
35 +2. Set the authentication type to **OAuth2** (not Bearer Token) and choose **Use your own developer authentication**.
36 +3. Paste the **Client ID** and **Client Secret**. If **New OAuth Flow** is enabled for your Monday app, set `use_oauth2_1` to `true`; leave it `false` for legacy OAuth 2.0. To use Monday triggers, paste the app's Signing Secret into `webhook_signing_secret` (it's not the Client Secret). Then click **Create Monday Auth Config**.
37 +4. Have a Monday workspace admin install your app in the workspace (see the "App is not installed" question above). Then click **Connect Account**, authorize, and confirm the account shows as **Active**.
38 +
39 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow. After the OAuth flow completes, Composio stores the access token automatically.
40
41 ## How do Monday scopes work?
42
docs/content/toolkits/faq/notebook_lm.md new
+57
@@ -0,0 +1,57 @@
1 +## How do I set up custom Google OAuth credentials for NotebookLM?
2 +
3 +Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.
4 +
5 +NotebookLM connects to an existing Gemini Notebook Enterprise deployment in the Global location. The user needs an active license and the **Cloud NotebookLM User** role in the deployment project. See Google's [Notebook Enterprise API prerequisites](https://docs.cloud.google.com/gemini/enterprise/notebooklm-enterprise/docs/api-notebooks).
6 +
7 +### Create the Google OAuth app
8 +
9 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
10 +
11 + ![Google Cloud console project picker](/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp)
12 +
13 +2. Open **APIs & Services** → **Library**, search for **Discovery Engine API** (`discoveryengine.googleapis.com`), and select **Enable**. If the page shows **Manage**, the API is already enabled. Enable it in the project that hosts your Notebook Enterprise deployment.
14 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
15 +
16 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp)
17 +
18 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
19 +
20 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp)
21 +
22 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
23 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
24 +
25 + ![Create OAuth client ID form with Web application selected](/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp)
26 +
27 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
28 +
29 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp)
30 +
31 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
32 +
33 + ![Google OAuth web client details with Client ID and Client secret](/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp)
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-notebook_lm), open **Auth Configs** → **Create** and select **NotebookLM**.
38 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
39 +3. Open the auth config, select **Connect Account**, and enter the Google Cloud project ID or numeric project number that hosts the Notebook Enterprise deployment. Then sign in. If the connection fails, check the Global location, the user's license, the Discovery Engine API, and IAM access in that project.
40 +
41 + ![Google consent screen asking to view, edit, create, and delete your Discovery Engine data](/images/toolkits/notebook_lm/google-consent-screen.webp)
42 +
43 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
44 +
45 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
46 +
47 +### Scopes
48 +
49 +The default auth config requests `https://www.googleapis.com/auth/discoveryengine.readwrite`. It can authorize Discovery Engine writes within the user's IAM permissions. See the [notebook listing reference](https://docs.cloud.google.com/gemini/enterprise/docs/reference/rest/v1alpha/projects.locations.notebooks/listRecentlyViewed) for the required scopes and IAM permissions.
50 +
51 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
52 +
53 +### Publish and verify the app
54 +
55 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
56 +
57 +If you change the requested scopes later, reconnect the account so the user grants the new access.
docs/content/toolkits/faq/notion.md
+46 -1
@@ -1,3 +1,48 @@
1 +## How do I set up custom OAuth credentials for Notion?
2 +
3 +Use your own Notion integration when you want your own name and logo on the consent screen and in Notion's activity, or to keep your users' tokens isolated to your product.
4 +
5 +### Create the Notion integration
6 +
7 +1. Go to [Notion integrations](https://www.notion.so/profile/integrations) and click **New integration**.
8 +2. Enter a name, such as `Composio Notion Integration`, and select the associated workspace.
9 +3. Set the integration type to **Public**. Composio's OAuth flow requires a public integration.
10 +4. Under **OAuth domains & URIs**, add the redirect URI `https://backend.composio.dev/api/v1/auth-apps/add`. Use it exactly as shown: HTTPS, no trailing slash, no fragments or wildcards. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
11 +5. Under **Capabilities**, select only what your integration needs, such as **Read content**, **Update content**, **Insert content**, and **Read user information**. Notion uses capabilities instead of OAuth scopes.
12 +
13 + ![Notion integration Capabilities section with content and user capabilities](/images/toolkits/notion/capabilities.webp)
14 +6. Save, then copy the **Client ID** and **Client Secret**.
15 +
16 + ![Notion integration configuration with redacted OAuth Client ID and hidden Client Secret](/images/toolkits/notion/oauth-credentials.webp)
17 +
18 +### Create the auth config in Composio
19 +
20 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Notion**.
21 +
22 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
23 +
24 + ![Create Auth Config search results showing Notion](/images/toolkits/notion/composio-search-notion.webp)
25 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
26 +
27 + ![Notion auth config with OAUTH2 selected and the Use your own developer credentials toggle](/images/toolkits/notion/oauth2-auth-config.webp)
28 +3. Paste the **Client ID** and **Client Secret** and click **Create Notion Auth Config**. Leave scopes empty.
29 +4. Click **Connect Account**, choose the pages to share during Notion's authorization, and confirm the account shows as **Active**.
30 +
31 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
32 +
33 +## How do I connect Notion with an API key?
34 +
35 +Use an internal integration secret when you connect your own workspace, don't need multi-user OAuth, and want to skip the redirect flow. API keys only work with internal integrations; public integrations must use OAuth.
36 +
37 +1. On [Notion integrations](https://www.notion.so/profile/integrations), click **New integration**, enter a name, select the workspace, and set the type to **Internal**.
38 +2. Copy the integration secret. It starts with `ntn_` or `secret_`.
39 +3. Share the pages and databases you want Composio to reach with the integration. The integration can only access pages shared with it.
40 +4. In the Composio dashboard, create a **Notion** auth config with the **API Key** auth type. Click **Connect Account**, paste the secret, and confirm the account shows as **Active**.
41 +
42 + ![Notion auth config with API KEY selected as the authentication method](/images/toolkits/notion/api-key-auth-config.webp)
43 +
44 + ![Composio connect screen with a redacted Notion API key](/images/toolkits/notion/connect-api-key.webp)
45 +
46 ## Why do Notion operations show "Composio" instead of the user's name?
47
48 Notion attributes actions to the integration itself, not the individual user. The name and logo shown come from the integration configuration. To use a custom name or logo, create your own Notion integration. See [Notion integration docs](https://developers.notion.com/docs/create-a-notion-integration).
@@ -18,7 +63,7 @@ It depends on the integration type. OAuth apps (public) let users select which p
63
64 - **The user disconnects the integration from Notion.** Notion documents that OAuth-installed public connections appear under `Settings` -> `Connections` and can be disconnected from the workspace. If a user removes the Composio-managed or custom Notion app there, the existing token set should be treated as revoked, and the user should reconnect Notion. See Notion's official guide to [adding and managing workspace connections](https://www.notion.com/help/add-and-manage-connections-with-the-api).
65
21 -- **The same Notion user connects again through the same Notion app.** When a Notion user connects to a Notion app, Notion issues a new `access_token` and `refresh_token` pair for that connection. If the same user connects to the same Notion app again, whether it is Composio-managed or custom, Notion can issue a new token pair and invalidate the older `refresh_token`. The older `access_token` may continue working for some time, but once it expires, the older connection can no longer refresh and should be treated as expired. To avoid this, keep one active Notion connection per real user for a given Notion app, reuse that existing connection in your product, and avoid asking users to reconnect repeatedly. For production Notion integrations, we strongly recommend using your own Notion app so your users' tokens are isolated to your product. Follow the [Notion OAuth setup guide](https://composio.dev/auth/notion).
66 +- **The same Notion user connects again through the same Notion app.** When a Notion user connects to a Notion app, Notion issues a new `access_token` and `refresh_token` pair for that connection. If the same user connects to the same Notion app again, whether it is Composio-managed or custom, Notion can issue a new token pair and invalidate the older `refresh_token`. The older `access_token` may continue working for some time, but once it expires, the older connection can no longer refresh and should be treated as expired. To avoid this, keep one active Notion connection per real user for a given Notion app, reuse that existing connection in your product, and avoid asking users to reconnect repeatedly. For production Notion integrations, we strongly recommend using your own Notion app so your users' tokens are isolated to your product. See "How do I set up custom OAuth credentials for Notion?" on this page for the steps.
67
68 ## How do I set up the Notion webhook ingress endpoint?
69
docs/content/toolkits/faq/one_drive.md
+87
@@ -1,3 +1,90 @@
1 +## How do I set up custom OAuth credentials for OneDrive?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions OneDrive requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +
14 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/shared/KZBDHtekgRetnjjIfoArkzSiZY.webp)
15 +
16 +4. On the app's **Overview** page, copy the **Application (client) ID**.
17 +
18 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/m3IgMHHfNa8gv1av1yK5u8y47Pg.webp)
19 +
20 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
21 +
22 + ![Certificates & secrets page with the New client secret button](/images/toolkits/shared/nDFU25pH9BfPuJzceax2NoFVzIw.webp)
23 +
24 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/Ea7qmGPRdmtbyoxbuXiKG7bct1Q.webp)
25 +
26 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
27 +
28 + ![Client secrets list with the Value and Secret ID censored](/images/toolkits/shared/wl7JybvARU75U43YShwhxk1Pgxk.webp)
29 +
30 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Files.ReadWrite.All`, `Sites.ReadWrite.All`, and `offline_access`, or only the subset your workflow uses, then click **Add permissions**.
31 +
32 + ![API permissions page with the Add a permission button](/images/toolkits/shared/BOmH98f2n8W8w0fbYP6WUJ1mFII.webp)
33 +
34 + ![Request API permissions panel with Microsoft Graph selected](/images/toolkits/shared/J4V5TpgIBuXDk4prikxhduGZQxM.webp)
35 +
36 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/9cVvSnHVsreVO2KBW80wvMy50Bo.webp)
37 +
38 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
39 +
40 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
41 +
42 +### Create the auth config in Composio
43 +
44 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **OneDrive**. Enter a config name and click **Next**.
45 +
46 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/10qkqAzadRISRYZhaXXdhXA.webp)
47 +
48 + ![Create Auth Config dialog with OneDrive selected](/images/toolkits/one_drive/composio-toolkit-picker.webp)
49 +
50 + ![Auth config name field with the Next button](/images/toolkits/one_drive/composio-config-name.webp)
51 +
52 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
53 +
54 + ![Composio auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/one_drive/composio-own-credentials.webp)
55 +
56 + ![Composio auth config with empty credential fields, the v1 redirect URI and Microsoft cloud environment set to global](/images/toolkits/one_drive/composio-credentials-cloud.webp)
57 +
58 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
59 +
60 + ![Composio scopes list with Files.ReadWrite.All, Sites.ReadWrite.All and offline_access selected](/images/toolkits/one_drive/composio-scopes.webp)
61 +
62 +4. Open the auth config and click **Connect Account**. Sign in with the account whose OneDrive you want to use, check that the consent prompt shows your app's name, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
63 +
64 + ![OneDrive auth config panel with the Connect Account button](/images/toolkits/one_drive/composio-connect-account.webp)
65 +
66 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/Ad4GMrYjKLi22dWKFlwp1NGTs.webp)
67 +
68 + ![Microsoft consent prompt for file and site access with organization consent unchecked](/images/toolkits/one_drive/microsoft-consent.webp)
69 +
70 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
71 +
72 + ![Connected Accounts tab with the OneDrive account showing Active](/images/toolkits/one_drive/connected-account-active.webp)
73 +
74 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
75 +
76 +### Scopes
77 +
78 +The default auth config requests `Files.ReadWrite.All`, `Sites.ReadWrite.All`, and `offline_access`. Basic file reads need only `Files.Read`, and file edits need `Files.ReadWrite`. Shared files and SharePoint-backed items need the broader permissions. See Microsoft's [get driveItem](https://learn.microsoft.com/en-us/graph/api/driveitem-get?view=graph-rest-1.0) reference.
79 +
80 +### Restrict sign-in to one tenant
81 +
82 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
83 +
84 +### App-only access (client credentials)
85 +
86 +OneDrive also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`generic_id`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent.
87 +
88 ## Why am I getting 404 on `ONE_DRIVE_DOWNLOAD_FILE` for a shared file?
89
90 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.
docs/content/toolkits/faq/onenote.md new
+85
@@ -0,0 +1,85 @@
1 +## How do I set up custom OAuth credentials for OneNote?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions OneNote requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/onenote/app-registrations.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +4. On the app's **Overview** page, copy the **Application (client) ID**.
14 +
15 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/onenote/app-overview.webp)
16 +
17 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
18 +
19 + ![Certificates & secrets page with the New client secret button](/images/toolkits/onenote/certificates-and-secrets.webp)
20 +
21 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/onenote/add-client-secret.webp)
22 +
23 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
24 +
25 + ![Client secrets tab with the Value and Secret ID columns](/images/toolkits/onenote/client-secrets-list.webp)
26 +
27 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add `Notes.ReadWrite` and `offline_access` (refresh tokens), plus any other OneNote scopes you'll select in Composio. `User.Read` is already listed by default, then click **Add permissions**.
28 +
29 + ![API permissions page with the Add a permission button](/images/toolkits/onenote/api-permissions.webp)
30 +
31 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/onenote/microsoft-graph-api.webp)
32 +
33 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/onenote/delegated-permissions.webp)
34 +
35 + ![Microsoft Graph delegated permissions with Notes.ReadWrite selected](/images/toolkits/onenote/notes-readwrite-permission.webp)
36 +
37 + ![Microsoft Graph delegated permissions with offline_access selected](/images/toolkits/onenote/offline-access-permission.webp)
38 +
39 + ![Configured permissions list with Notes.ReadWrite, offline_access and User.Read](/images/toolkits/onenote/configured-permissions.webp)
40 +
41 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
42 +
43 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
44 +
45 +### Create the auth config in Composio
46 +
47 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **OneNote**. Enter a config name and click **Next**.
48 +
49 + ![Composio Auth Configs page with the Create button](/images/toolkits/onenote/composio-auth-configs.webp)
50 +
51 + ![Create Auth Config dialog with Microsoft OneNote selected](/images/toolkits/onenote/composio-toolkit-picker.webp)
52 +
53 + ![Auth config name field with the Next button](/images/toolkits/onenote/composio-config-name.webp)
54 +
55 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
56 +
57 + ![Composio OAuth 2.0 form with empty Client id and Client secret fields and the v1 redirect URI](/images/toolkits/onenote/composio-oauth-credentials.webp)
58 +
59 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
60 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account you want to connect and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
61 +
62 + ![OneNote auth config panel with the Connect Account button](/images/toolkits/onenote/composio-connect-account.webp)
63 +
64 + ![Microsoft Pick an account page with the account censored](/images/toolkits/onenote/microsoft-account-picker.webp)
65 +
66 + ![Microsoft consent prompt for OneNote notebook access with organization consent unchecked](/images/toolkits/onenote/microsoft-consent.webp)
67 +
68 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
69 +
70 + ![Connected Accounts tab with the OneNote account showing Active](/images/toolkits/onenote/connected-account-active.webp)
71 +
72 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
73 +
74 +### Scopes
75 +
76 +The default auth config requests `Notes.Read`, `Notes.ReadWrite`, `Notes.Create`, `Notes.Read.All`, `Notes.ReadWrite.All`, `Sites.Read.All`, `Team.ReadBasic.All`, `offline_access`, and `User.Read`. If your agent only reads notes, `Notes.Read` is enough. OneNote calls go through Microsoft Graph at `https://graph.microsoft.com/v1.0/me/onenote/`.
77 +
78 +### Restrict sign-in to one tenant
79 +
80 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
81 +
82 +### Revoke access
83 +
84 +- In Composio, delete the connected account from the auth config, or disable the auth config.
85 +- In Microsoft, work or school users remove the app at [myapps.microsoft.com](https://myapps.microsoft.com/), and personal account users remove it at [account.microsoft.com/privacy/app-access](https://account.microsoft.com/privacy/app-access). This revokes OneNote's access.
docs/content/toolkits/faq/outlook.md
+88 -1
@@ -1,6 +1,93 @@
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).
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which permissions Outlook requests.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +
9 + ![Azure App registrations page with the New registration button](/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp)
10 +
11 +2. Enter a **Name**. Under **Supported account types**, choose **Accounts in any organizational directory and personal Microsoft accounts** (shown as **Any Entra ID Tenant + Personal Microsoft accounts**) if you want to connect both work or school and personal accounts. Choose a single-tenant or multitenant organizational option if you only connect work or school accounts.
12 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
13 +
14 + ![Entra Register an application form with Any Entra ID Tenant + Personal Microsoft accounts, the Web platform and the Composio redirect URI](/images/toolkits/shared/KZBDHtekgRetnjjIfoArkzSiZY.webp)
15 +
16 +4. On the app's **Overview** page, copy the **Application (client) ID**.
17 +
18 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/m3IgMHHfNa8gv1av1yK5u8y47Pg.webp)
19 +
20 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
21 +
22 + ![Certificates & secrets page with the New client secret button](/images/toolkits/shared/nDFU25pH9BfPuJzceax2NoFVzIw.webp)
23 +
24 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/Ea7qmGPRdmtbyoxbuXiKG7bct1Q.webp)
25 +
26 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
27 +
28 + ![Client secrets list with the Value and Secret ID censored](/images/toolkits/shared/wl7JybvARU75U43YShwhxk1Pgxk.webp)
29 +
30 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add the delegated permissions that match the scopes you'll select in Composio (see **Scopes** below), then click **Add permissions**.
31 +
32 + ![API permissions page with the Add a permission button](/images/toolkits/shared/BOmH98f2n8W8w0fbYP6WUJ1mFII.webp)
33 +
34 + ![Request API permissions panel with Microsoft Graph selected](/images/toolkits/shared/J4V5TpgIBuXDk4prikxhduGZQxM.webp)
35 +
36 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/9cVvSnHVsreVO2KBW80wvMy50Bo.webp)
37 +
38 + ![Microsoft Graph delegated permissions search with Mail.Read selected](/images/toolkits/outlook/mail-read-permission.webp)
39 +
40 + ![Configured Microsoft Graph delegated permissions for Outlook](/images/toolkits/outlook/configured-permissions.webp)
41 +
42 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. See the admin-consent question below for both ways to do this.
43 +
44 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
45 +
46 +### Create the auth config in Composio
47 +
48 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Outlook**. Enter a config name and click **Next**.
49 +
50 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/10qkqAzadRISRYZhaXXdhXA.webp)
51 +
52 + ![Create Auth Config dialog with Outlook selected](/images/toolkits/outlook/composio-toolkit-picker.webp)
53 +
54 + ![Auth config name field with the Next button](/images/toolkits/outlook/composio-config-name.webp)
55 +
56 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
57 +
58 + ![Composio auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/outlook/composio-own-credentials.webp)
59 +
60 + ![Composio auth config with empty credential fields, the v1 redirect URI and Microsoft cloud environment set to global](/images/toolkits/outlook/composio-credentials-cloud.webp)
61 +
62 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
63 +
64 + ![Composio scopes list with the 12 default Outlook scopes selected](/images/toolkits/outlook/composio-scopes.webp)
65 +
66 +4. Open the auth config and click **Connect Account**. Sign in with the Microsoft account you want to connect, check that the consent prompt shows your app's name, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
67 +
68 + ![Outlook auth config panel with the Connect Account button](/images/toolkits/outlook/composio-connect-account.webp)
69 +
70 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/Ad4GMrYjKLi22dWKFlwp1NGTs.webp)
71 +
72 + ![Microsoft consent prompt listing the Outlook permissions with organization consent unchecked](/images/toolkits/outlook/microsoft-consent.webp)
73 +
74 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
75 +
76 + ![Auth config Accounts tab with the Outlook account showing Active](/images/toolkits/outlook/connected-account-active.webp)
77 +
78 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
79 +
80 +### Scopes
81 +
82 +The default auth config requests `Calendars.Read`, `Calendars.ReadWrite`, `Calendars.ReadWrite.Shared`, `Contacts.ReadWrite`, `Chat.ReadWrite`, `Mail.Read`, `Mail.ReadWrite`, `Mail.Send`, `MailboxSettings.Read`, `MailboxSettings.ReadWrite`, `offline_access`, and `User.Read`. Request only what your workflow uses: reading full messages needs `Mail.Read`, and sending needs `Mail.Send`. If users sign in with personal Outlook.com accounts, leave out organization-only scopes such as `Chat.ReadWrite` (Teams chat). See Microsoft's [get message](https://learn.microsoft.com/en-us/graph/api/message-get?view=graph-rest-1.0) reference.
83 +
84 +### Restrict sign-in to one tenant
85 +
86 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
87 +
88 +### App-only access (client credentials)
89 +
90 +Outlook also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`generic_id`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent.
91
92 ## Why does the Outlook new message trigger only return a message ID?
93
docs/content/toolkits/faq/pagerduty.md new
+42
@@ -0,0 +1,42 @@
1 +## How do I set up custom OAuth credentials for PagerDuty?
2 +
3 +Use your own PagerDuty OAuth app when you want the consent screen to show your app name and to keep the client credentials under your control.
4 +
5 +### Create the PagerDuty app
6 +
7 +You need the **Admin** or **Account Owner** role in PagerDuty to see **App Registration**.
8 +
9 +1. Sign in to [PagerDuty](https://www.pagerduty.com/). In the top navigation, click **Integrations**, then under **Developer Tools** click **App Registration**. Don't pick **API Access Keys**; that page is for API keys.
10 +
11 + ![PagerDuty Integrations menu with App Registration under Developer Tools](/images/toolkits/pagerduty/integrations-menu.webp)
12 +
13 +2. Click **+ New App**. Apps you register here stay private to your PagerDuty account unless you publish them, and private is what you want for Composio.
14 +
15 + ![PagerDuty App Registration page with the New App button](/images/toolkits/pagerduty/new-app.webp)
16 +
17 +3. On **Info & Functionality**, enter a name and description. Under **Functionality**, check **OAuth 2.0**. Leave **Events Integration** unchecked unless you also need it. Click **Next**.
18 +
19 + ![PagerDuty Add New App form with name, description and OAuth 2.0 checked under Functionality](/images/toolkits/pagerduty/info-functionality.webp)
20 +
21 +4. On **Configure OAuth 2.0**, choose **Classic User OAuth**. It acts on behalf of the signing-in user with broad read and write access, which matches the `read` and `write` scopes the auth config requests. **Scoped OAuth** gives per-resource permissions but doesn't match the default auth config.
22 +
23 + ![PagerDuty Configure OAuth 2.0 step with Classic User OAuth selected](/images/toolkits/pagerduty/classic-user-oauth.webp)
24 +
25 +5. Set **Redirect URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
26 +6. Under **Permission Scope**, select **Read & Write**. PagerDuty shows the selected scope as `write`, which includes read.
27 +
28 + ![PagerDuty OAuth form with the Composio redirect URL and Read & Write permission scope](/images/toolkits/pagerduty/redirect-url-scope.webp)
29 +
30 +7. Click **Register App**. PagerDuty shows the **Client ID** and **Client Secret** once, in a dialog. Copy both now. If you lose the secret, generate a new one and update the auth config.
31 +
32 +### Create the auth config in Composio
33 +
34 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-pagerduty), go to **Auth Configs** → **Create** and select **PagerDuty** with the **OAuth2** badge.
35 +2. Choose your own credentials and paste the Client ID and Client Secret. Keep the redirect URI as the value you registered in PagerDuty. Click **Create Auth Config**.
36 +3. Click **Connect Account**, enter a user ID, and sign in to PagerDuty with the account you want to connect.
37 +4. If the user belongs to more than one PagerDuty account (subdomain), PagerDuty lists them. Pick the one whose incidents and services the agent should manage.
38 +5. On the consent screen, check the app name and permissions, then click **Submit Consent**. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
39 +
40 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
41 +
42 +PagerDuty also supports API key auth. Create the key under **Integrations** → **API Access Keys** and paste it when you connect the account.
docs/content/toolkits/faq/pipedrive.md
+31 -8
@@ -1,17 +1,40 @@
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).
3 +Use your own Pipedrive OAuth app when the managed app isn't available to your users, or when you want your app name on the consent screen and control over its scopes.
4
5 -## Why am I seeing "App not found" when connecting Pipedrive?
5 +### Create the Pipedrive app
6
7 -Pipedrive usually shows "App not found" when the OAuth app used for the connection is not approved or available for that user/workspace.
7 +1. Sign in to the [Pipedrive Developer Hub](https://app.pipedrive.com/developer-hub) with your developer sandbox account and click **Create an app**.
8 +
9 + ![Pipedrive Developer Sandbox welcome page with the Create an app button](/images/toolkits/pipedrive/create-an-app.webp)
10 +
11 +2. Choose the app type. A **Private** app works only for users you select and doesn't need Pipedrive's review. A **Public** app is open to any Pipedrive user, needs a name that's unique across Pipedrive, and must be approved by Pipedrive before others can use it.
12 +
13 + ![Pipedrive Select app type dialog comparing public and private apps](/images/toolkits/pipedrive/select-app-type.webp)
14 +
15 +3. On the **Basic info** tab, enter an **App name** and set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field. Click **Save**.
16 +4. On the **OAuth & access scopes** tab, under **Access scopes**, choose **Read only** or **Full access** for each area your tools need, such as deals, contacts, activities, leads, products, or projects. By default, Pipedrive grants only basic access to the user's settings.
17 +
18 + ![Pipedrive Access scopes with per-area toggles and Read only or Full access options](/images/toolkits/pipedrive/access-scopes.webp)
19
9 -If you are using managed Pipedrive OAuth, this means the managed OAuth app is still under Pipedrive review/verification. If you are using your own Pipedrive OAuth app, check the app's approval/verification status in Pipedrive and make sure the user is authorizing the same app configured in the auth config. After the app is approved or corrected, start a fresh connection.
20 +5. Scroll down to **OAuth credentials** and copy the **Client ID** and **Client Secret**.
21
11 -## How should I connect with my own Pipedrive OAuth app?
22 + ![Pipedrive OAuth & access scopes tab showing the Client ID and Client secret](/images/toolkits/pipedrive/oauth-credentials.webp)
23
13 -Create the OAuth app in Pipedrive Developer Hub, then use that app's client ID and client secret in a Pipedrive custom OAuth auth config.
24 +6. For a public app, submit it from the **App review info** tab. Private apps skip review.
25
15 -Do not start the user connection by clicking **Install and Test** inside Pipedrive's OAuth app settings. That button starts Pipedrive's own test/install flow, not the Composio connection flow, and can send the user to the callback URL without the Composio auth config context.
26 +### Create the auth config in Composio
27 +
28 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-pipedrive), go to **Auth Configs** → **Create** and select **Pipedrive**.
29 +2. Choose **OAuth2** and your own credentials, then paste the Client ID and Client Secret. Keep the redirect URI as the value you registered in Pipedrive.
30 +3. Click **Create Auth Config**, then click **Connect Account** and approve access in Pipedrive. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
31 +
32 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
33 +
34 +Start the connection from Composio. Don't use **Install and Test** in Pipedrive's app settings: that button runs Pipedrive's own install flow and sends the user to the callback URL without the Composio auth config context.
35 +
36 +## Why am I seeing "App not found" when connecting Pipedrive?
37 +
38 +Pipedrive usually shows "App not found" when the OAuth app used for the connection is not approved or available for that user/workspace.
39
17 -After saving the custom auth config, start the connection from Composio and enter the Pipedrive subdomain when prompted. If Pipedrive shows "App not found", verify that the client ID and secret match the same Pipedrive OAuth app, that the app is approved/available for the user, and that the redirect URI matches the Pipedrive auth setup guide.
40 +If you are using managed Pipedrive OAuth, this means the managed OAuth app is still under Pipedrive review/verification. If you are using your own Pipedrive OAuth app, check the app's approval/verification status in Pipedrive and make sure the user is authorizing the same app configured in the auth config. Also check that the client ID and secret come from that same app and that the callback URL matches the auth config's redirect URI. After the app is approved or corrected, start a fresh connection.
docs/content/toolkits/faq/plaid.md new
+117
@@ -0,0 +1,117 @@
1 +## How do I connect Plaid with API keys?
2 +
3 +Plaid has no sign-in screen. You connect by pasting keys from your Plaid account into a Composio connection. Each connection uses one Plaid environment: **Sandbox** for Plaid's test data or **Production** for real bank data.
4 +
5 +You use up to three values:
6 +
7 +- **Client ID**: identifies your Plaid account. Always required.
8 +- **Secret**: required. Sandbox and Production each have their own secret.
9 +- **Access token**: points to one linked bank login, which Plaid calls an Item. Only needed for tools that read one person's bank data.
10 +
11 +### Get your Plaid keys
12 +
13 +1. Sign in to the [Plaid Dashboard](https://dashboard.plaid.com/). In the left menu, open **Build** → **Keys**.
14 +2. Copy the **Client ID**. It's the same for Sandbox and Production.
15 +3. Copy the secret for the environment you'll use. A Sandbox secret on a Production connection fails on every call, and the reverse.
16 +
17 + ![Plaid Dashboard Keys page with the Client ID, Sandbox secret and Production secret](/images/toolkits/plaid/keys-page.webp)
18 +
19 +### Decide whether you need an access token
20 +
21 +Institution tools, such as searching or listing institutions, work with only the Client ID and secret. Tools that read accounts, balances, transactions, identity, liabilities, investments, or statements also need an access token.
22 +
23 +One connection stores one access token, so it works with one linked bank. For three linked banks, create three connections. If you're not sure, skip the token now and add it later.
24 +
25 +To get an access token:
26 +
27 +1. Open Plaid Link in your app. Plaid Link is Plaid's pop-up where a person picks their bank and signs in. You need a link token to open it; you can create one with the `PLAID_CREATE_LINK_TOKEN` tool on a connection that doesn't have an access token yet.
28 +2. When the person finishes signing in, Plaid gives your app a short-lived `public_token`.
29 +3. From your server, send it to Plaid's `POST /item/public_token/exchange` endpoint. Plaid returns the `access_token`.
30 +
31 +Sandbox tokens start with `access-sandbox-` and Production tokens with `access-production-`.
32 +
33 +### Create the auth config and connect
34 +
35 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-plaid), go to **Auth Configs** → **Create**, select **Plaid** (API Key is the only method), and click **Create Auth Config**.
36 +
37 + ![Composio Create Auth Config dialog with Plaid and its API Key badge](/images/toolkits/plaid/create-auth-config.webp)
38 +
39 + ![Plaid auth config with API Key as the only authentication method](/images/toolkits/plaid/api-key-method.webp)
40 +
41 +2. Open the auth config and click **Connect Account**.
42 +3. Fill in the form:
43 + - **Environment**: `sandbox` (the default) or `production`.
44 + - **Client ID** and **Secret**: the values from the Keys page. The secret must match the environment.
45 + - **Item access token**: optional. Leave it empty if you only need institution tools.
46 + - **Legacy user token**: leave empty. It's only for Plaid integrations created before December 10, 2025 that use Plaid's old User API.
47 +
48 + ![Composio connect form for Plaid with Client ID, Secret and Item access token fields](/images/toolkits/plaid/connect-form.webp)
49 +
50 +4. Click **Connect Account**. The account shows **Active** on the auth config's **Connected Accounts** tab.
51 +
52 +**Active** only means the connection was saved. Composio can't check Plaid keys when you connect, so a wrong secret still shows Active. Run an institution search tool to test the Client ID and secret, and the get accounts tool to test the access token.
53 +
54 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
55 +
56 +### Create a Sandbox access token without Plaid Link
57 +
58 +In Sandbox, two calls create a token for First Platypus Bank (`ins_109508`), Plaid's test bank. No bank sign-in is needed.
59 +
60 +```bash
61 +curl -X POST "https://sandbox.plaid.com/sandbox/public_token/create" \
62 + -H "Content-Type: application/json" \
63 + -d '{
64 + "client_id": "YOUR_CLIENT_ID",
65 + "secret": "YOUR_SANDBOX_SECRET",
66 + "institution_id": "ins_109508",
67 + "initial_products": ["transactions"]
68 + }'
69 +```
70 +
71 +Plaid returns a `public_token` starting with `public-sandbox-`. It expires after 30 minutes. Exchange it right away:
72 +
73 +```bash
74 +curl -X POST "https://sandbox.plaid.com/item/public_token/exchange" \
75 + -H "Content-Type: application/json" \
76 + -d '{
77 + "client_id": "YOUR_CLIENT_ID",
78 + "secret": "YOUR_SANDBOX_SECRET",
79 + "public_token": "YOUR_PUBLIC_TOKEN"
80 + }'
81 +```
82 +
83 +The response contains an `access_token` starting with `access-sandbox-`. In Production, a real person has to sign in through Plaid Link; then call the same exchange endpoint on `https://production.plaid.com` with your Production secret.
84 +
85 +### Add or replace the access token on an existing connection
86 +
87 +You don't need a new connection. The dashboard has no edit button for this, so [update the connected account](/reference/api-reference/connected-accounts/patchConnectedAccountsByNanoid) through the API. Copy the connected account ID (starts with `ca_`) from the **Connected Accounts** tab, and send a body that sets `connection.state.authScheme` to `API_KEY` and `connection.state.val.generic_token` to the Plaid access token. `generic_token` is the field that stores the access token, and the token must match the connection's environment. Only the token changes; the Client ID, secret, and environment stay the same. To remove the token, send `null` as its value. Run the get accounts tool to confirm it works.
88 +
89 +### Before using Production
90 +
91 +- Plaid must approve your account for Production and for each product you use.
92 +- Production secrets and access tokens read real bank data. Store them only in Composio connection fields, never in prompts or tool inputs.
93 +- Transfer and payment tools move real money in Production. Test them in Sandbox first; the toolkit includes Sandbox-only tools that simulate transfers, payments, and webhooks.
94 +
95 +## Do I need to choose scopes for Plaid?
96 +
97 +No. Plaid uses API keys, so there are no scopes. What a connection can do depends on the Plaid products enabled on your Plaid account and on whether the connection has an access token.
98 +
99 +## Why does every Plaid call fail with `INVALID_API_KEYS`?
100 +
101 +The Client ID or secret isn't valid for the connection's environment. The usual cause is a Sandbox secret on a Production connection, or the reverse. Create a new connection with the secret that matches the environment.
102 +
103 +## Why do institution tools work but account and transaction tools fail?
104 +
105 +The connection has no access token. Institution tools need only your keys; account, balance, and transaction tools also need the access token of a linked bank. Add one to the existing connection as described above.
106 +
107 +## Why do I get `INVALID_ACCESS_TOKEN` from Plaid?
108 +
109 +The access token is wrong or belongs to the other environment. A token starting with `access-sandbox-` works only on a Sandbox connection, and one starting with `access-production-` only on a Production connection.
110 +
111 +## Why do I get `INVALID_PRODUCT` from Plaid?
112 +
113 +Your Plaid account doesn't have access to the product the tool uses. Enable the product in the Plaid Dashboard or request access from Plaid.
114 +
115 +## What does `ITEM_LOGIN_REQUIRED` mean?
116 +
117 +The person's bank login changed or expired, so Plaid needs them to sign in again. Open Plaid Link in update mode for that bank. After they sign in, the same access token works again, and nothing changes in Composio.
docs/content/toolkits/faq/posthog.md
+24 -3
@@ -1,10 +1,31 @@
1 -## How do I set up custom OAuth credentials for PostHog?
1 +## How do I connect PostHog with an API key?
2
3 -For a step-by-step guide on creating and configuring your own PostHog OAuth credentials with Composio, see [How to create OAuth credentials for PostHog](https://composio.dev/auth/posthog).
3 +PostHog connects with a personal API key. There's no OAuth option.
4 +
5 +### Create the PostHog personal API key
6 +
7 +1. Sign in to [PostHog](https://posthog.com/). The key acts as your PostHog user, so use the account whose projects you want Composio to reach.
8 +2. Click **Settings**, then scroll to **Personal API keys** and start a new key.
9 +3. Give the key a descriptive label.
10 +4. Choose its scopes. You can limit the key to specific projects or organizations and to the resources your tools need. Avoid full access unless you need it.
11 +
12 + ![PostHog Create personal API key dialog with label, organization and project access, and the scopes menu](/images/toolkits/posthog/create-personal-api-key.webp)
13 +
14 +5. Click **Create** and copy the key right away. It starts with `phx_` and PostHog shows it only once. Don't use the `phc_` project key.
15 +
16 +### Create the auth config in Composio
17 +
18 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-posthog), go to **Auth Configs** → **Create**, select **PostHog**, and click **Create Auth Config**.
19 +2. Click **Connect Account**. Paste the personal API key and set the region (see the next question). The default is `us`.
20 +3. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
21 +
22 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
23 +
24 +The key's PostHog scopes decide what the connection can do. To limit which Composio tools run as well, list them under **Tools Available for Execution** in the auth config's settings.
25
26 ## How do I configure the PostHog region for US or EU Cloud?
27
7 -Set the PostHog region on the connection. Use `us` for US Cloud or `eu` for EU Cloud. Do not pass a full URL such as `https://eu.posthog.com`; the toolkit builds the host as `<region>.posthog.com` from the region value.
28 +Set the PostHog region on the connection. Use `us` for US Cloud or `eu` for EU Cloud. Do not pass a full URL such as `https://eu.posthog.com`; the toolkit builds the host as `<region>.posthog.com` from the region value. The field also accepts `us.i` or `eu.i` if your PostHog URL uses those hosts, and a self-hosted instance uses its own subdomain. Check your PostHog URL to confirm.
29
30 This matters because the PostHog API host is different for US and EU Cloud, and region is connection-specific rather than one fixed auth-config value for every connected account. A connection that should call `eu.posthog.com` but is left on the default `us` region can fail or return data from the wrong PostHog environment.
31
docs/content/toolkits/faq/ramp.md new
+54
@@ -0,0 +1,54 @@
1 +## How do I set up custom OAuth credentials for Ramp?
2 +
3 +Ramp has no Composio-managed app, so you register your own OAuth app in Ramp and use its credentials in the auth config. You need **Owner** or **Admin** access in Ramp to see the **Developer** page.
4 +
5 +### Create the Ramp app
6 +
7 +1. Sign in to Ramp. Click your profile icon in the top-right corner and select **Settings**.
8 +2. In the left sidebar, expand **Company** and click **Developer**.
9 +
10 + ![Ramp Settings sidebar with Company expanded and Developer at the bottom](/images/toolkits/ramp/company-developer-menu.webp)
11 +
12 +3. Under **My apps**, click **Create new app**. Enter an **App name**, accept the Developer Terms of Service, and click **Create app**.
13 +
14 + ![Ramp Developer page with Create new app under My apps](/images/toolkits/ramp/developer-page.webp)
15 +
16 + ![Ramp Create a new app dialog with the app name and Developer Terms checkbox](/images/toolkits/ramp/create-app-dialog.webp)
17 +
18 +4. Ramp emails you a 6-digit verification code. Enter it and click **Verify**. The code expires after 5 minutes; click **Resend** for a new one.
19 +5. Open the new app from **My apps**. Under **Redirect URIs**, click **+ Add new URI**, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Add**. It must exactly match the auth config's `oauth_redirect_uri` field, with no trailing slash.
20 +
21 + ![Ramp My apps list showing the new app](/images/toolkits/ramp/my-apps-list.webp)
22 +
23 + ![Ramp app detail page with the Composio redirect URI under Redirect URIs](/images/toolkits/ramp/redirect-uris.webp)
24 +
25 + ![Ramp Add new URI dialog with the Composio redirect URI](/images/toolkits/ramp/add-redirect-uri.webp)
26 +
27 +6. Under **Grant types**, turn on **Authorization code**, **Client credentials**, and **Refresh token**. Without the refresh token grant, connections stop working when the access token expires.
28 +
29 + ![Ramp Grant types section with Authorization code, Client credentials and Refresh token turned on](/images/toolkits/ramp/grant-types.webp)
30 +
31 +7. Copy the **Client ID**. Reveal the **Client secret** with the eye icon and copy it. If you lose it, click **Rotate client secret**, then update the auth config and reconnect affected accounts.
32 +8. Under **Scopes**, click **Configure allowed scopes**, turn on the scopes you'll request, and click **Set**.
33 +
34 +### Create the auth config in Composio
35 +
36 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-ramp), go to **Auth Configs** → **Create** and select **Ramp**.
37 +2. Paste the Client ID and Client Secret. Set the scopes to the same set you allowed on the Ramp app.
38 +3. Check **Base URL** and **Authorization URL**. The defaults, `https://api.ramp.com/developer/v1` and `https://app.ramp.com/v1/authorize`, are for production Ramp accounts. If you registered the app on a Ramp demo account (your browser shows `demo.ramp.com`), use the `demo-api.ramp.com` and `demo.ramp.com` hosts instead. The wrong environment makes the token exchange fail.
39 +4. Click **Create Auth Config**, then **Connect Account**. Review the permissions on Ramp's consent screen and click **Allow**. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
40 +
41 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
42 +
43 +### Scopes
44 +
45 +The default auth config requests read and write scopes across accounting, bills, cards, departments, limits, locations, memos, purchase orders, receipts, spend programs, users, and vendors, plus read access to transactions, statements, and other resources. Every scope the auth config requests must be allowed on the Ramp app, or authorization fails. Request only what your tools need, and remove from both sides anything you don't.
46 +
47 +If you request `accounting:write` and the Ramp account already has an accounting provider connected, Ramp's consent screen warns that granting it may conflict. Remove `accounting:write` from both the Ramp app and the auth config if you don't need it.
48 +
49 +### Troubleshooting
50 +
51 +- **`redirect_uri_mismatch`**: the redirect URI in Ramp doesn't exactly match the auth config's.
52 +- **Token exchange fails**: the Base URL and Authorization URL point to the wrong Ramp environment (demo or production).
53 +- **Connection goes inactive**: turn on the **Refresh token** grant type on the Ramp app, then reconnect from the auth config.
54 +- **No Developer page**: ask a Ramp owner for the Owner or Admin role.
docs/content/toolkits/faq/rocketlane.md new
+27
@@ -0,0 +1,27 @@
1 +## How do I connect Rocketlane with an API key?
2 +
3 +Rocketlane connects with an API key. There's no OAuth option.
4 +
5 +### Create the Rocketlane API key
6 +
7 +1. Sign in to [Rocketlane](https://www.rocketlane.com/login). The key is tied to your user, so use the account whose data Composio should reach.
8 +2. Click your profile icon in the bottom-left corner, then **Settings**.
9 +3. Scroll to the **Advanced** section, where you manage API keys, and click **Create API Key**.
10 +
11 + ![Rocketlane Settings API page with the Create API key button](/images/toolkits/rocketlane/api-settings.webp)
12 +
13 +4. Name the key, click **Add**, and copy it.
14 +
15 + ![Rocketlane Create API key dialog with the key name and Add button](/images/toolkits/rocketlane/create-api-key.webp)
16 +
17 +Rocketlane API keys have no scopes. A key can reach whatever the issuing user can access under Rocketlane's role-based permissions, so create it from a user with only the access you want to grant.
18 +
19 +### Create the auth config in Composio
20 +
21 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-rocketlane), go to **Auth Configs** → **Create**, select **Rocketlane**, and click **Create Auth Config**.
22 +2. Click **Connect Account**, enter a user ID, and paste the API key.
23 +3. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
24 +
25 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
26 +
27 +To restrict which Composio tools can run, list them under **Tools Available for Execution** in the auth config's settings.
docs/content/toolkits/faq/salesforce.md
+73 -6
@@ -1,6 +1,77 @@
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).
3 +Use your own Salesforce app when you want your app name on the consent screen, your own scopes, or control over the org's app policies. New orgs use External Client Apps; older orgs can still use Connected Apps.
4 +
5 +### Create the Salesforce app
6 +
7 +If you don't have an org to test in, sign up for a free [Salesforce Developer Edition](https://developer.salesforce.com/signup).
8 +
9 +**Option A: External Client App**
10 +
11 +1. In Salesforce, click the gear icon → **Setup**. Search **App Manager** in **Quick Find** and open it.
12 +2. Click **New External Client App**. Enter an **App Name** (the **API Name** fills in), a **Contact Email**, and keep **Distribution State** as **Local**.
13 +
14 + ![Salesforce External Client App Manager with the New External Client App button](/images/toolkits/salesforce/external-client-app-manager.webp)
15 +
16 + ![Salesforce new External Client App form with app name, API name, contact email and Distribution State](/images/toolkits/salesforce/new-external-client-app.webp)
17 +
18 +3. Expand **OAuth Settings** and check **Enable OAuth**.
19 +4. Set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
20 +5. Add OAuth scopes. The default auth config requests `full`, `refresh_token`, and `openid`, so select **Full access (full)**, **Perform requests at any time (refresh_token, offline_access)**, and **Access unique user identifiers (openid)**.
21 +6. Under security, keep **Require Secret for Web Server Flow** and **Require Secret for Refresh Token Flow** checked. Uncheck **Require PKCE** unless you plan to use PKCE.
22 +
23 + ![Salesforce Security section with Require secret for Web Server Flow and Refresh Token Flow checked and PKCE unchecked](/images/toolkits/salesforce/security-settings.webp)
24 +
25 +7. Save. Open the app's **Settings** tab → **OAuth Settings** → **Consumer Key and Secret** and copy the **Consumer Key** (client ID) and **Consumer Secret**.
26 +
27 +**Option B: Connected App**
28 +
29 +1. In Setup, search **External Client App Settings** in **Quick Find** and turn on **Allow creation of Connected Apps**. Then click **New Connected App**.
30 +
31 + ![Salesforce External Client App Settings with Allow creation of connected apps on and the New Connected App button](/images/toolkits/salesforce/external-client-app-settings.webp)
32 +
33 +2. Enter a **Connected App Name** and **Contact Email**.
34 +
35 + ![Salesforce New Connected App form with the basic information fields and Enable OAuth Settings](/images/toolkits/salesforce/new-connected-app.webp)
36 +
37 +3. Under **API (Enable OAuth Settings)**, check **Enable OAuth Settings** and set **Callback URL** to `https://backend.composio.dev/api/v1/auth-apps/add`.
38 +4. Add the same scopes as in Option A: `full`, `refresh_token, offline_access`, and `openid`. Add others such as `api` or `id, profile, email` if your tools need them.
39 +5. Keep the web server flow and refresh token flow enabled with **Require Secret for Web Server Flow** checked, and save. Salesforce can take about 10 minutes to provision a new Connected App.
40 +6. In **App Manager**, open the app's row menu → **View** → **Manage Consumer Details**, verify your identity if asked, and copy the **Consumer Key** and **Consumer Secret**.
41 +
42 + ![Salesforce Lightning Experience App Manager with the row menu open on View](/images/toolkits/salesforce/app-manager-view.webp)
43 +
44 + ![Salesforce Connected App consumer details with Consumer Key and Consumer Secret Copy buttons](/images/toolkits/salesforce/consumer-details.webp)
45 +
46 +### Create the auth config in Composio
47 +
48 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-salesforce), go to **Auth Configs** → **Create** and select **Salesforce**. Salesforce Data 360 and Salesforce Service Cloud are separate toolkits.
49 +
50 + ![Composio dashboard sidebar with Auth Configs](/images/toolkits/salesforce/composio-auth-configs-nav.webp)
51 +
52 + ![Composio Create Auth Config dialog with Salesforce in the toolkit search results](/images/toolkits/salesforce/create-auth-config.webp)
53 +
54 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Paste the Consumer Key as the client ID and the Consumer Secret as the client secret. Keep the redirect URI as the value you registered in Salesforce. Click **Create Auth Config**.
55 +
56 + ![Salesforce auth config form with Your Own Credentials, Client ID, Client Secret and the Composio redirect URI](/images/toolkits/salesforce/own-credentials.webp)
57 +
58 +3. Click **Connect Account** and fill in the connection fields:
59 + - **Subdomain**: the part of your Salesforce URL before `.salesforce.com`. Most orgs can keep the default `login`; Composio detects your instance after you sign in. If your org requires My Domain login, enter the My Domain part, such as `acme.my` for `acme.my.salesforce.com` (search **My Domain** in Setup). For a sandbox, enter `test`.
60 + - **Instance endpoint**: the API version path. Keep the default `/services/data/v67.0` unless your org needs another version.
61 +
62 +4. Sign in to Salesforce, review the permissions, and click **Allow**. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
63 +
64 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
65 +
66 +### IP allowlists
67 +
68 +If the app uses **Enforce Refresh Token IP Allowlist**, or your org restricts logins with **Login IP Ranges** or **Network Access** trusted IPs, add the four [Composio outbound IP addresses](/docs/security/outbound-ips). For an External Client App, open **External Client App Manager**, choose **Edit Settings** from the app's row menu, expand **OAuth Settings**, and under **Refresh Token IP Allowlist** click **+** for each address, with the same value as the start and end IP. Add the addresses and wait 30 to 45 minutes before you turn on enforcement. Otherwise token refreshes fail with `IP restricted by the app developer` (see below).
69 +
70 +![Salesforce External Client App Manager row menu with Edit Settings selected](/images/toolkits/salesforce/edit-settings-menu.webp)
71 +
72 +![Salesforce Refresh Token IP Allowlist containing Composio's four IP addresses with Enforce Refresh Token IP Allowlist checked](/images/toolkits/salesforce/refresh-token-ip-allowlist.webp)
73 +
74 +Some orgs also set **Limit Idle Refresh Token Time-to-Live (TTL)** to 30 days. In those orgs, a connection that isn't used for 30 days expires and has to be reconnected.
75
76 ## `URL_NOT_RESET` usually means Salesforce subdomain was not configured and defaulted to `login`
77
@@ -26,7 +97,7 @@ After you update the allowlist, ask affected users to reconnect. Connections tha
97
98 ## Salesforce allows only five active refresh tokens per user per app
99
29 -Salesforce allows only five active refresh tokens per user per connected app. When the same Salesforce user connects a sixth time, Salesforce can revoke the oldest refresh token, which makes older Composio connected accounts fail with token errors. Also check whether the user changed their password, revoked the app, changed connected app refresh-token policy away from `valid until revoked`, or has org-level session policies that invalidate tokens.
100 +Salesforce allows only five active refresh tokens per user per connected app. When the same Salesforce user connects a sixth time, Salesforce can revoke the oldest refresh token, which makes older Composio connected accounts fail with token errors. If the consent screen says you've already granted access five times, clicking **Allow** revokes the oldest approval. To keep that connection, click **Deny** and revoke an approval you no longer need first. Also check whether the user changed their password, revoked the app, changed connected app refresh-token policy away from `valid until revoked`, or has org-level session policies that invalidate tokens.
101
102 ## How do I query relationships like Pricebooks and Opportunities?
103
@@ -38,10 +109,6 @@ SELECT Id, Name,
109 FROM Opportunity
110 ```
111
41 -## What fields are required when connecting Salesforce?
42 -
43 -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.
44 -
112 ## What happens to deprecated Salesforce tools?
113
114 Deprecated tools continue to work until removed. Check tool descriptions for "DEPRECATED:" markers.
docs/content/toolkits/faq/servicem8.md new
+56
@@ -0,0 +1,56 @@
1 +## How do I set up custom OAuth credentials for ServiceM8?
2 +
3 +Composio-managed OAuth works for ServiceM8 without any setup. Use your own ServiceM8 add-on when you want your app name on the consent screen and control over its permissions. You need a [ServiceM8 developer account](https://developer.servicem8.com/).
4 +
5 +### Create the ServiceM8 add-on
6 +
7 +1. Sign in to ServiceM8 and open **Developer** from the main menu. On **Store Items**, click **Add Item**.
8 +
9 + ![ServiceM8 Store Items page with the Add Item button](/images/toolkits/servicem8/store-items.webp)
10 +
11 +2. Enter a **Name** and **Description**. Keep **Category** set to **Add-on**, choose a price (Free works for a private integration), and click **Save**. ServiceM8 opens the add-on's settings.
12 +
13 + ![ServiceM8 New Store Item form with name, Add-on category, description and Free price](/images/toolkits/servicem8/new-store-item.webp)
14 +
15 +3. Scroll to **Addon OAuth Credentials** and copy the **App Id** and **App Secret**. These are the client ID and client secret in Composio.
16 +
17 + ![ServiceM8 add-on settings showing Addon OAuth Credentials and Addon Type set to External Integration](/images/toolkits/servicem8/oauth-credentials.webp)
18 +
19 +4. Under **Addon SDK**, set **Addon Type** to **External Integration**.
20 +5. Set **Addon Activation URL** to `https://backend.composio.dev/api/v1/auth-apps/add` and click **Save**. ServiceM8 checks the OAuth redirect host against this URL, so it must match the auth config's `oauth_redirect_uri` field. See ServiceM8's [authentication docs](https://developer.servicem8.com/docs/authentication).
21 +
22 + ![ServiceM8 Addon SDK settings with the Composio Addon Activation URL and Save button](/images/toolkits/servicem8/activation-url.webp)
23 +
24 +### Create the auth config in Composio
25 +
26 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-servicem8), go to **Auth Configs** → **Create** and select **ServiceM8**.
27 +
28 + ![Composio Auth Configs page with the Create button](/images/toolkits/servicem8/auth-configs-create.webp)
29 +
30 + ![Composio Create Auth Config dialog with ServiceM8 in the search results](/images/toolkits/servicem8/search-servicem8.webp)
31 +
32 +2. Choose **OAuth 2.0** and **Your Own Credentials**. Enter the App Id as the client ID and the App Secret as the client secret. Keep the default redirect URI.
33 +
34 + ![ServiceM8 auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/servicem8/own-credentials.webp)
35 +
36 +3. Under **Scopes**, choose the permissions your tools need, then click **Create Auth Config**.
37 +
38 + ![Saved ServiceM8 auth config with custom credentials, the Composio redirect URI and the read_jobs scope](/images/toolkits/servicem8/auth-config-settings.webp)
39 +
40 +4. Click **Connect Account** and sign in to the ServiceM8 account you want to connect. A new draft add-on shows **This Addon isn't verified**; confirm it's your add-on and click **Proceed**. Check the app name and permissions, then click **Allow**.
41 +
42 + ![ServiceM8 This Addon isn't verified warning with the Proceed button](/images/toolkits/servicem8/unverified-warning.webp)
43 +
44 + ![ServiceM8 consent screen requesting read-only access to jobs with the Allow button](/images/toolkits/servicem8/consent-screen.webp)
45 +
46 +5. Open the auth config's **Accounts** tab and confirm the account shows **Active**. The auth config's own **Enabled** label doesn't mean an account is connected.
47 +
48 + ![Composio auth config Accounts tab with a ServiceM8 connected account showing Active](/images/toolkits/servicem8/active-account.webp)
49 +
50 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
51 +
52 +### Scopes
53 +
54 +ServiceM8 permissions are per resource, such as `read_jobs`, `manage_jobs`, `read_customers`, `manage_customers`, `read_staff`, and `read_schedule`. The default auth config requests read and manage permissions across jobs, customers, staff, schedule, inventory, assets, and messaging. A read-only jobs integration needs only `read_jobs`. See ServiceM8's [scope descriptions](https://developer.servicem8.com/docs/authentication).
55 +
56 +The add-on can stay a draft. Publishing it to the ServiceM8 directory is a separate process, and submitting the add-on for review removes the unverified warning.
docs/content/toolkits/faq/share_point.md
+84
@@ -1,3 +1,87 @@
1 +## How do I set up custom OAuth credentials for SharePoint?
2 +
3 +Use your own Microsoft Entra ID app registration when you want the Microsoft consent screen to show your app's name and you want to control which SharePoint permissions it requests. This applies to the **SharePoint** toolkit, which calls the SharePoint REST API; the separate **SharePoint Graph** toolkit uses Microsoft Graph permissions instead.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). Allowing personal accounts doesn't give them access to an organizational SharePoint site.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **SharePoint** (not Microsoft Graph), and choose **Delegated permissions**. Add the permissions your tools need, for example `AllSites.Read` for read-only access, and click **Add permissions**. Write, list-management, and admin operations can need more permissions and site or tenant roles.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/share_point/add-a-permission.webp)
25 +
26 + ![Request API permissions panel with SharePoint under Microsoft APIs](/images/toolkits/share_point/sharepoint-api.webp)
27 +
28 + ![SharePoint delegated permissions with AllSites.Read selected](/images/toolkits/share_point/allsites-read-permission.webp)
29 +
30 + ![Configured SharePoint AllSites.Read delegated permission details](/images/toolkits/share_point/allsites-read-details.webp)
31 +
32 +8. Keep **Allow public client flows** disabled on the **Authentication** page. This is a confidential Web client.
33 +9. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
34 +
35 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
36 +
37 +### Create the auth config in Composio
38 +
39 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **SharePoint**. Enter a config name and click **Next**.
40 +
41 + ![Composio Auth Configs page with the Create button](/images/toolkits/share_point/composio-auth-configs.webp)
42 +
43 + ![Create Auth Config search showing SharePoint and SharePoint Graph as separate toolkits](/images/toolkits/share_point/composio-toolkit-picker.webp)
44 +
45 + ![Auth config name field with the Next button](/images/toolkits/share_point/composio-config-name.webp)
46 +
47 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown.
48 +
49 + ![Composio auth config form with OAuth 2.0 and Your Own Credentials selected](/images/toolkits/share_point/composio-own-credentials.webp)
50 +
51 +3. Under **Scopes**, keep the default `.default` and `offline_access` scopes. The `.default` scope picks up the SharePoint permissions you added in Azure. Click **Create Auth Config**.
52 +
53 + ![Composio auth config with the v1 redirect URI and the tenant-templated .default and offline_access scopes](/images/toolkits/share_point/composio-scopes.webp)
54 +
55 +4. Open the auth config and click **Connect Account**. Enter the **Tenant Name** (`subdomain`) and, optionally, the **SharePoint Subsite** (`generic_id`), then click **Connect Account**. Sign in with a work or school account that can access the site, check that the consent prompt shows your app's name, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
56 +
57 + ![SharePoint auth config page with the Connect Account button](/images/toolkits/share_point/composio-connect-account.webp)
58 +
59 + ![Composio connection form with a censored Tenant Name and an empty SharePoint Subsite field](/images/toolkits/share_point/tenant-and-subsite-fields.webp)
60 +
61 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/1dBnBBEYr17c671yWVLvqnS4k.webp)
62 +
63 + ![Composio page confirming the SharePoint connection](/images/toolkits/share_point/connection-success.webp)
64 +
65 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
66 +
67 + ![Connected Accounts tab with the SharePoint account showing Active](/images/toolkits/share_point/connected-account-active.webp)
68 +
69 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
70 +
71 +### Scopes
72 +
73 +The default auth config requests `https://<tenant>.sharepoint.com/.default` (Composio fills in the tenant name you enter when connecting) and `offline_access`. The `.default` scope requests every permission configured on the app registration, not every SharePoint operation. If you reuse an app that has other API permissions, users and admins see those too, so review the full consent prompt. See Microsoft's [.default scope](https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc#the-default-scope) reference.
74 +
75 +### Connection fields
76 +
77 +- **Tenant Name** (`subdomain`, required): the part before `.sharepoint.com` in your site URL, such as `contoso` in `contoso.sharepoint.com`. Enter only the name, not a full URL or a tenant GUID.
78 +- **SharePoint Subsite** (`generic_id`): leave it empty for the root site. A bare name such as `marketing` resolves to `/sites/marketing`. For nested subsites or other managed paths, enter the full path, such as `/sites/marketing/archive` or `/teams/engineering`.
79 +- The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
80 +
81 +### App-only access (certificate)
82 +
83 +SharePoint also supports an app-only auth mode (`S2S_OAUTH2`) that uses a certificate instead of a client secret. Upload the certificate under **Certificates & secrets** on the app registration, then enter the tenant ID (`generic_id`, a GUID from **Microsoft Entra ID** > **Overview**), the **Client id**, the RSA private key in PEM format (`private_key`), and the certificate's base64url-encoded SHA-256 thumbprint (`cert_thumbprint`). Connections take the same **Tenant Name** and optional site path.
84 +
85 ## Why does my SharePoint `/teams/...` site resolve as `/sites/...`?
86
87 If a user's SharePoint site URL is under `/teams/<site>` instead of `/sites/<site>`, do not tell them to pass only `<site>` in the SharePoint Subsite field. A bare subsite value is interpreted as `/sites/<site>` by the toolkit.
docs/content/toolkits/faq/sharepoint_graph.md new
+79
@@ -0,0 +1,79 @@
1 +## How do I set up custom OAuth credentials for SharePoint Graph?
2 +
3 +SharePoint Graph has no Composio-managed app, so you need your own Microsoft Entra ID app registration to connect it.
4 +
5 +### Create the Microsoft Entra app
6 +
7 +1. Sign in to the [Azure portal](https://portal.azure.com/), open **App registrations**, and click **New registration**.
8 +2. Enter a **Name**. Under **Supported account types**, choose an organizational option: **Accounts in this organizational directory only** (single tenant) or **Accounts in any organizational directory** (multitenant). Personal Microsoft accounts can't use these site operations.
9 +3. Under **Redirect URI**, select the **Web** platform, enter `https://backend.composio.dev/api/v1/auth-apps/add`, and click **Register**.
10 +4. On the app's **Overview** page, copy the **Application (client) ID**.
11 +
12 + ![Entra app Overview page with the client, object and tenant IDs censored](/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp)
13 +
14 +5. Open **Certificates & secrets** and click **New client secret**. Add a description, choose an expiry that fits your rotation policy (for example, 180 days), and click **Add**. Rotate the secret before it expires.
15 +
16 + ![Add a client secret panel with a description and the 180-day expiry](/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp)
17 +
18 +6. Copy the secret **Value** right away. Use the **Value**, not the **Secret ID**. Azure shows the full value only once; if you lose it, create a new secret.
19 +
20 + ![Client secrets list with the Value and Secret ID columns censored](/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp)
21 +
22 +7. Open **API permissions**, click **Add a permission**, select **Microsoft Graph**, and choose **Delegated permissions** so the app acts as the signed-in user. Add the delegated permissions that match the scopes you'll select in Composio (see **Scopes** below), then click **Add permissions**.
23 +
24 + ![API permissions page with the Add a permission button](/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp)
25 +
26 + ![Request API permissions panel with Microsoft Graph under Microsoft APIs](/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp)
27 +
28 + ![Microsoft Graph permission type choice with Delegated permissions](/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp)
29 +
30 + ![Microsoft Graph delegated permissions with Sites.ReadWrite.All selected](/images/toolkits/sharepoint_graph/sites-readwrite-all-permission.webp)
31 +
32 + ![Configured permissions list after saving the Microsoft Graph permissions](/images/toolkits/sharepoint_graph/configured-permissions.webp)
33 +
34 +8. If your tenant restricts user consent, have a tenant admin click **Grant admin consent for** your tenant on the **API permissions** page. Adding a permission to the app registration doesn't grant consent by itself.
35 +
36 +The redirect URI you register must exactly match the `oauth_redirect_uri` field in your Composio auth config (default `https://backend.composio.dev/api/v1/auth-apps/add`).
37 +
38 +### Create the auth config in Composio
39 +
40 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **SharePoint Graph**. Enter a config name and click **Next**.
41 +
42 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/SKmiRvkpLj1fiXUXAPnkjJ2Ug.webp)
43 +
44 + ![Create Auth Config dialog with SharePoint Graph selected](/images/toolkits/sharepoint_graph/composio-toolkit-picker.webp)
45 +
46 + ![Auth config name field with the Next button](/images/toolkits/sharepoint_graph/composio-config-name.webp)
47 +
48 +2. Select **OAuth 2.0** and **Your Own Credentials**. Paste the Application (client) ID into **Client id** and the secret value into **Client secret**. Leave **Redirect URI** as shown. Keep **Microsoft cloud environment** (`microsoft_cloud`) set to `global` for commercial Microsoft 365, or set `gcc_high` for Microsoft 365 US Government GCC High. The app registration must live in that cloud.
49 +
50 + ![Composio auth config form with OAuth 2.0 selected and empty Client id and Client secret fields](/images/toolkits/sharepoint_graph/composio-oauth-credentials.webp)
51 +
52 + ![Composio auth config with the v1 redirect URI, Microsoft cloud environment set to global, and the Sites.ReadWrite.All, offline_access and User.Read scopes](/images/toolkits/sharepoint_graph/composio-cloud-and-scopes.webp)
53 +
54 +3. Under **Scopes**, select the same permissions you added in Azure, then click **Create Auth Config**.
55 +4. Open the auth config and click **Connect Account**. Sign in with a work or school account that can access the SharePoint sites you need, review the requested site access, and click **Accept**. Leave **Consent on behalf of your organization** unchecked unless you're an admin granting tenant-wide consent. An **unverified** label is expected for a custom app without a verified publisher.
56 +
57 + ![SharePoint Graph auth config panel with the Connect Account button](/images/toolkits/sharepoint_graph/composio-connect-account.webp)
58 +
59 + ![Microsoft Pick an account page with the accounts censored](/images/toolkits/shared/19hfD30iOecyW2OUu49tHoR7H4.webp)
60 +
61 + ![Microsoft consent prompt for site access with organization consent unchecked](/images/toolkits/sharepoint_graph/microsoft-consent.webp)
62 +
63 +5. Back on the auth config's **Connected Accounts** tab, confirm the account shows **Active**. The **Enabled** label at the top of the page describes the auth config, not the account.
64 +
65 + ![Connected Accounts tab with the SharePoint Graph account showing Active](/images/toolkits/sharepoint_graph/connected-account-active.webp)
66 +
67 +For the general flow, see [custom auth configs](/docs/auth-configuration/custom-auth-configs).
68 +
69 +### Scopes
70 +
71 +The default auth config requests `Sites.ReadWrite.All`, `Sites.Manage.All`, `Sites.FullControl.All`, `Files.ReadWrite.All`, `SensitivityLabels.Read.All`, `offline_access`, and `User.Read`. These allow edits and deletions. Creating list items needs only `Sites.ReadWrite.All`, and read-only site access can use `Sites.Read.All`. See Microsoft's [create listItem](https://learn.microsoft.com/en-us/graph/api/listitem-create?view=graph-rest-1.0) reference.
72 +
73 +### Restrict sign-in to one tenant
74 +
75 +The connection's tenant field (`issuer`) defaults to `common`. To restrict sign-in to one tenant, set it to your **Directory (tenant) ID** from the app's **Overview** page or a verified tenant domain.
76 +
77 +### App-only access (client credentials)
78 +
79 +SharePoint Graph also supports an app-only auth mode (`S2S_OAUTH2`) that runs without a signed-in user. It takes the **Client id**, the **Client secret** value, and your Microsoft Entra **tenant ID** (`generic_id`) as a GUID, found under **Microsoft Entra ID** > **Overview** > **Tenant ID**. For this mode, add **Application permissions** instead of delegated permissions on the app registration, and have an admin grant admin consent.
docs/content/toolkits/faq/shopify.md
+47 -1
@@ -1,6 +1,52 @@
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).
3 +Use your own app from the Shopify Dev Dashboard when you want to choose the scopes and the app name merchants see, or when the default app isn't available.
4 +
5 +### Create the Shopify app
6 +
7 +1. Sign in to your Shopify admin. If you don't have a store, start one at [shopify.com](https://www.shopify.com/).
8 +2. Search for **App Development** in the admin search bar and open it, then click **Build apps in Dev Dashboard**.
9 +
10 +3. Click **Create App**, enter an app name, and click **Create**. Shopify opens the app's version configuration.
11 +
12 + ![Shopify Dev Dashboard Create an app page with the app name and Create button](/images/toolkits/shopify/create-app.webp)
13 +
14 +4. Set **App URL** to your application's URL.
15 +
16 + ![Shopify Create a version page with the App URL field](/images/toolkits/shopify/app-url.webp)
17 +
18 +5. Select the access scopes your tools need, such as `read_products`, `write_products`, `read_orders`, `write_orders`, `read_customers`, and `read_inventory`.
19 +
20 + ![Shopify Select scopes dialog listing Admin API scopes](/images/toolkits/shopify/select-scopes.webp)
21 +
22 +6. Set the redirect URL to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
23 +
24 + ![Shopify app version Access section with scopes filled in and the Composio redirect URL](/images/toolkits/shopify/scopes-redirect-url.webp)
25 +
26 +7. Click **Release**, optionally add a version name and message, and click **Release** again.
27 +
28 + ![Shopify Release this new version dialog with optional version name and message](/images/toolkits/shopify/release-version.webp)
29 +
30 +8. Open **Settings** in the left sidebar and copy the **Client ID** and **Client Secret**.
31 +
32 + ![Shopify Dev Dashboard Settings page with the Client ID and Secret under Credentials](/images/toolkits/shopify/client-credentials.webp)
33 +
34 +### Create the auth config in Composio
35 +
36 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-shopify), go to **Auth Configs** → **Create** and select **Shopify**.
37 +2. Choose **OAuth2** and your own credentials, then paste the Client ID and Client Secret. Keep the redirect URI as the value you registered in Shopify. Click **Create Auth Config**.
38 +
39 + ![Composio Shopify auth config Client id, Client secret and Composio redirect URI fields](/images/toolkits/shopify/own-credentials.webp)
40 +
41 +3. Click **Connect Account** and enter the store subdomain: the permanent `myshopify.com` name, not a custom domain. For `https://acme.myshopify.com`, enter `acme`. You can find it under **Settings** → **Domains** in the Shopify admin.
42 +
43 +4. Install the app on the store and grant the permissions. Confirm the account shows **Active** on the auth config's **Connected Accounts** tab.
44 +
45 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
46 +
47 +### Scopes
48 +
49 +The default auth config requests read and write access to products, orders, customers, inventory, fulfillments, content, themes, discounts, draft orders, metaobjects, webhooks, and more. Select the same scopes on the Shopify app, and remove the ones you don't need from both.
50
51 ## Why am I seeing "App not found" when connecting Shopify?
52
docs/content/toolkits/faq/slack.md
+57 -2
@@ -8,7 +8,62 @@ Composio executes API calls on behalf of your connected account. All data is enc
8
9 ## How do I set up custom OAuth credentials for Slack?
10
11 -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).
11 +Composio-managed auth works without any setup: create a Slack auth config, choose **Composio Managed**, and connect. Use your own Slack app when you want your own branding, specific scopes, or full control over the app, or when a workspace blocks apps that aren't in the Slack Marketplace.
12 +
13 +### Create the Slack app
14 +
15 +1. Go to [Slack API: Your Apps](https://api.slack.com/apps) and click **Create New App** → **From scratch**.
16 +
17 + ![Slack API Your Apps page with the Create an App button](/images/toolkits/slack/create-an-app.webp)
18 +
19 + ![Slack Create an app dialog with the From scratch option](/images/toolkits/slack/from-scratch.webp)
20 +
21 +2. Enter an **App Name**, select your workspace, and click **Create App**.
22 +
23 + ![Slack Name app and choose workspace dialog with the Create App button](/images/toolkits/slack/name-and-workspace.webp)
24 +
25 +3. Open **OAuth & Permissions**. Under **Redirect URLs**, click **Add New Redirect URL**, enter `https://backend.composio.dev/api/v1/auth-apps/add`, click **Add**, then **Save URLs**. It must exactly match the auth config's `oauth_redirect_uri` field.
26 +
27 + ![Slack OAuth & Permissions Redirect URLs with the Composio redirect URL and Save URLs button](/images/toolkits/slack/redirect-urls.webp)
28 +
29 +4. On the same page, under **Scopes** → **User Token Scopes**, add the scopes your auth config will request. The Slack toolkit acts as the connecting user, and some default scopes, such as `search:read`, exist only as user scopes. For example, `channels:history` reads channel messages, `chat:write` sends messages, and `users:read` reads user info. For a bot that posts as itself, use the [Slackbot](/toolkits/slackbot) toolkit instead.
30 +
31 +5. Open **Basic Information** and scroll to **App Credentials**. Copy the **Client ID**, **Client Secret**, and, if you'll use Slack triggers, the **Verification Token**.
32 +
33 + ![Slack Basic Information App Credentials with Client ID, Client Secret and Signing Secret](/images/toolkits/slack/app-credentials.webp)
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-slack), go to **Auth Configs** → **Create** and select **Slack**.
38 +
39 + ![Composio Auth Configs page with the Create button](/images/toolkits/slack/auth-configs-create.webp)
40 +
41 + ![Composio Create Auth Config dialog with Slack and Slackbot in the search results](/images/toolkits/slack/search-slack.webp)
42 +
43 +2. Under **Credentials**, choose **Your Own Credentials** and paste the Client ID and Client Secret. Keep the redirect URI as the value you added in Slack.
44 +
45 + ![Composio Slack auth config with Your Own Credentials selected and Client id and Client secret fields](/images/toolkits/slack/own-credentials.webp)
46 +
47 +3. Paste the **Verification Token** if you need Slack triggers, choose the scopes, and click **Create Auth Config**.
48 +
49 + ![Composio Slack auth config Verification Token field and selected scopes](/images/toolkits/slack/verification-token-scopes.webp)
50 +
51 +4. Click **Connect Account**, select your workspace on the Slack page, review the permissions, and click **Allow**. Confirm the account shows **Active** on the auth config's **Accounts** tab.
52 +
53 + ![Slack authorization page with workspace picker, requested permissions and the Allow button](/images/toolkits/slack/consent-screen.webp)
54 +
55 + ![Composio Slack auth config Accounts tab with a connected account showing Active](/images/toolkits/slack/active-account.webp)
56 +
57 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow, and [custom OAuth webhooks](/docs/setting-up-triggers/custom-oauth-webhooks) for trigger setup with your own app.
58 +
59 +### Scopes
60 +
61 +The default auth config requests a broad set covering channels, groups, DMs, chat, files, reactions, pins, reminders, search, usergroups, and users. Request only what your workflow needs; an agent that only sends messages may need just `chat:write`. Every scope the auth config requests must also be added to the Slack app, or users see scope errors. See Slack's [scopes reference](https://docs.slack.dev/reference/scopes/).
62 +
63 +### Revoke access
64 +
65 +- In Composio, delete the connected account from the auth config, or disable the auth config.
66 +- In Slack, a workspace admin can remove the app under **Settings & administration** → **Manage apps**, which revokes its tokens right away.
67
68 ## When do users see "This app isn't listed in the Slack Marketplace…"?
69
@@ -27,7 +82,7 @@ Because **Require approved apps** is enabled in the workspace's **App Management
82 Two ways:
83
84 - Disable both **Require apps from Slack Marketplace** and **Require approved apps** in the workspace's app management settings.
30 -- Use the workspace's own OAuth app, which is recommended and safest. See [How to create OAuth credentials for Slack](https://composio.dev/auth/slack).
85 +- Use the workspace's own OAuth app, which is recommended and safest. See **How do I set up custom OAuth credentials for Slack?** on this page.
86
87 ## What is the difference between Slack and Slackbot toolkits?
88
docs/content/toolkits/faq/snowflake.md
+50 -11
@@ -1,19 +1,58 @@
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).
3 +Snowflake has no Composio-managed OAuth app, so you create an OAuth security integration in your own Snowflake account and use its credentials in Composio. Snowflake has no web form for this; you create the integration with SQL.
4
5 -## How do I create a Snowflake OAuth app?
5 +### Create the Snowflake OAuth integration
6
7 -Example Snowflake SQL to create a security integration for OAuth:
7 +You need the `ACCOUNTADMIN` role, or a role with the privilege to create integrations.
8
9 -```sql
10 -CREATE SECURITY INTEGRATION oauth_custom_all_roles
11 - TYPE = oauth
12 - ENABLED = true
13 - OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
14 - OAUTH_REDIRECT_URI = 'https://your-app.com/oauth/callback'
15 - OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;
16 -```
9 +1. Sign in to [Snowflake](https://app.snowflake.com/) and open a SQL worksheet.
10 +
11 + ![Snowflake sign-in page asking for the account identifier](/images/toolkits/snowflake/sign-in.webp)
12 +2. Run this command to create a confidential OAuth client that points at Composio:
13 +
14 + ```sql
15 + CREATE SECURITY INTEGRATION oauth_custom_all_roles
16 + TYPE = oauth
17 + ENABLED = true
18 + OAUTH_CLIENT = custom
19 + OAUTH_CLIENT_TYPE = 'CONFIDENTIAL'
20 + OAUTH_REDIRECT_URI = 'https://backend.composio.dev/api/v1/auth-apps/add'
21 + OAUTH_ISSUE_REFRESH_TOKENS = TRUE
22 + OAUTH_REFRESH_TOKEN_VALIDITY = 7776000;
23 + ```
24 +
25 + `OAUTH_REDIRECT_URI` must exactly match the `oauth_redirect_uri` field in your Composio auth config.
26 +
27 + ![Snowflake worksheet with the CREATE SECURITY INTEGRATION command and the Composio redirect URI](/images/toolkits/snowflake/create-security-integration.webp)
28 +3. Run `DESC SECURITY INTEGRATION oauth_custom_all_roles;` and copy the `OAUTH_CLIENT_ID` value.
29 +4. Run the following command and copy the `OAUTH_CLIENT_SECRET` value from the result:
30 +
31 + ```sql
32 + SELECT SYSTEM$SHOW_OAUTH_CLIENT_SECRETS('OAUTH_CUSTOM_ALL_ROLES') AS SECRETS;
33 + ```
34 +
35 +### Create the auth config in Composio
36 +
37 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Snowflake**.
38 +
39 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/snowflake/create-auth-config.webp)
40 +
41 + ![Composio toolkit picker with Snowflake selected](/images/toolkits/snowflake/select-toolkit.webp)
42 +2. Keep the authentication type as **OAuth2**.
43 +
44 + ![Snowflake auth config form with OAUTH2 selected and the refresh_token scope](/images/toolkits/snowflake/oauth2-auth-method.webp)
45 +3. Paste the `OAUTH_CLIENT_ID` into **Client ID** and the `OAUTH_CLIENT_SECRET` into **Client Secret**, then click **Create Auth Config**.
46 +
47 + ![Snowflake auth config with redacted client ID and secret and the Composio redirect URI](/images/toolkits/snowflake/client-credentials.webp)
48 +4. Click **Connect Account** and enter your Snowflake account identifier in `orgname-accountname` format, for example `myorg-account123`. In Snowsight, click your account in the bottom left and choose **View account details** to find it.
49 +5. Sign in to Snowflake, approve access, and confirm the account shows as **Active**.
50 +
51 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
52 +
53 +### Scopes
54 +
55 +The default auth config requests the `refresh_token` scope, so Composio can refresh access without asking the user to sign in again. Snowflake roles, not OAuth scopes, decide which databases, schemas, and warehouses the connection can use.
56
57 ## How do I configure roles and permissions for Snowflake?
58
docs/content/toolkits/faq/stripe.md
+43 -1
@@ -1,6 +1,48 @@
1 ## How do I set up custom OAuth credentials for Stripe?
2
3 -For a step-by-step guide on creating and configuring your own Stripe OAuth credentials with Composio, see [How to create OAuth credentials for Stripe](https://composio.dev/auth/stripe).
3 +Use your own Stripe Connect OAuth app when you want users to see your platform's name on the consent screen and control the credentials yourself. If you only need to connect your own Stripe account, an API key is simpler; see the next question.
4 +
5 +### Create the Stripe OAuth app
6 +
7 +1. In the [Stripe Dashboard](https://dashboard.stripe.com/), go to **Settings** → **Connect**.
8 +2. Under **Integration settings**, click **+ Add Integration** and fill in the form:
9 + - **Name**: something recognizable, for example `Composio-Integration`.
10 + - **Redirect URL**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must use `https`, have no trailing slash, and exactly match the `oauth_redirect_uri` field in your Composio auth config.
11 + - **Website**, **Privacy Policy**, and **EULA** are optional.
12 +3. Save the integration and copy the **Client ID** (starts with `ca_`).
13 +4. For the client secret, Stripe Connect OAuth uses your platform account's secret API key. Copy it from **Developers** → **API keys** (`sk_live_`, or `sk_test_` in test mode).
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Stripe**.
18 +
19 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
20 +
21 + ![Composio toolkit picker with Stripe selected](/images/toolkits/stripe/select-toolkit.webp)
22 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
23 +
24 + ![Stripe auth config form with OAUTH2 selected, the read_write scope, and Use your own developer credentials enabled](/images/toolkits/stripe/oauth2-own-credentials.webp)
25 +3. Paste the **Client ID** and the secret key as the **Client Secret**, then click **Create Stripe Auth Config**.
26 +4. Click **Connect Account**, approve access in Stripe, and confirm the account shows as **Active**.
27 +
28 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
29 +
30 +### Scopes
31 +
32 +Stripe OAuth has two scopes: `read_only` and `read_write`. The default auth config requests `read_write`. Use `read_only` if your tools only read data.
33 +
34 +## How do I connect Stripe with an API key?
35 +
36 +1. In the [Stripe Dashboard](https://dashboard.stripe.com/apikeys), go to **Developers** → **API keys**.
37 +2. Under **Standard keys**, copy the **Secret key**. It starts with `sk_live_`, or `sk_test_` in test mode. Don't use the publishable `pk_` key.
38 +
39 + ![Stripe Developers API keys page with the publishable and secret keys redacted](/images/toolkits/stripe/api-keys.webp)
40 +3. In Composio, go to **Auth Configs**, click **Create Auth Config**, select **Stripe**, and choose **API Key** as the authentication type. Click **Create Stripe Auth Config**.
41 +
42 + ![Stripe auth config form with API KEY selected](/images/toolkits/stripe/api-key-auth-method.webp)
43 +4. Click **Connect Account**, paste the secret key, and confirm the account shows as **Active**.
44 +
45 +Keep the secret key out of client-side code.
46
47 ## Why is my Stripe trigger enabled but not receiving events?
48
docs/content/toolkits/faq/supabase.md
+30 -2
@@ -1,3 +1,31 @@
1 -## Limit Supabase scopes in the user's OAuth app, not through Composio's default app
1 +## How do I set up custom OAuth credentials for Supabase?
2
3 -For Supabase permission scoping, configure the desired permissions in the user's own OAuth app and create the Composio auth config with that app. The default Composio OAuth app may be configured with broader permissions.
3 +Use your own Supabase OAuth app when you want to limit what the connection can do or show your app's name on the consent screen. The default Composio OAuth app may be configured with broader permissions, so scope limits belong in your own app.
4 +
5 +### Create the Supabase app
6 +
7 +1. Open your [Supabase organization](https://supabase.com/dashboard/organizations) and go to **Organization Settings**.
8 +2. Click **Add Application** and fill in the form:
9 + - **Name**: for example, `Composio-Supabase`.
10 + - **Website URL**: your application's URL.
11 + - **Authorization Callback URL**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
12 +3. Grant only the read and write permissions your tools need, then click **Create**.
13 +4. Copy the **Client ID** and **Client Secret** from the page Supabase opens next.
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Supabase**.
18 +2. Set the authentication type to **OAuth2** and choose **Use your own developer credentials**.
19 +3. Paste the **Client ID** and **Client Secret**, then click **Create Supabase Auth Config**.
20 +4. Click **Connect Account**. Keep the Supabase API URL at `https://api.supabase.com` unless you self-host Supabase.
21 +5. Check that the consent screen lists only the permissions you granted the app, click **Authorize**, and confirm the account shows as **Active**.
22 +
23 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
24 +
25 +### Scopes
26 +
27 +The permissions you select in the Supabase app decide what the connection can access. Composio's auth config requests the `all` scope and can't narrow it further, so set the limits in Supabase.
28 +
29 +### Use a personal access token instead
30 +
31 +Supabase also supports API key authentication. Choose **API Key** as the authentication type, then on **Connect Account** paste a personal access token that starts with `sbp_`. Create one at [Account → Access Tokens](https://supabase.com/dashboard/account/tokens). Supabase shows it only once, so copy it right away.
docs/content/toolkits/faq/telegram.md new
+37
@@ -0,0 +1,37 @@
1 +## How do I connect Telegram with a bot token?
2 +
3 +Telegram doesn't support OAuth. Composio connects to a Telegram bot using the bot token from BotFather. The connection acts as the bot, not your personal Telegram account.
4 +
5 +### Create the Telegram bot
6 +
7 +1. In Telegram, start a chat with [@BotFather](https://t.me/BotFather) and send `/newbot`.
8 +
9 + ![Telegram search results for @BotFather](/images/toolkits/telegram/botfather-search.webp)
10 +2. Enter a display name for the bot, then a username that ends in `bot`, for example `composio_test_bot`.
11 +
12 + ![BotFather chat after /newbot asking for the bot name and username](/images/toolkits/telegram/newbot.webp)
13 +3. Copy the bot token BotFather returns. It looks like `123456:ABC-DEF1234ghIkl`. For an existing bot, send `/token` to BotFather to get it.
14 +
15 + ![BotFather confirmation message with the bot token redacted](/images/toolkits/telegram/bot-token.webp)
16 +
17 +The token gives full control of the bot, so store it securely.
18 +
19 +### Create the auth config in Composio
20 +
21 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Telegram**.
22 +
23 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
24 +
25 + ![Composio toolkit picker with Telegram and its API_KEY badge](/images/toolkits/telegram/select-toolkit.webp)
26 +2. Keep the authentication type as **API Key** and click **Create Auth Config**.
27 +
28 + ![Telegram auth config form with API KEY as the authentication method](/images/toolkits/telegram/api-key-auth-method.webp)
29 +3. Click **Connect Account**, paste the bot token, and confirm the account shows as **Active**.
30 +
31 + ![Composio connect screen with the Bot Token field, value redacted](/images/toolkits/telegram/connect-bot-token.webp)
32 +
33 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
34 +
35 +### Permissions
36 +
37 +Telegram bots don't use scopes. What the bot can do depends on which chats, groups, and channels you add it to, and on the admin rights you give it there.
docs/content/toolkits/faq/ticktick.md new
+33
@@ -0,0 +1,33 @@
1 +## How do I set up custom OAuth credentials for TickTick?
2 +
3 +Use your own TickTick OAuth app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the TickTick app
6 +
7 +1. Sign in to the [TickTick Developer Center](https://developer.ticktick.com/) and open **My Apps**.
8 +2. Click **Create App** and fill in the form:
9 + - **App Name**: for example, `Composio-TickTick`.
10 + - **App Description**: a short description of your integration.
11 + - **Redirect URI**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must use `https`, have no trailing slash, and exactly match the `oauth_redirect_uri` field in your Composio auth config.
12 +3. Save the app and copy the **Client ID** and **Client Secret**.
13 +
14 +### Create the auth config in Composio
15 +
16 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **TickTick**.
17 +
18 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
19 +
20 + ![Composio toolkit picker with TickTick selected](/images/toolkits/ticktick/select-toolkit.webp)
21 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
22 +
23 + ![TickTick auth config form with OAUTH2 and the tasks:read and tasks:write scopes](/images/toolkits/ticktick/oauth2-auth-method.webp)
24 +
25 + ![Use your own developer credentials toggle turned on](/images/toolkits/ticktick/own-credentials-toggle.webp)
26 +3. Paste the **Client ID** and **Client Secret**, then click **Create TickTick Auth Config**.
27 +4. Click **Connect Account**, approve access in TickTick, and confirm the account shows as **Active**.
28 +
29 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
30 +
31 +### Scopes
32 +
33 +TickTick has no scope settings in its developer dashboard. Scopes are requested during authorization, and the default auth config requests `tasks:read` and `tasks:write`.
docs/content/toolkits/faq/trello.md new
+45
@@ -0,0 +1,45 @@
1 +## How do I set up custom credentials for Trello?
2 +
3 +Composio connects Trello with OAuth 1.0a. Use your own Trello API key and secret when you want the authorization screen to show your app name. Your Trello API key is the auth config's consumer key, and the Trello secret is its consumer secret.
4 +
5 +### Create the Trello Power-Up and API key
6 +
7 +1. Sign in to Trello and open the [Power-Ups admin portal](https://trello.com/power-ups/admin). The old `https://trello.com/app-key` page redirects here.
8 +2. Click **New** and fill in the form: an app name, any workspace you belong to, an email and support contact, an author, and an **Iframe connector URL**. A placeholder such as `https://example.com` works if you aren't building a Power-Up UI. Click **Create**.
9 +
10 + ![Trello Power-Ups admin portal Your Apps page with the New button](/images/toolkits/trello/power-ups-admin.webp)
11 +
12 + ![Trello New App form with app name, workspace, email, support contact, author, and Iframe connector URL](/images/toolkits/trello/new-app-form.webp)
13 +
14 +3. Open the Power-Up, go to the **API Key** tab, and click **Generate a new API Key**.
15 +
16 + ![Trello Power-Up API key tab with the Generate a new API Key button](/images/toolkits/trello/generate-api-key.webp)
17 +
18 +4. Copy the **API Key**, then reveal and copy the **Secret**.
19 +
20 + ![Trello API key page with the API key, Allowed origins, and Secret fields (redacted)](/images/toolkits/trello/api-key-secret.webp)
21 +
22 +5. **Allowed origins** lists the origins Trello may redirect users back to after they authorize. Trello blocks redirects to any origin not on the list. If authorization fails at the redirect step, add `https://backend.composio.dev`.
23 +
24 +### Create the auth config in Composio
25 +
26 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-trello), go to **Auth Configs** → **Create** and select **Trello**.
27 +2. Choose your own credentials. Paste the API key into the consumer key field (`consumer_key`) and the secret into the consumer secret field (`consumer_secret`).
28 +3. Click **Create Auth Config**, then click **Connect Account**.
29 +4. Click **Allow** on Trello's authorization screen and check that the account shows **Active**.
30 +
31 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
32 +
33 +### Scopes
34 +
35 +The default auth config requests `read`, `write`, and `account`:
36 +
37 +- `read`: read boards, lists, and cards
38 +- `write`: create, update, and move cards
39 +- `account`: read basic account information
40 +
41 +Request only what you need, for example `read` alone for read-only access.
42 +
43 +### Keep credentials safe and revoke access
44 +
45 +The API key on its own doesn't grant access to anyone's data. The secret and any user token do, so keep them private. Each Trello user can see and revoke the tokens they've granted at `https://trello.com/u/{username}/account` under **Applications**. Trello can't reset an API key. If yours is exposed, rotate the secret and revoke the affected tokens.
docs/content/toolkits/faq/twitter.md
+62 -1
@@ -1,9 +1,70 @@
1 +## How do I set up custom OAuth credentials for Twitter (X)?
2 +
3 +Composio has no managed OAuth app for Twitter, so you need your own X developer app. X API usage follows [X's access and billing requirements](https://docs.x.com/x-api/getting-started/pricing).
4 +
5 +### Create the X app
6 +
7 +1. Sign in to the [X Developer Console](https://console.x.com/), open **Apps**, and click **Create App**. Enter an **Application Name**, select at least one existing project under **Project Access**, pick the environment, and click **Create**.
8 +
9 + ![X Developer Console Apps page with the Create App button](/images/toolkits/twitter/apps-list.webp)
10 +
11 + ![Create New Client Application dialog with an app name and a project selected](/images/toolkits/twitter/create-app.webp)
12 +2. Open the app's **Settings** and find **User authentication settings**. In the older console, click **Set up** or **Edit** under that heading.
13 +3. Under **App permissions**, choose the access your workflow needs. For **Type of App**, select **Web App, Automated App or Bot**. This confidential client type issues OAuth 2.0 credentials.
14 +
15 + ![X user authentication settings with Read permissions and Web App, Automated App or Bot selected](/images/toolkits/twitter/user-auth-settings.webp)
16 +4. Under **App info**, set **Callback URI / Redirect URL** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config. Enter your public **Website URL**, fill in any other required fields, and click **Save Changes**.
17 +
18 + ![X app info with the Composio callback URL and a website URL, ready to save](/images/toolkits/twitter/callback-url.webp)
19 +5. Open **Keys & Tokens**. Copy the **Client ID** and **Client Secret** under **OAuth 2.0 Keys**, and the **Bearer Token** under **App-Only Authentication**.
20 +
21 + ![X Keys and Tokens tab showing the Bearer Token, OAuth 1.0 keys, and OAuth 2.0 Client ID and Client Secret](/images/toolkits/twitter/keys-and-tokens.webp)
22 +
23 +The **API Key** and **API Key Secret** shown when you create the app are not the OAuth 2.0 Client ID and Client Secret.
24 +
25 +### Create the auth config in Composio
26 +
27 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Twitter**.
28 +
29 + ![Composio Create Auth Config dialog with Twitter in the search results](/images/toolkits/twitter/select-toolkit.webp)
30 +
31 + ![Twitter auth config name field](/images/toolkits/twitter/config-name.webp)
32 +2. Use OAuth 2.0. Paste the **Client id** and **Client secret**, and paste the app-only Bearer Token into **Application Bearer Token**. All three values must come from the same X app. Composio uses the Bearer Token for app-only actions such as recent search and post lookup.
33 +3. Trim the scopes to what your tools need (see below), then click **Create Auth Config**.
34 +
35 + ![Twitter auth config with the Application Bearer Token field, the Composio redirect URI, and three scopes selected](/images/toolkits/twitter/bearer-token-and-scopes.webp)
36 +4. Click **Connect Account**, sign in to X, check the app name and permissions, and click **Authorize app**.
37 +
38 + ![X consent screen listing the requested permissions with an Authorize app button](/images/toolkits/twitter/authorize-app.webp)
39 +5. Open **Accounts** and confirm the connected account shows as **Active**. The auth config's **Enabled** label alone doesn't confirm a connection.
40 +
41 + ![Composio auth config Accounts tab with a connected account marked Active](/images/toolkits/twitter/connected-account-active.webp)
42 +
43 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
44 +
45 +### Scopes
46 +
47 +The default auth config requests a broad set that includes DMs, likes, lists, bookmarks, and media. Remove the ones you don't need:
48 +
49 +- `tweet.read` and `users.read`: read profiles and posts.
50 +- `tweet.write`: create posts.
51 +- `offline.access`: lets Composio refresh access without another sign-in.
52 +
53 +See [X's endpoint-to-scope mapping](https://docs.x.com/fundamentals/authentication/guides/v2-authentication-mapping) for other endpoints. Changing scopes doesn't update existing connections; reconnect the account to grant the new set.
54 +
55 +### Troubleshooting
56 +
57 +- **Invalid client**: use the OAuth 2.0 Client ID and Client Secret from a **Web App, Automated App or Bot** app, not the API Key and Secret.
58 +- **Callback mismatch**: compare the full callback URL in X and in Composio.
59 +- **Missing refresh token**: add `offline.access` and reconnect.
60 +- **Credits or usage-limit errors**: check the account's X usage and billing. OAuth scopes don't grant API access or usage credits.
61 +
62 ## Why are Composio managed credentials no longer available for Twitter?
63
64 As of February 2026, Composio managed credentials for the Twitter toolkit have been removed. You must now bring your own Twitter API credentials. To migrate:
65
66 1. Create a Twitter Developer account and obtain API credentials from the [Twitter Developer Portal](https://developer.x.com/en/portal/dashboard).
6 -2. Set up a custom auth configuration with your credentials in Composio.
67 +2. Set up a custom auth configuration with your credentials in Composio, as described in the setup question above.
68
69 If you were relying on managed credentials, your Twitter integrations will stop working until you configure your own. See the [changelog entry](/docs/changelog/2026/02/12) for full details.
70
docs/content/toolkits/faq/workday.md new
+49
@@ -0,0 +1,49 @@
1 +## How do I set up custom OAuth credentials for Workday?
2 +
3 +Workday has no Composio-managed OAuth app, so you register an API client in your own Workday tenant. You need administrator or integration security permissions in Workday, and your tenant name, which appears in your Workday URLs.
4 +
5 +### Register the Workday API client
6 +
7 +1. Sign in to your Workday tenant, type `Register API Client` in the search bar, and press Enter.
8 +2. Under **Tasks and Reports**, open **Register API Client**. Don't pick the Integrations variant or the external OAuth client task. If the task doesn't appear, your account lacks the required security permissions.
9 +3. Fill in the form:
10 + - **Client Name**: for example, `composio-workday`.
11 + - **Client Grant Type**: **Authorization Code Grant**.
12 + - **Access Token Type**: **Bearer**.
13 + - **Support PKCE**: leave unchecked.
14 + - **Redirection URI**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config, or the connection fails with `redirect_uri_mismatch`.
15 + - **Non-Expiring Refresh Tokens**: enable.
16 + - **Scopes**: select the areas your tools need, and check **Include Workday Owned Scope**.
17 +
18 + ![Workday Register API Client form with the client name, Authorization Code Grant, Bearer token type, and redirection URI](/images/toolkits/workday/register-api-client-form.webp)
19 +
20 + ![Workday Register API Client form with Non-Expiring Refresh Tokens, functional scopes, and Include Workday Owned Scope checked](/images/toolkits/workday/register-api-client-scopes.webp)
21 +4. Click **OK**, review the summary, and click **Done**.
22 +
23 + ![Workday registered API client summary with the Composio redirection URI](/images/toolkits/workday/registered-client-summary.webp)
24 +5. On the client detail page, copy five values: **Client ID**, **Client Secret**, **REST API Endpoint**, **Token Endpoint**, and **Authorization Endpoint**. Copy them now; the secret can be masked once you leave the page, and you'd have to regenerate it.
25 +
26 +### Create the auth config in Composio
27 +
28 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Workday** (OAuth2).
29 +2. Paste the **Client ID** and **Client Secret**, then create the auth config.
30 +3. Click **Connect Account** and enter a stable user ID from your own system, such as a UUID from your user database.
31 +4. Enter the three tenant URLs you copied, then click **Connect Account** and complete the Workday consent flow:
32 + - **REST API base URL**: for example, `https://wd2-impl-services1.workday.com/ccx/api/v1/<tenant>`.
33 + - **Authorization URL**: for example, `https://wd2-impl-services1.workday.com/ccx/oauth2/<tenant>/authorize`.
34 + - **Token URL**: for example, `https://wd2-impl-services1.workday.com/ccx/oauth2/<tenant>/token`.
35 +5. Confirm the account shows as **Active** under **Connected Accounts**.
36 +
37 +Use the exact URLs from your API client's detail page. Generic Workday URLs fail the token exchange.
38 +
39 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
40 +
41 +### Set up an Integration System User and security group
42 +
43 +Workday recommends running API clients as an Integration System User (ISU) with the right domain permissions. Most tenants already have one; check with your Workday admin first.
44 +
45 +1. Run **Create Integration System User**. Set a username and password, set **Session Timeout Minutes** to `0`, and check **Do Not Allow UI Sessions**.
46 +2. Run **Maintain Password Rules** and add the ISU to **System Users exempt from password expiration**.
47 +3. Run **Create Security Group** and choose **Integration System Security Group (Unconstrained)** for access to all data instances, or **(Constrained)** for access scoped by context. Add the ISU as a member.
48 +4. Run **Maintain Permissions for Security Group**, select the group, and on **Domain Security Policy Permissions** grant GET access to `Integration Build`, `Integration Process`, `Integration Debug`, `Integration Event`, `Worker Data: Current Staffing Information`, and `Worker Data: Public Worker Reports`.
49 +5. Run **Activate Pending Security Policy Changes**, enter a comment, and confirm.
docs/content/toolkits/faq/xero.md
+38 -1
@@ -1,3 +1,40 @@
1 ## How do I set up custom OAuth credentials for Xero?
2
3 -For a step-by-step guide on creating and configuring your own Xero OAuth credentials with Composio, see [How to create OAuth credentials for Xero](https://composio.dev/auth/xero).
3 +Composio has no managed OAuth app for Xero, so you need your own Xero app. It also lets you control the app name users see and the permissions your integration requests.
4 +
5 +### Create the Xero app
6 +
7 +1. Sign in to the [Xero Developer Portal](https://developer.xero.com/app/manage), open your apps, and click **New app**.
8 +
9 + ![Xero Developer Portal My Apps page with the New app button](/images/toolkits/xero/my-apps.webp)
10 +2. Enter an **App name** and **Company or application URL**, and select the **Auth code** flow for a web app.
11 +
12 + ![Xero Add a new app form with Web app selected and the app details and redirect URI redacted](/images/toolkits/xero/new-app-form.webp)
13 +3. Set the **Redirect URI** to `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field in your Composio auth config. Fill in the remaining required fields and click **Create app**.
14 +4. Open the app's configuration and copy the **Client ID**. Click **Generate a secret** and copy the **Client Secret**.
15 +
16 +### Create the auth config in Composio
17 +
18 +1. In the Composio dashboard, go to **Auth Configs**, click **Create**, and select **Xero**.
19 +
20 + ![Composio Auth Configs page with the Create button](/images/toolkits/xero/auth-configs.webp)
21 +
22 + ![Composio Create Auth Config dialog with Xero in the search results](/images/toolkits/xero/select-toolkit.webp)
23 +2. Choose **Your Own Credentials** and paste the **Client id** and **Client secret**.
24 +
25 + ![Xero auth config form with Your Own Credentials selected and the Client id and Client secret fields](/images/toolkits/xero/own-credentials.webp)
26 +3. Keep the default scopes or adjust them (see below), then click **Create Auth Config**.
27 +4. Click **Connect Account**, sign in to Xero, check the app name, organisation, and permissions, and click **Allow access**.
28 +
29 + ![Saved Xero auth config with the Connect Account button](/images/toolkits/xero/connect-account.webp)
30 +
31 + ![Xero consent screen listing the requested permissions with an Allow access button](/images/toolkits/xero/consent.webp)
32 +5. Open **Accounts** and confirm the connected account shows as **Active**. The auth config's **Enabled** label alone doesn't confirm a connection.
33 +
34 + ![Xero auth config Accounts tab with a connected account marked Active](/images/toolkits/xero/connected-account-active.webp)
35 +
36 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
37 +
38 +### Scopes
39 +
40 +The default auth config requests `openid`, `profile`, `email`, `offline_access`, plus read and write access to accounting, files, and projects (for example `accounting.invoices`, `accounting.contacts`, `accounting.payments`, and the `accounting.reports.*.read` scopes). Keep `offline_access` so Composio can refresh tokens without another sign-in, and remove any accounting areas your tools don't use.
docs/content/toolkits/faq/youtube.md
+71 -1
@@ -1,6 +1,76 @@
1 ## How do I set up custom Google OAuth credentials for YouTube?
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).
3 +Use your own Google OAuth app when you want your app name on the consent screen, full control over the requested scopes, or your own YouTube API quota (see the quota question below).
4 +
5 +### Create the Google OAuth app
6 +
7 +1. In [Google Cloud Console](https://console.cloud.google.com/), select the project that will own the OAuth client, or create one.
8 +
9 + ![Google Cloud console project picker](/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp)
10 +
11 +2. Open **APIs & Services** → **Library**, search for **YouTube Data API v3**, and select **Enable**. If the page shows **Manage**, the API is already enabled. See Google's [server-side web app guide](https://developers.google.com/youtube/v3/guides/auth/server-side-web-apps).
12 +
13 + ![YouTube Data API v3 page in the API Library with the Enable button](/images/toolkits/youtube/enable-youtube-data-api.webp)
14 +
15 +3. Open **Google Auth Platform** → **Branding**. If Google shows **Get started**, enter the app name, user support email, and developer contact email, then save.
16 +
17 + ![Google Auth Platform Branding page with app name and user support email](/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp)
18 +
19 +4. Open **Audience**. Choose **Internal** to limit the app to users in your Google Workspace organization, or **External** for consumer accounts and users outside it. While an external app's publishing status is **Testing**, only accounts listed under **Test users** can connect, so add every account you'll test with.
20 +
21 + ![Google Auth Platform Audience page with Testing status, External user type, and Test users](/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp)
22 +
23 +5. Open **Data Access** → **Add or remove scopes** and add the scopes listed under **Scopes** below. If a scope isn't in the list, paste its full URL under **Manually add scopes** and select **Add to table**. Select **Update**, then **Save**.
24 +
25 + ![Data Access scope picker with the youtube.readonly scope selected](/images/toolkits/youtube/data-access-youtube-scope.webp)
26 +
27 +6. Open **Clients** → **Create client**, choose **Web application**, and give it a name.
28 +
29 + ![Create OAuth client ID form with Web application selected and a client name](/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp)
30 +
31 +7. Under **Authorized redirect URIs**, add `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the `oauth_redirect_uri` field on your Composio auth config.
32 +
33 + ![OAuth client form with the Composio redirect URI under Authorized redirect URIs](/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp)
34 +
35 +8. Select **Create**. Copy the **Client ID** and **Client secret**. Google shows the full secret only once, so save it before you close the dialog.
36 +
37 + ![OAuth client created dialog with the Client ID and Client secret](/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp)
38 +
39 +### Create the auth config in Composio
40 +
41 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-youtube), open **Auth Configs** → **Create** and select **YouTube**.
42 +
43 + ![Composio Auth Configs page with the Create button](/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp)
44 +
45 + ![Create Auth Config dialog with YouTube in the search results](/images/toolkits/youtube/select-youtube-toolkit.webp)
46 +
47 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste your **Client ID** and **Client secret**. Leave **Redirect URI** unchanged, keep the scopes in line with what you added in Google, and select **Create Auth Config**.
48 +
49 + ![YouTube auth config form with Client ID, Client secret, Redirect URI, and the youtube.readonly scope](/images/toolkits/youtube/auth-config-credentials.webp)
50 +
51 +3. Open the auth config, select **Connect Account**, and sign in. If Google asks, pick the YouTube channel or Brand Account you want to connect.
52 +
53 + ![Google consent screen asking to view your YouTube account](/images/toolkits/youtube/google-consent-screen.webp)
54 +
55 +4. Open **Accounts** on the auth config and confirm the connected account shows **Active**. The auth config's own **Enabled** label doesn't confirm a connection.
56 +
57 + ![Composio auth config panel with the YouTube connected account shown as Active](/images/toolkits/youtube/connected-account-active.webp)
58 +
59 +For the general flow, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
60 +
61 +### Scopes
62 +
63 +The default auth config requests these scopes under `https://www.googleapis.com/auth/`: `youtube`, `youtube.readonly`, `youtube.force-ssl`, `youtube.upload`, `youtube.channel-memberships.creator`, `youtubepartner`, and `youtubepartner-channel-audit`. To only read channel data, `youtube.readonly` is enough. Uploads, content management, memberships, and partner operations need their own scopes and, for some, YouTube eligibility. See Google's [YouTube authentication guide](https://developers.google.com/youtube/v3/guides/authentication).
64 +
65 +Short scope names on this page leave out the `https://www.googleapis.com/auth/` prefix. When you paste a scope under **Manually add scopes**, use the full URL, for example `https://www.googleapis.com/auth/userinfo.email`. Scopes already written as a full URL, such as `https://mail.google.com/`, go in as shown.
66 +
67 +### Publish and verify the app
68 +
69 +While an external app is in **Testing**, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select **Publish app** on the **Audience** page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from **Verification Center**. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's [verification requirements](https://developers.google.com/identity/protocols/oauth2/production-readiness/overview).
70 +
71 +![Google hasn't verified this app notice for an app in Testing](/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp)
72 +
73 +If you change the requested scopes later, reconnect the account so the user grants the new access.
74
75 ## Why am I getting quota errors on YouTube?
76
docs/content/toolkits/faq/zendesk.md
+33 -1
@@ -1,3 +1,35 @@
1 ## How do I set up custom OAuth credentials for Zendesk?
2
3 -For a step-by-step guide on creating and configuring your own Zendesk OAuth credentials with Composio, see [How to create OAuth credentials for Zendesk](https://composio.dev/auth/zendesk).
3 +Use your own Zendesk OAuth client when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Zendesk OAuth client
6 +
7 +1. Sign in to Zendesk Admin Center at `https://<subdomain>.zendesk.com/admin/home`.
8 +2. In the sidebar, click **Apps and integrations**, then **APIs**, and open the **OAuth clients** tab.
9 +3. Click **Add OAuth client** and fill in the form:
10 + - **Client Name**: for example, `Composio-Zendesk`.
11 + - **Description**: optional.
12 + - **Redirect URLs**: `https://backend.composio.dev/api/v1/auth-apps/add`. It must use `https`, have no trailing slash, and exactly match the `oauth_redirect_uri` field in your Composio auth config.
13 +4. Save the client and copy the **Identifier** (the client ID) and the **Secret**.
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Zendesk**.
18 +
19 + ![Composio Auth Configs page with the Create Auth Config button](/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp)
20 +
21 + ![Composio Create Auth Config dialog with Zendesk in the search results](/images/toolkits/zendesk/select-toolkit.webp)
22 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
23 +
24 + ![Zendesk auth config form with OAUTH2, the default scopes, and Use your own developer credentials enabled](/images/toolkits/zendesk/oauth2-own-credentials.webp)
25 +3. Paste the client ID and secret, then click **Create Zendesk Auth Config**.
26 +4. Click **Connect Account** and enter your Zendesk subdomain, the part before `.zendesk.com` (for example `acme` in `acme.zendesk.com`).
27 +5. Approve access in Zendesk and confirm the account shows as **Active**.
28 +
29 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
30 +
31 +### Scopes
32 +
33 +Zendesk has no scope settings in Admin Center. Scopes are requested during authorization from the auth config's **Scopes** field. The default auth config requests `read`, `write`, and resource scopes for organizations, tickets, users, and webhooks, such as `tickets:read` and `tickets:write`.
34 +
35 +The user's Zendesk role (agent, admin, and so on) still limits what the connection can do, even when broader scopes are granted.
docs/content/toolkits/faq/zoho.md
+28 -1
@@ -1,3 +1,30 @@
1 ## How do I set up custom OAuth credentials for Zoho CRM?
2
3 -For a step-by-step guide on creating and configuring your own Zoho CRM OAuth credentials with Composio, see [How to create OAuth credentials for Zoho CRM](https://composio.dev/auth/zoho).
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho CRM. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications**. Composio's callback is a backend endpoint, so a client-based app won't work. You can reuse an existing server-based client if it has the right redirect URI.
9 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
10 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
11 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
12 +
13 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret fields](/images/toolkits/zoho/client-secret.webp)
14 +
15 +### Create the auth config in Composio
16 +
17 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho), go to **Auth Configs** → **Create** and select **Zoho CRM**.
18 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret.
19 +3. Adjust the scopes if needed (see below) and click **Create Auth Config**.
20 +4. Click **Connect Account**, enter your data center code in **Region**, and accept the permissions on Zoho's consent screen. Check that the account shows **Active**.
21 +
22 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
23 +
24 +### Scopes
25 +
26 +The Zoho API Console has no scope settings. Zoho takes scopes from the authorization request, so you set them in the auth config. The default auth config requests `ZohoCRM.modules.ALL`, `ZohoCRM.settings.ALL`, and `ZohoCRM.users.ALL`. Add or remove scopes to match the tools you use; extra scopes add to what the user has to approve. See Zoho's [CRM scope reference](https://www.zoho.com/crm/developer/docs/api/v8/select-api-scopes.html).
27 +
28 +### Data center
29 +
30 +**Region** is the ending of your Zoho web address when you're signed in: `com` for `zoho.com`, `eu` for `zoho.eu`, `in` for `zoho.in`, and so on. Enter the code only, not a full URL. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
docs/content/toolkits/faq/zoho_bigin.md new
+56
@@ -0,0 +1,56 @@
1 +## How do I set up custom OAuth credentials for Zoho Bigin?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need access to an existing Zoho Bigin organization.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho Bigin. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications** → **Create Now**. You can reuse an existing server-based client if it has the right redirect URI.
9 +
10 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp)
11 +
12 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
13 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
14 +
15 + ![Zoho API Console Create New Client form with the Composio redirect URI](/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp)
16 +
17 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
18 +
19 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp)
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_bigin), go to **Auth Configs** → **Create** and select **Zoho Bigin**.
24 +
25 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
26 +
27 +3. In **Scopes**, keep only what your workflow needs. To add a scope that isn't listed, type its exact name and click **Add scope**. Click **Create Auth Config**.
28 +
29 +4. Click **Connect Account** and enter your data center code in **Region** (see below).
30 +
31 + ![Composio Connect Account form with a data center code in Region](/images/toolkits/zoho_bigin/data-center.webp)
32 +
33 +5. Sign in to Zoho, review the app name, organization, and permissions, tick the consent checkbox if shown, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
34 +
35 + ![Zoho consent screen for Zoho Bigin with the consent checkbox and Accept button](/images/toolkits/zoho_bigin/consent-screen.webp)
36 +
37 + ![Zoho Bigin auth config Accounts tab with the connected account Active](/images/toolkits/zoho_bigin/account-active.webp)
38 +
39 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
40 +
41 +### Scopes
42 +
43 +Zoho takes scopes from the authorization request, so you set them in the auth config, not in the API Console. The default auth config requests `ZohoBigin.modules.ALL`, `ZohoBigin.users.ALL`, `ZohoBigin.org.ALL`, `ZohoBigin.settings.ALL`, `ZohoBigin.bulk.ALL`, and `ZohoBigin.notifications.ALL`. For a read-only check of organization details, `ZohoBigin.org.READ` is enough. Check each tool against the [Bigin API reference](https://www.bigin.com/developer/docs/apis/v2/).
44 +
45 +If you add scopes later, reconnect the account. An existing connection doesn't pick up new permissions.
46 +
47 +### Data center
48 +
49 +**Region** is the ending of your Zoho Bigin web address: `com` for `bigin.zoho.com`, `eu` for `bigin.zoho.eu`, `in` for `bigin.zoho.in`, `au` for `bigin.zoho.com.au`. Other options are `jp`, `ca`, `cn`, and `sa`. Enter the code only, not a full URL. The client's data center and the account's data center must be compatible. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
50 +
51 +### Troubleshooting
52 +
53 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
54 +- **Invalid client or data center error**: check the API Console's data center, the account's data center, and **Region**.
55 +- **Permission or organization error**: check that the user can access the Zoho Bigin organization and that the auth config requests the scope the tool needs.
56 +- **"Cannot grant these permissions as you don't have access to Bigin"**: ask your Zoho One administrator to assign Bigin to your user, then retry. Registering an OAuth client doesn't give an account access to Bigin.
docs/content/toolkits/faq/zoho_books.md new
+55
@@ -0,0 +1,55 @@
1 +## How do I set up custom OAuth credentials for Zoho Books?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need access to an existing Zoho Books organization.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho Books. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications** → **Create Now**. You can reuse an existing server-based client if it has the right redirect URI.
9 +
10 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp)
11 +
12 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
13 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
14 +
15 + ![Zoho API Console Create New Client form with the Composio redirect URI](/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp)
16 +
17 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
18 +
19 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp)
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_books), go to **Auth Configs** → **Create** and select **Zoho Books**.
24 +
25 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
26 +
27 +3. In **Scopes**, keep only what your workflow needs. To add a scope that isn't listed, type its exact name and click **Add scope**. Click **Create Auth Config**.
28 +
29 +4. Click **Connect Account** and enter your data center code in **Domain Extension** (see below).
30 +
31 + ![Composio Connect Account form with a data center code in Domain Extension](/images/toolkits/zoho_books/data-center.webp)
32 +
33 +5. Sign in to Zoho, review the app name, organization, and permissions, tick the consent checkbox if shown, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
34 +
35 + ![Zoho consent screen for Zoho Books with the consent checkbox and Accept button](/images/toolkits/zoho_books/consent-screen.webp)
36 +
37 + ![Zoho Books auth config Accounts tab with the connected account Active](/images/toolkits/zoho_books/account-active.webp)
38 +
39 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
40 +
41 +### Scopes
42 +
43 +Zoho takes scopes from the authorization request, so you set them in the auth config, not in the API Console. The default auth config requests `ZohoBooks.fullaccess.all`. For a read-only check of organization and user details, `ZohoBooks.settings.READ` is enough. Check each tool against the [Zoho Books API reference](https://www.zoho.com/books/api/v3/introduction/).
44 +
45 +If you add scopes later, reconnect the account. An existing connection doesn't pick up new permissions.
46 +
47 +### Data center
48 +
49 +**Domain Extension** is the ending of your Zoho Books web address: `com` for `books.zoho.com`, `eu` for `books.zoho.eu`, `in` for `books.zoho.in`, `au` for `books.zoho.com.au`. Other options are `jp`, `ca`, `cn`, and `sa`. Enter the code only, not a full URL. The client's data center and the account's data center must be compatible. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
50 +
51 +### Troubleshooting
52 +
53 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
54 +- **Invalid client or data center error**: check the API Console's data center, the account's data center, and **Domain Extension**.
55 +- **Permission or organization error**: check that the user can access the Zoho Books organization and that the auth config requests the scope the tool needs.
docs/content/toolkits/faq/zoho_desk.md new
+54
@@ -0,0 +1,54 @@
1 +## How do I set up custom OAuth credentials for Zoho Desk?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need access to an existing Zoho Desk organization.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho Desk. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications** → **Create Now**. You can reuse an existing server-based client if it has the right redirect URI.
9 +
10 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp)
11 +
12 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
13 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
14 +
15 + ![Zoho API Console Create New Client form with the Composio redirect URI](/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp)
16 +
17 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
18 +
19 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp)
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_desk), go to **Auth Configs** → **Create** and select **Zoho Desk**.
24 +
25 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
26 +
27 +3. In **Scopes**, keep only what your workflow needs. To add a scope that isn't listed, type its exact name and click **Add scope**. Click **Create Auth Config**.
28 +4. Click **Connect Account** and enter your data center code in **Domain Extension** (see below).
29 +
30 + ![Composio Connect Account form with a data center code in Domain Extension](/images/toolkits/zoho_desk/data-center.webp)
31 +
32 +5. Sign in to Zoho, review the app name, organization, and permissions, tick the consent checkbox if shown, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
33 +
34 + ![Zoho consent screen for Zoho Desk with the consent checkbox and Accept button](/images/toolkits/zoho_desk/consent-screen.webp)
35 +
36 + ![Zoho Desk auth config Accounts tab with the connected account Active](/images/toolkits/zoho_desk/account-active.webp)
37 +
38 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
39 +
40 +### Scopes
41 +
42 +Zoho takes scopes from the authorization request, so you set them in the auth config, not in the API Console. The default auth config requests `Desk.contacts.ALL`, `Desk.tickets.ALL`, `Desk.tasks.ALL`, `Desk.settings.ALL`, and `Desk.events.ALL`. For read-only access, `Desk.basic.READ` covers basic organization details, and `Desk.contacts.READ` plus `Desk.search.READ` cover listing help center users. Check each operation in the [Zoho Desk API reference](https://desk.zoho.com/DeskAPIDocument).
43 +
44 +If you add scopes later, reconnect the account. An existing connection doesn't pick up new permissions.
45 +
46 +### Data center
47 +
48 +**Domain Extension** is the ending of your Zoho Desk web address: `com` for `desk.zoho.com`, `eu` for `desk.zoho.eu`, `in` for `desk.zoho.in`, `au` for `desk.zoho.com.au`. Other options are `jp`, `ca`, `cn`, and `sa`. Enter the code only, not a full URL. The client's data center and the account's data center must be compatible. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
49 +
50 +### Troubleshooting
51 +
52 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
53 +- **Invalid client or data center error**: check the API Console's data center, the account's data center, and **Domain Extension**.
54 +- **Permission or organization error**: check that the user can access the Zoho Desk organization and that the auth config requests the scope the tool needs.
docs/content/toolkits/faq/zoho_inventory.md new
+54
@@ -0,0 +1,54 @@
1 +## How do I set up custom OAuth credentials for Zoho Inventory?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need access to an existing Zoho Inventory organization.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho Inventory. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications** → **Create Now**. You can reuse an existing server-based client if it has the right redirect URI.
9 +
10 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp)
11 +
12 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
13 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
14 +
15 + ![Zoho API Console Create New Client form with the Composio redirect URI](/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp)
16 +
17 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
18 +
19 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp)
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_inventory), go to **Auth Configs** → **Create** and select **Zoho Inventory**.
24 +
25 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
26 +
27 +3. In **Scopes**, keep only what your workflow needs. To add a scope that isn't listed, type its exact name and click **Add scope**. Click **Create Auth Config**.
28 +4. Click **Connect Account** and enter your data center code in **Region** (see below). **Organization ID** is optional: enter it to pick a specific Inventory organization (find it under **Settings** → **Organization Profile**). If you leave it blank, Composio uses the first organization available to the account.
29 +
30 + ![Composio Connect Account form with a data center code in Region and the optional Organization ID field](/images/toolkits/zoho_inventory/data-center.webp)
31 +
32 +5. Sign in to Zoho, review the app name, organization, and permissions, tick the consent checkbox if shown, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
33 +
34 + ![Zoho consent screen for Zoho Inventory with the consent checkbox and Accept button](/images/toolkits/zoho_inventory/consent-screen.webp)
35 +
36 + ![Zoho Inventory auth config Accounts tab with the connected account Active](/images/toolkits/zoho_inventory/account-active.webp)
37 +
38 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
39 +
40 +### Scopes
41 +
42 +Zoho takes scopes from the authorization request, so you set them in the auth config, not in the API Console. The default auth config requests the `.ALL` scopes for contacts, items, composite items, transfer orders, sales orders, packages, shipment orders, invoices, customer payments, credit notes, purchase orders, purchase receives, and bills, plus `ZohoInventory.settings.READ`. For a read-only check of organization details, `ZohoInventory.settings.READ` is enough. Check each tool against the [Zoho Inventory API reference](https://www.zoho.com/inventory/api/v1/introduction/).
43 +
44 +If you add scopes later, reconnect the account. An existing connection doesn't pick up new permissions.
45 +
46 +### Data center
47 +
48 +**Region** is the ending of your Zoho Inventory web address: `com` for `inventory.zoho.com`, `eu` for `inventory.zoho.eu`, `in` for `inventory.zoho.in`, `au` for `inventory.zoho.com.au`. Other options are `jp`, `ca`, `cn`, and `sa`. Enter the code only, not a full URL. The client's data center and the account's data center must be compatible. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
49 +
50 +### Troubleshooting
51 +
52 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
53 +- **Invalid client or data center error**: check the API Console's data center, the account's data center, and **Region**.
54 +- **Permission or organization error**: check that the user can access the Zoho Inventory organization and that the auth config requests the scope the tool needs.
docs/content/toolkits/faq/zoho_invoice.md new
+55
@@ -0,0 +1,55 @@
1 +## How do I set up custom OAuth credentials for Zoho Invoice?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need access to an existing Zoho Invoice organization.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/) with the account you use for Zoho Invoice. Use the console for your account's data center, for example `https://api-console.zoho.in/` for India.
8 +2. Click **Add Client** (or **Get Started** for your first client) and choose **Server-based Applications** → **Create Now**. You can reuse an existing server-based client if it has the right redirect URI.
9 +
10 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp)
11 +
12 +3. Enter a **Client Name** and a **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO`.
13 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
14 +
15 + ![Zoho API Console Create New Client form with the Composio redirect URI](/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp)
16 +
17 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
18 +
19 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp)
20 +
21 +### Create the auth config in Composio
22 +
23 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_invoice), go to **Auth Configs** → **Create** and select **Zoho Invoice**.
24 +
25 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
26 +
27 +3. In **Scopes**, keep only what your workflow needs. To add a scope that isn't listed, type its exact name and click **Add scope**. Click **Create Auth Config**.
28 +
29 +4. Click **Connect Account** and enter your data center code in **Domain Extension** (see below).
30 +
31 + ![Composio Connect Account form with a data center code in Domain Extension](/images/toolkits/zoho_invoice/data-center.webp)
32 +
33 +5. Sign in to Zoho, review the app name, organization, and permissions, tick the consent checkbox if shown, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
34 +
35 + ![Zoho consent screen for Zoho Invoice with the consent checkbox and Accept button](/images/toolkits/zoho_invoice/consent-screen.webp)
36 +
37 + ![Zoho Invoice auth config Accounts tab with the connected account Active](/images/toolkits/zoho_invoice/account-active.webp)
38 +
39 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
40 +
41 +### Scopes
42 +
43 +Zoho takes scopes from the authorization request, so you set them in the auth config, not in the API Console. The default auth config requests the `.ALL` scopes for contacts, settings, estimates, invoices, customer payments, credit notes, projects, and expenses (for example `ZohoInvoice.invoices.ALL`). For a read-only check of organization and user details, `ZohoInvoice.settings.READ` is enough. Check each tool against the [Zoho Invoice API reference](https://www.zoho.com/invoice/api/v3/introduction/).
44 +
45 +If you add scopes later, reconnect the account. An existing connection doesn't pick up new permissions.
46 +
47 +### Data center
48 +
49 +**Domain Extension** is the ending of your Zoho Invoice web address: `com` for `invoice.zoho.com`, `eu` for `invoice.zoho.eu`, `in` for `invoice.zoho.in`, `au` for `invoice.zoho.com.au`. Other options are `jp`, `ca`, `cn`, and `sa`. Enter the code only, not a full URL. The client's data center and the account's data center must be compatible. If your app connects accounts in more than one data center, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) for those regions on the client in the API Console.
50 +
51 +### Troubleshooting
52 +
53 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
54 +- **Invalid client or data center error**: check the API Console's data center, the account's data center, and **Domain Extension**.
55 +- **Permission or organization error**: check that the user can access the Zoho Invoice organization and that the auth config requests the scope the tool needs.
docs/content/toolkits/faq/zoho_mail.md
+81 -1
@@ -1,3 +1,83 @@
1 +## How do I set up custom OAuth credentials for Zoho Mail?
2 +
3 +Use your own Zoho OAuth client when you want the consent screen to show your app name and to manage the client credentials yourself. You need an existing Zoho Mail account.
4 +
5 +### Create the Zoho OAuth client
6 +
7 +1. Sign in to the [Zoho API Console](https://api-console.zoho.com/). Click **Add Client** (or **Get Started** for your first client).
8 +
9 + ![Zoho API Console Applications list with the Add Client button](/images/toolkits/zoho_mail/add-client.webp)
10 +
11 +2. Choose **Server-based Applications** and click **Create Now**. See Zoho's [client registration guide](https://www.zoho.com/developer/oauth/register-app.html).
12 +
13 + ![Zoho API Console client type picker with Server-based Applications](/images/toolkits/zoho_mail/client-type.webp)
14 +
15 +3. Enter a **Client Name** and your application's **Homepage URL**. Use your own product name: Zoho rejects client names that contain `ZOHO` with "Client name should not contain ZOHO".
16 +
17 + ![Zoho API Console Create New Client form showing the "Client name should not contain ZOHO" error](/images/toolkits/zoho_mail/client-name-error.webp)
18 +
19 +4. In **Authorized Redirect URIs**, enter `https://backend.composio.dev/api/v1/auth-apps/add`. It must exactly match the auth config's `oauth_redirect_uri` field.
20 +
21 + ![Zoho API Console Client Details tab with the Composio redirect URI saved](/images/toolkits/zoho_mail/client-details.webp)
22 +
23 +5. Click **Create**, then open the **Client Secret** tab and copy the **Client ID** and **Client Secret**.
24 +
25 + ![Zoho API Console Client Secret tab with the Client ID and Client Secret (redacted)](/images/toolkits/zoho_mail/client-secret.webp)
26 +
27 +### Create the auth config in Composio
28 +
29 +1. In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=toolkits-zoho_mail), go to **Auth Configs** → **Create** and select **Zoho Mail**.
30 +
31 + ![Composio Create Auth Config dialog with Zoho Mail selected](/images/toolkits/zoho_mail/select-toolkit.webp)
32 +
33 +2. Choose **OAuth 2.0** and **Your Own Credentials**, then paste the Client ID and Client Secret. Leave **Redirect URI** as the value you registered in Zoho.
34 +
35 +3. Enter the scopes your workflow needs (see below) and click **Create Auth Config**. To add a scope that isn't listed, type its exact name and click **Add scope**.
36 +
37 + ![Zoho Mail auth config scope picker adding ZohoMail.accounts.READ by exact name](/images/toolkits/zoho_mail/add-scope.webp)
38 +
39 +4. Click **Connect Account** and enter the account's data center code in **Domain Extension** (see the region question below).
40 +
41 + ![Saved Zoho Mail auth config with the Connect Account button](/images/toolkits/zoho_mail/connect-account.webp)
42 +
43 + ![Composio Connect Account form with a data center code in Domain Extension](/images/toolkits/zoho_mail/data-center.webp)
44 +
45 +5. Sign in to Zoho Mail, review the app name and permissions, tick the consent checkbox, and click **Accept**. Then open the auth config's **Accounts** tab and check that the account shows **Active**. The config showing **Enabled** doesn't mean an account is connected.
46 +
47 + ![Zoho consent screen asking to view mail account information](/images/toolkits/zoho_mail/consent-screen.webp)
48 +
49 + ![Zoho Mail auth config Accounts tab with the connected account Active](/images/toolkits/zoho_mail/account-active.webp)
50 +
51 +See [custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
52 +
53 +### Scopes
54 +
55 +The default auth config requests no scopes, but Zoho requires scope names in the authorization request, so add the ones your tools need. Scope names are case-sensitive. Common ones:
56 +
57 +- `ZohoMail.accounts.READ`: list the user's mail accounts
58 +- `ZohoMail.messages.READ`: read messages
59 +- `ZohoMail.messages.CREATE`: send messages
60 +
61 +See the [Zoho Mail API reference](https://www.zoho.com/mail/help/api/) for the scope each operation needs.
62 +
63 +### Troubleshooting
64 +
65 +- **Invalid client or region error**: check the client's data center, the account's data center, and **Domain Extension**.
66 +- **Invalid scope**: use the exact, case-sensitive Zoho Mail scope names.
67 +- **Redirect mismatch**: compare the full callback URL in Zoho and in Composio, including the path.
68 +
69 ## What should I pass for the correct Zoho region when connecting Zoho Mail?
70
3 -For Zoho Mail connection issues, verify the region passed during connection initiation. Zoho accounts can be region-specific, so an EU or other regional account may fail if the default/wrong region is used. Retry the connection with the correct Zoho region.
71 +Enter the code from your Zoho Mail web address in **Domain Extension**. Zoho accounts live in one data center, so an EU or other regional account fails if you connect with the default `com`.
72 +
73 +- `mail.zoho.com`: `com`
74 +- `mail.zoho.eu`: `eu`
75 +- `mail.zoho.in`: `in`
76 +- `mail.zoho.com.au`: `au`
77 +- `mail.zohocloud.ca`: `ca`
78 +- `mail.zoho.com.cn`: `cn`
79 +- `mail.zoho.jp`: `jp`
80 +- `mail.zoho.ae`: `ae`
81 +- `mail.zoho.sa`: `sa`
82 +
83 +Enter the code only, not a full URL. If your app connects users in data centers other than the one where you registered the client, enable [multi-DC support](https://www.zoho.com/developer/oauth/web-server-apps/overview.html) in the API Console. See Zoho's [Mail data center list](https://www.zoho.com/mail/help/api/getting-started-with-api.html).
docs/content/toolkits/faq/zoom.md
+27 -1
@@ -1,3 +1,29 @@
1 ## How do I set up custom OAuth credentials for Zoom?
2
3 -For a step-by-step guide on creating and configuring your own Zoom OAuth credentials with Composio, see [How to create OAuth credentials for Zoom](https://composio.dev/auth/zoom).
3 +Use your own Zoom OAuth app when you want users to see your app's name on the consent screen and control the credentials yourself.
4 +
5 +### Create the Zoom app
6 +
7 +1. Go to the [Zoom App Marketplace](https://marketplace.zoom.us/develop/create) and create a **General** app. Composio connects users through the OAuth authorization flow, which a General app supports.
8 +
9 + ![Zoom App Marketplace dialog asking what kind of app you are creating, with General App selected](/images/toolkits/zoom/choose-general-app.webp)
10 +2. On the app's **Basic Information** tab, under **App Credentials**, copy the **Client ID** and **Client Secret**. You can set the app name and developer details separately for the **Development** and **Production** environments.
11 +
12 + ![Zoom app header with the Development and Production environment tabs](/images/toolkits/zoom/development-production-tabs.webp)
13 +3. In the **OAuth Information** section below the credentials, add `https://backend.composio.dev/api/v1/auth-apps/add` as the redirect URL. It must exactly match the `oauth_redirect_uri` field in your Composio auth config.
14 +4. Open the **Scopes** tab and click **+ Add Scopes**. Zoom enables no scopes by default, so add every scope your tools need (see below).
15 +
16 +### Create the auth config in Composio
17 +
18 +1. In the Composio dashboard, go to **Auth Configs**, click **Create Auth Config**, and select **Zoom**.
19 +2. Set the authentication type to **OAuth2** and choose **Use your own developer authentication**.
20 +3. Paste the **Client ID** and **Client Secret**, then click **Create Zoom Auth Config**.
21 +4. Click **Connect Account**, click **Allow** on the Zoom authorization screen, and confirm the account shows as **Active**.
22 +
23 +See [Custom auth configs](/docs/auth-configuration/custom-auth-configs) for the general flow.
24 +
25 +### Scopes
26 +
27 +The default auth config requests granular scopes for meetings, webinars, cloud recordings, archiving, contacts, and users, for example `meeting:read:meeting`, `meeting:write:meeting`, `webinar:read:list_webinars`, `cloud_recording:read:list_recording_files`, and `user:read:user`. Add the same scopes to your Zoom app, or remove the ones you don't need from the auth config's **Scopes** field on **Manage Auth Config**.
28 +
29 +While testing in the Development environment, you can select all scopes and remove the unneeded ones before you move to Production.
docs/lib/knowledge/auth-guides.ts
+22 -28
@@ -1,3 +1,4 @@
1 +import { z } from 'zod';
2 import authGuideRegistry from '@/kb/external-sources/auth-guides.json';
3 import type { AlgoliaDocsRecord } from '@/lib/search-index';
4 import {
@@ -8,33 +9,26 @@ import {
9 export interface AuthGuideRegistryEntry {
10 slug: string;
11 toolkitSlug: string;
11 - canonicalUrl: `https://composio.dev/auth/${string}`;
12 + canonicalUrl: `/toolkits/${string}`;
13 title: string;
14 description: string;
15 }
16
17 function parseRegistry(value: unknown): AuthGuideRegistryEntry[] {
17 - if (!Array.isArray(value)) throw new Error('OAuth guide registry must be an array');
18 -
19 - const entries = value.map((candidate, index) => {
20 - if (!candidate || typeof candidate !== 'object') {
21 - throw new Error(`OAuth guide registry entry ${index} must be an object`);
22 - }
23 - const entry = candidate as Record<string, unknown>;
24 - const slug = typeof entry.slug === 'string' ? entry.slug.trim() : '';
25 - const toolkitSlug = typeof entry.toolkitSlug === 'string' ? entry.toolkitSlug.trim() : '';
26 - const canonicalUrl = typeof entry.canonicalUrl === 'string' ? entry.canonicalUrl.trim() : '';
27 - const title = typeof entry.title === 'string' ? entry.title.trim() : '';
28 - const description = typeof entry.description === 'string' ? entry.description.trim() : '';
29 -
30 - if (!/^[a-z0-9-]+$/.test(slug)) throw new Error(`Invalid OAuth guide slug at entry ${index}`);
31 - if (!toolkitSlug) throw new Error(`Missing OAuth guide toolkit slug for ${slug}`);
32 - if (canonicalUrl !== `https://composio.dev/auth/${slug}`) {
33 - throw new Error(`Invalid OAuth guide canonical URL for ${slug}`);
34 - }
35 - if (!title || !description) throw new Error(`Missing OAuth guide copy for ${slug}`);
36 -
37 - return { slug, toolkitSlug, canonicalUrl, title, description } as AuthGuideRegistryEntry;
18 + // The imported snapshot retains landing URLs. Resolve destinations here so
19 + // refreshing that snapshot cannot restore retired routes to the search index.
20 + const entries = z.array(z.object({
21 + slug: z.string().trim().regex(/^[a-z0-9-]+$/),
22 + toolkitSlug: z.string().trim().regex(/^[a-z0-9_-]+$/),
23 + title: z.string().trim().min(1),
24 + description: z.string().trim().min(1),
25 + })).parse(value).map((entry): AuthGuideRegistryEntry => {
26 + const toolkitSlug = entry.toolkitSlug === 'googleapps' ? 'googlesuper' : entry.toolkitSlug;
27 + return {
28 + ...entry,
29 + toolkitSlug,
30 + canonicalUrl: `/toolkits/${toolkitSlug}`,
31 + };
32 });
33
34 if (new Set(entries.map((entry) => entry.slug)).size !== entries.length) {
@@ -95,19 +89,20 @@ export async function validateAuthGuideUrls(
89 fetchImpl: typeof fetch = fetch,
90 ): Promise<void> {
91 await Promise.all(entries.map(async (entry) => {
92 + const expected = new URL(entry.canonicalUrl, 'https://docs.composio.dev');
93 let response: Response;
94 try {
100 - response = await fetchImpl(entry.canonicalUrl, {
95 + response = await fetchImpl(expected.href, {
96 method: 'GET',
97 redirect: 'follow',
98 headers: { accept: 'text/html' },
99 });
100 } catch (error) {
106 - throw new Error(`Failed to validate OAuth guide ${entry.canonicalUrl}`, { cause: error });
101 + throw new Error(`Failed to validate OAuth guide ${expected.href}`, { cause: error });
102 }
103 if (!response.ok) {
104 throw new Error(
110 - `Failed to validate OAuth guide ${entry.canonicalUrl}: HTTP ${response.status}`,
105 + `Failed to validate OAuth guide ${expected.href}: HTTP ${response.status}`,
106 );
107 }
108
@@ -117,14 +112,13 @@ export async function validateAuthGuideUrls(
112 finalUrl = `${resolved.origin}${resolved.pathname.replace(/\/+$/, '')}`;
113 } catch {
114 throw new Error(
120 - `Failed to validate OAuth guide ${entry.canonicalUrl}: missing final response URL`,
115 + `Failed to validate OAuth guide ${expected.href}: missing final response URL`,
116 );
117 }
123 - const expected = new URL(entry.canonicalUrl);
118 const expectedUrl = `${expected.origin}${expected.pathname.replace(/\/+$/, '')}`;
119 if (finalUrl !== expectedUrl) {
120 throw new Error(
127 - `Failed to validate OAuth guide ${entry.canonicalUrl}: redirected to ${response.url}`,
121 + `Failed to validate OAuth guide ${expected.href}: redirected to ${response.url}`,
122 );
123 }
124 }));
docs/lib/knowledge/catalog.ts
+1 -1
@@ -39,7 +39,7 @@ const FEATURED_CANONICAL_URLS = [
39 '/kb/guide/platform-pagination',
40 '/kb/guide/platform-triggers',
41 '/kb/guide/platform-custom-connection-data-fields',
42 - 'https://composio.dev/auth/github',
42 + '/toolkits/github',
43 ] as const;
44
45 let catalogPromise: Promise<KnowledgeLink[]> | null = null;
docs/lib/search-index.ts
+8 -1
@@ -747,7 +747,14 @@ export async function getDocsSearchIndexes(): Promise<SearchIndex[]> {
747 keywords: record.keywords,
748 } satisfies SearchIndex));
749
750 - return [...mdxIndexes, ...dynamicToolkitIndexes, ...getChangelogIndexes(), ...oauthIndexes];
750 + // Migrated auth guides share the toolkit page, so keep one local search hit.
751 + const oauthUrls = new Set(oauthIndexes.map(index => index.url));
752 + return [
753 + ...mdxIndexes,
754 + ...dynamicToolkitIndexes.filter(index => !oauthUrls.has(index.url)),
755 + ...getChangelogIndexes(),
756 + ...oauthIndexes,
757 + ];
758 }
759
760 async function getOpenApiRecords(): Promise<AlgoliaDocsRecord[]> {
docs/public/images/toolkits/airtable/oauth-integrations-list.webp
Binary files /dev/null and b/docs/public/images/toolkits/airtable/oauth-integrations-list.webp differ
docs/public/images/toolkits/apollo/admin-settings-menu.webp
Binary files /dev/null and b/docs/public/images/toolkits/apollo/admin-settings-menu.webp differ
docs/public/images/toolkits/apollo/auth-config-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/apollo/auth-config-api-key.webp differ
docs/public/images/toolkits/apollo/integrations-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/apollo/integrations-api.webp differ
docs/public/images/toolkits/apollo/paste-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/apollo/paste-api-key.webp differ
docs/public/images/toolkits/apollo/select-apollo.webp
Binary files /dev/null and b/docs/public/images/toolkits/apollo/select-apollo.webp differ
docs/public/images/toolkits/asana/client-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/asana/client-credentials.webp differ
docs/public/images/toolkits/asana/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/asana/create-app.webp differ
docs/public/images/toolkits/asana/create-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/asana/create-auth-config.webp differ
docs/public/images/toolkits/asana/oauth-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/asana/oauth-scopes.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/add-a-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/add-a-permission.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/azure-service-management-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/azure-service-management-api.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/azure-subscriptions.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/azure-subscriptions.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-auth-configs.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-config-name.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-connect-account.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-oauth-credentials.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-scopes.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/composio-toolkit-picker.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/connected-account-active.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/connection-success.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/connection-success.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/microsoft-consent.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/subscription-id-field.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/subscription-id-field.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/user-impersonation-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/user-impersonation-details.webp differ
docs/public/images/toolkits/azure_monitor_activity_log/user-impersonation-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/azure_monitor_activity_log/user-impersonation-permission.webp differ
docs/public/images/toolkits/bitbucket/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/account-active.webp differ
docs/public/images/toolkits/bitbucket/auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/auth-configs.webp differ
docs/public/images/toolkits/bitbucket/authorisation-callback.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/authorisation-callback.webp differ
docs/public/images/toolkits/bitbucket/client-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/client-credentials.webp differ
docs/public/images/toolkits/bitbucket/connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/connect-account.webp differ
docs/public/images/toolkits/bitbucket/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/consent-screen.webp differ
docs/public/images/toolkits/bitbucket/create-oauth-client.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/create-oauth-client.webp differ
docs/public/images/toolkits/bitbucket/oauth-client-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/oauth-client-details.webp differ
docs/public/images/toolkits/bitbucket/oauth-clients-nav.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/oauth-clients-nav.webp differ
docs/public/images/toolkits/bitbucket/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/own-credentials.webp differ
docs/public/images/toolkits/bitbucket/redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/redirect-uri.webp differ
docs/public/images/toolkits/bitbucket/scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/scopes.webp differ
docs/public/images/toolkits/bitbucket/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/select-toolkit.webp differ
docs/public/images/toolkits/bitbucket/workspace-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/bitbucket/workspace-settings.webp differ
docs/public/images/toolkits/calendly/auth-config-oauth2.webp
Binary files /dev/null and b/docs/public/images/toolkits/calendly/auth-config-oauth2.webp differ
docs/public/images/toolkits/calendly/client-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/calendly/client-credentials.webp differ
docs/public/images/toolkits/calendly/my-apps.webp
Binary files /dev/null and b/docs/public/images/toolkits/calendly/my-apps.webp differ
docs/public/images/toolkits/calendly/select-calendly.webp
Binary files /dev/null and b/docs/public/images/toolkits/calendly/select-calendly.webp differ
docs/public/images/toolkits/canva/credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/canva/credentials.webp differ
docs/public/images/toolkits/canva/integration-type.webp
Binary files /dev/null and b/docs/public/images/toolkits/canva/integration-type.webp differ
docs/public/images/toolkits/canva/submit-for-review.webp
Binary files /dev/null and b/docs/public/images/toolkits/canva/submit-for-review.webp differ
docs/public/images/toolkits/canva/your-integrations.webp
Binary files /dev/null and b/docs/public/images/toolkits/canva/your-integrations.webp differ
docs/public/images/toolkits/confluence/api-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/confluence/api-scopes.webp differ
docs/public/images/toolkits/confluence/create-oauth-integration.webp
Binary files /dev/null and b/docs/public/images/toolkits/confluence/create-oauth-integration.webp differ
docs/public/images/toolkits/confluence/missing-scopes-error.webp
Binary files /dev/null and b/docs/public/images/toolkits/confluence/missing-scopes-error.webp differ
docs/public/images/toolkits/confluence/permissions-apis.webp
Binary files /dev/null and b/docs/public/images/toolkits/confluence/permissions-apis.webp differ
docs/public/images/toolkits/docusign/admin-nav.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/admin-nav.webp differ
docs/public/images/toolkits/docusign/apps-and-keys-sidebar.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/apps-and-keys-sidebar.webp differ
docs/public/images/toolkits/docusign/authorization-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/authorization-url.webp differ
docs/public/images/toolkits/docusign/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/consent-screen.webp differ
docs/public/images/toolkits/docusign/cors-save.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/cors-save.webp differ
docs/public/images/toolkits/docusign/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/create-app.webp differ
docs/public/images/toolkits/docusign/redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/redirect-uri.webp differ
docs/public/images/toolkits/docusign/secret-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/secret-key.webp differ
docs/public/images/toolkits/docusign/user-application.webp
Binary files /dev/null and b/docs/public/images/toolkits/docusign/user-application.webp differ
docs/public/images/toolkits/dropbox/auth-config-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/auth-config-credentials.webp differ
docs/public/images/toolkits/dropbox/auth-config-oauth2.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/auth-config-oauth2.webp differ
docs/public/images/toolkits/dropbox/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/create-app.webp differ
docs/public/images/toolkits/dropbox/name-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/name-app.webp differ
docs/public/images/toolkits/dropbox/permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/permissions.webp differ
docs/public/images/toolkits/dropbox/scoped-access.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/scoped-access.webp differ
docs/public/images/toolkits/dropbox/select-dropbox.webp
Binary files /dev/null and b/docs/public/images/toolkits/dropbox/select-dropbox.webp differ
docs/public/images/toolkits/dynamics365/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/composio-auth-configs.webp differ
docs/public/images/toolkits/dynamics365/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/composio-config-name.webp differ
docs/public/images/toolkits/dynamics365/composio-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/composio-own-credentials.webp differ
docs/public/images/toolkits/dynamics365/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/composio-scopes.webp differ
docs/public/images/toolkits/dynamics365/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/composio-toolkit-picker.webp differ
docs/public/images/toolkits/dynamics365/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/configured-permissions.webp differ
docs/public/images/toolkits/dynamics365/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/connected-account-active.webp differ
docs/public/images/toolkits/dynamics365/connection-fields.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/connection-fields.webp differ
docs/public/images/toolkits/dynamics365/dynamics-crm-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/dynamics-crm-api.webp differ
docs/public/images/toolkits/dynamics365/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/microsoft-consent.webp differ
docs/public/images/toolkits/dynamics365/user-impersonation-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/dynamics365/user-impersonation-permission.webp differ
docs/public/images/toolkits/excel/add-a-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/add-a-permission.webp differ
docs/public/images/toolkits/excel/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/composio-auth-configs.webp differ
docs/public/images/toolkits/excel/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/composio-config-name.webp differ
docs/public/images/toolkits/excel/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/composio-connect-account.webp differ
docs/public/images/toolkits/excel/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/composio-toolkit-picker.webp differ
docs/public/images/toolkits/excel/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/connected-account-active.webp differ
docs/public/images/toolkits/excel/files-readwrite-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/files-readwrite-details.webp differ
docs/public/images/toolkits/excel/files-readwrite-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/files-readwrite-permission.webp differ
docs/public/images/toolkits/excel/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/microsoft-account-picker.webp differ
docs/public/images/toolkits/excel/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/excel/microsoft-consent.webp differ
docs/public/images/toolkits/facebook/app-settings-basic.webp
Binary files /dev/null and b/docs/public/images/toolkits/facebook/app-settings-basic.webp differ
docs/public/images/toolkits/facebook/business-portfolio.webp
Binary files /dev/null and b/docs/public/images/toolkits/facebook/business-portfolio.webp differ
docs/public/images/toolkits/facebook/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/facebook/create-app.webp differ
docs/public/images/toolkits/facebook/own-credentials-toggle.webp
Binary files /dev/null and b/docs/public/images/toolkits/facebook/own-credentials-toggle.webp differ
docs/public/images/toolkits/fathom/active-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/active-account.webp differ
docs/public/images/toolkits/fathom/add-to-project.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/add-to-project.webp differ
docs/public/images/toolkits/fathom/allow-access.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/allow-access.webp differ
docs/public/images/toolkits/fathom/api-access-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/api-access-settings.webp differ
docs/public/images/toolkits/fathom/composio-managed-oauth.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/composio-managed-oauth.webp differ
docs/public/images/toolkits/fathom/config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/config-name.webp differ
docs/public/images/toolkits/fathom/connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/connect-account.webp differ
docs/public/images/toolkits/fathom/search-fathom.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/search-fathom.webp differ
docs/public/images/toolkits/fathom/toolkits-page.webp
Binary files /dev/null and b/docs/public/images/toolkits/fathom/toolkits-page.webp differ
docs/public/images/toolkits/github/callback-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/github/callback-url.webp differ
docs/public/images/toolkits/github/oauth-apps-sidebar.webp
Binary files /dev/null and b/docs/public/images/toolkits/github/oauth-apps-sidebar.webp differ
docs/public/images/toolkits/github/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/github/own-credentials.webp differ
docs/public/images/toolkits/github/register-oauth-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/github/register-oauth-app.webp differ
docs/public/images/toolkits/gitlab/application-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/gitlab/application-credentials.webp differ
docs/public/images/toolkits/gitlab/applications-page.webp
Binary files /dev/null and b/docs/public/images/toolkits/gitlab/applications-page.webp differ
docs/public/images/toolkits/gitlab/composio-auth-config-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/gitlab/composio-auth-config-scopes.webp differ
docs/public/images/toolkits/gitlab/new-application-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/gitlab/new-application-form.webp differ
docs/public/images/toolkits/gmail/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/composio-auth-config-form.webp differ
docs/public/images/toolkits/gmail/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/composio-config-name.webp differ
docs/public/images/toolkits/gmail/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/composio-connected-account-active.webp differ
docs/public/images/toolkits/gmail/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/composio-select-toolkit.webp differ
docs/public/images/toolkits/gmail/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/data-access-scopes.webp differ
docs/public/images/toolkits/gmail/enable-gmail-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/enable-gmail-api.webp differ
docs/public/images/toolkits/gmail/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/gmail/google-consent-screen.webp differ
docs/public/images/toolkits/gong/admin-center-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/gong/admin-center-api.webp differ
docs/public/images/toolkits/gong/api-base-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/gong/api-base-url.webp differ
docs/public/images/toolkits/gong/integration-basic-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/gong/integration-basic-details.webp differ
docs/public/images/toolkits/gong/integration-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/gong/integration-scopes.webp differ
docs/public/images/toolkits/google_admin/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_admin/google-consent-screen.webp differ
docs/public/images/toolkits/google_adsense/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_adsense/connected-account-active.webp differ
docs/public/images/toolkits/google_adsense/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_adsense/google-consent-screen.webp differ
docs/public/images/toolkits/google_analytics/auth-config-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/auth-config-credentials.webp differ
docs/public/images/toolkits/google_analytics/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/connected-account-active.webp differ
docs/public/images/toolkits/google_analytics/data-access-analytics-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/data-access-analytics-scope.webp differ
docs/public/images/toolkits/google_analytics/enable-analytics-data-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/enable-analytics-data-api.webp differ
docs/public/images/toolkits/google_analytics/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/google-consent-screen.webp differ
docs/public/images/toolkits/google_analytics/google-sign-in-profile.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/google-sign-in-profile.webp differ
docs/public/images/toolkits/google_analytics/select-google-analytics-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_analytics/select-google-analytics-toolkit.webp differ
docs/public/images/toolkits/google_business_profile/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_business_profile/google-consent-screen.webp differ
docs/public/images/toolkits/google_chat/data-access-chat-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_chat/data-access-chat-scope.webp differ
docs/public/images/toolkits/google_chat/enable-chat-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_chat/enable-chat-api.webp differ
docs/public/images/toolkits/google_chat/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_chat/google-consent-screen.webp differ
docs/public/images/toolkits/google_chat/search-chat-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_chat/search-chat-api.webp differ
docs/public/images/toolkits/google_classroom/data-access-classroom-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_classroom/data-access-classroom-scopes.webp differ
docs/public/images/toolkits/google_classroom/enable-classroom-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_classroom/enable-classroom-api.webp differ
docs/public/images/toolkits/google_classroom/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_classroom/google-consent-screen.webp differ
docs/public/images/toolkits/google_maps/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_maps/google-consent-screen.webp differ
docs/public/images/toolkits/google_merchant/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_merchant/google-consent-screen.webp differ
docs/public/images/toolkits/google_search_console/auth-config-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/auth-config-credentials.webp differ
docs/public/images/toolkits/google_search_console/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/connected-account-active.webp differ
docs/public/images/toolkits/google_search_console/data-access-webmasters-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/data-access-webmasters-scope.webp differ
docs/public/images/toolkits/google_search_console/enable-search-console-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/enable-search-console-api.webp differ
docs/public/images/toolkits/google_search_console/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/google-consent-screen.webp differ
docs/public/images/toolkits/google_search_console/select-google-search-console-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/google_search_console/select-google-search-console-toolkit.webp differ
docs/public/images/toolkits/googleads/auth-config-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/auth-config-credentials.webp differ
docs/public/images/toolkits/googleads/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/connected-account-active.webp differ
docs/public/images/toolkits/googleads/data-access-adwords-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/data-access-adwords-scope.webp differ
docs/public/images/toolkits/googleads/enable-google-ads-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/enable-google-ads-api.webp differ
docs/public/images/toolkits/googleads/enter-customer-id.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/enter-customer-id.webp differ
docs/public/images/toolkits/googleads/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/google-consent-screen.webp differ
docs/public/images/toolkits/googleads/select-google-ads-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleads/select-google-ads-toolkit.webp differ
docs/public/images/toolkits/googlebigquery/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlebigquery/connected-account-active.webp differ
docs/public/images/toolkits/googlebigquery/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlebigquery/google-consent-screen.webp differ
docs/public/images/toolkits/googlecalendar/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/composio-auth-config-form.webp differ
docs/public/images/toolkits/googlecalendar/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/composio-config-name.webp differ
docs/public/images/toolkits/googlecalendar/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/composio-connected-account-active.webp differ
docs/public/images/toolkits/googlecalendar/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/composio-select-toolkit.webp differ
docs/public/images/toolkits/googlecalendar/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/data-access-scopes.webp differ
docs/public/images/toolkits/googlecalendar/enable-calendar-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/enable-calendar-api.webp differ
docs/public/images/toolkits/googlecalendar/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecalendar/google-consent-screen.webp differ
docs/public/images/toolkits/googlecontacts/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecontacts/data-access-scopes.webp differ
docs/public/images/toolkits/googlecontacts/enable-people-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecontacts/enable-people-api.webp differ
docs/public/images/toolkits/googlecontacts/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecontacts/google-consent-screen.webp differ
docs/public/images/toolkits/googlecontacts/people-api-enabled.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlecontacts/people-api-enabled.webp differ
docs/public/images/toolkits/googledocs/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/composio-auth-config-form.webp differ
docs/public/images/toolkits/googledocs/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/composio-config-name.webp differ
docs/public/images/toolkits/googledocs/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/composio-connected-account-active.webp differ
docs/public/images/toolkits/googledocs/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/composio-select-toolkit.webp differ
docs/public/images/toolkits/googledocs/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/data-access-scopes.webp differ
docs/public/images/toolkits/googledocs/enable-docs-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/enable-docs-api.webp differ
docs/public/images/toolkits/googledocs/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledocs/google-consent-screen.webp differ
docs/public/images/toolkits/googledrive/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledrive/composio-auth-config-form.webp differ
docs/public/images/toolkits/googledrive/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledrive/composio-config-name.webp differ
docs/public/images/toolkits/googledrive/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledrive/composio-connected-account-active.webp differ
docs/public/images/toolkits/googledrive/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledrive/composio-select-toolkit.webp differ
docs/public/images/toolkits/googledrive/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googledrive/google-consent-screen.webp differ
docs/public/images/toolkits/googleforms/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleforms/data-access-scopes.webp differ
docs/public/images/toolkits/googleforms/enable-forms-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleforms/enable-forms-api.webp differ
docs/public/images/toolkits/googleforms/forms-api-enabled.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleforms/forms-api-enabled.webp differ
docs/public/images/toolkits/googleforms/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleforms/google-consent-screen.webp differ
docs/public/images/toolkits/googlemeet/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlemeet/data-access-scopes.webp differ
docs/public/images/toolkits/googlemeet/enable-meet-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlemeet/enable-meet-api.webp differ
docs/public/images/toolkits/googlemeet/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlemeet/google-consent-screen.webp differ
docs/public/images/toolkits/googlemeet/meet-api-enabled.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlemeet/meet-api-enabled.webp differ
docs/public/images/toolkits/googlephotos/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlephotos/composio-connected-account-active.webp differ
docs/public/images/toolkits/googlephotos/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlephotos/google-consent-screen.webp differ
docs/public/images/toolkits/googlesheets/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/composio-auth-config-form.webp differ
docs/public/images/toolkits/googlesheets/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/composio-config-name.webp differ
docs/public/images/toolkits/googlesheets/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/composio-connected-account-active.webp differ
docs/public/images/toolkits/googlesheets/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/composio-select-toolkit.webp differ
docs/public/images/toolkits/googlesheets/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/data-access-scopes.webp differ
docs/public/images/toolkits/googlesheets/enable-sheets-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/enable-sheets-api.webp differ
docs/public/images/toolkits/googlesheets/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesheets/google-consent-screen.webp differ
docs/public/images/toolkits/googleslides/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleslides/data-access-scopes.webp differ
docs/public/images/toolkits/googleslides/enable-slides-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleslides/enable-slides-api.webp differ
docs/public/images/toolkits/googleslides/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleslides/google-consent-screen.webp differ
docs/public/images/toolkits/googleslides/slides-api-enabled.webp
Binary files /dev/null and b/docs/public/images/toolkits/googleslides/slides-api-enabled.webp differ
docs/public/images/toolkits/googlesuper/composio-auth-config-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesuper/composio-auth-config-form.webp differ
docs/public/images/toolkits/googlesuper/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesuper/composio-config-name.webp differ
docs/public/images/toolkits/googlesuper/composio-connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesuper/composio-connected-account-active.webp differ
docs/public/images/toolkits/googlesuper/composio-select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesuper/composio-select-toolkit.webp differ
docs/public/images/toolkits/googlesuper/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googlesuper/google-consent-screen.webp differ
docs/public/images/toolkits/googletasks/data-access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/googletasks/data-access-scopes.webp differ
docs/public/images/toolkits/googletasks/enable-tasks-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/googletasks/enable-tasks-api.webp differ
docs/public/images/toolkits/googletasks/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/googletasks/google-consent-screen.webp differ
docs/public/images/toolkits/googletasks/tasks-api-enabled.webp
Binary files /dev/null and b/docs/public/images/toolkits/googletasks/tasks-api-enabled.webp differ
docs/public/images/toolkits/gorgias/add-to-project.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/add-to-project.webp differ
docs/public/images/toolkits/gorgias/app-store-search.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/app-store-search.webp differ
docs/public/images/toolkits/gorgias/composio-app-authorize.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/composio-app-authorize.webp differ
docs/public/images/toolkits/gorgias/config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/config-name.webp differ
docs/public/images/toolkits/gorgias/create-app-redirect-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/create-app-redirect-url.webp differ
docs/public/images/toolkits/gorgias/enter-subdomain.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/enter-subdomain.webp differ
docs/public/images/toolkits/gorgias/managed-oauth.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/managed-oauth.webp differ
docs/public/images/toolkits/gorgias/oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/oauth-credentials.webp differ
docs/public/images/toolkits/gorgias/partner-portal-my-apps.webp
Binary files /dev/null and b/docs/public/images/toolkits/gorgias/partner-portal-my-apps.webp differ
docs/public/images/toolkits/highlevel_location/add-client-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/add-client-key.webp differ
docs/public/images/toolkits/highlevel_location/client-keys.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/client-keys.webp differ
docs/public/images/toolkits/highlevel_location/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/composio-auth-configs.webp differ
docs/public/images/toolkits/highlevel_location/composio-search-highlevel.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/composio-search-highlevel.webp differ
docs/public/images/toolkits/highlevel_location/config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/config-name.webp differ
docs/public/images/toolkits/highlevel_location/connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/connect-account.webp differ
docs/public/images/toolkits/highlevel_location/install-confirmation.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/install-confirmation.webp differ
docs/public/images/toolkits/highlevel_location/my-apps-create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/my-apps-create-app.webp differ
docs/public/images/toolkits/highlevel_location/oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/oauth-credentials.webp differ
docs/public/images/toolkits/highlevel_location/redirect-uri-and-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/redirect-uri-and-scopes.webp differ
docs/public/images/toolkits/highlevel_location/redirect-url-added.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/redirect-url-added.webp differ
docs/public/images/toolkits/highlevel_location/select-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/select-scopes.webp differ
docs/public/images/toolkits/highlevel_location/select-sub-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/select-sub-account.webp differ
docs/public/images/toolkits/highlevel_location/sign-in.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/sign-in.webp differ
docs/public/images/toolkits/highlevel_location/start-from-scratch.webp
Binary files /dev/null and b/docs/public/images/toolkits/highlevel_location/start-from-scratch.webp differ
docs/public/images/toolkits/hubspot/app-info.webp
Binary files /dev/null and b/docs/public/images/toolkits/hubspot/app-info.webp differ
docs/public/images/toolkits/hubspot/composio-client-fields.webp
Binary files /dev/null and b/docs/public/images/toolkits/hubspot/composio-client-fields.webp differ
docs/public/images/toolkits/hubspot/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/hubspot/create-app.webp differ
docs/public/images/toolkits/hubspot/use-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/hubspot/use-own-credentials.webp differ
docs/public/images/toolkits/instantly/api-key-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/instantly/api-key-auth-config.webp differ
docs/public/images/toolkits/instantly/api-keys-page.webp
Binary files /dev/null and b/docs/public/images/toolkits/instantly/api-keys-page.webp differ
docs/public/images/toolkits/instantly/composio-search-instantly.webp
Binary files /dev/null and b/docs/public/images/toolkits/instantly/composio-search-instantly.webp differ
docs/public/images/toolkits/instantly/create-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/instantly/create-api-key.webp differ
docs/public/images/toolkits/jira/api-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/jira/api-scopes.webp differ
docs/public/images/toolkits/jira/create-oauth-integration.webp
Binary files /dev/null and b/docs/public/images/toolkits/jira/create-oauth-integration.webp differ
docs/public/images/toolkits/jira/missing-scopes-error.webp
Binary files /dev/null and b/docs/public/images/toolkits/jira/missing-scopes-error.webp differ
docs/public/images/toolkits/jira/permissions-apis.webp
Binary files /dev/null and b/docs/public/images/toolkits/jira/permissions-apis.webp differ
docs/public/images/toolkits/linear/api-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/linear/api-settings.webp differ
docs/public/images/toolkits/linkedin/app-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/linkedin/app-details.webp differ
docs/public/images/toolkits/linkedin/auth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/linkedin/auth-credentials.webp differ
docs/public/images/toolkits/linkedin/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/linkedin/create-app.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-auth-configs.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_advertising/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_advertising/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_advertising/developer-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/developer-settings.webp differ
docs/public/images/toolkits/microsoft_advertising/developer-token-field.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/developer-token-field.webp differ
docs/public/images/toolkits/microsoft_advertising/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/microsoft-account-picker.webp differ
docs/public/images/toolkits/microsoft_advertising/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_advertising/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_bookings/bookings-read-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/bookings-read-all-permission.webp differ
docs/public/images/toolkits/microsoft_bookings/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_bookings/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_bookings/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_bookings/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_bookings/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_bookings/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/configured-permissions.webp differ
docs/public/images/toolkits/microsoft_bookings/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_bookings/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/microsoft-account-picker.webp differ
docs/public/images/toolkits/microsoft_bookings/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_bookings/microsoft-tenant-field.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_bookings/microsoft-tenant-field.webp differ
docs/public/images/toolkits/microsoft_entra_id/composio-cloud-and-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/composio-cloud-and-scopes.webp differ
docs/public/images/toolkits/microsoft_entra_id/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_entra_id/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_entra_id/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_entra_id/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_entra_id/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_entra_id/connection-success.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/connection-success.webp differ
docs/public/images/toolkits/microsoft_entra_id/user-read-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_entra_id/user-read-details.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-auth-configs.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_power_bi/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_power_bi/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/configured-permissions.webp differ
docs/public/images/toolkits/microsoft_power_bi/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_power_bi/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_power_bi/power-bi-service-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/power-bi-service-api.webp differ
docs/public/images/toolkits/microsoft_power_bi/registered-redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/registered-redirect-uri.webp differ
docs/public/images/toolkits/microsoft_power_bi/workspace-read-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_power_bi/workspace-read-all-permission.webp differ
docs/public/images/toolkits/microsoft_powerpoint/add-client-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/add-client-secret.webp differ
docs/public/images/toolkits/microsoft_powerpoint/api-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/api-permissions.webp differ
docs/public/images/toolkits/microsoft_powerpoint/app-overview.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/app-overview.webp differ
docs/public/images/toolkits/microsoft_powerpoint/certificates-and-secrets.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/certificates-and-secrets.webp differ
docs/public/images/toolkits/microsoft_powerpoint/client-secret-value.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/client-secret-value.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-auth-configs.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-credentials-entered.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-credentials-entered.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_powerpoint/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_powerpoint/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/configured-permissions.webp differ
docs/public/images/toolkits/microsoft_powerpoint/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_powerpoint/delegated-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/delegated-permissions.webp differ
docs/public/images/toolkits/microsoft_powerpoint/files-readwrite-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/files-readwrite-all-permission.webp differ
docs/public/images/toolkits/microsoft_powerpoint/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_powerpoint/microsoft-graph-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/microsoft-graph-api.webp differ
docs/public/images/toolkits/microsoft_powerpoint/offline-access-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/offline-access-permission.webp differ
docs/public/images/toolkits/microsoft_powerpoint/register-application.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/register-application.webp differ
docs/public/images/toolkits/microsoft_powerpoint/registered-redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_powerpoint/registered-redirect-uri.webp differ
docs/public/images/toolkits/microsoft_teams/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_teams/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_teams/composio-credentials-cloud.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-credentials-cloud.webp differ
docs/public/images/toolkits/microsoft_teams/composio-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-own-credentials.webp differ
docs/public/images/toolkits/microsoft_teams/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_teams/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_teams/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_teams/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/microsoft-account-picker.webp differ
docs/public/images/toolkits/microsoft_teams/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_teams/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_todo/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_todo/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_todo/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_todo/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_todo/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_todo/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/configured-permissions.webp differ
docs/public/images/toolkits/microsoft_todo/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_todo/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_todo/tasks-readwrite-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_todo/tasks-readwrite-permission.webp differ
docs/public/images/toolkits/microsoft_word/add-client-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/add-client-secret.webp differ
docs/public/images/toolkits/microsoft_word/api-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/api-permissions.webp differ
docs/public/images/toolkits/microsoft_word/app-overview.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/app-overview.webp differ
docs/public/images/toolkits/microsoft_word/certificates-and-secrets.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/certificates-and-secrets.webp differ
docs/public/images/toolkits/microsoft_word/client-secret-value.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/client-secret-value.webp differ
docs/public/images/toolkits/microsoft_word/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-auth-configs.webp differ
docs/public/images/toolkits/microsoft_word/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-config-name.webp differ
docs/public/images/toolkits/microsoft_word/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-connect-account.webp differ
docs/public/images/toolkits/microsoft_word/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-oauth-credentials.webp differ
docs/public/images/toolkits/microsoft_word/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-scopes.webp differ
docs/public/images/toolkits/microsoft_word/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/composio-toolkit-picker.webp differ
docs/public/images/toolkits/microsoft_word/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/configured-permissions.webp differ
docs/public/images/toolkits/microsoft_word/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/connected-account-active.webp differ
docs/public/images/toolkits/microsoft_word/delegated-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/delegated-permissions.webp differ
docs/public/images/toolkits/microsoft_word/files-readwrite-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/files-readwrite-all-permission.webp differ
docs/public/images/toolkits/microsoft_word/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/microsoft-account-picker.webp differ
docs/public/images/toolkits/microsoft_word/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/microsoft-consent.webp differ
docs/public/images/toolkits/microsoft_word/microsoft-graph-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/microsoft-graph-api.webp differ
docs/public/images/toolkits/microsoft_word/offline-access-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/offline-access-permission.webp differ
docs/public/images/toolkits/microsoft_word/register-application.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/register-application.webp differ
docs/public/images/toolkits/microsoft_word/registered-redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/registered-redirect-uri.webp differ
docs/public/images/toolkits/microsoft_word/sites-read-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/microsoft_word/sites-read-all-permission.webp differ
docs/public/images/toolkits/monday/app-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/monday/app-credentials.webp differ
docs/public/images/toolkits/monday/general-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/monday/general-settings.webp differ
docs/public/images/toolkits/monday/oauth-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/monday/oauth-scopes.webp differ
docs/public/images/toolkits/notebook_lm/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/notebook_lm/google-consent-screen.webp differ
docs/public/images/toolkits/notion/api-key-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/api-key-auth-config.webp differ
docs/public/images/toolkits/notion/capabilities.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/capabilities.webp differ
docs/public/images/toolkits/notion/composio-search-notion.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/composio-search-notion.webp differ
docs/public/images/toolkits/notion/connect-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/connect-api-key.webp differ
docs/public/images/toolkits/notion/oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/oauth-credentials.webp differ
docs/public/images/toolkits/notion/oauth2-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/notion/oauth2-auth-config.webp differ
docs/public/images/toolkits/one_drive/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-config-name.webp differ
docs/public/images/toolkits/one_drive/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-connect-account.webp differ
docs/public/images/toolkits/one_drive/composio-credentials-cloud.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-credentials-cloud.webp differ
docs/public/images/toolkits/one_drive/composio-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-own-credentials.webp differ
docs/public/images/toolkits/one_drive/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-scopes.webp differ
docs/public/images/toolkits/one_drive/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/composio-toolkit-picker.webp differ
docs/public/images/toolkits/one_drive/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/connected-account-active.webp differ
docs/public/images/toolkits/one_drive/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/one_drive/microsoft-consent.webp differ
docs/public/images/toolkits/onenote/add-client-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/add-client-secret.webp differ
docs/public/images/toolkits/onenote/api-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/api-permissions.webp differ
docs/public/images/toolkits/onenote/app-overview.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/app-overview.webp differ
docs/public/images/toolkits/onenote/app-registrations.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/app-registrations.webp differ
docs/public/images/toolkits/onenote/certificates-and-secrets.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/certificates-and-secrets.webp differ
docs/public/images/toolkits/onenote/client-secrets-list.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/client-secrets-list.webp differ
docs/public/images/toolkits/onenote/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/composio-auth-configs.webp differ
docs/public/images/toolkits/onenote/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/composio-config-name.webp differ
docs/public/images/toolkits/onenote/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/composio-connect-account.webp differ
docs/public/images/toolkits/onenote/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/composio-oauth-credentials.webp differ
docs/public/images/toolkits/onenote/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/composio-toolkit-picker.webp differ
docs/public/images/toolkits/onenote/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/configured-permissions.webp differ
docs/public/images/toolkits/onenote/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/connected-account-active.webp differ
docs/public/images/toolkits/onenote/delegated-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/delegated-permissions.webp differ
docs/public/images/toolkits/onenote/microsoft-account-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/microsoft-account-picker.webp differ
docs/public/images/toolkits/onenote/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/microsoft-consent.webp differ
docs/public/images/toolkits/onenote/microsoft-graph-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/microsoft-graph-api.webp differ
docs/public/images/toolkits/onenote/notes-readwrite-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/notes-readwrite-permission.webp differ
docs/public/images/toolkits/onenote/offline-access-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/onenote/offline-access-permission.webp differ
docs/public/images/toolkits/outlook/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-config-name.webp differ
docs/public/images/toolkits/outlook/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-connect-account.webp differ
docs/public/images/toolkits/outlook/composio-credentials-cloud.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-credentials-cloud.webp differ
docs/public/images/toolkits/outlook/composio-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-own-credentials.webp differ
docs/public/images/toolkits/outlook/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-scopes.webp differ
docs/public/images/toolkits/outlook/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/composio-toolkit-picker.webp differ
docs/public/images/toolkits/outlook/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/configured-permissions.webp differ
docs/public/images/toolkits/outlook/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/connected-account-active.webp differ
docs/public/images/toolkits/outlook/mail-read-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/mail-read-permission.webp differ
docs/public/images/toolkits/outlook/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/outlook/microsoft-consent.webp differ
docs/public/images/toolkits/pagerduty/classic-user-oauth.webp
Binary files /dev/null and b/docs/public/images/toolkits/pagerduty/classic-user-oauth.webp differ
docs/public/images/toolkits/pagerduty/info-functionality.webp
Binary files /dev/null and b/docs/public/images/toolkits/pagerduty/info-functionality.webp differ
docs/public/images/toolkits/pagerduty/integrations-menu.webp
Binary files /dev/null and b/docs/public/images/toolkits/pagerduty/integrations-menu.webp differ
docs/public/images/toolkits/pagerduty/new-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/pagerduty/new-app.webp differ
docs/public/images/toolkits/pagerduty/redirect-url-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/pagerduty/redirect-url-scope.webp differ
docs/public/images/toolkits/pipedrive/access-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/pipedrive/access-scopes.webp differ
docs/public/images/toolkits/pipedrive/create-an-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/pipedrive/create-an-app.webp differ
docs/public/images/toolkits/pipedrive/oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/pipedrive/oauth-credentials.webp differ
docs/public/images/toolkits/pipedrive/select-app-type.webp
Binary files /dev/null and b/docs/public/images/toolkits/pipedrive/select-app-type.webp differ
docs/public/images/toolkits/plaid/api-key-method.webp
Binary files /dev/null and b/docs/public/images/toolkits/plaid/api-key-method.webp differ
docs/public/images/toolkits/plaid/connect-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/plaid/connect-form.webp differ
docs/public/images/toolkits/plaid/create-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/plaid/create-auth-config.webp differ
docs/public/images/toolkits/plaid/keys-page.webp
Binary files /dev/null and b/docs/public/images/toolkits/plaid/keys-page.webp differ
docs/public/images/toolkits/posthog/create-personal-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/posthog/create-personal-api-key.webp differ
docs/public/images/toolkits/ramp/add-redirect-uri.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/add-redirect-uri.webp differ
docs/public/images/toolkits/ramp/company-developer-menu.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/company-developer-menu.webp differ
docs/public/images/toolkits/ramp/create-app-dialog.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/create-app-dialog.webp differ
docs/public/images/toolkits/ramp/developer-page.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/developer-page.webp differ
docs/public/images/toolkits/ramp/grant-types.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/grant-types.webp differ
docs/public/images/toolkits/ramp/my-apps-list.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/my-apps-list.webp differ
docs/public/images/toolkits/ramp/redirect-uris.webp
Binary files /dev/null and b/docs/public/images/toolkits/ramp/redirect-uris.webp differ
docs/public/images/toolkits/rocketlane/api-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/rocketlane/api-settings.webp differ
docs/public/images/toolkits/rocketlane/create-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/rocketlane/create-api-key.webp differ
docs/public/images/toolkits/salesforce/app-manager-view.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/app-manager-view.webp differ
docs/public/images/toolkits/salesforce/composio-auth-configs-nav.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/composio-auth-configs-nav.webp differ
docs/public/images/toolkits/salesforce/consumer-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/consumer-details.webp differ
docs/public/images/toolkits/salesforce/create-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/create-auth-config.webp differ
docs/public/images/toolkits/salesforce/edit-settings-menu.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/edit-settings-menu.webp differ
docs/public/images/toolkits/salesforce/external-client-app-manager.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/external-client-app-manager.webp differ
docs/public/images/toolkits/salesforce/external-client-app-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/external-client-app-settings.webp differ
docs/public/images/toolkits/salesforce/new-connected-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/new-connected-app.webp differ
docs/public/images/toolkits/salesforce/new-external-client-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/new-external-client-app.webp differ
docs/public/images/toolkits/salesforce/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/own-credentials.webp differ
docs/public/images/toolkits/salesforce/refresh-token-ip-allowlist.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/refresh-token-ip-allowlist.webp differ
docs/public/images/toolkits/salesforce/security-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/salesforce/security-settings.webp differ
docs/public/images/toolkits/servicem8/activation-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/activation-url.webp differ
docs/public/images/toolkits/servicem8/active-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/active-account.webp differ
docs/public/images/toolkits/servicem8/auth-config-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/auth-config-settings.webp differ
docs/public/images/toolkits/servicem8/auth-configs-create.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/auth-configs-create.webp differ
docs/public/images/toolkits/servicem8/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/consent-screen.webp differ
docs/public/images/toolkits/servicem8/new-store-item.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/new-store-item.webp differ
docs/public/images/toolkits/servicem8/oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/oauth-credentials.webp differ
docs/public/images/toolkits/servicem8/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/own-credentials.webp differ
docs/public/images/toolkits/servicem8/search-servicem8.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/search-servicem8.webp differ
docs/public/images/toolkits/servicem8/store-items.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/store-items.webp differ
docs/public/images/toolkits/servicem8/unverified-warning.webp
Binary files /dev/null and b/docs/public/images/toolkits/servicem8/unverified-warning.webp differ
docs/public/images/toolkits/share_point/add-a-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/add-a-permission.webp differ
docs/public/images/toolkits/share_point/allsites-read-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/allsites-read-details.webp differ
docs/public/images/toolkits/share_point/allsites-read-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/allsites-read-permission.webp differ
docs/public/images/toolkits/share_point/composio-auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-auth-configs.webp differ
docs/public/images/toolkits/share_point/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-config-name.webp differ
docs/public/images/toolkits/share_point/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-connect-account.webp differ
docs/public/images/toolkits/share_point/composio-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-own-credentials.webp differ
docs/public/images/toolkits/share_point/composio-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-scopes.webp differ
docs/public/images/toolkits/share_point/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/composio-toolkit-picker.webp differ
docs/public/images/toolkits/share_point/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/connected-account-active.webp differ
docs/public/images/toolkits/share_point/connection-success.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/connection-success.webp differ
docs/public/images/toolkits/share_point/sharepoint-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/sharepoint-api.webp differ
docs/public/images/toolkits/share_point/tenant-and-subsite-fields.webp
Binary files /dev/null and b/docs/public/images/toolkits/share_point/tenant-and-subsite-fields.webp differ
docs/public/images/toolkits/shared/10qkqAzadRISRYZhaXXdhXA.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/10qkqAzadRISRYZhaXXdhXA.webp differ
docs/public/images/toolkits/shared/19hfD30iOecyW2OUu49tHoR7H4.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/19hfD30iOecyW2OUu49tHoR7H4.webp differ
docs/public/images/toolkits/shared/1dBnBBEYr17c671yWVLvqnS4k.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/1dBnBBEYr17c671yWVLvqnS4k.webp differ
docs/public/images/toolkits/shared/1iIDmPCxFpXJP7zt73rUtnOLkxc.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/1iIDmPCxFpXJP7zt73rUtnOLkxc.webp differ
docs/public/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/1qh7A0aEGRUU1K19aU37FrcxTY.webp differ
docs/public/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/5uRKMRjmfWRjXAIPnkdZ8jDIX4.webp differ
docs/public/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/8KdDacyTQMo8T6CGQiwoDnYz7WU.webp differ
docs/public/images/toolkits/shared/9cVvSnHVsreVO2KBW80wvMy50Bo.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/9cVvSnHVsreVO2KBW80wvMy50Bo.webp differ
docs/public/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/9j8wjr2HocIhIsgedntpgb4m8Y.webp differ
docs/public/images/toolkits/shared/Ad4GMrYjKLi22dWKFlwp1NGTs.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/Ad4GMrYjKLi22dWKFlwp1NGTs.webp differ
docs/public/images/toolkits/shared/BOmH98f2n8W8w0fbYP6WUJ1mFII.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/BOmH98f2n8W8w0fbYP6WUJ1mFII.webp differ
docs/public/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/BetTxXqa2c1dgg4QeV4g9RV008.webp differ
docs/public/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/DUtMN0UWIU2kEqnvS5DvD7qhWU.webp differ
docs/public/images/toolkits/shared/Ea7qmGPRdmtbyoxbuXiKG7bct1Q.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/Ea7qmGPRdmtbyoxbuXiKG7bct1Q.webp differ
docs/public/images/toolkits/shared/J4V5TpgIBuXDk4prikxhduGZQxM.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/J4V5TpgIBuXDk4prikxhduGZQxM.webp differ
docs/public/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/Jttbz3Cm6xJFWNlukXLGTxWjf6c.webp differ
docs/public/images/toolkits/shared/KZBDHtekgRetnjjIfoArkzSiZY.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/KZBDHtekgRetnjjIfoArkzSiZY.webp differ
docs/public/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/M0mS4XrLbK5mU52ry578MBa7M.webp differ
docs/public/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/Mavl5IyzWvxI5tP64ScXgpeyI94.webp differ
docs/public/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/NPebZadjeI4xIhtObtt8Fou0hs.webp differ
docs/public/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/O3hvEI521MXY1DbagDCQ8U3W2vo.webp differ
docs/public/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/P6j2HSVMJwSq5F11Whsyl5lgvM.webp differ
docs/public/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/Q8INvnJoiCMyajqrrAtq6ovCE5U.webp differ
docs/public/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/S7mFFv6C5mCP4y0ScTzRzQd8Nc.webp differ
docs/public/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/SHZSEmH6MtzuytgGtV6w538oSZ8.webp differ
docs/public/images/toolkits/shared/SKmiRvkpLj1fiXUXAPnkjJ2Ug.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/SKmiRvkpLj1fiXUXAPnkjJ2Ug.webp differ
docs/public/images/toolkits/shared/SzVC6OY8pTVVwlrOjHLuhuv0u3Y.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/SzVC6OY8pTVVwlrOjHLuhuv0u3Y.webp differ
docs/public/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/TmVTLOgVKQDqamjQVxKDBXJtPQ.webp differ
docs/public/images/toolkits/shared/VNt0egQy2o9O5i6LMd4JFpNcmAU.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/VNt0egQy2o9O5i6LMd4JFpNcmAU.webp differ
docs/public/images/toolkits/shared/WyfUBqcv3KROYF9jYs3rIFcs.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/WyfUBqcv3KROYF9jYs3rIFcs.webp differ
docs/public/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/XrRJcE8kllnTRDHzOTTTl8s9oxc.webp differ
docs/public/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/YdKWAswsL2nVXnSbA4zgBUDmwA.webp differ
docs/public/images/toolkits/shared/ch2L6hWRPSOigltUpRF7r9hyA.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/ch2L6hWRPSOigltUpRF7r9hyA.webp differ
docs/public/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/eZiGGdUoPbOHKz4sCPqGdS04k.webp differ
docs/public/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/hiQJlSSKAljLV6UM2Wu8e5sUCzU.webp differ
docs/public/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/hjaj4jg5CtBRolXXYddY8NDXCes.webp differ
docs/public/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/jDTS80dlfwHF6u1WAQhBdnjTrI.webp differ
docs/public/images/toolkits/shared/jkkvkcA7QbpyHuUXzLJNP0lvxLo.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/jkkvkcA7QbpyHuUXzLJNP0lvxLo.webp differ
docs/public/images/toolkits/shared/kvxWqV89dZHkBHkJJGy5XQdhGko.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/kvxWqV89dZHkBHkJJGy5XQdhGko.webp differ
docs/public/images/toolkits/shared/m3IgMHHfNa8gv1av1yK5u8y47Pg.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/m3IgMHHfNa8gv1av1yK5u8y47Pg.webp differ
docs/public/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/mOoTcq0Tv58rR84sOt4c4MqcWgM.webp differ
docs/public/images/toolkits/shared/nDFU25pH9BfPuJzceax2NoFVzIw.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/nDFU25pH9BfPuJzceax2NoFVzIw.webp differ
docs/public/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/sA0bvCBPtMCWw8lqecCrx76Dyc.webp differ
docs/public/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/wIAvY0hheAM7HQEF4kG2KTYATY.webp differ
docs/public/images/toolkits/shared/wl7JybvARU75U43YShwhxk1Pgxk.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/wl7JybvARU75U43YShwhxk1Pgxk.webp differ
docs/public/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp
Binary files /dev/null and b/docs/public/images/toolkits/shared/x4VkWS3iceKKFGyjlFN1THrtTRQ.webp differ
docs/public/images/toolkits/sharepoint_graph/composio-cloud-and-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/composio-cloud-and-scopes.webp differ
docs/public/images/toolkits/sharepoint_graph/composio-config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/composio-config-name.webp differ
docs/public/images/toolkits/sharepoint_graph/composio-connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/composio-connect-account.webp differ
docs/public/images/toolkits/sharepoint_graph/composio-oauth-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/composio-oauth-credentials.webp differ
docs/public/images/toolkits/sharepoint_graph/composio-toolkit-picker.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/composio-toolkit-picker.webp differ
docs/public/images/toolkits/sharepoint_graph/configured-permissions.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/configured-permissions.webp differ
docs/public/images/toolkits/sharepoint_graph/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/connected-account-active.webp differ
docs/public/images/toolkits/sharepoint_graph/microsoft-consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/microsoft-consent.webp differ
docs/public/images/toolkits/sharepoint_graph/sites-readwrite-all-permission.webp
Binary files /dev/null and b/docs/public/images/toolkits/sharepoint_graph/sites-readwrite-all-permission.webp differ
docs/public/images/toolkits/shopify/app-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/app-url.webp differ
docs/public/images/toolkits/shopify/client-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/client-credentials.webp differ
docs/public/images/toolkits/shopify/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/create-app.webp differ
docs/public/images/toolkits/shopify/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/own-credentials.webp differ
docs/public/images/toolkits/shopify/release-version.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/release-version.webp differ
docs/public/images/toolkits/shopify/scopes-redirect-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/scopes-redirect-url.webp differ
docs/public/images/toolkits/shopify/select-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/shopify/select-scopes.webp differ
docs/public/images/toolkits/slack/active-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/active-account.webp differ
docs/public/images/toolkits/slack/app-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/app-credentials.webp differ
docs/public/images/toolkits/slack/auth-configs-create.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/auth-configs-create.webp differ
docs/public/images/toolkits/slack/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/consent-screen.webp differ
docs/public/images/toolkits/slack/create-an-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/create-an-app.webp differ
docs/public/images/toolkits/slack/from-scratch.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/from-scratch.webp differ
docs/public/images/toolkits/slack/name-and-workspace.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/name-and-workspace.webp differ
docs/public/images/toolkits/slack/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/own-credentials.webp differ
docs/public/images/toolkits/slack/redirect-urls.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/redirect-urls.webp differ
docs/public/images/toolkits/slack/search-slack.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/search-slack.webp differ
docs/public/images/toolkits/slack/verification-token-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/slack/verification-token-scopes.webp differ
docs/public/images/toolkits/snowflake/client-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/client-credentials.webp differ
docs/public/images/toolkits/snowflake/create-auth-config.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/create-auth-config.webp differ
docs/public/images/toolkits/snowflake/create-security-integration.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/create-security-integration.webp differ
docs/public/images/toolkits/snowflake/oauth2-auth-method.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/oauth2-auth-method.webp differ
docs/public/images/toolkits/snowflake/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/select-toolkit.webp differ
docs/public/images/toolkits/snowflake/sign-in.webp
Binary files /dev/null and b/docs/public/images/toolkits/snowflake/sign-in.webp differ
docs/public/images/toolkits/stripe/api-key-auth-method.webp
Binary files /dev/null and b/docs/public/images/toolkits/stripe/api-key-auth-method.webp differ
docs/public/images/toolkits/stripe/api-keys.webp
Binary files /dev/null and b/docs/public/images/toolkits/stripe/api-keys.webp differ
docs/public/images/toolkits/stripe/oauth2-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/stripe/oauth2-own-credentials.webp differ
docs/public/images/toolkits/stripe/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/stripe/select-toolkit.webp differ
docs/public/images/toolkits/telegram/api-key-auth-method.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/api-key-auth-method.webp differ
docs/public/images/toolkits/telegram/bot-token.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/bot-token.webp differ
docs/public/images/toolkits/telegram/botfather-search.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/botfather-search.webp differ
docs/public/images/toolkits/telegram/connect-bot-token.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/connect-bot-token.webp differ
docs/public/images/toolkits/telegram/newbot.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/newbot.webp differ
docs/public/images/toolkits/telegram/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/telegram/select-toolkit.webp differ
docs/public/images/toolkits/ticktick/oauth2-auth-method.webp
Binary files /dev/null and b/docs/public/images/toolkits/ticktick/oauth2-auth-method.webp differ
docs/public/images/toolkits/ticktick/own-credentials-toggle.webp
Binary files /dev/null and b/docs/public/images/toolkits/ticktick/own-credentials-toggle.webp differ
docs/public/images/toolkits/ticktick/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/ticktick/select-toolkit.webp differ
docs/public/images/toolkits/trello/api-key-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/trello/api-key-secret.webp differ
docs/public/images/toolkits/trello/generate-api-key.webp
Binary files /dev/null and b/docs/public/images/toolkits/trello/generate-api-key.webp differ
docs/public/images/toolkits/trello/new-app-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/trello/new-app-form.webp differ
docs/public/images/toolkits/trello/power-ups-admin.webp
Binary files /dev/null and b/docs/public/images/toolkits/trello/power-ups-admin.webp differ
docs/public/images/toolkits/twitter/apps-list.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/apps-list.webp differ
docs/public/images/toolkits/twitter/authorize-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/authorize-app.webp differ
docs/public/images/toolkits/twitter/bearer-token-and-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/bearer-token-and-scopes.webp differ
docs/public/images/toolkits/twitter/callback-url.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/callback-url.webp differ
docs/public/images/toolkits/twitter/config-name.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/config-name.webp differ
docs/public/images/toolkits/twitter/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/connected-account-active.webp differ
docs/public/images/toolkits/twitter/create-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/create-app.webp differ
docs/public/images/toolkits/twitter/keys-and-tokens.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/keys-and-tokens.webp differ
docs/public/images/toolkits/twitter/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/select-toolkit.webp differ
docs/public/images/toolkits/twitter/user-auth-settings.webp
Binary files /dev/null and b/docs/public/images/toolkits/twitter/user-auth-settings.webp differ
docs/public/images/toolkits/workday/register-api-client-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/workday/register-api-client-form.webp differ
docs/public/images/toolkits/workday/register-api-client-scopes.webp
Binary files /dev/null and b/docs/public/images/toolkits/workday/register-api-client-scopes.webp differ
docs/public/images/toolkits/workday/registered-client-summary.webp
Binary files /dev/null and b/docs/public/images/toolkits/workday/registered-client-summary.webp differ
docs/public/images/toolkits/xero/auth-configs.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/auth-configs.webp differ
docs/public/images/toolkits/xero/connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/connect-account.webp differ
docs/public/images/toolkits/xero/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/connected-account-active.webp differ
docs/public/images/toolkits/xero/consent.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/consent.webp differ
docs/public/images/toolkits/xero/my-apps.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/my-apps.webp differ
docs/public/images/toolkits/xero/new-app-form.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/new-app-form.webp differ
docs/public/images/toolkits/xero/own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/own-credentials.webp differ
docs/public/images/toolkits/xero/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/xero/select-toolkit.webp differ
docs/public/images/toolkits/youtube/auth-config-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/auth-config-credentials.webp differ
docs/public/images/toolkits/youtube/connected-account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/connected-account-active.webp differ
docs/public/images/toolkits/youtube/data-access-youtube-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/data-access-youtube-scope.webp differ
docs/public/images/toolkits/youtube/enable-youtube-data-api.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/enable-youtube-data-api.webp differ
docs/public/images/toolkits/youtube/google-consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/google-consent-screen.webp differ
docs/public/images/toolkits/youtube/select-youtube-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/youtube/select-youtube-toolkit.webp differ
docs/public/images/toolkits/zendesk/oauth2-own-credentials.webp
Binary files /dev/null and b/docs/public/images/toolkits/zendesk/oauth2-own-credentials.webp differ
docs/public/images/toolkits/zendesk/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/zendesk/select-toolkit.webp differ
docs/public/images/toolkits/zoho/client-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho/client-secret.webp differ
docs/public/images/toolkits/zoho_bigin/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_bigin/account-active.webp differ
docs/public/images/toolkits/zoho_bigin/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_bigin/consent-screen.webp differ
docs/public/images/toolkits/zoho_bigin/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_bigin/data-center.webp differ
docs/public/images/toolkits/zoho_books/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_books/account-active.webp differ
docs/public/images/toolkits/zoho_books/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_books/consent-screen.webp differ
docs/public/images/toolkits/zoho_books/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_books/data-center.webp differ
docs/public/images/toolkits/zoho_desk/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_desk/account-active.webp differ
docs/public/images/toolkits/zoho_desk/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_desk/consent-screen.webp differ
docs/public/images/toolkits/zoho_desk/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_desk/data-center.webp differ
docs/public/images/toolkits/zoho_inventory/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_inventory/account-active.webp differ
docs/public/images/toolkits/zoho_inventory/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_inventory/consent-screen.webp differ
docs/public/images/toolkits/zoho_inventory/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_inventory/data-center.webp differ
docs/public/images/toolkits/zoho_invoice/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_invoice/account-active.webp differ
docs/public/images/toolkits/zoho_invoice/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_invoice/consent-screen.webp differ
docs/public/images/toolkits/zoho_invoice/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_invoice/data-center.webp differ
docs/public/images/toolkits/zoho_mail/account-active.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/account-active.webp differ
docs/public/images/toolkits/zoho_mail/add-client.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/add-client.webp differ
docs/public/images/toolkits/zoho_mail/add-scope.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/add-scope.webp differ
docs/public/images/toolkits/zoho_mail/client-details.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/client-details.webp differ
docs/public/images/toolkits/zoho_mail/client-name-error.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/client-name-error.webp differ
docs/public/images/toolkits/zoho_mail/client-secret.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/client-secret.webp differ
docs/public/images/toolkits/zoho_mail/client-type.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/client-type.webp differ
docs/public/images/toolkits/zoho_mail/connect-account.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/connect-account.webp differ
docs/public/images/toolkits/zoho_mail/consent-screen.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/consent-screen.webp differ
docs/public/images/toolkits/zoho_mail/data-center.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/data-center.webp differ
docs/public/images/toolkits/zoho_mail/select-toolkit.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoho_mail/select-toolkit.webp differ
docs/public/images/toolkits/zoom/choose-general-app.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoom/choose-general-app.webp differ
docs/public/images/toolkits/zoom/development-production-tabs.webp
Binary files /dev/null and b/docs/public/images/toolkits/zoom/development-production-tabs.webp differ
docs/tests/integration/rendering.test.ts
+4 -17
@@ -176,23 +176,10 @@ describe("Page rendering - content markers", () => {
176
177 test("toolkit knowledge pages open only external cards in a new tab", async () => {
178 const summaries = await getKnowledgeToolkitSummaries();
179 - let toolkitWithMixedLinks: (typeof summaries)[number] | undefined;
180 - let toolkitLinks: Awaited<ReturnType<typeof getKnowledgeByToolkit>> = [];
181 -
182 - for (const toolkit of summaries) {
183 - if (toolkit.knowledgeCount <= 1) continue;
184 - const links = await getKnowledgeByToolkit(toolkit.slug);
185 - const hasExternalLink = links.some((link) => /^https?:\/\//.test(link.href));
186 - const hasInternalLink = links.some((link) => !/^https?:\/\//.test(link.href));
187 - if (hasExternalLink && hasInternalLink) {
188 - toolkitWithMixedLinks = toolkit;
189 - toolkitLinks = links;
190 - break;
191 - }
192 - }
193 -
194 - expect(toolkitWithMixedLinks).toBeDefined();
195 - const res = await fetchPage(`/kb/toolkit/${toolkitWithMixedLinks!.slug}`);
179 + const toolkit = summaries.find((candidate) => candidate.knowledgeCount > 1);
180 + expect(toolkit).toBeDefined();
181 + const toolkitLinks = await getKnowledgeByToolkit(toolkit!.slug);
182 + const res = await fetchPage(`/kb/toolkit/${toolkit!.slug}`);
183 const html = await res.text();
184 const collection = html.match(
185 /<ul[^>]*aria-label="Toolkit knowledge sources"[^>]*>[\s\S]*?<\/ul>/,
docs/tests/static/auth-guide-indexing.test.ts
+14 -6
@@ -1,4 +1,5 @@
1 import { describe, expect, test } from 'bun:test';
2 +import { getAllToolkitsSync } from '@/lib/toolkit-data';
3 import {
4 getAuthGuideRegistry,
5 getAuthGuideSearchRecords,
@@ -20,14 +21,21 @@ describe('OAuth guide indexing', () => {
21 const entries = getAuthGuideRegistry();
22
23 expect(entries.length).toBeGreaterThan(0);
24 + const toolkitSlugs = new Set(getAllToolkitsSync().map(toolkit => toolkit.slug));
25 + expect(entries.every(entry => toolkitSlugs.has(entry.toolkitSlug))).toBe(true);
26 expect(new Set(entries.map((entry) => entry.slug)).size).toBe(entries.length);
27 expect(new Set(entries.map((entry) => entry.canonicalUrl)).size).toBe(entries.length);
25 - expect(entries.every((entry) => entry.canonicalUrl === `https://composio.dev/auth/${entry.slug}`))
28 + expect(entries.every((entry) => entry.canonicalUrl === `/toolkits/${entry.toolkitSlug}`))
29 .toBe(true);
30 expect(entries.every((entry) => entry.title.trim() && entry.description.trim()))
31 .toBe(true);
32 });
33
34 + test('resolves the legacy Google Apps alias to a real toolkit', () => {
35 + expect(getAuthGuideRegistry().find(entry => entry.slug === 'googleapps'))
36 + .toMatchObject({ toolkitSlug: 'googlesuper', canonicalUrl: '/toolkits/googlesuper' });
37 + });
38 +
39 test('creates one normalized OAuth search record per guide', () => {
40 const entries = getAuthGuideRegistry();
41 const records = getAuthGuideSearchRecords();
@@ -40,7 +48,7 @@ describe('OAuth guide indexing', () => {
48 expect(records.map(record => record.canonical_url))
49 .toEqual(entries.map(entry => entry.canonicalUrl));
50 expect(records.every((record, index) =>
43 - record.toolkit_slugs[0] === entries[index]?.slug && record.page_rank === 1_700))
51 + record.toolkit_slugs[0] === entries[index]?.toolkitSlug && record.page_rank === 1_700))
52 .toBe(true);
53 });
54
@@ -52,7 +60,7 @@ describe('OAuth guide indexing', () => {
60 };
61
62 await expect(validateAuthGuideUrls(entries, fetchImpl as typeof fetch))
55 - .rejects.toThrow('https://composio.dev/auth/gong');
63 + .rejects.toThrow('https://docs.composio.dev/toolkits/gong');
64 });
65
66 test('builds the full replacement only after every registered URL validates', async () => {
@@ -66,7 +74,7 @@ describe('OAuth guide indexing', () => {
74
75 const records = await buildCompleteSearchReplacement({ fetchImpl: fetchImpl as typeof fetch });
76
69 - expect(visited).toEqual(entries.map(entry => entry.canonicalUrl));
77 + expect(visited).toEqual(entries.map(entry => `https://docs.composio.dev${entry.canonicalUrl}`));
78 expect(records.filter((record) => record.source_type === 'oauth-guide'))
79 .toHaveLength(entries.length);
80 });
@@ -81,7 +89,7 @@ describe('OAuth guide indexing', () => {
89 };
90 const fetchImpl = async (input: string | URL | Request) => {
91 const url = String(input);
84 - return responseAt(url, url === entry?.canonicalUrl ? 503 : 200);
92 + return responseAt(url, url === `https://docs.composio.dev${entry?.canonicalUrl}` ? 503 : 200);
93 };
94
95 await expect(replaceSearchDocuments(client, 'docs_composio', {
@@ -92,7 +100,7 @@ describe('OAuth guide indexing', () => {
100
101 test('rejects a registered guide that redirects to a generic auth page', async () => {
102 const [entry] = getAuthGuideRegistry();
95 - const fetchImpl = async () => responseAt('https://composio.dev/auth');
103 + const fetchImpl = async () => responseAt('https://docs.composio.dev/toolkits');
104
105 await expect(validateAuthGuideUrls([entry], fetchImpl as typeof fetch))
106 .rejects.toThrow(entry.canonicalUrl);
docs/tests/static/dashboard-links.test.ts
+5 -3
@@ -10,14 +10,16 @@
10 * page inside the user's workspace.
11 *
12 * Code fences and inline mentions are exempt from rules 2-3; rule 1 applies
13 - * to all file content. content/reference is generated upstream and excluded.
13 + * to all file content. Scans .mdx and .md (toolkit FAQs) under docs,
14 + * examples, changelog and toolkits. content/reference is generated upstream
15 + * and excluded.
16 * TS/TSX is enforced by the no-restricted-syntax rules in .oxlintrc.json.
17 */
18 import { describe, test, expect } from "bun:test";
19 import { readdir, readFile } from "fs/promises";
20 import { join, relative } from "path";
21
20 -const CONTENT_DIRS = ["docs", "examples", "changelog"].map((dir) =>
22 +const CONTENT_DIRS = ["docs", "examples", "changelog", "toolkits"].map((dir) =>
23 join(import.meta.dir, "../../content", dir),
24 );
25 const CONTENT_ROOT = join(import.meta.dir, "../../content");
@@ -40,7 +42,7 @@ async function findMdxFiles(dir: string): Promise<string[]> {
42 const fullPath = join(dir, entry.name);
43 if (entry.isDirectory()) {
44 results.push(...(await findMdxFiles(fullPath)));
43 - } else if (entry.name.endsWith(".mdx")) {
45 + } else if (/\.mdx?$/.test(entry.name)) {
46 results.push(fullPath);
47 }
48 }
docs/tests/static/knowledge-browse.test.tsx
+11 -1
@@ -57,6 +57,16 @@ describe('knowledge browse pages', () => {
57 expect(PRODUCT_AREAS.map((area) => area.slug)).not.toContain('authentication');
58 });
59
60 + test('migrated auth guides stay on the current docs origin without duplicate toolkit cards', async () => {
61 + const links = await getKnowledgeByToolkit('github');
62 + const toolkitLinks = links.filter(link => link.href.endsWith('/toolkits/github'));
63 + expect(toolkitLinks).toHaveLength(1);
64 + expect(toolkitLinks[0].href).toBe('/toolkits/github');
65 + const html = renderToStaticMarkup(<BrowseResults links={toolkitLinks} variant="topic" />);
66 + expect(html).toContain('href="/toolkits/github"');
67 + expect(html).not.toContain('target="_blank"');
68 + });
69 +
70 test('combines OAuth and verified support answers on toolkit pages', async () => {
71 const toolkitGuides = getPublishedKbGuides().flatMap(guide =>
72 guide.sources.flatMap(source => {
@@ -109,7 +119,7 @@ describe('knowledge browse pages', () => {
119 const links = await getFeaturedKnowledgeLinks();
120 expect(links.length).toBeGreaterThan(0);
121 expect(new Set(links.map(item => item.href)).size).toBe(links.length);
112 - expect(links.every(item => item.href.startsWith('/kb/guide/') || item.href.startsWith('https://')))
122 + expect(links.every(item => item.href.startsWith('/kb/guide/') || item.href.startsWith('/toolkits/')))
123 .toBe(true);
124 });
125
docs/tests/static/knowledge-corpus.test.ts
+4 -1
@@ -137,7 +137,10 @@ describe('unified public knowledge corpus', () => {
137 records.filter(record => record.source_type === 'oauth-guide').map(record => record.canonical_url),
138 );
139 expect(oauthUrls.size).toBeGreaterThan(0);
140 - expect(indexes.some(index => oauthUrls.has(index.url))).toBe(true);
140 + for (const url of oauthUrls) {
141 + expect(url.startsWith('/toolkits/')).toBe(true);
142 + expect(indexes.filter(index => index.url === url)).toHaveLength(1);
143 + }
144 });
145
146 test('discovers local hub and browse routes without duplicating external OAuth pages', async () => {
docs/tests/static/toolkit-faq-render.test.tsx new
+18
@@ -0,0 +1,18 @@
1 +import { expect, test } from 'bun:test';
2 +import { readFileSync } from 'node:fs';
3 +import { renderToStaticMarkup } from 'react-dom/server';
4 +import { FaqSection } from '@/components/toolkits/faq-section';
5 +import { parseToolkitFaq } from '@/lib/toolkit-faq';
6 +
7 +test('closed toolkit FAQs retain setup instructions in server-rendered HTML', () => {
8 + const faq = parseToolkitFaq(readFileSync('content/toolkits/faq/github.md', 'utf8'));
9 + const html = renderToStaticMarkup(<FaqSection faq={faq} />);
10 +
11 + expect(html).toContain('https://backend.composio.dev/api/v1/auth-apps/add');
12 + expect(html).toContain('Register application');
13 + expect(html).toContain('Organization access');
14 + expect(html).toContain('<summary');
15 + // A fragment inside the answer triggers native details ancestor revealing.
16 + expect(html).toMatch(/<details><summary[^>]*>How do I set up custom OAuth credentials for GitHub\?<\/summary><div id="how-do-i-set-up-custom-oauth-credentials-for-github"/);
17 + expect(html).not.toMatch(/<summary[^>]* id=/);
18 +});