@devries-cameron20 / composio-1 / commits / 454b04fd7
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(kb): answer Ask AI from the public KB and retire the support-knowledge sync (#5340)

The docs site now answers from one public knowledge base. The docs Ask AI agent reads the `/kb` guides, its separate hand-written FAQ is gone, and the 6-hourly import from the dead `ComposioHQ/support-knowledge` repo is removed. KB guides now come only from the support portal through `docs-kb-publish.yml` (`kb-guide-approved` dispatch), and the PR that workflow opens is the approval: merge to publish, close to dismiss. ## What moved where **Ask AI (`docs/agent`) reads the KB** - `content/kb` is now a collection in the agent's existing BM25 index, in both `agent/lib/docs.ts` (live) and `scripts/build-agent-index.ts` (the bundle the deployed agent uses). URLs are `/kb/guide/<slug>`, and KB guides rank like docs. - `read_doc` opens KB guides by URL, and the tool descriptions, instructions and concept map now mention them. - I added `content/kb` to the existing index rather than pointing `search_docs` at `/api/knowledge-search`. That keeps the agent's fast local search and adds no network call or embedding key at runtime. - `tests/static/eve-kb-retrieval.test.ts` checks that a KB guide comes back from `search_docs` with its content and opens through `read_doc`. It passes against both the live content tree and the bundled snapshot (`EVE_FORCE_BUNDLE=1`). **`agent/knowledge.md` removed, no new guides** All six entries are already covered by docs pages, so none became a KB guide: | Entry | Covered by | |---|---| | Installing and getting started | `/docs/quickstart` | | Choosing a provider | `/docs/providers` | | userID best practices | `/docs/how-composio-works` (users section) | | Native tools vs MCP | `/docs/sessions-via-mcp` ("Tool-call modifiers don't run") | | Sandbox files and `/mnt/files` | `/docs/sandbox/remote` (states both the `expiresAt` and the no-custom-mounts facts) | | Reusing and updating sessions | `/docs/how-composio-works` | The loader and the `knowledge` collection are gone from the agent and the index builder. **support-knowledge sync retired** - Deleted `scripts/import-support-knowledge.ts`, `scripts/resolve-kb-refresh-source.sh`, `lib/kb/support-knowledge.ts`, the `import:kb` script, and their tests. - Removed `manifest.source`. It pinned a support-knowledge commit and nothing else used it. - Removed `verify:kb --check-source-pin`, along with its source token in `docs-update-data.yml`. - `lib/knowledge/semantic-artifact.ts` no longer requires `repository == support-knowledge` or a matching commit. Freshness still comes from `docsContentHash` plus the content hash of every record, which already covered KB guides. The checked-in `kb/semantic-index.json` still validates unchanged, and its old `source` fields drop out on the next rebuild. - `eval:kb-search` no longer compares the fixture against that commit. That comparison failed on every run, because the fixture and manifest commits had drifted apart. **`docs-update-kb.yml` keeps only the semantic repair** - The 6-hourly run used to do two things: import from support-knowledge, and repair a stale `kb/semantic-index.json`. The repair is still needed for changes that reach `next` without a rebuild: fork PRs, or a portal publication that merges itself before `docs-rebuild-kb-semantic.yml` finishes. - So the workflow is now `Docs - Repair KB Semantic Artifact`, with only that job, still on `docs/auto-update-kb`. The `docs-kb-publish.yml` wait loop still serialises against that branch, and `docs-kb-publish.yml` itself is unchanged. - The `.ast-grep/baseline.json` entries for the two edited workflows are refreshed to match their current text. The same `continue-on-error` steps are allowed as before, minus the removed ones. **The KB PR is the approval (second commit)** - Akram decided approvals should just be PRs. `docs-kb-publish.yml` no longer auto-merges the PR it opens. The PR body now says to review and merge to publish, or close to dismiss. - Neither KB workflow waits for other open KB PRs any more. That wait failed after about 30 minutes, so a PR sitting in review would have blocked every later one. The shared concurrency group still runs the workflows one at a time. - Open PRs no longer conflict with each other: - Each guide's definition moved from `kb/manifest.json` into `kb/guides/<slug>.json`. The manifest keeps only `schemaVersion` and `topics`. - `readKbManifest()` in `lib/kb/repository.ts` assembles the guides, and `publish-kb-guide.ts` writes only the touched guide's file. - `content/kb` is no longer committed. `generate:kb` already builds it on install, dev, build, test and typecheck. - I regenerated `content/kb` from the split files and it is byte-identical to the committed copy it replaces. That's why this commit is +6976/−13938 across 270 files: 125 new guide files, 127 removed generated pages. - The event name stays `kb-guide-approved`, so the portal doesn't need to change. **A guide's PR no longer fails on other guides' findings (third commit)** - Before this, "Regenerate KB pages" piped `verify:kb` under pipefail, so a finding anywhere in the KB failed every publication. On `next` today, the 60 guides whose `reviewAfter` has passed block every KB PR, so none could ever open. - The step now fails only on this guide's errors or support prose, and on KB-wide errors. Other guides' findings stay with the data-sync freshness check, which already reports them. **Zen can propose guides too (fourth commit)** - `docs-kb-publish.yml` now also accepts `source: "zen"` dispatches, carrying `request_id`, `origin_url` and `origin_author`. - Each of those fields is validated before it is used in the branch name (`docs/kb-<request_id>`) or the PR body ("proposed by Zen from <PR> (@author)"). - Portal dispatches, which have no `source` and a numeric `draft_id`, are unchanged. Any other `source` is rejected. **Docs and decisions:** `decisions/public-knowledge-base.md` now describes support-portal publication and a single store. The freshness-verification and toolkit-availability decision records, `CONTRIBUTING.md` and `scripts/README.md` no longer mention the source pin or support-knowledge. ## Checks run locally (`docs/`) - `bun run types:check`: passes. - `bun run generate:kb` and `check:kb`: pass (124 published, 0 held). The output is byte-identical to the previously committed `content/kb`. - `node scripts/check-antislop.mjs`: passes, no new findings. - `bun run lint`: no errors (only existing warnings in `components/version-selector.tsx`). - `bun run eval:kb-search` (local keyword): runs to completion. On `next` it stopped at the commit-pin mismatch. - `bun test tests/static/`: 802 pass, 5 fail. The 5 failures are all in `content-freshness.test.ts`, and they fail identically on an untouched `next` snapshot, because those tests need real git history that a tarball snapshot doesn't have. - `bun run verify:kb`: exits 1 with 60 `review-window-expired` errors (guides whose `reviewAfter` was 2026-11-10) and 3 cliff warnings. That output is identical on untouched `next`, so it's not from this change. ## Local end-to-end test `bun run test:kb-publish` (in `docs/tests/e2e/kb-publish.ts`) runs in a throwaway git worktree and does three things: 1. Replays two `kb-guide-approved` dispatches through the real steps of `docs-kb-publish.yml`. The guide payloads have the shape the support portal's `kb.py` sends, and the steps run with the same bash flags as Actions. 2. Checks that each PR touches only its own guide's files, then merges both PR branches one after the other. 3. Rebuilds the KB and checks that Ask AI's `search_docs` and `read_doc` find both guides in the deployed bundle. All 12 checks pass. Before the third commit, the run failed at "Regenerate KB pages" because of the 60 expired guides. I also ran the docs dev server on the merged result: `/kb/guide/sdk-e2e-webhook-retries` renders, and `/api/knowledge-search` (keyword mode locally) returns it second for "webhook delivery retries idempotent". ## Not run - **Ask AI evals** (`eval:agent`, `eval:agent:flows`): these need `INCEPTION_API_KEY` or an AI Gateway key, which I don't have locally. - **`build:kb-semantic` and `check:kb-semantic` without `--allow-stale`**: these need `OPENAI_API_KEY`. - **`bun run build` and `lint:links`.** ## Related The support-portal KB PR (#394) dispatches straight away and treats this repo's PR as the approval: merged means live, closed unmerged means dismissed. Zen's PR-review KB-impact step is separate work. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: jkomyno <alberto@composio.dev>

akram-composio committed Nov 19, 2026 at 00:09 UTC 454b04fd7f2b3a3b04db933e42782e2885fb6876
299 files changed +7238 -13930
.ast-grep/baseline.json
+8 -20
@@ -8,13 +8,13 @@
8 {
9 "ruleId": "py-empty-except",
10 "file": "python/composio/utils/schema_converter.py",
11 - "source": " except Exception: # noqa: BLE001 - pydantic raises SchemaError subclasses\n pass",
11 + "source": " except Exception:\n pass",
12 "count": 1
13 },
14 {
15 "ruleId": "py-empty-except",
16 "file": "python/composio/utils/schema_converter.py",
17 - "source": " except Exception:\n pass",
17 + "source": " except Exception: # noqa: BLE001 - pydantic raises SchemaError subclasses\n pass",
18 "count": 1
19 },
20 {
@@ -386,13 +386,13 @@
386 {
387 "ruleId": "ts-empty-catch",
388 "file": "ts/packages/core/src/utils/uploadDirAllowlist.node.ts",
389 - "source": " } catch {\n // ignore and fall through\n }",
389 + "source": " } catch {\n // ignore\n }",
390 "count": 1
391 },
392 {
393 "ruleId": "ts-empty-catch",
394 "file": "ts/packages/core/src/utils/uploadDirAllowlist.node.ts",
395 - "source": " } catch {\n // ignore\n }",
395 + "source": " } catch {\n // ignore and fall through\n }",
396 "count": 1
397 },
398 {
@@ -431,12 +431,6 @@
431 "source": " - name: Close tracking issue on recovery\n if: success()\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n GH_REPO: ${{ github.repository }}\n LABEL: docs-data-sync-failure\n run: |\n existing=$(gh issue list --label \"$LABEL\" --state open --limit 1 \\\n --json number --jq '.[0].number // empty')\n if [ -n \"$existing\" ]; then\n gh issue close \"$existing\" \\\n --comment \"The docs data sync recovered in run ${{ github.run_id }}: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}.\"\n fi\n\n # A verifier crash is a tooling failure, not evidence that published guides\n # contradict production. Track it separately and close it after the verifier\n # returns either of its expected outcomes: clean (0) or findings (1).",
432 "count": 1
433 },
434 - {
435 - "ruleId": "yaml-continue-on-error",
436 - "file": ".github/workflows/docs-update-data.yml",
437 - "source": " - name: Generate read-only KB source token\n id: source-token\n continue-on-error: true\n uses: actions/create-github-app-token@64ab729a6294000f5aa4a4bc0b73d1f32bc45510 # v3.3.0\n with:\n client-id: ${{ vars.RELEASE_BOT_CLIENT_ID }}\n private-key: ${{ secrets.RELEASE_BOT_APP_PRIVATE_KEY }}\n owner: ComposioHQ\n repositories: support-knowledge\n permission-contents: read",
438 - "count": 1
439 - },
434 {
435 "ruleId": "yaml-continue-on-error",
436 "file": ".github/workflows/docs-update-data.yml",
@@ -452,7 +446,7 @@
446 {
447 "ruleId": "yaml-continue-on-error",
448 "file": ".github/workflows/docs-update-data.yml",
455 - "source": " - name: Track KB freshness findings\n if: always() && (steps.verify-kb.outputs.exit_code == '0' || steps.verify-kb.outputs.exit_code == '1')\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n VERIFY_EXIT: ${{ steps.verify-kb.outputs.exit_code }}\n TITLE: 'KB freshness: published guides contradict production data'\n run: |\n set -euo pipefail\n # Exactly one issue carries this label, so listing by label is the lookup.\n existing=$(gh issue list --state open --label kb-freshness \\\n --json number --jq '.[0].number // empty' 2>/dev/null || true)\n\n if [ \"$VERIFY_EXIT\" = \"0\" ]; then\n if [ -n \"$existing\" ]; then\n gh issue close \"$existing\" \\\n --comment \"Verified clean against the current production catalog by run ${{ github.run_id }}.\"\n fi\n exit 0\n fi\n\n {\n echo \"\\`verify:kb\\` found published KB guides whose claims no longer match production.\"\n echo\n echo \"Fix the guide, or demote it to \\`state: needs-review\\` in \\`docs/kb/manifest.json\\`\"\n echo \"so it stops serving readers while it is wrong.\"\n echo\n cat \"$RUNNER_TEMP/kb-freshness.md\" 2>/dev/null \\\n || echo \"Report unavailable — \\`verify:kb\\` exited $VERIFY_EXIT before writing it.\"\n echo\n echo \"_Regenerated by [run ${{ github.run_id }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})._\"\n } > \"$RUNNER_TEMP/kb-issue.md\"\n\n gh label create kb-freshness --color FBCA04 \\\n --description \"Published KB guides contradicting production data\" 2>/dev/null || true\n\n if [ -n \"$existing\" ]; then\n gh issue edit \"$existing\" --body-file \"$RUNNER_TEMP/kb-issue.md\"\n else\n gh issue create --title \"$TITLE\" --label kb-freshness \\\n --body-file \"$RUNNER_TEMP/kb-issue.md\"\n fi\n",
449 + "source": " - name: Track KB freshness findings\n if: always() && (steps.verify-kb.outputs.exit_code == '0' || steps.verify-kb.outputs.exit_code == '1')\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n VERIFY_EXIT: ${{ steps.verify-kb.outputs.exit_code }}\n TITLE: 'KB freshness: published guides contradict production data'\n run: |\n set -euo pipefail\n # Exactly one issue carries this label, so listing by label is the lookup.\n existing=$(gh issue list --state open --label kb-freshness \\\n --json number --jq '.[0].number // empty' 2>/dev/null || true)\n\n if [ \"$VERIFY_EXIT\" = \"0\" ]; then\n if [ -n \"$existing\" ]; then\n gh issue close \"$existing\" \\\n --comment \"Verified clean against the current production catalog by run ${{ github.run_id }}.\"\n fi\n exit 0\n fi\n\n {\n echo \"\\`verify:kb\\` found published KB guides whose claims no longer match production.\"\n echo\n echo \"Fix the guide, or demote it to \\`state: needs-review\\` in its \\`docs/kb/guides/<slug>.json\\`\"\n echo \"so it stops serving readers while it is wrong.\"\n echo\n cat \"$RUNNER_TEMP/kb-freshness.md\" 2>/dev/null \\\n || echo \"Report unavailable — \\`verify:kb\\` exited $VERIFY_EXIT before writing it.\"\n echo\n echo \"_Regenerated by [run ${{ github.run_id }}](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }})._\"\n } > \"$RUNNER_TEMP/kb-issue.md\"\n\n gh label create kb-freshness --color FBCA04 \\\n --description \"Published KB guides contradicting production data\" 2>/dev/null || true\n\n if [ -n \"$existing\" ]; then\n gh issue edit \"$existing\" --body-file \"$RUNNER_TEMP/kb-issue.md\"\n else\n gh issue create --title \"$TITLE\" --label kb-freshness \\\n --body-file \"$RUNNER_TEMP/kb-issue.md\"\n fi\n",
450 "count": 1
451 },
452 {
@@ -464,25 +458,19 @@
458 {
459 "ruleId": "yaml-continue-on-error",
460 "file": ".github/workflows/docs-update-data.yml",
467 - "source": " - name: Verify KB freshness against refreshed data\n id: verify-kb\n continue-on-error: true\n env:\n # Resolves manifest.source.commit on the upstream KB repository. Without\n # read access there the check reports \"unverifiable\" and stays silent,\n # so an unset or narrow token degrades quietly rather than crying wolf.\n GH_TOKEN: ${{ steps.source-token.outputs.token }}\n run: |\n set +e\n if [ -z \"${GH_TOKEN:-}\" ]; then\n echo \"KB source token unavailable; source-pin status will be unverifiable.\"\n fi\n bun scripts/verify-kb.ts --check-links --check-source-pin \\\n --markdown \"$RUNNER_TEMP/kb-freshness.md\"\n echo \"exit_code=$?\" >> \"$GITHUB_OUTPUT\"\n cat \"$RUNNER_TEMP/kb-freshness.md\" >> \"$GITHUB_STEP_SUMMARY\"",
468 - "count": 1
469 - },
470 - {
471 - "ruleId": "yaml-continue-on-error",
472 - "file": ".github/workflows/docs-update-kb.yml",
473 - "source": " - name: Close KB refresh failure issue\n if: needs.refresh.result == 'success' && (needs.refresh.outputs.changed != 'true' || needs.propose.result == 'success')\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n GH_REPO: ${{ github.repository }}\n LABEL: docs-kb-refresh-failure\n run: |\n existing=$(gh issue list --label \"$LABEL\" --state open --limit 1 \\\n --json number --jq '.[0].number // empty')\n if [ -n \"$existing\" ]; then\n gh issue close \"$existing\" \\\n --comment \"The support knowledge publication pipeline recovered in run ${{ github.run_id }}: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}.\"\n fi\n",
461 + "source": " - name: Verify KB freshness against refreshed data\n id: verify-kb\n continue-on-error: true\n run: |\n set +e\n bun scripts/verify-kb.ts --check-links \\\n --markdown \"$RUNNER_TEMP/kb-freshness.md\"\n echo \"exit_code=$?\" >> \"$GITHUB_OUTPUT\"\n cat \"$RUNNER_TEMP/kb-freshness.md\" >> \"$GITHUB_STEP_SUMMARY\"",
462 "count": 1
463 },
464 {
465 "ruleId": "yaml-continue-on-error",
466 "file": ".github/workflows/docs-update-kb.yml",
479 - "source": " - name: Generate read-only upstream token\n id: upstream-token\n continue-on-error: true\n uses: actions/create-github-app-token@64ab729a6294000f5aa4a4bc0b73d1f32bc45510 # v3.3.0\n with:\n client-id: ${{ vars.RELEASE_BOT_CLIENT_ID }}\n private-key: ${{ secrets.RELEASE_BOT_APP_PRIVATE_KEY }}\n owner: ComposioHQ\n repositories: support-knowledge\n permission-contents: read",
467 + "source": " - name: Close KB repair failure issue\n if: needs.refresh.result == 'success' && (needs.refresh.outputs.changed != 'true' || needs.propose.result == 'success')\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n GH_REPO: ${{ github.repository }}\n LABEL: docs-kb-refresh-failure\n run: |\n existing=$(gh issue list --label \"$LABEL\" --state open --limit 1 \\\n --json number --jq '.[0].number // empty')\n if [ -n \"$existing\" ]; then\n gh issue close \"$existing\" \\\n --comment \"The KB semantic artifact repair recovered in run ${{ github.run_id }}: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}.\"\n fi\n",
468 "count": 1
469 },
470 {
471 "ruleId": "yaml-continue-on-error",
472 "file": ".github/workflows/docs-update-kb.yml",
485 - "source": " - name: Open KB refresh failure issue\n if: needs.refresh.result == 'failure' || needs.propose.result == 'failure'\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n GH_REPO: ${{ github.repository }}\n LABEL: docs-kb-refresh-failure\n RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\n EVENT_NAME: ${{ github.event_name }}\n REFRESH_RESULT: ${{ needs.refresh.result }}\n PROPOSE_RESULT: ${{ needs.propose.result }}\n run: |\n gh label create \"$LABEL\" \\\n --color B60205 \\\n --description \"Scheduled support knowledge refresh is failing\" 2>/dev/null || true\n\n existing=$(gh issue list --label \"$LABEL\" --state open --limit 1 \\\n --json number --jq '.[0].number // empty')\n if [ -n \"$existing\" ]; then\n echo \"Issue #$existing is already open for this failure; not filing a duplicate.\"\n exit 0\n fi\n\n gh issue create \\\n --title \"Support knowledge refresh is failing\" \\\n --label \"$LABEL\" \\\n --body \"The automated support knowledge publication pipeline failed.\n\n - Run: $RUN_URL\n - Trigger: \\`$EVENT_NAME\\`\n - Refresh job: \\`$REFRESH_RESULT\\`\n - Proposal job: \\`$PROPOSE_RESULT\\`\n\n **Impact:** docs.composio.dev/kb remains on its last successfully imported\n support-knowledge commit until this workflow recovers.\n\n **First checks:** verify that the Release Bot GitHub App can read\n \\`ComposioHQ/support-knowledge\\` and write the refresh branch and PR in\n \\`ComposioHQ/composio\\`.\"",
473 + "source": " - name: Open KB repair failure issue\n if: needs.refresh.result == 'failure' || needs.propose.result == 'failure'\n continue-on-error: true\n env:\n GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}\n GH_REPO: ${{ github.repository }}\n LABEL: docs-kb-refresh-failure\n RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\n EVENT_NAME: ${{ github.event_name }}\n REFRESH_RESULT: ${{ needs.refresh.result }}\n PROPOSE_RESULT: ${{ needs.propose.result }}\n run: |\n gh label create \"$LABEL\" \\\n --color B60205 \\\n --description \"Scheduled KB semantic artifact repair is failing\" 2>/dev/null || true\n\n existing=$(gh issue list --label \"$LABEL\" --state open --limit 1 \\\n --json number --jq '.[0].number // empty')\n if [ -n \"$existing\" ]; then\n echo \"Issue #$existing is already open for this failure; not filing a duplicate.\"\n exit 0\n fi\n\n gh issue create \\\n --title \"KB semantic artifact repair is failing\" \\\n --label \"$LABEL\" \\\n --body \"The scheduled KB semantic artifact repair failed.\n\n - Run: $RUN_URL\n - Trigger: \\`$EVENT_NAME\\`\n - Rebuild job: \\`$REFRESH_RESULT\\`\n - Proposal job: \\`$PROPOSE_RESULT\\`\n\n **Impact:** KB search answers new or changed content with keyword results\n only until this workflow recovers.\n\n **First checks:** verify that \\`OPENAI_API_KEY\\` is set and that the Release\n Bot GitHub App can write the repair branch and PR in \\`ComposioHQ/composio\\`.\"",
474 "count": 1
475 },
476 {
.github/workflows/docs-kb-publish.yml
+48 -47
@@ -1,7 +1,10 @@
1 name: Docs - Publish KB Guide
2
3 -# The support portal sends this when someone approves a KB guide that Front Desk drafted: a new guide, a
4 -# rewrite or a retirement. It becomes one PR on next that merges itself once checks pass.
3 +# The support portal sends this when Front Desk proposes a KB change, and Zen (source: zen) sends it
4 +# when a merged code PR changes what a guide says: a new guide, a rewrite or a retirement. It becomes
5 +# one PR on next, and reviewing and merging that PR is the approval. Each guide
6 +# lives in its own files (kb/guides/<slug>.json, kb/articles, kb/source) and content/kb is generated
7 +# at build time, so PRs for different guides can wait for review side by side without conflicting.
8 on:
9 repository_dispatch:
10 types: [kb-guide-approved]
@@ -10,7 +13,7 @@ permissions:
13 contents: read
14
15 concurrency:
13 - # Shared with docs-update-kb: both workflows replace the KB snapshot.
16 + # Shared with docs-update-kb so each run starts from a settled next.
17 group: docs-kb-publication
18 cancel-in-progress: false
19 queue: max
@@ -20,48 +23,48 @@ jobs:
23 runs-on: ubuntu-latest
24 permissions:
25 contents: read
23 - pull-requests: read
26 defaults:
27 run:
28 shell: bash
29 working-directory: ./docs
30
31 steps:
32 + # Every payload field that reaches a branch name or the PR body is checked here first.
33 - name: Check request
34 + id: request
35 env:
36 + SOURCE: ${{ github.event.client_payload.source }}
37 DRAFT_ID: ${{ github.event.client_payload.draft_id }}
38 + REQUEST_ID: ${{ github.event.client_payload.request_id }}
39 + ORIGIN_URL: ${{ github.event.client_payload.origin_url }}
40 + ORIGIN_AUTHOR: ${{ github.event.client_payload.origin_author }}
41 run: |
34 - if ! [[ "$DRAFT_ID" =~ ^[0-9]+$ ]]; then
35 - echo "draft_id must be a number" >&2
42 + if [ "$SOURCE" = zen ]; then
43 + if ! [[ "$REQUEST_ID" =~ ^[a-z0-9-]+$ ]]; then
44 + echo "request_id must match ^[a-z0-9-]+$" >&2
45 + exit 1
46 + fi
47 + if ! [[ "$ORIGIN_URL" =~ ^https://github\.com/[A-Za-z0-9_.-]+/[A-Za-z0-9_.-]+/pull/[0-9]+$ ]]; then
48 + echo "origin_url must be a GitHub pull request URL" >&2
49 + exit 1
50 + fi
51 + if ! [[ "$ORIGIN_AUTHOR" =~ ^[A-Za-z0-9-]+$ ]]; then
52 + echo "origin_author must be a GitHub login" >&2
53 + exit 1
54 + fi
55 + echo "branch=docs/kb-$REQUEST_ID" >> "$GITHUB_OUTPUT"
56 + elif [ -z "$SOURCE" ]; then
57 + if ! [[ "$DRAFT_ID" =~ ^[0-9]+$ ]]; then
58 + echo "draft_id must be a number" >&2
59 + exit 1
60 + fi
61 + echo "branch=docs/kb-front-desk-$DRAFT_ID" >> "$GITHUB_OUTPUT"
62 + else
63 + echo "Unknown source: $SOURCE" >&2
64 exit 1
65 fi
66 working-directory: .
67
40 - # A finished workflow may still have a PR waiting on checks or review.
41 - # Wait before checkout so each approval starts from the preceding merge.
42 - - name: Wait for earlier KB publications
43 - timeout-minutes: 31
44 - working-directory: .
45 - env:
46 - GH_TOKEN: ${{ github.token }}
47 - GH_REPO: ${{ github.repository }}
48 - PUBLISH_BRANCH: docs/kb-front-desk-${{ github.event.client_payload.draft_id }}
49 - run: |
50 - for ((attempt = 1; attempt <= 60; attempt++)); do
51 - pending=$(gh api --paginate "repos/$GH_REPO/pulls?state=open&base=next&per_page=100" \
52 - --jq '.[] | select(.head.repo.full_name == env.GH_REPO) | select(.head.ref == "docs/auto-update-kb" or (.head.ref | startswith("docs/kb-front-desk-"))) | select(.head.ref != env.PUBLISH_BRANCH) | .html_url')
53 - if [ -z "$pending" ]; then
54 - exit 0
55 - fi
56 - echo "Waiting for earlier KB publications to merge or close:"
57 - echo "$pending"
58 - if [ "$attempt" -lt 60 ]; then
59 - sleep 30
60 - fi
61 - done
62 - echo "Earlier KB publications are still open. Merge or close them, then rerun this workflow." >&2
63 - exit 1
64 -
68 - name: Checkout docs repository
69 uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
70 with:
@@ -87,11 +90,20 @@ jobs:
90 run: |
91 bun run generate:kb
92 bun run check:kb
90 - bun run verify:kb --json | tee "$RUNNER_TEMP/kb-verify.json"
93 + # verify:kb exits 1 for any finding in the whole KB. Other guides' findings (such as
94 + # expired review dates) are tracked by the data-sync freshness check; only this guide's
95 + # errors and support prose, and KB-wide errors, block its publication.
96 + bun run verify:kb --json > "$RUNNER_TEMP/kb-verify.json" || true
97 + jq -e '.findings | type == "array"' "$RUNNER_TEMP/kb-verify.json" > /dev/null
98 if ! jq -e '[.findings[] | select(.kind == "unedited-support-prose" and .guideSlug == env.GUIDE_SLUG)] | length == 0' "$RUNNER_TEMP/kb-verify.json"; then
99 echo "KB publication contains support-facing prose. Rewrite it for public readers before approving again." >&2
100 exit 1
101 fi
102 + if ! jq -e '[.findings[] | select(.severity == "error" and ((.guideSlug // "") == env.GUIDE_SLUG or (.guideSlug // "") == ""))] | length == 0' "$RUNNER_TEMP/kb-verify.json"; then
103 + jq -r '.findings[] | select(.severity == "error" and ((.guideSlug // "") == env.GUIDE_SLUG or (.guideSlug // "") == "")) | "\(.kind): \(.detail)"' "$RUNNER_TEMP/kb-verify.json" >&2
104 + echo "KB publication fails verification. Fix the guide before approving again." >&2
105 + exit 1
106 + fi
107
108 - name: Generate composio PR token
109 id: write-token
@@ -105,30 +117,19 @@ jobs:
117 permission-pull-requests: write
118
119 - name: Create pull request
108 - id: pr
120 uses: peter-evans/create-pull-request@3ffccacd46053766916f087ce41d627c0b8cf2d1 # v8.1.3
121 with:
122 token: ${{ steps.write-token.outputs.token }}
123 commit-message: 'docs(kb): ${{ github.event.client_payload.summary }}'
124 title: 'docs(kb): ${{ github.event.client_payload.summary }}'
125 body: |
115 - KB guide approved in the support portal by ${{ github.event.client_payload.approved_by }}.
126 + ${{ github.event.client_payload.source == 'zen' && format('KB guide change proposed by Zen from {0} (@{1}).', github.event.client_payload.origin_url, github.event.client_payload.origin_author) || 'KB guide change proposed by Front Desk in the support portal.' }}
127
128 - Guide: `${{ github.event.client_payload.guide.slug }}` (${{ github.event.client_payload.guide.action }})
118 - - Draft: ${{ github.event.client_payload.portal_url }}
129 + ${{ github.event.client_payload.source != 'zen' && format('- Draft: {0}', github.event.client_payload.portal_url) || '' }}
130
120 - Front Desk drafted it; the approver reviewed and edited it in the portal. This PR merges itself
121 - once checks pass.
122 - branch: docs/kb-front-desk-${{ github.event.client_payload.draft_id }}
131 + Review the article and merge to publish it; close the PR to dismiss it. Nothing merges on its own.
132 + branch: ${{ steps.request.outputs.branch }}
133 base: next
134 add-paths: |
135 docs/kb/
126 - docs/content/kb/
127 -
128 - - name: Merge once checks pass
129 - if: steps.pr.outputs.pull-request-number
130 - env:
131 - GH_TOKEN: ${{ steps.write-token.outputs.token }}
132 - GH_REPO: ${{ github.repository }}
133 - PR: ${{ steps.pr.outputs.pull-request-number }}
134 - run: gh pr merge "$PR" --auto --squash
.github/workflows/docs-rebuild-kb-semantic.yml
+1 -1
@@ -171,7 +171,7 @@ jobs:
171 GH_TOKEN: ${{ steps.write-token.outputs.token }}
172 HEAD_REF: ${{ needs.authorize.outputs.head_ref }}
173 run: |
174 - git add kb/semantic-index.json content/kb/
174 + git add kb/semantic-index.json
175 if git diff --cached --quiet; then
176 echo "::error::Semantic freshness failed, but rebuilding produced no tracked artifact changes."
177 exit 1
.github/workflows/docs-update-data.yml
+2 -21
@@ -51,17 +51,6 @@ jobs:
51 permission-contents: write
52 permission-pull-requests: write
53
54 - - name: Generate read-only KB source token
55 - id: source-token
56 - continue-on-error: true
57 - uses: actions/create-github-app-token@64ab729a6294000f5aa4a4bc0b73d1f32bc45510 # v3.3.0
58 - with:
59 - client-id: ${{ vars.RELEASE_BOT_CLIENT_ID }}
60 - private-key: ${{ secrets.RELEASE_BOT_APP_PRIVATE_KEY }}
61 - owner: ComposioHQ
62 - repositories: support-knowledge
63 - permission-contents: read
64 -
54 - name: Checkout repository
55 uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
56 with:
@@ -128,17 +117,9 @@ jobs:
117 - name: Verify KB freshness against refreshed data
118 id: verify-kb
119 continue-on-error: true
131 - env:
132 - # Resolves manifest.source.commit on the upstream KB repository. Without
133 - # read access there the check reports "unverifiable" and stays silent,
134 - # so an unset or narrow token degrades quietly rather than crying wolf.
135 - GH_TOKEN: ${{ steps.source-token.outputs.token }}
120 run: |
121 set +e
138 - if [ -z "${GH_TOKEN:-}" ]; then
139 - echo "KB source token unavailable; source-pin status will be unverifiable."
140 - fi
141 - bun scripts/verify-kb.ts --check-links --check-source-pin \
122 + bun scripts/verify-kb.ts --check-links \
123 --markdown "$RUNNER_TEMP/kb-freshness.md"
124 echo "exit_code=$?" >> "$GITHUB_OUTPUT"
125 cat "$RUNNER_TEMP/kb-freshness.md" >> "$GITHUB_STEP_SUMMARY"
@@ -335,7 +316,7 @@ jobs:
316 {
317 echo "\`verify:kb\` found published KB guides whose claims no longer match production."
318 echo
338 - echo "Fix the guide, or demote it to \`state: needs-review\` in \`docs/kb/manifest.json\`"
319 + echo "Fix the guide, or demote it to \`state: needs-review\` in its \`docs/kb/guides/<slug>.json\`"
320 echo "so it stops serving readers while it is wrong."
321 echo
322 cat "$RUNNER_TEMP/kb-freshness.md" 2>/dev/null \
.github/workflows/docs-update-kb.yml
+39 -134
@@ -1,19 +1,19 @@
1 -name: Docs - Update Support Knowledge
1 +name: Docs - Repair KB Semantic Artifact
2
3 +# KB guides are published by the support portal through docs-kb-publish.yml.
4 +# This six-hour run repairs kb/semantic-index.json when docs or guide changes
5 +# landed on next without a rebuild (fork PRs, or a publication that merged
6 +# before docs-rebuild-kb-semantic.yml finished).
7 on:
4 - # Dispatch is the primary path; this six-hour run reconciles missed events and
5 - # repairs semantic artifacts made stale by docs-side content changes.
8 schedule:
9 - cron: '17 */6 * * *'
8 - repository_dispatch:
9 - types: [support-knowledge-updated]
10 workflow_dispatch:
11
12 permissions:
13 contents: read
14
15 concurrency:
16 - # Shared with portal publications so neither snapshots an outdated KB.
16 + # Shared with portal publications so each run starts from a settled next.
17 group: docs-kb-publication
18 cancel-in-progress: false
19 queue: max
@@ -23,56 +23,14 @@ jobs:
23 runs-on: ubuntu-latest
24 permissions:
25 contents: read
26 - pull-requests: read
26 outputs:
27 docs_base_sha: ${{ steps.docs-base.outputs.sha }}
29 - changed: ${{ steps.rebuild.outputs.changed }}
30 - upstream_changed: ${{ steps.source.outputs.upstream_changed }}
31 - commit: ${{ steps.source.outputs.commit }}
28 + changed: ${{ steps.semantic.outputs.stale }}
29 defaults:
30 run:
31 working-directory: ./docs
32
33 steps:
37 - # A finished workflow may still have a PR waiting on checks or review.
38 - # Wait before checkout so each approval starts from the preceding merge.
39 - - name: Wait for earlier KB publications
40 - timeout-minutes: 31
41 - working-directory: .
42 - env:
43 - GH_TOKEN: ${{ github.token }}
44 - GH_REPO: ${{ github.repository }}
45 - PUBLISH_BRANCH: docs/auto-update-kb
46 - run: |
47 - for ((attempt = 1; attempt <= 60; attempt++)); do
48 - pending=$(gh api --paginate "repos/$GH_REPO/pulls?state=open&base=next&per_page=100" \
49 - --jq '.[] | select(.head.repo.full_name == env.GH_REPO) | select(.head.ref == "docs/auto-update-kb" or (.head.ref | startswith("docs/kb-front-desk-"))) | select(.head.ref != env.PUBLISH_BRANCH) | .html_url')
50 - if [ -z "$pending" ]; then
51 - exit 0
52 - fi
53 - echo "Waiting for earlier KB publications to merge or close:"
54 - echo "$pending"
55 - if [ "$attempt" -lt 60 ]; then
56 - sleep 30
57 - fi
58 - done
59 - echo "Earlier KB publications are still open. Merge or close them, then rerun this workflow." >&2
60 - exit 1
61 -
62 - # If the app has no installation on support-knowledge, this fails
63 - # with 404. Degrade to an upstream-sync skip instead of killing the
64 - # whole job: the stale-artifact rebuild below needs only this repo.
65 - - name: Generate read-only upstream token
66 - id: upstream-token
67 - continue-on-error: true
68 - uses: actions/create-github-app-token@64ab729a6294000f5aa4a4bc0b73d1f32bc45510 # v3.3.0
69 - with:
70 - client-id: ${{ vars.RELEASE_BOT_CLIENT_ID }}
71 - private-key: ${{ secrets.RELEASE_BOT_APP_PRIVATE_KEY }}
72 - owner: ComposioHQ
73 - repositories: support-knowledge
74 - permission-contents: read
75 -
34 - name: Checkout docs repository
35 uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
36 with:
@@ -85,26 +43,6 @@ jobs:
43 docs_base_sha=$(git rev-parse HEAD)
44 echo "sha=$docs_base_sha" >> "$GITHUB_OUTPUT"
45
88 - - name: Checkout support knowledge
89 - if: steps.upstream-token.outcome == 'success'
90 - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
91 - with:
92 - repository: ComposioHQ/support-knowledge
93 - token: ${{ steps.upstream-token.outputs.token }}
94 - ref: ${{ github.event_name == 'repository_dispatch' && github.event.client_payload.source_commit || 'main' }}
95 - path: .support-knowledge
96 - persist-credentials: false
97 - fetch-depth: 0
98 -
99 - - name: Resolve upstream change
100 - id: source
101 - env:
102 - SOURCE_ROOT: ${{ github.workspace }}/.support-knowledge
103 - HAVE_UPSTREAM: ${{ steps.upstream-token.outcome == 'success' }}
104 - EVENT_NAME: ${{ github.event_name }}
105 - REQUESTED_SOURCE_COMMIT: ${{ github.event_name == 'repository_dispatch' && github.event.client_payload.source_commit || '' }}
106 - run: bash scripts/resolve-kb-refresh-source.sh
107 -
46 - name: Setup Node.js, pnpm, Bun
47 uses: ./.github/actions/setup-node-pnpm-bun
48
@@ -119,12 +57,8 @@ jobs:
57 - name: Install dependencies
58 run: bun install
59
122 - # Docs-side text changes (generator updates, guide edits) also invalidate
123 - # the checked-in semantic artifact. Detect that here so CI rebuilds the
124 - # artifact even when the upstream support-knowledge commit has not moved.
60 - name: Detect stale semantic artifact
61 id: semantic
127 - if: steps.source.outputs.upstream_changed == 'false'
62 run: |
63 if bun scripts/build-kb-semantic-index.ts --check; then
64 echo "stale=false" >> "$GITHUB_OUTPUT"
@@ -133,46 +67,22 @@ jobs:
67 echo "Semantic artifact is stale against the checked-in docs corpus."
68 fi
69
136 - - name: Resolve rebuild
137 - id: rebuild
138 - run: |
139 - if [ "${{ steps.source.outputs.upstream_changed }}" = "true" ] || [ "${{ steps.semantic.outputs.stale }}" = "true" ]; then
140 - echo "changed=true" >> "$GITHUB_OUTPUT"
141 - else
142 - echo "changed=false" >> "$GITHUB_OUTPUT"
143 - echo "Support knowledge and semantic artifact are both current."
144 - fi
145 -
146 - - name: Import public support knowledge
147 - if: steps.source.outputs.upstream_changed == 'true'
148 - env:
149 - SOURCE_ROOT: ${{ github.workspace }}/.support-knowledge
150 - SOURCE_COMMIT: ${{ steps.source.outputs.commit }}
151 - run: >-
152 - bun run import:kb --
153 - --source-root "$SOURCE_ROOT"
154 - --source-commit "$SOURCE_COMMIT"
155 -
70 - name: Rebuild generated pages and semantic artifact
157 - if: steps.rebuild.outputs.changed == 'true'
71 + if: steps.semantic.outputs.stale == 'true'
72 env:
73 OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
74 run: bun run build:kb-semantic
75
162 - - name: Verify refreshed knowledge base
163 - if: steps.rebuild.outputs.changed == 'true'
164 - run: |
165 - bun run verify:kb
166 - bun run check:kb-semantic
76 + - name: Verify rebuilt semantic artifact
77 + if: steps.semantic.outputs.stale == 'true'
78 + run: bun run check:kb-semantic
79
168 - - name: Upload verified KB artifacts
169 - if: steps.rebuild.outputs.changed == 'true'
80 + - name: Upload verified semantic artifact
81 + if: steps.semantic.outputs.stale == 'true'
82 uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7.0.2
83 with:
172 - name: support-knowledge-refresh
173 - path: |
174 - docs/kb/
175 - docs/content/kb/
84 + name: kb-semantic-repair
85 + path: docs/kb/semantic-index.json
86 if-no-files-found: error
87 retention-days: 1
88
@@ -191,11 +101,11 @@ jobs:
101 ref: ${{ needs.refresh.outputs.docs_base_sha }}
102 persist-credentials: false
103
194 - - name: Download verified KB artifacts
104 + - name: Download verified semantic artifact
105 uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8.0.2
106 with:
197 - name: support-knowledge-refresh
198 - path: docs
107 + name: kb-semantic-repair
108 + path: docs/kb
109
110 - name: Generate composio PR token
111 id: write-token
@@ -208,28 +118,24 @@ jobs:
118 permission-contents: write
119 permission-pull-requests: write
120
211 - - name: Create refresh pull request
121 + - name: Create repair pull request
122 uses: peter-evans/create-pull-request@3ffccacd46053766916f087ce41d627c0b8cf2d1 # v8.1.3
123 with:
124 token: ${{ steps.write-token.outputs.token }}
215 - commit-message: 'docs(kb): refresh public support knowledge'
216 - title: 'docs(kb): refresh public support knowledge'
125 + commit-message: 'docs(kb): rebuild stale semantic artifact'
126 + title: 'docs(kb): rebuild stale semantic artifact'
127 body: |
218 - Automated knowledge-base refresh for `ComposioHQ/support-knowledge`.
128 + Automated rebuild of `docs/kb/semantic-index.json` after docs or KB guide changes landed on `next` without one.
129
220 - - Source commit: `${{ needs.refresh.outputs.commit }}` (${{ needs.refresh.outputs.upstream_changed == 'true' && 'imported new support knowledge' || 'unchanged; rebuilt a stale semantic artifact' }})
221 - - Regenerated public KB pages and search records
222 - - Reused unchanged vectors and rebuilt the checked semantic artifact
223 - - Ran KB freshness and semantic-artifact verification
130 + - Reused unchanged vectors and embedded only changed records
131 + - Verified semantic artifact against the checked-in corpus
132 branch: docs/auto-update-kb
133 base: next
226 - add-paths: |
227 - docs/kb/
228 - docs/content/kb/
134 + add-paths: docs/kb/semantic-index.json
135
230 - # Import and PR creation are one publication pipeline. Report after both jobs
231 - # so a successful import cannot hide a failed proposal, and close the issue
232 - # only after every required stage has recovered.
136 + # Rebuild and PR creation are one pipeline. Report after both jobs so a
137 + # successful rebuild cannot hide a failed proposal, and close the issue only
138 + # after every required stage has recovered.
139 report:
140 needs: [refresh, propose]
141 if: always()
@@ -238,7 +144,7 @@ jobs:
144 issues: write
145
146 steps:
241 - - name: Open KB refresh failure issue
147 + - name: Open KB repair failure issue
148 if: needs.refresh.result == 'failure' || needs.propose.result == 'failure'
149 continue-on-error: true
150 env:
@@ -252,7 +158,7 @@ jobs:
158 run: |
159 gh label create "$LABEL" \
160 --color B60205 \
255 - --description "Scheduled support knowledge refresh is failing" 2>/dev/null || true
161 + --description "Scheduled KB semantic artifact repair is failing" 2>/dev/null || true
162
163 existing=$(gh issue list --label "$LABEL" --state open --limit 1 \
164 --json number --jq '.[0].number // empty')
@@ -262,23 +168,22 @@ jobs:
168 fi
169
170 gh issue create \
265 - --title "Support knowledge refresh is failing" \
171 + --title "KB semantic artifact repair is failing" \
172 --label "$LABEL" \
267 - --body "The automated support knowledge publication pipeline failed.
173 + --body "The scheduled KB semantic artifact repair failed.
174
175 - Run: $RUN_URL
176 - Trigger: \`$EVENT_NAME\`
271 - - Refresh job: \`$REFRESH_RESULT\`
177 + - Rebuild job: \`$REFRESH_RESULT\`
178 - Proposal job: \`$PROPOSE_RESULT\`
179
274 - **Impact:** docs.composio.dev/kb remains on its last successfully imported
275 - support-knowledge commit until this workflow recovers.
180 + **Impact:** KB search answers new or changed content with keyword results
181 + only until this workflow recovers.
182
277 - **First checks:** verify that the Release Bot GitHub App can read
278 - \`ComposioHQ/support-knowledge\` and write the refresh branch and PR in
279 - \`ComposioHQ/composio\`."
183 + **First checks:** verify that \`OPENAI_API_KEY\` is set and that the Release
184 + Bot GitHub App can write the repair branch and PR in \`ComposioHQ/composio\`."
185
281 - - name: Close KB refresh failure issue
186 + - name: Close KB repair failure issue
187 if: needs.refresh.result == 'success' && (needs.refresh.outputs.changed != 'true' || needs.propose.result == 'success')
188 continue-on-error: true
189 env:
@@ -290,5 +195,5 @@ jobs:
195 --json number --jq '.[0].number // empty')
196 if [ -n "$existing" ]; then
197 gh issue close "$existing" \
293 - --comment "The support knowledge publication pipeline recovered in run ${{ github.run_id }}: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}."
198 + --comment "The KB semantic artifact repair recovered in run ${{ github.run_id }}: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}."
199 fi
docs/.gitignore
+3
@@ -47,3 +47,6 @@ next-env.d.ts.cache
47
48 # Source-history manifest (generated before dev/build/typecheck; bundled for runtime).
49 /.generated/
50 +
51 +# Generated from kb/ by `bun run generate:kb` (postinstall, dev, build, test, typecheck).
52 +/content/kb/
docs/CONTRIBUTING.md
+1 -1
@@ -54,7 +54,7 @@ To check the built site's endpoints, run `bun run start` in one terminal and `bu
54
55 The semantic artifact covers both regular docs and KB articles, so edits to either can make it stale. PR checks use `--allow-stale` to warn about freshness while still rejecting missing or corrupt artifacts. Search falls back to keyword results until the artifact is rebuilt.
56
57 -The `Docs - Rebuild KB Semantic Artifact` workflow can rebuild it for eligible same-repository PRs after `Docs - Tests` runs. The scheduled support-knowledge refresh also proposes stale-artifact repairs. If you rebuild locally with `bun run build:kb-semantic`, use an authorized `OPENAI_API_KEY`: the generator sends the indexed docs content to the embeddings service. Run `bun run check:kb-semantic` without `--allow-stale` to verify a rebuild. Never edit embedding values or content hashes by hand.
57 +The `Docs - Rebuild KB Semantic Artifact` workflow can rebuild it for eligible same-repository PRs after `Docs - Tests` runs. The scheduled `Docs - Repair KB Semantic Artifact` workflow also proposes repairs for anything that reached `next` stale. If you rebuild locally with `bun run build:kb-semantic`, use an authorized `OPENAI_API_KEY`: the generator sends the indexed docs content to the embeddings service. Run `bun run check:kb-semantic` without `--allow-stale` to verify a rebuild. Never edit embedding values or content hashes by hand.
58
59 ## Agent-readable representations
60
docs/agent/instructions.md
+1 -1
@@ -14,7 +14,7 @@ You are **Eve**, the Composio documentation assistant. You live in the right sid
14 You have a **concept map** (always in your context) with the canonical page for each Composio concept, plus exactly two tools. You have **no web search and no file access**, so answer only from the Composio docs via these tools, and link the docs' own relative URLs (never `docs.composio.dev` or other external links).
15
16 - You may receive **eager docs search context** with the user's latest message. It is an automatic `search_docs` result injected before the model step to save latency.
17 -- `search_docs(query)`: fast BM25-style local docs search. It returns relevant pages and bounded full content plus sections for the top results. You can still call it whenever eager context is missing, weak, ambiguous, or too narrow.
17 +- `search_docs(query)`: fast BM25-style local search over the docs and the Knowledge Base guides (`/kb/guide/...`). It returns relevant pages and bounded full content plus sections for the top results. You can still call it whenever eager context is missing, weak, ambiguous, or too narrow.
18 - `read_doc(url)`: read a page's full Markdown content when you need a page beyond the content included by eager context or `search_docs`.
19
20 Workflow for anything non-trivial:
docs/agent/instructions/context.ts
+2
@@ -22,6 +22,8 @@ This is your always-on map of Composio's concepts and the canonical page for eac
22 - **Providers** — adapter packages that format Composio tools for a framework (OpenAI, Anthropic, Vercel AI SDK, LangChain, Mastra, Pi, …). → [Providers](/docs/providers)
23 - **Is a toolkit / integration supported?** Composio has ${TOOLKIT_COUNT_LABEL} toolkits, and \`search_docs\` indexes the catalog. A matching \`/toolkits/<slug>\` result means **yes, it's supported** — answer from the returned content when sufficient, call \`read_doc\` only for more details, and point the user at [the toolkits directory](/toolkits). If nothing matches, it isn't a built-in toolkit; suggest [proxy execute](/docs/extending-sessions/proxy-execute) or a [local tool](/docs/extending-sessions/local-tools-and-toolkits) for an API you already have.
24
25 +- **Errors, limits, and toolkit-specific behavior** — the [Knowledge Base](/kb) holds verified troubleshooting guides from Composio support (\`/kb/guide/<slug>\`). \`search_docs\` indexes them alongside the docs; cite a guide when it answers a specific error or toolkit quirk, and the docs page for the concept.
26 +
27 ## Authentication
28
29 - **How auth works** — Composio uses Connect Links (hosted auth pages) and **auth configs** (per-toolkit blueprints) to create **connected accounts** (stored credentials) scoped to a userID. This is the page for "how does authentication work". → [Authentication](/docs/authentication)
docs/agent/knowledge.md deleted
-37
@@ -1,37 +0,0 @@
1 -# Composio knowledge base
2 -
3 -Curated, searchable knowledge for the docs assistant. Each `## Heading (/url)`
4 -section is indexed by `search_docs` and links its canonical page. Add entries
5 -here to expose more answers to search without changing the docs themselves.
6 -
7 -## Installing and getting started (/docs/quickstart)
8 -
9 -Install the SDK with `npm install @composio/core` (TypeScript) or `pip install composio` (Python), set `COMPOSIO_API_KEY`, then create a session with `composio.create("user_123")`. The quickstart walks through creating a session, fetching tools for your framework via a provider, and running an agent.
10 -
11 -## Choosing a provider (/docs/providers)
12 -
13 -A provider adapts Composio tools into the shape your AI framework expects. Composio ships providers for OpenAI, the Anthropic SDK, the Vercel AI SDK, LangChain, Mastra, the Pi coding agent, and more. Pass a provider when constructing `Composio({ provider })`, then `session.tools()` returns tools formatted for that framework. You can also build a custom provider.
14 -
15 -## userID best practices (/docs/how-composio-works)
16 -
17 -The userID scopes connected accounts and tool executions and isolates users from each other. Use a stable identifier such as your database UUID or primary key. Avoid email addresses (they change) and never use `default` in production, since that exposes one user's connections to others.
18 -
19 -## Native tools vs MCP (/docs/sessions-via-mcp)
20 -
21 -By default a session gives your agent tools it calls directly through a provider package; this integrates with your framework and supports modifiers and custom tools. Creating a session with `{ mcp: true }` also exposes `session.mcp.url` and `session.mcp.headers` for any MCP-compatible client. MCP is more portable across clients, but modifiers and custom tools do not apply over the MCP surface.
22 -
23 -## Apps: Composio Built vs Provider MCP toolkits (/docs/apps-and-toolkits)
24 -
25 -An App groups the sibling toolkits for one product in the catalog; for example, the Notion app contains the `notion` and `notion_mcp` toolkits. A Composio Built toolkit is built and maintained by Composio on the product's public API and can have triggers. A Provider MCP toolkit (for example, `notion_mcp`) connects to the product's own hosted MCP server, commonly uses DCR OAuth, and has no triggers today. Siblings are separate toolkits with separate auth configs and connected accounts; sessions, search, and execution take exact toolkit slugs, and an App display name is not a toolkit identifier. To choose, compare auth schemes, tool lists, and triggers, and prefer the toolkit your users can authenticate.
26 -
27 -## Custom MCP vs Provider MCP toolkits (/docs/extending-sessions/custom-mcp)
28 -
29 -A Custom MCP toolkit is your own remote MCP server registered into your project (slug `CUSTOM_*`); it can be shared within the project or private to one user and never grouped into an App. A Provider MCP toolkit is a catalog toolkit that connects to a product's own hosted MCP server (for example, `notion_mcp`) and is available to every project. Use Custom MCP for an MCP server that isn't in the catalog; when the product already ships a Provider MCP toolkit, use that instead.
30 -
31 -## Sandbox files and the /mnt/files mount (/docs/sandbox)
32 -
33 -The sandbox has a persistent file mount at `/mnt/files/` that survives sandbox restarts (changing the compute tier clears in-memory state but keeps the mount). Move files between your app and the mount with `session.experimental.files` (`upload`, `list`, `download`, `delete`). A `RemoteFile`'s `expiresAt` is the download-link expiry, not a file TTL, and there is no SDK call to create custom mounts.
34 -
35 -## Reusing and updating sessions (/docs/how-composio-works)
36 -
37 -Sessions persist on the server and do not expire. For a multi-turn conversation, store the session ID and reuse it with `composio.use(sessionId)` instead of calling `create()` again. You can also change a live session in place with `session.update({ toolkits, authConfigs, connectedAccounts })`.
docs/agent/lib/docs-search.ts
+2 -10
@@ -20,11 +20,11 @@ import {
20 */
21
22 // Collection priority: docs first, then examples, then references and toolkits.
23 -// (Curated knowledge ranks with docs.) A toolkit-name query still surfaces its
23 +// (Knowledge base guides rank with docs.) A toolkit-name query still surfaces its
24 // toolkit page because nothing else matches it.
25 const PRIORITY: Record<DocPage['collection'], number> = {
26 docs: 1.3,
27 - knowledge: 1.3,
27 + kb: 1.3,
28 examples: 1.1,
29 reference: 0.85,
30 toolkits: 0.9,
@@ -290,14 +290,6 @@ function contentFor(
290 maxContentChars: number,
291 maxSections: number
292 ) {
293 - if (page.collection === 'knowledge') {
294 - const evidence = excerpt(page.text, terms, maxContentChars);
295 - return {
296 - content: evidence.value,
297 - contentTruncated: evidence.truncated,
298 - };
299 - }
300 -
293 const found = readPageByUrl(page.url);
294
295 if (found) {
docs/agent/lib/docs.ts
+7 -38
@@ -1,9 +1,10 @@
1 /**
2 * Shared docs access for the agent's retrieval tools.
3 *
4 - * Builds a lazy in-memory index over `content/` plus the curated
5 - * `agent/knowledge.md`, maps page URLs to files, and flags legacy pages so the
6 - * search tool can heavily downrank them.
4 + * Builds a lazy in-memory index over `content/` (docs, reference, examples,
5 + * toolkits and the public knowledge base guides under `content/kb`), maps page
6 + * URLs to files, and flags legacy pages so the search tool can heavily downrank
7 + * them.
8 */
9
10 import { resolveToolkitCount } from '../../lib/toolkit-count';
@@ -43,8 +44,7 @@ function resolveAppRoot(): string {
44
45 const APP_ROOT = resolveAppRoot();
46 const CONTENT_ROOT = join(APP_ROOT, 'content');
46 -const KNOWLEDGE_FILE = join(APP_ROOT, 'agent', 'knowledge.md');
47 -const COLLECTIONS = ['docs', 'reference', 'examples', 'toolkits'] as const;
47 +const COLLECTIONS = ['docs', 'reference', 'examples', 'toolkits', 'kb'] as const;
48
49 /** URL prefixes for the legacy, pre-session / direct-execution docs. */
50 const LEGACY_URL_PATTERNS = [
@@ -111,7 +111,7 @@ const STOPWORDS = new Set([
111 'up',
112 ]);
113
114 -export type Collection = 'docs' | 'examples' | 'reference' | 'toolkits' | 'knowledge';
114 +export type Collection = (typeof COLLECTIONS)[number];
115
116 export interface DocPage {
117 collection: Collection;
@@ -176,6 +176,7 @@ export function urlFromContentPath(absPath: string): string | undefined {
176 if (collection === 'docs') return `/docs/${parts.join('/')}`.replace(/\/index$/, '');
177 if (collection === 'examples') return `/examples/${parts.join('/')}`.replace(/\/index$/, '');
178 if (collection === 'reference') return `/reference/${parts.join('/')}`.replace(/\/index$/, '');
179 + if (collection === 'kb') return `/kb/${parts.join('/')}`.replace(/\/index$/, '');
180 if (collection === 'toolkits') {
181 if (parts[0] === 'faq') return undefined;
182 return `/toolkits/${parts.join('/')}`.replace(/\/index$/, '');
@@ -287,34 +288,6 @@ function makePage(args: {
288 };
289 }
290
290 -/**
291 - * Parse `agent/knowledge.md` into searchable entries. Each `## Title (/url)`
292 - * section becomes one entry linked to its canonical doc page.
293 - */
294 -function loadKnowledge(): DocPage[] {
295 - let raw: string;
296 - try {
297 - raw = readFileSync(KNOWLEDGE_FILE, 'utf8');
298 - } catch {
299 - return [];
300 - }
301 - const pages: DocPage[] = [];
302 - const sectionRe = /^##\s+(.+?)\s*(?:\(([^)]+)\))?\s*$/gm;
303 - const matches = [...raw.matchAll(sectionRe)];
304 - for (let i = 0; i < matches.length; i++) {
305 - const m = matches[i];
306 - const title = m[1].trim();
307 - const url = (m[2] ?? '').trim() || '/docs';
308 - const bodyStart = m.index! + m[0].length;
309 - const bodyEnd = i + 1 < matches.length ? matches[i + 1].index! : raw.length;
310 - const body = raw.slice(bodyStart, bodyEnd).trim();
311 - pages.push(
312 - makePage({ collection: 'knowledge', title, description: '', url, legacy: false, body })
313 - );
314 - }
315 - return pages;
316 -}
317 -
291 /**
292 * Index the toolkit catalog from `public/data/toolkits.json` so the assistant
293 * can answer "do you have <toolkit>?" — individual toolkit pages are generated
@@ -397,9 +370,7 @@ let indexCache: DocPage[] | undefined;
370
371 export function buildBundledIndex(): DocPage[] {
372 const pages: DocPage[] = [];
400 - let bundleHasKnowledge = false;
373 for (const p of BUNDLE.pages) {
402 - if (p.collection === 'knowledge') bundleHasKnowledge = true;
374 pages.push(
375 makePage({
376 collection: p.collection,
@@ -411,7 +382,6 @@ export function buildBundledIndex(): DocPage[] {
382 })
383 );
384 }
414 - if (!bundleHasKnowledge) pages.push(...loadKnowledge());
385 pages.push(...loadBundledToolkits());
386 return pages;
387 }
@@ -458,7 +428,6 @@ export function buildIndex(): DocPage[] {
428 indexCache = pages;
429 return pages;
430 }
461 - pages.push(...loadKnowledge());
431 pages.push(...loadToolkits());
432 indexCache = pages;
433 return pages;
docs/agent/tools/read_doc.ts
+1 -1
@@ -13,7 +13,7 @@ const MAX_CHARS = 12000;
13
14 export default defineTool({
15 description:
16 - 'Read the full Markdown content of a Composio docs page by its URL (e.g. "/docs/authentication"). Returns the page content plus its `sections` (with anchors). Use this on the most relevant pages from search_docs before answering, and link the specific section anchor (e.g. /docs/how-composio-works#users) when your answer comes from one.',
16 + 'Read the full Markdown content of a Composio docs page or Knowledge Base guide by its URL (e.g. "/docs/authentication" or "/kb/guide/<slug>"). Returns the page content plus its `sections` (with anchors). Use this on the most relevant pages from search_docs before answering, and link the specific section anchor (e.g. /docs/how-composio-works#users) when your answer comes from one.',
17 inputSchema: z.object({
18 url: z.string().min(1).describe('The page URL, e.g. "/docs/authentication" or "/docs/configuring-sessions".'),
19 }),
docs/agent/tools/search_docs.ts
+1 -1
@@ -13,7 +13,7 @@ import { DEFAULT_SEARCH_LIMIT, searchDocs } from '../lib/docs-search';
13
14 export default defineTool({
15 description:
16 - 'Search the Composio documentation with a fast BM25-style local retriever. Returns relevant pages and includes full bounded content for the top matches, so you can answer from the returned context. Call read_doc only if you need a page beyond the included content.',
16 + 'Search the Composio documentation and Knowledge Base troubleshooting guides (/kb/guide/...) with a fast BM25-style local retriever. Returns relevant pages and includes full bounded content for the top matches, so you can answer from the returned context. Call read_doc only if you need a page beyond the included content.',
17 inputSchema: z.object({
18 query: z
19 .string()
docs/content/kb/guide/consumer-project-boundaries-and-auth-selection.mdx deleted
-62
@@ -1,62 +0,0 @@
1 ----
2 -title: "Consumer and Developer Project Boundaries"
3 -description: "Public support knowledge for Consumer and Developer Project Boundaries."
4 -keywords: ["consumer","for-you","project-boundaries-and-auth-selection","authentication","errors-and-troubleshooting","getting-started","sessions-and-execution","/kb/composio-for-you/workspace-members-do-not-automatically-share-for-you-connections","workspace-members-do-not-automatically-share-for-you-connections"]
5 -sources: [{"sourcePath":"consumer/project-boundaries-and-auth-selection/public.md","sourceHeading":"Rotate the Connect MCP consumer key"},{"sourcePath":"consumer/project-boundaries-and-auth-selection/public.md","sourceHeading":"Workspace members do not automatically share For You connections"},{"sourcePath":"consumer/project-boundaries-and-auth-selection/public.md","sourceHeading":"Shared connections must be explicitly allowed and pinned"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","getting-started","sessions-and-execution"]
10 -aliases: ["/kb/composio-for-you/workspace-members-do-not-automatically-share-for-you-connections","workspace-members-do-not-automatically-share-for-you-connections"]
11 ----
12 -Composio organizations have separate developer and consumer project surfaces. The developer dashboard/API shows developer projects. The consumer dashboard and consumer MCP / Composio MCP / Composio For You clients use a separate consumer project that customers usually do not see directly.
13 -
14 -Developer-project auth configs and connected accounts are not available in the consumer project. Consumer-project connections are not available in the developer project. If you created an auth config or connected an account in the developer dashboard but cannot use it in Claude, ChatGPT, Codex, Cursor, Composio For You, or another consumer MCP client, connect the account through the consumer flow instead.
15 -
16 -Consumer MCP auth has two common paths:
17 -
18 -1. Use the consumer MCP URL directly. If the MCP client supports auth, it can trigger the Composio auth flow, open a popup, let the customer authenticate, and let them select the organization.
19 -
20 -2. Use the consumer API key when the MCP client does not support auth and only supports API keys/headers. Copy the key from the consumer dashboard and pass it as the `x-consumer-api-key` header.
21 -
22 -Under the hood, a consumer-scoped MCP session is created for the specific user and allowed tools.
23 -
24 -The For You connection flow uses the auth config in the consumer project. Its current behavior is:
25 -
26 -1. When a Composio-managed auth app is available, the app uses that managed config and does not expose provider credentials for editing.
27 -
28 -2. When no managed app is available, **Manage Auth** appears for toolkits with editable customer-owned credentials or multiple auth schemes. Enter the provider client ID/secret or other required fields there and register the callback URI shown by the current form.
29 -
30 -3. Provider scopes are determined by the selected auth scheme and its current config. A managed app is limited to its approved scope set; customer-owned apps must configure and verify their scopes with the provider.
31 -
32 -## Rotate the Connect MCP consumer key
33 -
34 -These steps apply to a Connect consumer key with the `ck_*` prefix, sent as `x-consumer-api-key`. They do not apply to a Platform Project API key with the `ak_*` prefix. Reconnecting Gmail, Calendar, or another individual app does not rotate the consumer key.
35 -
36 -1. Open For You / Connect.
37 -2. Select **Settings** in the left sidebar.
38 -3. Open **Sessions & API Key**.
39 -4. Select **Regenerate** next to “Your API Key” and confirm.
40 -5. Update every MCP client that uses `https://connect.composio.dev/mcp` with the new `x-consumer-api-key` value.
41 -
42 -Regeneration immediately invalidates the old consumer key. If the button is missing even though you are in the correct workspace with write access, or you need help investigating suspicious usage, contact Composio support for account-level assistance.
43 -
44 -## Workspace members do not automatically share For You connections
45 -
46 -In the normal For You/Connect MCP flow, connected accounts belong to the member who authorized them. Another teammate using their own Connect MCP endpoint or `ck_*` consumer key resolves to their own connected accounts, not yours.
47 -
48 -- Admins can manage workspace settings and members, but their own Connect MCP session does not automatically use another member's accounts.
49 -- Members can connect and use their own accounts.
50 -- Viewers cannot connect or invoke tools from the For You surface.
51 -
52 -Raw `ak_*` Project API keys are different from `ck_*` consumer keys and must be treated as privileged project secrets. Explicitly shared or pinned connections are also a separate configuration from ordinary member-scoped connections.
53 -
54 -## Shared connections must be explicitly allowed and pinned
55 -
56 -A normal `PRIVATE` connection belongs to the user who created it. A `SHARED`
57 -connection can be used by other user IDs only when its ACL allows them and the
58 -connection is explicitly pinned into the session by connected-account ID.
59 -Shared connections are deny-by-default and are never selected implicitly.
60 -
61 -Follow the [Shared Connections guide](https://docs.composio.dev/docs/shared-connections#shared-vs-private)
62 -for the current ACL and session configuration.
docs/content/kb/guide/dashboard-account-deletion.mdx deleted
-26
@@ -1,26 +0,0 @@
1 ----
2 -title: "Delete a Composio organization"
3 -description: "Current self-service path and safety checks for organization deletion."
4 -keywords: ["account-deletion","dashboard","for-you","platform","account-and-billing"]
5 -sources: [{"sourcePath":"dashboard/account-deletion/public.md","sourceHeading":"Organization admins can use Delete this organization"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["account-and-billing"]
10 -aliases: []
11 ----
12 -## Organization admins can use Delete this organization
13 -
14 -In Platform, open **Settings → Organization Settings → General**. In For You,
15 -open **Settings → General**. Under **Delete this organization**, select **Delete
16 -organization** and complete the confirmation shown by the dashboard.
17 -
18 -The control is disabled for non-admins. A non-admin should contact an
19 -organization admin. The current warning states that deletion permanently
20 -removes the organization, its projects, connected accounts, API keys, and logs,
21 -so confirm the organization before proceeding.
22 -
23 -If upstream provider credentials also need to be invalidated, revoke the
24 -connected accounts where supported and remove the app or rotate the credential
25 -in the provider's own settings when necessary. Never send credentials to
26 -Composio support.
docs/content/kb/guide/dashboard-auth-configs-navigation.mdx deleted
-37
@@ -1,37 +0,0 @@
1 ----
2 -title: "Manage Platform auth configs"
3 -description: "Current dashboard steps for creating and managing Platform auth configs."
4 -keywords: ["auth-configs","dashboard","platform","auth-config","authentication","getting-started"]
5 -sources: [{"sourcePath":"dashboard/auth-configs-navigation/public.md","sourceHeading":"Create an auth config from the selected Platform project"},{"sourcePath":"dashboard/auth-configs-navigation/public.md","sourceHeading":"Connect Account on an auth config is a Playground test connection"},{"sourcePath":"dashboard/auth-configs-navigation/public.md","sourceHeading":"Manage Config changes future authentication behavior"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","getting-started"]
10 -aliases: []
11 ----
12 -## Create an auth config from the selected Platform project
13 -
14 -Open **Platform → Auth Configs → Create Auth Config**, choose the toolkit and
15 -supported authentication method, then select managed authentication when it is
16 -available or enter customer-owned credentials. For custom OAuth, register the
17 -exact callback URI shown by the current dashboard in the provider app; do not
18 -copy a callback URI from an old example.
19 -
20 -Auth configs belong to one Platform project. If a config or connection is
21 -missing, verify the selected organization and project before recreating it.
22 -
23 -## Connect Account on an auth config is a Playground test connection
24 -
25 -Open an auth config and select **Connect Account** to authenticate the
26 -project's Playground user for testing. This control does not ask for an
27 -application user ID. To connect an actual application user, create a hosted
28 -connection link through the SDK or API with that application's stable
29 -`user_id` and the intended auth config.
30 -
31 -## Manage Config changes future authentication behavior
32 -
33 -Use **Manage Config** to inspect the enabled state, credentials, and available
34 -scope or execution settings for that config type. Changing credentials or
35 -scopes can require users to create a fresh connection before the change is
36 -reflected in their provider grant. Review dependent connections, sessions, and
37 -triggers before disabling or deleting a config.
docs/content/kb/guide/dashboard-for-you-navigation.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Composio For You navigation"
3 -description: "Current navigation for connecting apps and agents in Composio For You."
4 -keywords: ["dashboard","for-you","account-and-billing","authentication","getting-started"]
5 -sources: [{"sourcePath":"dashboard/for-you-navigation/public.md","sourceHeading":"Use Connect Apps for provider accounts and Connect my agent for clients"},{"sourcePath":"dashboard/for-you-navigation/public.md","sourceHeading":"For You settings include Sessions & API Key"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["account-and-billing","authentication","getting-started"]
10 -aliases: []
11 ----
12 -## Use Connect Apps for provider accounts and Connect my agent for clients
13 -
14 -The current For You sidebar contains **Home**, **Connect Apps**, **Connect my
15 -agent**, and **Help**.
16 -
17 -- Open **Connect Apps**, select an app, and choose **Connect** to authenticate a
18 - provider account.
19 -- Open **Connect my agent** and select the target agent or MCP client for the
20 - current setup instructions. Copy the MCP URL, header, or key shown on that
21 - page rather than transferring configuration syntax from another client.
22 -- Open **Help** when the user needs the support route rather than self-service
23 - product guidance.
24 -
25 -
26 -## For You settings include Sessions & API Key
27 -
28 -For You settings currently contain **General**, **Members**, **Sessions & API
29 -Key**, and **Billing**. Use **Sessions & API Key** to inspect the current
30 -consumer connection instructions or regenerate the consumer key. Regeneration
31 -invalidates the previous key, so update every client that uses it. Never ask a
32 -customer to paste the key into a support conversation.
33 -
34 -For project auth configs, project users, triggers, logs, or `ak_...` project API
35 -keys, switch to Platform instead.
docs/content/kb/guide/dashboard-log-storage.mdx deleted
-18
@@ -1,18 +0,0 @@
1 ----
2 -title: "Dashboard Log Storage"
3 -description: "Public behavior of the project Log storage setting."
4 -keywords: ["dashboard","data-retention","logs","platform","errors-and-troubleshooting","security-and-trust","sessions-and-execution","/kb/dashboard-and-projects/don-t-store-data-removes-new-payload-content-not-the-audit-row","don-t-store-data-removes-new-payload-content-not-the-audit-row"]
5 -sources: [{"sourcePath":"dashboard/log-storage/public.md","sourceHeading":"“Don't store data” removes new payload content, not the audit row"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","security-and-trust","sessions-and-execution"]
10 -aliases: ["/kb/dashboard-and-projects/don-t-store-data-removes-new-payload-content-not-the-audit-row","don-t-store-data-removes-new-payload-content-not-the-audit-row"]
11 ----
12 -## “Don't store data” removes new payload content, not the audit row
13 -
14 -New tool executions can still appear in Tool Logs with audit metadata such as tool, status, timestamp, duration, and related identifiers. With **Don't store data** enabled, their request arguments and response payload content are not stored in those rows.
15 -
16 -Changing the setting does not retroactively erase older payloads. Run a new test after changing it and inspect that new row. If new request or response content remains visible, contact support with the timestamp and log reference.
17 -
18 -This setting does not define every contractual retention or deletion window. Use Composio's approved security and privacy documentation for those questions.
docs/content/kb/guide/dashboard-login-restrictions.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Dashboard MFA Setup"
3 -description: "Public guidance for completing dashboard MFA setup."
4 -keywords: ["login-restrictions","platform","authentication","errors-and-troubleshooting","security-and-trust","/kb/dashboard-and-projects/mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails","mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails"]
5 -sources: [{"sourcePath":"dashboard/login-restrictions/public.md","sourceHeading":"Use the manual setup key when QR scanning does not complete"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","security-and-trust"]
10 -aliases: ["/kb/dashboard-and-projects/mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails","mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails"]
11 ----
12 -Use this when a user cannot complete authenticator-app enrollment from the QR
13 -code in Account Settings.
14 -
15 -## Use the manual setup key when QR scanning does not complete
16 -
17 -The MFA setup screen shows a QR code and a **View setup key** option. If the QR
18 -code cannot be scanned or the setup screen expires, open **View setup key** and
19 -enter that key manually in the authenticator app. Then enter the resulting
20 -six-digit passcode in Composio to finish enrollment.
21 -
22 -After enrollment is complete, resetting the setup key requires removing or
23 -resetting the MFA factor and enrolling the authenticator again.
docs/content/kb/guide/dashboard-navigation-overview.mdx deleted
-43
@@ -1,43 +0,0 @@
1 ----
2 -title: "Composio dashboard navigation"
3 -description: "Current navigation map for Composio Platform and Composio For You."
4 -keywords: ["dashboard","for-you","navigation","platform","getting-started","workflows"]
5 -sources: [{"sourcePath":"dashboard/navigation-overview/public.md","sourceHeading":"Choose Platform for developer projects and For You for personal agent connections"},{"sourcePath":"dashboard/navigation-overview/public.md","sourceHeading":"Current Platform project navigation"},{"sourcePath":"dashboard/navigation-overview/public.md","sourceHeading":"Organization and project settings are separate"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["getting-started","workflows"]
10 -aliases: []
11 ----
12 -## Choose Platform for developer projects and For You for personal agent connections
13 -
14 -**Platform** contains developer projects, Playground, project API keys,
15 -toolkits, skills, users, sessions, auth configs, triggers, logs, and project
16 -settings. **For You** connects a person's apps to supported agents and MCP
17 -clients. Resources in one surface do not automatically appear in the other.
18 -
19 -Use the product switcher when a user is looking for a personal app connection
20 -inside Platform or for project resources inside For You.
21 -
22 -## Current Platform project navigation
23 -
24 -The Platform project sidebar contains **Getting Started**, **Playground**,
25 -**API Keys**, **Toolkits**, **Skills**, **Users**, **Sessions**, **Auth Configs**,
26 -**Triggers**, and **Logs**. Pinned destinations include **Support**,
27 -**Documentation**, and **Settings**.
28 -
29 -- Use **Playground** to test a session with selected toolkits, tools, auth
30 - configs, and connected accounts.
31 -- Use **Toolkits** to inspect current toolkit versions, tool and trigger schemas,
32 - and supported auth schemes.
33 -- Use **Users** and **Sessions** to correlate a project user with connections,
34 - executions, and session restrictions.
35 -- Use **Logs** for the request, response, error, version, and Log ID of a tool or
36 - trigger execution.
37 -
38 -## Organization and project settings are separate
39 -
40 -Project settings include **General**, **API Keys**, **Webhooks**, **White
41 -Labeling**, and **Usage**. Organization settings include **General**,
42 -**Members**, **Billing**, **Usage**, and **Account Settings**. Verify the page
43 -heading before changing or deleting a resource.
docs/content/kb/guide/dashboard-org-members.mdx deleted
-66
@@ -1,66 +0,0 @@
1 ----
2 -title: "Organization Members and Roles"
3 -description: "What the Admin, Member (Developer), and Viewer roles can do in Composio For You and Platform, and how to transfer organization control."
4 -keywords: ["dashboard","for-you","members","organizations","permissions","platform","roles","account-and-billing","getting-started","/kb/dashboard-and-projects/transfer-organization-control-to-another-user","transfer-organization-control-to-another-user"]
5 -sources: [{"sourcePath":"dashboard/org-members/public.md","sourceHeading":"What each organization role can do"},{"sourcePath":"dashboard/org-members/public.md","sourceHeading":"Transfer organization control to another user"}]
6 -lastVerifiedAt: "2026-10-13"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["account-and-billing","getting-started"]
10 -aliases: ["/kb/dashboard-and-projects/transfer-organization-control-to-another-user","transfer-organization-control-to-another-user"]
11 ----
12 -## What each organization role can do
13 -
14 -Every member of your organization has one of three roles: **Admin**, **Member**, or **Viewer**. The role applies to the whole organization, so it covers both Composio For You and Platform.
15 -
16 -**Member** and **Developer** are the same role. The For You **Members** settings page calls it **Member**, and the Platform **Team Members** settings page calls it **Developer**. If you change someone's role on either page, it changes in both products.
17 -
18 -Only Admins can manage the organization itself, in both products:
19 -
20 -- Invite people, create invite links, change roles, and remove members.
21 -- Manage billing, plans, and wallet top-ups.
22 -- Rename or delete the organization, and set up SSO.
23 -
24 -### Composio For You
25 -
26 -| Action | Admin | Member | Viewer |
27 -|---|---|---|---|
28 -| Open For You | Yes | Yes | No |
29 -| Connect your own apps | Yes | Yes | No |
30 -| Use connections an admin or teammate shared with the organization | Yes | Yes | No |
31 -| Share one of your connections with the organization | Yes | Yes | No |
32 -| Rename, reconnect, unshare, or delete a shared connection | Only the person who shared it | Only the person who shared it | No |
33 -| Turn Instant Tools on or off for the organization | Yes | No | No |
34 -| See tool logs for the whole organization | Yes | Own activity only | No |
35 -
36 -Viewers can't use For You at all. Give your team the **Member** role if they need to connect their own apps or use shared connections.
37 -
38 -Members only see and manage their own personal connections. Only the person who shared a connection can rename, reconnect, unshare, or delete it. Admins can't change a teammate's shared connection either.
39 -
40 -### Composio Platform
41 -
42 -| Action | Admin | Developer | Viewer |
43 -|---|---|---|---|
44 -| View projects, logs, and settings | Yes | Yes | Yes |
45 -| Connect apps and manage connected accounts in a project | Yes | Yes | No |
46 -| Create, edit, enable, or delete auth configs | Yes | Yes | No |
47 -| Manage triggers, webhook subscriptions, and custom toolkits | Yes | Yes | No |
48 -| Rename a project | Yes | Yes | No |
49 -| Create or delete a project | Yes | No | No |
50 -| Create or revoke project API keys and set IP allowlists | Yes | No | No |
51 -| Change project security settings, such as 2FA, required MCP API keys, data masking, and log visibility | Yes | No | No |
52 -
53 -Developers can build inside existing projects. Ask an Admin to create a project or to issue an API key for it.
54 -
55 -## Transfer organization control to another user
56 -
57 -Transfer organization control by assigning the **Admin** role:
58 -
59 -1. Open **Organization Settings → Team Members**.
60 -2. Invite the new user and assign the **Admin** role.
61 -3. Have the new user accept the invitation and sign in.
62 -4. If the previous admin should no longer have control, the new admin can lower or remove that person afterward.
63 -
64 -A user cannot normally remove or change their own Team Members row. If the existing administrator cannot access the organization, the invitation or role selector fails, or the change could leave the organization without an administrator, contact support.
65 -
66 -Removing the previous user does not delete the organization, but API keys owned by that removed account can stop working. Rotate or replace those keys before removal when necessary.
docs/content/kb/guide/dashboard-project-settings-navigation.mdx deleted
-32
@@ -1,32 +0,0 @@
1 ----
2 -title: "Platform project settings"
3 -description: "Current navigation for Platform project configuration and organization settings."
4 -keywords: ["dashboard","platform","settings","account-and-billing","authentication","workflows"]
5 -sources: [{"sourcePath":"dashboard/project-settings-navigation/public.md","sourceHeading":"Project settings control one project"},{"sourcePath":"dashboard/project-settings-navigation/public.md","sourceHeading":"Organization settings control the organization"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["account-and-billing","authentication","workflows"]
10 -aliases: []
11 ----
12 -## Project settings control one project
13 -
14 -Open **Platform → Settings** for the selected project. The current project
15 -settings pages are **General**, **API Keys**, **Webhooks**, **White Labeling**,
16 -and **Usage**.
17 -
18 -- **API Keys** creates or revokes project keys and manages any key-level IP
19 - allowlist. Copy a newly created secret into the customer's secret manager;
20 - never ask for it in support.
21 -- **Webhooks** manages the project webhook endpoint and signing secret.
22 -- **White Labeling** controls the hosted authentication screen. Provider OAuth
23 - consent-screen branding still requires the customer's own provider app.
24 -- **Usage** shows project-level usage rather than organization-wide usage.
25 -
26 -## Organization settings control the organization
27 -
28 -The organization settings pages are **General**, **Members**, **Billing**,
29 -**Usage**, and **Account Settings**. Use them for organization identity,
30 -membership, plan and usage information, account security, and organization
31 -deletion. Confirm whether the customer intends to change one project or the
32 -whole organization before directing them to a destructive control.
docs/content/kb/guide/dashboard-tool-trigger-logs-navigation.mdx deleted
-38
@@ -1,38 +0,0 @@
1 ----
2 -title: "Debug Platform tools, triggers, users, and sessions"
3 -description: "Current dashboard paths for inspecting Platform execution state and support identifiers."
4 -keywords: ["dashboard","logs","platform","triggers","errors-and-troubleshooting","sessions-and-execution","workflows"]
5 -sources: [{"sourcePath":"dashboard/tool-trigger-logs-navigation/public.md","sourceHeading":"Use Logs for execution evidence"},{"sourcePath":"dashboard/tool-trigger-logs-navigation/public.md","sourceHeading":"Use Users and Sessions to explain retrieval and execution context"},{"sourcePath":"dashboard/tool-trigger-logs-navigation/public.md","sourceHeading":"Disable a trigger when the goal is to pause it"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","workflows"]
10 -aliases: []
11 ----
12 -## Use Logs for execution evidence
13 -
14 -Open **Platform → Logs** and choose the tool or trigger log view. Filter by the
15 -smallest known non-secret identifier, then open the row to inspect its status,
16 -toolkit, action or trigger, version, user, connection, request/response or
17 -provider error, timing, and correlation IDs.
18 -
19 -Use a **Log ID** for a tool execution, a **Trigger ID** plus Log ID for a
20 -trigger event, and a **Session ID** for session behavior. Never request API
21 -keys, access or refresh tokens, provider client secrets, webhook secrets, or
22 -passwords.
23 -
24 -## Use Users and Sessions to explain retrieval and execution context
25 -
26 -Open **Users** to find a project user and its connected accounts, triggers,
27 -sessions, and filtered logs. Open **Sessions** to inspect session toolkits,
28 -connection behavior, and execution timeline. An active connection elsewhere in
29 -the organization does not prove it was eligible for this session: project,
30 -`user_id`, toolkit restrictions, auth-config selection, and explicit connected
31 -account selection all affect resolution.
32 -
33 -## Disable a trigger when the goal is to pause it
34 -
35 -Open **Triggers** to inspect status and related logs. Disable a trigger when it
36 -should pause temporarily; delete it only when the subscription should be
37 -removed. Before recreating a trigger, verify the selected project, user,
38 -connected account, trigger type, and current provider event support.
docs/content/kb/guide/faqs.mdx deleted
-58
@@ -1,58 +0,0 @@
1 ----
2 -title: "Current Support FAQs"
3 -description: "Public answers for recurring Composio support issues."
4 -keywords: ["faq","faqs","for-you","platform","authentication","errors-and-troubleshooting","security-and-trust","sessions-and-execution","toolkits-and-providers","/kb/sdk-and-api/misc-faqs","misc-faqs","request-a-missing-toolkit-tool-or-trigger","security-privacy-data-retention-and-compliance-information"]
5 -sources: [{"sourcePath":"faqs/public.md","sourceHeading":"Route toolkit requests and toolkit partnership applications"},{"sourcePath":"faqs/public.md","sourceHeading":"Security, privacy, data-retention, and compliance information"},{"sourcePath":"faqs/public.md","sourceHeading":"Security reporting"},{"sourcePath":"faqs/public.md","sourceHeading":"Google `access_not_configured` requires a Workspace for Education administrator"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","security-and-trust","sessions-and-execution","toolkits-and-providers"]
10 -aliases: ["/kb/sdk-and-api/misc-faqs","misc-faqs","request-a-missing-toolkit-tool-or-trigger","security-privacy-data-retention-and-compliance-information"]
11 ----
12 -## Request a toolkit, tool, trigger, or partnership
13 -
14 -The same public request board covers all three request types:
15 -
16 -- a new toolkit or integration;
17 -- a missing tool or action in an existing toolkit;
18 -- a missing trigger or event in an existing toolkit.
19 -
20 -Submit any of these requests at https://request.composio.dev/boards/tool-requests. Include the provider or toolkit, the exact tool/action/API endpoint or trigger/event, and your use case. The request board is the source of truth for status; an ETA is not guaranteed.
21 -
22 -If your company wants its own product added to Composio, apply with a company
23 -work email and product details at https://composio.dev/partnerships#apply. The
24 -public partnership form asks for company, product, and proposed-journey context.
25 -
26 -## Security, privacy, data-retention, and compliance information
27 -
28 -Use https://trust.composio.dev/ for general security, privacy, data-retention, audit, and compliance information. If the Trust Center does not answer your question, contact Composio support. Use the documented Dashboard self-service path for ordinary organization deletion. Report potential vulnerabilities privately through the security-reporting channels below; direct legal requests, data-erasure requests beyond the self-service flow, and account-specific access questions to Composio support.
29 -
30 -## Security reporting
31 -
32 -If you believe you have found a potential security vulnerability in Composio,
33 -please report it privately through the channels in our
34 -[security policy](https://github.com/ComposioHQ/composio/security/policy). A
35 -private GitHub Security Advisory is the preferred route, with
36 -`security@composio.dev` available as an email alternative.
37 -
38 -Include enough detail to help the team reproduce and assess the finding, but do
39 -not include customer data, credentials, or other secrets.
40 -
41 -## Google `access_not_configured` requires a Workspace for Education administrator
42 -
43 -Google documents `400 access_not_configured` as a Workspace for Education app
44 -access-policy error. The institution's Workspace administrator must configure
45 -access for the app; changing Composio scopes or repeatedly reconnecting does not
46 -resolve that policy decision.
47 -
48 -If the organization allows users to request access, the user can submit the
49 -request from Google's error page. An administrator with the required Security
50 -settings privilege can review pending requests or configure the exact OAuth
51 -client under **Security → Access and data control → API controls → Manage
52 -App Access**. The administrator should use the access level and organizational
53 -unit appropriate for the institution. Google says policy changes can take up to
54 -24 hours, though they usually apply sooner.
55 -
56 -Do not generalize this code to every Google Workspace account. Distinguish it
57 -from `admin_policy_enforced`, `access_denied`, and unverified-app errors before
58 -giving instructions.
docs/content/kb/guide/mcp-mcp-hermes.mdx deleted
-33
@@ -1,33 +0,0 @@
1 ----
2 -title: "Hermes MCP"
3 -description: "Public support knowledge for Hermes MCP."
4 -keywords: ["for-you","mcp","mcp-hermes","platform","auth-config","authentication","errors-and-troubleshooting","getting-started","sessions-and-execution","/kb/tool-router-and-mcp/mcp-mcp-hermes","auth-configs-are-project-scoped","production-mcp-api-paths-and-direct-transport-tests"]
5 -sources: [{"sourcePath":"mcp/mcp-hermes/public.md","sourceHeading":"Production MCP API paths and direct transport tests"},{"sourcePath":"mcp/mcp-hermes/public.md","sourceHeading":"Auth configs are project-scoped"}]
6 -lastVerifiedAt: "2026-11-10"
7 -reviewAfter: "2027-02-08"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","getting-started","sessions-and-execution"]
10 -aliases: ["/kb/tool-router-and-mcp/mcp-mcp-hermes","auth-configs-are-project-scoped","production-mcp-api-paths-and-direct-transport-tests"]
11 ----
12 -Use these checks to troubleshoot Composio MCP connection failures in Hermes / Nous Hermes Agent.
13 -
14 -## Production MCP API paths and direct transport tests
15 -
16 -**Warning:** For consumer connections, use `https://connect.composio.dev/mcp`, not this URL.
17 -
18 -Use HTTPS and the full production API path:
19 -
20 -```text
21 -https://backend.composio.dev/api/v3.1/mcp/servers
22 -https://backend.composio.dev/api/v3.1/mcp/<mcp_server_id>
23 -```
24 -
25 -Pass the Project API key in `x-api-key`. Avoid an HTTP URL, staging hosts, or a trailing slash on `/servers`, which can produce redirects. For a no-auth server, still pass `auth_config_ids: []` explicitly with `no_auth_apps`.
26 -
27 -When testing the returned MCP transport directly, include the Project API key, either `user_id` or `connected_account_id`, and `Accept: application/json, text/event-stream`. A redirect from the returned URL to the current Streamable HTTP endpoint is expected when the client follows it.
28 -
29 -## Auth configs are project-scoped
30 -
31 -A hosted For You/consumer MCP session cannot reuse a custom auth config created in a separate Platform developer project. The session resolves configs only in its own project.
32 -
33 -For a customer-created Platform Tool Router session, bind a same-project config with its real `ac_*` ID. A display name is not the auth-config ID, and cross-project binding is unsupported.
docs/content/kb/guide/mcp-tool-router-files.mdx deleted
-24
@@ -1,24 +0,0 @@
1 ----
2 -title: "Tool Router Files"
3 -description: "Public guidance for passing Tool Router session files to toolkit actions."
4 -keywords: ["files","for-you","mcp","platform","tool-router","uploads","errors-and-troubleshooting","sessions-and-execution","/kb/tool-router-and-mcp/use-tool-router-session-files-as-tool-inputs","use-tool-router-session-files-as-tool-inputs"]
5 -sources: [{"sourcePath":"mcp/tool-router-files/public.md","sourceHeading":"Session paths are not `FileUploadable` storage keys"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/tool-router-and-mcp/use-tool-router-session-files-as-tool-inputs","use-tool-router-session-files-as-tool-inputs"]
11 ----
12 -## Session paths are not `FileUploadable` storage keys
13 -
14 -Tool Router session files and toolkit `FileUploadable` inputs are different abstractions. Do not pass `/workspace/output/...`, `/mnt/files/...`, a local machine path, or an old/foreign `file_...` handle directly as `s3key`.
15 -
16 -When workbench/meta tools are available:
17 -
18 -- For a file already under `/mnt/files`, use `get_mount_file_s3_key("file.ext")`.
19 -- For another sandbox path, use `upload_local_file("/path/to/file.ext")`.
20 -- Pass the returned key to the toolkit action as `{ "name": "file.ext", "mimetype": "...", "s3key": "<returned key>" }`.
21 -
22 -In SDK/API flows, upload or stage the file first and pass the fresh returned file object.
23 -
24 -If an action reports `Failed to download file with s3key ... storage returned HTTP 404`, it failed while resolving the Composio-staged file, before the provider received it. Re-stage the file and retry with the fresh object.
docs/content/kb/guide/mcp-tool-router-sessions.mdx deleted
-138
@@ -1,138 +0,0 @@
1 ----
2 -title: "Tool Router Sessions"
3 -description: "Public setup guidance for creating and using Tool Router sessions."
4 -keywords: ["for-you","mcp","platform","sessions","tool-router","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","workflows","/kb/tool-router-and-mcp/mcp-tool-router-sessions","choose-a-connected-account-for-a-session","tool-router-session-lifetime-and-deletion","toolkit-is-not-allowed-for-this-session"]
5 -sources: [{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Create Tool Router sessions through the SDK or API"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Session lifetime and deletion"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Select among multiple accounts with an alias or account ID"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"The session user must match the connected-account user"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Connected-account selection is live unless pinned"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Toolkit allowlists are enforced before connection lookup"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"A fresh task context is a new session runtime, not model memory"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Auth links create project- and user-scoped connected accounts"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Toolkit filters do not preload every matching tool"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"SDK custom tools and Custom MCP toolkits have different runtimes"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Enhanced Control requires client support for MCP elicitation"},{"sourcePath":"mcp/tool-router-sessions/public.md","sourceHeading":"Pin the intended auth config when a toolkit has multiple auth schemes"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","workflows"]
10 -aliases: ["/kb/tool-router-and-mcp/mcp-tool-router-sessions","choose-a-connected-account-for-a-session","tool-router-session-lifetime-and-deletion","toolkit-is-not-allowed-for-this-session"]
11 ----
12 -## Create Tool Router sessions through the SDK or API
13 -
14 -There is no normal dashboard toggle required to enable Tool Router. Create a session through the SDK or the REST API.
15 -
16 -- [Quickstart](https://docs.composio.dev/docs/quickstart)
17 -- [Configuring sessions](https://docs.composio.dev/docs/configuring-sessions)
18 -- [Create a Tool Router session API](https://docs.composio.dev/reference/api-reference/tool-router/postToolRouterSession)
19 -
20 -If you receive an actual 403 or an error saying Tool Router is not enabled for the account, do not keep repeating the setup steps. Contact Composio support for account-level checking and include the exact error body plus the request or code snippet.
21 -
22 -## Session lifetime and deletion
23 -
24 -Tool Router sessions are long-lived records and do not currently have a time-based expiration. This is separate from temporary workbench files, live sandbox retention, and short response-cache lifetimes.
25 -
26 -Reuse an existing session with `composio.use(sessionId)` in TypeScript or `composio.use(session_id)` in Python. Delete it with `session.delete()`, or delete by ID:
27 -
28 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
29 -
30 -<Tab value="Python">
31 -```python
32 -composio.sessions.delete("trs_1a2b3c4d5e6f")
33 -```
34 -</Tab>
35 -
36 -<Tab value="TypeScript">
37 -```typescript
38 -import { Composio } from "@composio/core";
39 -
40 -const composio = new Composio();
41 -await composio.sessions.delete("trs_1a2b3c4d5e6f");
42 -```
43 -</Tab>
44 -
45 -<Tab value="API">
46 -```bash
47 -curl -X DELETE https://backend.composio.dev/api/v3.1/tool_router/session/trs_1a2b3c4d5e6f \
48 - -H "x-api-key: $COMPOSIO_API_KEY"
49 -```
50 -</Tab>
51 -
52 -</Tabs>
53 -
54 -
55 -
56 -Deletion takes effect immediately. A deleted, missing, or inaccessible session returns 404 when retrieved; deleting a session does not delete its users, auth configs, or connected accounts.
57 -
58 -## Select among multiple accounts with an alias or account ID
59 -
60 -When a toolkit has multiple connected accounts, assign clear aliases such as `work`, `personal`, or `primary`, then pass the alias as the execution `account`. Without an alias, use the generated account ID returned by connection discovery.
61 -
62 -Do not rely on fuzzy phrases such as “office email” unless a matching alias exists. If explicit account selection is disabled and no `account` is supplied, the session can fall back to its first/default account.
63 -
64 -## The session user must match the connected-account user
65 -
66 -An account can be active in the dashboard but unavailable to Tool Router when the session uses a different `user_id`. Private accounts resolve for their owning user; explicitly shared or pinned accounts follow the session configuration.
67 -
68 -Create the session and connection with the same stable user ID. If a particular account must be used, pass its allowed connected-account override in the session configuration.
69 -
70 -## Connected-account selection is live unless pinned
71 -
72 -When `connectedAccounts` is omitted, Tool Router resolves currently active accounts for the session user at execution time, including accounts connected after session creation. When `connectedAccounts` is supplied, it is an exact toolkit override and Tool Router does not fall back to another active account for that toolkit.
73 -
74 -Adding another account later does not change an explicit pin. Update or recreate the session when the pinned account should change; omit the override when you want live account discovery.
75 -
76 -## Toolkit allowlists are enforced before connection lookup
77 -
78 -When a session has a non-empty `toolkits.enabled` list, every other toolkit is blocked. A `toolkits.disabled` list does the inverse: listed toolkits are blocked while the rest remain eligible. This restriction is checked before auth configs and connected accounts.
79 -
80 -If Tool Router reports `[Session Restriction] Toolkit '<name>' is not allowed`, update or recreate the session's toolkit configuration first. Only then debug whether that toolkit has an auth config and connection.
81 -
82 -## A fresh task context is a new session runtime, not model memory
83 -
84 -Every `create()` call returns a new session ID. A session scopes the user,
85 -toolkit and tool access, auth and account selection, and session runtime
86 -resources such as sandbox files. It is not the model's conversation memory.
87 -
88 -Reuse a stored session with `composio.use(sessionId)` when a conversation or
89 -workflow should retain the same session configuration and runtime context.
90 -Create a new session for a different user or materially different setup. A new
91 -session for the same user can still resolve that user's eligible connected
92 -accounts, but it does not inherit the old session's sandbox state.
93 -
94 -## Auth links create project- and user-scoped connected accounts
95 -
96 -`session.authorize()` and `COMPOSIO_MANAGE_CONNECTIONS` create a Connect Link
97 -for the session user and selected auth config. After authentication, the
98 -connected account belongs to that project/user rather than only to the session
99 -that produced the link. Later unpinned sessions for the same stable user can
100 -resolve it; an explicit connected-account pin remains unchanged until the
101 -session is updated or recreated.
102 -
103 -## Toolkit filters do not preload every matching tool
104 -
105 -By default, a session exposes meta tools that discover and load app tools at
106 -runtime. Enabling a toolkit limits what the session can discover and execute;
107 -it does not put every tool from that toolkit into the initial schema set.
108 -
109 -Use an explicit `preload.tools` list when the agent must receive known tools
110 -directly. Use the direct-tools preset or `preload.tools = "all"` only with a
111 -narrow positive filter; broad preload sets are capped and increase agent
112 -context.
113 -
114 -## SDK custom tools and Custom MCP toolkits have different runtimes
115 -
116 -An SDK-defined custom tool runs inside the customer's application process. Its
117 -function body is not uploaded into Composio and is not automatically callable
118 -from a remote session MCP URL or Remote Workbench.
119 -
120 -To expose customer-owned functionality remotely, host it as an MCP server and
121 -register it as a Custom MCP toolkit. The resulting remote tools remain subject
122 -to the session's toolkit and connection restrictions.
123 -
124 -## Enhanced Control requires client support for MCP elicitation
125 -
126 -For You's Enhanced Control approval flow relies on MCP elicitation. It works
127 -only with clients that advertise and implement that capability. If a client
128 -does not support elicitation, use a supported client, set an applicable
129 -**Always Allow** policy, or disable Enhanced Control under **For You → Settings
130 -→ General** and reconnect the client.
131 -
132 -## Pin the intended auth config when a toolkit has multiple auth schemes
133 -
134 -Tool Router first uses the auth config explicitly mapped in the session. When
135 -the toolkit supports multiple schemes, map the intended `ac_...` ID rather than
136 -depending on automatic selection. The selected config must belong to the same
137 -project and be enabled for Tool Router. An explicit connected-account override
138 -is an exact toolkit selection and does not fall back to another active account.
docs/content/kb/guide/meta.json deleted
-128
@@ -1,128 +0,0 @@
1 -{
2 - "title": "Guides",
3 - "pages": [
4 - "consumer-project-boundaries-and-auth-selection",
5 - "dashboard-account-deletion",
6 - "dashboard-auth-configs-navigation",
7 - "dashboard-for-you-navigation",
8 - "dashboard-log-storage",
9 - "dashboard-login-restrictions",
10 - "dashboard-navigation-overview",
11 - "dashboard-org-members",
12 - "dashboard-project-settings-navigation",
13 - "dashboard-tool-trigger-logs-navigation",
14 - "faqs",
15 - "mcp-mcp-hermes",
16 - "mcp-tool-router-files",
17 - "mcp-tool-router-sessions",
18 - "platform-connected-accounts",
19 - "platform-custom-connection-data-fields",
20 - "platform-file-storage",
21 - "platform-google-oauth",
22 - "platform-microsoft-oauth",
23 - "platform-pagination",
24 - "platform-production-readiness",
25 - "platform-project-api-key-permissions",
26 - "platform-rate-limits",
27 - "platform-routing",
28 - "platform-self-hosted-helm",
29 - "platform-session-tool-policies",
30 - "platform-tool-router-workbench",
31 - "platform-triggers",
32 - "sdk-tool-execution-retries",
33 - "sdk-tool-schemas",
34 - "toolkits-ahrefs",
35 - "toolkits-airtable",
36 - "toolkits-apollo",
37 - "toolkits-asana",
38 - "toolkits-attio",
39 - "toolkits-browser-tool",
40 - "toolkits-calendly",
41 - "toolkits-canva",
42 - "toolkits-canvas",
43 - "toolkits-clickup",
44 - "toolkits-confluence",
45 - "toolkits-databricks",
46 - "toolkits-digital-ocean",
47 - "toolkits-discord",
48 - "toolkits-discordbot",
49 - "toolkits-docusign",
50 - "toolkits-dropbox",
51 - "toolkits-excel",
52 - "toolkits-facebook",
53 - "toolkits-fathom",
54 - "toolkits-figma",
55 - "toolkits-firecrawl",
56 - "toolkits-gemini",
57 - "toolkits-github",
58 - "toolkits-gmail",
59 - "toolkits-gong",
60 - "toolkits-google-analytics",
61 - "toolkits-google-calendar",
62 - "toolkits-google-classroom",
63 - "toolkits-google-maps",
64 - "toolkits-googleads",
65 - "toolkits-googlebigquery",
66 - "toolkits-googledocs",
67 - "toolkits-googledrive",
68 - "toolkits-googlemeet",
69 - "toolkits-googlesheets",
70 - "toolkits-googleslides",
71 - "toolkits-googlesuper",
72 - "toolkits-googletasks",
73 - "toolkits-granola-mcp",
74 - "toolkits-hubspot",
75 - "toolkits-instagram",
76 - "toolkits-intercom",
77 - "toolkits-jira",
78 - "toolkits-kickbox",
79 - "toolkits-klaviyo",
80 - "toolkits-kommo",
81 - "toolkits-launch-darkly",
82 - "toolkits-linear",
83 - "toolkits-linkedin",
84 - "toolkits-mailchimp",
85 - "toolkits-marketstack",
86 - "toolkits-microsoft-teams",
87 - "toolkits-monday",
88 - "toolkits-netsuite",
89 - "toolkits-notion",
90 - "toolkits-odoo",
91 - "toolkits-one-drive",
92 - "toolkits-onenote",
93 - "toolkits-openai",
94 - "toolkits-outlook",
95 - "toolkits-perplexityai",
96 - "toolkits-pipedrive",
97 - "toolkits-posthog",
98 - "toolkits-quickbooks",
99 - "toolkits-reddit",
100 - "toolkits-salesforce",
101 - "toolkits-serpapi",
102 - "toolkits-servicenow",
103 - "toolkits-sharepoint",
104 - "toolkits-shopify",
105 - "toolkits-slack",
106 - "toolkits-slackbot",
107 - "toolkits-snapchat",
108 - "toolkits-snowflake",
109 - "toolkits-spotify",
110 - "toolkits-stripe",
111 - "toolkits-supabase",
112 - "toolkits-tavily",
113 - "toolkits-tiktok",
114 - "toolkits-trello",
115 - "toolkits-twitter",
116 - "toolkits-webflow",
117 - "toolkits-whatsapp",
118 - "toolkits-wrike",
119 - "toolkits-xero",
120 - "toolkits-ynab",
121 - "toolkits-youtube",
122 - "toolkits-zendesk",
123 - "toolkits-zoho-books",
124 - "toolkits-zoho-mail",
125 - "toolkits-zoho",
126 - "toolkits-zoom"
127 - ]
128 -}
docs/content/kb/guide/platform-connected-accounts.mdx deleted
-65
@@ -1,65 +0,0 @@
1 ----
2 -title: "Connected Accounts"
3 -description: "Public support knowledge for Connected Accounts."
4 -keywords: ["connected-accounts","platform","authentication","errors-and-troubleshooting","/kb/sdk-and-api/platform-connected-accounts","connection-status-describes-a-lifecycle-not-credential-validity","oauth-refresh-failures-have-multiple-causes","public-refresh-endpoint-starts-a-new-auth-flow","same-user-id-does-not-prove-same-upstream-account","token-based-connections-are-not-always-validated-when-stored"]
5 -sources: [{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Prefer a new auth link session when a user must reconnect"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Same user ID does not prove same upstream account"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Hosted connect links expire after 10 minutes"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Connection status describes a lifecycle, not credential validity"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"OAuth refresh failures have multiple causes"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Provider tokens are redacted from connected-account responses"},{"sourcePath":"platform/connected-accounts/public.md","sourceHeading":"Revoke provider credentials before removing a connection when required"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting"]
10 -aliases: ["/kb/sdk-and-api/platform-connected-accounts","connection-status-describes-a-lifecycle-not-credential-validity","oauth-refresh-failures-have-multiple-causes","public-refresh-endpoint-starts-a-new-auth-flow","same-user-id-does-not-prove-same-upstream-account","token-based-connections-are-not-always-validated-when-stored"]
11 ----
12 -Use this for Composio connected-account status, refresh, and identity debugging.
13 -
14 -## Prefer a new auth link session when a user must reconnect
15 -
16 -Create a new auth link session when a user must authenticate again. Redirect the user to the returned hosted link and wait for the resulting connected account to become active. The older `POST /connected_accounts/{nanoid}/refresh` re-initiation endpoint is deprecated; it did not perform Composio's internal background token refresh.
17 -
18 -If the user completes that auth flow successfully, the connected account can return to `ACTIVE`.
19 -
20 -Example response:
21 -
22 -```text
23 -This starts a new authentication flow. For OAuth connections, the user must open the hosted link and complete provider consent. Once the OAuth flow succeeds, use the newly active connected account.
24 -```
25 -
26 -## Same user ID does not prove same upstream account
27 -
28 -Do not assume multiple connected accounts under the same `clientUniqueUserId` are duplicates of the same upstream account. A single Composio user ID can legitimately connect personal, work, and business accounts.
29 -
30 -If the root-cause hypothesis depends on repeated reconnects to the same upstream Google/Microsoft/etc. account, verify the upstream identity first. Use a safe profile/current-user action for each connected account, customer-provided labels, or another non-sensitive identity signal.
31 -
32 -## Hosted connect links expire after 10 minutes
33 -
34 -A hosted connect link/session is short-lived. If the initial authentication flow is not completed within 10 minutes, the link can show wording such as “We couldn't verify the session associated with the link” or “Validation error while processing request.” The dashboard may briefly continue to show the connection as initializing.
35 -
36 -Generate a fresh connect link for the same user and open it immediately. If the new link also fails immediately, contact Composio support with its generation timestamp and the exact error. Do not keep retrying an older link.
37 -
38 -## Connection status describes a lifecycle, not credential validity
39 -
40 -- `INITIALIZING`: the connection row and hosted flow were created.
41 -- `INITIATED`: the user opened or advanced the authentication flow.
42 -- `ACTIVE`: the connection flow completed and its credential data was stored.
43 -- `EXPIRED`: the flow timed out or the connection can no longer refresh/use its authorization. Read `statusReason` to distinguish those cases.
44 -
45 -`Connection initiation did not complete within 10 minutes` means the original flow timed out; it is not a background token-refresh failure. Generate a fresh link and wait for `ACTIVE` before treating its connected-account ID as usable.
46 -
47 -## OAuth refresh failures have multiple causes
48 -
49 -An OAuth connection may expire when the provider rejects its refresh token, the user or admin revokes the app, provider security policy invalidates the grant, a rotating-token chain is interrupted, or customer-owned OAuth credentials change. Reconnecting obtains a new grant. If connections repeatedly expire across users, contact Composio support with redacted connection IDs and timestamps instead of repeatedly reconnecting.
50 -
51 -## Provider tokens are redacted from connected-account responses
52 -
53 -Connected-account APIs do not return raw access or refresh tokens. Use Composio
54 -tool execution or [Proxy Execute](https://docs.composio.dev/docs/proxy-execute)
55 -when a workflow needs to call a provider API through an existing connection. Do
56 -not build a workflow that depends on reading provider tokens from connected-
57 -account data.
58 -
59 -## Revoke provider credentials before removing a connection when required
60 -
61 -Use the connected-account revoke operation when the toolkit supports
62 -programmatic provider revocation. When provider-side revocation is unavailable,
63 -remove Composio's access in the provider's connected-app settings or rotate the
64 -API key in the provider dashboard. Never send access tokens, refresh tokens, API
65 -keys, or private-key material to Composio support.
docs/content/kb/guide/platform-custom-connection-data-fields.mdx deleted
-82
@@ -1,82 +0,0 @@
1 ----
2 -title: "Custom Connection Data Field Names"
3 -description: "Public support knowledge for Custom Connection Data Field Names."
4 -keywords: ["custom-connection-data-fields","platform","authentication","errors-and-troubleshooting","sessions-and-execution","/kb/authentication/custom-connection-data-fields-are-toolkit-specific","custom-connection-data-fields-are-toolkit-specific"]
5 -sources: [{"sourcePath":"platform/custom-connection-data-fields/public.md","sourceHeading":"Field names are toolkit-specific"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/authentication/custom-connection-data-fields-are-toolkit-specific","custom-connection-data-fields-are-toolkit-specific"]
11 ----
12 -Use this when a customer creates a custom/API-key style connected account and tool execution fails with `No authentication provided`, 401/403 provider errors, or a provider-specific auth error even though the credential itself works directly against the upstream API.
13 -
14 -## Field names are toolkit-specific
15 -
16 -Do not assume every API-key or bearer-token toolkit accepts `custom_connection_data.val.api_key`. The required field name is toolkit-specific. For example, this shape is incorrect for Crowdin:
17 -
18 -```json
19 -{
20 - "val": {
21 - "api_key": "<token>"
22 - }
23 -}
24 -```
25 -
26 -Crowdin expected:
27 -
28 -```json
29 -{
30 - "val": {
31 - "bearer_token": "<token>"
32 - }
33 -}
34 -```
35 -
36 -To verify the required field names, inspect toolkit metadata:
37 -
38 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
39 -
40 -<Tab value="Python">
41 -```python
42 -toolkit = composio.toolkits.get("crowdin")
43 -print(toolkit.auth_config_details)
44 -```
45 -</Tab>
46 -
47 -<Tab value="TypeScript">
48 -```typescript
49 -import { Composio } from "@composio/core";
50 -
51 -const composio = new Composio();
52 -const toolkit = await composio.toolkits.get("crowdin");
53 -console.log(toolkit.authConfigDetails);
54 -```
55 -</Tab>
56 -
57 -<Tab value="API">
58 -```bash
59 -curl --location 'https://backend.composio.dev/api/v3.1/toolkits/crowdin' \
60 - --header "x-api-key: $COMPOSIO_API_KEY"
61 -```
62 -
63 -Look under:
64 -
65 -```text
66 -auth_config_details[].fields.connected_account_initiation.required
67 -```
68 -
69 -If the mismatch continues, share a request ID or log ID with Composio support. If no request ID is available, share how `custom_connection_data` is being constructed, with secrets removed.
70 -
71 -Example response:
72 -
73 -```text
74 -Could you share the `custom_connection_data` shape you're sending, with the secret value removed?
75 -
76 -The field name is toolkit-specific. For example, some toolkits expect `bearer_token` rather than `api_key`. We can verify the required field from the toolkit metadata and make sure the credential is landing in the right field.
77 -```
78 -</Tab>
79 -
80 -</Tabs>
81 -
82 -
docs/content/kb/guide/platform-file-storage.mdx deleted
-18
@@ -1,18 +0,0 @@
1 ----
2 -title: "File Download Storage and Expiry"
3 -description: "Public guidance for staged files, signed download URLs, retention, and size questions."
4 -keywords: ["files","platform","signed-urls","storage","errors-and-troubleshooting","sessions-and-execution","/kb/sdk-and-api/composio-file-urls-are-short-lived-staged-downloads","composio-file-urls-are-short-lived-staged-downloads"]
5 -sources: [{"sourcePath":"platform/file-storage/public.md","sourceHeading":"Composio file URLs are short-lived staged downloads"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/sdk-and-api/composio-file-urls-are-short-lived-staged-downloads","composio-file-urls-are-short-lived-staged-downloads"]
11 ----
12 -## Composio file URLs are short-lived staged downloads
13 -
14 -When a hosted tool returns a file URL such as `data.file.s3url`, Composio normally stages the bytes in Composio-managed object storage and returns a signed download URL rather than the provider's original URL.
15 -
16 -The default signed-URL lifetime is one hour. Organization admins can change it to any duration from 1 second to 24 hours in [**Project Settings > General**](https://dashboard.composio.dev/~/project/settings/general?utm_source=docs&utm_medium=content&utm_campaign=platform-file-storage) under **Configuration > File download link expiry**. Staged files are cleaned up after 24 hours. URL expiry and file cleanup are separate: rerun the tool or download the file again to obtain a fresh URL.
17 -
18 -There is no single customer-facing maximum that applies to every tool. Provider limits, the action implementation, runtime memory, and timeouts can impose lower limits, so check the exact action before quoting a hard cap.
docs/content/kb/guide/platform-google-oauth.mdx deleted
-36
@@ -1,36 +0,0 @@
1 ----
2 -title: "Google OAuth setup and consent"
3 -description: "Shared OAuth setup and consent guidance for Google toolkits."
4 -keywords: ["for-you","google","oauth","platform","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"platform/google-oauth/public.md","sourceHeading":"An unapproved Google OAuth scope can block consent"},{"sourcePath":"platform/google-oauth/public.md","sourceHeading":"A customer-owned OAuth app controls the provider consent-screen brand"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -aliases: []
11 ----
12 -## An unapproved Google OAuth scope can block consent
13 -
14 -Google can block sign-in when an OAuth app requests a sensitive or restricted
15 -scope that is not approved for that app. Use the scopes already available on
16 -the selected Composio auth config, or create a customer-owned Google OAuth app
17 -and complete Google's required verification before requesting additional
18 -scopes. After changing scopes, create a fresh connection so the user grants the
19 -new scope set.
20 -
21 -Google's current verification requirements are documented in its
22 -[OAuth 2.0 policies](https://developers.google.com/identity/protocols/oauth2/policies)
23 -and [sensitive-scope verification guide](https://developers.google.com/identity/protocols/oauth2/production-readiness/sensitive-scope-verification).
24 -
25 -## A customer-owned OAuth app controls the provider consent-screen brand
26 -
27 -Use a customer-owned Google OAuth app when the Google consent screen should
28 -show the customer's app name and branding. A callback forwarder on the
29 -customer's domain still redirects the browser to Composio; it does not hide
30 -Composio's domain. The forwarding endpoint receives the authorization code and
31 -state, so its query string must not be logged. See
32 -[callback-domain limits](/docs/authentication/white-labeling-authentication#routing-the-callback-through-your-domain).
33 -
34 -The OAuth app's authorized redirect URI must still match the callback URI
35 -shown by Composio. Provider consent-screen branding and the URL to which the
36 -customer's application sends a user after authentication are separate settings.
docs/content/kb/guide/platform-microsoft-oauth.mdx deleted
-37
@@ -1,37 +0,0 @@
1 ----
2 -title: "Microsoft OAuth scopes and tenant consent"
3 -description: "Shared OAuth scope and tenant-consent guidance for Microsoft toolkits."
4 -keywords: ["for-you","microsoft","oauth","platform","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"platform/microsoft-oauth/public.md","sourceHeading":"Request `offline_access` when a delegated connection needs refresh tokens"},{"sourcePath":"platform/microsoft-oauth/public.md","sourceHeading":"Some Microsoft tenant policies and permissions require administrator consent"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -aliases: []
11 ----
12 -## Request `offline_access` when a delegated connection needs refresh tokens
13 -
14 -Microsoft's v2 OAuth endpoint requires an explicit `offline_access` request to
15 -return refresh tokens. Composio's standard Microsoft delegated OAuth scope sets
16 -include it. For a customer-owned Microsoft app, include `offline_access` in the
17 -app and Composio auth-config scopes before creating a new connection.
18 -
19 -Microsoft documents this behavior in
20 -[Scopes and permissions in the Microsoft identity platform](https://learn.microsoft.com/en-us/entra/identity-platform/scopes-oidc#the-offline_access-scope).
21 -
22 -## Some Microsoft tenant policies and permissions require administrator consent
23 -
24 -A work or school account can show **Needs Admin Approval** or **Admin approval
25 -required** when the tenant prevents users from approving the app or when the
26 -requested permission is administrator-restricted. A tenant administrator must
27 -approve the selected Composio-managed app or the customer's own app and its
28 -requested permissions. The affected user should then start a fresh connection.
29 -
30 -Adding a permission to an Entra app registration does not itself grant tenant
31 -consent. Microsoft explains the distinction in its
32 -[permissions and consent overview](https://learn.microsoft.com/en-us/entra/identity-platform/permissions-consent-overview).
33 -
34 -This guidance applies across Microsoft toolkits that use delegated Microsoft
35 -OAuth, including Outlook, Microsoft Teams, OneDrive, OneNote, Excel, Power BI,
36 -and Dynamics 365. SharePoint REST and app-only/S2S flows may
37 -also require resource-specific permissions and administrator consent.
docs/content/kb/guide/platform-pagination.mdx deleted
-20
@@ -1,20 +0,0 @@
1 ----
2 -title: "Platform Pagination"
3 -description: "Public guidance for endpoint-specific list limits and cursor pagination."
4 -keywords: ["api","cursors","pagination","platform","auth-config","errors-and-troubleshooting","sessions-and-execution","/kb/authentication/auth-config-list-pages-return-at-most-50-items","/kb/sdk-and-api/pagination-limits-are-endpoint-specific","auth-config-list-pages-return-at-most-50-items","pagination-limits-are-endpoint-specific"]
5 -sources: [{"sourcePath":"platform/pagination/public.md","sourceHeading":"Pagination limits are endpoint-specific"},{"sourcePath":"platform/pagination/public.md","sourceHeading":"Auth-config list pages return at most 50 items"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/authentication/auth-config-list-pages-return-at-most-50-items","/kb/sdk-and-api/pagination-limits-are-endpoint-specific","auth-config-list-pages-return-at-most-50-items","pagination-limits-are-endpoint-specific"]
11 ----
12 -## Pagination limits are endpoint-specific
13 -
14 -Composio does not have one global page-size limit. Resource lists, catalogs, Tool Router, logs, and billing endpoints can define different limits, while toolkit actions also inherit provider-specific rules. Check the exact endpoint schema and live behavior before quoting a maximum.
15 -
16 -## Auth-config list pages return at most 50 items
17 -
18 -`GET /api/v3/auth_configs` and `GET /api/v3.1/auth_configs` currently return at most 50 auth configs per page. Read `next_cursor` from each response and pass it as `cursor` until it is empty.
19 -
20 -Some generated descriptions may advertise a larger limit; the deployed endpoint still clamps the page to 50. Treat that documentation/runtime mismatch as a product issue, not as a reason to skip cursor pagination.
docs/content/kb/guide/platform-production-readiness.mdx deleted
-76
@@ -1,76 +0,0 @@
1 ----
2 -title: "Move a Composio Integration from Prototype to Production"
3 -description: "Public guidance for production user identity, environment isolation, authentication, sessions, and trigger delivery."
4 -keywords: ["authentication","deployment","platform","production","projects","sessions","users","auth-config","authentication","getting-started","security-and-trust","sessions-and-execution","workflows"]
5 -sources: [{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Replace example user IDs with stable application user IDs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Isolate environments with separate Composio projects when needed"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Use managed auth in production, and your own OAuth app when you need dedicated limits"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Restrict the production session to the capabilities the agent needs"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Reuse a stored session until the user or configuration changes"},{"sourcePath":"platform/production-readiness/public.md","sourceHeading":"Test production trigger handling through the real webhook path"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","getting-started","security-and-trust","sessions-and-execution","workflows"]
10 -aliases: []
11 ----
12 -## Replace example user IDs with stable application user IDs
13 -
14 -Create sessions and connected accounts with a stable identifier from the
15 -application database, such as a UUID or primary key. Do not use an email
16 -address that can change, and never use `default` in production. Composio uses
17 -the user ID to isolate connections and tool calls, so each application user
18 -must resolve to the same Composio user ID across sessions.
19 -
20 -- [Authentication and user IDs](https://docs.composio.dev/docs/authentication)
21 -- [How Composio sessions work](https://docs.composio.dev/docs/how-composio-works)
22 -
23 -## Isolate environments with separate Composio projects when needed
24 -
25 -A Composio project scopes its API keys, connected accounts, auth configs, and
26 -webhooks. Use separate projects for development, staging, and production when
27 -those resources must not overlap. Use the API key for the intended project in
28 -each deployment, and create environment-specific auth configs when the OAuth
29 -apps, scopes, or provider credentials differ.
30 -
31 -- [Composio glossary: Project](https://docs.composio.dev/reference/glossary#project)
32 -- [Configure authentication](https://docs.composio.dev/docs/tools-direct/authenticating-tools)
33 -
34 -## Use managed auth in production, and your own OAuth app when you need dedicated limits
35 -
36 -Composio-managed OAuth apps work in production. Because the OAuth app is shared,
37 -you may run into shared provider rate limits as your usage grows. For higher
38 -volume, we recommend a custom auth config with your own OAuth app. It also gives
39 -you your application's OAuth brand, custom scopes, a dedicated provider quota,
40 -different polling requirements, and custom instances.
41 -Both options keep connected-account credential storage and refresh in Composio.
42 -Pass the resulting auth config ID to the session; creating the config alone
43 -does not make the session use it.
44 -
45 -- [Managed vs custom auth](https://docs.composio.dev/docs/authentication/custom-app-vs-managed-app)
46 -- [Controlling OAuth scopes](https://docs.composio.dev/docs/authentication/controlling-scopes)
47 -
48 -## Restrict the production session to the capabilities the agent needs
49 -
50 -Set toolkit, tool, and behavior-tag filters when creating the session. For a
51 -sensitive or deterministic workflow, prefer an explicit allowlist of exact
52 -tool slugs. For a broader read-only agent, filter on `readOnlyHint` and disable
53 -`destructiveHint`, then inspect the resulting tool set before rollout.
54 -
55 -- [Configure session tool access](https://docs.composio.dev/docs/configuring-sessions)
56 -- [Create read-only and restricted sessions](/kb/guide/platform-session-tool-policies)
57 -
58 -## Reuse a stored session until the user or configuration changes
59 -
60 -Store the session ID and restore it with `composio.use(session_id)` instead of
61 -creating a new session for every turn. Create a new session for a different
62 -user or a materially different setup, such as a new tool policy or auth-config
63 -mapping. A session preserves its scoped runtime state, but it is not the
64 -language model's conversation memory.
65 -
66 -- [Reuse a session](https://docs.composio.dev/docs/how-composio-works#how-sessions-behave)
67 -
68 -## Test production trigger handling through the real webhook path
69 -
70 -The local `subscribe()` stream is useful for inspecting events, but it bypasses
71 -the production webhook handler and signature verification. Before rollout,
72 -forward events to the real local handler or use a tunnel, verify the signed
73 -payload with `parse()`, and then register the production HTTPS webhook URL for
74 -the production project.
75 -
76 -- [Receive trigger events locally and in production](https://docs.composio.dev/docs/setting-up-triggers/subscribing-to-events)
docs/content/kb/guide/platform-project-api-key-permissions.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Project API Key Permissions"
3 -description: "Public guidance for scoped Project API key permissions."
4 -keywords: ["api-keys","permissions","platform","sessions","tool-router","authentication","errors-and-troubleshooting","sessions-and-execution","/kb/sdk-and-api/platform-project-api-key-permissions","org-api-created-keys-do-not-currently-enable-proxy-execute","tool-router-session-creation-requires-sessions-write-access"]
5 -sources: [{"sourcePath":"platform/project-api-key-permissions/public.md","sourceHeading":"Proxy Execute requires an explicitly allowed Project API key"},{"sourcePath":"platform/project-api-key-permissions/public.md","sourceHeading":"Tool Router session creation requires Sessions write access"},{"sourcePath":"platform/project-api-key-permissions/public.md","sourceHeading":"Tool execution requires Tool execution write access"}]
6 -lastVerifiedAt: "2026-08-28"
7 -reviewAfter: "2026-11-26"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/sdk-and-api/platform-project-api-key-permissions","org-api-created-keys-do-not-currently-enable-proxy-execute","tool-router-session-creation-requires-sessions-write-access"]
11 ----
12 -## Proxy Execute requires an explicitly allowed Project API key
13 -
14 -Create a scoped Project API key in the Dashboard and enable **Proxy Execute**
15 -during key creation before calling the v3.1 Proxy Execute API. If a request is
16 -denied, verify the key's scope before debugging the provider connection. Use a
17 -fresh request ID from the correctly scoped key when contacting Composio support is still necessary.
18 -
19 -## Tool Router session creation requires Session management write access
20 -
21 -For scoped Project API keys, creating a session through `composio.sessions.create(...)` or `POST /api/v3.1/tool_router/session` requires the Session management permission with write or read/write access.
22 -
23 -A key can successfully call `GET /api/v3.1/toolkits` with Toolkits read access and still be unable to create a session. The SDK can surface a scoped-permission denial as a generic 401 `Invalid API key`.
24 -
25 -Create a scoped Project API key with Session management set to Write only, then retry session creation.
26 -
27 -## Tool execution requires Tool execution write access
28 -
29 -For a scoped Project API key, `composio.tools.execute()` and the tool-execute API require Tool execution set to Write or Read and write. A key without that permission can surface a generic 401 `Invalid API key` even when the key exists and is active.
30 -
31 -Create a correctly scoped Project API key or use an appropriate full-access Project API key, then retry. The current API may return a generic permission error, so diagnose this behavior from the key's permissions.
32 -
33 -## Session tool execution requires write access
34 -
35 -Set **Session tool execution** to Write to search and execute tools through a session or its MCP server. This permission allows the key to invoke any tool exposed by the session-linked MCP server. It does not cover session proxy requests; those need **Proxy execute**.
docs/content/kb/guide/platform-rate-limits.mdx deleted
-18
@@ -1,18 +0,0 @@
1 ----
2 -title: "Platform API Rate Limits"
3 -description: "Public guidance for organization-level Composio API limits and 429 handling."
4 -keywords: ["api","billing","platform","rate-limits","account-and-billing","errors-and-troubleshooting","sessions-and-execution"]
5 -sources: [{"sourcePath":"platform/rate-limits/public.md","sourceHeading":"Organization API limits and 429 handling"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["account-and-billing","errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: []
11 ----
12 -## Organization API limits and 429 handling
13 -
14 -Composio applies a shared API budget per organization across authenticated endpoints. Current published limits are Starter and Hobby: 2,000 requests per minute; Growth: 10,000 per minute; Enterprise: custom. Check the [current rate-limit documentation](https://docs.composio.dev/reference/rate-limits) before quoting a plan limit, and do not describe Enterprise as unlimited.
15 -
16 -Rate-limit responses include remaining/window information, and a 429 includes `Retry-After`. Honor `Retry-After` before retrying. Provider quotas such as Google API limits are separate and can throttle a tool even when the Composio organization has capacity.
17 -
18 -If an upgraded organization still sees its old 2,000-per-minute ceiling, share the error time and response rate-limit headers with support.
docs/content/kb/guide/platform-routing.mdx deleted
-24
@@ -1,24 +0,0 @@
1 ----
2 -title: "Support Routing"
3 -description: "Public routing for hiring, compliance, and toolkit feature requests."
4 -keywords: ["compliance","platform","requests","routing","getting-started","security-and-trust","toolkits-and-providers","/kb/sdk-and-api/dpa-enterprise-data-handling-and-compliance","dpa-enterprise-data-handling-and-compliance"]
5 -sources: [{"sourcePath":"platform/routing/public.md","sourceHeading":"Hiring"},{"sourcePath":"platform/routing/public.md","sourceHeading":"DPA, enterprise data handling, and compliance"},{"sourcePath":"platform/routing/public.md","sourceHeading":"Tool or toolkit feature requests"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["getting-started","security-and-trust","toolkits-and-providers"]
10 -aliases: ["/kb/sdk-and-api/dpa-enterprise-data-handling-and-compliance","dpa-enterprise-data-handling-and-compliance"]
11 ----
12 -Use these routes when a request is not primarily a support or debugging issue.
13 -
14 -## Hiring
15 -
16 -Direct hiring inquiries to Composio's public careers channel.
17 -
18 -## DPA, enterprise data handling, and compliance
19 -
20 -Pro and Enterprise Developer customers can accept the [standard DPA](https://composio.dev/legal/dpa) in Organization Settings > Billing > Data Processing Addendum. Route requests for bespoke data-processing terms or end-to-end contractual no-training requirements to the Enterprise track. See [Compliance, Data Retention, and Model Training](/docs/security/vendor-security-review) for details.
21 -
22 -## Tool or toolkit feature requests
23 -
24 -Submit requests through the [Composio request board](https://request.composio.dev).
docs/content/kb/guide/platform-self-hosted-helm.mdx deleted
-83
@@ -1,83 +0,0 @@
1 ----
2 -title: "Self-hosted Helm"
3 -description: "Public support knowledge for Self-hosted Helm."
4 -keywords: ["platform","self-hosted-helm","authentication","errors-and-troubleshooting","getting-started","/kb/sdk-and-api/platform-self-hosted-helm","apollo-s3-with-irsa-serviceaccount-credentials-needs-no-static-s3-secr","disable-social-login-explicitly-for-self-hosted-deployments"]
5 -sources: [{"sourcePath":"platform/self-hosted-helm/public.md","sourceHeading":"Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys"},{"sourcePath":"platform/self-hosted-helm/public.md","sourceHeading":"Disable social login explicitly for self-hosted deployments"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","getting-started"]
10 -aliases: ["/kb/sdk-and-api/platform-self-hosted-helm","apollo-s3-with-irsa-serviceaccount-credentials-needs-no-static-s3-secr","disable-social-login-explicitly-for-self-hosted-deployments"]
11 ----
12 -Use these checks to troubleshoot Composio self-hosted or on-prem Helm deployments.
13 -
14 -## Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys
15 -
16 -For IRSA / ServiceAccount-based S3 access, `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` should not be populated in the Apollo container. These secret keys are optional. If the keys are removed from `composio-composio-secrets`, Apollo can fall back to the configured pod ServiceAccount / AWS SDK credential chain.
17 -
18 -Do not set placeholder S3 credential values for IRSA deployments. Values such as `dummy-value` or a literal string `null` are treated as credentials and can make S3 pre-signed URLs fail with provider errors such as:
19 -
20 -```text
21 -InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
22 -InvalidToken: The provided token is malformed or otherwise invalid.
23 -```
24 -
25 -For AWS IRSA, configure the Apollo ServiceAccount annotation and object storage backend, then leave static S3 credential secret keys absent:
26 -
27 -```yaml
28 -apollo:
29 - serviceAccount:
30 - enabled: true
31 - name: "composio-apollo"
32 - annotations:
33 - eks.amazonaws.com/role-arn: "arn:aws:iam::<AWS_ACCOUNT_ID>:role/<IAM_ROLE_NAME>"
34 - objectStorage:
35 - backend: "s3"
36 -```
37 -
38 -Debug checks:
39 -
40 -```bash
41 -kubectl exec -n composio deploy/composio-apollo -- env | grep -E "^S3_|^AWS_"
42 -kubectl logs -n composio deploy/composio-apollo --tail=200
43 -```
44 -
45 -If using pod/container credentials, the Helm storage doc says the Kubernetes secret credential section can be skipped. Verify that `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` are not present with dummy/static values in Apollo's runtime environment.
46 -
47 -Example response:
48 -
49 -```text
50 -This looks like Apollo is still receiving static S3 credential env vars, so the AWS SDK is using those instead of falling back to the ServiceAccount/IRSA credentials.
51 -
52 -For IRSA, `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` should be absent from the Apollo container. Those secrets are optional; if you remove those keys from `composio-composio-secrets`, Apollo should use the configured ServiceAccount. Placeholder values like `dummy-value` or literal `null` are treated as real credentials and can cause S3 signing errors such as `InvalidAccessKeyId` or `InvalidToken`.
53 -
54 -The immediate fix is to remove `S3_ACCESS_KEY_ID` and `S3_SECRET_ACCESS_KEY` from `composio-composio-secrets`, then confirm the Apollo pod environment no longer includes those values.
55 -```
56 -
57 -## Disable social login explicitly for self-hosted deployments
58 -
59 -`NEXT_PUBLIC_DISABLE_SOCIAL_LOGIN` controls whether social login buttons such as Google/GitHub appear on the frontend login page. For self-hosted customers that should hide social login, set the Helm values override as a string:
60 -
61 -```yaml
62 -apollo:
63 - nextPublicDisableSocialLogin: "true"
64 -```
65 -
66 -This makes the generated Apollo ConfigMap render an explicit value instead of an empty/null value and should remove repeated ArgoCD diffs immediately.
67 -
68 -Customers can apply the override directly to unblock the deployment.
69 -
70 -Example response:
71 -
72 -~~~text
73 -`NEXT_PUBLIC_DISABLE_SOCIAL_LOGIN` controls whether the Google/GitHub social login buttons show up on the frontend login page. For your setup, I'd set it explicitly to `"true"` in the Helm values override:
74 -
75 -```yaml
76 -apollo:
77 - nextPublicDisableSocialLogin: "true"
78 -```
79 -
80 -This should make the generated Apollo ConfigMap render the explicit value and stop ArgoCD from diffing null vs empty string immediately.
81 -
82 -The override above can be applied directly; no release-specific promise is required.
83 -~~~
docs/content/kb/guide/platform-session-tool-policies.mdx deleted
-220
@@ -1,220 +0,0 @@
1 ----
2 -title: "Create Read-Only and Restricted Composio Sessions"
3 -description: "Public guidance for limiting session tool access with tags, exact tool allowlists, OAuth scopes, and sandbox controls."
4 -keywords: ["least-privilege","oauth-scopes","platform","read-only","sessions","tool-policy","authentication","security-and-trust","sessions-and-execution"]
5 -sources: [{"sourcePath":"platform/session-tool-policies/public.md","sourceHeading":"Filter a broad read-only session with behavior tags"},{"sourcePath":"platform/session-tool-policies/public.md","sourceHeading":"Use exact tool allowlists for the narrowest policy"},{"sourcePath":"platform/session-tool-policies/public.md","sourceHeading":"Combine provider scopes with session tool restrictions"},{"sourcePath":"platform/session-tool-policies/public.md","sourceHeading":"Apply toolkit-specific exceptions without widening every toolkit"},{"sourcePath":"platform/session-tool-policies/public.md","sourceHeading":"Disable the session sandbox when the workflow does not need code execution"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["authentication","security-and-trust","sessions-and-execution"]
10 -aliases: []
11 ----
12 -## Filter a broad read-only session with behavior tags
13 -
14 -Use session-level behavior tags when the agent may discover tools across
15 -multiple toolkits but should only receive tools marked as read-only. The same
16 -filters are enforced when the session executes tools.
17 -
18 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
19 -
20 -<Tab value="Python">
21 -```python
22 -session = composio.sessions.create(
23 - user_id="user_123",
24 - tags={
25 - "enable": ["readOnlyHint"],
26 - "disable": ["destructiveHint"],
27 - },
28 -)
29 -```
30 -</Tab>
31 -
32 -<Tab value="TypeScript">
33 -```typescript
34 -import { Composio } from "@composio/core";
35 -
36 -const composio = new Composio();
37 -const session = await composio.create("user_123", {
38 - tags: {
39 - enable: ["readOnlyHint"],
40 - disable: ["destructiveHint"],
41 - },
42 -});
43 -```
44 -</Tab>
45 -
46 -<Tab value="API">
47 -```bash
48 -curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
49 - -H "x-api-key: $COMPOSIO_API_KEY" \
50 - -H "Content-Type: application/json" \
51 - -d '{"user_id":"user_123","tags":{"enable":["readOnlyHint"],"disable":["destructiveHint"]}}'
52 -```
53 -</Tab>
54 -
55 -</Tabs>
56 -
57 -
58 -
59 -Behavior tags describe tool behavior. Inspect the tools the session exposes
60 -before rollout, especially when a workflow handles sensitive data.
61 -
62 -- [Filter tools by tags](https://docs.composio.dev/docs/configuring-sessions#filtering-tools-by-tags)
63 -
64 -## Use exact tool allowlists for the narrowest policy
65 -
66 -For a workflow with a known set of operations, allow only the exact tool slugs
67 -it requires. An allowlist avoids admitting a newly added tool merely because it
68 -shares a toolkit or behavior tag.
69 -
70 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
71 -
72 -<Tab value="Python">
73 -```python
74 -session = composio.sessions.create(
75 - user_id="user_123",
76 - tools={
77 - "gmail": {"enable": ["GMAIL_FETCH_EMAILS"]},
78 - "github": {"enable": ["GITHUB_GET_AN_ISSUE"]},
79 - },
80 -)
81 -```
82 -</Tab>
83 -
84 -<Tab value="TypeScript">
85 -```typescript
86 -import { Composio } from "@composio/core";
87 -
88 -const composio = new Composio();
89 -const session = await composio.create("user_123", {
90 - tools: {
91 - gmail: { enable: ["GMAIL_FETCH_EMAILS"] },
92 - github: { enable: ["GITHUB_GET_AN_ISSUE"] },
93 - },
94 -});
95 -```
96 -</Tab>
97 -
98 -<Tab value="API">
99 -```bash
100 -curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
101 - -H "x-api-key: $COMPOSIO_API_KEY" \
102 - -H "Content-Type: application/json" \
103 - -d '{"user_id":"user_123","tools":{"gmail":{"enable":["GMAIL_FETCH_EMAILS"]},"github":{"enable":["GITHUB_GET_AN_ISSUE"]}}}'
104 -```
105 -</Tab>
106 -
107 -</Tabs>
108 -
109 -
110 -
111 -- [Enable and disable specific tools](https://docs.composio.dev/docs/configuring-sessions#enabling-or-disabling-specific-tools)
112 -
113 -## Combine provider scopes with session tool restrictions
114 -
115 -OAuth scopes control what the provider grants to a connected account. Session
116 -filters control which Composio tools the agent can discover and execute. Use
117 -both layers for least privilege: request only the provider scopes the use case
118 -needs, then restrict the session to the intended tools.
119 -
120 -Changing an auth config's scopes affects new connections only. Existing users
121 -keep their prior grants until they reconnect. Pass the intended auth config ID
122 -to the session, keyed by toolkit, or the session will not request those scopes.
123 -
124 -- [Control OAuth scopes](https://docs.composio.dev/docs/authentication/controlling-scopes)
125 -- [Select an auth config in a session](https://docs.composio.dev/docs/authentication/custom-app-vs-managed-app#create-a-custom-auth-config)
126 -
127 -## Apply toolkit-specific exceptions without widening every toolkit
128 -
129 -Set a global tag policy and override it only for a named toolkit. This is safer
130 -than relaxing the global policy for the entire session.
131 -
132 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
133 -
134 -<Tab value="Python">
135 -```python
136 -session = composio.sessions.create(
137 - user_id="user_123",
138 - tags=["readOnlyHint"],
139 - tools={
140 - "github": {"tags": {"disable": ["destructiveHint"]}},
141 - "gmail": {"tags": ["readOnlyHint"]},
142 - },
143 -)
144 -```
145 -</Tab>
146 -
147 -<Tab value="TypeScript">
148 -```typescript
149 -import { Composio } from "@composio/core";
150 -
151 -const composio = new Composio();
152 -const session = await composio.create("user_123", {
153 - tags: ["readOnlyHint"],
154 - tools: {
155 - github: { tags: { disable: ["destructiveHint"] } },
156 - gmail: { tags: ["readOnlyHint"] },
157 - },
158 -});
159 -```
160 -</Tab>
161 -
162 -<Tab value="API">
163 -```bash
164 -curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
165 - -H "x-api-key: $COMPOSIO_API_KEY" \
166 - -H "Content-Type: application/json" \
167 - -d '{"user_id":"user_123","tags":["readOnlyHint"],"tools":{"github":{"tags":{"disable":["destructiveHint"]}},"gmail":{"tags":["readOnlyHint"]}}}'
168 -```
169 -</Tab>
170 -
171 -</Tabs>
172 -
173 -
174 -
175 -- [Toolkit-specific tag filters](https://docs.composio.dev/docs/configuring-sessions#filtering-tools-by-tags)
176 -
177 -## Disable the session sandbox when the workflow does not need code execution
178 -
179 -Session tool filters govern app tools. Sessions also include remote sandbox
180 -tools by default. Disable the sandbox for a tightly constrained workflow that
181 -does not need Python, shell, file processing, or remote workbench execution.
182 -
183 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
184 -
185 -<Tab value="Python">
186 -```python
187 -session = composio.sessions.create(
188 - user_id="user_123",
189 - tags=["readOnlyHint"],
190 - sandbox={"enable": False},
191 -)
192 -```
193 -</Tab>
194 -
195 -<Tab value="TypeScript">
196 -```typescript
197 -import { Composio } from "@composio/core";
198 -
199 -const composio = new Composio();
200 -const session = await composio.create("user_123", {
201 - tags: ["readOnlyHint"],
202 - sandbox: { enable: false },
203 -});
204 -```
205 -</Tab>
206 -
207 -<Tab value="API">
208 -```bash
209 -curl -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
210 - -H "x-api-key: $COMPOSIO_API_KEY" \
211 - -H "Content-Type: application/json" \
212 - -d '{"user_id":"user_123","tags":["readOnlyHint"],"workbench":{"enable":false}}'
213 -```
214 -</Tab>
215 -
216 -</Tabs>
217 -
218 -
219 -
220 -- [Disable the session sandbox](https://docs.composio.dev/docs/configuring-sessions#disabling-the-sandbox)
docs/content/kb/guide/platform-tool-router-workbench.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Tool Router Workbench Retention"
3 -description: "Public support knowledge for Tool Router Workbench Retention."
4 -keywords: ["platform","tool-router-workbench","errors-and-troubleshooting","sessions-and-execution","/kb/sdk-and-api/a-fresh-client-label-can-still-reuse-the-same-sandbox","a-fresh-client-label-can-still-reuse-the-same-sandbox"]
5 -sources: [{"sourcePath":"platform/tool-router-workbench/public.md","sourceHeading":"A “fresh” client label can still reuse the same sandbox"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/sdk-and-api/a-fresh-client-label-can-still-reuse-the-same-sandbox","a-fresh-client-label-can-still-reuse-the-same-sandbox"]
11 ----
12 -Use this when customers ask whether Tool Router workbench state persists forever, or whether personal data used in the remote workbench is retained indefinitely.
13 -
14 -## A “fresh” client label can still reuse the same sandbox
15 -
16 -Workbench and sandbox reuse follows the actual Tool Router session, not an arbitrary client-side session label. Reusing the same `trs_*` session or MCP URL can reuse the same cached workbench and sandbox.
17 -
18 -Create a new Tool Router session and use its newly returned MCP URL when a
19 -workflow requires an independent sandbox rather than reused session state.
docs/content/kb/guide/platform-triggers.mdx deleted
-27
@@ -1,27 +0,0 @@
1 ----
2 -title: "Triggers"
3 -description: "Public trigger catalog and webhook delivery guidance."
4 -keywords: ["catalog","platform","retries","triggers","webhooks","errors-and-troubleshooting","sessions-and-execution","workflows","/kb/triggers-and-webhooks/platform-triggers","deduplicate-trigger-webhook-deliveries","find-every-toolkit-that-currently-supports-triggers"]
5 -sources: [{"sourcePath":"platform/triggers/public.md","sourceHeading":"Find every toolkit that currently supports triggers"},{"sourcePath":"platform/triggers/public.md","sourceHeading":"Trigger webhook delivery is at-least-once"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","workflows"]
10 -aliases: ["/kb/triggers-and-webhooks/platform-triggers","deduplicate-trigger-webhook-deliveries","find-every-toolkit-that-currently-supports-triggers"]
11 ----
12 -## Find every toolkit that currently supports triggers
13 -
14 -Do not rely on a dashboard count as the complete trigger catalog because availability changes and list views can be partial.
15 -
16 -- Call `GET /api/v3.1/triggers_types` to list trigger types and their parent toolkits. Use `toolkit_slugs` to narrow the result when needed.
17 -- Or call `GET /api/v3.1/toolkits` and select toolkits whose `triggers_count` is greater than zero.
18 -- Follow pagination through every result page before calculating a total or claiming the list is complete.
19 -- Each trigger type declares its required configuration and may be webhook/event-driven or polling-based.
20 -
21 -References: [trigger types API](https://docs.composio.dev/reference/api-reference/triggers/getTriggersTypes), [toolkits API](https://docs.composio.dev/reference/api-reference/toolkits/getToolkits), and [creating triggers](https://docs.composio.dev/docs/setting-up-triggers/creating-triggers).
22 -
23 -## Trigger webhook delivery is at-least-once
24 -
25 -A receiver can occasionally see the same trigger webhook more than once, including the same `log_id` or provider event/message ID, when an outbound delivery attempt is retried. This does not necessarily mean Composio ingested the provider event twice.
26 -
27 -Webhook handlers should be idempotent and deduplicate on a stable identifier such as `log_id`, the provider message/event ID, or the webhook event ID. If duplicates continue beyond normal retry behavior, contact Composio support with the relevant IDs and receipt timestamps.
docs/content/kb/guide/sdk-tool-execution-retries.mdx deleted
-22
@@ -1,22 +0,0 @@
1 ----
2 -title: "Tool Execution Retries"
3 -description: "Public support knowledge for Tool Execution Retries."
4 -keywords: ["platform","sdk","tool-execution-retries","errors-and-troubleshooting","sessions-and-execution","/kb/sdk-and-api/tool-execution-timeouts-can-retry-non-idempotent-actions","tool-execution-timeouts-can-retry-non-idempotent-actions"]
5 -sources: [{"sourcePath":"sdk/tool-execution-retries/public.md","sourceHeading":"Current SDKs do not automatically retry non-idempotent tool executions"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/sdk-and-api/tool-execution-timeouts-can-retry-non-idempotent-actions","tool-execution-timeouts-can-retry-non-idempotent-actions"]
11 ----
12 -## Current SDKs do not automatically retry non-idempotent tool executions
13 -
14 -Python SDK 0.16.0 and TypeScript SDK 0.14.0 changed tool execution and Proxy Execute so non-idempotent writes are not automatically retried after timeouts, rate limits, or server errors. Upgrade to at least those versions before diagnosing duplicate sends or writes as current SDK retry behavior.
15 -
16 -An ambiguous client timeout still does not prove that the provider-side action failed. Before manually retrying a send, create, update, or delete action, inspect the execution log or provider state to determine whether the first attempt completed. If duplicates persist on a current SDK, collect the SDK version, execution log IDs, and timestamps for support.
17 -
18 -Suggested guidance:
19 -
20 -```text
21 -Current Composio SDKs do not automatically retry non-idempotent tool executions. A timeout can still be ambiguous, so check the execution log or provider state before manually retrying an action that may have completed.
22 -```
docs/content/kb/guide/sdk-tool-schemas.mdx deleted
-18
@@ -1,18 +0,0 @@
1 ----
2 -title: "TypeScript Tool Schema Definitions"
3 -description: "Public guidance for dangling JSON Schema references in older TypeScript SDK versions."
4 -keywords: ["json-schema","platform","sdk","typescript","errors-and-troubleshooting","sessions-and-execution","/kb/sdk-and-api/upgrade-when-ref-is-present-but-root-defs-is-missing","upgrade-when-ref-is-present-but-root-defs-is-missing"]
5 -sources: [{"sourcePath":"sdk/tool-schemas/public.md","sourceHeading":"Upgrade when `$ref` is present but root `$defs` is missing"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution"]
10 -aliases: ["/kb/sdk-and-api/upgrade-when-ref-is-present-but-root-defs-is-missing","upgrade-when-ref-is-present-but-root-defs-is-missing"]
11 ----
12 -## Upgrade when `$ref` is present but root `$defs` is missing
13 -
14 -Older `@composio/core` releases through 0.11.0 could preserve a nested `$ref` while stripping the root `$defs` or `definitions` block from raw tool schemas. Downstream schema parsers then see a dangling reference.
15 -
16 -The shared fix shipped in `@composio/core` 0.12.0. Upgrade core to 0.12.0 or later and use a compatible provider-package version. That release line is ESM-only and requires Node.js 22.22.3 or later, so confirm runtime and provider compatibility before upgrading.
17 -
18 -After upgrading, fetch the exact tool again and verify every internal `$ref` has a matching root definition.
docs/content/kb/guide/toolkits-ahrefs.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "Ahrefs"
3 -description: "Public support knowledge for Ahrefs."
4 -keywords: ["ahrefs","for-you","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/ahrefs-actions-use-the-api-host","ahrefs-actions-use-the-api-host"]
5 -sources: [{"sourcePath":"toolkits/ahrefs/public.md","sourceHeading":"Ahrefs actions must call api.ahrefs.com, not ahrefs.com"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["ahrefs"]
11 -aliases: ["/kb/toolkits/ahrefs-actions-use-the-api-host","ahrefs-actions-use-the-api-host"]
12 ----
13 -## Ahrefs actions must call api.ahrefs.com, not ahrefs.com
14 -
15 -Ahrefs API calls should use the API host `https://api.ahrefs.com/v3`. If Ahrefs actions or connection checks are hitting `https://ahrefs.com/v3` and returning 404 HTML, treat it as a connector base-URL configuration problem rather than an API-key or request-payload issue. Confirm the failing request is using api.ahrefs.com; if it is not, contact Composio support with the redacted request or log ID for connector review.
docs/content/kb/guide/toolkits-airtable.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Airtable"
3 -description: "Public support knowledge for Airtable."
4 -keywords: ["airtable","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/airtable-troubleshooting","airtable-triggers-and-webhooks-were-not-yet-generally-available","airtable-troubleshooting","batch-airtable-record-updates-in-groups-of-10","connect-airtable-to-claude-using-mcp","connection-initiation-timeout-after-10-minutes-is-not-airtable-specifi","missing-airtable-tools-may-be-caused-by-default-list-limits-or-ts-sdk","use-custom-airtable-oauth-credentials-for-additional-scopes"]
5 -sources: [{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"Connect Airtable to Claude using MCP"},{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"Use custom Airtable OAuth credentials for additional scopes"},{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"Connection initiation timeout after 10 minutes is not Airtable-specific"},{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"Missing Airtable tools may be caused by list limits or an older toolkit version"},{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"AIRTABLE_UPDATE_MULTIPLE_RECORDS updates at most 10 records per call"},{"sourcePath":"toolkits/airtable/public.md","sourceHeading":"Use one of the current Airtable metadata triggers"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["airtable"]
11 -aliases: ["/kb/toolkits/airtable-troubleshooting","airtable-triggers-and-webhooks-were-not-yet-generally-available","airtable-troubleshooting","batch-airtable-record-updates-in-groups-of-10","connect-airtable-to-claude-using-mcp","connection-initiation-timeout-after-10-minutes-is-not-airtable-specifi","missing-airtable-tools-may-be-caused-by-default-list-limits-or-ts-sdk","use-custom-airtable-oauth-credentials-for-additional-scopes"]
12 ----
13 -Use this guide to connect Airtable, discover and execute current tools, and configure metadata triggers.
14 -
15 -## Connect and authenticate Airtable
16 -
17 -**Connect Airtable to Claude through MCP.** Airtable can be connected to Claude through Composio MCP. Create or use an MCP server with Airtable tools selected, add the MCP server configuration to Claude, and complete the Airtable account connection from the MCP/connect flow.
18 -
19 -**Use custom OAuth credentials for additional scopes.** For additional Airtable scopes, use your own Airtable OAuth developer app. Configure the required scopes in Airtable, enable/use custom OAuth credentials in Composio, and create a new integration/auth config with those credentials and scopes. If an existing integration was created before the scope change, create a new one and retry the connection.
20 -
21 -**Restart connection flows that exceed ten minutes.** The expiry reason "Connection initiation did not complete within 10 minutes" means the user opened or initiated the connection but did not finish the authentication flow within ten minutes. It is a generic connected-account timeout across toolkits, not an Airtable-specific error. Start a fresh connection/initiation link and complete the OAuth flow within the allowed window.
22 -
23 -## Discover and execute Airtable tools
24 -
25 -**Increase list limits and use a current toolkit version.** If Airtable tools appear missing, first increase the tools list limit or paginate
26 -because the response may contain only the first page. Explicitly request the
27 -latest toolkit version when a pinned version lacks a current action. Old names
28 -such as `create_multiple_records` and `create_record` were deprecated in favor
29 -of current uppercase slugs such as `AIRTABLE_CREATE_RECORDS`.
30 -
31 -**Batch updates in groups of ten records.** `AIRTABLE_UPDATE_MULTIPLE_RECORDS` can update a maximum of 10 Airtable records at a time. For larger updates, split the records into batches of 10 and execute multiple calls while respecting Airtable's API rate limits.
32 -
33 -## Configure Airtable metadata triggers
34 -
35 -**Choose an event from the current trigger catalog.** The current Airtable toolkit exposes triggers for base metadata changes, base schema changes, user profile changes, and view creation, deletion, or metadata changes. Fetch the current trigger catalog before implementation and use the exact returned slug. If the needed event is not in that catalog, submit that Airtable event through the Composio request portal.
docs/content/kb/guide/toolkits-apollo.mdx deleted
-33
@@ -1,33 +0,0 @@
1 ----
2 -title: "Apollo"
3 -description: "Public support knowledge for Apollo."
4 -keywords: ["apollo","for-you","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/apollo-tools-have-had-missing-or-incorrect-request-schema-parameters","/kb/toolkits/apollo-troubleshooting","apollo-people-enrichment-and-bulk-enrichment-can-behave-differently","apollo-search-results-may-mirror-apollo-s-official-api-behavior","apollo-tools-have-had-missing-or-incorrect-request-schema-parameters","apollo-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/apollo/public.md","sourceHeading":"Apollo 403s on search/enrichment endpoints can be key-permission or plan-access gated"},{"sourcePath":"toolkits/apollo/public.md","sourceHeading":"Apollo people enrichment and bulk enrichment can behave differently"},{"sourcePath":"toolkits/apollo/public.md","sourceHeading":"Apollo search results may mirror Apollo's official API behavior"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["apollo"]
11 -aliases: ["/kb/toolkits/apollo-tools-have-had-missing-or-incorrect-request-schema-parameters","/kb/toolkits/apollo-troubleshooting","apollo-people-enrichment-and-bulk-enrichment-can-behave-differently","apollo-search-results-may-mirror-apollo-s-official-api-behavior","apollo-tools-have-had-missing-or-incorrect-request-schema-parameters","apollo-troubleshooting"]
12 ----
13 -## Apollo 403s on search/enrichment endpoints can be key-permission or plan-access gated
14 -
15 -For Apollo 403 errors on search/enrichment-style endpoints, first confirm whether your Apollo API key has the relevant endpoint enabled or has **Set as master key** turned on. Apollo documents People API Search as requiring a master API key, and Apollo API keys can be created with either individual endpoint access or master-key access. Apollo also gates advanced API access by plan, so a 403 can be Apollo-side endpoint permission, master-key, credit/API-access, or plan gating even when other Apollo tools work.
16 -
17 -Checks to isolate the cause:
18 -
19 -- Confirm the Composio credential field is `generic_api_key`.
20 -
21 -- Run the exact upstream Apollo endpoint directly with the same key and compare the redacted status and response body.
22 -
23 -- If `APOLLO_GET_AUTH_STATUS` or `APOLLO_VIEW_API_USAGE_STATS` succeeds but search/enrichment endpoints fail, do not say the key is definitely invalid. Phrase it as Apollo endpoint permission / master-key / plan-access gating.
24 -
25 -- If you contact Composio support, include the failing Composio log ID, upstream endpoint, and whether the Apollo key was created with **Set as master key** or per-endpoint permissions.
26 -
27 -## Apollo people enrichment and bulk enrichment can behave differently
28 -
29 -Apollo's single people enrichment and bulk people enrichment APIs do not behave identically. `APOLLO_PEOPLE_ENRICHMENT` and `APOLLO_BULK_PEOPLE_ENRICHMENT` call different upstream Apollo endpoints, and the bulk endpoint may require more complete or different unique person details. If single enrichment works but bulk enrichment does not, compare against Apollo's official bulk people enrichment API behavior before treating it as a Composio response transformation issue. Composio does not intentionally modify the upstream Apollo response.
30 -
31 -## Apollo search results may mirror Apollo's official API behavior
32 -
33 -When Apollo search returns unexpected results, compare the Composio tool call with the equivalent Apollo official API request using the same query parameters and API key. If Apollo's official endpoint returns the same response, the behavior is upstream from Apollo rather than a Composio transformation. Use the direct Apollo API curl as the baseline for debugging search filters and response differences.
docs/content/kb/guide/toolkits-asana.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Asana"
3 -description: "Public support knowledge for Asana."
4 -keywords: ["asana","for-you","platform","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava","/kb/toolkits/asana-troubleshooting","asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava","asana-troubleshooting","deleted-asana-auth-configs-can-block-mcp-config-edits-create-a-new-mcp","older-sdk-connection-initiation-may-require-appname-integrationid-enti","verify-current-production-availability-before-using-asana-triggers"]
5 -sources: [{"sourcePath":"toolkits/asana/public.md","sourceHeading":"Use `ASANA_GET_STORIES_FOR_TASK` and pass the task ID as a string"},{"sourcePath":"toolkits/asana/public.md","sourceHeading":"Use the current Asana task triggers"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["asana"]
11 -aliases: ["/kb/toolkits/asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava","/kb/toolkits/asana-troubleshooting","asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava","asana-troubleshooting","deleted-asana-auth-configs-can-block-mcp-config-edits-create-a-new-mcp","older-sdk-connection-initiation-may-require-appname-integrationid-enti","verify-current-production-availability-before-using-asana-triggers"]
12 ----
13 -## Use `ASANA_GET_STORIES_FOR_TASK` and pass the task ID as a string
14 -
15 -Asana represents task comments as stories. Use `ASANA_GET_STORIES_FOR_TASK` to retrieve the comments and activity for a task, and pass the task ID as a string rather than an integer. For custom toolkit-based tools, set the Asana base URL to `https://app.asana.com/api/1.0` and include the required Authorization header.
16 -
17 -## Use the current Asana task triggers
18 -
19 -The current Asana toolkit exposes triggers for task creation, updates, comments, attachments, tags, and moves between sections. Fetch the trigger catalog before implementation and use the exact returned slug, such as `ASANA_TASK_COMMENT_ADDED` or `ASANA_TASK_UPDATED`.
docs/content/kb/guide/toolkits-attio.mdx deleted
-27
@@ -1,27 +0,0 @@
1 ----
2 -title: "Attio"
3 -description: "Public support knowledge for Attio."
4 -keywords: ["attio","for-you","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/attio-troubleshooting","attio-meeting-and-call-recording-get-by-id-endpoints-were-a-feature-re","attio-oauth-tokens-cannot-be-programmatically-revoked-by-composio","attio-toolkit-defaults-can-stay-on-the-base-pinned-version-unless-a-ve","attio-troubleshooting","auth-config-names-can-carry-a-reference-id-but-custom-auth-config-meta","missing-attio-scopes-on-composio-managed-auth-require-confirming-the-a","use-contains-for-partial-text-matching-in-attio-find-record-filters","use-custom-tools-when-an-attio-api-object-is-not-built-into-composio-y"]
5 -sources: [{"sourcePath":"toolkits/attio/public.md","sourceHeading":"Use $contains for partial text matching in ATTIO_FIND_RECORD filters"},{"sourcePath":"toolkits/attio/public.md","sourceHeading":"Use custom tools when an Attio API object is not built into Composio yet"},{"sourcePath":"toolkits/attio/public.md","sourceHeading":"Top-level $ parameter names were fixed for LLM provider compatibility in the latest schema version"},{"sourcePath":"toolkits/attio/public.md","sourceHeading":"Attio toolkit defaults can stay on the base pinned version unless a version is explicitly selected"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["attio"]
11 -aliases: ["/kb/toolkits/attio-troubleshooting","attio-meeting-and-call-recording-get-by-id-endpoints-were-a-feature-re","attio-oauth-tokens-cannot-be-programmatically-revoked-by-composio","attio-toolkit-defaults-can-stay-on-the-base-pinned-version-unless-a-ve","attio-troubleshooting","auth-config-names-can-carry-a-reference-id-but-custom-auth-config-meta","missing-attio-scopes-on-composio-managed-auth-require-confirming-the-a","use-contains-for-partial-text-matching-in-attio-find-record-filters","use-custom-tools-when-an-attio-api-object-is-not-built-into-composio-y"]
12 ----
13 -## Use $contains for partial text matching in ATTIO_FIND_RECORD filters
14 -
15 -For partial matching on text attributes in ATTIO_FIND_RECORD, structure the filter with the attribute slug mapped to a $contains condition, for example &#123;"name": &#123;"$contains": "John"&#125;&#125;. If you receive exact-match behavior instead, verify the specific attribute and filter shape, then try the contains-style filter first.
16 -
17 -## Use custom tools when an Attio API object is not built into Composio yet
18 -
19 -If an Attio endpoint is not covered by the built-in toolkit, create a custom tool and request the missing tool through the Composio request portal. Custom tools can use Composio-managed auth, so you do not need to build the entire OAuth/token-storage layer yourself.
20 -
21 -## Top-level $ parameter names were fixed for LLM provider compatibility in the latest schema version
22 -
23 -For schema failures caused by top-level $-prefixed parameter names, update to the latest tool schema/toolkit version. The root cause was corrected for top-level $ prefixes, and compatibility was verified across OpenAI, Claude, Gemini, and Vercel AI SDK. Nested $ prefixes were accepted by the major providers tested, while broader parameter naming conventions may still need case-specific review.
24 -
25 -## Attio toolkit defaults can stay on the base pinned version unless a version is explicitly selected
26 -
27 -Do not assume Attio calls use the latest toolkit definition automatically. Composio can default to an older base pinned version because latest versions can change. If you need updated Attio tool descriptions or fixes, explicitly set the Attio toolkit version in your SDK or environment and then retest.
docs/content/kb/guide/toolkits-browser-tool.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "Browser Tool"
3 -description: "Public support knowledge for Browser Tool."
4 -keywords: ["browser_tool","for-you","platform","security-and-trust","sessions-and-execution","toolkits-and-providers","/kb/toolkits/browser-tool-profiles-do-not-work-in-zero-data-retention-projects","browser-tool-profiles-do-not-work-in-zero-data-retention-projects"]
5 -sources: [{"sourcePath":"toolkits/browser_tool/public.md","sourceHeading":"Browser Tool profiles do not work in Zero Data Retention projects"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["security-and-trust","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["browser_tool"]
11 -aliases: ["/kb/toolkits/browser-tool-profiles-do-not-work-in-zero-data-retention-projects","browser-tool-profiles-do-not-work-in-zero-data-retention-projects"]
12 ----
13 -## Browser Tool profiles do not work in Zero Data Retention projects
14 -
15 -Browser Tool requires persistent browser profiles to maintain session state, so it is incompatible with projects configured for Zero Data Retention or removal of execution data. Move the Browser Tool usage to a project without ZDR enabled, or change the project's log/data visibility setting from removing execution data to storing/showing all logs where policy allows. The dashboard path is Project Settings / Log storage configuration, and the API setting is `log_visibility_setting: show_all`.
docs/content/kb/guide/toolkits-calendly.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "Calendly"
3 -description: "Public support knowledge for Calendly."
4 -keywords: ["calendly","for-you","platform","errors-and-troubleshooting","toolkits-and-providers","/kb/toolkits/use-calendly-post-invitee","use-calendly-post-invitee"]
5 -sources: [{"sourcePath":"toolkits/calendly/public.md","sourceHeading":"Use CALENDLY_POST_INVITEE instead of deprecated CALENDLY_CREATE_EVENT_INVITEE"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["calendly"]
11 -aliases: ["/kb/toolkits/use-calendly-post-invitee","use-calendly-post-invitee"]
12 ----
13 -## Use CALENDLY_POST_INVITEE instead of deprecated CALENDLY_CREATE_EVENT_INVITEE
14 -
15 -For Calendly invitee creation flows, prefer `CALENDLY_POST_INVITEE` instead of the legacy `CALENDLY_CREATE_EVENT_INVITEE`. New implementations and migration guidance should point customers to `CALENDLY_POST_INVITEE`.
docs/content/kb/guide/toolkits-canva.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "Canva"
3 -description: "Public support knowledge for Canva."
4 -keywords: ["canva","for-you","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/use-canva-autofill-jobs-for-design-content","use-canva-autofill-jobs-for-design-content"]
5 -sources: [{"sourcePath":"toolkits/canva/public.md","sourceHeading":"Use Canva autofill jobs when content must be populated into a design"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["canva"]
11 -aliases: ["/kb/toolkits/use-canva-autofill-jobs-for-design-content","use-canva-autofill-jobs-for-design-content"]
12 ----
13 -## Use Canva autofill jobs when content must be populated into a design
14 -
15 -For Canva workflows that need content inserted into a generated design, do not rely on the create-design endpoint/tool. `CANVA_CREATE_CANVA_DESIGN_WITH_OPTIONAL_ASSET` is deprecated and should be replaced with `CANVA_POST_DESIGNS`, but both the old and new create-design flows create a blank design by default and do not accept arbitrary content in the request. Use `CANVA_INITIATE_CANVA_DESIGN_AUTOFILL_JOB` for the content-population use case, because that flow is built around Canva's autofill capability.
docs/content/kb/guide/toolkits-canvas.mdx deleted
-47
@@ -1,47 +0,0 @@
1 ----
2 -title: "Canvas"
3 -description: "Public support knowledge for Canvas."
4 -keywords: ["canvas","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/canvas-troubleshooting","canvas-404s-on-course-analytics-usually-mean-the-course-or-endpoint-is","canvas-assignment-graded-trigger-is-expected-to-work-for-teacher-accou","canvas-create-calendar-event-can-use-a-user-id-and-canvas-api-field-na","canvas-discussion-topics-and-announcements-require-only-announcements","canvas-does-not-expose-webhooks-for-every-requested-trigger-use-case","canvas-oauth-credentials-must-match-the-configured-canvas-base-url","canvas-quiz-matching-question-answers-use-unprefixed-answer-field-keys","canvas-response-schemas-are-being-standardized-gradually-not-universal","canvas-trigger-payloads-expose-canvas-user-id-separately-as-canvas-use","canvas-triggers-are-available-and-course-selection-can-be-driven-from","canvas-troubleshooting","older-canvas-toolkit-versions-cannot-be-patched-in-place","paginate-canvas-list-results","resolve-canvas-account-endpoint-access-errors","toolkit-versioning-does-not-version-canvas-trigger-logic","use-shorter-polling-intervals-for-canvas-triggers-when-longer-interval"]
5 -sources: [{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas triggers are available, and course selection can be driven from course IDs"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas triggers fire for users visible to the connected bearer-token user"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas Assignment Graded trigger is expected to work for Teacher accounts, not Student accounts"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas trigger payloads expose Canvas user ID separately as `canvas_user_id`"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas action 401/unauthorized errors can be caused by missing action-level scopes"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas OAuth credentials must match the configured Canvas base URL"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas account-level endpoints require admin permissions"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"`CANVAS_CREATE_CALENDAR_EVENT` can use a user ID, and Canvas API field names are preserved"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas list/fetch endpoints follow Canvas pagination behavior and may need `per_page`"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas discussion topics and announcements require `only_announcements` selection"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas 404s on course analytics usually mean the course or endpoint is unavailable"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Canvas quiz matching question answers use unprefixed answer field keys"},{"sourcePath":"toolkits/canvas/public.md","sourceHeading":"Older Canvas toolkit versions cannot be patched in place"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["canvas"]
11 -aliases: ["/kb/toolkits/canvas-troubleshooting","canvas-404s-on-course-analytics-usually-mean-the-course-or-endpoint-is","canvas-assignment-graded-trigger-is-expected-to-work-for-teacher-accou","canvas-create-calendar-event-can-use-a-user-id-and-canvas-api-field-na","canvas-discussion-topics-and-announcements-require-only-announcements","canvas-does-not-expose-webhooks-for-every-requested-trigger-use-case","canvas-oauth-credentials-must-match-the-configured-canvas-base-url","canvas-quiz-matching-question-answers-use-unprefixed-answer-field-keys","canvas-response-schemas-are-being-standardized-gradually-not-universal","canvas-trigger-payloads-expose-canvas-user-id-separately-as-canvas-use","canvas-triggers-are-available-and-course-selection-can-be-driven-from","canvas-troubleshooting","older-canvas-toolkit-versions-cannot-be-patched-in-place","paginate-canvas-list-results","resolve-canvas-account-endpoint-access-errors","toolkit-versioning-does-not-version-canvas-trigger-logic","use-shorter-polling-intervals-for-canvas-triggers-when-longer-interval"]
12 ----
13 -Use this guide to configure Canvas authentication and permissions, set up triggers, run Canvas actions, and troubleshoot course or toolkit-version issues.
14 -
15 -## Configure Canvas authentication and permissions
16 -
17 -**Check action-level scopes when Canvas returns 401 or unauthorized.** Compare the auth configs and verify that the failing Canvas connection has the scope required by the action. `CANVAS_GET_USER_PROFILE` requires `url:GET|/api/v1/users/:user_id/profile`. If scopes are missing, update the auth config settings; newly created connected accounts will get the updated scopes from that point onward.
18 -
19 -**Match OAuth credentials to the configured Canvas base URL.** For Canvas OAuth, the client ID and client secret must belong to the same Canvas base URL configured on the connection/auth config. A mismatch between the Canvas domain, base URL, and OAuth credentials can cause auth failures even if the credentials are otherwise valid.
20 -
21 -**Use an administrator for account-level endpoints.** Canvas account-level endpoints require account administrator permissions in Canvas. Use `CANVAS_LIST_MANAGEABLE_ACCOUNTS` to list accounts the connected user can manage, and `CANVAS_GET_SINGLE_ACCOUNT` when the account ID is already known. If you get an authorization error, confirm that the connected Canvas user has account-level admin permissions before treating it as a Composio-side failure.
22 -
23 -## Set up Canvas triggers
24 -
25 -**Select courses by their Canvas IDs.** Canvas triggers are available. For a course-based setup flow, first call `CANVAS_LIST_COURSES` or the relevant get-courses action, show the course IDs with their course names to the user, and then redirect the user to the trigger configuration page with the selected course context.
26 -
27 -**Target users visible to the connected bearer-token user.** Canvas trigger behavior is tied to the user represented by the bearer token on the connected account. A trigger should work for users visible through `CANVAS_GET_ALL_USERS` for the relevant account. The user field cannot be removed entirely because Composio cannot infer every logged-in Canvas user from the provider token without a configured target.
28 -
29 -**Use a Teacher account for Assignment Graded.** For Canvas Assignment Graded, the trigger can work for Teacher accounts but not Student accounts because of Canvas permission behavior. If the same connected account also has token-expiry symptoms, execute a Canvas action on that connected account to separate permission behavior from connection/auth issues.
30 -
31 -**Distinguish Canvas and Composio user IDs in payloads.** Canvas trigger payloads now separate the Canvas-side user identifier from Composio's user identifier. Use `canvas_user_id` for the Canvas LMS user and `user_id` for the Composio/project user. This avoids ambiguity when both identifiers are present in the same payload.
32 -
33 -## Execute Canvas actions and handle provider behavior
34 -
35 -**Follow Canvas field descriptions for calendar events.** For `CANVAS_CREATE_CALENDAR_EVENT`, a Canvas user ID can be used where accepted by the Canvas API. Composio keeps Canvas API field names to stay consistent with the provider API, so rely on each field description for accepted values when the field name is ambiguous.
36 -
37 -**Paginate list and fetch endpoints with `per_page`.** Canvas list endpoints follow Canvas API pagination behavior. Where supported, pass `per_page` to control how many records are returned in a response. If a Canvas action appears capped or returns a smaller page, check whether the relevant tool version supports `per_page` and upgrade if needed.
38 -
39 -**Use `only_announcements` to request discussion topics and announcements separately.** For Canvas discussion topics, use `only_announcements: false` or omit it when calling the discussion-topic flow. For announcements, use `only_announcements: true`. Canvas cannot return both discussion topics and announcements in one combined call for this case, so make two separate API calls and merge the results client-side if both are needed.
40 -
41 -**Use unprefixed keys for quiz matching answers.** For Canvas quiz matching question answers, use `comments_html`, `text`, `weight`, `match_left`, and `match_right`. Do not use `answer_comments_html`, `answer_text`, `answer_weight`, `answer_match_left`, or `answer_match_right` for this payload.
42 -
43 -## Troubleshoot Canvas courses and toolkit versions
44 -
45 -**Verify the course before diagnosing analytics 404s.** For Canvas course-level participation or analytics actions, first verify the course ID by listing courses or fetching the course by ID with `CANVAS_LIST_COURSES` or `CANVAS_GET_SINGLE_COURSE`. If the course ID is valid but the analytics endpoint still 404s, the Canvas analytics activity endpoint may simply not be available on that Canvas instance.
46 -
47 -**Upgrade instead of patching older toolkit versions.** Composio cannot patch older toolkit versions in place. If a Canvas behavior or schema fix is released in a newer version, the path is to upgrade the toolkit version. Customers can compare differences between toolkit versions in the dashboard before upgrading.
docs/content/kb/guide/toolkits-clickup.mdx deleted
-26
@@ -1,26 +0,0 @@
1 ----
2 -title: "ClickUp"
3 -description: "Public support knowledge for ClickUp."
4 -keywords: ["clickup","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/clickup-troubleshooting","clickup-custom-oauth-should-use-the-composio-callback-url-registered-i","clickup-folders-and-tasks-are-supported-through-clickup-get-folders-an","clickup-supports-default-auth-or-customer-owned-credentials-when-creat","clickup-tokens-may-require-manual-provider-side-removal-if-programmati","clickup-troubleshooting","cursor-may-fail-when-too-many-mcp-servers-are-configured-keep-clickup"]
5 -sources: [{"sourcePath":"toolkits/clickup/public.md","sourceHeading":"ClickUp supports managed OAuth, custom OAuth, and API-key credentials"},{"sourcePath":"toolkits/clickup/public.md","sourceHeading":"ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app"},{"sourcePath":"toolkits/clickup/public.md","sourceHeading":"ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["clickup"]
11 -aliases: ["/kb/toolkits/clickup-troubleshooting","clickup-custom-oauth-should-use-the-composio-callback-url-registered-i","clickup-folders-and-tasks-are-supported-through-clickup-get-folders-an","clickup-supports-default-auth-or-customer-owned-credentials-when-creat","clickup-tokens-may-require-manual-provider-side-removal-if-programmati","clickup-troubleshooting","cursor-may-fail-when-too-many-mcp-servers-are-configured-keep-clickup"]
12 ----
13 -## ClickUp supports managed OAuth, custom OAuth, and API-key credentials
14 -
15 -Use Composio-managed OAuth for the standard connection flow. Use a custom
16 -ClickUp OAuth app or API-key credentials when you need greater control.
17 -In newer SDK/API flows, use the v3 auth config nano ID (`ac_...`) rather than
18 -older v1/v2 integration assumptions.
19 -
20 -## ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app
21 -
22 -For ClickUp custom OAuth, make sure the redirect URL in the ClickUp app matches the callback shown by the current Composio auth-config flow. A mismatch between the current auth config and an old callback copied from a legacy SDK example is a common cause of setup failure.
23 -
24 -## ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`
25 -
26 -For ClickUp folder/task-list workflows, use supported tools such as `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`. If a more specific ClickUp endpoint is missing, request that tool through the standard tool-request flow.
docs/content/kb/guide/toolkits-confluence.mdx deleted
-37
@@ -1,37 +0,0 @@
1 ----
2 -title: "Confluence"
3 -description: "Public support knowledge for Confluence."
4 -keywords: ["confluence","for-you","platform","auth-config","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/confluence-troubleshooting","confluence-custom-oauth-should-keep-scopes-aligned-with-composio-defau","confluence-managed-oauth-failures-can-come-from-scope-mismatch-between","confluence-needs-offline-access-for-refresh","confluence-troubleshooting","download-confluence-attachments-by-first-getting-attachment-ids","for-atlassian-confluence-oauth-use-the-same-redirect-uri-in-auth-confi","page-created-triggers-can-auto-disable-after-repeated-cloud-id-lookup"]
5 -sources: [{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Confluence custom OAuth should keep scopes aligned with Composio defaults and endpoint type"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Add `offline_access` to Confluence auth configs when refresh tokens are needed"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Use connected account ID, not auth config ID, when executing Confluence tools"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Use `CONFLUENCE_GET_PAGE_BY_ID` to retrieve Confluence page content"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"`CONFLUENCE_UPDATE_PAGE` should be paired with `CONFLUENCE_GET_PAGE_VERSIONS` for versioned updates"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Download Confluence attachments by first getting attachment IDs"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"Confluence tool scopes are exposed in MCP listTools annotations for supported deployments"},{"sourcePath":"toolkits/confluence/public.md","sourceHeading":"For Atlassian/Confluence OAuth, use the same redirect URI in auth config and Atlassian app"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["confluence"]
11 -aliases: ["/kb/toolkits/confluence-troubleshooting","confluence-custom-oauth-should-keep-scopes-aligned-with-composio-defau","confluence-managed-oauth-failures-can-come-from-scope-mismatch-between","confluence-needs-offline-access-for-refresh","confluence-troubleshooting","download-confluence-attachments-by-first-getting-attachment-ids","for-atlassian-confluence-oauth-use-the-same-redirect-uri-in-auth-confi","page-created-triggers-can-auto-disable-after-repeated-cloud-id-lookup"]
12 ----
13 -Use this guide to configure Confluence OAuth, execute tools with the correct account, and read, update, or download Confluence content.
14 -
15 -## Configure Confluence OAuth
16 -
17 -**Align custom OAuth scopes with the endpoint type.** For Confluence custom OAuth, keep Atlassian scopes aligned with the scopes Composio expects. Classic and granular scopes differ depending on whether the underlying Confluence endpoint is v1 or v2. Incorrect substitutions such as using an irrelevant space scope can cause tool execution errors even if OAuth completes.
18 -
19 -**Add `offline_access` when refresh tokens are needed.** For Confluence OAuth, include the `offline_access` scope in the auth config and then create a new connected account. `offline_access` enables token refresh, and adding it to an existing auth config only affects new connections after users reconnect.
20 -
21 -**Use the same redirect URI in Composio and Atlassian.** The redirect URI in the Composio auth config and the Atlassian OAuth app must match. Copy the callback shown by the current auth-config flow or documentation; do not reuse legacy v1 or v3 callback paths from older examples.
22 -
23 -## Execute Confluence tools with the correct account
24 -
25 -**Pass the connected account ID, not the auth config ID.** For Confluence tool execution, pass the connected account ID. Do not pass the auth config ID/integration ID in the connected account field. Older SDK versions may also require the UUID form rather than the nano ID, so verify the SDK version and expected ID format.
26 -
27 -**Read supported scopes from MCP tool annotations.** For supported MCP deployments, Confluence scopes can be retrieved from the `annotations` field in the `listTools` API response.
28 -
29 -## Read and update Confluence pages
30 -
31 -**Retrieve page content by page ID.** Use `CONFLUENCE_GET_PAGE_BY_ID` to retrieve Confluence page content by page ID. This is the tool support shared for page body retrieval.
32 -
33 -**Fetch the latest page version before an update.** Confluence page updates require the correct page version. Pair `CONFLUENCE_UPDATE_PAGE` with `CONFLUENCE_GET_PAGE_VERSIONS` so the agent can fetch the latest required version and then update the page. By default, the agent should update over the latest version unless a specific version is requested.
34 -
35 -## Download Confluence attachments
36 -
37 -Use `CONFLUENCE_GET_ATTACHMENTS` to list attachments and get the attachment ID, then pass that ID to `CONFLUENCE_DOWNLOAD_ATTACHMENT` to download the file.
docs/content/kb/guide/toolkits-databricks.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Databricks"
3 -description: "Public support knowledge for Databricks."
4 -keywords: ["databricks","for-you","platform","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/databricks-troubleshooting","databricks-oauth-client-and-secret-setup-reference","databricks-requires-custom-credentials-when-managed-auth-is-unavailabl","databricks-toolkit-does-not-yet-support-oauth-m2m","databricks-troubleshooting","enter-databricks-api-key-credentials-during-connected-account-linking"]
5 -sources: [{"sourcePath":"toolkits/databricks/public.md","sourceHeading":"Databricks OAuth client and secret setup reference"},{"sourcePath":"toolkits/databricks/public.md","sourceHeading":"Enter Databricks API key credentials during connected account linking"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["databricks"]
11 -aliases: ["/kb/toolkits/databricks-troubleshooting","databricks-oauth-client-and-secret-setup-reference","databricks-requires-custom-credentials-when-managed-auth-is-unavailabl","databricks-toolkit-does-not-yet-support-oauth-m2m","databricks-troubleshooting","enter-databricks-api-key-credentials-during-connected-account-linking"]
12 ----
13 -## Databricks OAuth client and secret setup reference
14 -
15 -For Databricks OAuth client and secret setup, follow the [official Databricks OAuth application guide](https://docs.databricks.com/aws/en/agents/mcp/connect-clients). An account administrator creates the OAuth application, configures its redirect URL and scopes, and securely records the generated client ID and client secret.
16 -
17 -## Enter Databricks API key credentials during connected account linking
18 -
19 -The Databricks API key credentials are entered during the connection flow. In code, point customers to `composio.connected_accounts.link()` for creating the connected account and entering the API key details.
docs/content/kb/guide/toolkits-digital-ocean.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "DigitalOcean authentication"
3 -description: "Current authentication choices for the DigitalOcean toolkit."
4 -keywords: ["digital_ocean","for-you","platform","auth-config","authentication","toolkits-and-providers","/kb/toolkits/managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva","managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva"]
5 -sources: [{"sourcePath":"toolkits/digital_ocean/public.md","sourceHeading":"DigitalOcean supports managed OAuth2, custom OAuth2, or a personal access token"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","toolkits-and-providers"]
10 -toolkitSlugs: ["digital_ocean"]
11 -aliases: ["/kb/toolkits/managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva","managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva"]
12 ----
13 -## DigitalOcean supports managed OAuth2, custom OAuth2, or a personal access token
14 -
15 -The current `digital_ocean` toolkit supports OAuth2 and API-key authentication.
16 -Use Composio-managed OAuth for the standard connection flow. Use a custom
17 -DigitalOcean OAuth app when you need control over provider settings;
18 -register the exact callback URI shown by the current Composio flow.
19 -
20 -For API-key authentication, provide a DigitalOcean Personal Access Token in the
21 -`bearer_token` connection field. If OAuth fails before consent, compare the
22 -authorization request with your custom app registration and use the API-key path
23 -only when it matches your security requirements.
docs/content/kb/guide/toolkits-discord.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Discord"
3 -description: "Public support knowledge for Discord."
4 -keywords: ["discord","for-you","platform","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers","/kb/toolkits/discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio","/kb/toolkits/multiple-accounts-for-the-same-discord-app-were-not-supported-in-that","discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio","multiple-accounts-for-the-same-discord-app-were-not-supported-in-that"]
5 -sources: [{"sourcePath":"toolkits/discord/public.md","sourceHeading":"Discord OAuth credentials do not have a fixed expiration period"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["discord"]
11 -aliases: ["/kb/toolkits/discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio","/kb/toolkits/multiple-accounts-for-the-same-discord-app-were-not-supported-in-that","discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio","multiple-accounts-for-the-same-discord-app-were-not-supported-in-that"]
12 ----
13 -## Discord OAuth credentials do not have a fixed expiration period
14 -
15 -Discord OAuth2 client credentials do not have a fixed expiration period. If a
16 -customer-owned credential suddenly fails, it may have been manually revoked,
17 -reset, or regenerated in Discord. Verify the current Discord developer-app
18 -credentials and create a fresh connection before treating the failure as a
19 -broader provider or Composio issue.
docs/content/kb/guide/toolkits-discordbot.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Discord Bot"
3 -description: "Public support knowledge for Discord Bot."
4 -keywords: ["discordbot","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/discord-bot-troubleshooting","/kb/toolkits/discord-message-triggers-need-bot-token-auth-which-is-not-available-th","/kb/toolkits/multiple-connected-accounts-for-the-same-app-are-not-supported","choose-discordbot-for-bot-token-operations","discord-bot-troubleshooting","discord-message-triggers-need-bot-token-auth-which-is-not-available-th","managed-discordbot-oauth-401s-can-be-worked-around-with-custom-credent","multiple-connected-accounts-for-the-same-app-are-not-supported","verify-discord-auth-config-scopes-when-bot-actions-do-not-respond"]
5 -sources: [{"sourcePath":"toolkits/discordbot/public.md","sourceHeading":"Discord and DiscordBot use different token types"},{"sourcePath":"toolkits/discordbot/public.md","sourceHeading":"Verify Discord auth config scopes when bot actions do not respond"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["discordbot"]
11 -aliases: ["/kb/authentication/discord-bot-troubleshooting","/kb/toolkits/discord-message-triggers-need-bot-token-auth-which-is-not-available-th","/kb/toolkits/multiple-connected-accounts-for-the-same-app-are-not-supported","choose-discordbot-for-bot-token-operations","discord-bot-troubleshooting","discord-message-triggers-need-bot-token-auth-which-is-not-available-th","managed-discordbot-oauth-401s-can-be-worked-around-with-custom-credent","multiple-connected-accounts-for-the-same-app-are-not-supported","verify-discord-auth-config-scopes-when-bot-actions-do-not-respond"]
12 ----
13 -## Discord and DiscordBot use different token types
14 -
15 -Discord has two different authorization models: a user token represents an individual Discord user, while a bot token represents a bot account inside Discord. Composio separates these into different toolkits because the credentials and API behavior are different. Use the Discord toolkit for user-authorized actions and DiscordBot when the workflow needs to act as a Discord bot.
16 -
17 -## Verify Discord auth config scopes when bot actions do not respond
18 -
19 -For DiscordBot behavior that does not respond as expected, verify that the Discord auth config includes the necessary scopes and permissions for the action being tested. Discord's OAuth2 documentation should be used as the source for the required scopes. If scopes look correct and the issue persists, collect the connected account ID or log ID for debugging.
docs/content/kb/guide/toolkits-docusign.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "DocuSign"
3 -description: "Public support knowledge for DocuSign."
4 -keywords: ["docusign","for-you","platform","authentication","toolkits-and-providers","/kb/toolkits/docusign-auth-guide-url","docusign-auth-guide-url"]
5 -sources: [{"sourcePath":"toolkits/docusign/public.md","sourceHeading":"DocuSign auth guide URL"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","toolkits-and-providers"]
10 -toolkitSlugs: ["docusign"]
11 -aliases: ["/kb/toolkits/docusign-auth-guide-url","docusign-auth-guide-url"]
12 ----
13 -## DocuSign auth guide URL
14 -
15 -Use the DocuSign authentication guide at https://composio.dev/auth/docusign for the current Composio DocuSign setup instructions.
docs/content/kb/guide/toolkits-dropbox.mdx deleted
-33
@@ -1,33 +0,0 @@
1 ----
2 -title: "Dropbox"
3 -description: "Public support knowledge for Dropbox."
4 -keywords: ["dropbox","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/dropbox-triggers-are-not-currently-available","/kb/toolkits/dropbox-troubleshooting","allow-the-composio-auth-app-redirect-url-in-the-dropbox-app","dropbox-connections-use-dropbox-native-oauth-not-microsoft-azure-outlo","dropbox-triggers-are-not-currently-available","dropbox-troubleshooting","for-dropbox-upload-path-is-the-dropbox-destination-and-content-is-the","initiate-dropbox-oauth-connections-with-entityid-authmode-integrationi","pass-file-paths-to-sdk-attachment-arguments-rather-than-base64-file-me","recreate-older-dropbox-integrations-after-composio-updates-the-default","use-custom-dropbox-oauth-credentials-for-production-instead-of-the-def","use-dropbox-get-about-me-to-confirm-which-dropbox-account-is-connected"]
5 -sources: [{"sourcePath":"toolkits/dropbox/public.md","sourceHeading":"Allow the Composio auth-app redirect URL in the Dropbox app"},{"sourcePath":"toolkits/dropbox/public.md","sourceHeading":"Dropbox connections use Dropbox native OAuth, not Microsoft/Azure/Outlook login"},{"sourcePath":"toolkits/dropbox/public.md","sourceHeading":"For Dropbox upload, `path` is the Dropbox destination and `content` is the local file path"},{"sourcePath":"toolkits/dropbox/public.md","sourceHeading":"Pass file paths to SDK attachment arguments rather than base64/file metadata objects"},{"sourcePath":"toolkits/dropbox/public.md","sourceHeading":"Use DROPBOX_GET_ABOUT_ME to confirm which Dropbox account is connected"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["dropbox"]
11 -aliases: ["/kb/toolkits/dropbox-triggers-are-not-currently-available","/kb/toolkits/dropbox-troubleshooting","allow-the-composio-auth-app-redirect-url-in-the-dropbox-app","dropbox-connections-use-dropbox-native-oauth-not-microsoft-azure-outlo","dropbox-triggers-are-not-currently-available","dropbox-troubleshooting","for-dropbox-upload-path-is-the-dropbox-destination-and-content-is-the","initiate-dropbox-oauth-connections-with-entityid-authmode-integrationi","pass-file-paths-to-sdk-attachment-arguments-rather-than-base64-file-me","recreate-older-dropbox-integrations-after-composio-updates-the-default","use-custom-dropbox-oauth-credentials-for-production-instead-of-the-def","use-dropbox-get-about-me-to-confirm-which-dropbox-account-is-connected"]
12 ----
13 -## Allow the Composio auth-app redirect URL in the Dropbox app
14 -
15 -For Dropbox OAuth setup, configure the Dropbox app with the exact callback shown by the current Composio auth-config flow. Do not use the legacy v1 auth-app callback from older examples.
16 -
17 -## Dropbox connections use Dropbox native OAuth, not Microsoft/Azure/Outlook login
18 -
19 -The Dropbox integration uses Dropbox's native OAuth2 flow, so users authenticate through Dropbox's login page. Composio cannot add Microsoft, Azure, or Outlook as alternative identity providers for Dropbox because the authentication method is controlled by Dropbox's API. If the customer's Dropbox Business tenant has SSO configured with Microsoft/Azure AD, that SSO behavior must be configured in Dropbox, not in Composio.
20 -
21 -## For Dropbox upload, `path` is the Dropbox destination and `content` is the local file path
22 -
23 -For the Dropbox upload action, `path` is the destination path inside Dropbox,
24 -while `content` is the local file path that should be uploaded. Provide the
25 -local file path in `content`.
26 -
27 -## Pass file paths to SDK attachment arguments rather than base64/file metadata objects
28 -
29 -When using the SDK attachment argument for supported email tools, pass a file path rather than an object containing filename, data, and content type. The SDK handles the file path. If the source file is available at a Dropbox-backed path, pass that Dropbox file path directly in the attachment argument.
30 -
31 -## Use DROPBOX_GET_ABOUT_ME to confirm which Dropbox account is connected
32 -
33 -If Dropbox files or folders appear to be missing after a successful operation, confirm the connected Dropbox account before deeper debugging. Use `DROPBOX_GET_ABOUT_ME` to inspect the account tied to the active Composio connection and compare it with the Dropbox account the user is checking manually.
docs/content/kb/guide/toolkits-excel.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Excel"
3 -description: "Public support knowledge for Excel."
4 -keywords: ["excel","for-you","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/excel-troubleshooting","excel-get-range-failures-can-come-from-sheet-name-or-item-id-mismatche","excel-support-for-oauth2-client-credentials-may-vary-by-action","excel-troubleshooting","excel-update-range-values-must-be-a-2d-array","excel-upload-tools-accept-structured-workbook-data","excel-uses-the-microsoft-auth-guide-at-composio-dev-auth-outlook","generic-column-formatting-and-wrapping-support-was-added-in-the-may-13","shared-item-listing-cannot-reliably-search-for-a-specific-shared-file","upgrade-older-on-prem-versions-if-excel-schemas-contain-dollar-sign-pa","use-excel-toolkit-actions-for-workbook-operations-on-sharepoint-backed"]
5 -sources: [{"sourcePath":"toolkits/excel/public.md","sourceHeading":"EXCEL_UPDATE_RANGE values must be a 2D array"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"Excel upload tools accept structured workbook data"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"EXCEL_GET_RANGE failures can come from sheet name or item_id mismatches"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"Use Excel toolkit actions for workbook operations on SharePoint-backed Excel files"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"Excel uses the Microsoft auth guide at composio.dev/auth/outlook"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"Upgrade if Excel schemas contain dollar-sign parameters"},{"sourcePath":"toolkits/excel/public.md","sourceHeading":"Generic column formatting and wrapping are available in current versions"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["excel"]
11 -aliases: ["/kb/toolkits/excel-troubleshooting","excel-get-range-failures-can-come-from-sheet-name-or-item-id-mismatche","excel-support-for-oauth2-client-credentials-may-vary-by-action","excel-troubleshooting","excel-update-range-values-must-be-a-2d-array","excel-upload-tools-accept-structured-workbook-data","excel-uses-the-microsoft-auth-guide-at-composio-dev-auth-outlook","generic-column-formatting-and-wrapping-support-was-added-in-the-may-13","shared-item-listing-cannot-reliably-search-for-a-specific-shared-file","upgrade-older-on-prem-versions-if-excel-schemas-contain-dollar-sign-pa","use-excel-toolkit-actions-for-workbook-operations-on-sharepoint-backed"]
12 ----
13 -Use this guide to pass valid Excel workbook inputs, operate on SharePoint-backed files, and keep Microsoft auth and tool schemas current.
14 -
15 -## Pass valid inputs to Excel workbook actions
16 -
17 -**Send range values as a two-dimensional array.** Pass values as a two-dimensional array, where the outer list represents rows and each inner list contains the cell values for that row. Even a single cell must be wrapped twice, for example &#123;"values": [["92"]]&#125;.
18 -
19 -**Use structured workbook data for uploads.** Use the revamped Excel tool shape that accepts structured data through worksheet_names and worksheet_data lists/dicts. The tool generates the .xlsx file before upload, instead of requiring the caller or LLM to provide binary workbook content directly.
20 -
21 -**Check the worksheet name and workbook item ID when `EXCEL_GET_RANGE` fails.** If get range appears to fail while the tool itself is working, verify that the workbook actually has the requested worksheet name, such as Sheet1, and that the item_id being passed is the correct file ID for that workbook.
22 -
23 -**Use Excel actions for SharePoint-backed workbook operations.** For workbook operations, use the Excel toolkit actions because they are Excel APIs. Support identified EXCEL_CLOSE_SESSION, EXCEL_DELETE_WORKSHEET, EXCEL_UPDATE_WORKSHEET, and EXCEL_UPDATE_RANGE as already supported for the remaining Excel use cases.
24 -
25 -## Configure Excel authentication and current tool schemas
26 -
27 -**Use the shared Microsoft auth guide.** For Excel auth setup, use the Microsoft auth guide published at https://composio.dev/auth/outlook. The same guide applies to SharePoint, Microsoft Teams, Outlook, and Excel.
28 -
29 -**Upgrade schemas that expose dollar-sign parameters.** Upgrade to the latest available release when an older Excel schema exposes dollar-sign parameter names that the model provider rejects. The current schema no longer uses those invalid top-level parameter names.
30 -
31 -**Use current versions for column formatting and wrapping.** Generic column wrapping and related sheet operations are available in the current Excel toolkit. If they are missing from the action schema, switch to the latest toolkit version.
docs/content/kb/guide/toolkits-facebook.mdx deleted
-27
@@ -1,27 +0,0 @@
1 ----
2 -title: "Facebook"
3 -description: "Public support knowledge for Facebook."
4 -keywords: ["facebook","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/facebook-troubleshooting","change-the-connected-facebook-or-instagram-account","connect-meta-ads-with-your-own-credentials","facebook-delete-post-failure-can-be-fixed-by-using-the-latest-facebook","facebook-troubleshooting","instagram-webhook-verification-config-is-not-needed-if-composio-has-no","meta-ads-toolkit-exists-missing-apis-should-be-filed-as-feature-reques","meta-ads-toolkit-was-updated-to-api-version-v24-0","whatsapp-connections-require-waba-id-as-generic-id-with-bearer-token-f","whatsapp-template-sending-needs-an-existing-template-and-required-phon"]
5 -sources: [{"sourcePath":"toolkits/facebook/public.md","sourceHeading":"FACEBOOK_DELETE_POST failure can be fixed by using the latest Facebook toolkit version"},{"sourcePath":"toolkits/facebook/public.md","sourceHeading":"Meta OAuth issues can require adding the Composio redirect URI in the Meta app settings"},{"sourcePath":"toolkits/facebook/public.md","sourceHeading":"Facebook or Instagram connections authenticate the account selected in Meta's picker and cannot be repointed server-side"},{"sourcePath":"toolkits/facebook/public.md","sourceHeading":"WhatsApp connections require WABA ID as generic_id, with bearer_token for API-key auth"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["facebook"]
11 -aliases: ["/kb/toolkits/facebook-troubleshooting","change-the-connected-facebook-or-instagram-account","connect-meta-ads-with-your-own-credentials","facebook-delete-post-failure-can-be-fixed-by-using-the-latest-facebook","facebook-troubleshooting","instagram-webhook-verification-config-is-not-needed-if-composio-has-no","meta-ads-toolkit-exists-missing-apis-should-be-filed-as-feature-reques","meta-ads-toolkit-was-updated-to-api-version-v24-0","whatsapp-connections-require-waba-id-as-generic-id-with-bearer-token-f","whatsapp-template-sending-needs-an-existing-template-and-required-phon"]
12 ----
13 -## FACEBOOK_DELETE_POST failure can be fixed by using the latest Facebook toolkit version
14 -
15 -If `FACEBOOK_DELETE_POST` fails on an older pinned toolkit version, try the latest Facebook toolkit version first. Remove the historical pin or pass `latest` according to the SDK/API path being used.
16 -
17 -## Meta OAuth issues can require adding the Composio redirect URI in the Meta app settings
18 -
19 -For Meta/Facebook OAuth failures, verify that the Composio redirect URI is added to the correct redirect URI field in the Meta developer app settings. If the app is using custom credentials, the redirect URI in Meta must match the Composio callback URI used by that auth config. After adding it, retry the connection flow.
20 -
21 -## Facebook or Instagram connections authenticate the account selected in Meta's picker and cannot be repointed server-side
22 -
23 -If the wrong Facebook/Page/Instagram account is connected, remove the existing Composio/Meta app authorization from Facebook's Business Integrations or business tools settings, sign out of other Facebook accounts or use a clean browser profile, then reconnect and choose the correct account/Page/Instagram asset in Meta's picker. Composio cannot manually switch the underlying account for an already-issued Meta token.
24 -
25 -## WhatsApp connections require WABA ID as generic_id, with bearer_token for API-key auth
26 -
27 -For WhatsApp, OAuth2 connection initiation requires `generic_id`, which is the WABA ID. API-key auth requires both `bearer_token` (System User Token) and `generic_id` (WABA ID). Customers can find the WABA ID in the Facebook developer app's WhatsApp API setup, or through Meta APIs such as `/me/businesses` followed by `/{business_id}/owned_whatsapp_business_accounts`. To avoid hardcoding, use hosted auth links so the user can enter required fields during connection.
docs/content/kb/guide/toolkits-fathom.mdx deleted
-19
@@ -1,19 +0,0 @@
1 ----
2 -title: "Fathom"
3 -description: "Public support knowledge for Fathom."
4 -keywords: ["fathom","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/fathom-troubleshooting","fathom-and-granola-mcp-are-supported-meeting-transcription-toolkits-re","fathom-troubleshooting","oauth-authorization-urls-are-provider-specific"]
5 -sources: [{"sourcePath":"toolkits/fathom/public.md","sourceHeading":"Fathom and granola_mcp are supported meeting transcription toolkits; request unsupported tools separately"},{"sourcePath":"toolkits/fathom/public.md","sourceHeading":"OAuth authorization URLs are provider-specific"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["fathom"]
11 -aliases: ["/kb/toolkits/fathom-troubleshooting","fathom-and-granola-mcp-are-supported-meeting-transcription-toolkits-re","fathom-troubleshooting","oauth-authorization-urls-are-provider-specific"]
12 ----
13 -## Fathom and granola_mcp are supported meeting transcription toolkits; request unsupported tools separately
14 -
15 -The `fathom` and `granola_mcp` toolkits are supported. If a requested meeting transcriber is not available, such as Otter, direct the customer to submit the request at `https://request.composio.dev/`.
16 -
17 -## OAuth authorization URLs are provider-specific
18 -
19 -Authorization URLs depend on the provider/toolkit involved in the connection flow. When troubleshooting OAuth redirects, check which provider the auth config and connection flow resolve to before treating a provider-specific authorization domain as inherently incorrect.
docs/content/kb/guide/toolkits-figma.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Figma"
3 -description: "Public support knowledge for Figma."
4 -keywords: ["figma","for-you","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/figma-troubleshooting","figma-429s-can-come-from-figma-provider-limits-use-custom-credentials","figma-token-auth-is-handled-by-composio-customers-do-not-need-a-separa","figma-tools-are-available-across-auth-modes-fetch-available-tools-dyna","figma-troubleshooting","new-figma-scopes-may-require-custom-oauth-api-key-auth-because-default"]
5 -sources: [{"sourcePath":"toolkits/figma/public.md","sourceHeading":"Figma token auth is handled by Composio; customers do not need a separate Bearer-token auth scheme"},{"sourcePath":"toolkits/figma/public.md","sourceHeading":"`FIGMA_EXTRACT_DESIGN_TOKENS` variables may be limited by the customer's Figma plan"},{"sourcePath":"toolkits/figma/public.md","sourceHeading":"Figma 429s can come from Figma/provider limits; use custom credentials for production"},{"sourcePath":"toolkits/figma/public.md","sourceHeading":"Remove deprecated `file_read` from Figma auth configs and reconnect"},{"sourcePath":"toolkits/figma/public.md","sourceHeading":"Figma tools are available across auth modes; fetch available tools dynamically"},{"sourcePath":"toolkits/figma/public.md","sourceHeading":"Common Figma design-token tools include extract, Tailwind conversion, and node fetch"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["figma"]
11 -aliases: ["/kb/toolkits/figma-troubleshooting","figma-429s-can-come-from-figma-provider-limits-use-custom-credentials","figma-token-auth-is-handled-by-composio-customers-do-not-need-a-separa","figma-tools-are-available-across-auth-modes-fetch-available-tools-dyna","figma-troubleshooting","new-figma-scopes-may-require-custom-oauth-api-key-auth-because-default"]
12 ----
13 -Use this guide to configure Figma authentication, discover available tools, and work with design tokens and components.
14 -
15 -## Configure Figma authentication for production
16 -
17 -**Let Composio handle Bearer authorization.** For Figma, customers can provide the supported credentials/token through the toolkit's auth mode, and Composio handles the Bearer authorization header internally. They should not need to manually create a separate Bearer-token auth scheme for normal Figma tool use.
18 -
19 -**Use customer-owned credentials for production rate limits.** If Figma returns 429, verify the response is coming from Figma and review Figma's rate-limit docs. Composio's default Figma app is fine for testing, but production use should use the customer's own Figma credentials to avoid shared-app pressure and to control scopes/rate limits.
20 -
21 -**Remove deprecated scopes before reconnecting.** If a Figma auth config contains the deprecated `file_read` scope, remove it and initiate a new connection.
22 -
23 -## Discover and run Figma tools across auth modes
24 -
25 -Figma tools should be usable regardless of whether the connection uses Composio-managed OAuth, a custom OAuth app, or token/API-key auth. If you cannot find a tool, fetch available tools dynamically and check the auth scopes required by that tool.
26 -
27 -## Work with Figma design tokens and components
28 -
29 -**Check plan access when extracting variables.** Some Figma API features are plan-limited. If `FIGMA_EXTRACT_DESIGN_TOKENS` fails when `include_variables` is enabled, verify your Figma plan/API access. As a workaround, set `include_variables` to false.
30 -
31 -**Use current design-token and component actions.** For Figma design-token and component workflows, use `FIGMA_EXTRACT_DESIGN_TOKENS`, `FIGMA_DESIGN_TOKENS_TO_TAILWIND`, and `FIGMA_GET_FILE_NODES`. The older `FIGMA_GET_COMPONENT` action is deprecated. If a needed Figma tool is missing, submit it through the Composio request portal.
docs/content/kb/guide/toolkits-firecrawl.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Firecrawl"
3 -description: "Public support knowledge for Firecrawl."
4 -keywords: ["firecrawl","for-you","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/firecrawl-troubleshooting","batch-fewer-urls-or-raise-timeout-for-long-firecrawl-scrape-jobs","connect-mcp-sessions-are-tied-to-individual-consumer-accounts-not-a-sh","create-a-firecrawl-api-key-connected-account-with-generic-api-key","firecrawl-api-base-url-is-https-api-firecrawl-dev-v1","firecrawl-search-may-be-hidden-by-default-tool-list-limits","firecrawl-troubleshooting","firecrawl-uses-api-key-auth-not-oauth-provide-a-firecrawl-api-key","use-firecrawl-scrape-or-firecrawl-extract-for-web-content-retrieval"]
5 -sources: [{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Firecrawl uses API-key auth, not OAuth; provide a Firecrawl API key"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Create a Firecrawl API-key connected account with generic_api_key"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"FIRECRAWL_SEARCH may be hidden by default tool list limits"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Batch fewer URLs or raise timeout for long Firecrawl scrape jobs"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Firecrawl API base URL is https://api.firecrawl.dev/v1"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Use FIRECRAWL_SCRAPE or FIRECRAWL_EXTRACT for web-content retrieval"},{"sourcePath":"toolkits/firecrawl/public.md","sourceHeading":"Connect MCP sessions are tied to individual consumer accounts, not a shared workspace"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["firecrawl"]
11 -aliases: ["/kb/toolkits/firecrawl-troubleshooting","batch-fewer-urls-or-raise-timeout-for-long-firecrawl-scrape-jobs","connect-mcp-sessions-are-tied-to-individual-consumer-accounts-not-a-sh","create-a-firecrawl-api-key-connected-account-with-generic-api-key","firecrawl-api-base-url-is-https-api-firecrawl-dev-v1","firecrawl-search-may-be-hidden-by-default-tool-list-limits","firecrawl-troubleshooting","firecrawl-uses-api-key-auth-not-oauth-provide-a-firecrawl-api-key","use-firecrawl-scrape-or-firecrawl-extract-for-web-content-retrieval"]
12 ----
13 -Use this guide to connect Firecrawl with an API key, discover and run its tools, configure scrape endpoints and timeouts, and use it through Connect MCP.
14 -
15 -## Connect Firecrawl with an API key
16 -
17 -**Use API-key auth instead of OAuth.** Firecrawl does not use a Composio-managed OAuth/test connector flow. It is an API-key toolkit, so you need a Firecrawl API key and, in many cases, your own Firecrawl subscription/account. If an MCP client does not prompt for the key, provide it through the connection flow or explicitly tell the agent/client to use the Firecrawl API key for authentication.
18 -
19 -**Create the connected account with `generic_api_key`.** For Firecrawl API-key auth, create the connected account with `authScheme: "API_KEY"` and a value object containing `status: "ACTIVE"` and `generic_api_key: "fc-..."`. The exact required key names can be checked from the toolkit metadata/connection initiation fields.
20 -
21 -## Discover and run Firecrawl tools
22 -
23 -**Increase the tool-list limit when actions are missing.** If `FIRECRAWL_SEARCH` or other Firecrawl tools are missing from a tools list, increase the list limit or paginate. The default list can return only the first 20 tools, so request a higher limit such as `limit=1000` when fetching Firecrawl tools.
24 -
25 -**Choose the retrieval tool that matches the task.** For website content retrieval with Firecrawl, use `FIRECRAWL_SCRAPE` to scrape page content or `FIRECRAWL_EXTRACT` for extraction-style workflows. For broader web search, Composio Search may be a better fit depending on the use case.
26 -
27 -## Configure endpoints and scrape timeouts
28 -
29 -**Batch fewer URLs or raise the timeout for long scrape jobs.** For Firecrawl scrape timeouts, reduce the number of links per request, such as batching 1-2 links at a time for complex pages, or increase the scrape timeout if the tool call supports it. A useful starting value is `timeout: 120000` for roughly a 2-minute timeout.
30 -
31 -**Use the Firecrawl v1 API base URL.** The Firecrawl API base URL is `https://api.firecrawl.dev/v1`. If you must manually enter a base URL to unblock a connection or custom call, use that value. If the toolkit should have supplied it automatically, contact Composio support with the connection details.
32 -
33 -## Use Firecrawl with Connect MCP
34 -
35 -**Connect Firecrawl separately for each consumer account.** For Connect MCP on the For You side, each user's MCP session is tied to their own Composio consumer account, not the shared workspace context. A Firecrawl connection created under one user's account/workspace will not automatically appear for colleagues in Claude. Each colleague should create/connect their own Firecrawl account connection for their individual Connect MCP session.
docs/content/kb/guide/toolkits-gemini.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Gemini"
3 -description: "Public support knowledge for Gemini."
4 -keywords: ["for-you","gemini","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/gemini-troubleshooting","composio-supports-google-gemini-vertex-ai-providers-with-python-suppor","disable-automatic-file-handling-when-gemini-generated-files-should-rem","gemini-can-use-composio-tool-router-through-any-mcp-client","gemini-cli-mcp-issues-may-be-client-side-claude-can-be-a-more-stable-f","gemini-schema-errors-can-come-from-google-s-openapi-vs-json-schema-lim","gemini-toolkit-quota-is-shared","gemini-troubleshooting","gemini-video-generation-should-use-supported-veo-model-names","gemini-wait-for-video-can-fail-with-missing-presigned-url-after-succes","langchain-mcp-tools-are-not-openai-only-and-can-work-with-gemini-capab","use-gemini-get-videos-operation-or-gemini-wait-for-video-before-using","use-newer-gemini-models-such-as-gemini-2-5-flash-instead-of-old-gemini"]
5 -sources: [{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Gemini no-auth/toolkit usage is counted as regular Composio tool calls"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Use newer Gemini models such as `gemini-2.5-flash` instead of old `gemini-1.5-flash` defaults"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Gemini video generation should use supported Veo model names"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Use `GEMINI_WAIT_FOR_VIDEO` before using generated video output"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Disable automatic file handling when Gemini generated files should remain as URLs/content"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Gemini can use Composio Tool Router through any MCP client"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Gemini CLI MCP issues may be client-side; Claude can be a more stable fallback"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Gemini schema errors can come from Google's OpenAPI-vs-JSON-Schema limitations"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"Composio supports Google Gemini/Vertex AI providers, with Python support historically ahead of JS"},{"sourcePath":"toolkits/gemini/public.md","sourceHeading":"LangChain MCP tools are not OpenAI-only and can work with Gemini-capable tool calling"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["gemini"]
11 -aliases: ["/kb/toolkits/gemini-troubleshooting","composio-supports-google-gemini-vertex-ai-providers-with-python-suppor","disable-automatic-file-handling-when-gemini-generated-files-should-rem","gemini-can-use-composio-tool-router-through-any-mcp-client","gemini-cli-mcp-issues-may-be-client-side-claude-can-be-a-more-stable-f","gemini-schema-errors-can-come-from-google-s-openapi-vs-json-schema-lim","gemini-toolkit-quota-is-shared","gemini-troubleshooting","gemini-video-generation-should-use-supported-veo-model-names","gemini-wait-for-video-can-fail-with-missing-presigned-url-after-succes","langchain-mcp-tools-are-not-openai-only-and-can-work-with-gemini-capab","use-gemini-get-videos-operation-or-gemini-wait-for-video-before-using","use-newer-gemini-models-such-as-gemini-2-5-flash-instead-of-old-gemini"]
12 ----
13 -Use this guide to choose supported Gemini models, handle generated media, connect through MCP, and troubleshoot provider compatibility.
14 -
15 -## Choose supported models and handle generated media
16 -
17 -**Use current Gemini model names.** If Gemini tool calls fail with older model names, switch to a currently supported Gemini model. For example, use `gemini-2.5-flash` instead of the older `gemini-1.5-flash`; model availability changes over time.
18 -
19 -**Choose a supported Veo model for video generation.** For Gemini video generation, use supported Veo models such as `veo-3.1-generate-preview`, `veo-3.1-fast-generate-preview`, `veo-3.0-generate-001`, or `veo-3.0-fast-generate-001`. If the default model fails, explicitly pass a current supported Veo model.
20 -
21 -**Wait for asynchronous video generation to complete.** Gemini video generation is asynchronous. Pass the `operation_name` returned by `GEMINI_GENERATE_VIDEOS` to `GEMINI_WAIT_FOR_VIDEO`, which polls for completion and returns the generated video file. The older `GEMINI_GET_VIDEOS_OPERATION` action is deprecated.
22 -
23 -**Disable automatic file handling when outputs should remain as URLs or content.** Composio SDKs automatically handle file upload/download by default. For Gemini generated images or similar file outputs, disable automatic file handling with `autoUploadDownloadFiles: false` / `auto_upload_download_files=False` where supported, or update to a version that supports that option.
24 -
25 -## Connect Gemini through MCP and frameworks
26 -
27 -**Use Tool Router with any compatible MCP client.** Tool Router can be used with any MCP client or framework/LLM that supports tool calling or MCP. For Gemini, initialize Composio with `GeminiProvider`, create a session, then connect to the session MCP URL and headers using a streamable HTTP MCP client.
28 -
29 -**Isolate Gemini CLI-specific MCP failures.** If a Composio MCP server URL returns tools but Gemini CLI still fails, the issue may be in the Gemini client. Try the latest Gemini CLI version and, if needed, compare with another MCP client to isolate whether the failure is client-specific.
30 -
31 -**Use LangChain MCP tools with any capable model.** Composio MCP tools with LangChain are not limited to OpenAI. They can work with any LLM/framework path that supports LangChain function calling capabilities, including Gemini and Claude.
32 -
33 -## Check provider compatibility and tool-call accounting
34 -
35 -**Account for no-auth toolkit calls like regular tool calls.** Gemini no-auth toolkit calls are logged like other toolkit calls and can be tracked in Composio tool logs. Confirm the current plan's tool-call accounting when answering billing questions because pricing can change.
36 -
37 -**Check Google's schema limitations when otherwise-valid tools fail.** Gemini models/providers can have schema compatibility issues because Gemini uses OpenAPI-style schema handling rather than full JSON Schema support in some paths. If a schema works in OpenAI/Claude but fails in Gemini, check provider schema limitations and upgrade Composio/provider SDKs where fixes exist.
38 -
39 -**Verify current language-specific provider support.** Composio supports Google Gemini and Vertex AI providers. Verify the current SDK version and provider documentation when answering implementation-specific questions because language-specific support changes over time.
docs/content/kb/guide/toolkits-github.mdx deleted
-45
@@ -1,45 +0,0 @@
1 ----
2 -title: "GitHub"
3 -description: "Public support knowledge for GitHub."
4 -keywords: ["for-you","github","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/github-troubleshooting","access-token-freshness-when-retrieving-tokens-for-direct-github-operat","connect-a-github-app","github-troubleshooting","github-v2-triggers-do-not-require-creating-a-webhook-endpoint-first","list-github-organizations-and-repositories-for-the-authenticated-user","session-level-tool-allowlists-are-enforced-server-side-at-execution-ti","use-custom-oauth-credentials-for-branded-github-consent-and-redirect-f","why-github-connected-account-tokens-may-show-as-redacted"]
5 -sources: [{"sourcePath":"toolkits/github/public.md","sourceHeading":"GitHub V2 triggers do not require creating a webhook endpoint first"},{"sourcePath":"toolkits/github/public.md","sourceHeading":"List GitHub organizations and repositories for the authenticated user"},{"sourcePath":"toolkits/github/public.md","sourceHeading":"GitHub connected-account tokens are redacted from API responses"},{"sourcePath":"toolkits/github/public.md","sourceHeading":"GitHub organization access can require approval from an organization owner"},{"sourcePath":"toolkits/github/public.md","sourceHeading":"Session-level tool allowlists are enforced server-side at execution time"},{"sourcePath":"toolkits/github/public.md","sourceHeading":"Use custom OAuth credentials for branded GitHub consent and redirect flows"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["github"]
11 -aliases: ["/kb/toolkits/github-troubleshooting","access-token-freshness-when-retrieving-tokens-for-direct-github-operat","connect-a-github-app","github-troubleshooting","github-v2-triggers-do-not-require-creating-a-webhook-endpoint-first","list-github-organizations-and-repositories-for-the-authenticated-user","session-level-tool-allowlists-are-enforced-server-side-at-execution-ti","use-custom-oauth-credentials-for-branded-github-consent-and-redirect-f","why-github-connected-account-tokens-may-show-as-redacted"]
12 ----
13 -## GitHub V2 triggers do not require creating a webhook endpoint first
14 -
15 -GitHub V2 trigger setup does not require a separate webhook endpoint creation step. The webhook URL is automatically provisioned when the trigger instance is created. Skip the `/webhook_endpoints` call and create or update the trigger directly through `/trigger_instances/{slug}/upsert`.
16 -
17 -## List GitHub organizations and repositories for the authenticated user
18 -
19 -Use `GITHUB_LIST_ORGANIZATIONS_FOR_THE_AUTHENTICATED_USER` to list organizations available to the authenticated GitHub user. Then use `GITHUB_LIST_ORGANIZATION_REPOSITORIES` to list repositories for a selected organization. During connection, the user should be able to choose the organization they want to grant access to.
20 -
21 -## GitHub connected-account tokens are redacted from API responses
22 -
23 -Provider tokens are redacted from connected-account API responses for both Composio-managed and customer-owned auth configs. Use Composio tool execution or Proxy Execute when a workflow needs to call GitHub; do not build a flow that reads the OAuth token from connected-account data.
24 -
25 -## GitHub organization access can require approval from an organization owner
26 -
27 -If a GitHub connection works for personal repositories but cannot access an
28 -organization, check whether that organization restricts OAuth app access. The
29 -user can open GitHub **Settings → Applications → Authorized OAuth Apps**, select
30 -the OAuth app, and request access for the organization. An organization owner
31 -must approve the request in GitHub; reconnecting in Composio does not bypass the
32 -organization's policy.
33 -
34 -GitHub documents the member request flow at
35 -[https://docs.github.com/en/account-and-profile/how-tos/organization-membership/requesting-organization-approval-for-oauth-apps](https://docs.github.com/en/account-and-profile/how-tos/organization-membership/requesting-organization-approval-for-oauth-apps)
36 -and the owner approval flow at
37 -[https://docs.github.com/en/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization](https://docs.github.com/en/organizations/managing-oauth-access-to-your-organizations-data/approving-oauth-apps-for-your-organization).
38 -
39 -## Session-level tool allowlists are enforced server-side at execution time
40 -
41 -Session-level restrictions are enforced server-side at execution time. When a session is configured with `toolkits`, `tools`, or `tags`, every execution request is validated against the enabled or disabled toolkit list, per-toolkit tool list, and tag filters. Disabled tools are filtered from search results, and execution is blocked before the provider API call if the tool fails validation.
42 -
43 -## Use custom OAuth credentials for branded GitHub consent and redirect flows
44 -
45 -Composio supports white-labeling the hosted auth page by customizing the logo and app name in Project Settings > Auth Screen. For provider OAuth consent screens such as GitHub, use your own OAuth app credentials so the provider consent screen shows your brand instead of Composio's shared OAuth app. Redirect URLs can also be routed through your own domain so users do not see a Composio domain during the redirect path.
docs/content/kb/guide/toolkits-gmail.mdx deleted
-67
@@ -1,67 +0,0 @@
1 ----
2 -title: "Gmail"
3 -description: "Public support knowledge for Gmail."
4 -keywords: ["for-you","gmail","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/gmail-troubleshooting","configure-gmail-scopes-on-managed-auth-config-as-a-comma-joined-scopes","create-gmail-filters-scope","filter-gmail-new-message-trigger-by-label-query-instead-of-label-ids","for-gmail-attachments-over-mcp-upload-files-before-tool-execution","gmail-attachments-can-make-send-email-slow-enough-to-hit-sdk-request-t","gmail-send-email-accepts-at-least-one-of-to-cc-or-bcc","gmail-send-is-granular-but-sensitive-mail-google-com-gives-full-access","gmail-troubleshooting","patch-gmail-label-colors-with-background-color-and-accepted-color-valu","reduce-gmail-fetch-payload-size","send-gmail-from-a-send-as-alias","use-gmail-label-ids-not-label-names-for-label-operations","use-googlesuper-for-one-google-auth-across-gmail-calendar-drive-style","use-latest-or-v3-1-for-newer-gmail-settings-tools","verbose-gmail-thread-results-cannot-select-custom-fields-and-may-not-b"]
5 -sources: [{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Use `latest` or v3.1 for newer Gmail settings tools"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Create Gmail custom OAuth auth config, then initiate a connection with callback URL"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Creating Gmail filters requires `gmail.settings.basic`"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"`gmail.send` is granular but sensitive; `mail.google.com` gives full access"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Configure Gmail scopes on managed auth config as a comma-joined scopes string"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Avoid `gmail.metadata` when fetching full Gmail email content"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Use `me` for Gmail `user_id` in tool calls"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"`GMAIL_SEND_EMAIL` accepts at least one of `to`, `cc`, or `bcc`"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"For Gmail attachments over MCP, upload files before tool execution"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Gmail attachment sends can outlast a client timeout; verify before retrying"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Reduce Gmail fetch payload size with `include_payload=false`, `verbose=false`, `only_ids`, query, and limits"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Use `from_email` to select Gmail send-as alias"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Use Gmail label IDs, not label names, for label operations"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Patch Gmail label colors with `background_color` and accepted color values"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Filter Gmail new-message trigger by label/query instead of label IDs"},{"sourcePath":"toolkits/gmail/public.md","sourceHeading":"Use `googlesuper` for one Google auth across Gmail, Calendar, Drive-style use cases"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["gmail"]
11 -aliases: ["/kb/toolkits/gmail-troubleshooting","configure-gmail-scopes-on-managed-auth-config-as-a-comma-joined-scopes","create-gmail-filters-scope","filter-gmail-new-message-trigger-by-label-query-instead-of-label-ids","for-gmail-attachments-over-mcp-upload-files-before-tool-execution","gmail-attachments-can-make-send-email-slow-enough-to-hit-sdk-request-t","gmail-send-email-accepts-at-least-one-of-to-cc-or-bcc","gmail-send-is-granular-but-sensitive-mail-google-com-gives-full-access","gmail-troubleshooting","patch-gmail-label-colors-with-background-color-and-accepted-color-valu","reduce-gmail-fetch-payload-size","send-gmail-from-a-send-as-alias","use-gmail-label-ids-not-label-names-for-label-operations","use-googlesuper-for-one-google-auth-across-gmail-calendar-drive-style","use-latest-or-v3-1-for-newer-gmail-settings-tools","verbose-gmail-thread-results-cannot-select-custom-fields-and-may-not-b"]
12 ----
13 -Use this guide to configure Gmail authentication, send and fetch messages, work with attachments and labels, and set up new-message triggers.
14 -
15 -## Configure Gmail OAuth, scopes, and toolkit versions
16 -
17 -**Use `latest` or v3.1 for newer Gmail settings tools.** The v3 execute endpoint can default to base toolkit version `00000000_00` when no version is specified. For newer Gmail tools like `GMAIL_PATCH_SEND_AS`, `GMAIL_LIST_SEND_AS`, and `GMAIL_GET_VACATION_SETTINGS`, pass `version: "latest"` in the execute body or use the v3.1 endpoint, which defaults to latest.
18 -
19 -**Create the auth config before initiating a connection.** Create the Gmail auth config first with the custom OAuth credentials, then initiate a connected account using that auth config. The callback URL is supplied during connection initiation, while the OAuth client ID/secret and redirect URI live on the auth config.
20 -
21 -**Choose scopes based on the actions and data required.** When creating the Gmail auth config, pass the desired Gmail scopes in `credentials.scopes`, typically as a comma-joined string. Example scopes include `gmail.send`, `gmail.readonly`, `gmail.compose`, `gmail.modify`, and `gmail.labels`.
22 -
23 -Gmail filter creation maps to the Gmail API `users.settings.filters.create` endpoint: `POST /gmail/v1/users/{userId}/settings/filters`. Google lists `https://www.googleapis.com/auth/gmail.settings.basic` as the required OAuth scope for this endpoint, and the current Composio `GMAIL_CREATE_FILTER` action declares the same single required scope. Google must approve this scope for the OAuth app used by the connection. If the consent screen blocks an unverified scope, use an OAuth app that is verified for `gmail.settings.basic` and reconnect.
24 -
25 -`https://www.googleapis.com/auth/gmail.send` can send messages, but it is a granular sensitive scope and requires Google verification. The broader `https://mail.google.com/` scope gives full mailbox access and can cover send use cases, but it is broader than many customers want.
26 -
27 -The Gmail metadata scope cannot be used when requesting full email content. Remove `https://www.googleapis.com/auth/gmail.metadata` and use a scope that allows message content access, such as `https://mail.google.com/`, when full payload/body data is needed.
28 -
29 -**Use Google Super for one Google connection across services.** Google Super owns the canonical multi-service authentication guidance. See [Google Super is a unified Google Workspace toolkit](/kb/guide/toolkits-googlesuper).
30 -
31 -## Address and send Gmail messages
32 -
33 -Check tool slugs and input parameter tables in the [Gmail toolkit catalog](/toolkits/gmail) before writing a tool call.
34 -
35 -**Use `me` for the authenticated user.** For Gmail tool calls, `me` can be used as the `user_id` to refer to the authenticated connected account.
36 -
37 -**Provide at least one recipient channel.** `GMAIL_SEND_EMAIL` no longer needs a single required recipient field. At least one recipient channel such as `to` / `recipient_email`, `cc`, or `bcc` can be supplied, which keeps the tool flexible for different email composition flows.
38 -
39 -For hosted MCP / Tool Router calls through `COMPOSIO_MULTI_EXECUTE_TOOL`, put recipient fields inside the nested tool `arguments` object. Prefer `recipient_email` for the first To recipient and `extra_recipients` for additional To recipients unless the current schema explicitly exposes another shape.
40 -
41 -If the connection is active but the action returns `At least one of 'to' (or 'recipient_email'), 'cc', or 'bcc' must be provided`, the tool did not receive a recipient channel and failed before Gmail API execution. Retry with the exact nested `recipient_email` shape; if it still fails, provide a fresh request ID for investigation.
42 -
43 -**Select a send-as alias with `from_email`.** Use the `from_email` parameter on `GMAIL_SEND_EMAIL` to choose the Gmail send-as alias.
44 -
45 -## Send attachments safely
46 -
47 -**Upload files before tool execution.** Temporary S3/file instances are short-lived. Use `files.upload` before tool execution via the SDK or MCP flow, then pass the resulting `FileUploadable`/uploaded file object to the agent/tool call.
48 -
49 -**Verify a timed-out send before retrying.** `GMAIL_SEND_EMAIL` accepts attachments as uploaded Composio file references, not signed URLs or JSON strings. The action downloads the uploaded file, builds the MIME message, base64-url encodes it, and posts it to Gmail. Attachment sends can therefore take materially longer than small text-only sends.
50 -
51 -Current Python and TypeScript SDKs do not automatically retry non-idempotent tool executions. However, a client timeout can still occur after Gmail accepted the message. If `GMAIL_SEND_EMAIL` hangs or creates duplicate sends with attachments:
52 -
53 -- If the log is a fast 400 validation error, verify the `attachment` argument is an object/list with `name`, `mimetype`, and `s3key`.
54 -- If the client timed out, inspect the Composio execution log or Gmail Sent folder before retrying manually.
55 -- If the client is older than Python SDK 0.16.0 or TypeScript SDK 0.14.0, upgrade before investigating SDK-level automatic retries.
56 -
57 -## Fetch messages and manage labels
58 -
59 -**Reduce fetch payload size.** For Gmail fetch/list flows, set `include_payload=false` and `verbose=false` where supported. For very lightweight flows, use `only_ids=true` and then fetch selected messages separately. Also use `max_results` and Gmail `query` filters to keep result sets small.
60 -
61 -**Use label IDs for label operations.** For Gmail label operations and trigger label filters that require IDs, pass the label ID rather than the display name. Use `GMAIL_LIST_LABELS` to retrieve IDs.
62 -
63 -**Use accepted Gmail color values when patching labels.** To patch a label color, use the label ID and pass background color as an object field such as `{ "background_color": "#FFFF0000" }`. Gmail only accepts specific label color values from the Gmail API reference.
64 -
65 -## Configure Gmail new-message trigger filters
66 -
67 -Use a Gmail query such as `label:sent OR label:category_personal` to filter matching messages. This avoids depending on label IDs for that trigger path.
docs/content/kb/guide/toolkits-gong.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Gong"
3 -description: "Public support knowledge for Gong."
4 -keywords: ["for-you","gong","platform","auth-config","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/gong-triggers-were-planned-requested-but-may-not-be-available-for-ever","/kb/toolkits/gong-troubleshooting","gong-base-url-differs-by-customer-and-should-be-provided-at-connection","gong-connection-initiation-can-use-basic-auth-fields-access-key-access","gong-mcp-tool-scopes-can-be-read-from-tool-annotations-in-the-tools-ap","gong-oauth2-support-may-need-to-be-treated-as-a-feature-request-if-not","gong-triggers-were-planned-requested-but-may-not-be-available-for-ever","gong-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/gong/public.md","sourceHeading":"Gong base URL differs by customer and should be provided at connection time"},{"sourcePath":"toolkits/gong/public.md","sourceHeading":"Gong connection initiation can use Basic auth fields: access key, access key secret, and Gong URL"},{"sourcePath":"toolkits/gong/public.md","sourceHeading":"Gong MCP tool scopes can be read from tool annotations in the tools API"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["gong"]
11 -aliases: ["/kb/toolkits/gong-triggers-were-planned-requested-but-may-not-be-available-for-ever","/kb/toolkits/gong-troubleshooting","gong-base-url-differs-by-customer-and-should-be-provided-at-connection","gong-connection-initiation-can-use-basic-auth-fields-access-key-access","gong-mcp-tool-scopes-can-be-read-from-tool-annotations-in-the-tools-ap","gong-oauth2-support-may-need-to-be-treated-as-a-feature-request-if-not","gong-triggers-were-planned-requested-but-may-not-be-available-for-ever","gong-troubleshooting"]
12 ----
13 -## Gong base URL differs by customer and should be provided at connection time
14 -
15 -Gong's base URL can differ per user/customer. Avoid hardcoding a single Gong base URL in a shared auth config for all users; collect and pass the user's `gong_url`/base URL when initiating the connected account.
16 -
17 -## Gong connection initiation can use Basic auth fields: access key, access key secret, and Gong URL
18 -
19 -For Gong Basic auth, collect the access key as username, access key secret as password, and the customer's Gong URL/base URL. Pass those fields when initiating the connected account; hosted auth can also collect required fields for the customer instead of manually building the frontend form.
20 -
21 -## Gong MCP tool scopes can be read from tool annotations in the tools API
22 -
23 -For Gong MCP tools, scopes are exposed through the `annotations` field from the `listTools` API per the newer MCP spec. To determine Gong scopes, inspect tool annotations from the tools API instead of relying only on static docs.
docs/content/kb/guide/toolkits-google-analytics.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Google Analytics"
3 -description: "Public support knowledge for Google Analytics."
4 -keywords: ["for-you","google_analytics","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-analytics-troubleshooting","add-google-analytics-to-an-mcp-config-as-a-selected-tool-toolkit","empty-google-analytics-reports-may-be-provider-data-availability-rathe","google-analytics-troubleshooting","old-google-analytics-mcp-could-show-0-actions-because-it-was-auth-only","use-latest-toolkit-version-when-google-analytics-tools-return-toolnotf"]
5 -sources: [{"sourcePath":"toolkits/google_analytics/public.md","sourceHeading":"Use latest toolkit version when Google Analytics tools return ToolNotFound or only a few tools"},{"sourcePath":"toolkits/google_analytics/public.md","sourceHeading":"Add Google Analytics to an MCP config as a selected tool/toolkit"},{"sourcePath":"toolkits/google_analytics/public.md","sourceHeading":"Empty Google Analytics reports may be provider data availability rather than Composio failure"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["google_analytics"]
11 -aliases: ["/kb/toolkits/google-analytics-troubleshooting","add-google-analytics-to-an-mcp-config-as-a-selected-tool-toolkit","empty-google-analytics-reports-may-be-provider-data-availability-rathe","google-analytics-troubleshooting","old-google-analytics-mcp-could-show-0-actions-because-it-was-auth-only","use-latest-toolkit-version-when-google-analytics-tools-return-toolnotf"]
12 ----
13 -## Use latest toolkit version when Google Analytics tools return ToolNotFound or only a few tools
14 -
15 -If Google Analytics tools return `ToolNotFound` or the tools API only returns a small subset of Google Analytics tools, pass the latest toolkit version. For tools listing, use query params like `toolkit_versions=latest&toolkit_slug=google_analytics&limit=1000`. Older pinned/default versions can expose far fewer tools than the latest version.
16 -
17 -## Add Google Analytics to an MCP config as a selected tool/toolkit
18 -
19 -To use Google Analytics through MCP, create an MCP config with Google Analytics selected, or edit an existing MCP config and add Google Analytics as a tool/toolkit. Then follow the MCP quickstart to connect and use the generated MCP configuration.
20 -
21 -## Empty Google Analytics reports may be provider data availability rather than Composio failure
22 -
23 -If Google Analytics report tools return no data or unexpected data, compare the same property, date range, dimensions, and metrics through Google Analytics itself or a Proxy Execute request. If the provider returns the same empty result, it is likely a data-availability or query issue. If the equivalent provider request works but the Composio tool does not, contact Composio support with the log ID and a redacted comparison. Never extract or share a token from connected-account data.
docs/content/kb/guide/toolkits-google-calendar.mdx deleted
-43
@@ -1,43 +0,0 @@
1 ----
2 -title: "Google Calendar"
3 -description: "Public support knowledge for Google Calendar."
4 -keywords: ["for-you","google_calendar","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/google-calendar-troubleshooting","calendar-events-scope-is-required-for-event-list-fetch-flows","composio-does-not-support-org-wide-google-workspace-authentication-for","create-a-google-calendar-integration-to-access-tools-and-triggers","google-calendar-trigger-moved-toward-polling-for-more-verbose-payloads","google-calendar-troubleshooting","updating-rsvp-status-has-an-attendee-list-api-limitation","use-find-free-slots-when-you-need-processed-availability-free-busy-doe","use-latest-google-calendar-toolkit-version-when-filters-are-ignored","use-primary-for-google-calendar-id","use-trigger-types-endpoint-to-retrieve-google-calendar-trigger-info-pr"]
5 -sources: [{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Create a Google Calendar integration to access tools and triggers"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Updating RSVP status has an attendee-list API limitation"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Canceled/deleted event trigger sends payloads for canceled or deleted events"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Multiple triggers for the same slug/user can target different calendar IDs"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"`calendar.events` scope is required for event list/fetch flows"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Google Calendar triggers now return full event data instead of only an ID"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Google Calendar trigger moved toward polling for more verbose payloads"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Use trigger-types endpoint to retrieve Google Calendar trigger info programmatically"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Use Find Free Slots when you need processed availability; free/busy does not do timezone processing"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Use `primary` as calendar ID; `me` is not valid for calendar ID"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Use latest Google Calendar toolkit version when filters are ignored"},{"sourcePath":"toolkits/google_calendar/public.md","sourceHeading":"Google Calendar meeting link is returned in `hangout_link`"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googlecalendar"]
11 -aliases: ["/kb/authentication/google-calendar-troubleshooting","calendar-events-scope-is-required-for-event-list-fetch-flows","composio-does-not-support-org-wide-google-workspace-authentication-for","create-a-google-calendar-integration-to-access-tools-and-triggers","google-calendar-trigger-moved-toward-polling-for-more-verbose-payloads","google-calendar-troubleshooting","updating-rsvp-status-has-an-attendee-list-api-limitation","use-find-free-slots-when-you-need-processed-availability-free-busy-doe","use-latest-google-calendar-toolkit-version-when-filters-are-ignored","use-primary-for-google-calendar-id","use-trigger-types-endpoint-to-retrieve-google-calendar-trigger-info-pr"]
12 ----
13 -Use this guide to connect Google Calendar, work with event data and availability, configure triggers, and troubleshoot version-specific behavior.
14 -
15 -## Connect a Google Calendar account
16 -
17 -Create a Google Calendar integration/auth config, connect the account, and then use the Google Calendar toolkit's tools and triggers through that connected account.
18 -
19 -Ensure the connected account has `https://www.googleapis.com/auth/calendar.events` when calling event-list or event-fetch tools that require event access.
20 -
21 -## Work with events and availability
22 -
23 -**Update RSVP status with the attendee-list limitation in mind.** Google Calendar can limit RSVP/status updates when an event has multiple attendees. Update the authenticated user's RSVP and then re-add the attendees, or resend the attendee list with the updated status.
24 -
25 -**Use Find Free Slots for processed availability.** Query-free/busy returns provider data without extra processing such as timezone handling, so callers using free/busy may need to process it themselves.
26 -
27 -**Use `primary` as the calendar ID.** For Google Calendar tools, use a calendar ID such as `primary`; `me` is not a valid Google Calendar ID.
28 -
29 -**Read generated meeting links from `hangout_link`.** After creating or updating a calendar event with conferencing, read the generated meeting URL from the response's `hangout_link` field.
30 -
31 -## Configure Google Calendar triggers
32 -
33 -**Handle canceled or deleted events.** `GOOGLECALENDAR_EVENT_CANCELED_DELETED_TRIGGER` sends a payload when an event is canceled or deleted.
34 -
35 -**Create separate trigger instances for separate calendars.** Multiple triggers for the same trigger slug and user are supported when each trigger is configured for a different `calendarId`.
36 -
37 -**Expect full event data from newer triggers.** The newer Google Calendar new-event trigger payload includes complete event data rather than only the event ID. Google Calendar trigger behavior moved from webhook-style delivery toward polling so payloads can include more detail and require less follow-up processing. Existing trigger flows were preserved while polling could be introduced separately where needed.
38 -
39 -**Retrieve trigger metadata programmatically.** Use the trigger-types endpoint to retrieve Google Calendar trigger metadata programmatically, and use the triggers documentation for setup guidance.
40 -
41 -## Troubleshoot ignored event filters
42 -
43 -Older pinned Google Calendar toolkit versions can drop or remap filters such as `timeMin` and `timeMax` before the request reaches Google. Use the latest toolkit version or v3.1/latest behavior when filter changes produce identical results.
docs/content/kb/guide/toolkits-google-classroom.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "Google Classroom"
3 -description: "Public OAuth and connection troubleshooting for Google Classroom."
4 -keywords: ["for-you","google_classroom","oauth","platform","scopes","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-classroom-troubleshooting","enable-the-google-classroom-api-for-custom-oauth","google-blocks-sensitive-gmail-scopes","google-classroom-troubleshooting","resolve-401-errors-on-tool-calls","resolve-an-app-is-blocked-connection-error","resolve-an-app-is-blocked-connection-error-2","resolve-error-400-invalid-scope","set-up-custom-google-oauth-credentials","this-app-is-blocked-means-the-requested-google-scope-is-not-verified-o"]
5 -sources: [{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Set up custom Google OAuth credentials"},{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Resolve an \"App is blocked\" connection error"},{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Enable the Google Classroom API for custom OAuth"},{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Resolve `Error 400: invalid_scope`"},{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Choose managed or customer-owned Google OAuth"},{"sourcePath":"toolkits/google_classroom/public.md","sourceHeading":"Resolve 401 errors on tool calls"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["google_classroom"]
11 -aliases: ["/kb/toolkits/google-classroom-troubleshooting","enable-the-google-classroom-api-for-custom-oauth","google-blocks-sensitive-gmail-scopes","google-classroom-troubleshooting","resolve-401-errors-on-tool-calls","resolve-an-app-is-blocked-connection-error","resolve-an-app-is-blocked-connection-error-2","resolve-error-400-invalid-scope","set-up-custom-google-oauth-credentials","this-app-is-blocked-means-the-requested-google-scope-is-not-verified-o"]
12 ----
13 -Use this guide to choose managed or customer-owned Google OAuth for Google Classroom and troubleshoot consent, scope, or token failures.
14 -
15 -## Configure Google OAuth for Google Classroom
16 -
17 -**Follow the Google Apps credential setup guide for custom OAuth.** For a step-by-step guide to creating and configuring Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
18 -
19 -**Enable the Google Classroom API for custom OAuth.** Enable the Google Classroom API in the Google Cloud project that owns the credentials. After enabling it under **APIs & Services**, wait a few minutes and retry.
20 -
21 -**Choose managed or customer-owned OAuth.** Use Composio-managed OAuth for the standard connection flow. Use a custom Google OAuth app when you need control over scopes, consent-screen branding, or Google Cloud project policy. For custom OAuth, configure the app name and branding in that project and use the redirect URL shown by Composio's current auth-config flow.
22 -
23 -## Troubleshoot Google Classroom OAuth and tool calls
24 -
25 -**Remove unverified scopes when Google reports “App is blocked.”** This error usually means the OAuth client is requesting scopes that Google has not verified for that client. Remove additional scopes beyond the defaults, or use a custom OAuth app and submit the scopes for verification.
26 -
27 -**Validate scopes when OAuth returns `Error 400: invalid_scope`.** Verify the requested scopes and their formatting against the [Google OAuth scopes documentation](https://developers.google.com/identity/protocols/oauth2).
28 -
29 -**Reconnect when tool calls return 401.** A 401 usually means the access token is no longer valid. The user may have revoked access, changed password or two-factor settings, been affected by an administrator policy, or exceeded Google's refresh-token limit. Re-authenticate the connected account and retry.
docs/content/kb/guide/toolkits-google-maps.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Google Maps"
3 -description: "Public support knowledge for Google Maps."
4 -keywords: ["for-you","google_maps","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-maps-troubleshooting","deprecated-geocoding-api-is-not-the-google-maps-toolkit-tool-to-use","google-maps-apis-may-require-billing-and-quota-management-in-gcp","google-maps-oauth-can-be-blocked-by-sensitive-cloud-platform-scope","google-maps-troubleshooting","maps-embed-api-requires-api-key-authentication","recreate-google-maps-auth-configs-after-default-oauth-app-updates","validate-places-includedtypes-against-google-s-supported-place-types"]
5 -sources: [{"sourcePath":"toolkits/google_maps/public.md","sourceHeading":"Maps Embed API requires API-key authentication"},{"sourcePath":"toolkits/google_maps/public.md","sourceHeading":"Google Maps OAuth can be blocked by sensitive cloud-platform scope"},{"sourcePath":"toolkits/google_maps/public.md","sourceHeading":"Validate Places `includedTypes` against Google's supported place types"},{"sourcePath":"toolkits/google_maps/public.md","sourceHeading":"Deprecated `GEOCODING_API` is not the Google Maps toolkit tool to use"},{"sourcePath":"toolkits/google_maps/public.md","sourceHeading":"Google Maps APIs may require billing and quota management in GCP"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["google_maps"]
11 -aliases: ["/kb/toolkits/google-maps-troubleshooting","deprecated-geocoding-api-is-not-the-google-maps-toolkit-tool-to-use","google-maps-apis-may-require-billing-and-quota-management-in-gcp","google-maps-oauth-can-be-blocked-by-sensitive-cloud-platform-scope","google-maps-troubleshooting","maps-embed-api-requires-api-key-authentication","recreate-google-maps-auth-configs-after-default-oauth-app-updates","validate-places-includedtypes-against-google-s-supported-place-types"]
12 ----
13 -## Maps Embed API requires API-key authentication
14 -
15 -`GOOGLE_MAPS_MAPS_EMBED_API` requires API-key authentication. Use an auth config whose auth mode is `api-key`, or pass the `api_key` parameter directly when making the tool call.
16 -
17 -## Google Maps OAuth can be blocked by sensitive cloud-platform scope
18 -
19 -Check whether the OAuth app requests the sensitive `https://www.googleapis.com/auth/cloud-platform` scope. If the Google OAuth app has not been verified, users who are not listed as test users and are outside the registering organization can be blocked by Google. Either complete Google verification or ensure the affected users are allowed test/org users for that OAuth app.
20 -
21 -## Validate Places `includedTypes` against Google's supported place types
22 -
23 -For Google Maps Places requests, `includedTypes` must use values supported by Google's Places API. If a request fails with an invalid argument around `includedTypes`, compare the value against Google's supported place type lists and replace unsupported values before retrying.
24 -
25 -## Deprecated `GEOCODING_API` is not the Google Maps toolkit tool to use
26 -
27 -`GEOCODING_API` belongs to a different toolkit and has been deprecated. Do not require it as part of normal `google_maps` toolkit usage; use the current Google Maps toolkit tool slugs instead.
28 -
29 -## Google Maps APIs may require billing and quota management in GCP
30 -
31 -Most Google APIs used through Composio are generally free to access, but Google Maps is an exception: Maps APIs can require billing on the Google Cloud project. If usage exceeds limits, customers may need to request higher limits in their own Google project.
docs/content/kb/guide/toolkits-googleads.mdx deleted
-52
@@ -1,52 +0,0 @@
1 ----
2 -title: "Google Ads"
3 -description: "Public support knowledge for Google Ads."
4 -keywords: ["for-you","googleads","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-ads-troubleshooting","custom-google-oauth-apps-need-callback-routing-through-the-customer-s","google-ads-campaign-mutate-invalid-argument","google-ads-developer-token-belongs-on-the-auth-config","google-ads-oauth-callback-token-exchange-failures-usually-point-to-bad","google-ads-resource-exhausted-errors","google-ads-toolkit-versions-should-be-passed-without-the-dashboard-v-p","google-ads-troubleshooting","older-sdk-workaround-passed-google-ads-developer-token-and-customer-id","target-a-google-ads-sub-account"]
5 -sources: [{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Google Ads developer token now belongs on the auth config, not connection initiation"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Google Ads API requires both OAuth access token and developer token"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Google Ads toolkit versions should be passed without the dashboard `v` prefix"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Google Ads MCC/sub-account customer ID targeting is supported"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Campaign mutate 400s can be caused by unsupported inline Campaign fields"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Google Ads OAuth callback token-exchange failures usually point to incorrect credentials"},{"sourcePath":"toolkits/googleads/public.md","sourceHeading":"Custom Google OAuth apps need callback routing through the customer's domain for branded consent"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googleads"]
11 -aliases: ["/kb/toolkits/google-ads-troubleshooting","custom-google-oauth-apps-need-callback-routing-through-the-customer-s","google-ads-campaign-mutate-invalid-argument","google-ads-developer-token-belongs-on-the-auth-config","google-ads-oauth-callback-token-exchange-failures-usually-point-to-bad","google-ads-resource-exhausted-errors","google-ads-toolkit-versions-should-be-passed-without-the-dashboard-v-p","google-ads-troubleshooting","older-sdk-workaround-passed-google-ads-developer-token-and-customer-id","target-a-google-ads-sub-account"]
12 ----
13 -## Google Ads developer token now belongs on the auth config, not connection initiation
14 -
15 -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.
16 -
17 -## Google Ads API requires both OAuth access token and developer token
18 -
19 -Google Ads API requests require both an OAuth access token and a Google Ads developer token. For production reliability and isolated provider quota, customers should use their own Google Ads developer token where possible.
20 -
21 -## Google Ads toolkit versions should be passed without the dashboard `v` prefix
22 -
23 -The SDK expects toolkit version strings without the dashboard's leading `v`. If the dashboard shows `v<version>`, pass `<version>` in `toolkitVersions` or per-execution `version`. `dangerouslySkipVersionCheck` is a per-execution option inside the `tools.execute()` payload, not a constructor option. Sessions can manage toolkit versions automatically if the customer migrates to session-based execution.
24 -
25 -## Google Ads MCC/sub-account customer ID targeting is supported
26 -
27 -The Google Ads toolkit now correctly supports an optional per-call `customer_id` for customer-scoped tools.
28 -
29 -- Pass the child/subaccount customer ID as `customer_id`; it becomes the target account in the Google Ads request path.
30 -- If `customer_id` is omitted, the tool falls back to the Customer ID stored on the connection.
31 -- When the requested customer differs from the connection Customer ID, the connection Customer ID can supply the MCC/manager context for Google's `login-customer-id` header unless that header is already present.
32 -- `GOOGLEADS_LIST_ACCESSIBLE_CUSTOMERS` is for account discovery. It can return accessible IDs, but later customer-scoped tools still need a selected target customer ID.
33 -
34 -If the request still fails, contact Composio support with the exact tool, request/log ID, manager/MCC customer ID, child customer ID, and Google error. The customer-ID override is already supported, so do not troubleshoot this as a pending feature.
35 -
36 -## Campaign mutate 400s can be caused by unsupported inline Campaign fields
37 -
38 -`GOOGLEADS_MUTATE_CAMPAIGNS` may fail with Google Ads 400 `INVALID_ARGUMENT` errors such as `Unknown name "dailyBudget" at operations[0].update` or `Unknown name "targetedLocations" ... Cannot find field`. These failures happen when the request includes fields that are not valid inline Campaign resource fields.
39 -
40 -Do not treat these as OAuth failures. Check the tool execution log for rejected payload fields. Google Ads does not accept `daily_budget`, `targeted_locations`, `exclusion_locations`, and related date/budget/location fields directly on the Campaign mutate body.
41 -
42 -Remove those inline fields and treat the error as a request-shape issue rather than an OAuth failure. A real daily budget requires a CampaignBudget resource (`campaignBudgets:mutate`) and then passing the CampaignBudget resource name through `campaign_budget`. Location targeting belongs in CampaignCriterion mutations, not inline Campaign fields.
43 -
44 -Example response: "The failure is in the Google Ads campaign-mutate payload shape, not your connection. Some inline campaign fields are being sent in a form that Google Ads rejects. Use CampaignBudget and CampaignCriterion mutations for budget and location targeting instead."
45 -
46 -## Google Ads OAuth callback token-exchange failures usually point to incorrect credentials
47 -
48 -The `OAuth callback failed during token exchange` error usually means the credentials used to complete the auth flow are incorrect, most often the client secret. Re-enter or update the client secret in the Google Ads auth config, make sure there are no leading/trailing spaces, and initiate a new connection.
49 -
50 -## Custom Google OAuth apps need callback routing through the customer's domain for branded consent
51 -
52 -For Google toolkits, creating a new authConfig with the customer's OAuth app credentials is not enough for full white-label consent. They also need to route the callback through their own domain using their own redirect URI so Google displays the configured consent screen for that OAuth app.
docs/content/kb/guide/toolkits-googlebigquery.mdx deleted
-24
@@ -1,24 +0,0 @@
1 ----
2 -title: "Google BigQuery"
3 -description: "Current authentication guidance for the Google BigQuery toolkit."
4 -keywords: ["for-you","googlebigquery","oauth","platform","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/googlebigquery/public.md","sourceHeading":"BigQuery supports managed OAuth2, custom OAuth2, and service-account auth"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["googlebigquery"]
11 -aliases: []
12 ----
13 -## BigQuery supports managed OAuth2, custom OAuth2, and service-account auth
14 -
15 -Use Composio-managed OAuth for the standard connection flow. Use a custom Google
16 -OAuth app when you need control over scopes, consent-screen branding,
17 -or Google Cloud project policy. Service-account authentication is also available;
18 -grant the service account only the BigQuery permissions required by the intended
19 -tools.
20 -
21 -If Google blocks an OAuth consent flow, check the OAuth app's verification,
22 -test-user, organizational-policy, and requested-scope settings before treating
23 -the failure as a Composio problem. Generate a fresh auth link after correcting
24 -the Google Cloud configuration.
docs/content/kb/guide/toolkits-googledocs.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Google Docs"
3 -description: "Public support knowledge for Google Docs."
4 -keywords: ["for-you","googledocs","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-docs-troubleshooting","google-docs-tab-level-read-and-edit-is-supported-by-specific-google-do","google-docs-troubleshooting","google-sensitive-scopes-can-cause-app-blocked-errors-unless-the-oauth","googledocs-create-document-markdown-accepts-github-flavored-markdown-a","managed-google-oauth-tokens-stay-redacted-custom-oauth-is-needed-for-r","multiple-google-accounts-require-multi-account-support-or-distinct-con","platform-connections-are-isolated-from-for-you-connect-mcp-connections","specify-google-auth-config-ids-at-session-creation-so-manage-connectio","tool-router-v2-sessions-require-connected-accounts-to-belong-to-the-sa"]
5 -sources: [{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"`GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown and HTML tables"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Google Docs tab-level read and edit is supported by specific Google Docs tools"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Google Docs supports managed and customer-owned OAuth2"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Google sensitive scopes can cause app-blocked errors unless the OAuth app is verified"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Google OAuth tokens are redacted from connected-account responses"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Multiple Google accounts require explicit multi-account selection"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Tool Router v2 sessions require connected accounts to belong to the same user/entity"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Specify Google auth config IDs at session creation so Manage Connection uses the intended configs"},{"sourcePath":"toolkits/googledocs/public.md","sourceHeading":"Platform connections are isolated from For You / Connect MCP connections"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googledocs"]
11 -aliases: ["/kb/toolkits/google-docs-troubleshooting","google-docs-tab-level-read-and-edit-is-supported-by-specific-google-do","google-docs-troubleshooting","google-sensitive-scopes-can-cause-app-blocked-errors-unless-the-oauth","googledocs-create-document-markdown-accepts-github-flavored-markdown-a","managed-google-oauth-tokens-stay-redacted-custom-oauth-is-needed-for-r","multiple-google-accounts-require-multi-account-support-or-distinct-con","platform-connections-are-isolated-from-for-you-connect-mcp-connections","specify-google-auth-config-ids-at-session-creation-so-manage-connectio","tool-router-v2-sessions-require-connected-accounts-to-belong-to-the-sa"]
12 ----
13 -Use this guide to create and edit Google Docs content, configure Google OAuth, manage accounts and sessions, and connect through the correct Composio surface.
14 -
15 -## Create and edit Google Docs content
16 -
17 -**Create documents from Markdown or HTML tables.** `GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown. Markdown tables should work, and HTML tables can also be passed in the markdown payload when a table shape is needed.
18 -
19 -**Use the tab-aware tools for reading and editing.** Google Docs tab-level access is supported. For reading tabs, use `GOOGLEDOCS_GET_DOCUMENT_BY_ID` or `GOOGLEDOCS_GET_DOCUMENT_PLAINTEXT`. For editing specific tabs, use `GOOGLEDOCS_REPLACE_ALL_TEXT`, `GOOGLEDOCS_REPLACE_IMAGE`, or `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT`.
20 -
21 -## Configure Google OAuth
22 -
23 -**Choose managed or customer-owned OAuth2.** Use Composio-managed OAuth for the standard connection flow. Create a custom auth config with your Google OAuth app when you need control over scopes, consent-screen branding, or Google Cloud project policy. A Composio Project API key authenticates SDK/API calls to Composio; it is not a replacement for the user's Google OAuth grant.
24 -
25 -**Verify sensitive scopes for production use.** Google may block OAuth consent when an app requests unverified sensitive scopes. For production Google Docs or Workspace usage with sensitive scopes, use a verified OAuth app and complete the required Google verification or CASA process where applicable. Without verification, users may see warnings or app-blocked errors.
26 -
27 -**Execute through Composio instead of reading provider tokens.** Provider tokens are redacted from connected-account API responses. Use Composio tool execution or Proxy Execute instead of reading access or refresh tokens from connected-account data.
28 -
29 -## Manage accounts, sessions, and auth configs
30 -
31 -**Select explicitly when a user has multiple Google accounts.** Composio can keep multiple connected accounts for the same toolkit and user. Enable multi-account behavior for the session when needed, give each account a clear alias, and select the intended alias or connected-account ID during execution rather than relying on an implicit default.
32 -
33 -**Keep Tool Router v2 accounts under the same user or entity.** Tool Router v2 sessions are scoped to a single `user_id`. Every connected account passed into that session must belong to the same entity, otherwise validation fails with `ToolRouterV2_InvalidConnectedAccountIds`. Reconnect the outlier Google account under the same `user_id` or create a separate session.
34 -
35 -**Specify auth config IDs when creating the session.** When creating a Composio session, pass `auth_configs` keyed by toolkit slug, such as `gmail`, `googledrive`, or `googlecalendar`. If specified, Manage Connection uses those auth configs directly instead of picking a default config.
36 -
37 -## Connect through Platform or Connect MCP
38 -
39 -**Connect the app separately on each surface.** Connections created on Platform (`dashboard.composio.dev`) are isolated from For You / Connect MCP and do not carry over. To use Google Docs, Sheets, or Workspace through Connect MCP, ask the MCP server to connect the app from the client flow and complete that OAuth flow.
docs/content/kb/guide/toolkits-googledrive.mdx deleted
-48
@@ -1,48 +0,0 @@
1 ----
2 -title: "Google Drive"
3 -description: "Public support knowledge for Google Drive."
4 -keywords: ["for-you","googledrive","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-drive-troubleshooting","a-missing-google-drive-tool-can-be-caused-by-passing-an-invalid-toolki","disable-sdk-auto-file-handling-when-you-need-the-raw-google-drive-down","for-a-google-drive-file-browser-ui-prefer-direct-tool-execution-over-m","google-drive-downloads-use-temporary-presigned-urls-with-configurable","google-drive-tool-execution-requests-should-include-an-arguments-objec","google-drive-troubleshooting","google-drive-upload-tools-can-accept-local-file-paths-or-urls-through","google-drive-watch-change-webhooks-require-a-public-endpoint","managed-google-drive-scope-is-narrow","tool-router-v2-sessions-require-all-connected-accounts-to-belong-to-th","use-custom-google-oauth-credentials-when-managed-credentials-are-not-v"]
5 -sources: [{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Google Drive upload tools can accept local file paths or URLs through SDK auto file handling"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Connect MCP exposes a curated Google Drive tool set and discovers the rest through meta-tools"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Google Drive watch/change webhooks require a public endpoint"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Google Drive downloads use temporary presigned URLs with configurable URL TTL and short-lived storage"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Disable SDK auto file handling when you need the raw Google Drive download output instead of a local path"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Use customer-owned Google OAuth credentials with verified scopes"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"A missing Google Drive tool can be caused by passing an invalid toolkit version"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"For a Google Drive file-browser UI, prefer direct tool execution over MCP as the primary integration layer"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Use `GOOGLEDRIVE_GET_ABOUT` to confirm which Google Drive account is connected"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Google Drive tool execution requests should include an `arguments` object, even when it is empty"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Tool Router v2 sessions require all connected accounts to belong to the same entity"},{"sourcePath":"toolkits/googledrive/public.md","sourceHeading":"Choose the narrowest Google Drive scope that supports the workflow"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googledrive"]
11 -aliases: ["/kb/toolkits/google-drive-troubleshooting","a-missing-google-drive-tool-can-be-caused-by-passing-an-invalid-toolki","disable-sdk-auto-file-handling-when-you-need-the-raw-google-drive-down","for-a-google-drive-file-browser-ui-prefer-direct-tool-execution-over-m","google-drive-downloads-use-temporary-presigned-urls-with-configurable","google-drive-tool-execution-requests-should-include-an-arguments-objec","google-drive-troubleshooting","google-drive-upload-tools-can-accept-local-file-paths-or-urls-through","google-drive-watch-change-webhooks-require-a-public-endpoint","managed-google-drive-scope-is-narrow","tool-router-v2-sessions-require-all-connected-accounts-to-belong-to-th","use-custom-google-oauth-credentials-when-managed-credentials-are-not-v"]
12 ----
13 -Use this guide to upload and download Google Drive files, choose an execution path, configure OAuth and webhooks, and troubleshoot account or session issues.
14 -
15 -## Upload and download Google Drive files
16 -
17 -**Pass local paths or URLs through SDK auto file handling.** For tools that support file-upload parameters such as `s3key`, `mimetype`, and `name`, the SDK can rewrite those parameters automatically. The caller can pass a local file path or URL string, and the SDK reads the file, uploads it to Composio-managed storage, and constructs the provider payload before executing the tool. For `GOOGLEDRIVE_UPLOAD_FILE`, passing `file_to_upload: "/path/to/file.pdf"` is the intended SDK pattern when auto file handling is enabled.
18 -
19 -**Plan for temporary download URLs and storage.** Downloaded files are staged in temporary S3-backed storage and exposed through presigned URLs. The default presigned URL TTL is 1 hour, and that URL expiration can be customized in Project Settings -> File TTL. The staged files themselves are short lived and are deleted from Composio storage after about 24 hours / one day.
20 -
21 -**Disable auto file handling when raw output is required.** If the SDK is converting downloaded file output into a local path and the application needs the raw URL or file payload, disable automatic file handling for the execution path. Use the documented `auto_upload_download_files=False` / disabling-auto-file-handling option, and make sure the relevant Composio SDK packages are upgraded to a version that supports that behavior.
22 -
23 -## Choose MCP or direct execution
24 -
25 -**Discover less common Connect MCP tools with meta-tools.** Connect MCP exposes a curated direct tool set so the assistant does not load hundreds or thousands of tools into context. Less common or higher-risk Google Drive actions, including `GOOGLEDRIVE_GOOGLE_DRIVE_DELETE_FOLDER_OR_FILE_ACTION`, should be discovered at runtime with `COMPOSIO_SEARCH_TOOLS` and executed with `COMPOSIO_MULTI_EXECUTE_TOOL`.
26 -
27 -**Prefer direct execution for a deterministic file-browser UI.** Using Composio MCP for a Google Drive file browser is feasible, but MCP servers are designed primarily for AI assistant integrations. For a product UI or deterministic file browser, prefer Direct Tool Execution through the Composio SDK or APIs so the application controls the tool calls, arguments, and rendering flow directly.
28 -
29 -## Configure Google OAuth, scopes, and webhooks
30 -
31 -**Use a public endpoint for watch and change webhooks.** Google Drive webhook payloads need to be delivered to a public domain or publicly reachable endpoint. A private-domain listener is not sufficient for Composio's server to send the webhook payload.
32 -
33 -**Use customer-owned OAuth credentials with verified scopes.** Google can block the OAuth flow when the OAuth app is not verified for the requested sensitive or restricted scope. Configure and verify the required scope on the customer's Google Cloud OAuth app, then use those credentials in the Composio auth config. Also verify that the auth config requests only the intended scopes.
34 -
35 -**Choose the narrowest scope that supports the workflow.** The `drive.file` scope allows access to files the app creates or that the user
36 -explicitly grants to it. A workflow that needs broader full-drive access may
37 -require the `drive` scope on the customer's Google OAuth app. Configure and
38 -verify only the scopes the product actually needs.
39 -
40 -## Troubleshoot account, toolkit, and session execution
41 -
42 -**Check for an invalid toolkit version when a tool is missing.** If a Google Drive tool appears missing, check whether the request is pinned to a toolkit version that exists. Passing an invalid version such as a non-existent dated version can make tools unavailable. Retry with a valid Google Drive toolkit version, or use the latest version when a pinned version is not required.
43 -
44 -**Confirm the connected identity with `GOOGLEDRIVE_GET_ABOUT`.** Run `GOOGLEDRIVE_GET_ABOUT` for the connected account ID to confirm the email address and identity of the Google Drive account being used. This is the quickest check when actions appear to affect a different Drive account than expected.
45 -
46 -**Include an `arguments` object in execution requests.** When calling tool execution APIs such as `GOOGLEDRIVE_FIND_FILE`, include the `arguments` object in the request body. If the tool does not need arguments for that call, send an empty object such as `"arguments": {}` along with the connected account, user/entity ID, and version fields.
47 -
48 -**Keep every Tool Router v2 account under the same entity.** Tool Router v2 sessions are scoped to a single entity/user ID. Every connected account included in a session must belong to that same entity, otherwise validation can fail with `ToolRouterV2_InvalidConnectedAccountIds`. Reconnect Google Drive under the same user/entity as the Gmail and Calendar accounts before combining them in one session. If needed, specify auth config IDs while creating the session so Manage Connection uses the intended auth config for each toolkit.
docs/content/kb/guide/toolkits-googlemeet.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Google Meet"
3 -description: "Public support knowledge for Google Meet."
4 -keywords: ["for-you","googlemeet","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-meet-troubleshooting","403-permission-errors-usually-mean-the-conference-resource-is-inaccess","configure-meet-scopes-and-enable-the-google-meet-api-before-creating-m","google-meet-troubleshooting","google-workspace-enterprise-is-required-to-record-meetings-and-access","use-google-super-tool-slugs-with-a-google-super-connected-account"]
5 -sources: [{"sourcePath":"toolkits/googlemeet/public.md","sourceHeading":"Use Google Super tool slugs with a Google Super connected account"},{"sourcePath":"toolkits/googlemeet/public.md","sourceHeading":"Configure Meet scopes and enable the Google Meet API before creating Meet spaces"},{"sourcePath":"toolkits/googlemeet/public.md","sourceHeading":"Fetch transcript entries by first resolving the conference record"},{"sourcePath":"toolkits/googlemeet/public.md","sourceHeading":"403 permission errors usually mean the conference resource is inaccessible or missing"},{"sourcePath":"toolkits/googlemeet/public.md","sourceHeading":"Recordings and transcripts require an eligible Google Workspace edition and enabled feature"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googlemeet"]
11 -aliases: ["/kb/toolkits/google-meet-troubleshooting","403-permission-errors-usually-mean-the-conference-resource-is-inaccess","configure-meet-scopes-and-enable-the-google-meet-api-before-creating-m","google-meet-troubleshooting","google-workspace-enterprise-is-required-to-record-meetings-and-access","use-google-super-tool-slugs-with-a-google-super-connected-account"]
12 ----
13 -## Use Google Super tool slugs with a Google Super connected account
14 -
15 -Google Super is a separate toolkit with its own tool slugs. If the connected account was created for Google Super, run the corresponding GOOGLESUPER_* tool, such as GOOGLESUPER_CREATE_MEET, instead of the GOOGLEMEET_* slug. A separate Google Meet auth config or connected account is not required when the workflow is intentionally using Google Super.
16 -
17 -## Configure Meet scopes and enable the Google Meet API before creating Meet spaces
18 -
19 -For Meet space creation/settings through Google Super, include the Meet scopes `https://www.googleapis.com/auth/meetings.space.created` and `https://www.googleapis.com/auth/meetings.space.settings` in the auth config, then initiate a new connection so the new scopes are granted. Also enable the Google Meet API in the Google Cloud Console project backing the OAuth app.
20 -
21 -## Fetch transcript entries by first resolving the conference record
22 -
23 -Start with `GOOGLEMEET_LIST_CONFERENCE_RECORDS`. It can filter conference records by meeting code, space name, or time range. Use the resulting conference record ID with `GOOGLEMEET_GET_TRANSCRIPTS_BY_CONFERENCE_RECORD_ID`, then call `GOOGLEMEET_LIST_TRANSCRIPT_ENTRIES` with the transcript resource to retrieve the spoken segments.
24 -
25 -## 403 permission errors usually mean the conference resource is inaccessible or missing
26 -
27 -For a Google Meet API error like "Permission denied on resource Conference (or it might not exist)", verify that the signed-in connected account has access to the conference/artifact and that the conference record exists. Compare the provider response through a least-privileged Composio tool or Proxy Execute call; provider tokens are redacted from connected-account responses and should not be copied into a support workflow.
28 -
29 -## Recordings and transcripts require an eligible Google Workspace edition and enabled feature
30 -
31 -Google Meet recordings and transcripts are available on several eligible Google
32 -Workspace editions, not only Enterprise. The meeting host must have the feature,
33 -the organization's administrator must allow it, and recording or transcription
34 -must have been started for the meeting. Free personal accounts do not provide
35 -the same artifact availability.
36 -
37 -Check Google's current [Meet feature matrix](https://support.google.com/meet/answer/10459644)
38 -and [transcript requirements](https://support.google.com/meet/answer/12849897)
39 -when diagnosing a missing recording or transcript.
docs/content/kb/guide/toolkits-googlesheets.mdx deleted
-42
@@ -1,42 +0,0 @@
1 ----
2 -title: "Google Sheets"
3 -description: "Public support knowledge for Google Sheets."
4 -keywords: ["for-you","googlesheets","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/google-sheets-troubleshooting","execute-google-sheets-tools-by-passing-the-exact-tool-slug","fetch-more-than-the-default-20-google-sheets-tools-with-limit","google-sheets-403s-can-be-caused-by-an-old-placeholder-toolkit-version","google-sheets-429s-are-google-s-api-quota-and-shared-default-oauth-can","google-sheets-auth-configs-require-full-scope-uris","google-sheets-mcp-may-require-the-spreadsheet-id-instead-of-searching","google-sheets-oauth-cannot-be-scoped-to-a-drive-folder","google-sheets-troubleshooting","old-google-sheets-integrations-may-need-a-new-integration-to-access-ne","platform-google-sheets-connections-are-isolated-from-for-you-connect-m","use-google-super-when-one-google-connection-should-cover-gmail-sheets","use-googlesheets-batch-update-or-googlesheets-sheet-from-json-to-add-v"]
5 -sources: [{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Platform Google Sheets connections are isolated from For You Connect MCP"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Fetch more than the default 20 Google Sheets tools with `limit`"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Google Sheets MCP may require the spreadsheet ID instead of searching by name"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Use the current values tools to update, append, or create a populated sheet"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Execute Google Sheets tools by passing the exact tool slug"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Google Sheets 403s can be caused by an old placeholder toolkit version"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Use Google Super when one Google connection should cover Gmail, Sheets, Docs, Drive, and other Google tools"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Use full Google scope URLs such as `https://www.googleapis.com/auth/drive`, not shorthand `/drive`"},{"sourcePath":"toolkits/googlesheets/public.md","sourceHeading":"Google Sheets provider quotas are separate from Composio plan limits"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googlesheets"]
11 -aliases: ["/kb/authentication/google-sheets-troubleshooting","execute-google-sheets-tools-by-passing-the-exact-tool-slug","fetch-more-than-the-default-20-google-sheets-tools-with-limit","google-sheets-403s-can-be-caused-by-an-old-placeholder-toolkit-version","google-sheets-429s-are-google-s-api-quota-and-shared-default-oauth-can","google-sheets-auth-configs-require-full-scope-uris","google-sheets-mcp-may-require-the-spreadsheet-id-instead-of-searching","google-sheets-oauth-cannot-be-scoped-to-a-drive-folder","google-sheets-troubleshooting","old-google-sheets-integrations-may-need-a-new-integration-to-access-ne","platform-google-sheets-connections-are-isolated-from-for-you-connect-m","use-google-super-when-one-google-connection-should-cover-gmail-sheets","use-googlesheets-batch-update-or-googlesheets-sheet-from-json-to-add-v"]
12 ----
13 -Use this guide to connect Google Sheets, discover and run the current tools, and configure Google authentication and quotas.
14 -
15 -## Connect Google Sheets and discover tools
16 -
17 -**Connect separately through Platform and Connect MCP.** Connections made on the Platform side (`dashboard.composio.dev`) are isolated from the For You / `connect.composio.dev/mcp` flow. A Google Sheets connection created on Platform will not automatically appear in Connect MCP. To use Sheets through Connect MCP, ask the MCP server from the client to connect Google Sheets, complete the surfaced auth link, then retry discovery/execution.
18 -
19 -**Increase the tool-list limit when needed.** `get_raw_composio_tools` returns 20 tools by default. Pass a larger `limit` to fetch the full Google Sheets tool set, for example `.get_raw_composio_tools(toolkits=["GOOGLESHEETS"], limit=1000)`.
20 -
21 -**Use the spreadsheet ID for MCP operations.** The Google Sheets MCP flow does not search through spreadsheets by name. Provide the spreadsheet ID directly in the chat/tool call when asking for operations such as getting sheet names.
22 -
23 -## Update and populate spreadsheets
24 -
25 -**Choose the current values tool for the operation.** Use `GOOGLESHEETS_VALUES_UPDATE` for one range, `GOOGLESHEETS_UPDATE_VALUES_BATCH` for multiple ranges, or `GOOGLESHEETS_SPREADSHEETS_VALUES_APPEND` to append rows. To create and populate a new spreadsheet, call `GOOGLESHEETS_CREATE_GOOGLE_SHEET1` and then one of the current values-update actions. `GOOGLESHEETS_BATCH_UPDATE` and `GOOGLESHEETS_SHEET_FROM_JSON` are deprecated.
26 -
27 -**Execute tools with the exact current slug.** When executing Google Sheets tools, pass the exact current slug directly as the tool identifier, for example `composio.tools.execute("GOOGLESHEETS_GET_SHEET_NAMES", executePayload)`. If a wrapper parameter like `params.toolIdentifier` is used, verify it resolves to the exact tool slug. The older `GOOGLESHEETS_LIST_TABLES` action is deprecated.
28 -
29 -## Configure Google authentication, versions, and quotas
30 -
31 -**Update old placeholder toolkit versions.** If Google Sheets actions fail with permission errors and logs show the base version `00000000_00`, switch to the latest Google Sheets toolkit version and check the toolkit versioning documentation.
32 -
33 -**Use Google Super for one shared Google connection.** For the canonical guidance on using one connection across Google Workspace services, see [Google Super is a unified Google Workspace toolkit](/kb/guide/toolkits-googlesuper).
34 -
35 -**Enter complete Google OAuth scope URLs.** When configuring Google scopes manually, use the full scope URL. For Drive access, use `https://www.googleapis.com/auth/drive` rather than shorthand values like `/drive`.
36 -
37 -**Treat Google provider quotas separately from Composio plan limits.** A Google Sheets 429 can come from Google's API quotas even when the Composio
38 -account has remaining tool calls. Google currently documents 300 read requests
39 -and 300 write requests per minute per project, plus 60 reads and 60 writes per
40 -minute per user per project. Apply exponential backoff and check
41 -[Google's current Sheets API limits](https://developers.google.com/workspace/sheets/api/limits)
42 -before relying on those numbers.
docs/content/kb/guide/toolkits-googleslides.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "Google Slides"
3 -description: "Public support knowledge for Google Slides."
4 -keywords: ["for-you","googleslides","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-slides-troubleshooting","custom-google-slides-oauth-apps-must-be-verified-for-sensitive-scopes","google-slide-creation-tools-are-available-through-google-super","google-slides-may-require-a-custom-oauth-app-instead-of-default-compos","google-slides-troubleshooting","googledrive-create-file-from-text-cannot-create-native-google-slides-f","googleslides-presentations-get-needs-the-presentation-id-from-the-url","use-google-drive-search-to-list-or-discover-google-slides-presentation","use-the-same-google-account-when-pairing-drive-discovery-with-google-s"]
5 -sources: [{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"Use Google Drive search to list or discover Google Slides presentations"},{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"`GOOGLESLIDES_PRESENTATIONS_GET` needs the presentation ID from the URL or Drive payload"},{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"Use the same Google account when pairing Drive discovery with Google Slides reads"},{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"Google Slide creation tools are available through Google Super"},{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"Custom Google Slides OAuth apps must be verified for sensitive scopes"},{"sourcePath":"toolkits/googleslides/public.md","sourceHeading":"Google Slides supports one trigger in Composio"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googleslides"]
11 -aliases: ["/kb/toolkits/google-slides-troubleshooting","custom-google-slides-oauth-apps-must-be-verified-for-sensitive-scopes","google-slide-creation-tools-are-available-through-google-super","google-slides-may-require-a-custom-oauth-app-instead-of-default-compos","google-slides-troubleshooting","googledrive-create-file-from-text-cannot-create-native-google-slides-f","googleslides-presentations-get-needs-the-presentation-id-from-the-url","use-google-drive-search-to-list-or-discover-google-slides-presentation","use-the-same-google-account-when-pairing-drive-discovery-with-google-s"]
12 ----
13 -Use this guide to discover, read, create, and connect Google Slides presentations in Composio.
14 -
15 -## Discover and read Google Slides presentations
16 -
17 -**Discover presentations through Google Drive.** Google Slides does not offer a dedicated endpoint to list all presentations through the Slides toolkit. Use `GOOGLEDRIVE_FIND_FILE` and filter Drive files with `q`, for example `mimeType = 'application/vnd.google-apps.presentation'`, then pass the returned presentation ID into the Google Slides tool.
18 -
19 -**Pass the presentation ID to `GOOGLESLIDES_PRESENTATIONS_GET`.** `GOOGLESLIDES_PRESENTATIONS_GET` should be called with the Google Slides presentation ID. Get that ID from the presentation URL, or use the ID returned by `GOOGLEDRIVE_FIND_FILE` when discovering presentations through Drive.
20 -
21 -**Use the same Google account for discovery and reading.** When a workflow discovers presentations with `GOOGLEDRIVE_FIND_FILE` and then reads them with `GOOGLESLIDES_PRESENTATIONS_GET`, make sure the connected Google Drive and Google Slides accounts are the same account. Otherwise the ID may be valid in Drive discovery but inaccessible to the Slides connection.
22 -
23 -## Create and connect Google Slides workflows
24 -
25 -**Create presentations through Google Super.** Google Slide creation tools were added to the Google Super toolkit. For slide creation workflows, use the relevant Google Super tools rather than trying to create a native Slides file through generic Drive text upload.
26 -
27 -**Verify custom OAuth apps for sensitive scopes.** When using a custom Google developer app for Google Slides, the app must be verified for the sensitive Google scopes it requests. Without verification, Google may block or warn on the OAuth consent flow.
28 -
29 -**Use the supported Google Slides trigger.** Google Slides is listed as a trigger-capable toolkit in Composio with one supported trigger.
docs/content/kb/guide/toolkits-googlesuper.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Google Super"
3 -description: "Public support knowledge for Google Super."
4 -keywords: ["for-you","googlesuper","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-super-troubleshooting","connection-initiation-did-not-complete-within-10-minutes-means-oauth-c","gmail-filter-creation-through-google-super-also-requires-gmail-setting","google-meet-through-google-super-needs-meet-scopes-and-google-meet-api","google-super-can-be-narrowed-by-removing-unneeded-scopes-and-tools","google-super-cannot-schedule-gmail-emails-out-of-the-box","google-super-is-a-unified-google-workspace-toolkit","google-super-sheets-404s-can-mean-wrong-spreadsheet-id-missing-access","google-super-troubleshooting","google-users-can-deselect-scopes-during-consent-composio-marks-active","googlesuper-list-labels-with-include-details-true-can-be-slow-because","googlesuper-list-threads-verbose-behavior-trades-payload-latency-for-d","managed-google-super-oauth-issues-can-be-unblocked-by-switching-to-a-c","missing-google-super-endpoints-should-be-filed-as-tool-requests-not-to","resultsizeestimate-was-added-to-gmail-thread-listing-response","use-gmail-google-super-query-and-label-filters-to-find-sent-or-labeled"]
5 -sources: [{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Google Super is a unified Google Workspace toolkit"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Google Meet through Google Super needs Meet scopes and Google Meet API enabled"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Google Super can be narrowed by removing unneeded scopes and tools"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Gmail filter creation through Google Super also requires `gmail.settings.basic`"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"`GOOGLESUPER_LIST_LABELS` with `include_details=true` can be slow because it fans out per label"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Gmail thread listing includes `resultSizeEstimate`"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Use Gmail/Google Super query and label filters to find sent or labeled messages"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Google Super Sheets 404s can mean wrong spreadsheet ID, missing access, or missing spreadsheet scope"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"`Connection initiation did not complete within 10 minutes` means OAuth consent was not completed, not token refresh failure"},{"sourcePath":"toolkits/googlesuper/public.md","sourceHeading":"Google users can deselect scopes during consent; Composio marks active if token exchange succeeds"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googlesuper"]
11 -aliases: ["/kb/toolkits/google-super-troubleshooting","connection-initiation-did-not-complete-within-10-minutes-means-oauth-c","gmail-filter-creation-through-google-super-also-requires-gmail-setting","google-meet-through-google-super-needs-meet-scopes-and-google-meet-api","google-super-can-be-narrowed-by-removing-unneeded-scopes-and-tools","google-super-cannot-schedule-gmail-emails-out-of-the-box","google-super-is-a-unified-google-workspace-toolkit","google-super-sheets-404s-can-mean-wrong-spreadsheet-id-missing-access","google-super-troubleshooting","google-users-can-deselect-scopes-during-consent-composio-marks-active","googlesuper-list-labels-with-include-details-true-can-be-slow-because","googlesuper-list-threads-verbose-behavior-trades-payload-latency-for-d","managed-google-super-oauth-issues-can-be-unblocked-by-switching-to-a-c","missing-google-super-endpoints-should-be-filed-as-tool-requests-not-to","resultsizeestimate-was-added-to-gmail-thread-listing-response","use-gmail-google-super-query-and-label-filters-to-find-sent-or-labeled"]
12 ----
13 -Use this guide to configure a Google Super connection and run Google Workspace actions with the required scopes and efficient filters.
14 -
15 -## Configure Google Super access and consent
16 -
17 -**Use one connection across supported Google Workspace services.** Google Super is a unified/superset toolkit for Google Workspace services. It can cover tools across Gmail, Google Calendar, Google Meet, and related Google APIs through one Google Super connection when the required scopes are configured.
18 -
19 -**Remove unneeded scopes and tools carefully.** Google Super can cover all Google services including Gmail, but customers can remove scopes and tools they do not want as part of the Google Super auth/tool configuration. Make sure the remaining scopes still cover the tools the customer expects to use.
20 -
21 -**Treat a 10-minute initiation timeout as incomplete consent.** If expired connections share status reason `Connection initiation did not complete within 10 minutes`, the OAuth flow was initiated but the user did not complete consent within the 10-minute window. No provider tokens were issued in that case, so it is not a 1-2 week refresh token expiry problem.
22 -
23 -**Account for scopes users deselect during consent.** Google lets users selectively deselect scopes during consent. Composio marks the connection active as long as token exchange succeeds, even if the final granted scopes are a subset of the auth config's requested scopes. The auth config scopes are the blueprint, but the final permissions are decided by the end user on the consent screen.
24 -
25 -## Enable service-specific scopes and APIs
26 -
27 -**Configure Meet scopes and enable the Google Meet API.** To use Google Meet tools through Google Super, configure `https://www.googleapis.com/auth/meetings.space.created` and `https://www.googleapis.com/auth/meetings.space.settings` in the Google Super auth config, create a new connection for the scope changes to apply, and enable the Google Meet API in Google Cloud Console.
28 -
29 -**Include the Gmail settings scope for filter creation.** Google Super uses the same underlying Gmail API requirement for filter creation. See the canonical Gmail guidance: [Creating Gmail filters requires `gmail.settings.basic`](/kb/guide/toolkits-gmail).
30 -
31 -**Check spreadsheet identity, access, and scope when Sheets returns 404.** For Google Super Sheets 404s, first verify the spreadsheet ID, confirm the sheet is shared with the connected Google account, and ensure the connection has `https://www.googleapis.com/auth/spreadsheets`. If those are all correct and only one tool fails, contact Composio support with the redacted request/response payload and log ID.
32 -
33 -## Query Gmail efficiently through Google Super
34 -
35 -**Avoid label-detail fan-out when it is unnecessary.** For `GOOGLESUPER_LIST_LABELS`, setting `include_details=true` fans out into one Gmail API call per label. Accounts with many labels can become slow because the calls happen sequentially. Set `include_details=false` or omit the parameter to return to a single API call and much lower latency.
36 -
37 -**Use the thread result estimate from current versions.** The current Gmail thread-listing response includes `resultSizeEstimate`. If it is absent through an older pinned Google Super toolkit version, compare its schema with the latest version before changing application logic.
38 -
39 -**Filter messages with Gmail queries and label IDs.** Gmail/Google Super tools are wrappers over Google APIs, so use Gmail-style `query` filters or `label_ids` where supported to filter messages, including sent-mail style queries. If the exact filter is not exposed, submit the endpoint or parameter through the Composio request portal.
docs/content/kb/guide/toolkits-googletasks.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "Google Tasks"
3 -description: "Public OAuth, connection, and quota troubleshooting for Google Tasks."
4 -keywords: ["for-you","googletasks","oauth","platform","quotas","scopes","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/google-tasks-troubleshooting","enable-the-google-tasks-api-for-custom-oauth","google-tasks-troubleshooting","handle-quota-or-rate-limit-exhaustion","resolve-error-400-invalid-scope-2","set-up-custom-google-oauth-credentials-2"]
5 -sources: [{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Set up custom Google OAuth credentials"},{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Resolve an \"App is blocked\" connection error"},{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Enable the Google Tasks API for custom OAuth"},{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Resolve `Error 400: invalid_scope`"},{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Choose managed or customer-owned Google OAuth"},{"sourcePath":"toolkits/googletasks/public.md","sourceHeading":"Resolve 401 errors on tool calls"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["googletasks"]
11 -aliases: ["/kb/toolkits/google-tasks-troubleshooting","enable-the-google-tasks-api-for-custom-oauth","google-tasks-troubleshooting","handle-quota-or-rate-limit-exhaustion","resolve-error-400-invalid-scope-2","set-up-custom-google-oauth-credentials-2"]
12 ----
13 -Use this guide to choose managed or customer-owned Google OAuth for Google Tasks and troubleshoot consent, scope, or token failures.
14 -
15 -## Configure Google OAuth for Google Tasks
16 -
17 -**Follow the Google Apps credential setup guide for custom OAuth.** For a step-by-step guide to creating and configuring Google OAuth credentials with Composio, see [How to create OAuth2 credentials for Google Apps](https://composio.dev/auth/googleapps).
18 -
19 -**Enable the Google Tasks API for custom OAuth.** Enable the Google Tasks API in the Google Cloud project that owns the credentials. After enabling it under **APIs & Services**, wait a few minutes and retry.
20 -
21 -**Choose managed or customer-owned OAuth.** Use Composio-managed OAuth for the standard connection flow. Use a custom Google OAuth app when you need control over scopes, consent-screen branding, or Google Cloud project policy. For custom OAuth, configure the app name and branding in that project and use the redirect URL shown by Composio's current auth-config flow.
22 -
23 -## Troubleshoot Google Tasks OAuth and tool calls
24 -
25 -**Remove unverified scopes when Google reports “App is blocked.”** This error usually means the OAuth client is requesting scopes that Google has not verified for that client. Remove additional scopes beyond the defaults, or use a custom OAuth app and submit the scopes for verification.
26 -
27 -**Validate scopes when OAuth returns `Error 400: invalid_scope`.** Verify the requested scopes and their formatting against the [Google OAuth scopes documentation](https://developers.google.com/identity/protocols/oauth2).
28 -
29 -**Reconnect when tool calls return 401.** A 401 usually means the access token is no longer valid. Re-authenticate the connected account and retry.
docs/content/kb/guide/toolkits-granola-mcp.mdx deleted
-20
@@ -1,20 +0,0 @@
1 ----
2 -title: "Granola MCP"
3 -description: "Public behavior and schema guidance for the official Granola MCP server."
4 -keywords: ["for-you","granola","mcp","platform","schemas","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/granola-mcp-metadata-comes-from-the-upstream-server","granola-mcp-metadata-comes-from-the-upstream-server"]
5 -sources: [{"sourcePath":"toolkits/granola_mcp/public.md","sourceHeading":"Composio mirrors Granola's official MCP server"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["granola_mcp"]
11 -aliases: ["/kb/toolkits/granola-mcp-metadata-comes-from-the-upstream-server","granola-mcp-metadata-comes-from-the-upstream-server"]
12 ----
13 -## Composio mirrors Granola's official MCP server
14 -
15 -The Granola MCP toolkit uses Granola's official MCP server. Tool names, descriptions, input definitions, and response metadata are limited to what that upstream server exposes.
16 -
17 -- If Granola supplies only a tool name and description, that is the metadata Composio can expose.
18 -- If Granola does not declare a response/output schema, Composio cannot invent one, so an empty output schema is not by itself evidence of a stale Composio catalog.
19 -- If you find a mismatch, note the exact tool name and missing field. Compare it with the current official Granola MCP server behavior before attributing it to the Composio catalog.
20 -- If the official server currently exposes a tool or schema field but the same item is absent from Composio, contact Composio support and include those comparison details.
docs/content/kb/guide/toolkits-hubspot.mdx deleted
-53
@@ -1,53 +0,0 @@
1 ----
2 -title: "HubSpot"
3 -description: "Public support knowledge for HubSpot."
4 -keywords: ["for-you","hubspot","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/hubspot-troubleshooting","/kb/toolkits/after-hubspot-trigger-fixes-recreate-old-triggers","after-hubspot-trigger-fixes-recreate-old-triggers","composio-does-not-provide-hubspot-field-level-permissions-restrict-by","create-custom-hubspot-tools-through-toolkit-authenticated-api-requests","fix-hubspot-oauth-token-exchange-400-client-secret-and-scopes","hubspot-auth-loops-can-be-caused-by-hubspot-side-workspace-login-state","hubspot-managed-oauth-app-unverified-warning-has-no-reliable-eta-byoa","hubspot-marketing-campaign-objects-do-not-expose-a-properties-api-like","hubspot-scopes-must-be-predeclared-in-the-hubspot-app-config","hubspot-trigger-setup-needs-the-hubspot-app-id","hubspot-triggers-require-each-customer-s-own-app-id-and-developer-api","hubspot-troubleshooting","minimum-hubspot-contact-scopes-are-contact-read-write","some-hubspot-scopes-are-not-in-composio-managed-auth-use-own-oauth-app","use-composio-scopes-api-or-hubspot-docs-to-find-required-hubspot-scope","use-custom-hubspot-credentials-for-white-label-auth"]
5 -sources: [{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Minimum HubSpot contact scopes are contact read/write"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Use Composio scopes API or HubSpot docs to find required HubSpot scopes"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Create custom HubSpot tools through toolkit-authenticated API requests"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot trigger setup needs the HubSpot app ID"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Use custom HubSpot credentials for white-label auth"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot scopes must be predeclared in the HubSpot app config"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot OAuth token-fetch 400: check client secret and required-scope alignment"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Old HubSpot SDK/toolkit versions use old double-prefixed slugs"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot auth loops can be caused by HubSpot-side workspace/login state"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot marketing campaign objects do not expose a properties API like CRM objects"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"HubSpot triggers require each customer’s own app ID and developer API key"},{"sourcePath":"toolkits/hubspot/public.md","sourceHeading":"Deleting a HubSpot connected account disconnects it and stops token refresh"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["hubspot"]
11 -aliases: ["/kb/authentication/hubspot-troubleshooting","/kb/toolkits/after-hubspot-trigger-fixes-recreate-old-triggers","after-hubspot-trigger-fixes-recreate-old-triggers","composio-does-not-provide-hubspot-field-level-permissions-restrict-by","create-custom-hubspot-tools-through-toolkit-authenticated-api-requests","fix-hubspot-oauth-token-exchange-400-client-secret-and-scopes","hubspot-auth-loops-can-be-caused-by-hubspot-side-workspace-login-state","hubspot-managed-oauth-app-unverified-warning-has-no-reliable-eta-byoa","hubspot-marketing-campaign-objects-do-not-expose-a-properties-api-like","hubspot-scopes-must-be-predeclared-in-the-hubspot-app-config","hubspot-trigger-setup-needs-the-hubspot-app-id","hubspot-triggers-require-each-customer-s-own-app-id-and-developer-api","hubspot-troubleshooting","minimum-hubspot-contact-scopes-are-contact-read-write","some-hubspot-scopes-are-not-in-composio-managed-auth-use-own-oauth-app","use-composio-scopes-api-or-hubspot-docs-to-find-required-hubspot-scope","use-custom-hubspot-credentials-for-white-label-auth"]
12 ----
13 -Use this guide to configure HubSpot authentication, troubleshoot OAuth connections, call HubSpot APIs, and set up triggers.
14 -
15 -## Configure HubSpot OAuth scopes and branding
16 -
17 -**Choose the required contact scopes.** For HubSpot CRM contacts, the minimum scopes are `crm.objects.contacts.read` and `crm.objects.contacts.write`. Sensitive contact fields require the corresponding sensitive scopes such as `crm.objects.contacts.sensitive.read` and `.write`.
18 -
19 -**Map tools to scopes before configuring the app.** Use HubSpot's own scopes documentation and Composio's scopes/tools API to map actions to required scopes. This is better than guessing scopes manually.
20 -
21 -**Keep the HubSpot app and Composio auth config aligned.** HubSpot requires scopes to be declared in the app configuration before OAuth. The scope set on the Composio auth config should match the HubSpot app settings; HubSpot will not dynamically adjust scopes at connection time.
22 -
23 -**Use customer-owned credentials for white-label OAuth.** Use your own HubSpot OAuth app credentials/custom auth config. That gives control over branding/consent and avoids relying on the Composio managed app for the customer-facing OAuth screen.
24 -
25 -## Troubleshoot HubSpot OAuth connections
26 -
27 -**For a 400 during token exchange, check the client secret first.** Several reported customer-owned HubSpot OAuth failures were resolved by copying the correct current client secret from the HubSpot app and updating the Composio custom auth config to match. If the secret was rotated or copied from the wrong HubSpot app, HubSpot can fail token exchange with a 400.
28 -
29 -Then check scope alignment. HubSpot is strict about required scopes:
30 -
31 -- Required scopes configured on the HubSpot app must be present in the OAuth request/install URL `scope` parameter for successful installation.
32 -- If the Composio auth config requests required scopes that do not match the customer-owned HubSpot app's configured required scopes, authorization/token exchange can fail.
33 -- Optional scopes should be requested through HubSpot's `optional_scope` parameter. If the selected HubSpot account/user cannot grant an optional scope, HubSpot can omit it and the resulting token will not include that scope. Do not assume optional scopes were granted; inspect token/granted scopes before relying on optional capabilities.
34 -
35 -For Composio-managed HubSpot auth configs, do not change the default scope set. If you need a different required/optional scope configuration, use your own HubSpot OAuth app through a custom Composio auth config.
36 -
37 -**For an authorization loop, verify HubSpot's workspace and login state.** If the HubSpot flow loops while Composio works on its side, retry while logged into the correct HubSpot workspace and confirm the OAuth app is public/configured correctly.
38 -
39 -**To disconnect HubSpot, delete the connected account.** Deleting the connected account disconnects the HubSpot account from Composio and stops refreshing that access token.
40 -
41 -## Use HubSpot APIs and current toolkit versions
42 -
43 -**Create custom HubSpot tools through authenticated API requests.** You can create a custom tool that sends authenticated requests to HubSpot API endpoints; Composio handles authentication for the connected account. Alternatively, call the provider directly with connection config/custom headers if needed.
44 -
45 -**Handle marketing objects separately from CRM properties.** For HubSpot marketing objects such as campaigns, HubSpot does not expose a properties API in the same way it does for CRM objects. You may need to inspect or configure these from the HubSpot portal.
46 -
47 -**Upgrade old HubSpot SDK and toolkit versions.** Older versions used slugs like `HUBSPOT_HUBSPOT_LIST_CONTACTS`; newer versions use slugs like `HUBSPOT_LIST_CONTACTS`. Update the SDK and explicitly use the latest HubSpot toolkit version.
48 -
49 -## Configure HubSpot triggers for each customer app
50 -
51 -HubSpot webhook APIs need the specific HubSpot app that should receive webhook notifications. Get the app ID from HubSpot's webhook app documentation or developer app settings and use it when configuring triggers.
52 -
53 -For triggers that use a customer-owned HubSpot app, `app_id` and developer API key are required because each app receives its own webhook delivery.
docs/content/kb/guide/toolkits-instagram.mdx deleted
-61
@@ -1,61 +0,0 @@
1 ----
2 -title: "Instagram"
3 -description: "Public support knowledge for Instagram."
4 -keywords: ["for-you","instagram","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/instagram-troubleshooting","for-custom-instagram-meta-oauth-configure-the-redirect-uri-in-the-meta","for-instagram-dms-via-n8n-claude-connect-mcp-can-simplify-setup","instagram-dm-send-failures-with-code-10-subcode-2534022-are-meta-s-24","instagram-is-available-as-a-toolkit-and-can-be-connected-via-a-new-aut","instagram-oauth-tokens-are-bound-to-the-account-selected-in-facebook-l","instagram-post-ig-media-comments-failures-can-be-caused-by-an-incorrec","instagram-reply-to-comment-may-require-a-scope-not-available-in-the-ma","instagram-toolkit-requires-a-business-creator-account-for-supported-bu","instagram-troubleshooting","instagram-uses-business-login-and-only-supported-verified-scopes-shoul","stage-local-instagram-media-before-publishing","use-instagram-list-all-messages-to-fetch-instagram-messages","use-your-own-meta-oauth-app-for-high-volume-instagram-production-usage"]
5 -sources: [{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Instagram OAuth tokens are bound to the account selected in Facebook Login"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Instagram uses Business Login and only supported/verified scopes should be configured"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Instagram toolkit requires a Business/Creator account for supported business features"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Use `INSTAGRAM_LIST_ALL_MESSAGES` to fetch Instagram messages"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Instagram DM send failures with code 10/subcode 2534022 are Meta's 24-hour messaging window"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"For custom Instagram/Meta OAuth, configure the redirect URI in the Meta app"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"For Instagram DMs via n8n/Claude, Connect MCP can simplify setup"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"`INSTAGRAM_POST_IG_MEDIA_COMMENTS` failures can be caused by an incorrect `ig_media_id`"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Instagram is available as a toolkit and can be connected via a new authConfig"},{"sourcePath":"toolkits/instagram/public.md","sourceHeading":"Publish local media with `image_file` or `video_file`"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["instagram"]
11 -aliases: ["/kb/toolkits/instagram-troubleshooting","for-custom-instagram-meta-oauth-configure-the-redirect-uri-in-the-meta","for-instagram-dms-via-n8n-claude-connect-mcp-can-simplify-setup","instagram-dm-send-failures-with-code-10-subcode-2534022-are-meta-s-24","instagram-is-available-as-a-toolkit-and-can-be-connected-via-a-new-aut","instagram-oauth-tokens-are-bound-to-the-account-selected-in-facebook-l","instagram-post-ig-media-comments-failures-can-be-caused-by-an-incorrec","instagram-reply-to-comment-may-require-a-scope-not-available-in-the-ma","instagram-toolkit-requires-a-business-creator-account-for-supported-bu","instagram-troubleshooting","instagram-uses-business-login-and-only-supported-verified-scopes-shoul","stage-local-instagram-media-before-publishing","use-instagram-list-all-messages-to-fetch-instagram-messages","use-your-own-meta-oauth-app-for-high-volume-instagram-production-usage"]
12 ----
13 -## Instagram OAuth tokens are bound to the account selected in Facebook Login
14 -
15 -Instagram connection goes through Facebook Login, where the user selects which Instagram accounts and Facebook Pages to grant access to. Once Instagram issues the token, it is bound to the specific account selected in that OAuth flow. Composio cannot repoint that token server-side to another Instagram account. To switch accounts, reconnect and select the intended Instagram account/page in the Facebook picker.
16 -
17 -## Instagram uses Business Login and only supported/verified scopes should be configured
18 -
19 -The Instagram toolkit uses Instagram API with Business Login for Instagram. OAuth errors commonly happen when unsupported or unverified scopes are configured. Prefer the default scopes where possible, because they are intended to cover the toolkit's supported actions. If configuring custom scopes, use only Meta-supported Instagram Business Login permissions and remove unsupported scopes such as `user_profile`.
20 -
21 -## Instagram toolkit requires a Business/Creator account for supported business features
22 -
23 -Instagram toolkit support is for Instagram Business/Creator account flows. If you are using a personal Instagram account, convert or connect a Business/Creator account linked through Meta/Facebook as required by Instagram's API.
24 -
25 -## Use `INSTAGRAM_LIST_ALL_MESSAGES` to fetch Instagram messages
26 -
27 -Use `INSTAGRAM_LIST_ALL_MESSAGES` to list Instagram messages. In playground, select the correct auth config/connected account; if the desired connected account does not appear, initiate a new connection for the test account and use that auth config.
28 -
29 -## Instagram DM send failures with code 10/subcode 2534022 are Meta's 24-hour messaging window
30 -
31 -That error is enforced by Instagram/Meta, not Composio. Instagram's messaging API only allows replies inside the 24-hour messaging window. Meta opens that window for specific interactions such as a direct DM from the user, story reply, story mention, or icebreaker/quick-reply button tap. Likes, comments, and follows do not open the window. If the qualifying interaction is older than 24 hours or never happened, the send will fail.
32 -
33 -If you have a fresh qualifying inbound DM, an accepted message request, the correct Business/Creator account, and a successful `INSTAGRAM_LIST_ALL_MESSAGES` call, the generic 24-hour-window explanation is not sufficient. Contact Composio support with the redacted call details for further investigation.
34 -
35 -- The current `INSTAGRAM_SEND_TEXT_MESSAGE` action sends `messaging_type: "RESPONSE"` for a normal in-window reply.
36 -
37 -- `INSTAGRAM_MARK_SEEN` can also return the same Meta subcode. Because sender actions are more provider-limited, retest the action before assuming it is supported for every Instagram account. If it still fails, contact Composio support with the exact request or log ID.
38 -
39 -## For custom Instagram/Meta OAuth, configure the redirect URI in the Meta app
40 -
41 -For custom Meta/Instagram OAuth apps, make sure the redirect URI is added in the correct Meta app configuration field and matches the Composio auth config redirect URI. Customers using their own auth app credentials can configure their own redirect URI.
42 -
43 -## For Instagram DMs via n8n/Claude, Connect MCP can simplify setup
44 -
45 -For Instagram DM workflows in MCP clients, use Connect MCP at `https://connect.composio.dev/mcp` with the `x-consumer-api-key` header copied from the current AI Clients setup in the Composio dashboard. The agent can then start the Instagram connection flow when authentication is needed.
46 -
47 -## `INSTAGRAM_POST_IG_MEDIA_COMMENTS` failures can be caused by an incorrect `ig_media_id`
48 -
49 -If `INSTAGRAM_POST_IG_MEDIA_COMMENTS` fails, verify the `ig_media_id` being passed. An incorrect media ID can cause the action to fail even when the action itself is available.
50 -
51 -## Instagram is available as a toolkit and can be connected via a new authConfig
52 -
53 -Instagram is available in the Composio marketplace. Create a new Instagram authConfig, complete the OAuth connection for the Instagram account, and then use the Instagram toolkit tools. The authConfig ID / integration ID can be found from the dashboard.
54 -
55 -## Publish local media with `image_file` or `video_file`
56 -
57 -For a locally generated JPEG, PNG, or video, use `INSTAGRAM_POST_IG_USER_MEDIA` and pass the staged file through `image_file` or `video_file`. Upload or stage the file first; a raw local path, workspace/session path, or stale storage key can fail before Meta receives the request. Follow with `INSTAGRAM_POST_IG_USER_MEDIA_PUBLISH` when the create step succeeds.
58 -
59 -Alternatively, use `image_url` or `video_url` only when it is a direct HTTP(S) media URL that Meta can fetch without authentication. The older `INSTAGRAM_CREATE_MEDIA_CONTAINER` path is URL-only and does not accept local files directly.
60 -
61 -If the error says `Failed to download file with s3key ... storage returned HTTP 404`, re-stage the file and retry with the fresh `FileUploadable` object. Treat this as a Composio file-reference failure before provider execution, not an Instagram OAuth failure.
docs/content/kb/guide/toolkits-intercom.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Intercom"
3 -description: "Public support knowledge for Intercom."
4 -keywords: ["for-you","intercom","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/intercom-troubleshooting","avoid-proxy-execute-for-slow-intercom-api-calls-that-can-hit-cloudflar","intercom-list-all-companies-per-page-limit-is-60","intercom-oauth-tokens-cannot-be-programmatically-revoked-by-composio","intercom-troubleshooting","update-python-sdk-packages-when-intercom-tool-schemas-fail-on-reserved","use-a-custom-intercom-developer-app-if-composio-s-hosted-oauth-app-is","use-external-pages-or-a-custom-agent-when-connecting-mcp-knowledge-to"]
5 -sources: [{"sourcePath":"toolkits/intercom/public.md","sourceHeading":"Use External Pages or a custom agent when connecting MCP knowledge to Intercom Fin"},{"sourcePath":"toolkits/intercom/public.md","sourceHeading":"INTERCOM_LIST_ALL_COMPANIES per_page limit is 60"},{"sourcePath":"toolkits/intercom/public.md","sourceHeading":"Update Python SDK packages when Intercom tool schemas fail on reserved parameter names"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["intercom"]
11 -aliases: ["/kb/toolkits/intercom-troubleshooting","avoid-proxy-execute-for-slow-intercom-api-calls-that-can-hit-cloudflar","intercom-list-all-companies-per-page-limit-is-60","intercom-oauth-tokens-cannot-be-programmatically-revoked-by-composio","intercom-troubleshooting","update-python-sdk-packages-when-intercom-tool-schemas-fail-on-reserved","use-a-custom-intercom-developer-app-if-composio-s-hosted-oauth-app-is","use-external-pages-or-a-custom-agent-when-connecting-mcp-knowledge-to"]
12 ----
13 -## Use External Pages or a custom agent when connecting MCP knowledge to Intercom Fin
14 -
15 -Composio does not control how Intercom Fin retrieves knowledge inside Intercom. For this use case, either push MCP-derived content into Fin's Content Library by creating and managing Intercom External Pages, or build a custom AI agent with Composio SDKs that connects to both the MCP server and Intercom for support workflows such as replying to conversations, creating tickets, and managing contacts.
16 -
17 -## INTERCOM_LIST_ALL_COMPANIES per_page limit is 60
18 -
19 -For Intercom company listing through Composio, keep `per_page` at 60 or lower. The generic Intercom pagination page can be misleading for this endpoint; Composio verified the list companies endpoint limit as 60 and updated the field description accordingly.
20 -
21 -## Update Python SDK packages when Intercom tool schemas fail on reserved parameter names
22 -
23 -This reserved-keyword schema issue was fixed in the SDK. Ask the user to update both `composio` and `composio-langchain` to the latest available versions; the fix was available by SDK version `0.11.4`.
docs/content/kb/guide/toolkits-jira.mdx deleted
-59
@@ -1,59 +0,0 @@
1 ----
2 -title: "Jira"
3 -description: "Public support knowledge for Jira."
4 -keywords: ["for-you","jira","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop","/kb/toolkits/jira-troubleshooting","composio-manages-jira-oauth-tokens-but-does-not-store-jira-api-respons","download-jira-attachments-with-jira-get-attachment","jira-credentials-expire-without-refresh","jira-custom-token-execution-needs-the-atlassian-base-url-subdomain","jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop","jira-oauth-redirect-uri-must-match-the-authconfig-and-atlassian-app","jira-search-pagination-token-requires-the-original-jql-or-filters","jira-service-account-use-requires-customer-owned-credentials-and-scope","jira-troubleshooting","pin-custom-jira-authconfig-when-creating-tool-router-sessions","use-jira-get-create-metadata-issue-type-fields-instead-of-deprecated-c"]
5 -sources: [{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Keep Jira OAuth scopes within Atlassian's supported set"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Pin custom Jira authConfig when creating Tool Router sessions"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Jira custom token execution needs the Atlassian base URL/subdomain"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Jira search pagination tokens returned by current tools preserve search context"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Jira OAuth redirect URI must match the authConfig and Atlassian app"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Missing `audience=api.atlassian.com` can prevent Jira refresh tokens"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Use `JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS` instead of deprecated create metadata behavior"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Download Jira attachments with `JIRA_GET_ATTACHMENT`"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Jira tool-call payload retention follows the project log-storage setting"},{"sourcePath":"toolkits/jira/public.md","sourceHeading":"Jira service account use requires customer-owned credentials and scopes"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["jira"]
11 -aliases: ["/kb/toolkits/jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop","/kb/toolkits/jira-troubleshooting","composio-manages-jira-oauth-tokens-but-does-not-store-jira-api-respons","download-jira-attachments-with-jira-get-attachment","jira-credentials-expire-without-refresh","jira-custom-token-execution-needs-the-atlassian-base-url-subdomain","jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop","jira-oauth-redirect-uri-must-match-the-authconfig-and-atlassian-app","jira-search-pagination-token-requires-the-original-jql-or-filters","jira-service-account-use-requires-customer-owned-credentials-and-scope","jira-troubleshooting","pin-custom-jira-authconfig-when-creating-tool-router-sessions","use-jira-get-create-metadata-issue-type-fields-instead-of-deprecated-c"]
12 ----
13 -## Keep Jira OAuth scopes within Atlassian's supported set
14 -
15 -Jira/Atlassian limits an OAuth app to 50 scopes, and unsupported or mismatched scopes can make consent fail. For a customer-owned app, keep the auth config aligned with the scopes approved on that Atlassian app. Diagnose current managed-auth failures from the current consent error and auth config rather than from previously resolved scope behavior.
16 -
17 -## Pin custom Jira authConfig when creating Tool Router sessions
18 -
19 -When using a custom Jira OAuth app with Tool Router, pass the custom auth config while creating the session. If the session does not specify the Jira auth config, Tool Router can fall back to an auto-generated/default Jira config and fail to see the customer's active custom-auth connections. Pin the active BYOA config, for example `auth_configs: { jira: "<auth_config_id>" }`, so Tool Router resolves the intended Jira connected accounts.
20 -
21 -## Jira custom token execution needs the Atlassian base URL/subdomain
22 -
23 -Jira expects the tenant URL in the form `https://<subdomain>.atlassian.net`. Supply the `subdomain` when initiating the connected account for OAuth2, API-key, or S2S OAuth2 auth. `JIRA_GET_SERVER_INFO` can help confirm the base URL. Do not rely on the old SDK workaround that injected a raw access token through `customConnectionData`.
24 -
25 -## Jira search pagination tokens returned by current tools preserve search context
26 -
27 -Current Jira search tools wrap provider pagination tokens with the original search context. Pass the `next_page_token` returned by the same Composio action directly to its next call. If a caller instead supplies a raw Jira `nextPageToken`, it must also supply the original JQL.
28 -
29 -Workaround:
30 -
31 -- Do not pass a token returned by one Jira action to a different action.
32 -
33 -- Use the token immediately for the next page.
34 -
35 -- Do not persist old tokens or retry rejected tokens. If Jira returns `invalid or expired` even with the same original context, discard the token and restart pagination from page 1.
36 -
37 -## Jira OAuth redirect URI must match the authConfig and Atlassian app
38 -
39 -For Jira/Atlassian OAuth, configure the same redirect URI in both the Composio auth config and the Atlassian OAuth app. Copy the callback shown by the current auth-config flow or documentation and match it exactly. Do not reuse legacy v1 or v3 callback paths from older examples.
40 -
41 -## Missing `audience=api.atlassian.com` can prevent Jira refresh tokens
42 -
43 -Atlassian OAuth 2.0 requires `audience=api.atlassian.com` in the authorization URL. Without this parameter, Atlassian may not honor `offline_access`, meaning no refresh token is returned and the access token expires without being refreshable. If Jira credentials expire immediately, check whether the connected account is missing `offline_access` and whether the Jira OAuth config includes the required `audience` parameter. As an urgent workaround, API key auth with Atlassian email + API token can provide stable non-expiring credentials.
44 -
45 -## Use `JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS` instead of deprecated create metadata behavior
46 -
47 -Use `JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS` for the closest replacement behavior to the deprecated `JIRA_GET_ISSUE_CREATE_METADATA` flow. The replacement was added after Jira deprecated the older create-metadata API behavior.
48 -
49 -## Download Jira attachments with `JIRA_GET_ATTACHMENT`
50 -
51 -Use `JIRA_GET_ATTACHMENT` to retrieve the binary content of a Jira attachment by attachment ID. This tool is intended for downloading a specific file attached to a Jira issue.
52 -
53 -## Jira tool-call payload retention follows the project log-storage setting
54 -
55 -Composio manages Jira OAuth tokens and returns Jira API responses to the customer's application. Whether request and response payloads are retained in Composio tool logs follows the project's log-storage setting; **Don't store data** omits payload content from new log rows but preserves audit metadata. The customer's own agent or application may retain tool outputs separately.
56 -
57 -## Jira service account use requires customer-owned credentials and scopes
58 -
59 -For Jira service-account-style usage, customers should use their own credentials with the required Jira and Jira service-account scopes when no dedicated managed auth app is available for that flow.
docs/content/kb/guide/toolkits-kickbox.mdx deleted
-45
@@ -1,45 +0,0 @@
1 ----
2 -title: "Kickbox"
3 -description: "Public support knowledge for Kickbox."
4 -keywords: ["for-you","kickbox","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/kickbox/public.md","sourceHeading":"Single verification auth and EU endpoint checks"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["kickbox"]
11 -aliases: []
12 ----
13 -## Single verification auth and EU endpoint checks
14 -
15 -For `KICKBOX_SINGLE_VERIFICATION_API`, the Composio credential field is `generic_api_key`. For direct/custom credential execution, customers should pass:
16 -
17 -```json
18 -{
19 - "val": {
20 - "generic_api_key": "<KICKBOX_API_KEY>"
21 - }
22 -}
23 -```
24 -
25 -Do not assume `api_key` is the correct field name for Composio custom credential data. The Kickbox provider API itself documents an `apikey` query parameter, but Kickbox's official quickstart also says `Authorization: Bearer <API key>` is accepted. Composio currently uses the Bearer header and `https://api.kickbox.com/v2/verify`, which is valid for standard Kickbox accounts.
26 -
27 -If Kickbox returns 403 `Invalid API key`, verify:
28 -
29 -- the redacted `custom_connection_data.val` shape
30 -
31 -- key validity
32 -
33 -- key permissions
34 -
35 -- account/credit state
36 -
37 -- whether the Kickbox account is EU-only
38 -
39 -Kickbox docs say EU-only accounts that sign in from `app.eu.kickbox.com` must use `api.eu.kickbox.com`. If your account is EU-only, contact Composio support about a possible toolkit base-URL/region gap because the current toolkit uses the standard `api.kickbox.com` host.
40 -
41 -Useful source docs:
42 -
43 -- Single Verification API: https://docs.kickbox.com/docs/single-verification-api
44 -
45 -- API Quickstart / authentication and EU endpoint note: https://docs.kickbox.com/docs/using-the-api
docs/content/kb/guide/toolkits-klaviyo.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "Klaviyo"
3 -description: "Public support knowledge for Klaviyo."
4 -keywords: ["for-you","klaviyo","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/klaviyo/public.md","sourceHeading":"Klaviyo schema keys that exceeded Claude's 64-character limit were fixed"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["klaviyo"]
11 -aliases: []
12 ----
13 -## Klaviyo schema keys that exceeded Claude's 64-character limit were fixed
14 -
15 -For Klaviyo tool schemas that failed Claude validation because flattened nested property keys exceeded 64 characters, the backend schema-generation issue was fixed in the latest version. Update or re-fetch the latest tools/schema before retrying. The same fix also addressed top-level parameter naming issues such as `$` prefixes; nested `$` parameters were verified as accepted across major model providers and SDKs.
docs/content/kb/guide/toolkits-kommo.mdx deleted
-17
@@ -1,17 +0,0 @@
1 ----
2 -title: "Kommo"
3 -description: "Public authentication and subdomain troubleshooting for Kommo."
4 -keywords: ["for-you","kommo","oauth","platform","subdomain","authentication","errors-and-troubleshooting","toolkits-and-providers","/kb/toolkits/enter-only-the-kommo-account-subdomain","enter-only-the-kommo-account-subdomain"]
5 -sources: [{"sourcePath":"toolkits/kommo/public.md","sourceHeading":"Enter only the Kommo account subdomain"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["kommo"]
11 -aliases: ["/kb/toolkits/enter-only-the-kommo-account-subdomain","enter-only-the-kommo-account-subdomain"]
12 ----
13 -## Enter only the Kommo account subdomain
14 -
15 -The **Subdomain** field should contain only the part before `.kommo.com` in the account URL. For `https://yourcompany.kommo.com`, enter `yourcompany`, not an email domain or a value containing `.com` or dots.
16 -
17 -If a failed connection already exists, delete it, reconnect, and enter the corrected subdomain.
docs/content/kb/guide/toolkits-launch-darkly.mdx deleted
-26
@@ -1,26 +0,0 @@
1 ----
2 -title: "LaunchDarkly"
3 -description: "Public support knowledge for LaunchDarkly."
4 -keywords: ["for-you","launch_darkly","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/launchdarkly-troubleshooting","feasibility-notes","launchdarkly-troubleshooting","oauth-client-actions-are-not-oauth-connection-support"]
5 -sources: [{"sourcePath":"toolkits/launch_darkly/public.md","sourceHeading":"LaunchDarkly currently uses a REST API access token"},{"sourcePath":"toolkits/launch_darkly/public.md","sourceHeading":"OAuth client actions operate after toolkit authentication"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["launch_darkly"]
11 -aliases: ["/kb/toolkits/launchdarkly-troubleshooting","feasibility-notes","launchdarkly-troubleshooting","oauth-client-actions-are-not-oauth-connection-support"]
12 ----
13 -## LaunchDarkly currently uses a REST API access token
14 -
15 -LaunchDarkly in Composio currently uses a LaunchDarkly REST API access token.
16 -
17 -## OAuth client actions operate after toolkit authentication
18 -
19 -The LaunchDarkly toolkit includes actions such as `Create OAuth 2.0 Client`. These call LaunchDarkly endpoints like `POST /oauth/clients` after the toolkit is already authenticated with an API access token.
20 -
21 -Use this distinction when replying to customers:
22 -
23 -- The action can create or manage a LaunchDarkly OAuth client inside LaunchDarkly.
24 -
25 -- The current toolkit connection still uses the LaunchDarkly REST API access
26 - token described above.
docs/content/kb/guide/toolkits-linear.mdx deleted
-17
@@ -1,17 +0,0 @@
1 ----
2 -title: "Linear"
3 -description: "Public trigger configuration guidance for Linear."
4 -keywords: ["for-you","linear","platform","team_id","triggers","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/linear-triggers-require-a-valid-team-id","linear-triggers-require-a-valid-team-id"]
5 -sources: [{"sourcePath":"toolkits/linear/public.md","sourceHeading":"Linear triggers require a valid `team_id`"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["linear"]
11 -aliases: ["/kb/toolkits/linear-triggers-require-a-valid-team-id","linear-triggers-require-a-valid-team-id"]
12 ----
13 -## Linear triggers require a valid `team_id`
14 -
15 -`team_id` is required for Linear triggers. An invalid-input error during trigger or webhook creation usually means the supplied team ID is missing or invalid.
16 -
17 -Use `LINEAR_LIST_LINEAR_TEAMS` to retrieve valid team IDs, then pass the selected team ID into the trigger configuration.
docs/content/kb/guide/toolkits-linkedin.mdx deleted
-45
@@ -1,45 +0,0 @@
1 ----
2 -title: "LinkedIn"
3 -description: "Public support knowledge for LinkedIn."
4 -keywords: ["for-you","linkedin","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/linkedin-troubleshooting","fetch-modern-linkedin-tools-with-toolkit-slug-linkedin-and-toolkit-ver","fix-linkedin-426-nonexistent-version","fix-linkedin-ads-redirect-uri-mismatch-before-debugging-scopes","linkedin-ads-unauthorized-scope-error-means-a-requested-scope-is-unava","linkedin-company-actions-require-organization-scopes","linkedin-get-company-info-currently-returns-one-company-profile","linkedin-post-creation-supports-image-arrays-through-sdk-api","linkedin-troubleshooting","use-connect-mcp-instead-of-legacy-platform-mcp-for-consumer-linkedin-c"]
5 -sources: [{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"Fix LinkedIn 426 NONEXISTENT_VERSION by using the latest toolkit version"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"Fetch modern LinkedIn tools with `toolkit_slug=linkedin` and `toolkit_versions=latest`"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"LinkedIn organization scopes depend on the toolkit and auth config"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"LinkedIn post creation supports image arrays through SDK/API"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"Use Connect MCP instead of legacy Platform MCP for consumer LinkedIn connector flows"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"Fix LinkedIn Ads `redirect_uri` mismatch before debugging scopes"},{"sourcePath":"toolkits/linkedin/public.md","sourceHeading":"LinkedIn Ads `unauthorized_scope_error` means a requested scope is unavailable"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["linkedin"]
11 -aliases: ["/kb/toolkits/linkedin-troubleshooting","fetch-modern-linkedin-tools-with-toolkit-slug-linkedin-and-toolkit-ver","fix-linkedin-426-nonexistent-version","fix-linkedin-ads-redirect-uri-mismatch-before-debugging-scopes","linkedin-ads-unauthorized-scope-error-means-a-requested-scope-is-unava","linkedin-company-actions-require-organization-scopes","linkedin-get-company-info-currently-returns-one-company-profile","linkedin-post-creation-supports-image-arrays-through-sdk-api","linkedin-troubleshooting","use-connect-mcp-instead-of-legacy-platform-mcp-for-consumer-linkedin-c"]
12 ----
13 -## Fix LinkedIn 426 NONEXISTENT_VERSION by using the latest toolkit version
14 -
15 -LinkedIn 426 `NONEXISTENT_VERSION` errors usually mean the request is using an older LinkedIn API version header. In Composio, this often happens when calls run on the base toolkit version `00000000_00` or another older pinned version. Specify the latest LinkedIn toolkit version on tool calls, or pin to the current fixed version if needed. If the error persists after switching to the latest version, contact Composio support with a failed call `logId` or request ID so the actual `LinkedIn-Version` header can be verified.
16 -
17 -## Fetch modern LinkedIn tools with `toolkit_slug=linkedin` and `toolkit_versions=latest`
18 -
19 -The v3 tools-list endpoint defaults to the base toolkit version when no toolkit version is specified, which can return only legacy LinkedIn slugs. Use the singular filter `toolkit_slug=linkedin`; plural or alternate filters such as `toolkit_slugs`, `toolkits`, `app`, or `app_names` may be ignored. Add `toolkit_versions=latest`. Example: `GET /api/v3/tools?toolkit_slug=linkedin&toolkit_versions=latest&limit=100`.
20 -
21 -## LinkedIn organization scopes depend on the toolkit and auth config
22 -
23 -An active LinkedIn connection can run personal/profile actions while organization actions return 403. Check the actual toolkit and scopes stored on the auth config: the standard LinkedIn flow commonly uses personal scopes, while LinkedIn Ads can request organization and advertising scopes.
24 -
25 -For organization ACLs, page statistics, or company-page posting, use an auth config that explicitly requests the required organization scopes and reconnect so LinkedIn issues a new grant. Reconnecting an unchanged config does not add scopes. Do not assume provider approval alone means those scopes were requested by the concrete connection.
26 -
27 -## LinkedIn post creation supports image arrays through SDK/API
28 -
29 -`LINKEDIN_CREATE_LINKED_IN_POST` supports image + text posting, including multiple images when using SDKs or APIs directly. Pass an array of values to the `images` field. If image posting fails, first confirm you are using a recent toolkit version, then contact Composio support with log IDs from failed tool calls if needed.
30 -
31 -## Use Connect MCP instead of legacy Platform MCP for consumer LinkedIn connector flows
32 -
33 -For consumer/client connector flows, use `connect.composio.dev` / Connect MCP rather than the legacy Platform MCP endpoint. The API key does not belong in the URL; configure the `x-consumer-api-key` header shown by the current AI Clients setup. If LinkedIn MCP calls fail with 401 despite an active connection, confirm the endpoint and header type. If the error persists, contact Composio support with the exact error and log ID.
34 -
35 -## Fix LinkedIn Ads `redirect_uri` mismatch before debugging scopes
36 -
37 -If LinkedIn rejects authorization with `The redirect_uri does not match the registered value`, register the exact callback shown by the current Composio auth-config flow in the customer's LinkedIn developer app. Do not guess between legacy v1, v3, and v3.1 callback paths; copy the callback from the current setup UI or auth-config documentation and match it exactly, without adding a trailing slash.
38 -
39 -This error occurs before a successful callback and is separate from LinkedIn product or scope approval.
40 -
41 -## LinkedIn Ads `unauthorized_scope_error` means a requested scope is unavailable
42 -
43 -LinkedIn rejects the complete OAuth request when any requested scope is unavailable to the developer app. Compare the exact auth-config scope set with the products and scopes enabled on that same LinkedIn app.
44 -
45 -The default LinkedIn Ads flow includes OpenID Connect scopes (`openid`, `profile`, `email`) as well as advertising and organization scopes. Legacy `r_basicprofile` is not a substitute for the OpenID Connect scopes. Enable the relevant LinkedIn products or narrow a custom auth config to scopes the app actually has, then reconnect.
docs/content/kb/guide/toolkits-mailchimp.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Mailchimp"
3 -description: "Public support knowledge for Mailchimp."
4 -keywords: ["for-you","mailchimp","platform","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/mailchimp-troubleshooting","mailchimp-has-trigger-support-in-the-supported-trigger-toolkit-list","mailchimp-proxy-execute-with-raw-access-token-also-needs-subdomain","mailchimp-server-prefix-is-the-url-prefix-before-admin-mailchimp-com","mailchimp-troubleshooting","some-mailchimp-tools-require-at-least-the-mailchimp-essentials-plan","use-subdomain-or-dc-not-server-prefix-for-mailchimp-connectionconfig"]
5 -sources: [{"sourcePath":"toolkits/mailchimp/public.md","sourceHeading":"Mailchimp server prefix is the URL prefix before .admin.mailchimp.com"},{"sourcePath":"toolkits/mailchimp/public.md","sourceHeading":"Use subdomain or dc, not server_prefix, for Mailchimp connectionConfig"},{"sourcePath":"toolkits/mailchimp/public.md","sourceHeading":"Some Mailchimp tools require at least the Mailchimp Essentials plan"},{"sourcePath":"toolkits/mailchimp/public.md","sourceHeading":"Mailchimp Proxy Execute with raw access token also needs subdomain"},{"sourcePath":"toolkits/mailchimp/public.md","sourceHeading":"Mailchimp has trigger support in the supported-trigger toolkit list"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["mailchimp"]
11 -aliases: ["/kb/toolkits/mailchimp-troubleshooting","mailchimp-has-trigger-support-in-the-supported-trigger-toolkit-list","mailchimp-proxy-execute-with-raw-access-token-also-needs-subdomain","mailchimp-server-prefix-is-the-url-prefix-before-admin-mailchimp-com","mailchimp-troubleshooting","some-mailchimp-tools-require-at-least-the-mailchimp-essentials-plan","use-subdomain-or-dc-not-server-prefix-for-mailchimp-connectionconfig"]
12 ----
13 -## Mailchimp server prefix is the URL prefix before .admin.mailchimp.com
14 -
15 -When connecting Mailchimp, pass the correct server prefix. It is the part of the Mailchimp URL before `.admin.mailchimp.com`. For example, if the Mailchimp URL is `https://us19.admin.mailchimp.com/`, the server prefix is `us19`. A wrong prefix can cause Mailchimp API calls to fail even if the API key/token itself looks correct.
16 -
17 -## Use subdomain or dc, not server_prefix, for Mailchimp connectionConfig
18 -
19 -For Mailchimp API connection configuration, send `connectionConfig.subdomain` with the server prefix value, or use the legacy alias `dc`. Do not send `server_prefix`; that key is ignored by the validator and may fall back to a default such as `us21`. The UI label may say Server Prefix, but the API field name is `subdomain`.
20 -
21 -## Some Mailchimp tools require at least the Mailchimp Essentials plan
22 -
23 -If Mailchimp tools fail despite the connection looking correct, check the customer's Mailchimp plan. Some Mailchimp API/tool capabilities require at least the Mailchimp Essentials plan. A free Mailchimp account may not be enough for the requested tool flow.
24 -
25 -## Mailchimp Proxy Execute with raw access token also needs subdomain
26 -
27 -When using Proxy Execute with Mailchimp custom connection data, include both the OAuth access token and Mailchimp `subdomain`/server prefix. The endpoint can then be called through `/api/v3/tools/execute/proxy` with `toolkitSlug: "mailchimp"`, `authScheme: "OAUTH2"`, and `val` containing `access_token` plus `subdomain` such as `us20`.
28 -
29 -## Mailchimp has trigger support in the supported-trigger toolkit list
30 -
31 -Mailchimp appears in the supported-trigger toolkit list. Before using a specific Mailchimp trigger, verify that the exact trigger or event exists in the current toolkit. If it does not, submit the use case through the Composio request portal.
docs/content/kb/guide/toolkits-marketstack.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Marketstack"
3 -description: "Public support knowledge for Marketstack."
4 -keywords: ["for-you","marketstack","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/marketstack/public.md","sourceHeading":"API Coverage"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["marketstack"]
11 -aliases: []
12 ----
13 -## API Coverage
14 -
15 -Marketstack's official APILayer v2 OpenAPI spec includes live and intraday market data endpoints that are not yet exposed by the current Composio Marketstack toolkit actions:
16 -
17 -- `/stockprice`
18 -
19 -- `/intraday`
20 -
21 -- `/intraday/latest`
22 -
23 -- `/intraday/{date}`
24 -
25 -- `/tickers/{symbol}/intraday`
26 -
27 -- `/tickers/{symbol}/intraday/latest`
28 -
29 -- `/exchanges/{mic}/intraday`
30 -
31 -- `/exchanges/{mic}/intraday/latest`
32 -
33 -- `/exchanges/{mic}/intraday/{date}`
34 -
35 -Supported intraday intervals in the OpenAPI spec are `1min`, `5min`, `10min`, `15min`, `30min`, and `1hour`. Intraday docs note that some TOPS feed fields can be null without IEX entitlement, while derived intraday data is available without an additional IEX market data agreement.
36 -
37 -Current Composio toolkit coverage includes EOD, ticker EOD, ticker EOD latest, ticker info/listing, exchange info/listing, splits, dividends, and currencies. Live quotes and 1D charts are not currently exposed as Marketstack toolkit actions; submit those capabilities through the Composio request portal rather than treating them as provider limitations.
38 -
39 -Do not promise Marketstack support for gainers, losers, most-active, movers, or sector-performance endpoints based on current v2 docs. Those paths are not present in the official OpenAPI spec as of 2026-06-21.
docs/content/kb/guide/toolkits-microsoft-teams.mdx deleted
-129
@@ -1,129 +0,0 @@
1 ----
2 -title: "Microsoft Teams"
3 -description: "Public support knowledge for Microsoft Teams."
4 -keywords: ["for-you","microsoft_teams","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/microsoft-teams-troubleshooting","microsoft-teams-chats-get-all-chats-and-microsoft-teams-create-meeting","microsoft-teams-delegated-permissions-should-be-checked-with-get-scope","microsoft-teams-mcp-access-is-tied-to-the-connected-account-user-id-us","microsoft-teams-often-needs-customer-owned-azure-oauth-credentials-and","microsoft-teams-one-on-one-chat-creation-needs-two-users-and-correct-o","microsoft-teams-tool-listing-may-return-only-20-tools-unless-limit-is","microsoft-teams-troubleshooting","some-microsoft-teams-slugs-were-restored-as-deprecated-aliases-with-re","teams-chat-tools-return-400-403-404-when-user-ids-or-chat-membership-d","tool-router-memory-for-microsoft-teams-should-be-a-list-under-the-tool"]
5 -sources: [{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Microsoft Teams delegated permissions should be checked with `get_scopes_required` and `toolkit_versions[microsoft_teams]=latest`"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Invalid OAuth scope: `ChannelMessage.Read.Group`"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"`MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` and `MICROSOFT_TEAMS_CREATE_MEETING` can work with delegated user scopes"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Microsoft Teams often needs customer-owned Azure OAuth credentials and tenant admin consent"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Microsoft Teams one-on-one chat creation needs two users and correct OData bind format"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Microsoft Teams MCP access is tied to the connected account `user_id` used in the MCP URL"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Teams chat tools return 400/403/404 when user IDs or chat membership do not match Microsoft Graph expectations"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Microsoft Teams tool listing may return only 20 tools unless `limit` is increased"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Some Microsoft Teams slugs were restored as deprecated aliases with replacement descriptions"},{"sourcePath":"toolkits/microsoft_teams/public.md","sourceHeading":"Tool Router memory for Microsoft Teams should be a list under the toolkit key"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["microsoft_teams"]
11 -aliases: ["/kb/toolkits/microsoft-teams-troubleshooting","microsoft-teams-chats-get-all-chats-and-microsoft-teams-create-meeting","microsoft-teams-delegated-permissions-should-be-checked-with-get-scope","microsoft-teams-mcp-access-is-tied-to-the-connected-account-user-id-us","microsoft-teams-often-needs-customer-owned-azure-oauth-credentials-and","microsoft-teams-one-on-one-chat-creation-needs-two-users-and-correct-o","microsoft-teams-tool-listing-may-return-only-20-tools-unless-limit-is","microsoft-teams-troubleshooting","some-microsoft-teams-slugs-were-restored-as-deprecated-aliases-with-re","teams-chat-tools-return-400-403-404-when-user-ids-or-chat-membership-d","tool-router-memory-for-microsoft-teams-should-be-a-list-under-the-tool"]
12 ----
13 -Use this guide to configure Microsoft Teams scopes, fix stale OAuth metadata, connect through MCP, and troubleshoot chat or tool execution.
14 -
15 -## Configure Microsoft Teams scopes and Azure consent
16 -
17 -**Check delegated permissions against the latest tool version.** For Microsoft Teams scope checks, call `/api/v3/tools/get_scopes_required` with the exact tool slug and include `toolkit_versions[microsoft_teams]=latest` when needed. Without the explicit toolkit version, the API may return data from the old `00000000_00` version.
18 -
19 -**Use the delegated scopes required by each action.** `MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` can use `Chat.ReadBasic`, `Chat.Read`, or `Chat.ReadWrite`. `MICROSOFT_TEAMS_CREATE_MEETING` requires `OnlineMeetings.ReadWrite`. Confirm exact required scopes with the latest versioned scope endpoint before changing auth config scopes.
20 -
21 -**Use customer-owned Azure credentials when custom scopes are needed.** For Microsoft Teams, recommend using the customer's own Azure/Microsoft developer app credentials when custom scopes are needed. Additional scopes should be added in the Microsoft app, and admin consent may need to be granted in Azure before the connection has usable permissions.
22 -
23 -## Fix the invalid OAuth scope `ChannelMessage.Read.Group`
24 -
25 -If Microsoft Teams OAuth fails before consent with:
26 -
27 -```text
28 -AADSTS650053: The application asked for scope 'ChannelMessage.Read.Group' that doesn't exist on the resource Microsoft Graph.
29 -```
30 -
31 -treat `ChannelMessage.Read.Group` as the wrong auth layer for the Composio delegated OAuth flow. It is a Microsoft Teams resource-specific consent (RSC) permission, not a normal Microsoft Graph OAuth scope to include in an OAuth `/authorize` URL.
32 -
33 -Debug steps:
34 -
35 -- Check whether the customer is using v3 base/default tool metadata or old Teams slugs.
36 -
37 -- `MICROSOFT_TEAMS_TEAMS_GET_MESSAGE` on v3 base can return `ChannelMessage.Read.Group`; the latest/v3.1 replacement is `MICROSOFT_TEAMS_GET_CHANNEL_MESSAGE`.
38 -
39 -- Use v3.1 or pass `toolkit_versions[microsoft_teams]=latest` when fetching tools/scopes.
40 -
41 -- Remove `ChannelMessage.Read.Group` from the OAuth auth config scopes and use `ChannelMessage.Read.All`, `Group.Read.All`, or `Group.ReadWrite.All` according to the latest tool scope response.
42 -
43 -- If an existing auth config already includes the invalid scope, update or recreate it and reconnect. Existing connected accounts may need refresh/reconnect depending on how the customer propagates scope changes.
44 -
45 -### Compare the legacy response
46 -
47 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
48 -
49 -<Tab value="Python">
50 -<Callout type="info">
51 -
52 -The Python SDK does not select the legacy `/api/v3` metadata route. Use the API option to reproduce this route-specific stale response.
53 -
54 -</Callout>
55 -</Tab>
56 -
57 -<Tab value="TypeScript">
58 -<Callout type="info">
59 -
60 -The TypeScript SDK does not select the legacy `/api/v3` metadata route. Use the API option to reproduce this route-specific stale response.
61 -
62 -</Callout>
63 -</Tab>
64 -
65 -<Tab value="API">
66 -```bash
67 -curl --globoff 'https://backend.composio.dev/api/v3/tools/MICROSOFT_TEAMS_TEAMS_GET_MESSAGE' \
68 - -H "x-api-key: $COMPOSIO_API_KEY"
69 -```
70 -</Tab>
71 -
72 -</Tabs>
73 -
74 -
75 -
76 -Expected stale response includes `version: "00000000_00"` and `scopes: ["ChannelMessage.Read.Group"]`.
77 -
78 -### Fetch current tool metadata
79 -
80 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
81 -
82 -<Tab value="Python">
83 -```python
84 -from composio import Composio
85 -
86 -composio = Composio(toolkit_versions={"microsoft_teams": "latest"})
87 -tool = composio.tools.get_raw_composio_tool_by_slug("MICROSOFT_TEAMS_GET_CHANNEL_MESSAGE")
88 -print(tool.scopes)
89 -```
90 -</Tab>
91 -
92 -<Tab value="TypeScript">
93 -```typescript
94 -import { Composio } from "@composio/core";
95 -
96 -const composio = new Composio({ toolkitVersions: { microsoft_teams: "latest" } });
97 -const tool = await composio.tools.getRawComposioToolBySlug("MICROSOFT_TEAMS_GET_CHANNEL_MESSAGE");
98 -console.log(tool.scopes);
99 -```
100 -</Tab>
101 -
102 -<Tab value="API">
103 -```bash
104 -curl --globoff 'https://backend.composio.dev/api/v3.1/tools/MICROSOFT_TEAMS_GET_CHANNEL_MESSAGE?toolkit_versions%5Bmicrosoft_teams%5D=latest' \
105 - -H "x-api-key: $COMPOSIO_API_KEY"
106 -```
107 -</Tab>
108 -
109 -</Tabs>
110 -
111 -
112 -
113 -Expected clean response includes `ChannelMessage.Read.All`, not `ChannelMessage.Read.Group`.
114 -
115 -## Connect Teams through MCP and Tool Router
116 -
117 -**Match the MCP URL user ID to the connected account.** For Microsoft Teams MCP, the user ID in the MCP server URL/query params must match the user ID attached to the connected account. If the connection is bound to an email/GUID, use that value in the MCP URL or create a new server/connection with the desired user ID.
118 -
119 -**Pass Tool Router memory as a list under the toolkit key.** When passing Tool Router memory for Microsoft Teams, use a real list under the `microsoft_teams` key, for example `"memory": { "microsoft_teams": ["Session id..."] }`. Do not pass escaped square brackets as a string.
120 -
121 -## Create chats and troubleshoot tool execution
122 -
123 -**Pass two users with the correct OData bind format for one-on-one chats.** For Microsoft Teams one-on-one chat creation, pass two users, not one. Also make sure the OData bind payload uses the correct role and bind-data format expected by Microsoft Graph.
124 -
125 -**Validate user IDs and chat membership for 400/403/404 errors.** For `MICROSOFT_TEAMS_LIST_USER_CHAT_MESSAGES`, a 400 commonly means `user_id` was not passed as a GUID or UPN. For chat members tools, 403/404 often means the connected user is not part of the meeting chat or the chat ID is not in that user's scope. Use `MICROSOFT_TEAMS_LIST_USERS` to find valid user IDs and verify the connected user is a participant in the target chat.
126 -
127 -**Increase `limit` when the tool list stops at 20.** When fetching Microsoft Teams tools by toolkit, the default list may return only 20 tools. Increase the `limit` parameter or search for exact tool slugs to retrieve the full set.
128 -
129 -**Prefer replacement slugs over restored deprecated aliases.** Some old Microsoft Teams slugs were deleted during cleanup and then restored with a deprecated flag and descriptions pointing to the correct replacement slugs. If a Teams slug suddenly disappears or changes, check the latest toolkit version/changelog and prefer the replacement slug.
docs/content/kb/guide/toolkits-monday.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Monday"
3 -description: "Public support knowledge for Monday."
4 -keywords: ["for-you","monday","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/monday-troubleshooting","add-the-composio-redirect-url-to-the-monday-oauth-app","monday-requires-the-oauth-app-to-be-installed-in-the-workspace-before","monday-scopes-come-from-the-oauth-app-and-do-not-need-separate-composi","monday-troubleshooting","monday-update-item-body-must-be-passed-as-a-properly-escaped-string"]
5 -sources: [{"sourcePath":"toolkits/monday/public.md","sourceHeading":"Monday requires the OAuth app to be installed in the workspace before user connections"},{"sourcePath":"toolkits/monday/public.md","sourceHeading":"Add the Composio redirect URL to the Monday OAuth app"},{"sourcePath":"toolkits/monday/public.md","sourceHeading":"`MONDAY_UPDATE_ITEM` body must be passed as a properly escaped string"},{"sourcePath":"toolkits/monday/public.md","sourceHeading":"Tool Router may prefer `MONDAY_MCP` over `MONDAY` when both are available"},{"sourcePath":"toolkits/monday/public.md","sourceHeading":"Monday scopes come from the OAuth app and do not need separate Composio-side setup in the common flow"},{"sourcePath":"toolkits/monday/public.md","sourceHeading":"Monday trigger management is not handled by the agent at runtime"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["monday"]
11 -aliases: ["/kb/toolkits/monday-troubleshooting","add-the-composio-redirect-url-to-the-monday-oauth-app","monday-requires-the-oauth-app-to-be-installed-in-the-workspace-before","monday-scopes-come-from-the-oauth-app-and-do-not-need-separate-composi","monday-troubleshooting","monday-update-item-body-must-be-passed-as-a-properly-escaped-string"]
12 ----
13 -## Monday requires the OAuth app to be installed in the workspace before user connections
14 -
15 -Monday is unusual among popular toolkits because the OAuth app must be installed in the Monday workspace before users initiate individual OAuth connections. An admin can install the app once for the workspace, then users can connect normally. For Composio's managed Monday app, use the official installation control or link exposed by the current connection flow. Do not construct or share a raw OAuth URL with a hard-coded client ID.
16 -
17 -## Add the Composio redirect URL to the Monday OAuth app
18 -
19 -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 by Composio automatically.
20 -
21 -## `MONDAY_UPDATE_ITEM` body must be passed as a properly escaped string
22 -
23 -`MONDAY_UPDATE_ITEM` expects the body in a format Monday's API accepts. If you pass JSON-like text or strings containing quotes/special characters, escape those characters and send a suitable string rather than unsupported raw structured content.
24 -
25 -## Tool Router may prefer `MONDAY_MCP` over `MONDAY` when both are available
26 -
27 -If both `MONDAY` and `MONDAY_MCP` are enabled, Tool Router may choose `MONDAY_MCP` for search/execution. If you specifically need the regular Monday toolkit, disable `monday_mcp` in the session or narrow toolkit availability so `COMPOSIO_SEARCH_TOOLS` returns the intended tools.
28 -
29 -## Monday scopes come from the OAuth app and do not need separate Composio-side setup in the common flow
30 -
31 -For Monday, the scopes configured on the Monday OAuth app are picked up during authorization. In the common flow, there is no separate Composio-side scope configuration required unless you intentionally request a subset.
32 -
33 -## Monday trigger management is not handled by the agent at runtime
34 -
35 -Trigger setup and management should be handled outside the agent runtime, for example through the CLI/API/dashboard flow. The agent should consume trigger payloads, not create or manage trigger instances as part of normal tool execution.
docs/content/kb/guide/toolkits-netsuite.mdx deleted
-15
@@ -1,15 +0,0 @@
1 ----
2 -title: "NetSuite"
3 -description: "Public support knowledge for NetSuite."
4 -keywords: ["for-you","netsuite","platform","authentication","errors-and-troubleshooting","toolkits-and-providers","/kb/toolkits/netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth","netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth"]
5 -sources: [{"sourcePath":"toolkits/netsuite/public.md","sourceHeading":"NetSuite OAuth token exchange failures can be caused by generic OAuth endpoints"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["netsuite"]
11 -aliases: ["/kb/toolkits/netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth","netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth"]
12 ----
13 -## NetSuite OAuth token exchange failures can be caused by generic OAuth endpoints
14 -
15 -For NetSuite OAuth2 callback/token-exchange failures, verify whether the OAuth flow is using the customer's account-specific NetSuite authorize/token endpoint. NetSuite expects OAuth endpoints to be keyed to the NetSuite account subdomain; using a generic endpoint can produce a token-exchange failure that looks like a permissions or role problem. Check the decoded token-exchange response before advising the customer to change NetSuite roles.
docs/content/kb/guide/toolkits-notion.mdx deleted
-33
@@ -1,33 +0,0 @@
1 ----
2 -title: "Notion"
3 -description: "Public support knowledge for Notion."
4 -keywords: ["for-you","notion","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/notion-troubleshooting","large-unfiltered-notion-responses-can-hurt-agent-quality","notion-401-can-be-caused-by-invalid-refresh-token-after-user-admin-rev","notion-database-trigger-fires-for-new-pages-not-updates","notion-page-database-access-is-granted-per-integration-not-per-composi","notion-troubleshooting","repeated-notion-reconnect-loops-may-be-a-rotating-refresh-token-issue","specifying-a-different-auth-config-affects-get-use-lookup-not-existing"]
5 -sources: [{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Use `NOTION_RETRIEVE_PAGE` instead of deprecated/invalid `NOTION_GET_PAGE`"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Use the current Notion page and data-source update triggers"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Notion page/database access is granted per integration, not per Composio auth config token"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Specifying a different auth config affects get/use lookup, not existing Notion token refresh"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Notion 401 can be caused by invalid refresh token after user/admin revokes integration"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Use `NOTION_FETCH_DATA`, not `NOTION_FETCH_NOTION_DATA`"},{"sourcePath":"toolkits/notion/public.md","sourceHeading":"Large unfiltered Notion responses can hurt agent quality"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["notion"]
11 -aliases: ["/kb/toolkits/notion-troubleshooting","large-unfiltered-notion-responses-can-hurt-agent-quality","notion-401-can-be-caused-by-invalid-refresh-token-after-user-admin-rev","notion-database-trigger-fires-for-new-pages-not-updates","notion-page-database-access-is-granted-per-integration-not-per-composi","notion-troubleshooting","repeated-notion-reconnect-loops-may-be-a-rotating-refresh-token-issue","specifying-a-different-auth-config-affects-get-use-lookup-not-existing"]
12 ----
13 -Use this guide to choose current Notion tools and triggers, understand integration access, and troubleshoot connection or response-size issues.
14 -
15 -## Use current Notion tools and triggers
16 -
17 -**Retrieve pages with the current tool slug.** `NOTION_GET_PAGE` is not the current valid slug. Use `NOTION_RETRIEVE_PAGE`, and verify available Notion tools from the marketplace/tool listing.
18 -
19 -**Fetch Notion data with the current tool slug.** `NOTION_FETCH_NOTION_DATA` is not valid. Use `NOTION_FETCH_DATA` instead.
20 -
21 -**Choose the trigger that matches the Notion event.** The current Notion catalog includes separate triggers for page creation, page content updates, page property updates, and data-source schema updates. Choose the trigger that matches the event rather than expecting a page-created trigger to fire for edits. Fetch the current trigger catalog before implementation and use the exact returned slug.
22 -
23 -## Configure Notion access and connected accounts
24 -
25 -**Grant page and database access through the Notion integration.** Notion does not model access as normal OAuth scopes. Page/database access is granted per Notion integration/OAuth client ID through Notion “Capabilities” and workspace grants. If multiple Composio auth configs use the same underlying Notion integration, page authorization can overlap.
26 -
27 -**Treat auth config selection as connection lookup behavior.** Existing connected accounts under a different auth config continue to refresh and work. Specifying an auth config affects which connection get/use functions look for; it does not rewrite refresh behavior for already-valid connected accounts.
28 -
29 -## Troubleshoot Notion connections and large responses
30 -
31 -**Check for a revoked integration when Notion returns 401 or refresh fails.** A Notion refresh failure with “Invalid refresh token” is usually a token revocation issue. Common causes are the user disconnecting the integration in Notion settings or a workspace admin removing/blocking the integration.
32 -
33 -**Keep Notion responses focused.** Large response payloads and overly complex structures can degrade agent behavior. Prefer narrower fetches/filters where available and track product improvements for simpler response structures.
docs/content/kb/guide/toolkits-odoo.mdx deleted
-17
@@ -1,17 +0,0 @@
1 ----
2 -title: "Odoo"
3 -description: "Public troubleshooting guidance for Odoo tools."
4 -keywords: ["for-you","json-rpc","odoo","platform","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/inspect-odoo-json-rpc-errors-inside-http-200-responses","inspect-odoo-json-rpc-errors-inside-http-200-responses"]
5 -sources: [{"sourcePath":"toolkits/odoo/public.md","sourceHeading":"JSON-RPC access errors can arrive inside HTTP 200 responses"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["odoo"]
11 -aliases: ["/kb/toolkits/inspect-odoo-json-rpc-errors-inside-http-200-responses","inspect-odoo-json-rpc-errors-inside-http-200-responses"]
12 ----
13 -## JSON-RPC access errors can arrive inside HTTP 200 responses
14 -
15 -`ODOO_CALL_ODOO_JSONRPC` can receive HTTP 200 while the JSON-RPC body contains an `error` such as `access denied`. HTTP success only confirms transport; inspect the returned JSON-RPC envelope.
16 -
17 -Verify the instance URL, database name, API key, and the Odoo user's permission for the requested model and method. Prefer current JSON-2 tools where they cover the use case. If the body still contains an application error, share the Composio log ID and timestamp without sharing the API key.
docs/content/kb/guide/toolkits-one-drive.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "OneDrive"
3 -description: "Public support knowledge for OneDrive."
4 -keywords: ["for-you","one_drive","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/onedrive-troubleshooting","deleting-a-onedrive-connection-may-not-revoke-provider-side-tokens","disable-onedrive-destructive-actions-with-destructivehint-or-explicit","onedrive-custom-oauth-issues-usually-require-verifying-azure-app-setup","onedrive-troubleshooting","tool-router-v2-sessions-should-keep-all-connected-accounts-under-the-s","use-the-scopes-required-endpoint-to-derive-onedrive-microsoft-graph-pe"]
5 -sources: [{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"OneDrive custom OAuth issues usually require verifying Azure app setup and recreating the integration"},{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"Use the scopes-required endpoint to derive OneDrive/Microsoft Graph permissions"},{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"Pass `version=latest` if OneDrive folder/list behavior looks stale"},{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"Use file-uploadable or base64-compatible inputs for supported OneDrive actions"},{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"Tool Router v2 sessions should keep all connected accounts under the same `user_id`"},{"sourcePath":"toolkits/one_drive/public.md","sourceHeading":"Disable OneDrive destructive actions with `destructiveHint` or explicit tool disables"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["one_drive"]
11 -aliases: ["/kb/toolkits/onedrive-troubleshooting","deleting-a-onedrive-connection-may-not-revoke-provider-side-tokens","disable-onedrive-destructive-actions-with-destructivehint-or-explicit","onedrive-custom-oauth-issues-usually-require-verifying-azure-app-setup","onedrive-troubleshooting","tool-router-v2-sessions-should-keep-all-connected-accounts-under-the-s","use-the-scopes-required-endpoint-to-derive-onedrive-microsoft-graph-pe"]
12 ----
13 -Use this guide to configure OneDrive OAuth, execute current file tools, and control Tool Router sessions safely.
14 -
15 -## Configure OneDrive OAuth and scopes
16 -
17 -**Verify Azure app setup and recreate the auth config after changes.** For OneDrive custom OAuth failures, first verify the Azure OAuth app setup, especially credentials and redirect URLs. If the Azure app settings were changed, create a new Composio integration/auth config with the updated configuration and retry the connection.
18 -
19 -**Derive Microsoft Graph permissions from the tools.** For OneDrive and other Microsoft Graph-backed toolkits, use `/api/v3/tools/get_scopes_required` with the relevant tool slugs to determine the scopes needed by those tools. This is more reliable than manually guessing Microsoft Graph delegated permissions.
20 -
21 -## Use current OneDrive tools and file inputs
22 -
23 -**Pass `version=latest` when folder behavior looks stale.** If OneDrive folder listing or related tool behavior appears stale, pass `version: "latest"` in the tool execution request so the call uses the latest toolkit version instead of the default pinned version.
24 -
25 -**Use supported upload inputs for file actions.** OneDrive has upload/update tools such as `ONE_DRIVE_ONEDRIVE_UPLOAD_FILE` and `ONE_DRIVE_UPDATE_FILE_CONTENT`. Where the selected action supports it, pass file content through `FileUploadable` or the shared storage/data-URI path, including base64-backed uploads.
26 -
27 -## Configure Tool Router sessions and safety
28 -
29 -**Keep connected accounts under the same `user_id`.** In Tool Router v2, connected accounts used in one session should belong to the same `user_id`. When creating the session, pass the intended auth config IDs and make sure the connected accounts for OneDrive and the other toolkits are associated with that same user.
30 -
31 -**Disable destructive actions with tags or exact tool slugs.** Use session-level tag controls to disable destructive tools globally or per toolkit. For OneDrive, disable the `destructiveHint` tag at the toolkit/session level, or disable exact tool slugs for finer-grained control.
docs/content/kb/guide/toolkits-onenote.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "Microsoft OneNote"
3 -description: "Current authentication setup for the Microsoft OneNote toolkit."
4 -keywords: ["for-you","microsoft","onenote","platform","auth-config","authentication","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/onenote/public.md","sourceHeading":"OneNote uses a customer-owned Microsoft OAuth app"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","toolkits-and-providers"]
10 -toolkitSlugs: ["onenote"]
11 -aliases: []
12 ----
13 -## OneNote uses a customer-owned Microsoft OAuth app
14 -
15 -The current `onenote` toolkit supports OAuth2 and requires a client ID and
16 -client secret from a Microsoft Entra app registration. Enter the app's
17 -Application (client) ID and the secret **value**, not the secret's identifier.
18 -Register the exact redirect URI shown by the current Composio auth-config flow.
19 -
20 -Choose the least-privileged delegated Microsoft Graph permissions that cover
21 -the intended OneNote actions. Common permissions include `Notes.Read`,
22 -`Notes.Create`, `Notes.ReadWrite`, and the corresponding `*.All` permissions
23 -for notebooks available through groups or sites. Include `offline_access` when
24 -the connection needs a refresh token. Microsoft documents the permission set in
25 -its [Graph permissions reference](https://learn.microsoft.com/en-us/graph/permissions-reference#notesreadwrite).
26 -
27 -Tenant policy or higher-privilege permissions can require administrator
28 -consent. Follow the shared Microsoft OAuth guidance and create a fresh
29 -connection after changing the app's permissions.
docs/content/kb/guide/toolkits-openai.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "OpenAI"
3 -description: "Public support knowledge for OpenAI."
4 -keywords: ["for-you","openai","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/openai-troubleshooting","append-session-experimental-assistiveprompt-when-gpt-models-are-flaky","openai-create-image-supports-gpt-image-2-in-the-latest-toolkit-version","openai-troubleshooting","pin-auth-config-and-connected-account-ids-in-tool-router-sessions-when","provider-schema-bugs-often-require-upgrading-composio-sdk-packages-tog","use-beforeexecute-modifiers-to-add-a-human-approval-layer-before-tool","use-openaiagentsprovider-when-wiring-composio-tools-into-openai-agents"]
5 -sources: [{"sourcePath":"toolkits/openai/public.md","sourceHeading":"`OPENAI_CREATE_IMAGE` supports `gpt-image-2` in the latest toolkit version"},{"sourcePath":"toolkits/openai/public.md","sourceHeading":"Use `OpenAIAgentsProvider` when wiring Composio tools into OpenAI Agents"},{"sourcePath":"toolkits/openai/public.md","sourceHeading":"Pin auth config and connected account IDs in Tool Router sessions when a specific connection must be used"},{"sourcePath":"toolkits/openai/public.md","sourceHeading":"Use `beforeExecute` modifiers to add a human approval layer before tool execution"},{"sourcePath":"toolkits/openai/public.md","sourceHeading":"Provider/schema compatibility errors often require upgrading Composio SDK packages together"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["openai"]
11 -aliases: ["/kb/toolkits/openai-troubleshooting","append-session-experimental-assistiveprompt-when-gpt-models-are-flaky","openai-create-image-supports-gpt-image-2-in-the-latest-toolkit-version","openai-troubleshooting","pin-auth-config-and-connected-account-ids-in-tool-router-sessions-when","provider-schema-bugs-often-require-upgrading-composio-sdk-packages-tog","use-beforeexecute-modifiers-to-add-a-human-approval-layer-before-tool","use-openaiagentsprovider-when-wiring-composio-tools-into-openai-agents"]
12 ----
13 -## `OPENAI_CREATE_IMAGE` supports `gpt-image-2` in the latest toolkit version
14 -
15 -`gpt-image-2` has been shipped and can be used through `OPENAI_CREATE_IMAGE` on the latest toolkit version. If the model is missing, have the customer update the toolkit/tool version before retrying.
16 -
17 -## Use `OpenAIAgentsProvider` when wiring Composio tools into OpenAI Agents
18 -
19 -For OpenAI Agents, initialize Composio with `OpenAIAgentsProvider`, create a session for the user, fetch tools from the session, and pass those tools into the OpenAI Agent. This is the expected provider path when using the OpenAI Agents SDK with Composio.
20 -
21 -## Pin auth config and connected account IDs in Tool Router sessions when a specific connection must be used
22 -
23 -When creating a Tool Router session, pass the desired `authConfigId` and `connectedAccountId` in the session creation options. Use `authConfigs: { [toolkitSlug]: authConfigId }` and `connectedAccounts: { [toolkitSlug]: connectedAccountId }` so the session uses that specific connection instead of relying on discovery/default selection.
24 -
25 -## Use `beforeExecute` modifiers to add a human approval layer before tool execution
26 -
27 -Composio SDK modifiers can be used to add a gating layer before tool execution. Implement a `beforeExecute` modifier to inspect the tool call, request approval, and only allow the execution to continue when the customer's approval logic passes.
28 -
29 -## Provider/schema compatibility errors often require upgrading Composio SDK packages together
30 -
31 -When debugging provider/schema errors with OpenAI or LangChain-style integrations, upgrade both the core Composio package and the relevant provider package to their latest compatible versions before retesting.
docs/content/kb/guide/toolkits-outlook.mdx deleted
-51
@@ -1,51 +0,0 @@
1 ----
2 -title: "Outlook"
3 -description: "Public support knowledge for Outlook."
4 -keywords: ["for-you","outlook","platform","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/outlook-troubleshooting","an-active-outlook-connection-can-have-a-disabled-webhook-trigger","connect-mcp-exposes-meta-tools-not-individual-outlook-tools-by-design","incomplete-outlook-auth-links-expire-after-about-10-minutes-and-mark-t","outlook-desktop-users-still-need-to-authenticate-the-cloud-microsoft-a","outlook-email-categories-and-send-draft-pin-email-support-may-need-too","outlook-gmail-email-attachments-through-sdk-should-be-passed-as-file-p","outlook-microsoft-apps-may-need-admin-consent-from-app-registration-or","outlook-multi-account-sessions-require-explicit-per-call-account-selec","outlook-troubleshooting","remove-old-bad-outlook-tool-slugs-from-mcp-configs-and-patch-allowed-t","target-outlook-shared-mailboxes-by-address","use-get-scopes-required-with-outlook-tool-slugs-then-refresh-reconnect"]
5 -sources: [{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Outlook desktop users still need to authenticate the cloud Microsoft account in browser"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Connect MCP exposes meta-tools, not individual Outlook tools, by design"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"For Outlook shared mailboxes, pass the shared mailbox address as `user_id`/mailbox target"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Remove obsolete or invalid Outlook tool slugs from MCP configs and patch `allowed_tools`"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Outlook multi-account sessions require explicit per-call `account` selection and aliases"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Use `get_scopes_required` with Outlook tool slugs, then refresh/reconnect after scope changes"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Outlook/Microsoft apps may need admin consent from App Registration or Enterprise Applications"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Outlook/Gmail email attachments through SDK should be passed as file paths"},{"sourcePath":"toolkits/outlook/public.md","sourceHeading":"Incomplete Outlook auth links expire after about 10 minutes and mark the connection `EXPIRED`"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["outlook"]
11 -aliases: ["/kb/authentication/outlook-troubleshooting","an-active-outlook-connection-can-have-a-disabled-webhook-trigger","connect-mcp-exposes-meta-tools-not-individual-outlook-tools-by-design","incomplete-outlook-auth-links-expire-after-about-10-minutes-and-mark-t","outlook-desktop-users-still-need-to-authenticate-the-cloud-microsoft-a","outlook-email-categories-and-send-draft-pin-email-support-may-need-too","outlook-gmail-email-attachments-through-sdk-should-be-passed-as-file-p","outlook-microsoft-apps-may-need-admin-consent-from-app-registration-or","outlook-multi-account-sessions-require-explicit-per-call-account-selec","outlook-troubleshooting","remove-old-bad-outlook-tool-slugs-from-mcp-configs-and-patch-allowed-t","target-outlook-shared-mailboxes-by-address","use-get-scopes-required-with-outlook-tool-slugs-then-refresh-reconnect"]
12 ----
13 -Use this guide to authorize Outlook, resolve Microsoft tenant consent, and target the correct mailbox or account through MCP and direct execution.
14 -
15 -## Connect and authorize Outlook
16 -
17 -**Authenticate the cloud Microsoft account in a browser.** Outlook tools authenticate through the Microsoft account/OAuth flow in a browser. Even if you only use Outlook desktop, log into the underlying Microsoft/Outlook account in the browser to complete OAuth. Desktop and cloud use the same account, so once the account is authenticated, the tools can operate against that mailbox.
18 -
19 -**Check exact tool scopes, then reconnect after changes.** For Outlook 403s, look up required scopes with `/api/v3/tools/get_scopes_required` using the exact Outlook tool slug, not the toolkit name. For example `OUTLOOK_GET_MAILBOX_SETTINGS` requires `MailboxSettings.ReadWrite`. After adding scopes to the auth config, create a new auth link session and have the user reconnect so the new scopes are granted.
20 -
21 -**Complete auth links within about 10 minutes.** If a connected account expires because the initiation flow was not completed, the likely reason is that the authorization link timed out. Users have roughly a 10-minute window to complete the auth flow; otherwise Composio invalidates the link and marks the connected account `EXPIRED`.
22 -
23 -## Grant Microsoft tenant admin consent
24 -
25 -Microsoft/Outlook admin-consent issues are Microsoft 365 tenant-level approval problems, not a Composio-side connection configuration issue. Adding delegated permissions to an Azure app registration is not the same as granting tenant admin consent. Once a tenant admin grants consent for the requested permissions, affected users should start a fresh normal Outlook connection flow with their own accounts; the admin does not need to connect every user individually.
26 -
27 -Two concrete ways an admin can approve:
28 -
29 -1. **App Registration / OAuth app level:** in Microsoft Entra / Azure Portal, go to **App registrations**, open the OAuth app, go to **API permissions**, click **Grant admin consent for [Tenant Name]**, then confirm/save.
30 -
31 -2. **Enterprise Applications / org level:** in Microsoft Entra / Azure Portal, go to **Enterprise applications**, find the Composio/Outlook app or the customer's own service principal, open **Permissions** / admin-consent controls, then grant admin consent for the organization.
32 -
33 -For the Composio-managed Outlook app, Microsoft's in-flow `sign in as an admin` / `Connectez-vous avec ce compte` link is also a real tenant-admin consent path. If the admin signs in through that same OAuth attempt, that attempt may connect the admin's mailbox, not the original user's mailbox; treat that connected account as the admin's and have the original user start a fresh Connect flow afterward. Incomplete/pending Outlook connection attempts expire after about 10 minutes, so an expired non-admin attempt cannot be resumed. Nothing needs to happen on Composio's side between the admin grant and the user's retry: no cache clear, webhook, or manual status change.
34 -
35 -Composio does not publish a `client_id` for its managed Outlook app for use in direct Microsoft `adminconsent` URLs. Do not guess this value. For a customer-owned/BYOA Azure app, use your own app's `client_id` and tenant ID in Microsoft's admin-consent URL.
36 -
37 -A customer-owned verified-publisher Azure app can improve branding/control and may reduce consent friction in tenants that allow user consent for verified publishers and the requested delegated permissions. It does not guarantee that no admin approval is needed: each Microsoft tenant's user-consent policy and the exact scopes requested still decide whether admin consent is required.
38 -
39 -## Use Outlook through MCP and direct execution
40 -
41 -**Expect Tool Router meta-tools on Connect MCP.** `connect.composio.dev/mcp` uses Tool Router architecture, so it intentionally exposes meta-tools such as `COMPOSIO_SEARCH_TOOLS` and `COMPOSIO_MULTI_EXECUTE_TOOL`. The agent discovers and executes Outlook tools at runtime through those meta-tools. If you need specific Outlook tools without meta-tool round trips, use SDK direct execution or create a focused MCP config with selected Outlook tools.
42 -
43 -**Remove obsolete slugs from MCP configs.** If an Outlook MCP config fails due to obsolete or invalid tool slugs, update the MCP config to remove them and include only current supported tools in `allowed_tools`. This can be done through the dashboard or the MCP patch endpoint.
44 -
45 -**Pass attachment file paths through the SDK.** When using SDK automatic file handling for email attachments, pass the local file path directly in the `attachment`/`attachments` argument. Do not pass only a filename or raw content fields unless the tool schema explicitly asks for them.
46 -
47 -## Target shared mailboxes and multiple accounts
48 -
49 -**Pass the shared mailbox address as `user_id` or the mailbox target.** Delegated access must already be granted in the Microsoft tenant. This applies to delegated and S2S/application auth patterns where the tenant permissions allow shared mailbox access.
50 -
51 -**Select an aliased account on every multi-account call.** For multi-account Outlook sessions, every connected account needs a unique non-null alias, the session should set `multi_account.enable=true` and `require_explicit_selection=true`, and the LLM must set the `account` field on each item in `COMPOSIO_MULTI_EXECUTE_TOOL.tools[]`. Without explicit selection, Tool Router cannot disambiguate and may default to one account.
docs/content/kb/guide/toolkits-perplexityai.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Perplexity AI authentication"
3 -description: "Current API-key setup for the Perplexity AI toolkit."
4 -keywords: ["for-you","perplexityai","platform","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/perplexityai/public.md","sourceHeading":"Perplexity AI uses the `generic_api_key` connection field"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["perplexityai"]
11 -aliases: []
12 ----
13 -## Perplexity AI uses the `generic_api_key` connection field
14 -
15 -The current `perplexityai` toolkit uses API-key authentication. Create the key
16 -in Perplexity's console and provide it as `generic_api_key` during connection
17 -initiation. The key is shown once by the provider, so store it in the
18 -customer's secret manager and never send it to support.
19 -
20 -If a first-party Perplexity tool succeeds but an equivalent Proxy Execute call
21 -returns 401 with the same connection, collect both Log IDs and the redacted
22 -request path. That comparison distinguishes a proxy auth-injection problem from
23 -an invalid provider key without asking the customer to rotate a working key.
docs/content/kb/guide/toolkits-pipedrive.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "Pipedrive"
3 -description: "Public support knowledge for Pipedrive."
4 -keywords: ["for-you","pipedrive","platform","auth-config","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/pipedrive-troubleshooting","claude-may-block-pipedrive-because-payment-processing-toolkits-are-res","do-not-install-the-pipedrive-app-directly-from-pipedrive-oauth-setting","hosted-auth-links-can-collect-pipedrive-required-fields","pass-callback-url-when-initiating-pipedrive-auth-to-redirect-users-aft","pipedrive-oauth-initiation-requires-the-workspace-subdomain","pipedrive-troubleshooting","use-custom-credentials-or-api-key-when-composio-s-default-pipedrive-oa"]
5 -sources: [{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Pipedrive requires custom OAuth or API-key credentials"},{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Pipedrive OAuth initiation requires the workspace subdomain"},{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Do not install the Pipedrive app directly from Pipedrive OAuth settings"},{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Hosted auth links can collect Pipedrive required fields"},{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Pass `callback_url` when initiating Pipedrive auth to redirect users after authentication"},{"sourcePath":"toolkits/pipedrive/public.md","sourceHeading":"Pipedrive has trigger support"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["pipedrive"]
11 -aliases: ["/kb/toolkits/pipedrive-troubleshooting","claude-may-block-pipedrive-because-payment-processing-toolkits-are-res","do-not-install-the-pipedrive-app-directly-from-pipedrive-oauth-setting","hosted-auth-links-can-collect-pipedrive-required-fields","pass-callback-url-when-initiating-pipedrive-auth-to-redirect-users-aft","pipedrive-oauth-initiation-requires-the-workspace-subdomain","pipedrive-troubleshooting","use-custom-credentials-or-api-key-when-composio-s-default-pipedrive-oa"]
12 ----
13 -Use this guide to configure Pipedrive authentication, initiate connections, and use Pipedrive triggers.
14 -
15 -## Configure Pipedrive authentication
16 -
17 -**Use custom OAuth or API-key credentials.** Composio-managed OAuth is not currently available for Pipedrive. Create a custom auth config with your Pipedrive OAuth app, or use API-key authentication when that better fits your security requirements.
18 -
19 -**Pass the workspace subdomain during OAuth initiation.** When initiating a Pipedrive OAuth connection, pass the Pipedrive workspace subdomain or domain expected by the auth config. For example, if the workspace is `your-workspace.pipedrive.com`, pass `your-workspace` rather than the full hostname.
20 -
21 -**Complete custom OAuth setup through Composio.** Enable the app in Composio and complete setup there with your developer app credentials. Do not try to install the custom app directly from Pipedrive's OAuth app settings. During the Composio connection flow, provide the Pipedrive subdomain when requested.
22 -
23 -**Let hosted auth links collect required fields.** Use hosted auth links when you want Composio to collect required provider-specific fields during connection initiation. You can also inspect the auth config or toolkit metadata to see the expected input fields before starting the connection.
24 -
25 -## Initiate Pipedrive connections and use triggers
26 -
27 -**Pass a callback URL when initiating auth.** When initiating a Pipedrive connection through SDK or API, pass `callback_url` or `callbackUrl` in the connection initiation call. Composio redirects the user to that URL after the provider authentication flow completes.
28 -
29 -**Check the current trigger catalog before relying on a count.** Pipedrive has trigger support. Verify the current trigger list in the toolkit catalog before naming an exact count.
docs/content/kb/guide/toolkits-posthog.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "PostHog"
3 -description: "Public support knowledge for PostHog."
4 -keywords: ["for-you","platform","posthog","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/posthog-troubleshooting","api-key-connections-may-show-active-without-live-credential-validation","configure-posthog-subdomain-for-eu-or-self-hosted-instances","create-a-posthog-integration-auth-config-before-expecting-it-in-auth-c","fetch-posthog-tool-schema-to-see-required-fields-for-a-tool-call","pass-auth-config-into-tool-router-sessions-platform-created-auth-confi","posthog-is-api-key-based-use-the-posthog-api-key-when-creating-the-con","posthog-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/posthog/public.md","sourceHeading":"PostHog is API-key based; use the PostHog API key when creating the connection"},{"sourcePath":"toolkits/posthog/public.md","sourceHeading":"Configure PostHog subdomain for EU or self-hosted instances"},{"sourcePath":"toolkits/posthog/public.md","sourceHeading":"Pass auth config into Tool Router sessions; platform-created auth configs are not automatically usable"},{"sourcePath":"toolkits/posthog/public.md","sourceHeading":"Create a PostHog integration/auth config before expecting it in auth_configs API results"},{"sourcePath":"toolkits/posthog/public.md","sourceHeading":"Fetch PostHog tool schema to see required fields for a tool call"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["posthog"]
11 -aliases: ["/kb/toolkits/posthog-troubleshooting","api-key-connections-may-show-active-without-live-credential-validation","configure-posthog-subdomain-for-eu-or-self-hosted-instances","create-a-posthog-integration-auth-config-before-expecting-it-in-auth-c","fetch-posthog-tool-schema-to-see-required-fields-for-a-tool-call","pass-auth-config-into-tool-router-sessions-platform-created-auth-confi","posthog-is-api-key-based-use-the-posthog-api-key-when-creating-the-con","posthog-troubleshooting"]
12 ----
13 -## PostHog is API-key based; use the PostHog API key when creating the connection
14 -
15 -PostHog is API-key based in Composio. Use the customer's PostHog API key when creating the connection. For connected-account creation, pass the key in the API-key auth state, for example with `generic_api_key` or the required field name returned by toolkit metadata.
16 -
17 -## Configure PostHog subdomain for EU or self-hosted instances
18 -
19 -For EU or self-hosted PostHog instances, configure the PostHog `subdomain` or instance value instead of assuming the default cloud host. Inspect the current auth-config and connection-initiation fields to confirm where the active toolkit accepts that value.
20 -
21 -## Pass auth config into Tool Router sessions; platform-created auth configs are not automatically usable
22 -
23 -When using PostHog through Tool Router MCP, include the auth config in the Tool Router session so the generated MCP URL has the correct auth config details. Auth configs or connected accounts created on the platform side are not automatically available inside every Tool Router session unless they are passed/associated correctly.
24 -
25 -## Create a PostHog integration/auth config before expecting it in auth_configs API results
26 -
27 -`/api/v3/auth_configs` lists the active auth configs/integrations already created in the project. If PostHog is missing or the response is empty, create a PostHog auth config/integration first, then connect the account to it.
28 -
29 -## Fetch PostHog tool schema to see required fields for a tool call
30 -
31 -If a PostHog tool call fails because of missing or mixed-up parameters, fetch the tool schema by slug, for example `/api/v3/tools/POSTHOG_CREATE_PROJECT_INSIGHTS_WITH_FORMAT_OPTION`, using the project API key. The schema response shows the required fields and expected shapes for that tool call.
docs/content/kb/guide/toolkits-quickbooks.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "QuickBooks"
3 -description: "Public support knowledge for QuickBooks."
4 -keywords: ["for-you","platform","quickbooks","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/quickbooks-disabled-for-this-session","/kb/toolkits/quickbooks-troubleshooting","connect-a-quickbooks-sandbox-company","connect-multiple-quickbooks-companies","missing-quickbooks-expense-bill-tools-should-be-filed-with-the-exact-i","quickbooks-disabled-for-this-session","quickbooks-hosted-auth-screen-can-be-skipped-by-sending-users-directly","quickbooks-oauth-fails-with-payments-scope","quickbooks-requests-resolve-to-company-none","quickbooks-tokens-are-refreshed-periodically-with-retries-before-expir","quickbooks-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"Use the sandbox QuickBooks API base URL for sandbox connections"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"QuickBooks auth configs need QuickBooks credentials and matching redirect URL"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"QuickBooks auth can accept custom auth and token URLs for sandbox/custom flows"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"QuickBooks payment scope requires payment module access"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"Realm ID mapping fixes may require the latest QuickBooks toolkit version"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"Multiple QuickBooks accounts can be selected in Claude/MCP by using separate user IDs or connected account IDs"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"QuickBooks tokens are refreshed periodically with retries before expiring the connection"},{"sourcePath":"toolkits/quickbooks/public.md","sourceHeading":"QuickBooks hosted auth screen can be skipped by sending users directly to the OAuth provider"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["quickbooks"]
11 -aliases: ["/kb/toolkits/quickbooks-disabled-for-this-session","/kb/toolkits/quickbooks-troubleshooting","connect-a-quickbooks-sandbox-company","connect-multiple-quickbooks-companies","missing-quickbooks-expense-bill-tools-should-be-filed-with-the-exact-i","quickbooks-disabled-for-this-session","quickbooks-hosted-auth-screen-can-be-skipped-by-sending-users-directly","quickbooks-oauth-fails-with-payments-scope","quickbooks-requests-resolve-to-company-none","quickbooks-tokens-are-refreshed-periodically-with-retries-before-expir","quickbooks-troubleshooting"]
12 ----
13 -Use this guide to configure QuickBooks OAuth for the correct environment, maintain connections, and target the intended company account.
14 -
15 -## Configure QuickBooks OAuth for the environment
16 -
17 -**Use the sandbox API base URL for sandbox accounts.** For QuickBooks sandbox accounts, pass `https://sandbox-quickbooks.api.intuit.com` as the URL/base URL when initiating the connection. Production connections should use the production Intuit API base URL.
18 -
19 -**Match Intuit credentials and the Composio redirect URL.** When creating a QuickBooks auth config, enter the QuickBooks OAuth credentials from the Intuit developer app and configure the Composio redirect URL in the QuickBooks auth app. A mismatch or missing redirect URL can break the OAuth flow.
20 -
21 -**Use current toolkit support for custom auth and token URLs.** QuickBooks toolkit support accepts auth and token URLs during connection initiation. If you need sandbox or custom Intuit OAuth endpoints, use a toolkit version that supports passing those URLs.
22 -
23 -**Request the payment scope only when payment access is enabled.** If the QuickBooks OAuth flow includes the payments scope `com.intuit.quickbooks.payment`, the QuickBooks payment module must be enabled for that account/app. If the customer does not need payment tools, remove that scope and retry the connection.
24 -
25 -## Maintain the QuickBooks connection and auth experience
26 -
27 -**Let Composio refresh tokens and retry transient failures.** QuickBooks OAuth refresh is handled by Composio through the provider's token endpoint. The current refresh path retries transient failures and uses credential-expiry timing rather than promising a fixed 15-minute schedule. If the provider conclusively rejects the grant or failures persist past the platform's retry budget, the connected account expires and the user must reauthenticate through a new auth link.
28 -
29 -**Send users directly to Intuit when the hosted auth screen should be skipped.** The Composio auth screen can be skipped for QuickBooks by sending users directly to the OAuth provider, following Composio's white-labeling/direct-provider auth flow. Use this when the customer wants the user to see the provider consent screen without the intermediate Composio auth screen.
30 -
31 -## Target the correct QuickBooks account and toolkit version
32 -
33 -**Retry realm or company mapping issues on the latest toolkit version.** For QuickBooks realm/company mapping issues, retry on the latest toolkit version rather than a historical pinned version.
34 -
35 -**Use distinct account identifiers for multiple QuickBooks accounts.** Create separate connected accounts for each QuickBooks account, preferably with distinct `user_id` values. In Claude/MCP setup, append the desired `connected_account_id` or `user_id` to the MCP URL/configuration so the session targets the intended QuickBooks connection.
docs/content/kb/guide/toolkits-reddit.mdx deleted
-30
@@ -1,30 +0,0 @@
1 ----
2 -title: "Reddit"
3 -description: "Public support knowledge for Reddit."
4 -keywords: ["for-you","platform","reddit","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/reddit-troubleshooting","connect-reddit-with-your-own-oauth-credentials","reddit-create-post-requires-flair-id","reddit-troubleshooting","use-connect-mcp-for-reddit-oauth-callback-failures-in-claude-code"]
5 -sources: [{"sourcePath":"toolkits/reddit/public.md","sourceHeading":"Use Connect MCP for Reddit OAuth callback failures in Claude Code"},{"sourcePath":"toolkits/reddit/public.md","sourceHeading":"Reddit supports managed and customer-owned OAuth 2.0"},{"sourcePath":"toolkits/reddit/public.md","sourceHeading":"Reddit toolkit behavior can change when Reddit changes its API or enforcement policies"},{"sourcePath":"toolkits/reddit/public.md","sourceHeading":"Older Reddit Create Post tool versions may require `flair_id`"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["reddit"]
11 -aliases: ["/kb/toolkits/reddit-troubleshooting","connect-reddit-with-your-own-oauth-credentials","reddit-create-post-requires-flair-id","reddit-troubleshooting","use-connect-mcp-for-reddit-oauth-callback-failures-in-claude-code"]
12 ----
13 -## Use Connect MCP for Reddit OAuth callback failures in Claude Code
14 -
15 -For Claude Code Reddit MCP OAuth callback failures on the legacy MCP path, switch the MCP server URL to `https://connect.composio.dev/mcp`. Remove the old `x-api-key` header and configure the current `x-consumer-api-key` header from the AI Clients setup. Connect MCP can then start the Reddit authorization flow from the client.
16 -
17 -## Reddit supports managed and customer-owned OAuth 2.0
18 -
19 -Use Composio-managed OAuth for the standard connection flow. Create a custom
20 -auth config with the customer's Reddit client ID and client secret when they
21 -need control over provider app settings and credentials. Make sure Reddit has
22 -approved a custom app for its intended access before using it in production.
23 -
24 -## Reddit toolkit behavior can change when Reddit changes its API or enforcement policies
25 -
26 -The Reddit toolkit depends on Reddit's underlying APIs and policy enforcement. Changes or restrictions from Reddit can affect toolkit behavior, and Reddit does not guarantee stable API behavior for all use cases. For production usage, use your own Reddit credentials to maximize control, and account for Reddit's spam and responsible builder policies when designing automations.
27 -
28 -## Older Reddit Create Post tool versions may require `flair_id`
29 -
30 -If Reddit Create Post fails on version `00000000_00`, check whether the request is missing `flair_id`; that old version requires it. Prefer pinning a specific current toolkit/tool version to avoid breaking changes. In recent Reddit tool versions, `flair_id` is no longer required for the Create Post call.
docs/content/kb/guide/toolkits-salesforce.mdx deleted
-61
@@ -1,61 +0,0 @@
1 ----
2 -title: "Salesforce"
3 -description: "Public support knowledge for Salesforce."
4 -keywords: ["for-you","platform","salesforce","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/salesforce-troubleshooting","migrate-deprecated-salesforce-retrieve-tools-to-the-newer-get-list-too","retrieve-a-specific-salesforce-contact-by-first-listing-contacts-and-t","salesforce-action-to-scope-mapping-is-not-granular-include-refresh-tok","salesforce-allows-only-five-active-refresh-tokens-per-user-per-app","salesforce-connection-initiation-needs-instance-endpoint-and-my-domain","salesforce-requires-customer-owned-developer-credentials","salesforce-subdomain-defaults-to-login-use-the-my-domain-api-prefix-wh","salesforce-troubleshooting","the-salesforce-custom-auth-redirect-url-is-composio-s-toolkit-auth-cal","url-not-reset-usually-means-salesforce-subdomain-was-not-configured-an","use-hosted-auth-for-salesforce-required-fields-or-direct-initiate-when","use-proxy-execute-for-salesforce-frontdoor-ui-bridge-flows-instead-of","use-salesforce-get-all-fields-for-object-to-inspect-a-salesforce-objec"]
5 -sources: [{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Use customer-owned Salesforce credentials when you need app-level control"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Salesforce connection initiation needs instance endpoint and My Domain subdomain fields"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Salesforce subdomain defaults to `login`; use the My Domain/API prefix when needed"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"`URL_NOT_RESET` usually means Salesforce subdomain was not configured and defaulted to `login`"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Use hosted auth for Salesforce required fields, or direct `.initiate()` when you want to prefill them yourself"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Use `SALESFORCE_GET_ALL_FIELDS_FOR_OBJECT` to inspect a Salesforce object's fields"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Salesforce org admins may need to install/approve the connected app before users can authenticate"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Salesforce allows only five active refresh tokens per user per app"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Use Proxy Execute for Salesforce Frontdoor/UI bridge flows instead of reading tokens from connected accounts"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Migrate deprecated Salesforce retrieve tools to the current get/list tools"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"Retrieve a specific Salesforce contact by listing contacts and then fetching by ID"},{"sourcePath":"toolkits/salesforce/public.md","sourceHeading":"The Salesforce custom auth redirect URL is Composio's toolkit auth callback endpoint"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["salesforce"]
11 -aliases: ["/kb/toolkits/salesforce-troubleshooting","migrate-deprecated-salesforce-retrieve-tools-to-the-newer-get-list-too","retrieve-a-specific-salesforce-contact-by-first-listing-contacts-and-t","salesforce-action-to-scope-mapping-is-not-granular-include-refresh-tok","salesforce-allows-only-five-active-refresh-tokens-per-user-per-app","salesforce-connection-initiation-needs-instance-endpoint-and-my-domain","salesforce-requires-customer-owned-developer-credentials","salesforce-subdomain-defaults-to-login-use-the-my-domain-api-prefix-wh","salesforce-troubleshooting","the-salesforce-custom-auth-redirect-url-is-composio-s-toolkit-auth-cal","url-not-reset-usually-means-salesforce-subdomain-was-not-configured-an","use-hosted-auth-for-salesforce-required-fields-or-direct-initiate-when","use-proxy-execute-for-salesforce-frontdoor-ui-bridge-flows-instead-of","use-salesforce-get-all-fields-for-object-to-inspect-a-salesforce-objec"]
12 ----
13 -Use this guide to configure Salesforce OAuth and domains, troubleshoot connected-app access, choose current tools, and build UI bridge flows safely.
14 -
15 -## Configure Salesforce OAuth and connection flows
16 -
17 -**Use customer-owned credentials for app-level control.** The current Salesforce toolkit supports OAuth2 and server-to-server OAuth2 with
18 -customer-owned credentials. Configure the Salesforce connected app according to
19 -Salesforce's OAuth guidance and use its credentials in a custom Composio auth
20 -config. This gives the customer control over scopes, branding, and provider-side
21 -policy.
22 -
23 -**Choose hosted auth or direct initiation based on who supplies required fields.** The Salesforce field collection interface is part of Hosted Authentication / the connection link flow. If you want Composio to collect required fields, use hosted auth. If your app already knows the Salesforce instance/subdomain values, skip that interface and call `.initiate()` directly with the required fields. Use `.refresh()` to regenerate the auth URL for an already initiated connection; `.link()` starts a new connection. If you truly need multiple connections for the same `user_id`, pass `allow_multiple=True` to `.initiate()`.
24 -
25 -**Match the redirect URI to the current Composio callback.** Use the callback URL shown by the current Composio auth-config flow as the authorized redirect URI for custom Salesforce OAuth. This provider callback is separate from the post-auth customer redirect passed as `callback_url` / `callbackUrl` during connection initiation.
26 -
27 -## Set the Salesforce domain and connection fields
28 -
29 -**Provide the instance endpoint and My Domain subdomain.** Salesforce accepts additional connection initiation fields. Fetch the toolkit by slug (`/api/v3.1/toolkits/salesforce`) to inspect the expected fields, and fetch the connected account to see the same fields after connection. The important Salesforce fields are `My Domain Subdomain` and `Instance endpoint`. If you are initiating directly through the SDK/API, pass these fields through `.initiate()` rather than waiting for the hosted connection UI.
30 -
31 -**Use the My Domain or API prefix when `login` is not enough.** For Salesforce, the default subdomain value is `login`, and that works in most cases. If the default or a simple org label fails, Composio needs the Salesforce login/API domain prefix rather than the full browser URL.
32 -
33 -Use these formats:
34 -
35 -- Default case: keep `login`.
36 -
37 -- Standard My Domain URL: for `https://your-company.my.salesforce.com/...`, pass `your-company.my`.
38 -
39 -- Developer Edition / Lightning URL: for `https://<org>.develop.lightning.force.com/...`, the matching OAuth/My Domain host is usually `https://<org>.develop.my.salesforce.com/...`, so pass `<org>.develop.my`.
40 -
41 -If the customer enters only `<org>`, Composio may generate `<org>.salesforce.com`, which can fail before OAuth with a browser DNS error such as `DNS_PROBE_FINISHED_NXDOMAIN`.
42 -
43 -**Recheck the domain when Salesforce returns `URL_NOT_RESET`.** `URL_NOT_RESET` can happen when the Salesforce org requires a specific My Domain value but the connection is using the generic `login` default or an incomplete subdomain. The default `login` value is fine for most Salesforce flows, but for org-specific failures recheck the Salesforce domain/subdomain values on the connection, pass the correct My Domain subdomain, and retry on the latest toolkit version if the issue was seen on an older pinned version.
44 -
45 -## Troubleshoot connected-app access and token policies
46 -
47 -**Ask an org admin to install or approve restricted connected apps.** Salesforce connected app usage restrictions can require an org admin to install or approve the connected app before org users can authenticate. Check whether the error URL includes `error=invalid_client&error_description=app+must+be+installed+into+org`. In Salesforce Setup, go to OAuth Connected App Usage and look for the app with an Install button in the Actions column. After the admin installs/enables the app, users should retry authentication.
48 -
49 -**Account for Salesforce's five active refresh-token limit.** 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.
50 -
51 -## Discover and use current Salesforce tools
52 -
53 -**Inspect object schemas before querying or updating them.** Use `SALESFORCE_GET_ALL_FIELDS_FOR_OBJECT` when you need to inspect the fields available on a Salesforce object. This is the right tool for schema discovery before building object-specific queries or update flows.
54 -
55 -**Replace deprecated retrieve actions with current get and list tools.** Use the current Salesforce tool slugs instead of the deprecated retrieve variants: `SALESFORCE_RETRIEVE_LEAD_BY_ID` -> `SALESFORCE_GET_LEAD`, `SALESFORCE_RETRIEVE_SPECIFIC_CONTACT_BY_ID` -> `SALESFORCE_GET_CONTACT_BY_ID`, and `SALESFORCE_RETRIEVE_OPPORTUNITIES_DATA` -> `SALESFORCE_LIST_OPPORTUNITIES`.
56 -
57 -**List contacts before fetching a specific contact by ID.** Use `SALESFORCE_LIST_CONTACTS` to list contacts and capture the IDs with their names. Then call `SALESFORCE_GET_CONTACT_BY_ID` with the desired contact ID to fetch the specific contact details.
58 -
59 -## Use Proxy Execute for Salesforce UI bridge flows
60 -
61 -Do not build Salesforce Frontdoor/UI bridge flows by reading access tokens from the connected account API. Use Proxy Execute with the Salesforce connected account instead. Composio injects the OAuth access token server-side into the proxied Salesforce request, such as a call to `/services/oauth2/singleaccess`, and Salesforce returns the frontdoor URI that the application can redirect the user's browser to.
docs/content/kb/guide/toolkits-serpapi.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "SerpApi"
3 -description: "Public support knowledge for SerpApi."
4 -keywords: ["for-you","platform","serpapi","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/serpapi-troubleshooting","avoid-serpapi-ebay-search-when-its-schema-causes-field-errors","disable-serpapi-by-listing-premium-toolkit-slugs-in-session-config","search-and-scraping-use-cases-can-use-serpapi-alongside-firecrawl-exa","serpapi-api-key-validation-was-not-available-in-the-connection-flow","serpapi-troubleshooting","use-toolkit-details-to-inspect-serpapi-required-auth-fields"]
5 -sources: [{"sourcePath":"toolkits/serpapi/public.md","sourceHeading":"Control SerpAPI availability in a Session"},{"sourcePath":"toolkits/serpapi/public.md","sourceHeading":"Use toolkit details to inspect SerpAPI required auth fields"},{"sourcePath":"toolkits/serpapi/public.md","sourceHeading":"Search and scraping use cases can use SerpAPI alongside Firecrawl, Exa, Tavily, or Composio Search"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["serpapi"]
11 -aliases: ["/kb/toolkits/serpapi-troubleshooting","avoid-serpapi-ebay-search-when-its-schema-causes-field-errors","disable-serpapi-by-listing-premium-toolkit-slugs-in-session-config","search-and-scraping-use-cases-can-use-serpapi-alongside-firecrawl-exa","serpapi-api-key-validation-was-not-available-in-the-connection-flow","serpapi-troubleshooting","use-toolkit-details-to-inspect-serpapi-required-auth-fields"]
12 ----
13 -## Control SerpAPI availability in a Session
14 -
15 -To exclude SerpAPI from a Session, disable `serpapi` in the top-level [toolkit configuration](/docs/configuring-sessions). To control only access through Composio accounts while keeping connected-account routes available, use the [Instant usage controls](/docs/instant-tools#control-instant-usage). Instant eligibility is per tool.
16 -
17 -## Use toolkit details to inspect SerpAPI required auth fields
18 -
19 -Use `.toolkits.get("serpapi")` to fetch the toolkit details, including required and optional auth fields. For SerpAPI, the connection initiation payload should include a required `generic_api_key` field displayed as `API Key`.
20 -
21 -## Search and scraping use cases can use SerpAPI alongside Firecrawl, Exa, Tavily, or Composio Search
22 -
23 -For search and scraping use cases, Composio has multiple relevant toolkits: SerpAPI, Firecrawl, Exa, Tavily, and Composio Search. Composio Search provides search providers such as Exa and Tavily without separate auth.
docs/content/kb/guide/toolkits-servicenow.mdx deleted
-29
@@ -1,29 +0,0 @@
1 ----
2 -title: "ServiceNow authentication"
3 -description: "Current instance-specific authentication setup for ServiceNow."
4 -keywords: ["for-you","platform","servicenow","auth-config","authentication","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/servicenow/public.md","sourceHeading":"ServiceNow credentials and instance subdomain are collected at different stages"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","toolkits-and-providers"]
10 -toolkitSlugs: ["servicenow"]
11 -aliases: []
12 ----
13 -## ServiceNow credentials and instance subdomain are collected at different stages
14 -
15 -The current `servicenow` toolkit supports Basic, OAuth2, and S2S OAuth2. OAuth
16 -auth-config creation accepts the ServiceNow application's client ID and client
17 -secret. Connection initiation then requires the instance subdomain, such as
18 -`mycompany` for `mycompany.service-now.com`.
19 -
20 -ServiceNow registers an inbound OAuth client inside a ServiceNow instance. A
21 -client registered in one customer instance does not automatically authorize an
22 -unrelated instance. Use a separate customer-owned auth config when different
23 -customers supply different ServiceNow application registrations.
24 -
25 -Use delegated OAuth2 when a user should sign in and consent. Use S2S OAuth2 for
26 -a backend integration whose identity and permissions are configured by the
27 -ServiceNow administrator. Fetch the current toolkit metadata before building a
28 -form because the required fields are separated into
29 -`auth_config_creation` and `connected_account_initiation`.
docs/content/kb/guide/toolkits-sharepoint.mdx deleted
-240
@@ -1,240 +0,0 @@
1 ----
2 -title: "SharePoint"
3 -description: "Public support knowledge for SharePoint."
4 -keywords: ["for-you","platform","sharepoint","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati","/kb/toolkits/sharepoint-troubleshooting","after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati","create-folder-odata-type-name-error","disable-destructive-sharepoint-tools-with-destructivehint-or-explicit","set-the-sharepoint-tenant-on-the-connection","share-point-upload-from-url-needs-a-server-fetchable-url","sharepoint-rest-and-graph-need-separate-connections","sharepoint-rest-app-only-client-credentials-use-certificate-auth","sharepoint-teams-site-returns-404","sharepoint-troubleshooting","the-sharepoint-subsite-field-is-not-a-permission-boundary","use-share-point-search-query-for-kql-fql-sharepoint-search"]
5 -sources: [{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"SharePoint REST APIs and SharePoint Graph are separate API families"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"`/teams/` SharePoint sites require the server-relative Subsite path"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"SharePoint REST app-only client credentials use certificate auth"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"SharePoint `.default` scope uses the tenant domain placeholder"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"Pass the SharePoint tenant/subdomain during connection initiation"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"The SharePoint subsite field is not a permission boundary"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"Retrieve SharePoint site name from connected account state"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"Use `SHARE_POINT_SEARCH_QUERY` for KQL/FQL SharePoint search"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"SharePoint toolkit slug is `share_point`"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"Disable destructive SharePoint tools with `destructiveHint` or explicit tool filters"},{"sourcePath":"toolkits/sharepoint/public.md","sourceHeading":"`SHARE_POINT_UPLOAD_FROM_URL` needs a server-fetchable URL"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["share_point"]
11 -aliases: ["/kb/toolkits/after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati","/kb/toolkits/sharepoint-troubleshooting","after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati","create-folder-odata-type-name-error","disable-destructive-sharepoint-tools-with-destructivehint-or-explicit","set-the-sharepoint-tenant-on-the-connection","share-point-upload-from-url-needs-a-server-fetchable-url","sharepoint-rest-and-graph-need-separate-connections","sharepoint-rest-app-only-client-credentials-use-certificate-auth","sharepoint-teams-site-returns-404","sharepoint-troubleshooting","the-sharepoint-subsite-field-is-not-a-permission-boundary","use-share-point-search-query-for-kql-fql-sharepoint-search"]
12 ----
13 -## Use a tenant-specific Microsoft endpoint for SharePoint Graph
14 -
15 -Set `issuer` to your Microsoft Entra tenant ID to authenticate SharePoint Graph
16 -through that tenant's endpoint instead of `/common`. Use the directory (tenant)
17 -ID, not your SharePoint site name. Microsoft's [tenant authority
18 -reference](https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc#find-your-apps-openid-configuration-document-uri)
19 -explains how tenant-specific sign-in differs from `common`.
20 -
21 -First, retrieve the toolkit's authentication fields with your Composio project
22 -API key:
23 -
24 -### Inspect the toolkit metadata
25 -
26 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
27 -
28 -<Tab value="Python">
29 -```python
30 -from composio import Composio
31 -
32 -composio = Composio()
33 -print(composio.toolkits.get("sharepoint_graph"))
34 -```
35 -</Tab>
36 -
37 -<Tab value="TypeScript">
38 -```typescript
39 -import { Composio } from "@composio/core";
40 -
41 -const composio = new Composio();
42 -console.log(await composio.toolkits.get("sharepoint_graph"));
43 -```
44 -</Tab>
45 -
46 -<Tab value="API">
47 -```bash
48 -curl --fail-with-body \
49 - 'https://backend.composio.dev/api/v3.1/toolkits/sharepoint_graph' \
50 - -H "x-api-key: $COMPOSIO_API_KEY"
51 -```
52 -</Tab>
53 -
54 -</Tabs>
55 -
56 -
57 -
58 -Find the `OAUTH2` auth scheme and inspect `fields.auth_config_creation` and
59 -`fields.connected_account_initiation`. The `issuer` field appears under
60 -`connected_account_initiation`.
61 -
62 -To apply the same tenant ID to new connections, [update your custom auth
63 -config](/reference/api-reference/auth-configs/patchAuthConfigsByNanoid) with
64 -`shared_credentials.issuer`:
65 -
66 -### Update the auth config
67 -
68 -<Tabs groupId="language" items={["Python","TypeScript","API"]} persist>
69 -
70 -<Tab value="Python">
71 -The high-level Python update helper does not forward `shared_credentials`; use its public generated client.
72 -
73 -```python
74 -from composio import Composio
75 -
76 -composio = Composio()
77 -result = composio.client.auth_configs.update(
78 - "<AUTH_CONFIG_ID>",
79 - type="custom",
80 - shared_credentials={"issuer": "<MICROSOFT_TENANT_ID>"},
81 -)
82 -print(result)
83 -```
84 -</Tab>
85 -
86 -<Tab value="TypeScript">
87 -```typescript
88 -import { Composio } from "@composio/core";
89 -
90 -const composio = new Composio();
91 -const result = await composio.getClient().authConfigs.update("<AUTH_CONFIG_ID>", {
92 - type: "custom",
93 - shared_credentials: { issuer: "<MICROSOFT_TENANT_ID>" },
94 -});
95 -console.log(result);
96 -```
97 -</Tab>
98 -
99 -<Tab value="API">
100 -```bash
101 -curl --fail-with-body -X PATCH \
102 - 'https://backend.composio.dev/api/v3.1/auth_configs/<AUTH_CONFIG_ID>' \
103 - -H "x-api-key: $COMPOSIO_API_KEY" \
104 - -H 'content-type: application/json' \
105 - -d '{
106 - "type": "custom",
107 - "shared_credentials": {
108 - "issuer": "<MICROSOFT_TENANT_ID>"
109 - }
110 - }'
111 -```
112 -</Tab>
113 -
114 -</Tabs>
115 -
116 -
117 -
118 -Replace `<AUTH_CONFIG_ID>` with your SharePoint Graph custom auth config ID.
119 -Every new connection created through this auth config inherits the tenant ID.
120 -Create a new connection using that config and complete Microsoft sign-in to use
121 -the tenant-specific endpoint. This recipe configures new connections; it does
122 -not migrate existing connected accounts.
123 -
124 -## SharePoint REST APIs and SharePoint Graph are separate API families
125 -
126 -Treat the current SharePoint toolkit and the SharePoint Graph toolkit as separate API families, not as interchangeable variants of the same connection.
127 -
128 -- The current SharePoint toolkit uses SharePoint REST/OData endpoints on the tenant SharePoint host, usually shaped like `https://<tenant>.sharepoint.com/_api/...`.
129 -
130 -- The SharePoint Graph toolkit uses Microsoft Graph endpoints, usually shaped like `https://graph.microsoft.com/v1.0/sites/...`.
131 -
132 -- The scopes and token audience must match the endpoint family. SharePoint REST expects a SharePoint resource token such as `https://<tenant>.sharepoint.com/.default`; SharePoint Graph expects Microsoft Graph permissions/scopes such as `Sites.*`, `Files.*`, `User.Read`, or `https://graph.microsoft.com/.default` for S2S.
133 -
134 -- Do not add Microsoft Graph scopes such as `Sites.Read.All` or `User.Read.All` to the current SharePoint REST auth config as a workaround. Those scopes produce a Graph-audience token and can cause 401 responses when the toolkit calls SharePoint REST.
135 -
136 -- Do not reuse an existing SharePoint REST connected account/token for SharePoint Graph. A Graph-scoped token is not valid for SharePoint REST, and a SharePoint-audience token is not valid for Graph.
137 -
138 -- The same Microsoft Entra app registration may be reused only if it has the right API permissions and redirect/client-credential setup for the target toolkit, but create or use a separate Composio auth config and reconnect.
139 -
140 -SharePoint REST is not deprecated just because SharePoint Add-Ins / Azure ACS are retiring. Microsoft still documents SharePoint REST/CSOM as valid when Graph does not cover the needed functionality. Graph is the unified Microsoft 365 API and is usually better for cross-service or client-secret S2S flows, but it does not have perfect parity with SharePoint REST.
141 -
142 -Example response:
143 -
144 -```text
145 -The SharePoint and SharePoint Graph toolkits use different Microsoft API surfaces.
146 -
147 -The existing SharePoint toolkit uses SharePoint REST/OData endpoints such as `https://<tenant>.sharepoint.com/_api/...` and needs a SharePoint-resource scope like `https://<tenant>.sharepoint.com/.default`.
148 -
149 -The SharePoint Graph toolkit uses Microsoft Graph endpoints such as `https://graph.microsoft.com/v1.0/sites/...` and needs Graph permissions such as `Sites.*`, `Files.*`, `User.Read`, or for S2S `https://graph.microsoft.com/.default`.
150 -
151 -Because the tokens are issued for different resources, please create/use a separate Composio auth config for SharePoint Graph and reconnect. You may be able to reuse the same Microsoft Entra app registration if it has the required Graph permissions configured, but the existing SharePoint connected account token should not be used for SharePoint Graph.
152 -```
153 -
154 -## `/teams/` SharePoint sites require the server-relative Subsite path
155 -
156 -If your SharePoint site URL is under `/teams/<site>` instead of `/sites/<site>`, do not pass only `<site>` in the SharePoint Subsite field. A bare subsite value is interpreted as `/sites/<site>` by the toolkit.
157 -
158 -Reconnect the SharePoint account and set SharePoint Subsite to the full server-relative path, for example `/teams/<site>`. For per-call overrides, pass `site_name: "/teams/<site>"`.
159 -
160 -Debugging signal: tool logs show SharePoint calls like `https://tenant.sharepoint.com/sites/<site>/_api/...` returning `404 FILE NOT FOUND`, while the customer's actual SharePoint URL is `https://tenant.sharepoint.com/teams/<site>`. If the connected account is `ACTIVE` and the auth config is enabled, treat this as a path-prefix mismatch first, not an OAuth issue.
161 -
162 -Example response:
163 -
164 -```text
165 -This looks like a SharePoint site-path mismatch. Your site is under `/teams/...`, but the current connection/tool call is hitting `/sites/...`, which SharePoint returns as 404.
166 -
167 -Please reconnect the SharePoint account and set the Subsite value to the full server-relative path: `/teams/<site-name>`. If you're passing it per tool call, use `site_name: "/teams/<site-name>"`. A bare value like `<site-name>` gets treated as `/sites/<site-name>`.
168 -```
169 -
170 -## SharePoint REST app-only client credentials use certificate auth
171 -
172 -For the current Composio `share_point` toolkit, client credentials and certificate-based authentication are the same app-only path: client credentials is implemented with certificate-based authentication.
173 -
174 -The required setup is:
175 -
176 -- SharePoint tenant name, used for `https://<tenant>.sharepoint.com/_api` and the resource scope `https://<tenant>.sharepoint.com/.default`
177 -
178 -- Microsoft Entra tenant ID
179 -
180 -- Application/client ID
181 -
182 -- RSA private key in PEM format for the certificate uploaded to the Entra app registration
183 -
184 -- Certificate thumbprint (`x5t#S256`)
185 -
186 -- Admin-consented SharePoint application permissions appropriate for the use case
187 -
188 -Composio signs a JWT client assertion with the certificate/private key and requests a token from `https://login.microsoftonline.com/<tenantId>/oauth2/v2.0/token` using `grant_type=client_credentials` and the SharePoint `.default` scope. Customers should provide the fields above; they do not need to manually construct or pass a JWT assertion.
189 -
190 -Scope wording: the token request uses `https://<tenant>.sharepoint.com/.default`. In Microsoft client credentials, `.default` means the token is issued for the application permissions/app roles already configured and admin-consented for that SharePoint resource. Composio's action-to-scope mapping API should not be recommended for this SharePoint S2S/certificate path today; it is useful for OAuth2 scope discovery, not as the S2S permission source of truth.
191 -
192 -Do not offer a client-secret-only client-credentials setup for the SharePoint REST toolkit. That belongs to Microsoft Graph app-only flows and Composio's `sharepoint_graph` toolkit, which uses `https://graph.microsoft.com/.default` and accepts client ID + client secret. The legacy SharePoint Azure ACS app-only client ID/secret model existed but is retired and should not be recommended for new/current SharePoint REST integrations.
193 -
194 -Example setup outline:
195 -
196 -1. Generate a private key and self-signed/public certificate, for example with OpenSSL.
197 -
198 -2. Upload the public certificate to the Microsoft Entra app registration under Certificates & secrets > Certificates.
199 -
200 -3. Add/admin-consent SharePoint application permissions, such as the least-privileged site/list/file permission set appropriate for the customer.
201 -
202 -4. Create/connect the Composio SharePoint S2S auth config with the SharePoint tenant name, Entra tenant ID, client ID, private key PEM, and certificate thumbprint. Composio handles the JWT client assertion and token exchange.
203 -
204 -5. Ensure the Entra app has/admin-consented the SharePoint application permissions needed for the intended SharePoint REST operations. The requested token scope is `https://<tenant>.sharepoint.com/.default`; if using Selected permissions such as `Sites.Selected`, also grant explicit access to the target site/list/file.
205 -
206 -6. Test with a simple SharePoint REST call such as `GET https://<tenant>.sharepoint.com/_api/web?$select=Title` using the connected account.
207 -
208 -## SharePoint `.default` scope uses the tenant domain placeholder
209 -
210 -For a custom Microsoft Entra app, replace `{{site_name}}` in `https://{{site_name}}.sharepoint.com/.default` with the customer's SharePoint tenant/domain name. The resulting `.default` scope requests the application permissions already configured and admin-consented for that SharePoint resource.
211 -
212 -## Pass the SharePoint tenant/subdomain during connection initiation
213 -
214 -The SharePoint tenant/subdomain is an explicit connection field; Composio does not derive it automatically from the OAuth token. If a connection points at `default.sharepoint.com` or the wrong tenant, reinitiate the connection and provide the correct tenant name.
215 -
216 -## The SharePoint subsite field is not a permission boundary
217 -
218 -The SharePoint Subsite field supplies a default target when a tool call omits `site_name`. It does not restrict the Microsoft token, which retains the access granted to the consenting user or application.
219 -
220 -## Retrieve SharePoint site name from connected account state
221 -
222 -Fetch the connected account and inspect its stored state to confirm the SharePoint site name. Newer SDK responses expose it under a shape such as `state.val.site_name`; older toolset responses may expose `data.site_name`.
223 -
224 -## Use `SHARE_POINT_SEARCH_QUERY` for KQL/FQL SharePoint search
225 -
226 -Use `SHARE_POINT_SEARCH_QUERY` when a workflow needs flexible SharePoint search with KQL or FQL. For broader agentic discovery across SharePoint actions, Tool Router can discover and execute the relevant tools dynamically.
227 -
228 -## SharePoint toolkit slug is `share_point`
229 -
230 -The SharePoint toolkit slug is `share_point`, while its tool slugs use the `SHARE_POINT_...` prefix. Related Microsoft toolkit slugs include `outlook`, `one_drive`, and `sharepoint_graph`.
231 -
232 -## Disable destructive SharePoint tools with `destructiveHint` or explicit tool filters
233 -
234 -At session creation, disable tools carrying `destructiveHint` globally or for selected toolkits such as SharePoint and OneDrive. For finer control, explicitly allow or deny destructive tools by name.
235 -
236 -## `SHARE_POINT_UPLOAD_FROM_URL` needs a server-fetchable URL
237 -
238 -This action first downloads `file_url` from Composio's backend and then uploads the bytes to SharePoint. The source must be a reachable HTTP(S) download URL; raw base64 content is not a URL.
239 -
240 -For base64 or in-memory bytes, use `SHARE_POINT_UPLOAD_FILE` with the file content and name, or first create a temporary URL that the backend can reach. A 401/403 while downloading the source should be debugged as source-URL access, not as a destination folder problem. `conflict_behavior="rename"` only affects the target name after download succeeds.
docs/content/kb/guide/toolkits-shopify.mdx deleted
-43
@@ -1,43 +0,0 @@
1 ----
2 -title: "Shopify"
3 -description: "Public support knowledge for Shopify."
4 -keywords: ["for-you","platform","shopify","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/shopify-troubleshooting","choose-current-shopify-app-auth-flow","custom-shopify-credentials-keep-the-same-hosted-auth-ux-and-composio-s","custom-shopify-tools-can-call-graphql-with-composio-injected-auth","dashboard-claude-shopify-flow-does-not-currently-support-multiple-conn","fetch-more-than-the-default-20-shopify-tools-and-enable-the-tool-in-mc","for-you-shopify-oauth-scopes-cannot-currently-be-customized","if-shopify-mcp-auth-completes-but-tools-fail-append-the-configured-use","shopify-managed-default-oauth-is-not-available-use-your-own-shopify-oa","shopify-oauth-400s-are-commonly-caused-by-bad-client-secrets-or-unveri","shopify-order-update-403s-can-be-caused-by-missing-read-all-orders-sco","shopify-subdomain-should-be-only-the-store-name-not-the-full-myshopify","shopify-troubleshooting","use-composio-s-toolkit-auth-callback-as-the-shopify-oauth-redirect-url","use-shopify-get-order-list-to-confirm-orders-and-retrieve-order-ids","use-shopify-graph-ql-query-for-shopify-graphql-queries"]
5 -sources: [{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Shopify API-key/admin-token auth is deprecated; use OAuth2 or S2S auth instead"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Use Composio's toolkit auth callback as the Shopify OAuth redirect URL"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Custom Shopify credentials keep the same hosted auth UX and Composio still manages refresh"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Shopify OAuth 400s are commonly caused by incorrect client secrets or unverified gated scopes"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Shopify subdomain should be only the store name, not the full `.myshopify.com` host"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Use `SHOPIFY_GRAPH_QL_QUERY` for Shopify GraphQL queries"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Fetch more than the default 20 Shopify tools and enable the tool in MCP config"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Use `SHOPIFY_GET_ORDERS_WITH_FILTERS` to confirm orders and retrieve order IDs"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Shopify order update 403s can be caused by missing `read_all_orders` scope"},{"sourcePath":"toolkits/shopify/public.md","sourceHeading":"Custom Shopify tools can call GraphQL with Composio-injected auth"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["shopify"]
11 -aliases: ["/kb/authentication/shopify-troubleshooting","choose-current-shopify-app-auth-flow","custom-shopify-credentials-keep-the-same-hosted-auth-ux-and-composio-s","custom-shopify-tools-can-call-graphql-with-composio-injected-auth","dashboard-claude-shopify-flow-does-not-currently-support-multiple-conn","fetch-more-than-the-default-20-shopify-tools-and-enable-the-tool-in-mc","for-you-shopify-oauth-scopes-cannot-currently-be-customized","if-shopify-mcp-auth-completes-but-tools-fail-append-the-configured-use","shopify-managed-default-oauth-is-not-available-use-your-own-shopify-oa","shopify-oauth-400s-are-commonly-caused-by-bad-client-secrets-or-unveri","shopify-order-update-403s-can-be-caused-by-missing-read-all-orders-sco","shopify-subdomain-should-be-only-the-store-name-not-the-full-myshopify","shopify-troubleshooting","use-composio-s-toolkit-auth-callback-as-the-shopify-oauth-redirect-url","use-shopify-get-order-list-to-confirm-orders-and-retrieve-order-ids","use-shopify-graph-ql-query-for-shopify-graphql-queries"]
12 ----
13 -Use this guide to configure Shopify authentication, discover the complete tool set, and work with Shopify orders and GraphQL.
14 -
15 -## Configure Shopify authentication
16 -
17 -**Use OAuth2 or S2S auth instead of API-key/admin-token auth.** Shopify deprecated the old admin-created custom-app token copy/paste path for new apps. New Dev Dashboard apps expose a Client ID and Client Secret, and the access token is generated programmatically with Shopify's client-credentials flow. In Composio, do not direct new Shopify users to API-key/Admin API Access Token auth. Use OAuth2 for user-facing Shopify integrations, or S2S auth when that matches the app's server-to-server/client-credentials use case.
18 -
19 -- Shopify docs: [client credentials grant](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens/client-credentials-grant), [admin-created custom app tokens](https://shopify.dev/docs/apps/build/authentication-authorization/access-tokens/generate-app-access-tokens-admin)
20 -
21 -If an auth screen still asks for an Admin API key, verify the authConfig is not using the deprecated API-key mode.
22 -
23 -**Use Composio's toolkit auth callback as the OAuth redirect URL.** Set the Shopify OAuth app redirect URL to the exact callback shown by the current Composio custom-auth-config flow. Older or mistyped v1/v3 callback paths can cause OAuth redirect failures, so copy the current value rather than relying on a hard-coded URL in this article.
24 -
25 -**Keep the hosted auth experience when using custom credentials.** Using custom Shopify OAuth credentials does not change the end-user hosted auth and redirect experience. Users still go through the same Composio connect flow, and Composio continues to handle token refresh and credential management automatically. Masking changes for managed credentials do not affect custom-credential toolkits in the same way.
26 -
27 -**Check credentials and gated scopes when OAuth returns 400.** A Shopify OAuth 400 during token exchange or connection initiation is commonly caused by incorrect credentials, especially a wrong client secret, or by gated scopes that have not been verified/approved. Re-enter the authConfig client secret carefully and initiate a fresh connection. Also verify the requested Shopify scopes are available to the app.
28 -
29 -**Pass only the store name as the Shopify subdomain.** When Composio asks for the Shopify subdomain, pass only the store name, such as `your-store-name`. Do not pass the full host like `your-store-name.myshopify.com`; Composio constructs the Shopify domain from the subdomain.
30 -
31 -## Discover and run Shopify tools
32 -
33 -**Use the current GraphQL tool slug.** Use the updated Shopify GraphQL tool slug `SHOPIFY_GRAPH_QL_QUERY` for Shopify GraphQL queries. If the tool is not visible in tool discovery, make sure enough tools are being fetched and that the tool is enabled in the MCP/config being used.
34 -
35 -**Fetch more than the default 20 tools when needed.** Tool fetching can default to a limited number of tools. Pass a higher `limit`, for example `tools.get(user_id="<userId>", toolkits=["shopify"], limit=1000)`, to fetch the full Shopify tool set. For MCP, also confirm the target Shopify tool is enabled when creating the MCP config or by modifying the existing config.
36 -
37 -**Create custom Shopify tools with Composio-injected auth.** Create a custom tool/action under the Shopify toolkit and call Shopify's GraphQL endpoint from inside it. Composio injects the Shopify auth automatically through the custom tool execution path. For newer examples, the endpoint can be `/graphql.json`; older snippets used the full `https://<shopify-sub-domain>.myshopify.com/admin/api/<version>/graphql.json` endpoint. Include the JSON content type header and pass the GraphQL query in the body.
38 -
39 -## Work with Shopify orders
40 -
41 -**List orders before running follow-up actions.** Call `SHOPIFY_GET_ORDERS_WITH_FILTERS` first to confirm the store has orders and retrieve order IDs from the response payload. Follow its `page_info` cursor when more than one page may match. Then pass a returned order ID into follow-up actions such as `SHOPIFY_GET_ORDER` or `SHOPIFY_UPDATE_ORDER`. The older `SHOPIFY_GET_ORDER_LIST` action is deprecated.
42 -
43 -**Check `read_all_orders` when order calls return 403.** Check the scopes on the Shopify connection. If the connection lacks `read_all_orders`, reconnect with the needed order scopes before retrying order update/read calls that require access beyond the default order scope set.
docs/content/kb/guide/toolkits-slack.mdx deleted
-43
@@ -1,43 +0,0 @@
1 ----
2 -title: "Slack"
3 -description: "Public support knowledge for Slack."
4 -keywords: ["for-you","platform","slack","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/slack-troubleshooting","download-slack-file-content-using-file-id","revoked-slack-tokens-can-remain-active-briefly-before-expiring","slack-admin-conversation-writes-require-enterprise","slack-assistant-search-context-requires-agents-ai-apps-and-business","slack-marketplace-warning-on-composio-managed-app-does-not-block-oauth","slack-scheduled-message-attachments-are-not-file-uploads","slack-short-connect-links-are-not-the-oauth-redirect-uri","slack-trigger-delivery-depends-on-the-slack-app-event-subscription-web","slack-troubleshooting","slackbot-token-rotation-can-make-externally-cached-tokens-expire-quick","use-slack-v2-trigger-slugs-for-channel-and-direct-messages","use-user-scopes-for-slack-user-token-permissions","use-your-own-slack-oauth-app-for-production-quota-isolation"]
5 -sources: [{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Use `user_scopes` for Slack user-token permissions"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Download Slack file content using file ID"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Slack `assistant.search.context` requires Agents & AI Apps and Business+"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Use Slack V2 trigger slugs for channel and direct messages"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Slack trigger delivery depends on the Slack app event subscription webhook URL"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Slack short connect links are not the OAuth redirect URI"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"Slack scheduled-message attachments are not file uploads"},{"sourcePath":"toolkits/slack/public.md","sourceHeading":"`admin.conversations:write` requires Slack Enterprise"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["slack"]
11 -aliases: ["/kb/toolkits/slack-troubleshooting","download-slack-file-content-using-file-id","revoked-slack-tokens-can-remain-active-briefly-before-expiring","slack-admin-conversation-writes-require-enterprise","slack-assistant-search-context-requires-agents-ai-apps-and-business","slack-marketplace-warning-on-composio-managed-app-does-not-block-oauth","slack-scheduled-message-attachments-are-not-file-uploads","slack-short-connect-links-are-not-the-oauth-redirect-uri","slack-trigger-delivery-depends-on-the-slack-app-event-subscription-web","slack-troubleshooting","slackbot-token-rotation-can-make-externally-cached-tokens-expire-quick","use-slack-v2-trigger-slugs-for-channel-and-direct-messages","use-user-scopes-for-slack-user-token-permissions","use-your-own-slack-oauth-app-for-production-quota-isolation"]
12 ----
13 -## Use `user_scopes` for Slack user-token permissions
14 -
15 -For the Slack toolkit, `scopes` refers to bot-user scopes. If the use case is to operate as the actual Slack user, pass the permissions in `user_scopes` on the auth config credentials. Slack is special because it separates bot scopes from user scopes. For user-token tools, set `credentials.user_scopes`; the bot `scopes` field may not matter if the Slack application has no bot-user tools for that use case.
16 -
17 -## Download Slack file content using file ID
18 -
19 -Slack file download is supported through `SLACK_DOWNLOAD_SLACK_FILE`. Pass the Slack file ID, which starts with `F` such as `F123ABCDEF0`. The tool returns downloadable file content plus metadata such as name, mimetype, and size. If the file ID is unknown, first call `SLACK_LIST_FILES_WITH_FILTERS_IN_SLACK` to find file IDs, then pass the selected ID to the download tool.
20 -
21 -## Slack `assistant.search.context` requires Agents & AI Apps and Business+
22 -
23 -Slack's `assistant.search.context` requires the Slack OAuth app to have the Agents & AI Apps feature enabled, and the Slack workspace must be on Business+ or higher. Verify workspace support by calling `assistant.search.info`; if `is_ai_search_enabled` is `false`, the workspace plan or feature enablement is the blocker. A customer can unblock with their own Slack OAuth app that has Agents & AI Apps enabled, but they still need Business+ on the workspace.
24 -
25 -## Use Slack V2 trigger slugs for channel and direct messages
26 -
27 -Use the Slack V2 triggers for message events. `SLACK_CHANNEL_MESSAGE_RECEIVED` is intended for channel messages, and `SLACK_DIRECT_MESSAGE_RECEIVED` is intended for DMs. Slack V2 triggers include dedicated endpoints, signature verification, better DM handling, and richer filtering. Older V1 Slack trigger slugs may still work, but V2 is the recommended path for new setups.
28 -
29 -## Slack trigger delivery depends on the Slack app event subscription webhook URL
30 -
31 -When Slack trigger events stop unexpectedly, check whether the Slack OAuth app's Event Subscriptions `webhook_url` was changed. If the webhook URL or other Slack app event-subscription settings changed, Slack may stop delivering events to Composio even though the trigger instance was previously working.
32 -
33 -## Slack short connect links are not the OAuth redirect URI
34 -
35 -The short `/api/v3/s/...` URL is not the `redirect_uri` sent to Slack. It is only a shortened link that redirects the browser to Slack's authorization page. The actual Redirect URI is available in the authConfig and must match what is configured in the Slack OAuth app. The static `callbackUrl` / `redirectUri` must be configured consistently on both Composio and the Slack OAuth app, while `redirectUrl` is the per-connection authentication URL used to send the user through the auth flow.
36 -
37 -## Slack scheduled-message attachments are not file uploads
38 -
39 -The `attachments` field on Slack scheduled messages refers to Slack's legacy secondary/rich-formatting attachments, not uploaded files. Slack's `chat.scheduleMessage` API does not natively upload files. Files must be uploaded separately, for example with `files.upload` / `files.upload.v2`, and then linked or embedded into the scheduled message body so they unfurl when the scheduled message is posted.
40 -
41 -## `admin.conversations:write` requires Slack Enterprise
42 -
43 -`admin.conversations:write` is an enterprise/admin-level Slack scope. For APIs such as `admin.conversations.delete`, the Slack workspace must be on an Enterprise plan. If you cannot use channel deletion/admin conversation tools, first confirm the Slack workspace plan and whether the app has the required admin scope.
docs/content/kb/guide/toolkits-slackbot.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Slackbot"
3 -description: "Public support knowledge for Slackbot."
4 -keywords: ["for-you","platform","slackbot","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/slackbot-troubleshooting","revoked-slack-tokens-may-stay-active-for-two-refresh-cycles-before-exp","slack-file-downloads-use-slack-download-slack-file-with-a-slack-file-i","slack-private-conversations-require-separate-history-scopes","slack-short-auth-links-are-not-the-oauth-redirect-uri","slackbot-trigger-payloads-include-connection-id-and-trigger-id","slackbot-trigger-setup-needs-team-read-on-the-user-token","slackbot-triggers-require-a-verification-token-or-subscription-id-in-c","slackbot-troubleshooting","use-slack-for-user-actions-and-slackbot-for-bot-token-bot-scope-action","with-slack-token-rotation-enabled-fetch-connected-account-data-frequen"]
5 -sources: [{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Use Slack for user actions and Slackbot for bot-token/bot-scope actions"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Slackbot triggers require the verification token in custom auth"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Private Slack channels and DMs require extra history scopes"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Slack file downloads use `SLACK_DOWNLOAD_SLACK_FILE` with a Slack file ID"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Slack short auth links are not the OAuth redirect URI"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Use `SLACKBOT_SEND_MESSAGE` to post a bot message"},{"sourcePath":"toolkits/slackbot/public.md","sourceHeading":"Slackbot trigger payloads include `connection_id` and `trigger_id`"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["slackbot"]
11 -aliases: ["/kb/toolkits/slackbot-troubleshooting","revoked-slack-tokens-may-stay-active-for-two-refresh-cycles-before-exp","slack-file-downloads-use-slack-download-slack-file-with-a-slack-file-i","slack-private-conversations-require-separate-history-scopes","slack-short-auth-links-are-not-the-oauth-redirect-uri","slackbot-trigger-payloads-include-connection-id-and-trigger-id","slackbot-trigger-setup-needs-team-read-on-the-user-token","slackbot-triggers-require-a-verification-token-or-subscription-id-in-c","slackbot-troubleshooting","use-slack-for-user-actions-and-slackbot-for-bot-token-bot-scope-action","with-slack-token-rotation-enabled-fetch-connected-account-data-frequen"]
12 ----
13 -Use this guide to choose the correct Slack token model, configure Slackbot scopes and triggers, and send or download Slack content.
14 -
15 -## Choose Slack or Slackbot and configure authentication
16 -
17 -**Match the toolkit to the token model.** Slack and Slackbot serve different token models. The Slack toolkit performs actions on behalf of an actual Slack user. The Slackbot toolkit performs actions as a bot and should be used for bot scopes such as `channels:join` or bot-token workflows. For mixed use cases, create separate Slack and Slackbot auth configs rather than combining user and bot scopes in one connection.
18 -
19 -**Include the verification token for custom Slackbot triggers.** For Slackbot triggers with custom auth, configure the Slack app verification token in the auth config, then create a fresh connection after updating the auth config. The current auth schema does not expose a separate subscription-ID field, so do not substitute one for the verification token.
20 -
21 -**Add history scopes for private channels and DMs.** Slack private-channel and DM access requires additional scopes. Use `groups:history` for private channels, `im:history` for direct messages, and `mpim:history` for multi-person DMs. These scopes are not always included by default and may be limited by Slack plan/provider constraints, so the customer may need a custom Slack app with the relevant scopes.
22 -
23 -**Do not use a short auth link as the OAuth redirect URI.** The short `/api/v3/s/...` auth link is only a shortened connection initiation URL that redirects the browser to Slack. It is not the `redirect_uri` sent to Slack. Configure the static redirect/callback URI shown in the Composio auth config in the Slack OAuth app; either supported v1 or v3 callback URI can be used depending on the auth config.
24 -
25 -## Run Slackbot actions and handle trigger events
26 -
27 -**Resolve the Slack file ID before downloading content.** Slack file content can be downloaded with `SLACK_DOWNLOAD_SLACK_FILE`. The tool needs the Slack file ID, usually starting with `F`. If the customer does not have the file ID yet, use `SLACK_LIST_FILES_WITH_FILTERS_IN_SLACK` first and pass the returned file ID to the download tool.
28 -
29 -**Choose one visible content mode when sending a bot message.** Use `SLACKBOT_SEND_MESSAGE` to post to a channel, direct message, or private group. Provide exactly one visible content mode: `markdown_text` for normal Markdown content, or `blocks` for a raw Block Kit layout. Use `fallback_text` only with `blocks`.
30 -
31 -**Use trigger identifiers to map events back to connections.** Slackbot trigger payloads include identifiers such as `connection_id` and `trigger_id` inside the payload data. Use `connection_id` to map the event back to the connected account involved in the trigger.
docs/content/kb/guide/toolkits-snapchat.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Snapchat authentication"
3 -description: "Current customer-owned OAuth setup for the Snapchat toolkit."
4 -keywords: ["for-you","platform","snapchat","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/snapchat/public.md","sourceHeading":"Snapchat uses customer-owned OAuth credentials"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["snapchat"]
11 -aliases: []
12 ----
13 -## Snapchat uses customer-owned OAuth credentials
14 -
15 -The current `snapchat` toolkit supports OAuth2 and requires a Snapchat app's
16 -client ID and client secret. Register the exact redirect URI shown by the
17 -current Composio auth-config flow and request only the Snapchat permissions
18 -approved for that app.
19 -
20 -If Snapchat rejects the authorization request before the user signs in, verify
21 -the client ID, redirect URI, and approved scopes on the Snapchat app. A
22 -pre-login authorization error is not evidence that the user's Snapchat
23 -password is wrong.
docs/content/kb/guide/toolkits-snowflake.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Snowflake"
3 -description: "Public support knowledge for Snowflake."
4 -keywords: ["for-you","platform","snowflake","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/snowflake-troubleshooting","configure-snowflake-oauth-refresh-tokens-and-expect-periodic-reconnect","snowflake-account-id-uses-org-account-format","snowflake-basic-auth-was-deprecated-in-favor-of-oauth2","snowflake-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Use one Snowflake auth config per customer account for multi-tenant SaaS OAuth"},{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Snowflake Basic auth was deprecated in favor of OAuth2"},{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Configure Snowflake OAuth refresh tokens and expect periodic reconnects"},{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Fetch connected-account fields or toolkit metadata to discover Snowflake account details"},{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Snowflake statement results may require checking each partition"},{"sourcePath":"toolkits/snowflake/public.md","sourceHeading":"Use processors or tool description overrides to reduce Snowflake tool output/token load"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["snowflake"]
11 -aliases: ["/kb/authentication/snowflake-troubleshooting","configure-snowflake-oauth-refresh-tokens-and-expect-periodic-reconnect","snowflake-account-id-uses-org-account-format","snowflake-basic-auth-was-deprecated-in-favor-of-oauth2","snowflake-troubleshooting"]
12 ----
13 -## Use one Snowflake auth config per customer account for multi-tenant SaaS OAuth
14 -
15 -For Snowflake multi-tenant OAuth, create one Composio auth config per customer Snowflake account using that customer's Snowflake OAuth credentials from `CREATE SECURITY INTEGRATION`. Store the returned `auth_config_id` against the customer on your side. When connecting a user, pass the correct `auth_config_id`; Composio will collect the per-connection Account ID, such as `myorg-myaccount`, and use it to construct the Snowflake authorization/token URLs.
16 -
17 -## Snowflake Basic auth was deprecated in favor of OAuth2
18 -
19 -Snowflake Basic authentication was deprecated and replaced by OAuth2. Customers using old Basic-auth Snowflake auth configs or connected accounts should migrate to OAuth2 by creating the Snowflake OAuth security integration, creating a Composio auth config with those credentials, and reconnecting users. Basic-auth actions may differ from OAuth2 actions and should not be treated as the long-term path.
20 -
21 -## Configure Snowflake OAuth refresh tokens and expect periodic reconnects
22 -
23 -For longer-lived Snowflake OAuth connections, configure the Snowflake security integration with `OAUTH_ISSUE_REFRESH_TOKENS = TRUE` so refresh tokens are issued, and set `OAUTH_REFRESH_TOKEN_VALIDITY` as high as Snowflake allows, such as 7776000 seconds (about 90 days). Even with the max window, Snowflake can require users to reconnect after the refresh-token validity period, so design the product flow to handle periodic reconnects.
24 -
25 -## Fetch connected-account fields or toolkit metadata to discover Snowflake account details
26 -
27 -To discover fields collected during connection initiation, call the toolkit-by-slug endpoint and inspect the accepted initiation fields. After a connection exists, fetch the connected account by ID to retrieve the stored connection fields. Provider schemas are mostly static, but providers can change them, so the toolkit metadata endpoint is the safer source for current required/accepted fields.
28 -
29 -## Snowflake statement results may require checking each partition
30 -
31 -If a Snowflake query returns partial results, check whether the result set is split into partitions. Snowflake may not return all partitions in a single tool call. Use `SNOWFLAKE_CHECK_STATEMENT_STATUS` with the statement handle to poll an asynchronous query until it finishes and retrieve its result.
32 -
33 -## Use processors or tool description overrides to reduce Snowflake tool output/token load
34 -
35 -For Snowflake tools that return too much data or need LLM-facing schema or description changes, use processors to post-process tool output before returning it to the model. For a local agent setup, you can also modify a returned tool object's description before passing it to the model.
docs/content/kb/guide/toolkits-spotify.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Spotify"
3 -description: "Public support knowledge for Spotify."
4 -keywords: ["for-you","platform","spotify","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/spotify-troubleshooting","custom-spotify-toolkit-names-cannot-collide-with-the-built-in-spotify","spotify-can-be-added-to-an-mcp-server-from-the-mcp-configs-page","spotify-has-trigger-support","spotify-library-scopes-may-need-to-be-added-to-the-auth-config-and-the","spotify-playlist-writes-require-playlist-modify-scopes","spotify-tokens-may-need-manual-provider-side-removal-when-programmatic","spotify-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Spotify requires a customer-owned OAuth app"},{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Spotify library scopes may need to be added to the auth config and then the user must reconnect"},{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Custom Spotify toolkit names cannot collide with the built-in Spotify toolkit slug/name"},{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Spotify can be added to an MCP server from the MCP configs page"},{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Spotify has trigger support"},{"sourcePath":"toolkits/spotify/public.md","sourceHeading":"Spotify playlist writes require playlist-modify scopes"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["spotify"]
11 -aliases: ["/kb/toolkits/spotify-troubleshooting","custom-spotify-toolkit-names-cannot-collide-with-the-built-in-spotify","spotify-can-be-added-to-an-mcp-server-from-the-mcp-configs-page","spotify-has-trigger-support","spotify-library-scopes-may-need-to-be-added-to-the-auth-config-and-the","spotify-playlist-writes-require-playlist-modify-scopes","spotify-tokens-may-need-manual-provider-side-removal-when-programmatic","spotify-troubleshooting"]
12 ----
13 -Use this guide to configure Spotify OAuth and scopes, then use Spotify through MCP, custom toolkits, and triggers.
14 -
15 -## Configure Spotify OAuth and scopes
16 -
17 -**Use a customer-owned OAuth app.** Composio-managed OAuth is not currently available for Spotify. Create a custom auth config with your Spotify client ID and client secret, then have each user complete the Spotify authorization flow.
18 -
19 -**Add library scopes before reconnecting.** If Spotify tools need library access, ensure scopes such as `user-library-read` and `user-library-modify` are present in the auth config. After adding scopes, reconnect so the connected account receives the new grants.
20 -
21 -**Add playlist-write scopes before reconnecting.** If playlist write actions return Spotify `403 Insufficient client scope`, make sure the auth config requests `playlist-modify-public`, `playlist-modify-private`, or both as appropriate. Add the scopes before reconnecting; reconnecting an unchanged auth config preserves the same missing-scope problem.
22 -
23 -This is separate from older playlist endpoint issues. A call can reach the current `/items` endpoint and still fail because its token lacks playlist write permission.
24 -
25 -## Use Spotify through MCP, custom toolkits, and triggers
26 -
27 -**Avoid names that collide with the built-in toolkit.** If creating a custom Spotify-related toolkit, avoid naming it exactly `Spotify` because a built-in Spotify toolkit already exists. Use a distinct name such as `spotify-custom` to avoid slug or name collision errors.
28 -
29 -**Add Spotify from the MCP configs page.** To use Spotify through MCP, create or edit an MCP config from the platform MCP configs page and add Spotify to that server. Then use the generated MCP URL in the MCP client.
30 -
31 -**Check the current trigger catalog when an event is missing.** Spotify is listed among trigger-capable toolkits, with three Spotify triggers. If the event you need is missing, submit it through the standard trigger-request flow.
docs/content/kb/guide/toolkits-stripe.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Stripe"
3 -description: "Public support knowledge for Stripe."
4 -keywords: ["for-you","platform","stripe","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/authentication/stripe-troubleshooting","/kb/toolkits/duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records","/kb/toolkits/stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n","a-stripe-trigger-should-create-a-corresponding-subscription-webhook-in","additional-stripe-endpoints-can-be-added-as-toolkit-requests","duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records","mrr-can-be-calculated-from-stripe-list-subscriptions","one-stripe-mcp-api-key-connection-maps-to-one-stripe-account-unless-th","some-stripe-triggers-worked-with-api-key-auth-but-failed-with-oauth-on","stripe-api-key-connections-require-a-secret-key","stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n","stripe-may-require-customer-owned-credentials-because-a-default-oauth","stripe-tokens-may-not-be-revocable-programmatically-through-provider-a","stripe-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/stripe/public.md","sourceHeading":"Stripe is supported and offers OAuth2 and API-key auth modes"},{"sourcePath":"toolkits/stripe/public.md","sourceHeading":"For Stripe API-key auth, use the Stripe secret key from Developers -> API Keys -> Standard keys"},{"sourcePath":"toolkits/stripe/public.md","sourceHeading":"One Stripe MCP/API-key connection maps to one Stripe account unless the customer uses Stripe Connect"},{"sourcePath":"toolkits/stripe/public.md","sourceHeading":"MRR can be calculated from `STRIPE_LIST_SUBSCRIPTIONS`"},{"sourcePath":"toolkits/stripe/public.md","sourceHeading":"Stripe payment-success triggers are available"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["stripe"]
11 -aliases: ["/kb/authentication/stripe-troubleshooting","/kb/toolkits/duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records","/kb/toolkits/stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n","a-stripe-trigger-should-create-a-corresponding-subscription-webhook-in","additional-stripe-endpoints-can-be-added-as-toolkit-requests","duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records","mrr-can-be-calculated-from-stripe-list-subscriptions","one-stripe-mcp-api-key-connection-maps-to-one-stripe-account-unless-th","some-stripe-triggers-worked-with-api-key-auth-but-failed-with-oauth-on","stripe-api-key-connections-require-a-secret-key","stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n","stripe-may-require-customer-owned-credentials-because-a-default-oauth","stripe-tokens-may-not-be-revocable-programmatically-through-provider-a","stripe-troubleshooting"]
12 ----
13 -## Stripe is supported and offers OAuth2 and API-key auth modes
14 -
15 -Composio supports the Stripe toolkit with OAuth2 and API-key auth modes; the marketplace entry is available on the Stripe toolkit page.
16 -
17 -## For Stripe API-key auth, use the Stripe secret key from Developers -> API Keys -> Standard keys
18 -
19 -For Stripe API-key auth, use the Stripe secret key from Stripe Dashboard -> Developers -> API Keys -> Standard keys -> Secret key. In API/SDK connection payloads, the auth config field may need to be passed as `api_key`.
20 -
21 -## One Stripe MCP/API-key connection maps to one Stripe account unless the customer uses Stripe Connect
22 -
23 -Stripe usually uses different API keys for separate accounts, so one connected account/MCP server has access to one Stripe account. If the customer uses Stripe Connect, the platform can consolidate connected accounts under one platform API key and may better fit multi-account workflows.
24 -
25 -## MRR can be calculated from `STRIPE_LIST_SUBSCRIPTIONS`
26 -
27 -Use `STRIPE_LIST_SUBSCRIPTIONS` to retrieve subscription data, then calculate MRR from the returned subscriptions in the agent/application layer.
28 -
29 -## Stripe payment-success triggers are available
30 -
31 -Use `STRIPE_CHECKOUT_SESSION_COMPLETED` for completed Checkout sessions. Fetch the current trigger catalog for invoice payment events before implementation rather than assuming every Stripe event has a corresponding trigger.
docs/content/kb/guide/toolkits-supabase.mdx deleted
-42
@@ -1,42 +0,0 @@
1 ----
2 -title: "Supabase"
3 -description: "Public support knowledge for Supabase."
4 -keywords: ["for-you","platform","supabase","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/supabase-troubleshooting","composio-does-not-enforce-hard-service-rate-limits-check-the-underlyin","cursor-mcp-server-name-length-limits-can-break-supabase-mcp","hosted-supabase-should-use-https-api-supabase-com-as-base-url-not-the","limit-supabase-scopes-in-the-customer-s-oauth-app-not-through-composio","self-hosted-supabase-requires-toolkit-support-for-a-custom-base-url","supabase-api-key-connections-pass-supabase-personal-token-during-conne","supabase-authorization-is-usually-organization-scoped","supabase-beta-run-sql-query-is-still-available-when-configured-in-an-m","supabase-mcp-in-cursor-may-need-an-explicit-initiate-connection-step","supabase-permission-errors-are-often-provider-side-access-control-fail","supabase-supports-both-oauth2-and-api-key-auth-through-composio-apis","supabase-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Supabase authorization is usually organization-scoped"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Supabase API-key connections pass `supabase_personal_token` during connected account creation"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Supabase supports both OAuth2 and API_KEY auth through Composio APIs"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Supabase MCP in Cursor may need an explicit initiate-connection step"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"`SUPABASE_BETA_RUN_SQL_QUERY` is still available when configured in an MCP server"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Hosted Supabase should use `https://api.supabase.com` as base URL, not the project URL"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Self-hosted Supabase requires toolkit support for a custom base URL"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Configure Supabase Management API scopes on the Supabase OAuth app"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Supabase permission errors are often provider-side access-control failures"},{"sourcePath":"toolkits/supabase/public.md","sourceHeading":"Diagnose Supabase rate limits from the underlying error"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["supabase"]
11 -aliases: ["/kb/toolkits/supabase-troubleshooting","composio-does-not-enforce-hard-service-rate-limits-check-the-underlyin","cursor-mcp-server-name-length-limits-can-break-supabase-mcp","hosted-supabase-should-use-https-api-supabase-com-as-base-url-not-the","limit-supabase-scopes-in-the-customer-s-oauth-app-not-through-composio","self-hosted-supabase-requires-toolkit-support-for-a-custom-base-url","supabase-api-key-connections-pass-supabase-personal-token-during-conne","supabase-authorization-is-usually-organization-scoped","supabase-beta-run-sql-query-is-still-available-when-configured-in-an-m","supabase-mcp-in-cursor-may-need-an-explicit-initiate-connection-step","supabase-permission-errors-are-often-provider-side-access-control-fail","supabase-supports-both-oauth2-and-api-key-auth-through-composio-apis","supabase-troubleshooting"]
12 ----
13 -Use this guide to connect Supabase, configure its tools and endpoints, and troubleshoot permissions or rate limits.
14 -
15 -## Connect Supabase with OAuth or an API key
16 -
17 -**Confirm the authorized Supabase organization.** Supabase authorization is usually scoped at the organization level. If you have project or account access issues, confirm which Supabase organization/account the connected credentials belong to before treating it as a tool-specific issue.
18 -
19 -**Pass the personal token with the required API-key field.** For Supabase API-key auth, create or use an API-key auth config and pass the personal token as `supabase_personal_token` when creating the connected account. The `/api/v3/toolkits/supabase` endpoint can be used to inspect the required connected-account initiation field name.
20 -
21 -**Choose either OAuth2 or API_KEY auth.** Supabase supports OAuth2 and API_KEY auth, and both can be initiated through Composio APIs. SDKs are wrappers over the same APIs, so anything possible through the SDK should be possible through the API.
22 -
23 -**Initiate the connection explicitly in Cursor.** Ask Cursor/the MCP client to initiate a Supabase connection first. The MCP server should provide an OAuth link, the user completes authentication, and then Supabase tools can execute against the connected account.
24 -
25 -## Configure Supabase tools and endpoints
26 -
27 -**Add the SQL tool to the MCP server when needed.** `SUPABASE_BETA_RUN_SQL_QUERY` is still supported. Create a Supabase integration/MCP server and explicitly configure the Supabase SQL tool in that MCP server if it is not shown on the simplified Supabase MCP page.
28 -
29 -**Use the hosted API base URL for hosted Supabase.** For hosted Supabase, the base URL should be `https://api.supabase.com`. Do not use the project's own Supabase URL unless the customer is self-hosting Supabase. If the wrong base URL was used, delete/recreate the MCP config or connection with the correct base URL.
30 -
31 -**Pass a supported custom base URL for self-hosted Supabase.** Supabase tools default to hosted Supabase at `https://api.supabase.com`, while current toolkit versions can accept a base URL for self-hosted instances. If a self-hosted setup fails, verify the toolkit version and that the custom base URL is passed in the supported field.
32 -
33 -**Configure Management API scopes on the OAuth app.** Supabase configures Management API OAuth scopes on the OAuth app rather than in
34 -the authorization URL. Set the desired scopes in the customer's Supabase OAuth
35 -app, create the corresponding Composio auth config, and reconnect so the new
36 -grant applies. See Supabase's current [OAuth scope documentation](https://supabase.com/docs/guides/integrations/build-a-supabase-oauth-integration/oauth-scopes).
37 -
38 -## Troubleshoot Supabase permissions and rate limits
39 -
40 -**Verify provider-side access for permission errors.** If Supabase returns a permissions/access-control error, verify the connected Supabase account has the required permissions in Supabase. These can be provider-side server permission errors rather than Composio issues.
41 -
42 -**Inspect the underlying error for rate limits.** If the customer sees a rate-limit message, capture the underlying Composio/tool/provider error rather than the wrapper agent's message, because the limit may come from the external provider or agent layer rather than a Composio service limit.
docs/content/kb/guide/toolkits-tavily.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Tavily"
3 -description: "Public support knowledge for Tavily."
4 -keywords: ["for-you","platform","tavily","auth-config","authentication","sessions-and-execution","toolkits-and-providers","/kb/toolkits/tavily-troubleshooting","initiate-tavily-api-key-connections-in-the-legacy-js-sdk-with-generic","tavily-troubleshooting","use-composio-search-for-auth-free-exa-tavily-style-search","use-composio-search-tavily-for-tavily-search"]
5 -sources: [{"sourcePath":"toolkits/tavily/public.md","sourceHeading":"Use COMPOSIO_SEARCH_TAVILY for Tavily search"},{"sourcePath":"toolkits/tavily/public.md","sourceHeading":"Initiate Tavily API-key connections in the legacy JS SDK with generic_api_key"},{"sourcePath":"toolkits/tavily/public.md","sourceHeading":"Use composio_search for auth-free Exa/Tavily-style search"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["tavily"]
11 -aliases: ["/kb/toolkits/tavily-troubleshooting","initiate-tavily-api-key-connections-in-the-legacy-js-sdk-with-generic","tavily-troubleshooting","use-composio-search-for-auth-free-exa-tavily-style-search","use-composio-search-tavily-for-tavily-search"]
12 ----
13 -## Use COMPOSIO_SEARCH_TAVILY for Tavily search
14 -
15 -Use the updated Tavily search tool slug `COMPOSIO_SEARCH_TAVILY` when invoking Tavily search through Composio. If an older Tavily search slug returns schema-related gateway errors, switch to this slug before deeper debugging.
16 -
17 -## Initiate Tavily API-key connections in the legacy JS SDK with generic_api_key
18 -
19 -For Tavily API-key auth in the legacy JS SDK, list the Tavily integration with `toolset.integrations.list({ appName: "tavily" })`, then initiate the connected account with `appName: "tavily"`, `authMode: "API_KEY"`, the integration ID, and `authConfig: { generic_api_key: "<tavily-api-key>" }`. This was provided as a workaround for a JS SDK issue, so prefer the current SDK flow when available.
20 -
21 -## Use composio_search for auth-free Exa/Tavily-style search
22 -
23 -For auth-free web search through Composio, use the `composio_search` toolkit, which provides Exa/Tavily and other search capabilities without separate authentication. Use the standalone Tavily toolkit when a workflow specifically needs Tavily as its own provider-backed integration.
docs/content/kb/guide/toolkits-tiktok.mdx deleted
-46
@@ -1,46 +0,0 @@
1 ----
2 -title: "TikTok"
3 -description: "Public support knowledge for TikTok."
4 -keywords: ["for-you","platform","tiktok","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/tiktok-troubleshooting","connect-tiktok-with-your-own-developer-app","fix-tiktok-client-key-errors","old-tiktok-specific-mcp-url-patterns-are-deprecated-use-connect-mcp","request-only-approved-tiktok-scopes","tiktok-ads-marketing-may-require-a-separate-approved-app-and-test-cred","tiktok-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok is supported, but customers generally need their own TikTok developer app"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok URL-prefix verification must be done on a customer-owned redirect domain, not Composio's shared callback domain"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok OAuth uses `client_key`; credential mismatch or old `client_id` handling causes `client_key` errors"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok app status, scopes, and sandbox/production mode determine who can complete OAuth"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"Old TikTok-specific MCP URL patterns are deprecated; use Connect MCP"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"Public TikTok posting requires the customer's own app to pass TikTok's content posting audit"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok Ads/Marketing may require a separate approved app and test credentials"},{"sourcePath":"toolkits/tiktok/public.md","sourceHeading":"TikTok custom auth must request only approved scopes"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["tiktok"]
11 -aliases: ["/kb/toolkits/tiktok-troubleshooting","connect-tiktok-with-your-own-developer-app","fix-tiktok-client-key-errors","old-tiktok-specific-mcp-url-patterns-are-deprecated-use-connect-mcp","request-only-approved-tiktok-scopes","tiktok-ads-marketing-may-require-a-separate-approved-app-and-test-cred","tiktok-troubleshooting"]
12 ----
13 -## TikTok is supported, but customers generally need their own TikTok developer app
14 -
15 -TikTok is available as a toolkit and currently uses customer-owned TikTok
16 -developer app credentials.
17 -
18 -## TikTok URL-prefix verification must be done on a customer-owned redirect domain, not Composio's shared callback domain
19 -
20 -Do not host TikTok verification files on Composio's shared callback domain. TikTok URL-prefix verification is meant to prove ownership of the redirect domain. Use a redirect URI on a domain you control, host TikTok's verification file there, register that static parameter-free URI in TikTok, and then forward or proxy the callback to Composio if needed.
21 -
22 -## TikTok OAuth uses `client_key`; credential mismatch or old `client_id` handling causes `client_key` errors
23 -
24 -A TikTok `client_key` error is returned by TikTok, not Composio. First re-copy the Client Key and Client Secret from the TikTok developer app, checking for swapped values or trailing spaces. Also confirm the registered redirect URI exactly matches TikTok requirements. Historically, TikTok required `client_key` in the authorize URL while older Composio handling used `client_id`; if an older flow is involved, unshorten the redirect URL and verify the parameter shape.
25 -
26 -## TikTok app status, scopes, and sandbox/production mode determine who can complete OAuth
27 -
28 -For TikTok OAuth failures, ask for the app type/status, sandbox vs production mode, enabled APIs/scopes, redirect URI, and screenshots of the OAuth screen. If the TikTok app is sandbox or under review, only authorized testers/users may be able to complete OAuth.
29 -
30 -## Old TikTok-specific MCP URL patterns are deprecated; use Connect MCP
31 -
32 -Do not use old toolkit-specific MCP URL patterns for TikTok. Use Connect MCP at `connect.composio.dev/mcp` or create the appropriate MCP/server through the current dashboard/API flow.
33 -
34 -## Public TikTok posting requires the customer's own app to pass TikTok's content posting audit
35 -
36 -For TikTok public content posting, you must go through TikTok's content posting audit with your own OAuth app. Without an audited/approved app, posting may be restricted, for example to private-only visibility or limited testing behavior.
37 -
38 -## TikTok Ads/Marketing may require a separate approved app and test credentials
39 -
40 -TikTok Ads/Marketing may require a separate approved TikTok app and active account credentials. Determine whether you need authentication only or specific tools, and allow time for TikTok app approval.
41 -
42 -## TikTok custom auth must request only approved scopes
43 -
44 -The TikTok toolkit's default set can include `user.info.basic`, `user.info.profile`, `user.info.stats`, `video.list`, `video.upload`, and `video.publish`. A customer-owned app approved for only a subset can fail OAuth when the auth config falls back to the full default.
45 -
46 -Set an explicit scope list on the custom auth config containing only permissions TikTok approved for that app, then reconnect. Existing tokens retain their original grants. Tools for profile details, statistics, or video lists remain unavailable unless the corresponding scopes are approved and requested.
docs/content/kb/guide/toolkits-trello.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Trello"
3 -description: "Public support knowledge for Trello."
4 -keywords: ["for-you","platform","trello","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/trello-troubleshooting","connect-trello-to-cursor-by-creating-a-trello-mcp-instance-and-running","get-the-authenticated-trello-user-with-trello-get-members-by-id-member","invalid-trello-board-id-can-break-trello-triggers","legacy-mcp-composio-dev-trello-endpoint-should-be-migrated-to-tool-rou","old-trello-auth-configs-can-fail-after-oauth-app-changes-create-a-new","route-trello-mcp-calls-by-appending-user-id-or-connected-account-id","trello-supports-oauth1-and-bearer-token-authentication","trello-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Trello supports managed and customer-owned OAuth1"},{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Route Trello MCP calls by appending user_id or connected_account_id"},{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Connect Trello to Cursor by creating a Trello MCP instance and running the generated command"},{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Get the authenticated Trello user with TRELLO_GET_MEMBERS_BY_ID_MEMBER and idMember=me"},{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Invalid Trello board ID can break Trello triggers"},{"sourcePath":"toolkits/trello/public.md","sourceHeading":"Legacy mcp.composio.dev Trello endpoint should be migrated to Tool Router or Connect"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["trello"]
11 -aliases: ["/kb/toolkits/trello-troubleshooting","connect-trello-to-cursor-by-creating-a-trello-mcp-instance-and-running","get-the-authenticated-trello-user-with-trello-get-members-by-id-member","invalid-trello-board-id-can-break-trello-triggers","legacy-mcp-composio-dev-trello-endpoint-should-be-migrated-to-tool-rou","old-trello-auth-configs-can-fail-after-oauth-app-changes-create-a-new","route-trello-mcp-calls-by-appending-user-id-or-connected-account-id","trello-supports-oauth1-and-bearer-token-authentication","trello-troubleshooting"]
12 ----
13 -Use this guide to connect Trello with OAuth1, route users through current MCP flows, and resolve Trello identities for tools and triggers.
14 -
15 -## Connect Trello with OAuth1
16 -
17 -Use Composio-managed OAuth1 for the standard connection flow. Create a custom OAuth1 auth config when you need control over the Trello provider app, and have each user complete the authorization flow.
18 -
19 -## Route Trello through current MCP and Connect flows
20 -
21 -**Route each call to the correct user or account.** For multi-user Trello MCP usage, create the Trello auth config and have users complete the auth flow. Then route MCP calls to the right user or connection by appending `user_id=<external-user-id>` or `connected_account_id=<ca_...>` to the MCP server URL, for example `/mcp?user_id=abcd`.
22 -
23 -**Use the generated MCP configuration in Cursor.** To use Trello in Cursor, create a Trello MCP instance or server in Composio, select the Trello tools, then run or add the generated MCP command or config in Cursor. Complete the Trello account connection when prompted by the MCP flow.
24 -
25 -**Migrate legacy MCP endpoints.** If you are using `https://mcp.composio.dev/trello` or another legacy Trello MCP endpoint, migrate to Tool Router or Composio Connect. Tool Router and Connect are the supported path for current integrations.
26 -
27 -## Resolve Trello users and trigger board IDs
28 -
29 -**Get the authenticated Trello user.** Use `TRELLO_GET_MEMBERS_BY_ID_MEMBER` with `idMember` set to `me` to retrieve the authenticated Trello user or member for the current connection.
30 -
31 -**Validate board IDs before creating triggers.** If Trello triggers fail, verify the board ID first. Use tools such as `TRELLO_GET_ORGANIZATIONS_BOARDS_BY_ID_ORG` or `TRELLO_GET_BOARDS_BY_ID_BOARD` to retrieve or confirm the board ID, then recreate or retry the trigger with the valid board ID.
docs/content/kb/guide/toolkits-twitter.mdx deleted
-36
@@ -1,36 +0,0 @@
1 ----
2 -title: "Twitter"
3 -description: "Public support knowledge for Twitter."
4 -keywords: ["for-you","platform","twitter","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/twitter-troubleshooting","connect-x-twitter-with-your-own-developer-app","if-x-v2-api-support-appears-missing-check-for-an-older-twitter-toolkit","search-and-other-app-only-actions-use-the-application-bearer-token","twitter-troubleshooting","twitter-x-posts-must-stay-within-x-s-character-counting-rules","use-composio-s-v1-auth-app-redirect-uri-for-twitter-oauth-callback-mis"]
5 -sources: [{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"Twitter/X requires a customer-owned OAuth app"},{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"Use the current auth-config callback URI for Twitter OAuth callback mismatch errors"},{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"Twitter/X posts must stay within X's character counting rules"},{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"`client-not-enrolled` and `App not linked to project` usually point to Twitter developer app/project setup issues"},{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"If X v2 API support appears missing, check for an older Twitter toolkit version"},{"sourcePath":"toolkits/twitter/public.md","sourceHeading":"Search and other app-only actions use the Application Bearer Token"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["twitter"]
11 -aliases: ["/kb/toolkits/twitter-troubleshooting","connect-x-twitter-with-your-own-developer-app","if-x-v2-api-support-appears-missing-check-for-an-older-twitter-toolkit","search-and-other-app-only-actions-use-the-application-bearer-token","twitter-troubleshooting","twitter-x-posts-must-stay-within-x-s-character-counting-rules","use-composio-s-v1-auth-app-redirect-uri-for-twitter-oauth-callback-mis"]
12 ----
13 -Use this guide to configure Twitter/X authentication, choose the credentials each action needs, and troubleshoot developer-app or toolkit-version errors.
14 -
15 -## Configure Twitter/X authentication
16 -
17 -**Use a customer-owned OAuth app.** Composio-managed credentials are not available for the Twitter toolkit. Create an app in the X Developer Portal, then create a custom Composio auth config with that app's credentials before connecting an account. This has been required since managed Twitter credentials were removed in February 2026.
18 -
19 -- [Twitter toolkit authentication details](https://docs.composio.dev/toolkits/twitter)
20 -- [Managed Twitter credentials removal](https://docs.composio.dev/docs/changelog/2026/02/12)
21 -
22 -**Match the current Composio callback exactly.** For Twitter OAuth callback mismatch errors, configure the Twitter/X developer app with the exact callback shown by the current Composio auth-config flow. Do not use a legacy v1 callback from older examples.
23 -
24 -## Publish and search with the correct credentials
25 -
26 -**Follow X's post-length rules.** Twitter/X enforces strict post length limits. For normal posts, keep the content under 280 characters and follow X's official character-counting behavior, since URLs, Unicode, and special characters may be counted by provider-specific rules.
27 -
28 -**Use the Application Bearer Token for app-only actions.** Several X actions—including recent or full-archive search and counts, post lookup by IDs, post usage, label-stream, and compliance-job actions—use app-only authentication. They read the `Application Bearer Token` from the Twitter auth config, not the connected user's OAuth access token.
29 -
30 -If user-token actions succeed but these actions return 401, verify that the bearer token comes from the same X Developer App as the OAuth client credentials and that the app's X API plan allows the endpoint. Adding user OAuth scopes does not repair an invalid app bearer token. Reconnect only when the user grant also needs to change.
31 -
32 -## Troubleshoot developer-app and toolkit-version errors
33 -
34 -**Fix `client-not-enrolled` and `App not linked to project` in the X developer app.** These errors usually mean the Twitter/X developer app is not correctly connected to a Twitter developer project, or the OAuth app configuration is stale after X's API model changes. Verify the app is linked to a project, configured according to the Twitter setup guide, and aligned with current X API requirements. If the connected account is already `EXPIRED`, recreate the connection after fixing the app configuration.
35 -
36 -**Update older toolkit versions for X v2 support.** The current Twitter/X toolkit uses v2 endpoints. If behavior looks like an older endpoint, check the toolkit version and retry on the latest available version.
docs/content/kb/guide/toolkits-webflow.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "Webflow"
3 -description: "Public support knowledge for Webflow."
4 -keywords: ["for-you","platform","webflow","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/webflow-troubleshooting","create-or-update-webflow-collection-items-with-the-draft-live-flag","deprecated-webflow-v1-endpoints-caused-publish-site-integration-failur","use-a-custom-webflow-oauth-app-when-the-default-app-cannot-authorize-w","use-the-current-webflow-toolkit-version-for-recently-added-page-tools","webflow-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/webflow/public.md","sourceHeading":"Create or update Webflow collection items with the draft/live flag"},{"sourcePath":"toolkits/webflow/public.md","sourceHeading":"Use the current Webflow toolkit version for recently added page tools"},{"sourcePath":"toolkits/webflow/public.md","sourceHeading":"Deprecated Webflow v1 endpoints caused publish-site integration failures"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["webflow"]
11 -aliases: ["/kb/toolkits/webflow-troubleshooting","create-or-update-webflow-collection-items-with-the-draft-live-flag","deprecated-webflow-v1-endpoints-caused-publish-site-integration-failur","use-a-custom-webflow-oauth-app-when-the-default-app-cannot-authorize-w","use-the-current-webflow-toolkit-version-for-recently-added-page-tools","webflow-troubleshooting"]
12 ----
13 -## Create or update Webflow collection items with the draft/live flag
14 -
15 -Use `WEBFLOW_CREATE_COLLECTION_ITEM` to create a collection item and set whether it is draft or live with the `is_draft` parameter. Use `WEBFLOW_UPDATE_COLLECTION_ITEM_V2` to update an existing item. If the customer specifically needs Webflow v2's dedicated individual collection-item publish/live endpoints, treat that as separate publish-collection-item support rather than the basic create/update flow. The older `WEBFLOW_UPDATE_COLLECTION_ITEM` action is deprecated.
16 -
17 -## Use the current Webflow toolkit version for recently added page tools
18 -
19 -When a recently added Webflow tool such as `WEBFLOW_GET_PAGE` is not found through the API, pass the toolkit/tool version explicitly. The base version `00000000_00` can be older than a dated release. Use the latest Webflow toolkit version shown by Composio for API calls that need newly added tools.
20 -
21 -## Deprecated Webflow v1 endpoints caused publish-site integration failures
22 -
23 -If Webflow calls fail because the integration is using unsupported or deprecated endpoints, check whether the failing action is an older v1 Webflow tool. Use the current `WEBFLOW_PUBLISH_SITE` action and current toolkit version; if the failure persists, share the failed tool-call log ID with Composio support.
docs/content/kb/guide/toolkits-whatsapp.mdx deleted
-51
@@ -1,51 +0,0 @@
1 ----
2 -title: "WhatsApp"
3 -description: "Public support knowledge for WhatsApp."
4 -keywords: ["for-you","platform","whatsapp","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro","/kb/toolkits/whatsapp-troubleshooting","meta-oauth-errors-can-require-adding-the-composio-redirect-uri-in-the","reading-whatsapp-replies-is-better-modeled-as-triggers-webhooks-than-a","use-proxy-execute-when-a-whatsapp-meta-workflow-needs-direct-provider","waba-id-is-required-for-whatsapp-connections","whatsapp-api-key-auth-needs-both-system-user-token-and-waba-id","whatsapp-business-app-coexistence-is-enabled-through-meta-embedded-sig","whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro","whatsapp-oauth-requires-a-meta-developer-app-with-business-use-case-en","whatsapp-oauth2-initiation-still-requires-generic-id-as-the-waba-id","whatsapp-send-template-message-supports-components-in-newer-toolkit-ve","whatsapp-template-messages-require-an-existing-template-before-sending","whatsapp-toolkit-supports-whatsapp-business-api-accounts-not-personal","whatsapp-troubleshooting","when-sending-whatsapp-messages-pass-real-phone-number-id-and-to-number"]
5 -sources: [{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp toolkit supports WhatsApp Business API accounts, not personal WhatsApp accounts"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WABA ID is required for WhatsApp connections"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp API key auth needs both system user token and WABA ID"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp OAuth2 initiation still requires `generic_id` as the WABA ID"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp OAuth requires a Meta developer app with Business use case enabled and published"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"Meta OAuth errors can require adding the Composio redirect URI in the Meta app"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp template messages require an existing template before sending"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"`WHATSAPP_SEND_TEMPLATE_MESSAGE` supports `components` in newer toolkit versions"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"When sending WhatsApp messages, pass real `phone_number_id` and `to_number` values"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"Reading WhatsApp replies is better modeled as triggers/webhooks than a normal read API"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"Use Proxy Execute when a WhatsApp/Meta workflow needs direct provider API access with scoped credentials"},{"sourcePath":"toolkits/whatsapp/public.md","sourceHeading":"WhatsApp Business app coexistence is enabled through Meta Embedded Signup"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["whatsapp"]
11 -aliases: ["/kb/toolkits/whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro","/kb/toolkits/whatsapp-troubleshooting","meta-oauth-errors-can-require-adding-the-composio-redirect-uri-in-the","reading-whatsapp-replies-is-better-modeled-as-triggers-webhooks-than-a","use-proxy-execute-when-a-whatsapp-meta-workflow-needs-direct-provider","waba-id-is-required-for-whatsapp-connections","whatsapp-api-key-auth-needs-both-system-user-token-and-waba-id","whatsapp-business-app-coexistence-is-enabled-through-meta-embedded-sig","whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro","whatsapp-oauth-requires-a-meta-developer-app-with-business-use-case-en","whatsapp-oauth2-initiation-still-requires-generic-id-as-the-waba-id","whatsapp-send-template-message-supports-components-in-newer-toolkit-ve","whatsapp-template-messages-require-an-existing-template-before-sending","whatsapp-toolkit-supports-whatsapp-business-api-accounts-not-personal","whatsapp-troubleshooting","when-sending-whatsapp-messages-pass-real-phone-number-id-and-to-number"]
12 ----
13 -Use this guide to connect a WhatsApp Business account, configure Meta authentication, send messages, receive events, and handle coexistence onboarding.
14 -
15 -## Connect a WhatsApp Business account
16 -
17 -**Use a WABA-backed business account instead of a personal account.** WhatsApp API usage requires a WhatsApp Business Account. Personal WhatsApp accounts are for personal communication and are not supported by the WhatsApp Business API flows used by the toolkit. To send WhatsApp messages through Composio, use a WABA-backed business account.
18 -
19 -**Provide the WhatsApp Business Account ID.** The WABA ID, or WhatsApp Business Account ID, is required because the WhatsApp Business API needs it to identify the business account. Customers can find it in Meta Developers under the app's WhatsApp API Setup section, or fetch it programmatically by calling `GET /me/businesses` and then `GET /{business_id}/owned_whatsapp_business_accounts` with an access token.
20 -
21 -**Pass the system user token and WABA ID for API-key auth.** For WhatsApp API key auth, pass the system user token as the bearer token and pass the WABA ID as `generic_id`. The required connection fields depend on the auth scheme, so fetch the toolkit/auth-config initiation fields if unsure. Hosted auth links can also collect these values from the user instead of hardcoding them.
22 -
23 -**Pass the WABA ID as `generic_id` for OAuth2.** WhatsApp OAuth2 auth still requires `generic_id`, and that value is the WhatsApp Business Account ID. API key auth requires both `bearer_token` and `generic_id`, while OAuth2 only requires `generic_id` for initiation. Differences in required initiation fields usually come from the selected auth scheme.
24 -
25 -## Configure Meta OAuth and app access
26 -
27 -**Publish a Meta developer app with the Business use case.** For WhatsApp OAuth with a customer-owned Meta app, create a Meta developer app, enable the Business use case, configure the WhatsApp product, and publish the app so users can connect to it. The Meta app/account used during connection should match the account that owns or can access the WhatsApp Business setup.
28 -
29 -**Add the Composio redirect URI to the Meta app.** For Meta OAuth apps, add the Composio redirect URI to the correct redirect/callback URI field in the Meta developer app. OAuth failures during callback can happen when the app does not allow the redirect URI used by the Composio auth config.
30 -
31 -## Send WhatsApp messages and templates
32 -
33 -**Create and approve a template before sending it.** Sending a WhatsApp template message requires a template to already exist in WhatsApp/Meta. The send-template tool sends an existing template by name/language and parameters; it does not remove the need to create and approve the template first.
34 -
35 -**Use a current toolkit version for template `components`.** Support for `components` was added to the WhatsApp send-template flow in a newer toolkit version. If you cannot pass template variables/components to `WHATSAPP_SEND_TEMPLATE_MESSAGE`, upgrade to the latest WhatsApp toolkit version and verify the `components` field is available in the tool schema.
36 -
37 -**Pass real sender and recipient identifiers.** For WhatsApp send-message actions, make sure the action arguments contain the actual `phone_number_id` and recipient `to_number`. Placeholder values in the tool arguments will fail even if the connected account itself is active.
38 -
39 -## Receive events and extend WhatsApp workflows
40 -
41 -**Use triggers or webhooks for replies.** WhatsApp does not expose every reply-reading flow as a normal API action in the toolkit. The better product shape is a trigger/webhook for events such as message or reply received. Where a first-party WhatsApp trigger is not available for the exact use case, TimelinesAI may be an alternative because it includes WhatsApp-related trigger support.
42 -
43 -**Use Proxy Execute for direct provider operations.** For provider API operations that are not exposed as first-class WhatsApp tools, Proxy Execute can be used with a scoped Composio API key that allows proxy execution. Use this when you need to call a Meta/WhatsApp endpoint directly while still going through Composio-managed connection context.
44 -
45 -## Set up WhatsApp Business app coexistence
46 -
47 -Keeping an existing WhatsApp Business app number active while also using the Cloud API is a Meta-side coexistence onboarding flow, not a Composio activation toggle. Follow Meta's [Onboard WhatsApp Business app users](https://developers.facebook.com/documentation/business-messaging/whatsapp/embedded-signup/onboarding-business-app-users) flow through a Solution Partner or Tech Provider that supports it.
48 -
49 -After the number is active on Cloud API, connect its WABA in Composio through the normal WhatsApp setup. For API-key auth, use the system user token as `bearer_token` and the WABA ID as `generic_id`.
50 -
51 -If the number is shown as `ON_PREMISE`, it may need Meta's On-Premises API to Cloud API migration steps before normal registration or coexistence. Route that onboarding/migration step to Meta or the customer's BSP, then help with the Composio connection once Cloud API is active.
docs/content/kb/guide/toolkits-wrike.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Wrike"
3 -description: "Public support knowledge for Wrike."
4 -keywords: ["for-you","platform","wrike","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/wrike-troubleshooting","assignee-is-not-a-native-field-in-wrike-fetch-task-api-responses","pass-entityid-as-a-string-when-getconnections-returns-404-in-v3-sdk-fl","use-the-composio-proxy-endpoint-or-sdk-executerequest-for-direct-wrike","use-the-wrike-user-id-not-the-account-id-when-assigning-or-updating-ta","use-wrike-toolkit-version-20260204-00-or-latest-for-nested-folder-pagi","wrike-task-responses-expose-multiple-user-id-fields-and-can-resolve-na","wrike-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Use the Wrike user id, not the account id, when assigning or updating task users"},{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Wrike task responses expose multiple user-id fields and can resolve names"},{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Assignee is not a native field in Wrike fetch-task API responses"},{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Use the Composio proxy endpoint or SDK executeRequest for direct Wrike API calls"},{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Pass entityId as a string when getConnections returns 404 in v3 SDK flows"},{"sourcePath":"toolkits/wrike/public.md","sourceHeading":"Use the latest Wrike toolkit version for nested folder pagination"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["wrike"]
11 -aliases: ["/kb/toolkits/wrike-troubleshooting","assignee-is-not-a-native-field-in-wrike-fetch-task-api-responses","pass-entityid-as-a-string-when-getconnections-returns-404-in-v3-sdk-fl","use-the-composio-proxy-endpoint-or-sdk-executerequest-for-direct-wrike","use-the-wrike-user-id-not-the-account-id-when-assigning-or-updating-ta","use-wrike-toolkit-version-20260204-00-or-latest-for-nested-folder-pagi","wrike-task-responses-expose-multiple-user-id-fields-and-can-resolve-na","wrike-troubleshooting"]
12 ----
13 -Use this guide to map Wrike users correctly, call Wrike APIs through Composio, and use current nested-folder behavior.
14 -
15 -## Map Wrike users and assignees
16 -
17 -**Use the Wrike user ID, not the account ID.** For Wrike task update or assignment fields, pass the Wrike user `id` value rather than the `accountId`. Wrike validates the user identifier shown in the user object, not the account identifier.
18 -
19 -**Read user relationships from Wrike's ID arrays.** Wrike task data can contain several user-id fields, including `authorIds`, `responsibleIds`, `sharedIds`, and `followerIds`. For fetch-task results, use the `resolve_user_names` parameter, which is enabled by default, to return those ids along with their names. If identifying the creator specifically, check `authorIds`.
20 -
21 -**Do not expect a native `assignee` field.** Do not expect a separate `assignee` field from the Wrike tasks API or the corresponding fetch-tasks tool. Wrike represents user relationships through id arrays such as responsible/user fields instead of a top-level `assignee` field.
22 -
23 -## Call Wrike APIs through Composio
24 -
25 -**Use the proxy endpoint or SDK `executeRequest`.** For direct Wrike API calls through an existing Composio connected account, call the Composio proxy endpoint with the Wrike path and method, for example `endpoint: "/tasks"`, `method: "GET"`, and the `connected_account_id`. In SDK code, the same pattern can be done with `toolset.client.actions.executeRequest({ connectedAccountId, endpoint: "/tasks", method: "GET", parameters: [] })`. Ensure endpoint values are quoted strings.
26 -
27 -**Pass `entityId` as a string when `getConnections` returns 404 in v3 SDK flows.** When using v3 SDK connection APIs, pass the `entityId` as a string. If the code stores the value as `enterpriseId`, pass it through the SDK entity helper, for example `.getEntity("enterpriseId")`. Also use a current v3 SDK package rather than an older release candidate.
28 -
29 -## Use the latest Wrike toolkit version for nested folders
30 -
31 -For Wrike folder APIs, avoid the base `00000000_00` toolkit version when dealing with nested folders. Retry with `latest` so the request uses the current nested-folder pagination behavior.
docs/content/kb/guide/toolkits-xero.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Xero"
3 -description: "Public support knowledge for Xero."
4 -keywords: ["for-you","platform","xero","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/xero-troubleshooting","connect-mcp-and-platform-mcp-xero-connections-are-independent","connect-mcp-discovers-xero-tools-through-meta-tools-instead-of-preload","connect-xero-with-your-own-oauth-app","if-for-you-xero-connect-button-is-blocked-use-connect-mcp-directly-whi","xero-can-be-blocked-in-claude-cowork-by-payment-processing-session-res","xero-redirect-uri-must-match-exactly-v1-auth-apps-callback-can-be-requ","xero-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/xero/public.md","sourceHeading":"Xero redirect URI must match the current auth-config flow exactly"},{"sourcePath":"toolkits/xero/public.md","sourceHeading":"Xero OAuth app should be a Web app and the client secret must match the auth config"},{"sourcePath":"toolkits/xero/public.md","sourceHeading":"Remove deprecated Xero scopes that cause invalid-scope/CSP/login errors"},{"sourcePath":"toolkits/xero/public.md","sourceHeading":"Connect MCP discovers Xero tools through meta-tools instead of preloading every tool"},{"sourcePath":"toolkits/xero/public.md","sourceHeading":"Connect MCP and Platform MCP Xero connections are independent"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["xero"]
11 -aliases: ["/kb/toolkits/xero-troubleshooting","connect-mcp-and-platform-mcp-xero-connections-are-independent","connect-mcp-discovers-xero-tools-through-meta-tools-instead-of-preload","connect-xero-with-your-own-oauth-app","if-for-you-xero-connect-button-is-blocked-use-connect-mcp-directly-whi","xero-can-be-blocked-in-claude-cowork-by-payment-processing-session-res","xero-redirect-uri-must-match-exactly-v1-auth-apps-callback-can-be-requ","xero-troubleshooting"]
12 ----
13 -## Xero redirect URI must match the current auth-config flow exactly
14 -
15 -Make sure the redirect URI configured in the Xero OAuth app exactly matches the URI shown by the current Composio auth-config flow. Do not fall back to a legacy v1 callback from an older example; copy the current callback from the setup UI or auth-config documentation and match it exactly, without adding a trailing slash.
16 -
17 -## Xero OAuth app should be a Web app and the client secret must match the auth config
18 -
19 -For Xero BYOA/custom OAuth, verify the Xero developer app is configured as a `Web app`, not `Mobile or Desktop`. The redirect URI must match exactly, and the client secret in Composio must match the current secret in the Xero developer portal. If a connection remains in `EXPIRED` with `Connection initiation did not complete within 10 minutes`, restart the auth flow and complete the Xero consent step within the 10-minute window.
20 -
21 -## Remove deprecated Xero scopes that cause invalid-scope/CSP/login errors
22 -
23 -Remove the deprecated/invalid Xero scopes `accounting.journals.read`, `accounting.reports.read`, `accounting.transactions`, and `accounting.transactions.read` from the auth config. Reconnect after removing them. Use Xero's current OAuth scope documentation and keep required scopes such as `offline_access`, `email`, `profile`, `openid`, and the supported `accounting.*` scopes needed for the tools.
24 -
25 -## Connect MCP discovers Xero tools through meta-tools instead of preloading every tool
26 -
27 -Connect MCP uses meta-tools such as `COMPOSIO_SEARCH_TOOLS` and `COMPOSIO_MULTI_EXECUTE_TOOL` to discover and execute toolkit-specific tools dynamically. For Xero, the expected flow is: ask/search for the task such as `get Xero contacts`, let the agent discover the relevant Xero tool, then execute it through the multi-execute tool. This avoids loading schemas from every toolkit into context up front.
28 -
29 -## Connect MCP and Platform MCP Xero connections are independent
30 -
31 -Connect MCP servers and Platform MCP servers are independent. A connection visible in Platform is not automatically available through Connect MCP, so confirm which surface created the Xero connection before debugging account selection.
docs/content/kb/guide/toolkits-ynab.mdx deleted
-23
@@ -1,23 +0,0 @@
1 ----
2 -title: "YNAB authentication"
3 -description: "Current OAuth setup for the YNAB toolkit."
4 -keywords: ["for-you","platform","ynab","auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
5 -sources: [{"sourcePath":"toolkits/ynab/public.md","sourceHeading":"YNAB supports managed and customer-owned OAuth"}]
6 -lastVerifiedAt: "2026-08-24"
7 -reviewAfter: "2026-11-22"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","toolkits-and-providers"]
10 -toolkitSlugs: ["ynab"]
11 -aliases: []
12 ----
13 -## YNAB supports managed and customer-owned OAuth
14 -
15 -Use Composio-managed OAuth for the standard connection flow. Create a custom
16 -auth config with the customer's YNAB client ID and client secret when they need
17 -control over the provider app. For custom OAuth, register the exact redirect URI
18 -shown by the current Composio auth-config flow.
19 -
20 -If YNAB reports that an application is restricted, review the YNAB app's
21 -current review and access-token restrictions. An app intended only for its
22 -owner and an app distributed to unrelated users can have different provider
23 -review requirements. Do not promise a provider approval date.
docs/content/kb/guide/toolkits-youtube.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "YouTube"
3 -description: "Public support knowledge for YouTube."
4 -keywords: ["for-you","platform","youtube","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran","/kb/toolkits/youtube-troubleshooting","use-a-custom-youtube-oauth-app-in-production-to-avoid-shared-default-a","use-direct-file-paths-or-multipart-upload-for-youtube-videos-fileuploa","youtube-caption-download-requires-https-www-googleapis-com-auth-youtub","youtube-has-trigger-support-but-trigger-creation-errors-may-only-surfa","youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran","youtube-transcript-community-post-tools-may-need-feature-requests-or-c","youtube-troubleshooting","youtube-upload-video-with-videofilepath-is-sdk-oriented-and-expects-a"]
5 -sources: [{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"`YOUTUBE_UPLOAD_VIDEO` with `videoFilePath` is SDK-oriented and expects a full file path"},{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"Use direct file paths or the current multipart upload action for YouTube videos"},{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"Diagnose YouTube `processing abandoned` from the current upload and provider state"},{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"YouTube caption download requires `https://www.googleapis.com/auth/youtube.force-ssl`"},{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"YouTube has trigger support, but trigger creation errors may only surface at trigger setup time"},{"sourcePath":"toolkits/youtube/public.md","sourceHeading":"`uploadLimitExceeded` is a YouTube channel limit, not an OAuth-app quota"}]
6 -lastVerifiedAt: "2026-08-17"
7 -reviewAfter: "2026-11-15"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["youtube"]
11 -aliases: ["/kb/toolkits/youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran","/kb/toolkits/youtube-troubleshooting","use-a-custom-youtube-oauth-app-in-production-to-avoid-shared-default-a","use-direct-file-paths-or-multipart-upload-for-youtube-videos-fileuploa","youtube-caption-download-requires-https-www-googleapis-com-auth-youtub","youtube-has-trigger-support-but-trigger-creation-errors-may-only-surfa","youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran","youtube-transcript-community-post-tools-may-need-feature-requests-or-c","youtube-troubleshooting","youtube-upload-video-with-videofilepath-is-sdk-oriented-and-expects-a"]
12 ----
13 -Use this guide to upload YouTube videos, configure scopes and triggers, and distinguish upload failures from provider limits.
14 -
15 -## Upload videos through current YouTube actions
16 -
17 -**Use a full file path with `YOUTUBE_UPLOAD_VIDEO`.** `YOUTUBE_UPLOAD_VIDEO` is intended to be used through the SDK because it accepts `videoFilePath`. Pass a full local file path string such as `/path/to/video.mp4`, and use the latest toolkit version when debugging older upload failures.
18 -
19 -**Choose the current upload path for the file.** For YouTube video uploads, pass a local file path through SDK automatic file handling or use `YOUTUBE_MULTIPART_UPLOAD_VIDEO` when its single-request upload shape fits the file. Do not quote the old 50 MB staged-file limit without checking the current upload path and platform limit.
20 -
21 -## Troubleshoot YouTube processing and provider limits
22 -
23 -**Inspect current execution and provider state for `processing abandoned`.** If YouTube returns `processing abandoned`, first check YouTube Studio/provider status, the video format, and the current toolkit version. Use a fresh execution log to distinguish provider processing failure from an upload-transfer failure.
24 -
25 -**Treat `uploadLimitExceeded` as a channel limit.** YouTube limits how many videos a channel can upload in a 24-hour period across the website, mobile apps, and the YouTube API. If an upload returns `uploadLimitExceeded` or YouTube shows **Daily upload limit reached**, wait 24 hours before retrying. Switching to a different OAuth app does not bypass the channel limit. See YouTube's [common uploading errors](https://support.google.com/youtube/answer/10383400).
26 -
27 -## Configure YouTube scopes and triggers
28 -
29 -**Include the caption-download scope.** For YouTube caption download, verify the connected account includes `https://www.googleapis.com/auth/youtube.force-ssl`. The scope was described as part of the default YouTube scope set, but the actual connection should still be checked from connection details when a tool call fails.
30 -
31 -**Validate the channel ID when creating a trigger.** YouTube supports triggers. For `YOUTUBE_NEW_ACTIVITY_TRIGGER`, use the field descriptions to provide the correct channel ID; trigger creation may otherwise fail without a separate preflight warning.
docs/content/kb/guide/toolkits-zendesk.mdx deleted
-35
@@ -1,35 +0,0 @@
1 ----
2 -title: "Zendesk"
3 -description: "Public support knowledge for Zendesk."
4 -keywords: ["for-you","platform","zendesk","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/zendesk-troubleshooting","include-toolkit-versions-when-listing-zendesk-tools-through-the-api","initiate-zendesk-oauth-connections-by-passing-subdomain-in-config-valu","use-your-own-zendesk-oauth-app-for-production-or-when-the-default-app","zendesk-api-key-basic-auth-initiation-passes-subdomain-and-base64-enco","zendesk-connections-require-the-account-subdomain","zendesk-get-ticket-by-id-returns-ticket-details-in-one-tool-call","zendesk-is-not-officially-supported-in-langflow-connect-through-the-co","zendesk-oauth-setup-does-not-require-manually-entering-an-access-token","zendesk-troubleshooting","zendesk-update-zendesk-ticket-is-available-for-updating-zendesk-ticket"]
5 -sources: [{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Zendesk OAuth setup does not require manually entering an access token"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Zendesk connections require the account subdomain"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Initiate Zendesk OAuth connections by passing `subdomain` in config values"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Zendesk API-key/basic auth initiation passes `subdomain` and base64 encoded credentials"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Include `toolkit_versions` when listing Zendesk tools through the API"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"`ZENDESK_SEARCH_ZENDESK` was added for Zendesk search use cases"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"`ZENDESK_UPDATE_ZENDESK_TICKET` is available for updating Zendesk tickets"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Zendesk get-ticket-by-id returns ticket details in one tool call"},{"sourcePath":"toolkits/zendesk/public.md","sourceHeading":"Zendesk supports triggers in Composio"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["zendesk"]
11 -aliases: ["/kb/toolkits/zendesk-troubleshooting","include-toolkit-versions-when-listing-zendesk-tools-through-the-api","initiate-zendesk-oauth-connections-by-passing-subdomain-in-config-valu","use-your-own-zendesk-oauth-app-for-production-or-when-the-default-app","zendesk-api-key-basic-auth-initiation-passes-subdomain-and-base64-enco","zendesk-connections-require-the-account-subdomain","zendesk-get-ticket-by-id-returns-ticket-details-in-one-tool-call","zendesk-is-not-officially-supported-in-langflow-connect-through-the-co","zendesk-oauth-setup-does-not-require-manually-entering-an-access-token","zendesk-troubleshooting","zendesk-update-zendesk-ticket-is-available-for-updating-zendesk-ticket"]
12 ----
13 -Use this guide to connect a Zendesk account and discover the current tools and triggers for tickets and search.
14 -
15 -## Connect Zendesk with the correct subdomain and auth scheme
16 -
17 -**Let OAuth inject the access token automatically.** For Zendesk OAuth, the access token is injected automatically after the OAuth flow completes; customers do not need to manually enter it. Redirect URI can be optional depending on the auth-config setup, but if Zendesk requires one, configure the Composio auth redirect URL in the Zendesk OAuth app.
18 -
19 -**Pass the account subdomain, not the full URL.** Zendesk requires the account subdomain during connection initiation. Pass the Zendesk site prefix, not the full URL, as `subdomain`. Composio uses that field to construct Zendesk URLs.
20 -
21 -**Include the subdomain in OAuth config values.** When initiating a Zendesk OAuth connected account, pass `subdomain` in the connection config values. For the current SDK shape, use `config={"auth_scheme":"OAUTH2","val":{"subdomain":"<site-name>"}}`; older examples used `connected_account_params={"subdomain":"<site-name>"}`.
22 -
23 -**Pass the subdomain and encoded credential for API-key/basic auth.** For Zendesk API-key/basic auth connection initiation, pass the Zendesk `subdomain` and `basic_encoded` credential value in the connection data. The `basic_encoded` value should be the base64 encoding of the Zendesk email/token credential form requested by the auth config.
24 -
25 -## Use current Zendesk tools and triggers
26 -
27 -**Request the latest toolkit version when listing tools.** When listing Zendesk tools through the API, include the toolkit version query parameter. For example, use `toolkit_versions=latest&toolkit_slug=zendesk&limit=1000`. Without the toolkit version query, the API response may not show the expected tool set.
28 -
29 -**Search Zendesk with the dedicated search action.** Use `ZENDESK_SEARCH_ZENDESK` for Zendesk search use cases.
30 -
31 -**Update tickets with the current ticket action.** Use `ZENDESK_UPDATE_ZENDESK_TICKET` for Zendesk ticket updates. For endpoint-level context, the corresponding Zendesk API is the Update Ticket endpoint in Zendesk's ticketing API.
32 -
33 -**Fetch known ticket details directly.** The Zendesk get-ticket-by-id action is available and returns the ticket details in a single tool call. Use it when the customer has a Zendesk ticket ID and needs the ticket's metadata/details rather than searching first.
34 -
35 -**Verify the current trigger catalog before quoting availability.** Zendesk has trigger support in Composio. Verify the current trigger catalog before naming an exact count.
docs/content/kb/guide/toolkits-zoho-books.mdx deleted
-27
@@ -1,27 +0,0 @@
1 ----
2 -title: "Zoho Books"
3 -description: "Public support knowledge for Zoho Books."
4 -keywords: ["for-you","platform","zoho_books","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/zoho-books-troubleshooting","optional-zoho-books-item-rate-filters-do-not-have-default-values","pin-zoho-books-toolkit-version-when-reproducing-list-items-behavior","use-existing-bill-read-tools-or-file-a-request-for-missing-bill-creati","zoho-books-troubleshooting","zoho-domain-suffix-parameter-expects-the-extension-value"]
5 -sources: [{"sourcePath":"toolkits/zoho_books/public.md","sourceHeading":"Use Zoho Invoice for create estimate"},{"sourcePath":"toolkits/zoho_books/public.md","sourceHeading":"Optional Zoho Books item rate filters do not have default values"},{"sourcePath":"toolkits/zoho_books/public.md","sourceHeading":"Pin Zoho Books toolkit version when reproducing list-items behavior"},{"sourcePath":"toolkits/zoho_books/public.md","sourceHeading":"Zoho domain suffix parameter expects the extension value"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["zoho_books"]
11 -aliases: ["/kb/toolkits/zoho-books-troubleshooting","optional-zoho-books-item-rate-filters-do-not-have-default-values","pin-zoho-books-toolkit-version-when-reproducing-list-items-behavior","use-existing-bill-read-tools-or-file-a-request-for-missing-bill-creati","zoho-books-troubleshooting","zoho-domain-suffix-parameter-expects-the-extension-value"]
12 ----
13 -## Use Zoho Invoice for create estimate
14 -
15 -`ZOHO_BOOKS_CREATE_ESTIMATE` is no longer the Zoho Books tool to use for estimates. Use the Zoho Invoice toolkit and `ZOHO_INVOICE_CREATE_ESTIMATE` instead.
16 -
17 -## Optional Zoho Books item rate filters do not have default values
18 -
19 -The Zoho Books item `rate` field and related rate filters are optional. Composio does not set default values for those fields; if omitted, they default to null behavior. If an agent includes `0` or another value, treat that as model/tool-call behavior and inspect the tool schema with the get-tools-by-slug API reference or adjust the agent/tool-call layer so optional rate filters are not sent unless explicitly requested.
20 -
21 -## Pin Zoho Books toolkit version when reproducing list-items behavior
22 -
23 -When reproducing or sharing a controlled snippet for Zoho Books list-items behavior, use `toolkit_versions={"zoho_books": "latest"}`, then request `ZOHO_BOOKS_LIST_ITEMS` explicitly for the user's connected account context.
24 -
25 -## Zoho domain suffix parameter expects the extension value
26 -
27 -For Zoho Books auth, the Zoho domain parameter expects the extension value such as `com`, `eu`, or `in`; Composio appends it into the URL as the corresponding domain suffix like `.com`. Do not include the leading dot in the parameter value.
docs/content/kb/guide/toolkits-zoho-mail.mdx deleted
-27
@@ -1,27 +0,0 @@
1 ----
2 -title: "Zoho Mail"
3 -description: "Public support knowledge for Zoho Mail."
4 -keywords: ["for-you","platform","zoho_mail","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/zoho-mail-troubleshooting","connect-mcp-is-agent-oriented-authenticate-zoho-mail-in-connect-dashbo","pass-the-correct-zoho-region-when-connecting-zoho-mail","zoho-mail-account-id-must-be-handled-as-a-string-to-avoid-javascript-p","zoho-mail-attachment-download-support-should-be-treated-as-a-feature-r","zoho-mail-messages-send-email-supports-sending-attachments","zoho-mail-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/zoho_mail/public.md","sourceHeading":"ZOHO_MAIL_MESSAGES_SEND_EMAIL supports sending attachments"},{"sourcePath":"toolkits/zoho_mail/public.md","sourceHeading":"Pass the correct Zoho region when connecting Zoho Mail"},{"sourcePath":"toolkits/zoho_mail/public.md","sourceHeading":"Zoho Mail account_id must be handled as a string to avoid JavaScript precision loss"},{"sourcePath":"toolkits/zoho_mail/public.md","sourceHeading":"Connect MCP is agent-oriented; authenticate Zoho Mail in Connect dashboard before tool use"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["zoho_mail"]
11 -aliases: ["/kb/toolkits/zoho-mail-troubleshooting","connect-mcp-is-agent-oriented-authenticate-zoho-mail-in-connect-dashbo","pass-the-correct-zoho-region-when-connecting-zoho-mail","zoho-mail-account-id-must-be-handled-as-a-string-to-avoid-javascript-p","zoho-mail-attachment-download-support-should-be-treated-as-a-feature-r","zoho-mail-messages-send-email-supports-sending-attachments","zoho-mail-troubleshooting"]
12 ----
13 -## ZOHO_MAIL_MESSAGES_SEND_EMAIL supports sending attachments
14 -
15 -`ZOHO_MAIL_MESSAGES_SEND_EMAIL` supports sending attachments. If attachment support was previously missing, retry with the latest toolkit version. If attachment sending still fails, contact Composio support with the redacted tool-call details.
16 -
17 -## Pass the correct Zoho region when connecting Zoho Mail
18 -
19 -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.
20 -
21 -## Zoho Mail account_id must be handled as a string to avoid JavaScript precision loss
22 -
23 -Treat Zoho Mail `account_id` values as strings, not integers. Zoho account IDs can exceed JavaScript's safe integer limit, and numeric coercion can silently truncate them before the tool call reaches Zoho. If you see unexpected account IDs or tool failures with long IDs, verify the schema and payload preserve `account_id` as a string.
24 -
25 -## Connect MCP is agent-oriented; authenticate Zoho Mail in Connect dashboard before tool use
26 -
27 -Connect MCP is intended for agent/client workflows through Tool Router, not as a raw direct API endpoint. For Zoho Mail, make sure the user has connected a Zoho Mail account in the Connect dashboard first, then use the supported MCP client flow. If the user wants direct API execution, route them to Tool Router/API or Proxy Execute patterns instead of treating Connect MCP as a raw REST proxy.
docs/content/kb/guide/toolkits-zoho.mdx deleted
-39
@@ -1,39 +0,0 @@
1 ----
2 -title: "Zoho"
3 -description: "Public support knowledge for Zoho."
4 -keywords: ["for-you","platform","zoho","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/zoho-troubleshooting","request-zoho-mail-attachment-download-if-the-current-toolkit-does-not","some-zoho-surfaces-may-be-auth-only-or-lack-formal-tools-use-custom-to","use-zoho-get-zoho-records-to-find-a-lead-id-before-converting-a-zoho-l","zoho-auth-config-and-connection-required-fields-can-be-fetched-from-to","zoho-books-bill-tools-exist-but-missing-purchase-order-bill-flows-may","zoho-books-create-estimate-moved-to-the-zoho-invoice-toolkit","zoho-books-list-items-has-no-default-rate-optional-fields-can-be-omitt","zoho-connections-require-the-correct-region-domain-extension","zoho-mail-account-ids-should-be-treated-as-strings-to-avoid-js-safe-in","zoho-mail-messages-send-email-supports-attachments-in-newer-versions","zoho-mail-uses-suffix-one-as-the-connection-initiation-domain-extensio","zoho-mcp-setup-uses-oauth2-and-should-initiate-a-new-connection-from-t","zoho-record-listing-can-require-page-tokens-and-is-subject-to-zoho-rat","zoho-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"`ZOHO_MAIL_MESSAGES_SEND_EMAIL` supports attachments in newer versions"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho connections require the correct region/domain extension"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho Mail uses `suffix.one` as the connection initiation domain-extension field"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho auth config and connection required fields can be fetched from toolkit schema APIs/SDK"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho Books create-estimate moved to the `zoho_invoice` toolkit"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"`ZOHO_BOOKS_LIST_ITEMS` has no default `rate`; optional fields can be omitted"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Use `ZOHO_GET_ZOHO_RECORDS` to find a `lead_id` before converting a Zoho lead"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho record listing can require page tokens and is subject to Zoho rate limits"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho MCP setup uses OAuth2 and should initiate a new connection from the client/dashboard"},{"sourcePath":"toolkits/zoho/public.md","sourceHeading":"Zoho Mail account IDs should be treated as strings to avoid JS safe-integer precision loss"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["zoho"]
11 -aliases: ["/kb/toolkits/zoho-troubleshooting","request-zoho-mail-attachment-download-if-the-current-toolkit-does-not","some-zoho-surfaces-may-be-auth-only-or-lack-formal-tools-use-custom-to","use-zoho-get-zoho-records-to-find-a-lead-id-before-converting-a-zoho-l","zoho-auth-config-and-connection-required-fields-can-be-fetched-from-to","zoho-books-bill-tools-exist-but-missing-purchase-order-bill-flows-may","zoho-books-create-estimate-moved-to-the-zoho-invoice-toolkit","zoho-books-list-items-has-no-default-rate-optional-fields-can-be-omitt","zoho-connections-require-the-correct-region-domain-extension","zoho-mail-account-ids-should-be-treated-as-strings-to-avoid-js-safe-in","zoho-mail-messages-send-email-supports-attachments-in-newer-versions","zoho-mail-uses-suffix-one-as-the-connection-initiation-domain-extensio","zoho-mcp-setup-uses-oauth2-and-should-initiate-a-new-connection-from-t","zoho-record-listing-can-require-page-tokens-and-is-subject-to-zoho-rat","zoho-troubleshooting"]
12 ----
13 -Use this guide to connect Zoho in the correct region, choose current Zoho tools and fields, and handle pagination or large identifiers safely.
14 -
15 -## Connect Zoho in the correct region
16 -
17 -**Pass the account's region as the domain extension.** Zoho requires the correct region/domain extension during connection initiation. Accepted values include `com`, `eu`, `in`, `cn`, and `au`. Pass the customer's Zoho account region, not a full URL, so Composio can build the correct `accounts.zoho.<region>` URL.
18 -
19 -**Use `suffix.one` for the Zoho Mail domain extension.** For Zoho Mail, the expected connection initiation field can appear as `suffix.one`, displayed as Domain Extension. Pass values such as `com`, `eu`, or `in` in `config.val["suffix.one"]` when initiating the connection.
20 -
21 -**Inspect the toolkit schema for required auth and connection fields.** Use `toolkits.get("<toolkit-slug>")` or the toolkit-by-slug API to inspect the full Zoho toolkit schema, including auth config creation fields and connected account initiation fields. This is the reliable way to discover region/domain fields and other required inputs.
22 -
23 -**Initiate a new OAuth2 connection for MCP setups.** Zoho uses OAuth2. For MCP setups, create an MCP config for Zoho, then initiate/connect the Zoho account through the MCP client or dashboard. If the client does not automatically start the OAuth flow, prompting it to initiate a new Zoho connection can help.
24 -
25 -## Choose current Zoho tools and fields
26 -
27 -**Use a current Zoho Mail tool version for attachments.** Attachment support was added to `ZOHO_MAIL_MESSAGES_SEND_EMAIL`. If you cannot send attachments with Zoho Mail, use a current toolkit version and verify the send-email tool schema includes attachment fields.
28 -
29 -**Create estimates through Zoho Invoice.** For creating estimates, use the `zoho_invoice` toolkit action `ZOHO_INVOICE_CREATE_ESTIMATE`; the estimate action is not exposed through the Zoho Books toolkit.
30 -
31 -**Omit optional Zoho Books fields unless they are needed.** `rate` on `ZOHO_BOOKS_LIST_ITEMS` is optional and has no default value in the schema. If an agent sends `rate: 25.5` or another value, that is coming from the model/tool-call generation, not from a Composio schema default. Prompt the model not to pass optional fields unless needed, or call the tool directly with only required arguments.
32 -
33 -**Find the lead before converting it.** For Zoho lead conversion, verify the `lead_id` first. Use `ZOHO_GET_ZOHO_RECORDS` to retrieve the lead record and obtain the correct `lead_id`, then pass that value into the conversion tool.
34 -
35 -## Handle Zoho pagination and identifiers
36 -
37 -**Follow page tokens and provider rate limits.** Zoho list endpoints may return around 200 records per request and require pagination with `page_token` for larger result sets. Multiple tool calls may be needed, and Zoho's own API rate limits can still apply.
38 -
39 -**Treat Zoho Mail account IDs as strings.** Zoho Mail account IDs can exceed JavaScript's safe integer range, so they should be modeled and passed as strings. If a Zoho Mail tool truncates or changes a large account ID, contact Composio support with the redacted payload and log ID so `account_id` can be verified as a string throughout serialization.
docs/content/kb/guide/toolkits-zoom.mdx deleted
-31
@@ -1,31 +0,0 @@
1 ----
2 -title: "Zoom"
3 -description: "Public support knowledge for Zoom."
4 -keywords: ["for-you","platform","zoom","auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers","/kb/toolkits/use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav","/kb/toolkits/zoom-troubleshooting","create-a-new-zoom-auth-config-if-the-default-oauth-app-changed-after-t","use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav","zoom-custom-oauth-apps-may-only-connect-users-in-the-app-owner-s-zoom","zoom-get-a-meeting-summary-needs-the-correct-past-meeting-uuid-and-aut","zoom-oauth-consent-branding-comes-from-the-customer-s-oauth-app","zoom-should-use-the-default-composio-redirect-url-unless-the-auth-guid","zoom-troubleshooting"]
5 -sources: [{"sourcePath":"toolkits/zoom/public.md","sourceHeading":"Zoom custom OAuth apps may only connect users in the app owner's Zoom organization unless configured/approved otherwise"},{"sourcePath":"toolkits/zoom/public.md","sourceHeading":"Zoom should use the default Composio redirect URL unless the auth guide says otherwise"},{"sourcePath":"toolkits/zoom/public.md","sourceHeading":"`ZOOM_GET_A_MEETING_SUMMARY` needs the correct past-meeting UUID and auto summary enabled"},{"sourcePath":"toolkits/zoom/public.md","sourceHeading":"Zoom delete/summary tools may require extra scopes in a custom OAuth app"},{"sourcePath":"toolkits/zoom/public.md","sourceHeading":"Zoom OAuth consent branding comes from the customer's OAuth app"}]
6 -lastVerifiedAt: "2026-08-12"
7 -reviewAfter: "2026-11-10"
8 -freshness: "evergreen"
9 -topics: ["auth-config","authentication","errors-and-troubleshooting","sessions-and-execution","toolkits-and-providers"]
10 -toolkitSlugs: ["zoom"]
11 -aliases: ["/kb/toolkits/use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav","/kb/toolkits/zoom-troubleshooting","create-a-new-zoom-auth-config-if-the-default-oauth-app-changed-after-t","use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav","zoom-custom-oauth-apps-may-only-connect-users-in-the-app-owner-s-zoom","zoom-get-a-meeting-summary-needs-the-correct-past-meeting-uuid-and-aut","zoom-oauth-consent-branding-comes-from-the-customer-s-oauth-app","zoom-should-use-the-default-composio-redirect-url-unless-the-auth-guid","zoom-troubleshooting"]
12 ----
13 -## Zoom custom OAuth apps may only connect users in the app owner's Zoom organization unless configured/approved otherwise
14 -
15 -If you are using your own Zoom OAuth app, verify whether the users you are connecting belong to the same Zoom organization or whether the app is published/approved for external users. An unpublished internal app may only connect users from its own Zoom organization.
16 -
17 -## Zoom should use the default Composio redirect URL unless the auth guide says otherwise
18 -
19 -For Zoom OAuth setup, do not arbitrarily change the redirect URL. Use the default redirect URL/callback shown by Composio or the Zoom auth guide. If auth fails after redirect changes, recreate or update the auth config with the default redirect URL.
20 -
21 -## `ZOOM_GET_A_MEETING_SUMMARY` needs the correct past-meeting UUID and auto summary enabled
22 -
23 -For Zoom meeting summaries, verify that the meeting was created with `settings__auto_start_meeting_summary=true`. Then fetch the correct past-meeting UUID from Zoom's `/v2/past_meetings/{meetingId}/instances` endpoint and use that UUID with `ZOOM_GET_A_MEETING_SUMMARY`; the numeric meeting ID alone may not be sufficient.
24 -
25 -## Zoom delete/summary tools may require extra scopes in a custom OAuth app
26 -
27 -If a Zoom tool fails with a scope or permission issue, check whether the required scope is configured on the customer's Zoom OAuth app. `ZOOM_DELETE_A_MEETING` needs `meeting:write` or `meeting:write:admin`, while fetching past meeting instances or summary UUIDs needs `meeting:read:list_past_instances`.
28 -
29 -## Zoom OAuth consent branding comes from the customer's OAuth app
30 -
31 -For Zoom OAuth branding, use the customer's own Zoom OAuth app. The OAuth consent screen logo/name is picked up from the OAuth app settings rather than from Composio alone.
docs/content/kb/index.mdx deleted
-6
@@ -1,6 +0,0 @@
1 ----
2 -title: "Knowledge Base"
3 -description: "Verified troubleshooting guides and answers for building with Composio."
4 ----
5 -
6 -Verified troubleshooting guides, operational answers, and known-good patterns from Composio support.
docs/content/kb/meta.json deleted
-8
@@ -1,8 +0,0 @@
1 -{
2 - "title": "Knowledge Base",
3 - "root": true,
4 - "pages": [
5 - "index",
6 - "guide"
7 - ]
8 -}
docs/decisions/README.md
+2 -2
@@ -7,8 +7,8 @@ Read these when a docs change touches an existing architecture, generated-data p
7 - `examples.md` - cookbook/examples restructuring plan.
8 - `feedback.md` - feedback collection system.
9 - `llm-guardrails.md` - LLM guardrail injection for markdown endpoints.
10 -- `public-knowledge-base.md` - event-driven public support publication, unified
11 - search, and Composio For You snapshot rules.
10 +- `public-knowledge-base.md` - support-portal KB publication, unified search,
11 + and Composio For You snapshot rules.
12 - `toolkit-page-availability.md` - docs-sync permissions, optional KB isolation,
13 and snapshot-miss toolkit page fallback.
14 - `toolkits.md` - toolkit page data, rendering, and live Instant eligibility filter decisions.
docs/decisions/kb-freshness-verification.md
-9
@@ -49,15 +49,6 @@ guides sharing a review date so the maintenance queue is visible before expiry.
49 | Review window not expired | manifest | error |
50 | Guides sharing one `reviewAfter` date | manifest | warning |
51 | Verification age past threshold | manifest | warning |
52 -| `manifest.source.commit` resolves upstream | GitHub API, `--check-source-pin` | warning |
53 -
54 -The source pin is a provenance claim, not a build dependency: the cited sections
55 -are vendored under `kb/source`, so the site builds whether or not the commit
56 -resolves. An unresolvable pin means no one can audit what a published guide was
57 -derived from, and it blocks source-drift detection, which must diff the vendored
58 -copy against upstream. Resolution distinguishes "missing" from "this token
59 -cannot read that repository" so a narrow token reports nothing rather than
60 -reporting false breakage.
52
53 Three exclusions keep the report trustworthy enough to act on. A permanently red
54 report is one nobody reads.
docs/decisions/public-knowledge-base.md
+23 -21
@@ -4,9 +4,14 @@
4
5 - The public knowledge base is hosted with the documentation at
6 `docs.composio.dev/kb`.
7 -- `ComposioHQ/support-knowledge` is the source of support-specific public prose.
8 -- The docs repository owns the reviewed publication snapshot, routes, search
9 - integration, and presentation.
7 +- The support portal's Front Desk is the only writer of KB guides. It writes
8 + them from public information and person-approved support answers.
9 +- The docs repository owns the published guides (`kb/manifest.json` for
10 + topics, `kb/guides/<slug>.json`, `kb/articles`, `kb/source`), routes, search
11 + integration, and presentation. `content/kb` is generated at build time and
12 + not committed.
13 +- The docs Ask AI agent and `/api/knowledge-search` read the same published
14 + guides; there is no separate agent-only knowledge file.
15 - Product documentation remains canonical for product concepts and workflows;
16 KB guides cover support questions and troubleshooting gaps.
17
@@ -24,19 +29,17 @@
29
30 ## Publication and maintenance
31
27 -- A source change triggers a refresh after it reaches the source repository's
28 - main branch; periodic reconciliation catches missed events.
29 -- The refresh validates the repository, source commit, and mainline ancestry
30 - before importing any content.
31 -- Delayed events resolve to the newest mainline commit that changed public
32 - content. Non-public or repository-maintenance changes do not advance the
33 - published snapshot.
34 -- Refreshes are serialized so overlapping runs cannot race.
35 -- The importer treats upstream files as data, never executes upstream code, and
36 - never writes back to the source repository.
37 -- Import, page generation, search-artifact generation, and validation complete
38 - before an automated refresh pull request is opened.
39 -- A human review and merge remains the final publication gate.
32 +- A proposed guide change reaches the docs repository as a `kb-guide-approved`
33 + dispatch. `docs-kb-publish.yml` applies it with `scripts/publish-kb-guide.ts`
34 + (create, rewrite, or retire), regenerates and validates the KB, and opens a
35 + pull request on `next`. Reviewing and merging that pull request is the
36 + approval; closing it dismisses the change. Nothing merges on its own.
37 +- Each guide lives in its own files, so pull requests for different guides
38 + can wait for review side by side without conflicting.
39 +- A scheduled workflow repairs the semantic artifact when docs or guide changes
40 + reached `next` without a rebuild.
41 +- The ComposioHQ/support-knowledge import was retired in 2026-11; that
42 + repository is no longer a source.
43
44 ## Rendering and discovery
45
@@ -55,9 +58,8 @@
58
59 ## Freshness and safety
60
58 -- The manifest records source provenance, a deterministic content hash,
59 - canonical routes, verification dates, review deadlines, and publication
60 - state.
61 +- The manifest records each guide's sources, canonical routes, verification
62 + dates, review deadlines, and publication state.
63 - Publication rejects content that is not explicitly public, contains known
64 private-data markers, has expired time-sensitive verification, has broken
65 references, or conflicts with an existing route.
@@ -65,8 +67,8 @@
67 - Evergreen review deadlines remain freshness-check errors for follow-up, but
68 do not block the docs build or remove previously reviewed guides. Dates are
69 extended only after review.
68 -- The running docs application reads only the checked-in public snapshot; it
69 - does not access the source repository at runtime.
70 +- The running docs application reads only the checked-in public guides; it
71 + does not call the support portal at runtime.
72
73 ## Failure handling
74
docs/decisions/toolkit-page-availability.md
+3 -4
@@ -27,10 +27,9 @@ toolkit pages.
27
28 The sync failure came from requesting a GitHub App permission that the
29 installation did not grant. Issue tracking does not need the App token because
30 -it only writes to the current repository. The separate token for
31 -`ComposioHQ/support-knowledge` and every step that consumes it are optional and
32 -non-fatal. A failure in that path can reduce KB freshness evidence, but it cannot
33 -block toolkit, OpenAPI, API index, or meta-tool generation.
30 +it only writes to the current repository. The KB freshness check is optional and
31 +non-fatal. A failure there can reduce KB freshness evidence, but it cannot block
32 +toolkit, OpenAPI, API index, or meta-tool generation.
33
34 ## Consequences
35
docs/evals/kb-search-v1.json
-1
@@ -1,5 +1,4 @@
1 {
2 - "sourceCommit": "d57f3d69079ee3819f4136df54512cdf0416cec0",
2 "cases": [
3 {
4 "id": "structural-connect-claude",
docs/kb/guides/consumer-project-boundaries-and-auth-selection.json new
+43
@@ -0,0 +1,43 @@
1 +{
2 + "slug": "consumer-project-boundaries-and-auth-selection",
3 + "title": "Consumer and Developer Project Boundaries",
4 + "description": "Public support knowledge for Consumer and Developer Project Boundaries.",
5 + "articlePath": "consumer-project-boundaries-and-auth-selection.md",
6 + "sources": [
7 + {
8 + "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
9 + "sourceHeading": "Rotate the Connect MCP consumer key"
10 + },
11 + {
12 + "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
13 + "sourceHeading": "Workspace members do not automatically share For You connections"
14 + },
15 + {
16 + "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
17 + "sourceHeading": "Shared connections must be explicitly allowed and pinned"
18 + }
19 + ],
20 + "topics": [
21 + "authentication",
22 + "errors-and-troubleshooting",
23 + "getting-started",
24 + "sessions-and-execution"
25 + ],
26 + "tags": [
27 + "consumer",
28 + "for-you",
29 + "project-boundaries-and-auth-selection"
30 + ],
31 + "aliases": [
32 + "/kb/composio-for-you/workspace-members-do-not-automatically-share-for-you-connections",
33 + "workspace-members-do-not-automatically-share-for-you-connections"
34 + ],
35 + "relatedGuides": [],
36 + "externalResources": [],
37 + "updatedAt": "2026-07-16",
38 + "lastVerifiedAt": "2026-08-17",
39 + "reviewAfter": "2026-11-15",
40 + "freshness": "evergreen",
41 + "state": "published",
42 + "featured": false
43 +}
docs/kb/guides/dashboard-account-deletion.json new
+30
@@ -0,0 +1,30 @@
1 +{
2 + "slug": "dashboard-account-deletion",
3 + "title": "Delete a Composio organization",
4 + "description": "Current self-service path and safety checks for organization deletion.",
5 + "articlePath": "dashboard-account-deletion.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/account-deletion/public.md",
9 + "sourceHeading": "Organization admins can use Delete this organization"
10 + }
11 + ],
12 + "topics": [
13 + "account-and-billing"
14 + ],
15 + "tags": [
16 + "account-deletion",
17 + "dashboard",
18 + "for-you",
19 + "platform"
20 + ],
21 + "aliases": [],
22 + "relatedGuides": [],
23 + "externalResources": [],
24 + "updatedAt": "2026-08-17",
25 + "lastVerifiedAt": "2026-08-17",
26 + "reviewAfter": "2026-11-15",
27 + "freshness": "evergreen",
28 + "state": "published",
29 + "featured": false
30 +}
docs/kb/guides/dashboard-auth-configs-navigation.json new
+39
@@ -0,0 +1,39 @@
1 +{
2 + "slug": "dashboard-auth-configs-navigation",
3 + "title": "Manage Platform auth configs",
4 + "description": "Current dashboard steps for creating and managing Platform auth configs.",
5 + "articlePath": "dashboard-auth-configs-navigation.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/auth-configs-navigation/public.md",
9 + "sourceHeading": "Create an auth config from the selected Platform project"
10 + },
11 + {
12 + "sourcePath": "dashboard/auth-configs-navigation/public.md",
13 + "sourceHeading": "Connect Account on an auth config is a Playground test connection"
14 + },
15 + {
16 + "sourcePath": "dashboard/auth-configs-navigation/public.md",
17 + "sourceHeading": "Manage Config changes future authentication behavior"
18 + }
19 + ],
20 + "topics": [
21 + "auth-config",
22 + "authentication",
23 + "getting-started"
24 + ],
25 + "tags": [
26 + "auth-configs",
27 + "dashboard",
28 + "platform"
29 + ],
30 + "aliases": [],
31 + "relatedGuides": [],
32 + "externalResources": [],
33 + "updatedAt": "2026-08-17",
34 + "lastVerifiedAt": "2026-08-17",
35 + "reviewAfter": "2026-11-15",
36 + "freshness": "evergreen",
37 + "state": "published",
38 + "featured": false
39 +}
docs/kb/guides/dashboard-for-you-navigation.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "dashboard-for-you-navigation",
3 + "title": "Composio For You navigation",
4 + "description": "Current navigation for connecting apps and agents in Composio For You.",
5 + "articlePath": "dashboard-for-you-navigation.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/for-you-navigation/public.md",
9 + "sourceHeading": "Use Connect Apps for provider accounts and Connect my agent for clients"
10 + },
11 + {
12 + "sourcePath": "dashboard/for-you-navigation/public.md",
13 + "sourceHeading": "For You settings include Sessions & API Key"
14 + }
15 + ],
16 + "topics": [
17 + "account-and-billing",
18 + "authentication",
19 + "getting-started"
20 + ],
21 + "tags": [
22 + "dashboard",
23 + "for-you"
24 + ],
25 + "aliases": [],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-08-17",
29 + "lastVerifiedAt": "2026-08-17",
30 + "reviewAfter": "2026-11-15",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/dashboard-log-storage.json new
+35
@@ -0,0 +1,35 @@
1 +{
2 + "slug": "dashboard-log-storage",
3 + "title": "Dashboard Log Storage",
4 + "description": "Public behavior of the project Log storage setting.",
5 + "articlePath": "dashboard-log-storage.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/log-storage/public.md",
9 + "sourceHeading": "“Don't store data” removes new payload content, not the audit row"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "security-and-trust",
15 + "sessions-and-execution"
16 + ],
17 + "tags": [
18 + "dashboard",
19 + "data-retention",
20 + "logs",
21 + "platform"
22 + ],
23 + "aliases": [
24 + "/kb/dashboard-and-projects/don-t-store-data-removes-new-payload-content-not-the-audit-row",
25 + "don-t-store-data-removes-new-payload-content-not-the-audit-row"
26 + ],
27 + "relatedGuides": [],
28 + "externalResources": [],
29 + "updatedAt": "2026-07-16",
30 + "lastVerifiedAt": "2026-08-12",
31 + "reviewAfter": "2026-11-10",
32 + "freshness": "evergreen",
33 + "state": "published",
34 + "featured": false
35 +}
docs/kb/guides/dashboard-login-restrictions.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "dashboard-login-restrictions",
3 + "title": "Dashboard MFA Setup",
4 + "description": "Public guidance for completing dashboard MFA setup.",
5 + "articlePath": "dashboard-login-restrictions.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/login-restrictions/public.md",
9 + "sourceHeading": "Use the manual setup key when QR scanning does not complete"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "security-and-trust"
16 + ],
17 + "tags": [
18 + "login-restrictions",
19 + "platform"
20 + ],
21 + "aliases": [
22 + "/kb/dashboard-and-projects/mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails",
23 + "mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails"
24 + ],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-06-24",
28 + "lastVerifiedAt": "2026-08-17",
29 + "reviewAfter": "2026-11-15",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/dashboard-navigation-overview.json new
+39
@@ -0,0 +1,39 @@
1 +{
2 + "slug": "dashboard-navigation-overview",
3 + "title": "Composio dashboard navigation",
4 + "description": "Current navigation map for Composio Platform and Composio For You.",
5 + "articlePath": "dashboard-navigation-overview.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/navigation-overview/public.md",
9 + "sourceHeading": "Choose Platform for developer projects and For You for personal agent connections"
10 + },
11 + {
12 + "sourcePath": "dashboard/navigation-overview/public.md",
13 + "sourceHeading": "Current Platform project navigation"
14 + },
15 + {
16 + "sourcePath": "dashboard/navigation-overview/public.md",
17 + "sourceHeading": "Organization and project settings are separate"
18 + }
19 + ],
20 + "topics": [
21 + "getting-started",
22 + "workflows"
23 + ],
24 + "tags": [
25 + "dashboard",
26 + "for-you",
27 + "navigation",
28 + "platform"
29 + ],
30 + "aliases": [],
31 + "relatedGuides": [],
32 + "externalResources": [],
33 + "updatedAt": "2026-08-17",
34 + "lastVerifiedAt": "2026-08-17",
35 + "reviewAfter": "2026-11-15",
36 + "freshness": "evergreen",
37 + "state": "published",
38 + "featured": false
39 +}
docs/kb/guides/dashboard-org-members.json new
+41
@@ -0,0 +1,41 @@
1 +{
2 + "slug": "dashboard-org-members",
3 + "title": "Organization Members and Roles",
4 + "description": "What the Admin, Member (Developer), and Viewer roles can do in Composio For You and Platform, and how to transfer organization control.",
5 + "articlePath": "dashboard-org-members.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/org-members/public.md",
9 + "sourceHeading": "What each organization role can do"
10 + },
11 + {
12 + "sourcePath": "dashboard/org-members/public.md",
13 + "sourceHeading": "Transfer organization control to another user"
14 + }
15 + ],
16 + "topics": [
17 + "account-and-billing",
18 + "getting-started"
19 + ],
20 + "tags": [
21 + "dashboard",
22 + "for-you",
23 + "members",
24 + "organizations",
25 + "permissions",
26 + "platform",
27 + "roles"
28 + ],
29 + "aliases": [
30 + "/kb/dashboard-and-projects/transfer-organization-control-to-another-user",
31 + "transfer-organization-control-to-another-user"
32 + ],
33 + "relatedGuides": [],
34 + "externalResources": [],
35 + "updatedAt": "2026-10-13",
36 + "lastVerifiedAt": "2026-10-13",
37 + "reviewAfter": "2026-11-15",
38 + "freshness": "evergreen",
39 + "state": "published",
40 + "featured": false
41 +}
docs/kb/guides/dashboard-project-settings-navigation.json new
+35
@@ -0,0 +1,35 @@
1 +{
2 + "slug": "dashboard-project-settings-navigation",
3 + "title": "Platform project settings",
4 + "description": "Current navigation for Platform project configuration and organization settings.",
5 + "articlePath": "dashboard-project-settings-navigation.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/project-settings-navigation/public.md",
9 + "sourceHeading": "Project settings control one project"
10 + },
11 + {
12 + "sourcePath": "dashboard/project-settings-navigation/public.md",
13 + "sourceHeading": "Organization settings control the organization"
14 + }
15 + ],
16 + "topics": [
17 + "account-and-billing",
18 + "authentication",
19 + "workflows"
20 + ],
21 + "tags": [
22 + "dashboard",
23 + "platform",
24 + "settings"
25 + ],
26 + "aliases": [],
27 + "relatedGuides": [],
28 + "externalResources": [],
29 + "updatedAt": "2026-08-17",
30 + "lastVerifiedAt": "2026-08-17",
31 + "reviewAfter": "2026-11-15",
32 + "freshness": "evergreen",
33 + "state": "published",
34 + "featured": false
35 +}
docs/kb/guides/dashboard-tool-trigger-logs-navigation.json new
+40
@@ -0,0 +1,40 @@
1 +{
2 + "slug": "dashboard-tool-trigger-logs-navigation",
3 + "title": "Debug Platform tools, triggers, users, and sessions",
4 + "description": "Current dashboard paths for inspecting Platform execution state and support identifiers.",
5 + "articlePath": "dashboard-tool-trigger-logs-navigation.md",
6 + "sources": [
7 + {
8 + "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
9 + "sourceHeading": "Use Logs for execution evidence"
10 + },
11 + {
12 + "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
13 + "sourceHeading": "Use Users and Sessions to explain retrieval and execution context"
14 + },
15 + {
16 + "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
17 + "sourceHeading": "Disable a trigger when the goal is to pause it"
18 + }
19 + ],
20 + "topics": [
21 + "errors-and-troubleshooting",
22 + "sessions-and-execution",
23 + "workflows"
24 + ],
25 + "tags": [
26 + "dashboard",
27 + "logs",
28 + "platform",
29 + "triggers"
30 + ],
31 + "aliases": [],
32 + "relatedGuides": [],
33 + "externalResources": [],
34 + "updatedAt": "2026-08-17",
35 + "lastVerifiedAt": "2026-08-17",
36 + "reviewAfter": "2026-11-15",
37 + "freshness": "evergreen",
38 + "state": "published",
39 + "featured": false
40 +}
docs/kb/guides/faqs.json new
+51
@@ -0,0 +1,51 @@
1 +{
2 + "slug": "faqs",
3 + "title": "Current Support FAQs",
4 + "description": "Public answers for recurring Composio support issues.",
5 + "articlePath": "faqs.md",
6 + "sources": [
7 + {
8 + "sourcePath": "faqs/public.md",
9 + "sourceHeading": "Route toolkit requests and toolkit partnership applications"
10 + },
11 + {
12 + "sourcePath": "faqs/public.md",
13 + "sourceHeading": "Security, privacy, data-retention, and compliance information"
14 + },
15 + {
16 + "sourcePath": "faqs/public.md",
17 + "sourceHeading": "Security reporting"
18 + },
19 + {
20 + "sourcePath": "faqs/public.md",
21 + "sourceHeading": "Google `access_not_configured` requires a Workspace for Education administrator"
22 + }
23 + ],
24 + "topics": [
25 + "authentication",
26 + "errors-and-troubleshooting",
27 + "security-and-trust",
28 + "sessions-and-execution",
29 + "toolkits-and-providers"
30 + ],
31 + "tags": [
32 + "faq",
33 + "faqs",
34 + "for-you",
35 + "platform"
36 + ],
37 + "aliases": [
38 + "/kb/sdk-and-api/misc-faqs",
39 + "misc-faqs",
40 + "request-a-missing-toolkit-tool-or-trigger",
41 + "security-privacy-data-retention-and-compliance-information"
42 + ],
43 + "relatedGuides": [],
44 + "externalResources": [],
45 + "updatedAt": "2026-07-14",
46 + "lastVerifiedAt": "2026-08-17",
47 + "reviewAfter": "2026-11-15",
48 + "freshness": "evergreen",
49 + "state": "published",
50 + "featured": false
51 +}
docs/kb/guides/mcp-mcp-hermes.json new
+42
@@ -0,0 +1,42 @@
1 +{
2 + "slug": "mcp-mcp-hermes",
3 + "title": "Hermes MCP",
4 + "description": "Public support knowledge for Hermes MCP.",
5 + "articlePath": "mcp-mcp-hermes.md",
6 + "sources": [
7 + {
8 + "sourcePath": "mcp/mcp-hermes/public.md",
9 + "sourceHeading": "Production MCP API paths and direct transport tests"
10 + },
11 + {
12 + "sourcePath": "mcp/mcp-hermes/public.md",
13 + "sourceHeading": "Auth configs are project-scoped"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "authentication",
19 + "errors-and-troubleshooting",
20 + "getting-started",
21 + "sessions-and-execution"
22 + ],
23 + "tags": [
24 + "for-you",
25 + "mcp",
26 + "mcp-hermes",
27 + "platform"
28 + ],
29 + "aliases": [
30 + "/kb/tool-router-and-mcp/mcp-mcp-hermes",
31 + "auth-configs-are-project-scoped",
32 + "production-mcp-api-paths-and-direct-transport-tests"
33 + ],
34 + "relatedGuides": [],
35 + "externalResources": [],
36 + "updatedAt": "2026-07-16",
37 + "lastVerifiedAt": "2026-11-10",
38 + "reviewAfter": "2027-02-08",
39 + "freshness": "evergreen",
40 + "state": "published",
41 + "featured": false
42 +}
docs/kb/guides/mcp-tool-router-files.json new
+36
@@ -0,0 +1,36 @@
1 +{
2 + "slug": "mcp-tool-router-files",
3 + "title": "Tool Router Files",
4 + "description": "Public guidance for passing Tool Router session files to toolkit actions.",
5 + "articlePath": "mcp-tool-router-files.md",
6 + "sources": [
7 + {
8 + "sourcePath": "mcp/tool-router-files/public.md",
9 + "sourceHeading": "Session paths are not `FileUploadable` storage keys"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution"
15 + ],
16 + "tags": [
17 + "files",
18 + "for-you",
19 + "mcp",
20 + "platform",
21 + "tool-router",
22 + "uploads"
23 + ],
24 + "aliases": [
25 + "/kb/tool-router-and-mcp/use-tool-router-session-files-as-tool-inputs",
26 + "use-tool-router-session-files-as-tool-inputs"
27 + ],
28 + "relatedGuides": [],
29 + "externalResources": [],
30 + "updatedAt": "2026-07-14",
31 + "lastVerifiedAt": "2026-08-12",
32 + "reviewAfter": "2026-11-10",
33 + "freshness": "evergreen",
34 + "state": "published",
35 + "featured": false
36 +}
docs/kb/guides/mcp-tool-router-sessions.json new
+84
@@ -0,0 +1,84 @@
1 +{
2 + "slug": "mcp-tool-router-sessions",
3 + "title": "Tool Router Sessions",
4 + "description": "Public setup guidance for creating and using Tool Router sessions.",
5 + "articlePath": "mcp-tool-router-sessions.md",
6 + "sources": [
7 + {
8 + "sourcePath": "mcp/tool-router-sessions/public.md",
9 + "sourceHeading": "Create Tool Router sessions through the SDK or API"
10 + },
11 + {
12 + "sourcePath": "mcp/tool-router-sessions/public.md",
13 + "sourceHeading": "Session lifetime and deletion"
14 + },
15 + {
16 + "sourcePath": "mcp/tool-router-sessions/public.md",
17 + "sourceHeading": "Select among multiple accounts with an alias or account ID"
18 + },
19 + {
20 + "sourcePath": "mcp/tool-router-sessions/public.md",
21 + "sourceHeading": "The session user must match the connected-account user"
22 + },
23 + {
24 + "sourcePath": "mcp/tool-router-sessions/public.md",
25 + "sourceHeading": "Connected-account selection is live unless pinned"
26 + },
27 + {
28 + "sourcePath": "mcp/tool-router-sessions/public.md",
29 + "sourceHeading": "Toolkit allowlists are enforced before connection lookup"
30 + },
31 + {
32 + "sourcePath": "mcp/tool-router-sessions/public.md",
33 + "sourceHeading": "A fresh task context is a new session runtime, not model memory"
34 + },
35 + {
36 + "sourcePath": "mcp/tool-router-sessions/public.md",
37 + "sourceHeading": "Auth links create project- and user-scoped connected accounts"
38 + },
39 + {
40 + "sourcePath": "mcp/tool-router-sessions/public.md",
41 + "sourceHeading": "Toolkit filters do not preload every matching tool"
42 + },
43 + {
44 + "sourcePath": "mcp/tool-router-sessions/public.md",
45 + "sourceHeading": "SDK custom tools and Custom MCP toolkits have different runtimes"
46 + },
47 + {
48 + "sourcePath": "mcp/tool-router-sessions/public.md",
49 + "sourceHeading": "Enhanced Control requires client support for MCP elicitation"
50 + },
51 + {
52 + "sourcePath": "mcp/tool-router-sessions/public.md",
53 + "sourceHeading": "Pin the intended auth config when a toolkit has multiple auth schemes"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "workflows"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "mcp",
66 + "platform",
67 + "sessions",
68 + "tool-router"
69 + ],
70 + "aliases": [
71 + "/kb/tool-router-and-mcp/mcp-tool-router-sessions",
72 + "choose-a-connected-account-for-a-session",
73 + "tool-router-session-lifetime-and-deletion",
74 + "toolkit-is-not-allowed-for-this-session"
75 + ],
76 + "relatedGuides": [],
77 + "externalResources": [],
78 + "updatedAt": "2026-07-16",
79 + "lastVerifiedAt": "2026-08-17",
80 + "reviewAfter": "2026-11-15",
81 + "freshness": "evergreen",
82 + "state": "published",
83 + "featured": false
84 +}
docs/kb/guides/platform-compliance-data-handling.json new
+53
@@ -0,0 +1,53 @@
1 +{
2 + "slug": "platform-compliance-data-handling",
3 + "title": "Compliance, Data Retention, and Model Training",
4 + "description": "Public guidance for data retention, model training, compliance, and enterprise security reviews.",
5 + "articlePath": "platform-compliance-data-handling.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/compliance-data-handling/public.md",
9 + "sourceHeading": "Canonical public sources"
10 + },
11 + {
12 + "sourcePath": "platform/compliance-data-handling/public.md",
13 + "sourceHeading": "Zero data retention and no-training requirements"
14 + },
15 + {
16 + "sourcePath": "platform/compliance-data-handling/public.md",
17 + "sourceHeading": "Model training"
18 + },
19 + {
20 + "sourcePath": "platform/compliance-data-handling/public.md",
21 + "sourceHeading": "FedRAMP"
22 + },
23 + {
24 + "sourcePath": "platform/compliance-data-handling/public.md",
25 + "sourceHeading": "Third-party providers"
26 + }
27 + ],
28 + "topics": [
29 + "security-and-trust"
30 + ],
31 + "tags": [
32 + "compliance",
33 + "platform",
34 + "privacy",
35 + "retention",
36 + "security"
37 + ],
38 + "aliases": [
39 + "/kb/sdk-and-api/platform-compliance-data-handling",
40 + "canonical-public-sources",
41 + "model-training",
42 + "third-party-providers",
43 + "zero-data-retention-and-no-training-requirements"
44 + ],
45 + "relatedGuides": [],
46 + "externalResources": [],
47 + "updatedAt": "2026-07-24",
48 + "lastVerifiedAt": "2026-08-12",
49 + "reviewAfter": "2026-11-10",
50 + "freshness": "evergreen",
51 + "state": "retired",
52 + "featured": false
53 +}
docs/kb/guides/platform-connected-accounts.json new
+60
@@ -0,0 +1,60 @@
1 +{
2 + "slug": "platform-connected-accounts",
3 + "title": "Connected Accounts",
4 + "description": "Public support knowledge for Connected Accounts.",
5 + "articlePath": "platform-connected-accounts.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/connected-accounts/public.md",
9 + "sourceHeading": "Prefer a new auth link session when a user must reconnect"
10 + },
11 + {
12 + "sourcePath": "platform/connected-accounts/public.md",
13 + "sourceHeading": "Same user ID does not prove same upstream account"
14 + },
15 + {
16 + "sourcePath": "platform/connected-accounts/public.md",
17 + "sourceHeading": "Hosted connect links expire after 10 minutes"
18 + },
19 + {
20 + "sourcePath": "platform/connected-accounts/public.md",
21 + "sourceHeading": "Connection status describes a lifecycle, not credential validity"
22 + },
23 + {
24 + "sourcePath": "platform/connected-accounts/public.md",
25 + "sourceHeading": "OAuth refresh failures have multiple causes"
26 + },
27 + {
28 + "sourcePath": "platform/connected-accounts/public.md",
29 + "sourceHeading": "Provider tokens are redacted from connected-account responses"
30 + },
31 + {
32 + "sourcePath": "platform/connected-accounts/public.md",
33 + "sourceHeading": "Revoke provider credentials before removing a connection when required"
34 + }
35 + ],
36 + "topics": [
37 + "authentication",
38 + "errors-and-troubleshooting"
39 + ],
40 + "tags": [
41 + "connected-accounts",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/sdk-and-api/platform-connected-accounts",
46 + "connection-status-describes-a-lifecycle-not-credential-validity",
47 + "oauth-refresh-failures-have-multiple-causes",
48 + "public-refresh-endpoint-starts-a-new-auth-flow",
49 + "same-user-id-does-not-prove-same-upstream-account",
50 + "token-based-connections-are-not-always-validated-when-stored"
51 + ],
52 + "relatedGuides": [],
53 + "externalResources": [],
54 + "updatedAt": "2026-07-16",
55 + "lastVerifiedAt": "2026-08-17",
56 + "reviewAfter": "2026-11-15",
57 + "freshness": "evergreen",
58 + "state": "published",
59 + "featured": false
60 +}
docs/kb/guides/platform-custom-connection-data-fields.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "platform-custom-connection-data-fields",
3 + "title": "Custom Connection Data Field Names",
4 + "description": "Public support knowledge for Custom Connection Data Field Names.",
5 + "articlePath": "platform-custom-connection-data-fields.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/custom-connection-data-fields/public.md",
9 + "sourceHeading": "Field names are toolkit-specific"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "sessions-and-execution"
16 + ],
17 + "tags": [
18 + "custom-connection-data-fields",
19 + "platform"
20 + ],
21 + "aliases": [
22 + "/kb/authentication/custom-connection-data-fields-are-toolkit-specific",
23 + "custom-connection-data-fields-are-toolkit-specific"
24 + ],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-06-24",
28 + "lastVerifiedAt": "2026-08-12",
29 + "reviewAfter": "2026-11-10",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/platform-file-storage.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "platform-file-storage",
3 + "title": "File Download Storage and Expiry",
4 + "description": "Public guidance for staged files, signed download URLs, retention, and size questions.",
5 + "articlePath": "platform-file-storage.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/file-storage/public.md",
9 + "sourceHeading": "Composio file URLs are short-lived staged downloads"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution"
15 + ],
16 + "tags": [
17 + "files",
18 + "platform",
19 + "signed-urls",
20 + "storage"
21 + ],
22 + "aliases": [
23 + "/kb/sdk-and-api/composio-file-urls-are-short-lived-staged-downloads",
24 + "composio-file-urls-are-short-lived-staged-downloads"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-07-16",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/platform-google-oauth.json new
+37
@@ -0,0 +1,37 @@
1 +{
2 + "slug": "platform-google-oauth",
3 + "title": "Google OAuth setup and consent",
4 + "description": "Shared OAuth setup and consent guidance for Google toolkits.",
5 + "articlePath": "platform-google-oauth.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/google-oauth/public.md",
9 + "sourceHeading": "An unapproved Google OAuth scope can block consent"
10 + },
11 + {
12 + "sourcePath": "platform/google-oauth/public.md",
13 + "sourceHeading": "A customer-owned OAuth app controls the provider consent-screen brand"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "authentication",
19 + "errors-and-troubleshooting",
20 + "toolkits-and-providers"
21 + ],
22 + "tags": [
23 + "for-you",
24 + "google",
25 + "oauth",
26 + "platform"
27 + ],
28 + "aliases": [],
29 + "relatedGuides": [],
30 + "externalResources": [],
31 + "updatedAt": "2026-08-17",
32 + "lastVerifiedAt": "2026-08-17",
33 + "reviewAfter": "2026-11-15",
34 + "freshness": "evergreen",
35 + "state": "published",
36 + "featured": false
37 +}
docs/kb/guides/platform-health-endpoints.json new
+38
@@ -0,0 +1,38 @@
1 +{
2 + "slug": "platform-health-endpoints",
3 + "title": "Platform Health Endpoints",
4 + "description": "Public reference for Composio on-prem and self-hosted health endpoints.",
5 + "articlePath": "platform-health-endpoints.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/health-endpoints/public.md",
9 + "sourceHeading": "Apollo"
10 + },
11 + {
12 + "sourcePath": "platform/health-endpoints/public.md",
13 + "sourceHeading": "Thermos"
14 + }
15 + ],
16 + "topics": [
17 + "errors-and-troubleshooting",
18 + "sessions-and-execution"
19 + ],
20 + "tags": [
21 + "health-endpoints",
22 + "platform"
23 + ],
24 + "aliases": [
25 + "/kb/sdk-and-api/platform-health-endpoints",
26 + "apollo",
27 + "metrics-export",
28 + "thermos"
29 + ],
30 + "relatedGuides": [],
31 + "externalResources": [],
32 + "updatedAt": "2026-06-24",
33 + "lastVerifiedAt": "2026-08-17",
34 + "reviewAfter": "2026-11-15",
35 + "freshness": "evergreen",
36 + "state": "retired",
37 + "featured": false
38 +}
docs/kb/guides/platform-microsoft-oauth.json new
+37
@@ -0,0 +1,37 @@
1 +{
2 + "slug": "platform-microsoft-oauth",
3 + "title": "Microsoft OAuth scopes and tenant consent",
4 + "description": "Shared OAuth scope and tenant-consent guidance for Microsoft toolkits.",
5 + "articlePath": "platform-microsoft-oauth.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/microsoft-oauth/public.md",
9 + "sourceHeading": "Request `offline_access` when a delegated connection needs refresh tokens"
10 + },
11 + {
12 + "sourcePath": "platform/microsoft-oauth/public.md",
13 + "sourceHeading": "Some Microsoft tenant policies and permissions require administrator consent"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "authentication",
19 + "errors-and-troubleshooting",
20 + "toolkits-and-providers"
21 + ],
22 + "tags": [
23 + "for-you",
24 + "microsoft",
25 + "oauth",
26 + "platform"
27 + ],
28 + "aliases": [],
29 + "relatedGuides": [],
30 + "externalResources": [],
31 + "updatedAt": "2026-08-17",
32 + "lastVerifiedAt": "2026-08-17",
33 + "reviewAfter": "2026-11-15",
34 + "freshness": "evergreen",
35 + "state": "published",
36 + "featured": false
37 +}
docs/kb/guides/platform-pagination.json new
+41
@@ -0,0 +1,41 @@
1 +{
2 + "slug": "platform-pagination",
3 + "title": "Platform Pagination",
4 + "description": "Public guidance for endpoint-specific list limits and cursor pagination.",
5 + "articlePath": "platform-pagination.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/pagination/public.md",
9 + "sourceHeading": "Pagination limits are endpoint-specific"
10 + },
11 + {
12 + "sourcePath": "platform/pagination/public.md",
13 + "sourceHeading": "Auth-config list pages return at most 50 items"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "errors-and-troubleshooting",
19 + "sessions-and-execution"
20 + ],
21 + "tags": [
22 + "api",
23 + "cursors",
24 + "pagination",
25 + "platform"
26 + ],
27 + "aliases": [
28 + "/kb/authentication/auth-config-list-pages-return-at-most-50-items",
29 + "/kb/sdk-and-api/pagination-limits-are-endpoint-specific",
30 + "auth-config-list-pages-return-at-most-50-items",
31 + "pagination-limits-are-endpoint-specific"
32 + ],
33 + "relatedGuides": [],
34 + "externalResources": [],
35 + "updatedAt": "2026-07-16",
36 + "lastVerifiedAt": "2026-08-12",
37 + "reviewAfter": "2026-11-10",
38 + "freshness": "evergreen",
39 + "state": "published",
40 + "featured": false
41 +}
docs/kb/guides/platform-production-readiness.json new
+58
@@ -0,0 +1,58 @@
1 +{
2 + "slug": "platform-production-readiness",
3 + "title": "Move a Composio Integration from Prototype to Production",
4 + "description": "Public guidance for production user identity, environment isolation, authentication, sessions, and trigger delivery.",
5 + "articlePath": "platform-production-readiness.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/production-readiness/public.md",
9 + "sourceHeading": "Replace example user IDs with stable application user IDs"
10 + },
11 + {
12 + "sourcePath": "platform/production-readiness/public.md",
13 + "sourceHeading": "Isolate environments with separate Composio projects when needed"
14 + },
15 + {
16 + "sourcePath": "platform/production-readiness/public.md",
17 + "sourceHeading": "Use managed auth in production, and your own OAuth app when you need dedicated limits"
18 + },
19 + {
20 + "sourcePath": "platform/production-readiness/public.md",
21 + "sourceHeading": "Restrict the production session to the capabilities the agent needs"
22 + },
23 + {
24 + "sourcePath": "platform/production-readiness/public.md",
25 + "sourceHeading": "Reuse a stored session until the user or configuration changes"
26 + },
27 + {
28 + "sourcePath": "platform/production-readiness/public.md",
29 + "sourceHeading": "Test production trigger handling through the real webhook path"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "getting-started",
36 + "security-and-trust",
37 + "sessions-and-execution",
38 + "workflows"
39 + ],
40 + "tags": [
41 + "authentication",
42 + "deployment",
43 + "platform",
44 + "production",
45 + "projects",
46 + "sessions",
47 + "users"
48 + ],
49 + "aliases": [],
50 + "relatedGuides": [],
51 + "externalResources": [],
52 + "updatedAt": "2026-08-24",
53 + "lastVerifiedAt": "2026-08-24",
54 + "reviewAfter": "2026-11-22",
55 + "freshness": "evergreen",
56 + "state": "published",
57 + "featured": false
58 +}
docs/kb/guides/platform-project-api-key-permissions.json new
+45
@@ -0,0 +1,45 @@
1 +{
2 + "slug": "platform-project-api-key-permissions",
3 + "title": "Project API Key Permissions",
4 + "description": "Public guidance for scoped Project API key permissions.",
5 + "articlePath": "platform-project-api-key-permissions.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/project-api-key-permissions/public.md",
9 + "sourceHeading": "Proxy Execute requires an explicitly allowed Project API key"
10 + },
11 + {
12 + "sourcePath": "platform/project-api-key-permissions/public.md",
13 + "sourceHeading": "Tool Router session creation requires Sessions write access"
14 + },
15 + {
16 + "sourcePath": "platform/project-api-key-permissions/public.md",
17 + "sourceHeading": "Tool execution requires Tool execution write access"
18 + }
19 + ],
20 + "topics": [
21 + "authentication",
22 + "errors-and-troubleshooting",
23 + "sessions-and-execution"
24 + ],
25 + "tags": [
26 + "api-keys",
27 + "permissions",
28 + "platform",
29 + "sessions",
30 + "tool-router"
31 + ],
32 + "aliases": [
33 + "/kb/sdk-and-api/platform-project-api-key-permissions",
34 + "org-api-created-keys-do-not-currently-enable-proxy-execute",
35 + "tool-router-session-creation-requires-sessions-write-access"
36 + ],
37 + "relatedGuides": [],
38 + "externalResources": [],
39 + "updatedAt": "2026-08-28",
40 + "lastVerifiedAt": "2026-08-28",
41 + "reviewAfter": "2026-11-26",
42 + "freshness": "evergreen",
43 + "state": "published",
44 + "featured": false
45 +}
docs/kb/guides/platform-rate-limits.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "platform-rate-limits",
3 + "title": "Platform API Rate Limits",
4 + "description": "Public guidance for organization-level Composio API limits and 429 handling.",
5 + "articlePath": "platform-rate-limits.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/rate-limits/public.md",
9 + "sourceHeading": "Organization API limits and 429 handling"
10 + }
11 + ],
12 + "topics": [
13 + "account-and-billing",
14 + "errors-and-troubleshooting",
15 + "sessions-and-execution"
16 + ],
17 + "tags": [
18 + "api",
19 + "billing",
20 + "platform",
21 + "rate-limits"
22 + ],
23 + "aliases": [],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-07-16",
27 + "lastVerifiedAt": "2026-08-12",
28 + "reviewAfter": "2026-11-10",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/platform-routing.json new
+43
@@ -0,0 +1,43 @@
1 +{
2 + "slug": "platform-routing",
3 + "title": "Support Routing",
4 + "description": "Public routing for hiring, compliance, and toolkit feature requests.",
5 + "articlePath": "platform-routing.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/routing/public.md",
9 + "sourceHeading": "Hiring"
10 + },
11 + {
12 + "sourcePath": "platform/routing/public.md",
13 + "sourceHeading": "DPA, enterprise data handling, and compliance"
14 + },
15 + {
16 + "sourcePath": "platform/routing/public.md",
17 + "sourceHeading": "Tool or toolkit feature requests"
18 + }
19 + ],
20 + "topics": [
21 + "getting-started",
22 + "security-and-trust",
23 + "toolkits-and-providers"
24 + ],
25 + "tags": [
26 + "compliance",
27 + "platform",
28 + "requests",
29 + "routing"
30 + ],
31 + "aliases": [
32 + "/kb/sdk-and-api/dpa-enterprise-data-handling-and-compliance",
33 + "dpa-enterprise-data-handling-and-compliance"
34 + ],
35 + "relatedGuides": [],
36 + "externalResources": [],
37 + "updatedAt": "2026-07-24",
38 + "lastVerifiedAt": "2026-08-17",
39 + "reviewAfter": "2026-11-15",
40 + "freshness": "evergreen",
41 + "state": "published",
42 + "featured": false
43 +}
docs/kb/guides/platform-self-hosted-helm.json new
+38
@@ -0,0 +1,38 @@
1 +{
2 + "slug": "platform-self-hosted-helm",
3 + "title": "Self-hosted Helm",
4 + "description": "Public support knowledge for Self-hosted Helm.",
5 + "articlePath": "platform-self-hosted-helm.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/self-hosted-helm/public.md",
9 + "sourceHeading": "Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys"
10 + },
11 + {
12 + "sourcePath": "platform/self-hosted-helm/public.md",
13 + "sourceHeading": "Disable social login explicitly for self-hosted deployments"
14 + }
15 + ],
16 + "topics": [
17 + "authentication",
18 + "errors-and-troubleshooting",
19 + "getting-started"
20 + ],
21 + "tags": [
22 + "platform",
23 + "self-hosted-helm"
24 + ],
25 + "aliases": [
26 + "/kb/sdk-and-api/platform-self-hosted-helm",
27 + "apollo-s3-with-irsa-serviceaccount-credentials-needs-no-static-s3-secr",
28 + "disable-social-login-explicitly-for-self-hosted-deployments"
29 + ],
30 + "relatedGuides": [],
31 + "externalResources": [],
32 + "updatedAt": "2026-06-24",
33 + "lastVerifiedAt": "2026-08-12",
34 + "reviewAfter": "2026-11-10",
35 + "freshness": "evergreen",
36 + "state": "published",
37 + "featured": false
38 +}
docs/kb/guides/platform-session-tool-policies.json new
+50
@@ -0,0 +1,50 @@
1 +{
2 + "slug": "platform-session-tool-policies",
3 + "title": "Create Read-Only and Restricted Composio Sessions",
4 + "description": "Public guidance for limiting session tool access with tags, exact tool allowlists, OAuth scopes, and sandbox controls.",
5 + "articlePath": "platform-session-tool-policies.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/session-tool-policies/public.md",
9 + "sourceHeading": "Filter a broad read-only session with behavior tags"
10 + },
11 + {
12 + "sourcePath": "platform/session-tool-policies/public.md",
13 + "sourceHeading": "Use exact tool allowlists for the narrowest policy"
14 + },
15 + {
16 + "sourcePath": "platform/session-tool-policies/public.md",
17 + "sourceHeading": "Combine provider scopes with session tool restrictions"
18 + },
19 + {
20 + "sourcePath": "platform/session-tool-policies/public.md",
21 + "sourceHeading": "Apply toolkit-specific exceptions without widening every toolkit"
22 + },
23 + {
24 + "sourcePath": "platform/session-tool-policies/public.md",
25 + "sourceHeading": "Disable the session sandbox when the workflow does not need code execution"
26 + }
27 + ],
28 + "topics": [
29 + "authentication",
30 + "security-and-trust",
31 + "sessions-and-execution"
32 + ],
33 + "tags": [
34 + "least-privilege",
35 + "oauth-scopes",
36 + "platform",
37 + "read-only",
38 + "sessions",
39 + "tool-policy"
40 + ],
41 + "aliases": [],
42 + "relatedGuides": [],
43 + "externalResources": [],
44 + "updatedAt": "2026-08-24",
45 + "lastVerifiedAt": "2026-08-24",
46 + "reviewAfter": "2026-11-22",
47 + "freshness": "evergreen",
48 + "state": "published",
49 + "featured": false
50 +}
docs/kb/guides/platform-tool-router-workbench.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "platform-tool-router-workbench",
3 + "title": "Tool Router Workbench Retention",
4 + "description": "Public support knowledge for Tool Router Workbench Retention.",
5 + "articlePath": "platform-tool-router-workbench.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/tool-router-workbench/public.md",
9 + "sourceHeading": "A “fresh” client label can still reuse the same sandbox"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution"
15 + ],
16 + "tags": [
17 + "platform",
18 + "tool-router-workbench"
19 + ],
20 + "aliases": [
21 + "/kb/sdk-and-api/a-fresh-client-label-can-still-reuse-the-same-sandbox",
22 + "a-fresh-client-label-can-still-reuse-the-same-sandbox"
23 + ],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-07-16",
27 + "lastVerifiedAt": "2026-08-17",
28 + "reviewAfter": "2026-11-15",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/platform-triggers.json new
+41
@@ -0,0 +1,41 @@
1 +{
2 + "slug": "platform-triggers",
3 + "title": "Triggers",
4 + "description": "Public trigger catalog and webhook delivery guidance.",
5 + "articlePath": "platform-triggers.md",
6 + "sources": [
7 + {
8 + "sourcePath": "platform/triggers/public.md",
9 + "sourceHeading": "Find every toolkit that currently supports triggers"
10 + },
11 + {
12 + "sourcePath": "platform/triggers/public.md",
13 + "sourceHeading": "Trigger webhook delivery is at-least-once"
14 + }
15 + ],
16 + "topics": [
17 + "errors-and-troubleshooting",
18 + "sessions-and-execution",
19 + "workflows"
20 + ],
21 + "tags": [
22 + "catalog",
23 + "platform",
24 + "retries",
25 + "triggers",
26 + "webhooks"
27 + ],
28 + "aliases": [
29 + "/kb/triggers-and-webhooks/platform-triggers",
30 + "deduplicate-trigger-webhook-deliveries",
31 + "find-every-toolkit-that-currently-supports-triggers"
32 + ],
33 + "relatedGuides": [],
34 + "externalResources": [],
35 + "updatedAt": "2026-07-14",
36 + "lastVerifiedAt": "2026-08-12",
37 + "reviewAfter": "2026-11-10",
38 + "freshness": "evergreen",
39 + "state": "published",
40 + "featured": false
41 +}
docs/kb/guides/sdk-tool-execution-retries.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "sdk-tool-execution-retries",
3 + "title": "Tool Execution Retries",
4 + "description": "Public support knowledge for Tool Execution Retries.",
5 + "articlePath": "sdk-tool-execution-retries.md",
6 + "sources": [
7 + {
8 + "sourcePath": "sdk/tool-execution-retries/public.md",
9 + "sourceHeading": "Current SDKs do not automatically retry non-idempotent tool executions"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution"
15 + ],
16 + "tags": [
17 + "platform",
18 + "sdk",
19 + "tool-execution-retries"
20 + ],
21 + "aliases": [
22 + "/kb/sdk-and-api/tool-execution-timeouts-can-retry-non-idempotent-actions",
23 + "tool-execution-timeouts-can-retry-non-idempotent-actions"
24 + ],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-06-24",
28 + "lastVerifiedAt": "2026-08-12",
29 + "reviewAfter": "2026-11-10",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/sdk-tool-schemas.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "sdk-tool-schemas",
3 + "title": "TypeScript Tool Schema Definitions",
4 + "description": "Public guidance for dangling JSON Schema references in older TypeScript SDK versions.",
5 + "articlePath": "sdk-tool-schemas.md",
6 + "sources": [
7 + {
8 + "sourcePath": "sdk/tool-schemas/public.md",
9 + "sourceHeading": "Upgrade when `$ref` is present but root `$defs` is missing"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution"
15 + ],
16 + "tags": [
17 + "json-schema",
18 + "platform",
19 + "sdk",
20 + "typescript"
21 + ],
22 + "aliases": [
23 + "/kb/sdk-and-api/upgrade-when-ref-is-present-but-root-defs-is-missing",
24 + "upgrade-when-ref-is-present-but-root-defs-is-missing"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-07-16",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-ahrefs.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "toolkits-ahrefs",
3 + "title": "Ahrefs",
4 + "description": "Public support knowledge for Ahrefs.",
5 + "articlePath": "toolkits-ahrefs.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/ahrefs/public.md",
9 + "sourceHeading": "Ahrefs actions must call api.ahrefs.com, not ahrefs.com"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "ahrefs",
19 + "for-you",
20 + "platform"
21 + ],
22 + "aliases": [
23 + "/kb/toolkits/ahrefs-actions-use-the-api-host",
24 + "ahrefs-actions-use-the-api-host"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-06-24",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-airtable.json new
+62
@@ -0,0 +1,62 @@
1 +{
2 + "slug": "toolkits-airtable",
3 + "title": "Airtable",
4 + "description": "Public support knowledge for Airtable.",
5 + "articlePath": "toolkits-airtable.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/airtable/public.md",
9 + "sourceHeading": "Connect Airtable to Claude using MCP"
10 + },
11 + {
12 + "sourcePath": "toolkits/airtable/public.md",
13 + "sourceHeading": "Use custom Airtable OAuth credentials for additional scopes"
14 + },
15 + {
16 + "sourcePath": "toolkits/airtable/public.md",
17 + "sourceHeading": "Connection initiation timeout after 10 minutes is not Airtable-specific"
18 + },
19 + {
20 + "sourcePath": "toolkits/airtable/public.md",
21 + "sourceHeading": "Missing Airtable tools may be caused by list limits or an older toolkit version"
22 + },
23 + {
24 + "sourcePath": "toolkits/airtable/public.md",
25 + "sourceHeading": "AIRTABLE_UPDATE_MULTIPLE_RECORDS updates at most 10 records per call"
26 + },
27 + {
28 + "sourcePath": "toolkits/airtable/public.md",
29 + "sourceHeading": "Use one of the current Airtable metadata triggers"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "airtable",
41 + "for-you",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/airtable-troubleshooting",
46 + "airtable-triggers-and-webhooks-were-not-yet-generally-available",
47 + "airtable-troubleshooting",
48 + "batch-airtable-record-updates-in-groups-of-10",
49 + "connect-airtable-to-claude-using-mcp",
50 + "connection-initiation-timeout-after-10-minutes-is-not-airtable-specifi",
51 + "missing-airtable-tools-may-be-caused-by-default-list-limits-or-ts-sdk",
52 + "use-custom-airtable-oauth-credentials-for-additional-scopes"
53 + ],
54 + "relatedGuides": [],
55 + "externalResources": [],
56 + "updatedAt": "2026-06-24",
57 + "lastVerifiedAt": "2026-08-17",
58 + "reviewAfter": "2026-11-15",
59 + "freshness": "evergreen",
60 + "state": "published",
61 + "featured": false
62 +}
docs/kb/guides/toolkits-apollo.json new
+47
@@ -0,0 +1,47 @@
1 +{
2 + "slug": "toolkits-apollo",
3 + "title": "Apollo",
4 + "description": "Public support knowledge for Apollo.",
5 + "articlePath": "toolkits-apollo.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/apollo/public.md",
9 + "sourceHeading": "Apollo 403s on search/enrichment endpoints can be key-permission or plan-access gated"
10 + },
11 + {
12 + "sourcePath": "toolkits/apollo/public.md",
13 + "sourceHeading": "Apollo people enrichment and bulk enrichment can behave differently"
14 + },
15 + {
16 + "sourcePath": "toolkits/apollo/public.md",
17 + "sourceHeading": "Apollo search results may mirror Apollo's official API behavior"
18 + }
19 + ],
20 + "topics": [
21 + "authentication",
22 + "errors-and-troubleshooting",
23 + "sessions-and-execution",
24 + "toolkits-and-providers"
25 + ],
26 + "tags": [
27 + "apollo",
28 + "for-you",
29 + "platform"
30 + ],
31 + "aliases": [
32 + "/kb/toolkits/apollo-tools-have-had-missing-or-incorrect-request-schema-parameters",
33 + "/kb/toolkits/apollo-troubleshooting",
34 + "apollo-people-enrichment-and-bulk-enrichment-can-behave-differently",
35 + "apollo-search-results-may-mirror-apollo-s-official-api-behavior",
36 + "apollo-tools-have-had-missing-or-incorrect-request-schema-parameters",
37 + "apollo-troubleshooting"
38 + ],
39 + "relatedGuides": [],
40 + "externalResources": [],
41 + "updatedAt": "2026-06-24",
42 + "lastVerifiedAt": "2026-08-12",
43 + "reviewAfter": "2026-11-10",
44 + "freshness": "evergreen",
45 + "state": "published",
46 + "featured": false
47 +}
docs/kb/guides/toolkits-asana.json new
+43
@@ -0,0 +1,43 @@
1 +{
2 + "slug": "toolkits-asana",
3 + "title": "Asana",
4 + "description": "Public support knowledge for Asana.",
5 + "articlePath": "toolkits-asana.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/asana/public.md",
9 + "sourceHeading": "Use `ASANA_GET_STORIES_FOR_TASK` and pass the task ID as a string"
10 + },
11 + {
12 + "sourcePath": "toolkits/asana/public.md",
13 + "sourceHeading": "Use the current Asana task triggers"
14 + }
15 + ],
16 + "topics": [
17 + "authentication",
18 + "sessions-and-execution",
19 + "toolkits-and-providers"
20 + ],
21 + "tags": [
22 + "asana",
23 + "for-you",
24 + "platform"
25 + ],
26 + "aliases": [
27 + "/kb/toolkits/asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava",
28 + "/kb/toolkits/asana-troubleshooting",
29 + "asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava",
30 + "asana-troubleshooting",
31 + "deleted-asana-auth-configs-can-block-mcp-config-edits-create-a-new-mcp",
32 + "older-sdk-connection-initiation-may-require-appname-integrationid-enti",
33 + "verify-current-production-availability-before-using-asana-triggers"
34 + ],
35 + "relatedGuides": [],
36 + "externalResources": [],
37 + "updatedAt": "2026-06-24",
38 + "lastVerifiedAt": "2026-08-12",
39 + "reviewAfter": "2026-11-10",
40 + "freshness": "evergreen",
41 + "state": "published",
42 + "featured": false
43 +}
docs/kb/guides/toolkits-attio.json new
+54
@@ -0,0 +1,54 @@
1 +{
2 + "slug": "toolkits-attio",
3 + "title": "Attio",
4 + "description": "Public support knowledge for Attio.",
5 + "articlePath": "toolkits-attio.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/attio/public.md",
9 + "sourceHeading": "Use $contains for partial text matching in ATTIO_FIND_RECORD filters"
10 + },
11 + {
12 + "sourcePath": "toolkits/attio/public.md",
13 + "sourceHeading": "Use custom tools when an Attio API object is not built into Composio yet"
14 + },
15 + {
16 + "sourcePath": "toolkits/attio/public.md",
17 + "sourceHeading": "Top-level $ parameter names were fixed for LLM provider compatibility in the latest schema version"
18 + },
19 + {
20 + "sourcePath": "toolkits/attio/public.md",
21 + "sourceHeading": "Attio toolkit defaults can stay on the base pinned version unless a version is explicitly selected"
22 + }
23 + ],
24 + "topics": [
25 + "authentication",
26 + "errors-and-troubleshooting",
27 + "sessions-and-execution",
28 + "toolkits-and-providers"
29 + ],
30 + "tags": [
31 + "attio",
32 + "for-you",
33 + "platform"
34 + ],
35 + "aliases": [
36 + "/kb/toolkits/attio-troubleshooting",
37 + "attio-meeting-and-call-recording-get-by-id-endpoints-were-a-feature-re",
38 + "attio-oauth-tokens-cannot-be-programmatically-revoked-by-composio",
39 + "attio-toolkit-defaults-can-stay-on-the-base-pinned-version-unless-a-ve",
40 + "attio-troubleshooting",
41 + "auth-config-names-can-carry-a-reference-id-but-custom-auth-config-meta",
42 + "missing-attio-scopes-on-composio-managed-auth-require-confirming-the-a",
43 + "use-contains-for-partial-text-matching-in-attio-find-record-filters",
44 + "use-custom-tools-when-an-attio-api-object-is-not-built-into-composio-y"
45 + ],
46 + "relatedGuides": [],
47 + "externalResources": [],
48 + "updatedAt": "2026-06-24",
49 + "lastVerifiedAt": "2026-08-12",
50 + "reviewAfter": "2026-11-10",
51 + "freshness": "evergreen",
52 + "state": "published",
53 + "featured": false
54 +}
docs/kb/guides/toolkits-browser-tool.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "toolkits-browser-tool",
3 + "title": "Browser Tool",
4 + "description": "Public support knowledge for Browser Tool.",
5 + "articlePath": "toolkits-browser-tool.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/browser_tool/public.md",
9 + "sourceHeading": "Browser Tool profiles do not work in Zero Data Retention projects"
10 + }
11 + ],
12 + "topics": [
13 + "security-and-trust",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "browser_tool",
19 + "for-you",
20 + "platform"
21 + ],
22 + "aliases": [
23 + "/kb/toolkits/browser-tool-profiles-do-not-work-in-zero-data-retention-projects",
24 + "browser-tool-profiles-do-not-work-in-zero-data-retention-projects"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-06-24",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-calendly.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "toolkits-calendly",
3 + "title": "Calendly",
4 + "description": "Public support knowledge for Calendly.",
5 + "articlePath": "toolkits-calendly.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/calendly/public.md",
9 + "sourceHeading": "Use CALENDLY_POST_INVITEE instead of deprecated CALENDLY_CREATE_EVENT_INVITEE"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "toolkits-and-providers"
15 + ],
16 + "tags": [
17 + "calendly",
18 + "for-you",
19 + "platform"
20 + ],
21 + "aliases": [
22 + "/kb/toolkits/use-calendly-post-invitee",
23 + "use-calendly-post-invitee"
24 + ],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-06-24",
28 + "lastVerifiedAt": "2026-08-12",
29 + "reviewAfter": "2026-11-10",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/toolkits-canva.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "toolkits-canva",
3 + "title": "Canva",
4 + "description": "Public support knowledge for Canva.",
5 + "articlePath": "toolkits-canva.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/canva/public.md",
9 + "sourceHeading": "Use Canva autofill jobs when content must be populated into a design"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "canva",
19 + "for-you",
20 + "platform"
21 + ],
22 + "aliases": [
23 + "/kb/toolkits/use-canva-autofill-jobs-for-design-content",
24 + "use-canva-autofill-jobs-for-design-content"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-06-24",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-canvas.json new
+99
@@ -0,0 +1,99 @@
1 +{
2 + "slug": "toolkits-canvas",
3 + "title": "Canvas",
4 + "description": "Public support knowledge for Canvas.",
5 + "articlePath": "toolkits-canvas.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/canvas/public.md",
9 + "sourceHeading": "Canvas triggers are available, and course selection can be driven from course IDs"
10 + },
11 + {
12 + "sourcePath": "toolkits/canvas/public.md",
13 + "sourceHeading": "Canvas triggers fire for users visible to the connected bearer-token user"
14 + },
15 + {
16 + "sourcePath": "toolkits/canvas/public.md",
17 + "sourceHeading": "Canvas Assignment Graded trigger is expected to work for Teacher accounts, not Student accounts"
18 + },
19 + {
20 + "sourcePath": "toolkits/canvas/public.md",
21 + "sourceHeading": "Canvas trigger payloads expose Canvas user ID separately as `canvas_user_id`"
22 + },
23 + {
24 + "sourcePath": "toolkits/canvas/public.md",
25 + "sourceHeading": "Canvas action 401/unauthorized errors can be caused by missing action-level scopes"
26 + },
27 + {
28 + "sourcePath": "toolkits/canvas/public.md",
29 + "sourceHeading": "Canvas OAuth credentials must match the configured Canvas base URL"
30 + },
31 + {
32 + "sourcePath": "toolkits/canvas/public.md",
33 + "sourceHeading": "Canvas account-level endpoints require admin permissions"
34 + },
35 + {
36 + "sourcePath": "toolkits/canvas/public.md",
37 + "sourceHeading": "`CANVAS_CREATE_CALENDAR_EVENT` can use a user ID, and Canvas API field names are preserved"
38 + },
39 + {
40 + "sourcePath": "toolkits/canvas/public.md",
41 + "sourceHeading": "Canvas list/fetch endpoints follow Canvas pagination behavior and may need `per_page`"
42 + },
43 + {
44 + "sourcePath": "toolkits/canvas/public.md",
45 + "sourceHeading": "Canvas discussion topics and announcements require `only_announcements` selection"
46 + },
47 + {
48 + "sourcePath": "toolkits/canvas/public.md",
49 + "sourceHeading": "Canvas 404s on course analytics usually mean the course or endpoint is unavailable"
50 + },
51 + {
52 + "sourcePath": "toolkits/canvas/public.md",
53 + "sourceHeading": "Canvas quiz matching question answers use unprefixed answer field keys"
54 + },
55 + {
56 + "sourcePath": "toolkits/canvas/public.md",
57 + "sourceHeading": "Older Canvas toolkit versions cannot be patched in place"
58 + }
59 + ],
60 + "topics": [
61 + "auth-config",
62 + "authentication",
63 + "errors-and-troubleshooting",
64 + "sessions-and-execution",
65 + "toolkits-and-providers"
66 + ],
67 + "tags": [
68 + "canvas",
69 + "for-you",
70 + "platform"
71 + ],
72 + "aliases": [
73 + "/kb/toolkits/canvas-troubleshooting",
74 + "canvas-404s-on-course-analytics-usually-mean-the-course-or-endpoint-is",
75 + "canvas-assignment-graded-trigger-is-expected-to-work-for-teacher-accou",
76 + "canvas-create-calendar-event-can-use-a-user-id-and-canvas-api-field-na",
77 + "canvas-discussion-topics-and-announcements-require-only-announcements",
78 + "canvas-does-not-expose-webhooks-for-every-requested-trigger-use-case",
79 + "canvas-oauth-credentials-must-match-the-configured-canvas-base-url",
80 + "canvas-quiz-matching-question-answers-use-unprefixed-answer-field-keys",
81 + "canvas-response-schemas-are-being-standardized-gradually-not-universal",
82 + "canvas-trigger-payloads-expose-canvas-user-id-separately-as-canvas-use",
83 + "canvas-triggers-are-available-and-course-selection-can-be-driven-from",
84 + "canvas-troubleshooting",
85 + "older-canvas-toolkit-versions-cannot-be-patched-in-place",
86 + "paginate-canvas-list-results",
87 + "resolve-canvas-account-endpoint-access-errors",
88 + "toolkit-versioning-does-not-version-canvas-trigger-logic",
89 + "use-shorter-polling-intervals-for-canvas-triggers-when-longer-interval"
90 + ],
91 + "relatedGuides": [],
92 + "externalResources": [],
93 + "updatedAt": "2026-06-24",
94 + "lastVerifiedAt": "2026-08-17",
95 + "reviewAfter": "2026-11-15",
96 + "freshness": "evergreen",
97 + "state": "published",
98 + "featured": false
99 +}
docs/kb/guides/toolkits-clickup.json new
+49
@@ -0,0 +1,49 @@
1 +{
2 + "slug": "toolkits-clickup",
3 + "title": "ClickUp",
4 + "description": "Public support knowledge for ClickUp.",
5 + "articlePath": "toolkits-clickup.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/clickup/public.md",
9 + "sourceHeading": "ClickUp supports managed OAuth, custom OAuth, and API-key credentials"
10 + },
11 + {
12 + "sourcePath": "toolkits/clickup/public.md",
13 + "sourceHeading": "ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app"
14 + },
15 + {
16 + "sourcePath": "toolkits/clickup/public.md",
17 + "sourceHeading": "ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`"
18 + }
19 + ],
20 + "topics": [
21 + "auth-config",
22 + "authentication",
23 + "errors-and-troubleshooting",
24 + "sessions-and-execution",
25 + "toolkits-and-providers"
26 + ],
27 + "tags": [
28 + "clickup",
29 + "for-you",
30 + "platform"
31 + ],
32 + "aliases": [
33 + "/kb/toolkits/clickup-troubleshooting",
34 + "clickup-custom-oauth-should-use-the-composio-callback-url-registered-i",
35 + "clickup-folders-and-tasks-are-supported-through-clickup-get-folders-an",
36 + "clickup-supports-default-auth-or-customer-owned-credentials-when-creat",
37 + "clickup-tokens-may-require-manual-provider-side-removal-if-programmati",
38 + "clickup-troubleshooting",
39 + "cursor-may-fail-when-too-many-mcp-servers-are-configured-keep-clickup"
40 + ],
41 + "relatedGuides": [],
42 + "externalResources": [],
43 + "updatedAt": "2026-06-24",
44 + "lastVerifiedAt": "2026-08-24",
45 + "reviewAfter": "2026-11-22",
46 + "freshness": "evergreen",
47 + "state": "published",
48 + "featured": false
49 +}
docs/kb/guides/toolkits-confluence.json new
+69
@@ -0,0 +1,69 @@
1 +{
2 + "slug": "toolkits-confluence",
3 + "title": "Confluence",
4 + "description": "Public support knowledge for Confluence.",
5 + "articlePath": "toolkits-confluence.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/confluence/public.md",
9 + "sourceHeading": "Confluence custom OAuth should keep scopes aligned with Composio defaults and endpoint type"
10 + },
11 + {
12 + "sourcePath": "toolkits/confluence/public.md",
13 + "sourceHeading": "Add `offline_access` to Confluence auth configs when refresh tokens are needed"
14 + },
15 + {
16 + "sourcePath": "toolkits/confluence/public.md",
17 + "sourceHeading": "Use connected account ID, not auth config ID, when executing Confluence tools"
18 + },
19 + {
20 + "sourcePath": "toolkits/confluence/public.md",
21 + "sourceHeading": "Use `CONFLUENCE_GET_PAGE_BY_ID` to retrieve Confluence page content"
22 + },
23 + {
24 + "sourcePath": "toolkits/confluence/public.md",
25 + "sourceHeading": "`CONFLUENCE_UPDATE_PAGE` should be paired with `CONFLUENCE_GET_PAGE_VERSIONS` for versioned updates"
26 + },
27 + {
28 + "sourcePath": "toolkits/confluence/public.md",
29 + "sourceHeading": "Download Confluence attachments by first getting attachment IDs"
30 + },
31 + {
32 + "sourcePath": "toolkits/confluence/public.md",
33 + "sourceHeading": "Confluence tool scopes are exposed in MCP listTools annotations for supported deployments"
34 + },
35 + {
36 + "sourcePath": "toolkits/confluence/public.md",
37 + "sourceHeading": "For Atlassian/Confluence OAuth, use the same redirect URI in auth config and Atlassian app"
38 + }
39 + ],
40 + "topics": [
41 + "auth-config",
42 + "authentication",
43 + "sessions-and-execution",
44 + "toolkits-and-providers"
45 + ],
46 + "tags": [
47 + "confluence",
48 + "for-you",
49 + "platform"
50 + ],
51 + "aliases": [
52 + "/kb/toolkits/confluence-troubleshooting",
53 + "confluence-custom-oauth-should-keep-scopes-aligned-with-composio-defau",
54 + "confluence-managed-oauth-failures-can-come-from-scope-mismatch-between",
55 + "confluence-needs-offline-access-for-refresh",
56 + "confluence-troubleshooting",
57 + "download-confluence-attachments-by-first-getting-attachment-ids",
58 + "for-atlassian-confluence-oauth-use-the-same-redirect-uri-in-auth-confi",
59 + "page-created-triggers-can-auto-disable-after-repeated-cloud-id-lookup"
60 + ],
61 + "relatedGuides": [],
62 + "externalResources": [],
63 + "updatedAt": "2026-07-16",
64 + "lastVerifiedAt": "2026-08-12",
65 + "reviewAfter": "2026-11-10",
66 + "freshness": "evergreen",
67 + "state": "published",
68 + "featured": false
69 +}
docs/kb/guides/toolkits-databricks.json new
+42
@@ -0,0 +1,42 @@
1 +{
2 + "slug": "toolkits-databricks",
3 + "title": "Databricks",
4 + "description": "Public support knowledge for Databricks.",
5 + "articlePath": "toolkits-databricks.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/databricks/public.md",
9 + "sourceHeading": "Databricks OAuth client and secret setup reference"
10 + },
11 + {
12 + "sourcePath": "toolkits/databricks/public.md",
13 + "sourceHeading": "Enter Databricks API key credentials during connected account linking"
14 + }
15 + ],
16 + "topics": [
17 + "authentication",
18 + "sessions-and-execution",
19 + "toolkits-and-providers"
20 + ],
21 + "tags": [
22 + "databricks",
23 + "for-you",
24 + "platform"
25 + ],
26 + "aliases": [
27 + "/kb/toolkits/databricks-troubleshooting",
28 + "databricks-oauth-client-and-secret-setup-reference",
29 + "databricks-requires-custom-credentials-when-managed-auth-is-unavailabl",
30 + "databricks-toolkit-does-not-yet-support-oauth-m2m",
31 + "databricks-troubleshooting",
32 + "enter-databricks-api-key-credentials-during-connected-account-linking"
33 + ],
34 + "relatedGuides": [],
35 + "externalResources": [],
36 + "updatedAt": "2026-06-24",
37 + "lastVerifiedAt": "2026-08-12",
38 + "reviewAfter": "2026-11-10",
39 + "freshness": "evergreen",
40 + "state": "published",
41 + "featured": false
42 +}
docs/kb/guides/toolkits-digital-ocean.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "toolkits-digital-ocean",
3 + "title": "DigitalOcean authentication",
4 + "description": "Current authentication choices for the DigitalOcean toolkit.",
5 + "articlePath": "toolkits-digital-ocean.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/digital_ocean/public.md",
9 + "sourceHeading": "DigitalOcean supports managed OAuth2, custom OAuth2, or a personal access token"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "digital_ocean",
19 + "for-you",
20 + "platform"
21 + ],
22 + "aliases": [
23 + "/kb/toolkits/managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva",
24 + "managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-08-17",
29 + "lastVerifiedAt": "2026-08-24",
30 + "reviewAfter": "2026-11-22",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-discord.json new
+37
@@ -0,0 +1,37 @@
1 +{
2 + "slug": "toolkits-discord",
3 + "title": "Discord",
4 + "description": "Public support knowledge for Discord.",
5 + "articlePath": "toolkits-discord.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/discord/public.md",
9 + "sourceHeading": "Discord OAuth credentials do not have a fixed expiration period"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "errors-and-troubleshooting",
16 + "toolkits-and-providers"
17 + ],
18 + "tags": [
19 + "discord",
20 + "for-you",
21 + "platform"
22 + ],
23 + "aliases": [
24 + "/kb/toolkits/discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio",
25 + "/kb/toolkits/multiple-accounts-for-the-same-discord-app-were-not-supported-in-that",
26 + "discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio",
27 + "multiple-accounts-for-the-same-discord-app-were-not-supported-in-that"
28 + ],
29 + "relatedGuides": [],
30 + "externalResources": [],
31 + "updatedAt": "2026-06-24",
32 + "lastVerifiedAt": "2026-08-12",
33 + "reviewAfter": "2026-11-10",
34 + "freshness": "evergreen",
35 + "state": "published",
36 + "featured": false
37 +}
docs/kb/guides/toolkits-discordbot.json new
+47
@@ -0,0 +1,47 @@
1 +{
2 + "slug": "toolkits-discordbot",
3 + "title": "Discord Bot",
4 + "description": "Public support knowledge for Discord Bot.",
5 + "articlePath": "toolkits-discordbot.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/discordbot/public.md",
9 + "sourceHeading": "Discord and DiscordBot use different token types"
10 + },
11 + {
12 + "sourcePath": "toolkits/discordbot/public.md",
13 + "sourceHeading": "Verify Discord auth config scopes when bot actions do not respond"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "authentication",
19 + "errors-and-troubleshooting",
20 + "sessions-and-execution",
21 + "toolkits-and-providers"
22 + ],
23 + "tags": [
24 + "discordbot",
25 + "for-you",
26 + "platform"
27 + ],
28 + "aliases": [
29 + "/kb/authentication/discord-bot-troubleshooting",
30 + "/kb/toolkits/discord-message-triggers-need-bot-token-auth-which-is-not-available-th",
31 + "/kb/toolkits/multiple-connected-accounts-for-the-same-app-are-not-supported",
32 + "choose-discordbot-for-bot-token-operations",
33 + "discord-bot-troubleshooting",
34 + "discord-message-triggers-need-bot-token-auth-which-is-not-available-th",
35 + "managed-discordbot-oauth-401s-can-be-worked-around-with-custom-credent",
36 + "multiple-connected-accounts-for-the-same-app-are-not-supported",
37 + "verify-discord-auth-config-scopes-when-bot-actions-do-not-respond"
38 + ],
39 + "relatedGuides": [],
40 + "externalResources": [],
41 + "updatedAt": "2026-06-24",
42 + "lastVerifiedAt": "2026-08-12",
43 + "reviewAfter": "2026-11-10",
44 + "freshness": "evergreen",
45 + "state": "published",
46 + "featured": false
47 +}
docs/kb/guides/toolkits-docusign.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "toolkits-docusign",
3 + "title": "DocuSign",
4 + "description": "Public support knowledge for DocuSign.",
5 + "articlePath": "toolkits-docusign.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/docusign/public.md",
9 + "sourceHeading": "DocuSign auth guide URL"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "toolkits-and-providers"
15 + ],
16 + "tags": [
17 + "docusign",
18 + "for-you",
19 + "platform"
20 + ],
21 + "aliases": [
22 + "/kb/toolkits/docusign-auth-guide-url",
23 + "docusign-auth-guide-url"
24 + ],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-06-24",
28 + "lastVerifiedAt": "2026-08-12",
29 + "reviewAfter": "2026-11-10",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/toolkits-dropbox.json new
+62
@@ -0,0 +1,62 @@
1 +{
2 + "slug": "toolkits-dropbox",
3 + "title": "Dropbox",
4 + "description": "Public support knowledge for Dropbox.",
5 + "articlePath": "toolkits-dropbox.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/dropbox/public.md",
9 + "sourceHeading": "Allow the Composio auth-app redirect URL in the Dropbox app"
10 + },
11 + {
12 + "sourcePath": "toolkits/dropbox/public.md",
13 + "sourceHeading": "Dropbox connections use Dropbox native OAuth, not Microsoft/Azure/Outlook login"
14 + },
15 + {
16 + "sourcePath": "toolkits/dropbox/public.md",
17 + "sourceHeading": "For Dropbox upload, `path` is the Dropbox destination and `content` is the local file path"
18 + },
19 + {
20 + "sourcePath": "toolkits/dropbox/public.md",
21 + "sourceHeading": "Pass file paths to SDK attachment arguments rather than base64/file metadata objects"
22 + },
23 + {
24 + "sourcePath": "toolkits/dropbox/public.md",
25 + "sourceHeading": "Use DROPBOX_GET_ABOUT_ME to confirm which Dropbox account is connected"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "dropbox",
37 + "for-you",
38 + "platform"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/dropbox-triggers-are-not-currently-available",
42 + "/kb/toolkits/dropbox-troubleshooting",
43 + "allow-the-composio-auth-app-redirect-url-in-the-dropbox-app",
44 + "dropbox-connections-use-dropbox-native-oauth-not-microsoft-azure-outlo",
45 + "dropbox-triggers-are-not-currently-available",
46 + "dropbox-troubleshooting",
47 + "for-dropbox-upload-path-is-the-dropbox-destination-and-content-is-the",
48 + "initiate-dropbox-oauth-connections-with-entityid-authmode-integrationi",
49 + "pass-file-paths-to-sdk-attachment-arguments-rather-than-base64-file-me",
50 + "recreate-older-dropbox-integrations-after-composio-updates-the-default",
51 + "use-custom-dropbox-oauth-credentials-for-production-instead-of-the-def",
52 + "use-dropbox-get-about-me-to-confirm-which-dropbox-account-is-connected"
53 + ],
54 + "relatedGuides": [],
55 + "externalResources": [],
56 + "updatedAt": "2026-06-24",
57 + "lastVerifiedAt": "2026-08-12",
58 + "reviewAfter": "2026-11-10",
59 + "freshness": "evergreen",
60 + "state": "published",
61 + "featured": false
62 +}
docs/kb/guides/toolkits-excel.json new
+68
@@ -0,0 +1,68 @@
1 +{
2 + "slug": "toolkits-excel",
3 + "title": "Excel",
4 + "description": "Public support knowledge for Excel.",
5 + "articlePath": "toolkits-excel.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/excel/public.md",
9 + "sourceHeading": "EXCEL_UPDATE_RANGE values must be a 2D array"
10 + },
11 + {
12 + "sourcePath": "toolkits/excel/public.md",
13 + "sourceHeading": "Excel upload tools accept structured workbook data"
14 + },
15 + {
16 + "sourcePath": "toolkits/excel/public.md",
17 + "sourceHeading": "EXCEL_GET_RANGE failures can come from sheet name or item_id mismatches"
18 + },
19 + {
20 + "sourcePath": "toolkits/excel/public.md",
21 + "sourceHeading": "Use Excel toolkit actions for workbook operations on SharePoint-backed Excel files"
22 + },
23 + {
24 + "sourcePath": "toolkits/excel/public.md",
25 + "sourceHeading": "Excel uses the Microsoft auth guide at composio.dev/auth/outlook"
26 + },
27 + {
28 + "sourcePath": "toolkits/excel/public.md",
29 + "sourceHeading": "Upgrade if Excel schemas contain dollar-sign parameters"
30 + },
31 + {
32 + "sourcePath": "toolkits/excel/public.md",
33 + "sourceHeading": "Generic column formatting and wrapping are available in current versions"
34 + }
35 + ],
36 + "topics": [
37 + "authentication",
38 + "errors-and-troubleshooting",
39 + "sessions-and-execution",
40 + "toolkits-and-providers"
41 + ],
42 + "tags": [
43 + "excel",
44 + "for-you",
45 + "platform"
46 + ],
47 + "aliases": [
48 + "/kb/toolkits/excel-troubleshooting",
49 + "excel-get-range-failures-can-come-from-sheet-name-or-item-id-mismatche",
50 + "excel-support-for-oauth2-client-credentials-may-vary-by-action",
51 + "excel-troubleshooting",
52 + "excel-update-range-values-must-be-a-2d-array",
53 + "excel-upload-tools-accept-structured-workbook-data",
54 + "excel-uses-the-microsoft-auth-guide-at-composio-dev-auth-outlook",
55 + "generic-column-formatting-and-wrapping-support-was-added-in-the-may-13",
56 + "shared-item-listing-cannot-reliably-search-for-a-specific-shared-file",
57 + "upgrade-older-on-prem-versions-if-excel-schemas-contain-dollar-sign-pa",
58 + "use-excel-toolkit-actions-for-workbook-operations-on-sharepoint-backed"
59 + ],
60 + "relatedGuides": [],
61 + "externalResources": [],
62 + "updatedAt": "2026-06-24",
63 + "lastVerifiedAt": "2026-08-17",
64 + "reviewAfter": "2026-11-15",
65 + "freshness": "evergreen",
66 + "state": "published",
67 + "featured": false
68 +}
docs/kb/guides/toolkits-facebook.json new
+56
@@ -0,0 +1,56 @@
1 +{
2 + "slug": "toolkits-facebook",
3 + "title": "Facebook",
4 + "description": "Public support knowledge for Facebook.",
5 + "articlePath": "toolkits-facebook.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/facebook/public.md",
9 + "sourceHeading": "FACEBOOK_DELETE_POST failure can be fixed by using the latest Facebook toolkit version"
10 + },
11 + {
12 + "sourcePath": "toolkits/facebook/public.md",
13 + "sourceHeading": "Meta OAuth issues can require adding the Composio redirect URI in the Meta app settings"
14 + },
15 + {
16 + "sourcePath": "toolkits/facebook/public.md",
17 + "sourceHeading": "Facebook or Instagram connections authenticate the account selected in Meta's picker and cannot be repointed server-side"
18 + },
19 + {
20 + "sourcePath": "toolkits/facebook/public.md",
21 + "sourceHeading": "WhatsApp connections require WABA ID as generic_id, with bearer_token for API-key auth"
22 + }
23 + ],
24 + "topics": [
25 + "auth-config",
26 + "authentication",
27 + "errors-and-troubleshooting",
28 + "sessions-and-execution",
29 + "toolkits-and-providers"
30 + ],
31 + "tags": [
32 + "facebook",
33 + "for-you",
34 + "platform"
35 + ],
36 + "aliases": [
37 + "/kb/toolkits/facebook-troubleshooting",
38 + "change-the-connected-facebook-or-instagram-account",
39 + "connect-meta-ads-with-your-own-credentials",
40 + "facebook-delete-post-failure-can-be-fixed-by-using-the-latest-facebook",
41 + "facebook-troubleshooting",
42 + "instagram-webhook-verification-config-is-not-needed-if-composio-has-no",
43 + "meta-ads-toolkit-exists-missing-apis-should-be-filed-as-feature-reques",
44 + "meta-ads-toolkit-was-updated-to-api-version-v24-0",
45 + "whatsapp-connections-require-waba-id-as-generic-id-with-bearer-token-f",
46 + "whatsapp-template-sending-needs-an-existing-template-and-required-phon"
47 + ],
48 + "relatedGuides": [],
49 + "externalResources": [],
50 + "updatedAt": "2026-06-24",
51 + "lastVerifiedAt": "2026-08-17",
52 + "reviewAfter": "2026-11-15",
53 + "freshness": "evergreen",
54 + "state": "published",
55 + "featured": false
56 +}
docs/kb/guides/toolkits-fathom.json new
+42
@@ -0,0 +1,42 @@
1 +{
2 + "slug": "toolkits-fathom",
3 + "title": "Fathom",
4 + "description": "Public support knowledge for Fathom.",
5 + "articlePath": "toolkits-fathom.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/fathom/public.md",
9 + "sourceHeading": "Fathom and granola_mcp are supported meeting transcription toolkits; request unsupported tools separately"
10 + },
11 + {
12 + "sourcePath": "toolkits/fathom/public.md",
13 + "sourceHeading": "OAuth authorization URLs are provider-specific"
14 + }
15 + ],
16 + "topics": [
17 + "auth-config",
18 + "authentication",
19 + "errors-and-troubleshooting",
20 + "sessions-and-execution",
21 + "toolkits-and-providers"
22 + ],
23 + "tags": [
24 + "fathom",
25 + "for-you",
26 + "platform"
27 + ],
28 + "aliases": [
29 + "/kb/toolkits/fathom-troubleshooting",
30 + "fathom-and-granola-mcp-are-supported-meeting-transcription-toolkits-re",
31 + "fathom-troubleshooting",
32 + "oauth-authorization-urls-are-provider-specific"
33 + ],
34 + "relatedGuides": [],
35 + "externalResources": [],
36 + "updatedAt": "2026-06-24",
37 + "lastVerifiedAt": "2026-08-12",
38 + "reviewAfter": "2026-11-10",
39 + "freshness": "evergreen",
40 + "state": "published",
41 + "featured": false
42 +}
docs/kb/guides/toolkits-figma.json new
+60
@@ -0,0 +1,60 @@
1 +{
2 + "slug": "toolkits-figma",
3 + "title": "Figma",
4 + "description": "Public support knowledge for Figma.",
5 + "articlePath": "toolkits-figma.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/figma/public.md",
9 + "sourceHeading": "Figma token auth is handled by Composio; customers do not need a separate Bearer-token auth scheme"
10 + },
11 + {
12 + "sourcePath": "toolkits/figma/public.md",
13 + "sourceHeading": "`FIGMA_EXTRACT_DESIGN_TOKENS` variables may be limited by the customer's Figma plan"
14 + },
15 + {
16 + "sourcePath": "toolkits/figma/public.md",
17 + "sourceHeading": "Figma 429s can come from Figma/provider limits; use custom credentials for production"
18 + },
19 + {
20 + "sourcePath": "toolkits/figma/public.md",
21 + "sourceHeading": "Remove deprecated `file_read` from Figma auth configs and reconnect"
22 + },
23 + {
24 + "sourcePath": "toolkits/figma/public.md",
25 + "sourceHeading": "Figma tools are available across auth modes; fetch available tools dynamically"
26 + },
27 + {
28 + "sourcePath": "toolkits/figma/public.md",
29 + "sourceHeading": "Common Figma design-token tools include extract, Tailwind conversion, and node fetch"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "figma",
41 + "for-you",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/figma-troubleshooting",
46 + "figma-429s-can-come-from-figma-provider-limits-use-custom-credentials",
47 + "figma-token-auth-is-handled-by-composio-customers-do-not-need-a-separa",
48 + "figma-tools-are-available-across-auth-modes-fetch-available-tools-dyna",
49 + "figma-troubleshooting",
50 + "new-figma-scopes-may-require-custom-oauth-api-key-auth-because-default"
51 + ],
52 + "relatedGuides": [],
53 + "externalResources": [],
54 + "updatedAt": "2026-06-24",
55 + "lastVerifiedAt": "2026-08-17",
56 + "reviewAfter": "2026-11-15",
57 + "freshness": "evergreen",
58 + "state": "published",
59 + "featured": false
60 +}
docs/kb/guides/toolkits-firecrawl.json new
+66
@@ -0,0 +1,66 @@
1 +{
2 + "slug": "toolkits-firecrawl",
3 + "title": "Firecrawl",
4 + "description": "Public support knowledge for Firecrawl.",
5 + "articlePath": "toolkits-firecrawl.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/firecrawl/public.md",
9 + "sourceHeading": "Firecrawl uses API-key auth, not OAuth; provide a Firecrawl API key"
10 + },
11 + {
12 + "sourcePath": "toolkits/firecrawl/public.md",
13 + "sourceHeading": "Create a Firecrawl API-key connected account with generic_api_key"
14 + },
15 + {
16 + "sourcePath": "toolkits/firecrawl/public.md",
17 + "sourceHeading": "FIRECRAWL_SEARCH may be hidden by default tool list limits"
18 + },
19 + {
20 + "sourcePath": "toolkits/firecrawl/public.md",
21 + "sourceHeading": "Batch fewer URLs or raise timeout for long Firecrawl scrape jobs"
22 + },
23 + {
24 + "sourcePath": "toolkits/firecrawl/public.md",
25 + "sourceHeading": "Firecrawl API base URL is https://api.firecrawl.dev/v1"
26 + },
27 + {
28 + "sourcePath": "toolkits/firecrawl/public.md",
29 + "sourceHeading": "Use FIRECRAWL_SCRAPE or FIRECRAWL_EXTRACT for web-content retrieval"
30 + },
31 + {
32 + "sourcePath": "toolkits/firecrawl/public.md",
33 + "sourceHeading": "Connect MCP sessions are tied to individual consumer accounts, not a shared workspace"
34 + }
35 + ],
36 + "topics": [
37 + "authentication",
38 + "errors-and-troubleshooting",
39 + "sessions-and-execution",
40 + "toolkits-and-providers"
41 + ],
42 + "tags": [
43 + "firecrawl",
44 + "for-you",
45 + "platform"
46 + ],
47 + "aliases": [
48 + "/kb/toolkits/firecrawl-troubleshooting",
49 + "batch-fewer-urls-or-raise-timeout-for-long-firecrawl-scrape-jobs",
50 + "connect-mcp-sessions-are-tied-to-individual-consumer-accounts-not-a-sh",
51 + "create-a-firecrawl-api-key-connected-account-with-generic-api-key",
52 + "firecrawl-api-base-url-is-https-api-firecrawl-dev-v1",
53 + "firecrawl-search-may-be-hidden-by-default-tool-list-limits",
54 + "firecrawl-troubleshooting",
55 + "firecrawl-uses-api-key-auth-not-oauth-provide-a-firecrawl-api-key",
56 + "use-firecrawl-scrape-or-firecrawl-extract-for-web-content-retrieval"
57 + ],
58 + "relatedGuides": [],
59 + "externalResources": [],
60 + "updatedAt": "2026-06-24",
61 + "lastVerifiedAt": "2026-08-12",
62 + "reviewAfter": "2026-11-10",
63 + "freshness": "evergreen",
64 + "state": "published",
65 + "featured": false
66 +}
docs/kb/guides/toolkits-gemini.json new
+82
@@ -0,0 +1,82 @@
1 +{
2 + "slug": "toolkits-gemini",
3 + "title": "Gemini",
4 + "description": "Public support knowledge for Gemini.",
5 + "articlePath": "toolkits-gemini.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/gemini/public.md",
9 + "sourceHeading": "Gemini no-auth/toolkit usage is counted as regular Composio tool calls"
10 + },
11 + {
12 + "sourcePath": "toolkits/gemini/public.md",
13 + "sourceHeading": "Use newer Gemini models such as `gemini-2.5-flash` instead of old `gemini-1.5-flash` defaults"
14 + },
15 + {
16 + "sourcePath": "toolkits/gemini/public.md",
17 + "sourceHeading": "Gemini video generation should use supported Veo model names"
18 + },
19 + {
20 + "sourcePath": "toolkits/gemini/public.md",
21 + "sourceHeading": "Use `GEMINI_WAIT_FOR_VIDEO` before using generated video output"
22 + },
23 + {
24 + "sourcePath": "toolkits/gemini/public.md",
25 + "sourceHeading": "Disable automatic file handling when Gemini generated files should remain as URLs/content"
26 + },
27 + {
28 + "sourcePath": "toolkits/gemini/public.md",
29 + "sourceHeading": "Gemini can use Composio Tool Router through any MCP client"
30 + },
31 + {
32 + "sourcePath": "toolkits/gemini/public.md",
33 + "sourceHeading": "Gemini CLI MCP issues may be client-side; Claude can be a more stable fallback"
34 + },
35 + {
36 + "sourcePath": "toolkits/gemini/public.md",
37 + "sourceHeading": "Gemini schema errors can come from Google's OpenAPI-vs-JSON-Schema limitations"
38 + },
39 + {
40 + "sourcePath": "toolkits/gemini/public.md",
41 + "sourceHeading": "Composio supports Google Gemini/Vertex AI providers, with Python support historically ahead of JS"
42 + },
43 + {
44 + "sourcePath": "toolkits/gemini/public.md",
45 + "sourceHeading": "LangChain MCP tools are not OpenAI-only and can work with Gemini-capable tool calling"
46 + }
47 + ],
48 + "topics": [
49 + "authentication",
50 + "errors-and-troubleshooting",
51 + "sessions-and-execution",
52 + "toolkits-and-providers"
53 + ],
54 + "tags": [
55 + "for-you",
56 + "gemini",
57 + "platform"
58 + ],
59 + "aliases": [
60 + "/kb/toolkits/gemini-troubleshooting",
61 + "composio-supports-google-gemini-vertex-ai-providers-with-python-suppor",
62 + "disable-automatic-file-handling-when-gemini-generated-files-should-rem",
63 + "gemini-can-use-composio-tool-router-through-any-mcp-client",
64 + "gemini-cli-mcp-issues-may-be-client-side-claude-can-be-a-more-stable-f",
65 + "gemini-schema-errors-can-come-from-google-s-openapi-vs-json-schema-lim",
66 + "gemini-toolkit-quota-is-shared",
67 + "gemini-troubleshooting",
68 + "gemini-video-generation-should-use-supported-veo-model-names",
69 + "gemini-wait-for-video-can-fail-with-missing-presigned-url-after-succes",
70 + "langchain-mcp-tools-are-not-openai-only-and-can-work-with-gemini-capab",
71 + "use-gemini-get-videos-operation-or-gemini-wait-for-video-before-using",
72 + "use-newer-gemini-models-such-as-gemini-2-5-flash-instead-of-old-gemini"
73 + ],
74 + "relatedGuides": [],
75 + "externalResources": [],
76 + "updatedAt": "2026-06-24",
77 + "lastVerifiedAt": "2026-08-17",
78 + "reviewAfter": "2026-11-15",
79 + "freshness": "evergreen",
80 + "state": "published",
81 + "featured": false
82 +}
docs/kb/guides/toolkits-github.json new
+63
@@ -0,0 +1,63 @@
1 +{
2 + "slug": "toolkits-github",
3 + "title": "GitHub",
4 + "description": "Public support knowledge for GitHub.",
5 + "articlePath": "toolkits-github.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/github/public.md",
9 + "sourceHeading": "GitHub V2 triggers do not require creating a webhook endpoint first"
10 + },
11 + {
12 + "sourcePath": "toolkits/github/public.md",
13 + "sourceHeading": "List GitHub organizations and repositories for the authenticated user"
14 + },
15 + {
16 + "sourcePath": "toolkits/github/public.md",
17 + "sourceHeading": "GitHub connected-account tokens are redacted from API responses"
18 + },
19 + {
20 + "sourcePath": "toolkits/github/public.md",
21 + "sourceHeading": "GitHub organization access can require approval from an organization owner"
22 + },
23 + {
24 + "sourcePath": "toolkits/github/public.md",
25 + "sourceHeading": "Session-level tool allowlists are enforced server-side at execution time"
26 + },
27 + {
28 + "sourcePath": "toolkits/github/public.md",
29 + "sourceHeading": "Use custom OAuth credentials for branded GitHub consent and redirect flows"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "github",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/github-troubleshooting",
46 + "access-token-freshness-when-retrieving-tokens-for-direct-github-operat",
47 + "connect-a-github-app",
48 + "github-troubleshooting",
49 + "github-v2-triggers-do-not-require-creating-a-webhook-endpoint-first",
50 + "list-github-organizations-and-repositories-for-the-authenticated-user",
51 + "session-level-tool-allowlists-are-enforced-server-side-at-execution-ti",
52 + "use-custom-oauth-credentials-for-branded-github-consent-and-redirect-f",
53 + "why-github-connected-account-tokens-may-show-as-redacted"
54 + ],
55 + "relatedGuides": [],
56 + "externalResources": [],
57 + "updatedAt": "2026-06-24",
58 + "lastVerifiedAt": "2026-08-17",
59 + "reviewAfter": "2026-11-15",
60 + "freshness": "evergreen",
61 + "state": "published",
62 + "featured": false
63 +}
docs/kb/guides/toolkits-gmail.json new
+110
@@ -0,0 +1,110 @@
1 +{
2 + "slug": "toolkits-gmail",
3 + "title": "Gmail",
4 + "description": "Public support knowledge for Gmail.",
5 + "articlePath": "toolkits-gmail.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/gmail/public.md",
9 + "sourceHeading": "Use `latest` or v3.1 for newer Gmail settings tools"
10 + },
11 + {
12 + "sourcePath": "toolkits/gmail/public.md",
13 + "sourceHeading": "Create Gmail custom OAuth auth config, then initiate a connection with callback URL"
14 + },
15 + {
16 + "sourcePath": "toolkits/gmail/public.md",
17 + "sourceHeading": "Creating Gmail filters requires `gmail.settings.basic`"
18 + },
19 + {
20 + "sourcePath": "toolkits/gmail/public.md",
21 + "sourceHeading": "`gmail.send` is granular but sensitive; `mail.google.com` gives full access"
22 + },
23 + {
24 + "sourcePath": "toolkits/gmail/public.md",
25 + "sourceHeading": "Configure Gmail scopes on managed auth config as a comma-joined scopes string"
26 + },
27 + {
28 + "sourcePath": "toolkits/gmail/public.md",
29 + "sourceHeading": "Avoid `gmail.metadata` when fetching full Gmail email content"
30 + },
31 + {
32 + "sourcePath": "toolkits/gmail/public.md",
33 + "sourceHeading": "Use `me` for Gmail `user_id` in tool calls"
34 + },
35 + {
36 + "sourcePath": "toolkits/gmail/public.md",
37 + "sourceHeading": "`GMAIL_SEND_EMAIL` accepts at least one of `to`, `cc`, or `bcc`"
38 + },
39 + {
40 + "sourcePath": "toolkits/gmail/public.md",
41 + "sourceHeading": "For Gmail attachments over MCP, upload files before tool execution"
42 + },
43 + {
44 + "sourcePath": "toolkits/gmail/public.md",
45 + "sourceHeading": "Gmail attachment sends can outlast a client timeout; verify before retrying"
46 + },
47 + {
48 + "sourcePath": "toolkits/gmail/public.md",
49 + "sourceHeading": "Reduce Gmail fetch payload size with `include_payload=false`, `verbose=false`, `only_ids`, query, and limits"
50 + },
51 + {
52 + "sourcePath": "toolkits/gmail/public.md",
53 + "sourceHeading": "Use `from_email` to select Gmail send-as alias"
54 + },
55 + {
56 + "sourcePath": "toolkits/gmail/public.md",
57 + "sourceHeading": "Use Gmail label IDs, not label names, for label operations"
58 + },
59 + {
60 + "sourcePath": "toolkits/gmail/public.md",
61 + "sourceHeading": "Patch Gmail label colors with `background_color` and accepted color values"
62 + },
63 + {
64 + "sourcePath": "toolkits/gmail/public.md",
65 + "sourceHeading": "Filter Gmail new-message trigger by label/query instead of label IDs"
66 + },
67 + {
68 + "sourcePath": "toolkits/gmail/public.md",
69 + "sourceHeading": "Use `googlesuper` for one Google auth across Gmail, Calendar, Drive-style use cases"
70 + }
71 + ],
72 + "topics": [
73 + "auth-config",
74 + "authentication",
75 + "errors-and-troubleshooting",
76 + "sessions-and-execution",
77 + "toolkits-and-providers"
78 + ],
79 + "tags": [
80 + "for-you",
81 + "gmail",
82 + "platform"
83 + ],
84 + "aliases": [
85 + "/kb/toolkits/gmail-troubleshooting",
86 + "configure-gmail-scopes-on-managed-auth-config-as-a-comma-joined-scopes",
87 + "create-gmail-filters-scope",
88 + "filter-gmail-new-message-trigger-by-label-query-instead-of-label-ids",
89 + "for-gmail-attachments-over-mcp-upload-files-before-tool-execution",
90 + "gmail-attachments-can-make-send-email-slow-enough-to-hit-sdk-request-t",
91 + "gmail-send-email-accepts-at-least-one-of-to-cc-or-bcc",
92 + "gmail-send-is-granular-but-sensitive-mail-google-com-gives-full-access",
93 + "gmail-troubleshooting",
94 + "patch-gmail-label-colors-with-background-color-and-accepted-color-valu",
95 + "reduce-gmail-fetch-payload-size",
96 + "send-gmail-from-a-send-as-alias",
97 + "use-gmail-label-ids-not-label-names-for-label-operations",
98 + "use-googlesuper-for-one-google-auth-across-gmail-calendar-drive-style",
99 + "use-latest-or-v3-1-for-newer-gmail-settings-tools",
100 + "verbose-gmail-thread-results-cannot-select-custom-fields-and-may-not-b"
101 + ],
102 + "relatedGuides": [],
103 + "externalResources": [],
104 + "updatedAt": "2026-07-14",
105 + "lastVerifiedAt": "2026-08-17",
106 + "reviewAfter": "2026-11-15",
107 + "freshness": "evergreen",
108 + "state": "published",
109 + "featured": false
110 +}
docs/kb/guides/toolkits-gong.json new
+49
@@ -0,0 +1,49 @@
1 +{
2 + "slug": "toolkits-gong",
3 + "title": "Gong",
4 + "description": "Public support knowledge for Gong.",
5 + "articlePath": "toolkits-gong.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/gong/public.md",
9 + "sourceHeading": "Gong base URL differs by customer and should be provided at connection time"
10 + },
11 + {
12 + "sourcePath": "toolkits/gong/public.md",
13 + "sourceHeading": "Gong connection initiation can use Basic auth fields: access key, access key secret, and Gong URL"
14 + },
15 + {
16 + "sourcePath": "toolkits/gong/public.md",
17 + "sourceHeading": "Gong MCP tool scopes can be read from tool annotations in the tools API"
18 + }
19 + ],
20 + "topics": [
21 + "auth-config",
22 + "authentication",
23 + "sessions-and-execution",
24 + "toolkits-and-providers"
25 + ],
26 + "tags": [
27 + "for-you",
28 + "gong",
29 + "platform"
30 + ],
31 + "aliases": [
32 + "/kb/toolkits/gong-triggers-were-planned-requested-but-may-not-be-available-for-ever",
33 + "/kb/toolkits/gong-troubleshooting",
34 + "gong-base-url-differs-by-customer-and-should-be-provided-at-connection",
35 + "gong-connection-initiation-can-use-basic-auth-fields-access-key-access",
36 + "gong-mcp-tool-scopes-can-be-read-from-tool-annotations-in-the-tools-ap",
37 + "gong-oauth2-support-may-need-to-be-treated-as-a-feature-request-if-not",
38 + "gong-triggers-were-planned-requested-but-may-not-be-available-for-ever",
39 + "gong-troubleshooting"
40 + ],
41 + "relatedGuides": [],
42 + "externalResources": [],
43 + "updatedAt": "2026-06-24",
44 + "lastVerifiedAt": "2026-08-12",
45 + "reviewAfter": "2026-11-10",
46 + "freshness": "evergreen",
47 + "state": "published",
48 + "featured": false
49 +}
docs/kb/guides/toolkits-google-analytics.json new
+47
@@ -0,0 +1,47 @@
1 +{
2 + "slug": "toolkits-google-analytics",
3 + "title": "Google Analytics",
4 + "description": "Public support knowledge for Google Analytics.",
5 + "articlePath": "toolkits-google-analytics.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/google_analytics/public.md",
9 + "sourceHeading": "Use latest toolkit version when Google Analytics tools return ToolNotFound or only a few tools"
10 + },
11 + {
12 + "sourcePath": "toolkits/google_analytics/public.md",
13 + "sourceHeading": "Add Google Analytics to an MCP config as a selected tool/toolkit"
14 + },
15 + {
16 + "sourcePath": "toolkits/google_analytics/public.md",
17 + "sourceHeading": "Empty Google Analytics reports may be provider data availability rather than Composio failure"
18 + }
19 + ],
20 + "topics": [
21 + "authentication",
22 + "errors-and-troubleshooting",
23 + "sessions-and-execution",
24 + "toolkits-and-providers"
25 + ],
26 + "tags": [
27 + "for-you",
28 + "google_analytics",
29 + "platform"
30 + ],
31 + "aliases": [
32 + "/kb/toolkits/google-analytics-troubleshooting",
33 + "add-google-analytics-to-an-mcp-config-as-a-selected-tool-toolkit",
34 + "empty-google-analytics-reports-may-be-provider-data-availability-rathe",
35 + "google-analytics-troubleshooting",
36 + "old-google-analytics-mcp-could-show-0-actions-because-it-was-auth-only",
37 + "use-latest-toolkit-version-when-google-analytics-tools-return-toolnotf"
38 + ],
39 + "relatedGuides": [],
40 + "externalResources": [],
41 + "updatedAt": "2026-06-24",
42 + "lastVerifiedAt": "2026-08-17",
43 + "reviewAfter": "2026-11-15",
44 + "freshness": "evergreen",
45 + "state": "published",
46 + "featured": false
47 +}
docs/kb/guides/toolkits-google-calendar.json new
+89
@@ -0,0 +1,89 @@
1 +{
2 + "slug": "toolkits-google-calendar",
3 + "title": "Google Calendar",
4 + "description": "Public support knowledge for Google Calendar.",
5 + "articlePath": "toolkits-google-calendar.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/google_calendar/public.md",
9 + "sourceHeading": "Create a Google Calendar integration to access tools and triggers"
10 + },
11 + {
12 + "sourcePath": "toolkits/google_calendar/public.md",
13 + "sourceHeading": "Updating RSVP status has an attendee-list API limitation"
14 + },
15 + {
16 + "sourcePath": "toolkits/google_calendar/public.md",
17 + "sourceHeading": "Canceled/deleted event trigger sends payloads for canceled or deleted events"
18 + },
19 + {
20 + "sourcePath": "toolkits/google_calendar/public.md",
21 + "sourceHeading": "Multiple triggers for the same slug/user can target different calendar IDs"
22 + },
23 + {
24 + "sourcePath": "toolkits/google_calendar/public.md",
25 + "sourceHeading": "`calendar.events` scope is required for event list/fetch flows"
26 + },
27 + {
28 + "sourcePath": "toolkits/google_calendar/public.md",
29 + "sourceHeading": "Google Calendar triggers now return full event data instead of only an ID"
30 + },
31 + {
32 + "sourcePath": "toolkits/google_calendar/public.md",
33 + "sourceHeading": "Google Calendar trigger moved toward polling for more verbose payloads"
34 + },
35 + {
36 + "sourcePath": "toolkits/google_calendar/public.md",
37 + "sourceHeading": "Use trigger-types endpoint to retrieve Google Calendar trigger info programmatically"
38 + },
39 + {
40 + "sourcePath": "toolkits/google_calendar/public.md",
41 + "sourceHeading": "Use Find Free Slots when you need processed availability; free/busy does not do timezone processing"
42 + },
43 + {
44 + "sourcePath": "toolkits/google_calendar/public.md",
45 + "sourceHeading": "Use `primary` as calendar ID; `me` is not valid for calendar ID"
46 + },
47 + {
48 + "sourcePath": "toolkits/google_calendar/public.md",
49 + "sourceHeading": "Use latest Google Calendar toolkit version when filters are ignored"
50 + },
51 + {
52 + "sourcePath": "toolkits/google_calendar/public.md",
53 + "sourceHeading": "Google Calendar meeting link is returned in `hangout_link`"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "toolkits-and-providers"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "google_calendar",
66 + "platform"
67 + ],
68 + "aliases": [
69 + "/kb/authentication/google-calendar-troubleshooting",
70 + "calendar-events-scope-is-required-for-event-list-fetch-flows",
71 + "composio-does-not-support-org-wide-google-workspace-authentication-for",
72 + "create-a-google-calendar-integration-to-access-tools-and-triggers",
73 + "google-calendar-trigger-moved-toward-polling-for-more-verbose-payloads",
74 + "google-calendar-troubleshooting",
75 + "updating-rsvp-status-has-an-attendee-list-api-limitation",
76 + "use-find-free-slots-when-you-need-processed-availability-free-busy-doe",
77 + "use-latest-google-calendar-toolkit-version-when-filters-are-ignored",
78 + "use-primary-for-google-calendar-id",
79 + "use-trigger-types-endpoint-to-retrieve-google-calendar-trigger-info-pr"
80 + ],
81 + "relatedGuides": [],
82 + "externalResources": [],
83 + "updatedAt": "2026-06-24",
84 + "lastVerifiedAt": "2026-08-12",
85 + "reviewAfter": "2026-11-10",
86 + "freshness": "evergreen",
87 + "state": "published",
88 + "featured": false
89 +}
docs/kb/guides/toolkits-google-classroom.json new
+66
@@ -0,0 +1,66 @@
1 +{
2 + "slug": "toolkits-google-classroom",
3 + "title": "Google Classroom",
4 + "description": "Public OAuth and connection troubleshooting for Google Classroom.",
5 + "articlePath": "toolkits-google-classroom.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/google_classroom/public.md",
9 + "sourceHeading": "Set up custom Google OAuth credentials"
10 + },
11 + {
12 + "sourcePath": "toolkits/google_classroom/public.md",
13 + "sourceHeading": "Resolve an \"App is blocked\" connection error"
14 + },
15 + {
16 + "sourcePath": "toolkits/google_classroom/public.md",
17 + "sourceHeading": "Enable the Google Classroom API for custom OAuth"
18 + },
19 + {
20 + "sourcePath": "toolkits/google_classroom/public.md",
21 + "sourceHeading": "Resolve `Error 400: invalid_scope`"
22 + },
23 + {
24 + "sourcePath": "toolkits/google_classroom/public.md",
25 + "sourceHeading": "Choose managed or customer-owned Google OAuth"
26 + },
27 + {
28 + "sourcePath": "toolkits/google_classroom/public.md",
29 + "sourceHeading": "Resolve 401 errors on tool calls"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "google_classroom",
42 + "oauth",
43 + "platform",
44 + "scopes"
45 + ],
46 + "aliases": [
47 + "/kb/toolkits/google-classroom-troubleshooting",
48 + "enable-the-google-classroom-api-for-custom-oauth",
49 + "google-blocks-sensitive-gmail-scopes",
50 + "google-classroom-troubleshooting",
51 + "resolve-401-errors-on-tool-calls",
52 + "resolve-an-app-is-blocked-connection-error",
53 + "resolve-an-app-is-blocked-connection-error-2",
54 + "resolve-error-400-invalid-scope",
55 + "set-up-custom-google-oauth-credentials",
56 + "this-app-is-blocked-means-the-requested-google-scope-is-not-verified-o"
57 + ],
58 + "relatedGuides": [],
59 + "externalResources": [],
60 + "updatedAt": "2026-07-24",
61 + "lastVerifiedAt": "2026-08-24",
62 + "reviewAfter": "2026-11-22",
63 + "freshness": "evergreen",
64 + "state": "published",
65 + "featured": false
66 +}
docs/kb/guides/toolkits-google-maps.json new
+58
@@ -0,0 +1,58 @@
1 +{
2 + "slug": "toolkits-google-maps",
3 + "title": "Google Maps",
4 + "description": "Public support knowledge for Google Maps.",
5 + "articlePath": "toolkits-google-maps.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/google_maps/public.md",
9 + "sourceHeading": "Maps Embed API requires API-key authentication"
10 + },
11 + {
12 + "sourcePath": "toolkits/google_maps/public.md",
13 + "sourceHeading": "Google Maps OAuth can be blocked by sensitive cloud-platform scope"
14 + },
15 + {
16 + "sourcePath": "toolkits/google_maps/public.md",
17 + "sourceHeading": "Validate Places `includedTypes` against Google's supported place types"
18 + },
19 + {
20 + "sourcePath": "toolkits/google_maps/public.md",
21 + "sourceHeading": "Deprecated `GEOCODING_API` is not the Google Maps toolkit tool to use"
22 + },
23 + {
24 + "sourcePath": "toolkits/google_maps/public.md",
25 + "sourceHeading": "Google Maps APIs may require billing and quota management in GCP"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "google_maps",
38 + "platform"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/google-maps-troubleshooting",
42 + "deprecated-geocoding-api-is-not-the-google-maps-toolkit-tool-to-use",
43 + "google-maps-apis-may-require-billing-and-quota-management-in-gcp",
44 + "google-maps-oauth-can-be-blocked-by-sensitive-cloud-platform-scope",
45 + "google-maps-troubleshooting",
46 + "maps-embed-api-requires-api-key-authentication",
47 + "recreate-google-maps-auth-configs-after-default-oauth-app-updates",
48 + "validate-places-includedtypes-against-google-s-supported-place-types"
49 + ],
50 + "relatedGuides": [],
51 + "externalResources": [],
52 + "updatedAt": "2026-06-24",
53 + "lastVerifiedAt": "2026-08-12",
54 + "reviewAfter": "2026-11-10",
55 + "freshness": "evergreen",
56 + "state": "published",
57 + "featured": false
58 +}
docs/kb/guides/toolkits-googleads.json new
+68
@@ -0,0 +1,68 @@
1 +{
2 + "slug": "toolkits-googleads",
3 + "title": "Google Ads",
4 + "description": "Public support knowledge for Google Ads.",
5 + "articlePath": "toolkits-googleads.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googleads/public.md",
9 + "sourceHeading": "Google Ads developer token now belongs on the auth config, not connection initiation"
10 + },
11 + {
12 + "sourcePath": "toolkits/googleads/public.md",
13 + "sourceHeading": "Google Ads API requires both OAuth access token and developer token"
14 + },
15 + {
16 + "sourcePath": "toolkits/googleads/public.md",
17 + "sourceHeading": "Google Ads toolkit versions should be passed without the dashboard `v` prefix"
18 + },
19 + {
20 + "sourcePath": "toolkits/googleads/public.md",
21 + "sourceHeading": "Google Ads MCC/sub-account customer ID targeting is supported"
22 + },
23 + {
24 + "sourcePath": "toolkits/googleads/public.md",
25 + "sourceHeading": "Campaign mutate 400s can be caused by unsupported inline Campaign fields"
26 + },
27 + {
28 + "sourcePath": "toolkits/googleads/public.md",
29 + "sourceHeading": "Google Ads OAuth callback token-exchange failures usually point to incorrect credentials"
30 + },
31 + {
32 + "sourcePath": "toolkits/googleads/public.md",
33 + "sourceHeading": "Custom Google OAuth apps need callback routing through the customer's domain for branded consent"
34 + }
35 + ],
36 + "topics": [
37 + "auth-config",
38 + "authentication",
39 + "errors-and-troubleshooting",
40 + "sessions-and-execution",
41 + "toolkits-and-providers"
42 + ],
43 + "tags": [
44 + "for-you",
45 + "googleads",
46 + "platform"
47 + ],
48 + "aliases": [
49 + "/kb/toolkits/google-ads-troubleshooting",
50 + "custom-google-oauth-apps-need-callback-routing-through-the-customer-s",
51 + "google-ads-campaign-mutate-invalid-argument",
52 + "google-ads-developer-token-belongs-on-the-auth-config",
53 + "google-ads-oauth-callback-token-exchange-failures-usually-point-to-bad",
54 + "google-ads-resource-exhausted-errors",
55 + "google-ads-toolkit-versions-should-be-passed-without-the-dashboard-v-p",
56 + "google-ads-troubleshooting",
57 + "older-sdk-workaround-passed-google-ads-developer-token-and-customer-id",
58 + "target-a-google-ads-sub-account"
59 + ],
60 + "relatedGuides": [],
61 + "externalResources": [],
62 + "updatedAt": "2026-07-14",
63 + "lastVerifiedAt": "2026-08-17",
64 + "reviewAfter": "2026-11-15",
65 + "freshness": "evergreen",
66 + "state": "published",
67 + "featured": false
68 +}
docs/kb/guides/toolkits-googlebigquery.json new
+33
@@ -0,0 +1,33 @@
1 +{
2 + "slug": "toolkits-googlebigquery",
3 + "title": "Google BigQuery",
4 + "description": "Current authentication guidance for the Google BigQuery toolkit.",
5 + "articlePath": "toolkits-googlebigquery.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googlebigquery/public.md",
9 + "sourceHeading": "BigQuery supports managed OAuth2, custom OAuth2, and service-account auth"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "errors-and-troubleshooting",
16 + "toolkits-and-providers"
17 + ],
18 + "tags": [
19 + "for-you",
20 + "googlebigquery",
21 + "oauth",
22 + "platform"
23 + ],
24 + "aliases": [],
25 + "relatedGuides": [],
26 + "externalResources": [],
27 + "updatedAt": "2026-08-17",
28 + "lastVerifiedAt": "2026-08-24",
29 + "reviewAfter": "2026-11-22",
30 + "freshness": "evergreen",
31 + "state": "published",
32 + "featured": false
33 +}
docs/kb/guides/toolkits-googledocs.json new
+76
@@ -0,0 +1,76 @@
1 +{
2 + "slug": "toolkits-googledocs",
3 + "title": "Google Docs",
4 + "description": "Public support knowledge for Google Docs.",
5 + "articlePath": "toolkits-googledocs.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googledocs/public.md",
9 + "sourceHeading": "`GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown and HTML tables"
10 + },
11 + {
12 + "sourcePath": "toolkits/googledocs/public.md",
13 + "sourceHeading": "Google Docs tab-level read and edit is supported by specific Google Docs tools"
14 + },
15 + {
16 + "sourcePath": "toolkits/googledocs/public.md",
17 + "sourceHeading": "Google Docs supports managed and customer-owned OAuth2"
18 + },
19 + {
20 + "sourcePath": "toolkits/googledocs/public.md",
21 + "sourceHeading": "Google sensitive scopes can cause app-blocked errors unless the OAuth app is verified"
22 + },
23 + {
24 + "sourcePath": "toolkits/googledocs/public.md",
25 + "sourceHeading": "Google OAuth tokens are redacted from connected-account responses"
26 + },
27 + {
28 + "sourcePath": "toolkits/googledocs/public.md",
29 + "sourceHeading": "Multiple Google accounts require explicit multi-account selection"
30 + },
31 + {
32 + "sourcePath": "toolkits/googledocs/public.md",
33 + "sourceHeading": "Tool Router v2 sessions require connected accounts to belong to the same user/entity"
34 + },
35 + {
36 + "sourcePath": "toolkits/googledocs/public.md",
37 + "sourceHeading": "Specify Google auth config IDs at session creation so Manage Connection uses the intended configs"
38 + },
39 + {
40 + "sourcePath": "toolkits/googledocs/public.md",
41 + "sourceHeading": "Platform connections are isolated from For You / Connect MCP connections"
42 + }
43 + ],
44 + "topics": [
45 + "auth-config",
46 + "authentication",
47 + "errors-and-troubleshooting",
48 + "sessions-and-execution",
49 + "toolkits-and-providers"
50 + ],
51 + "tags": [
52 + "for-you",
53 + "googledocs",
54 + "platform"
55 + ],
56 + "aliases": [
57 + "/kb/toolkits/google-docs-troubleshooting",
58 + "google-docs-tab-level-read-and-edit-is-supported-by-specific-google-do",
59 + "google-docs-troubleshooting",
60 + "google-sensitive-scopes-can-cause-app-blocked-errors-unless-the-oauth",
61 + "googledocs-create-document-markdown-accepts-github-flavored-markdown-a",
62 + "managed-google-oauth-tokens-stay-redacted-custom-oauth-is-needed-for-r",
63 + "multiple-google-accounts-require-multi-account-support-or-distinct-con",
64 + "platform-connections-are-isolated-from-for-you-connect-mcp-connections",
65 + "specify-google-auth-config-ids-at-session-creation-so-manage-connectio",
66 + "tool-router-v2-sessions-require-connected-accounts-to-belong-to-the-sa"
67 + ],
68 + "relatedGuides": [],
69 + "externalResources": [],
70 + "updatedAt": "2026-06-24",
71 + "lastVerifiedAt": "2026-08-24",
72 + "reviewAfter": "2026-11-22",
73 + "freshness": "evergreen",
74 + "state": "published",
75 + "featured": false
76 +}
docs/kb/guides/toolkits-googledrive.json new
+90
@@ -0,0 +1,90 @@
1 +{
2 + "slug": "toolkits-googledrive",
3 + "title": "Google Drive",
4 + "description": "Public support knowledge for Google Drive.",
5 + "articlePath": "toolkits-googledrive.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googledrive/public.md",
9 + "sourceHeading": "Google Drive upload tools can accept local file paths or URLs through SDK auto file handling"
10 + },
11 + {
12 + "sourcePath": "toolkits/googledrive/public.md",
13 + "sourceHeading": "Connect MCP exposes a curated Google Drive tool set and discovers the rest through meta-tools"
14 + },
15 + {
16 + "sourcePath": "toolkits/googledrive/public.md",
17 + "sourceHeading": "Google Drive watch/change webhooks require a public endpoint"
18 + },
19 + {
20 + "sourcePath": "toolkits/googledrive/public.md",
21 + "sourceHeading": "Google Drive downloads use temporary presigned URLs with configurable URL TTL and short-lived storage"
22 + },
23 + {
24 + "sourcePath": "toolkits/googledrive/public.md",
25 + "sourceHeading": "Disable SDK auto file handling when you need the raw Google Drive download output instead of a local path"
26 + },
27 + {
28 + "sourcePath": "toolkits/googledrive/public.md",
29 + "sourceHeading": "Use customer-owned Google OAuth credentials with verified scopes"
30 + },
31 + {
32 + "sourcePath": "toolkits/googledrive/public.md",
33 + "sourceHeading": "A missing Google Drive tool can be caused by passing an invalid toolkit version"
34 + },
35 + {
36 + "sourcePath": "toolkits/googledrive/public.md",
37 + "sourceHeading": "For a Google Drive file-browser UI, prefer direct tool execution over MCP as the primary integration layer"
38 + },
39 + {
40 + "sourcePath": "toolkits/googledrive/public.md",
41 + "sourceHeading": "Use `GOOGLEDRIVE_GET_ABOUT` to confirm which Google Drive account is connected"
42 + },
43 + {
44 + "sourcePath": "toolkits/googledrive/public.md",
45 + "sourceHeading": "Google Drive tool execution requests should include an `arguments` object, even when it is empty"
46 + },
47 + {
48 + "sourcePath": "toolkits/googledrive/public.md",
49 + "sourceHeading": "Tool Router v2 sessions require all connected accounts to belong to the same entity"
50 + },
51 + {
52 + "sourcePath": "toolkits/googledrive/public.md",
53 + "sourceHeading": "Choose the narrowest Google Drive scope that supports the workflow"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "toolkits-and-providers"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "googledrive",
66 + "platform"
67 + ],
68 + "aliases": [
69 + "/kb/toolkits/google-drive-troubleshooting",
70 + "a-missing-google-drive-tool-can-be-caused-by-passing-an-invalid-toolki",
71 + "disable-sdk-auto-file-handling-when-you-need-the-raw-google-drive-down",
72 + "for-a-google-drive-file-browser-ui-prefer-direct-tool-execution-over-m",
73 + "google-drive-downloads-use-temporary-presigned-urls-with-configurable",
74 + "google-drive-tool-execution-requests-should-include-an-arguments-objec",
75 + "google-drive-troubleshooting",
76 + "google-drive-upload-tools-can-accept-local-file-paths-or-urls-through",
77 + "google-drive-watch-change-webhooks-require-a-public-endpoint",
78 + "managed-google-drive-scope-is-narrow",
79 + "tool-router-v2-sessions-require-all-connected-accounts-to-belong-to-th",
80 + "use-custom-google-oauth-credentials-when-managed-credentials-are-not-v"
81 + ],
82 + "relatedGuides": [],
83 + "externalResources": [],
84 + "updatedAt": "2026-06-24",
85 + "lastVerifiedAt": "2026-08-17",
86 + "reviewAfter": "2026-11-15",
87 + "freshness": "evergreen",
88 + "state": "published",
89 + "featured": false
90 +}
docs/kb/guides/toolkits-googlemeet.json new
+56
@@ -0,0 +1,56 @@
1 +{
2 + "slug": "toolkits-googlemeet",
3 + "title": "Google Meet",
4 + "description": "Public support knowledge for Google Meet.",
5 + "articlePath": "toolkits-googlemeet.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googlemeet/public.md",
9 + "sourceHeading": "Use Google Super tool slugs with a Google Super connected account"
10 + },
11 + {
12 + "sourcePath": "toolkits/googlemeet/public.md",
13 + "sourceHeading": "Configure Meet scopes and enable the Google Meet API before creating Meet spaces"
14 + },
15 + {
16 + "sourcePath": "toolkits/googlemeet/public.md",
17 + "sourceHeading": "Fetch transcript entries by first resolving the conference record"
18 + },
19 + {
20 + "sourcePath": "toolkits/googlemeet/public.md",
21 + "sourceHeading": "403 permission errors usually mean the conference resource is inaccessible or missing"
22 + },
23 + {
24 + "sourcePath": "toolkits/googlemeet/public.md",
25 + "sourceHeading": "Recordings and transcripts require an eligible Google Workspace edition and enabled feature"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "googlemeet",
38 + "platform"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/google-meet-troubleshooting",
42 + "403-permission-errors-usually-mean-the-conference-resource-is-inaccess",
43 + "configure-meet-scopes-and-enable-the-google-meet-api-before-creating-m",
44 + "google-meet-troubleshooting",
45 + "google-workspace-enterprise-is-required-to-record-meetings-and-access",
46 + "use-google-super-tool-slugs-with-a-google-super-connected-account"
47 + ],
48 + "relatedGuides": [],
49 + "externalResources": [],
50 + "updatedAt": "2026-06-24",
51 + "lastVerifiedAt": "2026-08-17",
52 + "reviewAfter": "2026-11-15",
53 + "freshness": "evergreen",
54 + "state": "published",
55 + "featured": false
56 +}
docs/kb/guides/toolkits-googlesheets.json new
+79
@@ -0,0 +1,79 @@
1 +{
2 + "slug": "toolkits-googlesheets",
3 + "title": "Google Sheets",
4 + "description": "Public support knowledge for Google Sheets.",
5 + "articlePath": "toolkits-googlesheets.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googlesheets/public.md",
9 + "sourceHeading": "Platform Google Sheets connections are isolated from For You Connect MCP"
10 + },
11 + {
12 + "sourcePath": "toolkits/googlesheets/public.md",
13 + "sourceHeading": "Fetch more than the default 20 Google Sheets tools with `limit`"
14 + },
15 + {
16 + "sourcePath": "toolkits/googlesheets/public.md",
17 + "sourceHeading": "Google Sheets MCP may require the spreadsheet ID instead of searching by name"
18 + },
19 + {
20 + "sourcePath": "toolkits/googlesheets/public.md",
21 + "sourceHeading": "Use the current values tools to update, append, or create a populated sheet"
22 + },
23 + {
24 + "sourcePath": "toolkits/googlesheets/public.md",
25 + "sourceHeading": "Execute Google Sheets tools by passing the exact tool slug"
26 + },
27 + {
28 + "sourcePath": "toolkits/googlesheets/public.md",
29 + "sourceHeading": "Google Sheets 403s can be caused by an old placeholder toolkit version"
30 + },
31 + {
32 + "sourcePath": "toolkits/googlesheets/public.md",
33 + "sourceHeading": "Use Google Super when one Google connection should cover Gmail, Sheets, Docs, Drive, and other Google tools"
34 + },
35 + {
36 + "sourcePath": "toolkits/googlesheets/public.md",
37 + "sourceHeading": "Use full Google scope URLs such as `https://www.googleapis.com/auth/drive`, not shorthand `/drive`"
38 + },
39 + {
40 + "sourcePath": "toolkits/googlesheets/public.md",
41 + "sourceHeading": "Google Sheets provider quotas are separate from Composio plan limits"
42 + }
43 + ],
44 + "topics": [
45 + "auth-config",
46 + "authentication",
47 + "errors-and-troubleshooting",
48 + "sessions-and-execution",
49 + "toolkits-and-providers"
50 + ],
51 + "tags": [
52 + "for-you",
53 + "googlesheets",
54 + "platform"
55 + ],
56 + "aliases": [
57 + "/kb/authentication/google-sheets-troubleshooting",
58 + "execute-google-sheets-tools-by-passing-the-exact-tool-slug",
59 + "fetch-more-than-the-default-20-google-sheets-tools-with-limit",
60 + "google-sheets-403s-can-be-caused-by-an-old-placeholder-toolkit-version",
61 + "google-sheets-429s-are-google-s-api-quota-and-shared-default-oauth-can",
62 + "google-sheets-auth-configs-require-full-scope-uris",
63 + "google-sheets-mcp-may-require-the-spreadsheet-id-instead-of-searching",
64 + "google-sheets-oauth-cannot-be-scoped-to-a-drive-folder",
65 + "google-sheets-troubleshooting",
66 + "old-google-sheets-integrations-may-need-a-new-integration-to-access-ne",
67 + "platform-google-sheets-connections-are-isolated-from-for-you-connect-m",
68 + "use-google-super-when-one-google-connection-should-cover-gmail-sheets",
69 + "use-googlesheets-batch-update-or-googlesheets-sheet-from-json-to-add-v"
70 + ],
71 + "relatedGuides": [],
72 + "externalResources": [],
73 + "updatedAt": "2026-06-24",
74 + "lastVerifiedAt": "2026-08-17",
75 + "reviewAfter": "2026-11-15",
76 + "freshness": "evergreen",
77 + "state": "published",
78 + "featured": false
79 +}
docs/kb/guides/toolkits-googleslides.json new
+63
@@ -0,0 +1,63 @@
1 +{
2 + "slug": "toolkits-googleslides",
3 + "title": "Google Slides",
4 + "description": "Public support knowledge for Google Slides.",
5 + "articlePath": "toolkits-googleslides.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googleslides/public.md",
9 + "sourceHeading": "Use Google Drive search to list or discover Google Slides presentations"
10 + },
11 + {
12 + "sourcePath": "toolkits/googleslides/public.md",
13 + "sourceHeading": "`GOOGLESLIDES_PRESENTATIONS_GET` needs the presentation ID from the URL or Drive payload"
14 + },
15 + {
16 + "sourcePath": "toolkits/googleslides/public.md",
17 + "sourceHeading": "Use the same Google account when pairing Drive discovery with Google Slides reads"
18 + },
19 + {
20 + "sourcePath": "toolkits/googleslides/public.md",
21 + "sourceHeading": "Google Slide creation tools are available through Google Super"
22 + },
23 + {
24 + "sourcePath": "toolkits/googleslides/public.md",
25 + "sourceHeading": "Custom Google Slides OAuth apps must be verified for sensitive scopes"
26 + },
27 + {
28 + "sourcePath": "toolkits/googleslides/public.md",
29 + "sourceHeading": "Google Slides supports one trigger in Composio"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "googleslides",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/google-slides-troubleshooting",
46 + "custom-google-slides-oauth-apps-must-be-verified-for-sensitive-scopes",
47 + "google-slide-creation-tools-are-available-through-google-super",
48 + "google-slides-may-require-a-custom-oauth-app-instead-of-default-compos",
49 + "google-slides-troubleshooting",
50 + "googledrive-create-file-from-text-cannot-create-native-google-slides-f",
51 + "googleslides-presentations-get-needs-the-presentation-id-from-the-url",
52 + "use-google-drive-search-to-list-or-discover-google-slides-presentation",
53 + "use-the-same-google-account-when-pairing-drive-discovery-with-google-s"
54 + ],
55 + "relatedGuides": [],
56 + "externalResources": [],
57 + "updatedAt": "2026-06-24",
58 + "lastVerifiedAt": "2026-08-12",
59 + "reviewAfter": "2026-11-10",
60 + "freshness": "evergreen",
61 + "state": "published",
62 + "featured": false
63 +}
docs/kb/guides/toolkits-googlesuper.json new
+86
@@ -0,0 +1,86 @@
1 +{
2 + "slug": "toolkits-googlesuper",
3 + "title": "Google Super",
4 + "description": "Public support knowledge for Google Super.",
5 + "articlePath": "toolkits-googlesuper.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googlesuper/public.md",
9 + "sourceHeading": "Google Super is a unified Google Workspace toolkit"
10 + },
11 + {
12 + "sourcePath": "toolkits/googlesuper/public.md",
13 + "sourceHeading": "Google Meet through Google Super needs Meet scopes and Google Meet API enabled"
14 + },
15 + {
16 + "sourcePath": "toolkits/googlesuper/public.md",
17 + "sourceHeading": "Google Super can be narrowed by removing unneeded scopes and tools"
18 + },
19 + {
20 + "sourcePath": "toolkits/googlesuper/public.md",
21 + "sourceHeading": "Gmail filter creation through Google Super also requires `gmail.settings.basic`"
22 + },
23 + {
24 + "sourcePath": "toolkits/googlesuper/public.md",
25 + "sourceHeading": "`GOOGLESUPER_LIST_LABELS` with `include_details=true` can be slow because it fans out per label"
26 + },
27 + {
28 + "sourcePath": "toolkits/googlesuper/public.md",
29 + "sourceHeading": "Gmail thread listing includes `resultSizeEstimate`"
30 + },
31 + {
32 + "sourcePath": "toolkits/googlesuper/public.md",
33 + "sourceHeading": "Use Gmail/Google Super query and label filters to find sent or labeled messages"
34 + },
35 + {
36 + "sourcePath": "toolkits/googlesuper/public.md",
37 + "sourceHeading": "Google Super Sheets 404s can mean wrong spreadsheet ID, missing access, or missing spreadsheet scope"
38 + },
39 + {
40 + "sourcePath": "toolkits/googlesuper/public.md",
41 + "sourceHeading": "`Connection initiation did not complete within 10 minutes` means OAuth consent was not completed, not token refresh failure"
42 + },
43 + {
44 + "sourcePath": "toolkits/googlesuper/public.md",
45 + "sourceHeading": "Google users can deselect scopes during consent; Composio marks active if token exchange succeeds"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "googlesuper",
58 + "platform"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/google-super-troubleshooting",
62 + "connection-initiation-did-not-complete-within-10-minutes-means-oauth-c",
63 + "gmail-filter-creation-through-google-super-also-requires-gmail-setting",
64 + "google-meet-through-google-super-needs-meet-scopes-and-google-meet-api",
65 + "google-super-can-be-narrowed-by-removing-unneeded-scopes-and-tools",
66 + "google-super-cannot-schedule-gmail-emails-out-of-the-box",
67 + "google-super-is-a-unified-google-workspace-toolkit",
68 + "google-super-sheets-404s-can-mean-wrong-spreadsheet-id-missing-access",
69 + "google-super-troubleshooting",
70 + "google-users-can-deselect-scopes-during-consent-composio-marks-active",
71 + "googlesuper-list-labels-with-include-details-true-can-be-slow-because",
72 + "googlesuper-list-threads-verbose-behavior-trades-payload-latency-for-d",
73 + "managed-google-super-oauth-issues-can-be-unblocked-by-switching-to-a-c",
74 + "missing-google-super-endpoints-should-be-filed-as-tool-requests-not-to",
75 + "resultsizeestimate-was-added-to-gmail-thread-listing-response",
76 + "use-gmail-google-super-query-and-label-filters-to-find-sent-or-labeled"
77 + ],
78 + "relatedGuides": [],
79 + "externalResources": [],
80 + "updatedAt": "2026-06-24",
81 + "lastVerifiedAt": "2026-08-17",
82 + "reviewAfter": "2026-11-15",
83 + "freshness": "evergreen",
84 + "state": "published",
85 + "featured": false
86 +}
docs/kb/guides/toolkits-googletasks.json new
+63
@@ -0,0 +1,63 @@
1 +{
2 + "slug": "toolkits-googletasks",
3 + "title": "Google Tasks",
4 + "description": "Public OAuth, connection, and quota troubleshooting for Google Tasks.",
5 + "articlePath": "toolkits-googletasks.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/googletasks/public.md",
9 + "sourceHeading": "Set up custom Google OAuth credentials"
10 + },
11 + {
12 + "sourcePath": "toolkits/googletasks/public.md",
13 + "sourceHeading": "Resolve an \"App is blocked\" connection error"
14 + },
15 + {
16 + "sourcePath": "toolkits/googletasks/public.md",
17 + "sourceHeading": "Enable the Google Tasks API for custom OAuth"
18 + },
19 + {
20 + "sourcePath": "toolkits/googletasks/public.md",
21 + "sourceHeading": "Resolve `Error 400: invalid_scope`"
22 + },
23 + {
24 + "sourcePath": "toolkits/googletasks/public.md",
25 + "sourceHeading": "Choose managed or customer-owned Google OAuth"
26 + },
27 + {
28 + "sourcePath": "toolkits/googletasks/public.md",
29 + "sourceHeading": "Resolve 401 errors on tool calls"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "googletasks",
42 + "oauth",
43 + "platform",
44 + "quotas",
45 + "scopes"
46 + ],
47 + "aliases": [
48 + "/kb/toolkits/google-tasks-troubleshooting",
49 + "enable-the-google-tasks-api-for-custom-oauth",
50 + "google-tasks-troubleshooting",
51 + "handle-quota-or-rate-limit-exhaustion",
52 + "resolve-error-400-invalid-scope-2",
53 + "set-up-custom-google-oauth-credentials-2"
54 + ],
55 + "relatedGuides": [],
56 + "externalResources": [],
57 + "updatedAt": "2026-07-24",
58 + "lastVerifiedAt": "2026-08-24",
59 + "reviewAfter": "2026-11-22",
60 + "freshness": "evergreen",
61 + "state": "published",
62 + "featured": false
63 +}
docs/kb/guides/toolkits-granola-mcp.json new
+36
@@ -0,0 +1,36 @@
1 +{
2 + "slug": "toolkits-granola-mcp",
3 + "title": "Granola MCP",
4 + "description": "Public behavior and schema guidance for the official Granola MCP server.",
5 + "articlePath": "toolkits-granola-mcp.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/granola_mcp/public.md",
9 + "sourceHeading": "Composio mirrors Granola's official MCP server"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "granola",
20 + "mcp",
21 + "platform",
22 + "schemas"
23 + ],
24 + "aliases": [
25 + "/kb/toolkits/granola-mcp-metadata-comes-from-the-upstream-server",
26 + "granola-mcp-metadata-comes-from-the-upstream-server"
27 + ],
28 + "relatedGuides": [],
29 + "externalResources": [],
30 + "updatedAt": "2026-07-14",
31 + "lastVerifiedAt": "2026-08-17",
32 + "reviewAfter": "2026-11-15",
33 + "freshness": "evergreen",
34 + "state": "published",
35 + "featured": false
36 +}
docs/kb/guides/toolkits-hubspot.json new
+98
@@ -0,0 +1,98 @@
1 +{
2 + "slug": "toolkits-hubspot",
3 + "title": "HubSpot",
4 + "description": "Public support knowledge for HubSpot.",
5 + "articlePath": "toolkits-hubspot.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/hubspot/public.md",
9 + "sourceHeading": "Minimum HubSpot contact scopes are contact read/write"
10 + },
11 + {
12 + "sourcePath": "toolkits/hubspot/public.md",
13 + "sourceHeading": "Use Composio scopes API or HubSpot docs to find required HubSpot scopes"
14 + },
15 + {
16 + "sourcePath": "toolkits/hubspot/public.md",
17 + "sourceHeading": "Create custom HubSpot tools through toolkit-authenticated API requests"
18 + },
19 + {
20 + "sourcePath": "toolkits/hubspot/public.md",
21 + "sourceHeading": "HubSpot trigger setup needs the HubSpot app ID"
22 + },
23 + {
24 + "sourcePath": "toolkits/hubspot/public.md",
25 + "sourceHeading": "Use custom HubSpot credentials for white-label auth"
26 + },
27 + {
28 + "sourcePath": "toolkits/hubspot/public.md",
29 + "sourceHeading": "HubSpot scopes must be predeclared in the HubSpot app config"
30 + },
31 + {
32 + "sourcePath": "toolkits/hubspot/public.md",
33 + "sourceHeading": "HubSpot OAuth token-fetch 400: check client secret and required-scope alignment"
34 + },
35 + {
36 + "sourcePath": "toolkits/hubspot/public.md",
37 + "sourceHeading": "Old HubSpot SDK/toolkit versions use old double-prefixed slugs"
38 + },
39 + {
40 + "sourcePath": "toolkits/hubspot/public.md",
41 + "sourceHeading": "HubSpot auth loops can be caused by HubSpot-side workspace/login state"
42 + },
43 + {
44 + "sourcePath": "toolkits/hubspot/public.md",
45 + "sourceHeading": "HubSpot marketing campaign objects do not expose a properties API like CRM objects"
46 + },
47 + {
48 + "sourcePath": "toolkits/hubspot/public.md",
49 + "sourceHeading": "HubSpot triggers require each customer’s own app ID and developer API key"
50 + },
51 + {
52 + "sourcePath": "toolkits/hubspot/public.md",
53 + "sourceHeading": "Deleting a HubSpot connected account disconnects it and stops token refresh"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "toolkits-and-providers"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "hubspot",
66 + "platform"
67 + ],
68 + "aliases": [
69 + "/kb/authentication/hubspot-troubleshooting",
70 + "/kb/toolkits/after-hubspot-trigger-fixes-recreate-old-triggers",
71 + "after-hubspot-trigger-fixes-recreate-old-triggers",
72 + "composio-does-not-provide-hubspot-field-level-permissions-restrict-by",
73 + "create-custom-hubspot-tools-through-toolkit-authenticated-api-requests",
74 + "fix-hubspot-oauth-token-exchange-400-client-secret-and-scopes",
75 + "hubspot-auth-loops-can-be-caused-by-hubspot-side-workspace-login-state",
76 + "hubspot-managed-oauth-app-unverified-warning-has-no-reliable-eta-byoa",
77 + "hubspot-marketing-campaign-objects-do-not-expose-a-properties-api-like",
78 + "hubspot-scopes-must-be-predeclared-in-the-hubspot-app-config",
79 + "hubspot-trigger-setup-needs-the-hubspot-app-id",
80 + "hubspot-triggers-require-each-customer-s-own-app-id-and-developer-api",
81 + "hubspot-troubleshooting",
82 + "minimum-hubspot-contact-scopes-are-contact-read-write",
83 + "some-hubspot-scopes-are-not-in-composio-managed-auth-use-own-oauth-app",
84 + "use-composio-scopes-api-or-hubspot-docs-to-find-required-hubspot-scope",
85 + "use-custom-hubspot-credentials-for-white-label-auth"
86 + ],
87 + "relatedGuides": [],
88 + "externalResources": [],
89 + "updatedAt": "2026-06-24",
90 + "lastVerifiedAt": "2026-08-12",
91 + "reviewAfter": "2026-11-10",
92 + "freshness": "evergreen",
93 + "state": "published",
94 + "featured": false,
95 + "verifyIgnoreToolSlugs": [
96 + "HUBSPOT_HUBSPOT_LIST_CONTACTS"
97 + ]
98 +}
docs/kb/guides/toolkits-instagram.json new
+84
@@ -0,0 +1,84 @@
1 +{
2 + "slug": "toolkits-instagram",
3 + "title": "Instagram",
4 + "description": "Public support knowledge for Instagram.",
5 + "articlePath": "toolkits-instagram.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/instagram/public.md",
9 + "sourceHeading": "Instagram OAuth tokens are bound to the account selected in Facebook Login"
10 + },
11 + {
12 + "sourcePath": "toolkits/instagram/public.md",
13 + "sourceHeading": "Instagram uses Business Login and only supported/verified scopes should be configured"
14 + },
15 + {
16 + "sourcePath": "toolkits/instagram/public.md",
17 + "sourceHeading": "Instagram toolkit requires a Business/Creator account for supported business features"
18 + },
19 + {
20 + "sourcePath": "toolkits/instagram/public.md",
21 + "sourceHeading": "Use `INSTAGRAM_LIST_ALL_MESSAGES` to fetch Instagram messages"
22 + },
23 + {
24 + "sourcePath": "toolkits/instagram/public.md",
25 + "sourceHeading": "Instagram DM send failures with code 10/subcode 2534022 are Meta's 24-hour messaging window"
26 + },
27 + {
28 + "sourcePath": "toolkits/instagram/public.md",
29 + "sourceHeading": "For custom Instagram/Meta OAuth, configure the redirect URI in the Meta app"
30 + },
31 + {
32 + "sourcePath": "toolkits/instagram/public.md",
33 + "sourceHeading": "For Instagram DMs via n8n/Claude, Connect MCP can simplify setup"
34 + },
35 + {
36 + "sourcePath": "toolkits/instagram/public.md",
37 + "sourceHeading": "`INSTAGRAM_POST_IG_MEDIA_COMMENTS` failures can be caused by an incorrect `ig_media_id`"
38 + },
39 + {
40 + "sourcePath": "toolkits/instagram/public.md",
41 + "sourceHeading": "Instagram is available as a toolkit and can be connected via a new authConfig"
42 + },
43 + {
44 + "sourcePath": "toolkits/instagram/public.md",
45 + "sourceHeading": "Publish local media with `image_file` or `video_file`"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "instagram",
58 + "platform"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/instagram-troubleshooting",
62 + "for-custom-instagram-meta-oauth-configure-the-redirect-uri-in-the-meta",
63 + "for-instagram-dms-via-n8n-claude-connect-mcp-can-simplify-setup",
64 + "instagram-dm-send-failures-with-code-10-subcode-2534022-are-meta-s-24",
65 + "instagram-is-available-as-a-toolkit-and-can-be-connected-via-a-new-aut",
66 + "instagram-oauth-tokens-are-bound-to-the-account-selected-in-facebook-l",
67 + "instagram-post-ig-media-comments-failures-can-be-caused-by-an-incorrec",
68 + "instagram-reply-to-comment-may-require-a-scope-not-available-in-the-ma",
69 + "instagram-toolkit-requires-a-business-creator-account-for-supported-bu",
70 + "instagram-troubleshooting",
71 + "instagram-uses-business-login-and-only-supported-verified-scopes-shoul",
72 + "stage-local-instagram-media-before-publishing",
73 + "use-instagram-list-all-messages-to-fetch-instagram-messages",
74 + "use-your-own-meta-oauth-app-for-high-volume-instagram-production-usage"
75 + ],
76 + "relatedGuides": [],
77 + "externalResources": [],
78 + "updatedAt": "2026-07-14",
79 + "lastVerifiedAt": "2026-08-12",
80 + "reviewAfter": "2026-11-10",
81 + "freshness": "evergreen",
82 + "state": "published",
83 + "featured": false
84 +}
docs/kb/guides/toolkits-intercom.json new
+48
@@ -0,0 +1,48 @@
1 +{
2 + "slug": "toolkits-intercom",
3 + "title": "Intercom",
4 + "description": "Public support knowledge for Intercom.",
5 + "articlePath": "toolkits-intercom.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/intercom/public.md",
9 + "sourceHeading": "Use External Pages or a custom agent when connecting MCP knowledge to Intercom Fin"
10 + },
11 + {
12 + "sourcePath": "toolkits/intercom/public.md",
13 + "sourceHeading": "INTERCOM_LIST_ALL_COMPANIES per_page limit is 60"
14 + },
15 + {
16 + "sourcePath": "toolkits/intercom/public.md",
17 + "sourceHeading": "Update Python SDK packages when Intercom tool schemas fail on reserved parameter names"
18 + }
19 + ],
20 + "topics": [
21 + "errors-and-troubleshooting",
22 + "sessions-and-execution",
23 + "toolkits-and-providers"
24 + ],
25 + "tags": [
26 + "for-you",
27 + "intercom",
28 + "platform"
29 + ],
30 + "aliases": [
31 + "/kb/toolkits/intercom-troubleshooting",
32 + "avoid-proxy-execute-for-slow-intercom-api-calls-that-can-hit-cloudflar",
33 + "intercom-list-all-companies-per-page-limit-is-60",
34 + "intercom-oauth-tokens-cannot-be-programmatically-revoked-by-composio",
35 + "intercom-troubleshooting",
36 + "update-python-sdk-packages-when-intercom-tool-schemas-fail-on-reserved",
37 + "use-a-custom-intercom-developer-app-if-composio-s-hosted-oauth-app-is",
38 + "use-external-pages-or-a-custom-agent-when-connecting-mcp-knowledge-to"
39 + ],
40 + "relatedGuides": [],
41 + "externalResources": [],
42 + "updatedAt": "2026-06-24",
43 + "lastVerifiedAt": "2026-08-12",
44 + "reviewAfter": "2026-11-10",
45 + "freshness": "evergreen",
46 + "state": "published",
47 + "featured": false
48 +}
docs/kb/guides/toolkits-jira.json new
+83
@@ -0,0 +1,83 @@
1 +{
2 + "slug": "toolkits-jira",
3 + "title": "Jira",
4 + "description": "Public support knowledge for Jira.",
5 + "articlePath": "toolkits-jira.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/jira/public.md",
9 + "sourceHeading": "Keep Jira OAuth scopes within Atlassian's supported set"
10 + },
11 + {
12 + "sourcePath": "toolkits/jira/public.md",
13 + "sourceHeading": "Pin custom Jira authConfig when creating Tool Router sessions"
14 + },
15 + {
16 + "sourcePath": "toolkits/jira/public.md",
17 + "sourceHeading": "Jira custom token execution needs the Atlassian base URL/subdomain"
18 + },
19 + {
20 + "sourcePath": "toolkits/jira/public.md",
21 + "sourceHeading": "Jira search pagination tokens returned by current tools preserve search context"
22 + },
23 + {
24 + "sourcePath": "toolkits/jira/public.md",
25 + "sourceHeading": "Jira OAuth redirect URI must match the authConfig and Atlassian app"
26 + },
27 + {
28 + "sourcePath": "toolkits/jira/public.md",
29 + "sourceHeading": "Missing `audience=api.atlassian.com` can prevent Jira refresh tokens"
30 + },
31 + {
32 + "sourcePath": "toolkits/jira/public.md",
33 + "sourceHeading": "Use `JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS` instead of deprecated create metadata behavior"
34 + },
35 + {
36 + "sourcePath": "toolkits/jira/public.md",
37 + "sourceHeading": "Download Jira attachments with `JIRA_GET_ATTACHMENT`"
38 + },
39 + {
40 + "sourcePath": "toolkits/jira/public.md",
41 + "sourceHeading": "Jira tool-call payload retention follows the project log-storage setting"
42 + },
43 + {
44 + "sourcePath": "toolkits/jira/public.md",
45 + "sourceHeading": "Jira service account use requires customer-owned credentials and scopes"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "jira",
58 + "platform"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop",
62 + "/kb/toolkits/jira-troubleshooting",
63 + "composio-manages-jira-oauth-tokens-but-does-not-store-jira-api-respons",
64 + "download-jira-attachments-with-jira-get-attachment",
65 + "jira-credentials-expire-without-refresh",
66 + "jira-custom-token-execution-needs-the-atlassian-base-url-subdomain",
67 + "jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop",
68 + "jira-oauth-redirect-uri-must-match-the-authconfig-and-atlassian-app",
69 + "jira-search-pagination-token-requires-the-original-jql-or-filters",
70 + "jira-service-account-use-requires-customer-owned-credentials-and-scope",
71 + "jira-troubleshooting",
72 + "pin-custom-jira-authconfig-when-creating-tool-router-sessions",
73 + "use-jira-get-create-metadata-issue-type-fields-instead-of-deprecated-c"
74 + ],
75 + "relatedGuides": [],
76 + "externalResources": [],
77 + "updatedAt": "2026-07-16",
78 + "lastVerifiedAt": "2026-08-12",
79 + "reviewAfter": "2026-11-10",
80 + "freshness": "evergreen",
81 + "state": "published",
82 + "featured": false
83 +}
docs/kb/guides/toolkits-kickbox.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "toolkits-kickbox",
3 + "title": "Kickbox",
4 + "description": "Public support knowledge for Kickbox.",
5 + "articlePath": "toolkits-kickbox.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/kickbox/public.md",
9 + "sourceHeading": "Single verification auth and EU endpoint checks"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "sessions-and-execution",
16 + "toolkits-and-providers"
17 + ],
18 + "tags": [
19 + "for-you",
20 + "kickbox",
21 + "platform"
22 + ],
23 + "aliases": [],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-06-24",
27 + "lastVerifiedAt": "2026-08-12",
28 + "reviewAfter": "2026-11-10",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/toolkits-klaviyo.json new
+31
@@ -0,0 +1,31 @@
1 +{
2 + "slug": "toolkits-klaviyo",
3 + "title": "Klaviyo",
4 + "description": "Public support knowledge for Klaviyo.",
5 + "articlePath": "toolkits-klaviyo.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/klaviyo/public.md",
9 + "sourceHeading": "Klaviyo schema keys that exceeded Claude's 64-character limit were fixed"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "klaviyo",
20 + "platform"
21 + ],
22 + "aliases": [],
23 + "relatedGuides": [],
24 + "externalResources": [],
25 + "updatedAt": "2026-06-24",
26 + "lastVerifiedAt": "2026-08-12",
27 + "reviewAfter": "2026-11-10",
28 + "freshness": "evergreen",
29 + "state": "published",
30 + "featured": false
31 +}
docs/kb/guides/toolkits-kommo.json new
+36
@@ -0,0 +1,36 @@
1 +{
2 + "slug": "toolkits-kommo",
3 + "title": "Kommo",
4 + "description": "Public authentication and subdomain troubleshooting for Kommo.",
5 + "articlePath": "toolkits-kommo.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/kommo/public.md",
9 + "sourceHeading": "Enter only the Kommo account subdomain"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "kommo",
20 + "oauth",
21 + "platform",
22 + "subdomain"
23 + ],
24 + "aliases": [
25 + "/kb/toolkits/enter-only-the-kommo-account-subdomain",
26 + "enter-only-the-kommo-account-subdomain"
27 + ],
28 + "relatedGuides": [],
29 + "externalResources": [],
30 + "updatedAt": "2026-07-24",
31 + "lastVerifiedAt": "2026-08-12",
32 + "reviewAfter": "2026-11-10",
33 + "freshness": "evergreen",
34 + "state": "published",
35 + "featured": false
36 +}
docs/kb/guides/toolkits-launch-darkly.json new
+41
@@ -0,0 +1,41 @@
1 +{
2 + "slug": "toolkits-launch-darkly",
3 + "title": "LaunchDarkly",
4 + "description": "Public support knowledge for LaunchDarkly.",
5 + "articlePath": "toolkits-launch-darkly.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/launch_darkly/public.md",
9 + "sourceHeading": "LaunchDarkly currently uses a REST API access token"
10 + },
11 + {
12 + "sourcePath": "toolkits/launch_darkly/public.md",
13 + "sourceHeading": "OAuth client actions operate after toolkit authentication"
14 + }
15 + ],
16 + "topics": [
17 + "authentication",
18 + "errors-and-troubleshooting",
19 + "sessions-and-execution",
20 + "toolkits-and-providers"
21 + ],
22 + "tags": [
23 + "for-you",
24 + "launch_darkly",
25 + "platform"
26 + ],
27 + "aliases": [
28 + "/kb/toolkits/launchdarkly-troubleshooting",
29 + "feasibility-notes",
30 + "launchdarkly-troubleshooting",
31 + "oauth-client-actions-are-not-oauth-connection-support"
32 + ],
33 + "relatedGuides": [],
34 + "externalResources": [],
35 + "updatedAt": "2026-06-24",
36 + "lastVerifiedAt": "2026-08-17",
37 + "reviewAfter": "2026-11-15",
38 + "freshness": "evergreen",
39 + "state": "published",
40 + "featured": false
41 +}
docs/kb/guides/toolkits-linear.json new
+36
@@ -0,0 +1,36 @@
1 +{
2 + "slug": "toolkits-linear",
3 + "title": "Linear",
4 + "description": "Public trigger configuration guidance for Linear.",
5 + "articlePath": "toolkits-linear.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/linear/public.md",
9 + "sourceHeading": "Linear triggers require a valid `team_id`"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "linear",
20 + "platform",
21 + "team_id",
22 + "triggers"
23 + ],
24 + "aliases": [
25 + "/kb/toolkits/linear-triggers-require-a-valid-team-id",
26 + "linear-triggers-require-a-valid-team-id"
27 + ],
28 + "relatedGuides": [],
29 + "externalResources": [],
30 + "updatedAt": "2026-07-24",
31 + "lastVerifiedAt": "2026-08-12",
32 + "reviewAfter": "2026-11-10",
33 + "freshness": "evergreen",
34 + "state": "published",
35 + "featured": false
36 +}
docs/kb/guides/toolkits-linkedin.json new
+68
@@ -0,0 +1,68 @@
1 +{
2 + "slug": "toolkits-linkedin",
3 + "title": "LinkedIn",
4 + "description": "Public support knowledge for LinkedIn.",
5 + "articlePath": "toolkits-linkedin.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/linkedin/public.md",
9 + "sourceHeading": "Fix LinkedIn 426 NONEXISTENT_VERSION by using the latest toolkit version"
10 + },
11 + {
12 + "sourcePath": "toolkits/linkedin/public.md",
13 + "sourceHeading": "Fetch modern LinkedIn tools with `toolkit_slug=linkedin` and `toolkit_versions=latest`"
14 + },
15 + {
16 + "sourcePath": "toolkits/linkedin/public.md",
17 + "sourceHeading": "LinkedIn organization scopes depend on the toolkit and auth config"
18 + },
19 + {
20 + "sourcePath": "toolkits/linkedin/public.md",
21 + "sourceHeading": "LinkedIn post creation supports image arrays through SDK/API"
22 + },
23 + {
24 + "sourcePath": "toolkits/linkedin/public.md",
25 + "sourceHeading": "Use Connect MCP instead of legacy Platform MCP for consumer LinkedIn connector flows"
26 + },
27 + {
28 + "sourcePath": "toolkits/linkedin/public.md",
29 + "sourceHeading": "Fix LinkedIn Ads `redirect_uri` mismatch before debugging scopes"
30 + },
31 + {
32 + "sourcePath": "toolkits/linkedin/public.md",
33 + "sourceHeading": "LinkedIn Ads `unauthorized_scope_error` means a requested scope is unavailable"
34 + }
35 + ],
36 + "topics": [
37 + "auth-config",
38 + "authentication",
39 + "errors-and-troubleshooting",
40 + "sessions-and-execution",
41 + "toolkits-and-providers"
42 + ],
43 + "tags": [
44 + "for-you",
45 + "linkedin",
46 + "platform"
47 + ],
48 + "aliases": [
49 + "/kb/toolkits/linkedin-troubleshooting",
50 + "fetch-modern-linkedin-tools-with-toolkit-slug-linkedin-and-toolkit-ver",
51 + "fix-linkedin-426-nonexistent-version",
52 + "fix-linkedin-ads-redirect-uri-mismatch-before-debugging-scopes",
53 + "linkedin-ads-unauthorized-scope-error-means-a-requested-scope-is-unava",
54 + "linkedin-company-actions-require-organization-scopes",
55 + "linkedin-get-company-info-currently-returns-one-company-profile",
56 + "linkedin-post-creation-supports-image-arrays-through-sdk-api",
57 + "linkedin-troubleshooting",
58 + "use-connect-mcp-instead-of-legacy-platform-mcp-for-consumer-linkedin-c"
59 + ],
60 + "relatedGuides": [],
61 + "externalResources": [],
62 + "updatedAt": "2026-07-16",
63 + "lastVerifiedAt": "2026-08-12",
64 + "reviewAfter": "2026-11-10",
65 + "freshness": "evergreen",
66 + "state": "published",
67 + "featured": false
68 +}
docs/kb/guides/toolkits-mailchimp.json new
+56
@@ -0,0 +1,56 @@
1 +{
2 + "slug": "toolkits-mailchimp",
3 + "title": "Mailchimp",
4 + "description": "Public support knowledge for Mailchimp.",
5 + "articlePath": "toolkits-mailchimp.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/mailchimp/public.md",
9 + "sourceHeading": "Mailchimp server prefix is the URL prefix before .admin.mailchimp.com"
10 + },
11 + {
12 + "sourcePath": "toolkits/mailchimp/public.md",
13 + "sourceHeading": "Use subdomain or dc, not server_prefix, for Mailchimp connectionConfig"
14 + },
15 + {
16 + "sourcePath": "toolkits/mailchimp/public.md",
17 + "sourceHeading": "Some Mailchimp tools require at least the Mailchimp Essentials plan"
18 + },
19 + {
20 + "sourcePath": "toolkits/mailchimp/public.md",
21 + "sourceHeading": "Mailchimp Proxy Execute with raw access token also needs subdomain"
22 + },
23 + {
24 + "sourcePath": "toolkits/mailchimp/public.md",
25 + "sourceHeading": "Mailchimp has trigger support in the supported-trigger toolkit list"
26 + }
27 + ],
28 + "topics": [
29 + "authentication",
30 + "errors-and-troubleshooting",
31 + "sessions-and-execution",
32 + "toolkits-and-providers"
33 + ],
34 + "tags": [
35 + "for-you",
36 + "mailchimp",
37 + "platform"
38 + ],
39 + "aliases": [
40 + "/kb/toolkits/mailchimp-troubleshooting",
41 + "mailchimp-has-trigger-support-in-the-supported-trigger-toolkit-list",
42 + "mailchimp-proxy-execute-with-raw-access-token-also-needs-subdomain",
43 + "mailchimp-server-prefix-is-the-url-prefix-before-admin-mailchimp-com",
44 + "mailchimp-troubleshooting",
45 + "some-mailchimp-tools-require-at-least-the-mailchimp-essentials-plan",
46 + "use-subdomain-or-dc-not-server-prefix-for-mailchimp-connectionconfig"
47 + ],
48 + "relatedGuides": [],
49 + "externalResources": [],
50 + "updatedAt": "2026-06-24",
51 + "lastVerifiedAt": "2026-08-12",
52 + "reviewAfter": "2026-11-10",
53 + "freshness": "evergreen",
54 + "state": "published",
55 + "featured": false
56 +}
docs/kb/guides/toolkits-marketstack.json new
+31
@@ -0,0 +1,31 @@
1 +{
2 + "slug": "toolkits-marketstack",
3 + "title": "Marketstack",
4 + "description": "Public support knowledge for Marketstack.",
5 + "articlePath": "toolkits-marketstack.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/marketstack/public.md",
9 + "sourceHeading": "API Coverage"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "marketstack",
20 + "platform"
21 + ],
22 + "aliases": [],
23 + "relatedGuides": [],
24 + "externalResources": [],
25 + "updatedAt": "2026-06-24",
26 + "lastVerifiedAt": "2026-08-12",
27 + "reviewAfter": "2026-11-10",
28 + "freshness": "evergreen",
29 + "state": "published",
30 + "featured": false
31 +}
docs/kb/guides/toolkits-microsoft-teams.json new
+84
@@ -0,0 +1,84 @@
1 +{
2 + "slug": "toolkits-microsoft-teams",
3 + "title": "Microsoft Teams",
4 + "description": "Public support knowledge for Microsoft Teams.",
5 + "articlePath": "toolkits-microsoft-teams.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/microsoft_teams/public.md",
9 + "sourceHeading": "Microsoft Teams delegated permissions should be checked with `get_scopes_required` and `toolkit_versions[microsoft_teams]=latest`"
10 + },
11 + {
12 + "sourcePath": "toolkits/microsoft_teams/public.md",
13 + "sourceHeading": "Invalid OAuth scope: `ChannelMessage.Read.Group`"
14 + },
15 + {
16 + "sourcePath": "toolkits/microsoft_teams/public.md",
17 + "sourceHeading": "`MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` and `MICROSOFT_TEAMS_CREATE_MEETING` can work with delegated user scopes"
18 + },
19 + {
20 + "sourcePath": "toolkits/microsoft_teams/public.md",
21 + "sourceHeading": "Microsoft Teams often needs customer-owned Azure OAuth credentials and tenant admin consent"
22 + },
23 + {
24 + "sourcePath": "toolkits/microsoft_teams/public.md",
25 + "sourceHeading": "Microsoft Teams one-on-one chat creation needs two users and correct OData bind format"
26 + },
27 + {
28 + "sourcePath": "toolkits/microsoft_teams/public.md",
29 + "sourceHeading": "Microsoft Teams MCP access is tied to the connected account `user_id` used in the MCP URL"
30 + },
31 + {
32 + "sourcePath": "toolkits/microsoft_teams/public.md",
33 + "sourceHeading": "Teams chat tools return 400/403/404 when user IDs or chat membership do not match Microsoft Graph expectations"
34 + },
35 + {
36 + "sourcePath": "toolkits/microsoft_teams/public.md",
37 + "sourceHeading": "Microsoft Teams tool listing may return only 20 tools unless `limit` is increased"
38 + },
39 + {
40 + "sourcePath": "toolkits/microsoft_teams/public.md",
41 + "sourceHeading": "Some Microsoft Teams slugs were restored as deprecated aliases with replacement descriptions"
42 + },
43 + {
44 + "sourcePath": "toolkits/microsoft_teams/public.md",
45 + "sourceHeading": "Tool Router memory for Microsoft Teams should be a list under the toolkit key"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "microsoft_teams",
58 + "platform"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/microsoft-teams-troubleshooting",
62 + "microsoft-teams-chats-get-all-chats-and-microsoft-teams-create-meeting",
63 + "microsoft-teams-delegated-permissions-should-be-checked-with-get-scope",
64 + "microsoft-teams-mcp-access-is-tied-to-the-connected-account-user-id-us",
65 + "microsoft-teams-often-needs-customer-owned-azure-oauth-credentials-and",
66 + "microsoft-teams-one-on-one-chat-creation-needs-two-users-and-correct-o",
67 + "microsoft-teams-tool-listing-may-return-only-20-tools-unless-limit-is",
68 + "microsoft-teams-troubleshooting",
69 + "some-microsoft-teams-slugs-were-restored-as-deprecated-aliases-with-re",
70 + "teams-chat-tools-return-400-403-404-when-user-ids-or-chat-membership-d",
71 + "tool-router-memory-for-microsoft-teams-should-be-a-list-under-the-tool"
72 + ],
73 + "relatedGuides": [],
74 + "externalResources": [],
75 + "updatedAt": "2026-06-24",
76 + "lastVerifiedAt": "2026-08-17",
77 + "reviewAfter": "2026-11-15",
78 + "freshness": "evergreen",
79 + "state": "published",
80 + "featured": false,
81 + "verifyIgnoreToolSlugs": [
82 + "MICROSOFT_TEAMS_TEAMS_GET_MESSAGE"
83 + ]
84 +}
docs/kb/guides/toolkits-monday.json new
+63
@@ -0,0 +1,63 @@
1 +{
2 + "slug": "toolkits-monday",
3 + "title": "Monday",
4 + "description": "Public support knowledge for Monday.",
5 + "articlePath": "toolkits-monday.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/monday/public.md",
9 + "sourceHeading": "Monday requires the OAuth app to be installed in the workspace before user connections"
10 + },
11 + {
12 + "sourcePath": "toolkits/monday/public.md",
13 + "sourceHeading": "Add the Composio redirect URL to the Monday OAuth app"
14 + },
15 + {
16 + "sourcePath": "toolkits/monday/public.md",
17 + "sourceHeading": "`MONDAY_UPDATE_ITEM` body must be passed as a properly escaped string"
18 + },
19 + {
20 + "sourcePath": "toolkits/monday/public.md",
21 + "sourceHeading": "Tool Router may prefer `MONDAY_MCP` over `MONDAY` when both are available"
22 + },
23 + {
24 + "sourcePath": "toolkits/monday/public.md",
25 + "sourceHeading": "Monday scopes come from the OAuth app and do not need separate Composio-side setup in the common flow"
26 + },
27 + {
28 + "sourcePath": "toolkits/monday/public.md",
29 + "sourceHeading": "Monday trigger management is not handled by the agent at runtime"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "monday",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/monday-troubleshooting",
46 + "add-the-composio-redirect-url-to-the-monday-oauth-app",
47 + "monday-requires-the-oauth-app-to-be-installed-in-the-workspace-before",
48 + "monday-scopes-come-from-the-oauth-app-and-do-not-need-separate-composi",
49 + "monday-troubleshooting",
50 + "monday-update-item-body-must-be-passed-as-a-properly-escaped-string"
51 + ],
52 + "relatedGuides": [],
53 + "externalResources": [],
54 + "updatedAt": "2026-06-24",
55 + "lastVerifiedAt": "2026-08-12",
56 + "reviewAfter": "2026-11-10",
57 + "freshness": "evergreen",
58 + "state": "published",
59 + "featured": false,
60 + "verifyIgnoreToolSlugs": [
61 + "MONDAY_MCP"
62 + ]
63 +}
docs/kb/guides/toolkits-netsuite.json new
+34
@@ -0,0 +1,34 @@
1 +{
2 + "slug": "toolkits-netsuite",
3 + "title": "NetSuite",
4 + "description": "Public support knowledge for NetSuite.",
5 + "articlePath": "toolkits-netsuite.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/netsuite/public.md",
9 + "sourceHeading": "NetSuite OAuth token exchange failures can be caused by generic OAuth endpoints"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "netsuite",
20 + "platform"
21 + ],
22 + "aliases": [
23 + "/kb/toolkits/netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth",
24 + "netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth"
25 + ],
26 + "relatedGuides": [],
27 + "externalResources": [],
28 + "updatedAt": "2026-06-24",
29 + "lastVerifiedAt": "2026-08-12",
30 + "reviewAfter": "2026-11-10",
31 + "freshness": "evergreen",
32 + "state": "published",
33 + "featured": false
34 +}
docs/kb/guides/toolkits-notion.json new
+70
@@ -0,0 +1,70 @@
1 +{
2 + "slug": "toolkits-notion",
3 + "title": "Notion",
4 + "description": "Public support knowledge for Notion.",
5 + "articlePath": "toolkits-notion.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/notion/public.md",
9 + "sourceHeading": "Use `NOTION_RETRIEVE_PAGE` instead of deprecated/invalid `NOTION_GET_PAGE`"
10 + },
11 + {
12 + "sourcePath": "toolkits/notion/public.md",
13 + "sourceHeading": "Use the current Notion page and data-source update triggers"
14 + },
15 + {
16 + "sourcePath": "toolkits/notion/public.md",
17 + "sourceHeading": "Notion page/database access is granted per integration, not per Composio auth config token"
18 + },
19 + {
20 + "sourcePath": "toolkits/notion/public.md",
21 + "sourceHeading": "Specifying a different auth config affects get/use lookup, not existing Notion token refresh"
22 + },
23 + {
24 + "sourcePath": "toolkits/notion/public.md",
25 + "sourceHeading": "Notion 401 can be caused by invalid refresh token after user/admin revokes integration"
26 + },
27 + {
28 + "sourcePath": "toolkits/notion/public.md",
29 + "sourceHeading": "Use `NOTION_FETCH_DATA`, not `NOTION_FETCH_NOTION_DATA`"
30 + },
31 + {
32 + "sourcePath": "toolkits/notion/public.md",
33 + "sourceHeading": "Large unfiltered Notion responses can hurt agent quality"
34 + }
35 + ],
36 + "topics": [
37 + "auth-config",
38 + "authentication",
39 + "errors-and-troubleshooting",
40 + "sessions-and-execution",
41 + "toolkits-and-providers"
42 + ],
43 + "tags": [
44 + "for-you",
45 + "notion",
46 + "platform"
47 + ],
48 + "aliases": [
49 + "/kb/toolkits/notion-troubleshooting",
50 + "large-unfiltered-notion-responses-can-hurt-agent-quality",
51 + "notion-401-can-be-caused-by-invalid-refresh-token-after-user-admin-rev",
52 + "notion-database-trigger-fires-for-new-pages-not-updates",
53 + "notion-page-database-access-is-granted-per-integration-not-per-composi",
54 + "notion-troubleshooting",
55 + "repeated-notion-reconnect-loops-may-be-a-rotating-refresh-token-issue",
56 + "specifying-a-different-auth-config-affects-get-use-lookup-not-existing"
57 + ],
58 + "relatedGuides": [],
59 + "externalResources": [],
60 + "updatedAt": "2026-07-16",
61 + "lastVerifiedAt": "2026-08-17",
62 + "reviewAfter": "2026-11-15",
63 + "freshness": "evergreen",
64 + "state": "published",
65 + "featured": false,
66 + "verifyIgnoreToolSlugs": [
67 + "NOTION_GET_PAGE",
68 + "NOTION_FETCH_NOTION_DATA"
69 + ]
70 +}
docs/kb/guides/toolkits-odoo.json new
+35
@@ -0,0 +1,35 @@
1 +{
2 + "slug": "toolkits-odoo",
3 + "title": "Odoo",
4 + "description": "Public troubleshooting guidance for Odoo tools.",
5 + "articlePath": "toolkits-odoo.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/odoo/public.md",
9 + "sourceHeading": "JSON-RPC access errors can arrive inside HTTP 200 responses"
10 + }
11 + ],
12 + "topics": [
13 + "errors-and-troubleshooting",
14 + "sessions-and-execution",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "json-rpc",
20 + "odoo",
21 + "platform"
22 + ],
23 + "aliases": [
24 + "/kb/toolkits/inspect-odoo-json-rpc-errors-inside-http-200-responses",
25 + "inspect-odoo-json-rpc-errors-inside-http-200-responses"
26 + ],
27 + "relatedGuides": [],
28 + "externalResources": [],
29 + "updatedAt": "2026-07-16",
30 + "lastVerifiedAt": "2026-08-12",
31 + "reviewAfter": "2026-11-10",
32 + "freshness": "evergreen",
33 + "state": "published",
34 + "featured": false
35 +}
docs/kb/guides/toolkits-one-drive.json new
+61
@@ -0,0 +1,61 @@
1 +{
2 + "slug": "toolkits-one-drive",
3 + "title": "OneDrive",
4 + "description": "Public support knowledge for OneDrive.",
5 + "articlePath": "toolkits-one-drive.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/one_drive/public.md",
9 + "sourceHeading": "OneDrive custom OAuth issues usually require verifying Azure app setup and recreating the integration"
10 + },
11 + {
12 + "sourcePath": "toolkits/one_drive/public.md",
13 + "sourceHeading": "Use the scopes-required endpoint to derive OneDrive/Microsoft Graph permissions"
14 + },
15 + {
16 + "sourcePath": "toolkits/one_drive/public.md",
17 + "sourceHeading": "Pass `version=latest` if OneDrive folder/list behavior looks stale"
18 + },
19 + {
20 + "sourcePath": "toolkits/one_drive/public.md",
21 + "sourceHeading": "Use file-uploadable or base64-compatible inputs for supported OneDrive actions"
22 + },
23 + {
24 + "sourcePath": "toolkits/one_drive/public.md",
25 + "sourceHeading": "Tool Router v2 sessions should keep all connected accounts under the same `user_id`"
26 + },
27 + {
28 + "sourcePath": "toolkits/one_drive/public.md",
29 + "sourceHeading": "Disable OneDrive destructive actions with `destructiveHint` or explicit tool disables"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "one_drive",
42 + "platform"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/onedrive-troubleshooting",
46 + "deleting-a-onedrive-connection-may-not-revoke-provider-side-tokens",
47 + "disable-onedrive-destructive-actions-with-destructivehint-or-explicit",
48 + "onedrive-custom-oauth-issues-usually-require-verifying-azure-app-setup",
49 + "onedrive-troubleshooting",
50 + "tool-router-v2-sessions-should-keep-all-connected-accounts-under-the-s",
51 + "use-the-scopes-required-endpoint-to-derive-onedrive-microsoft-graph-pe"
52 + ],
53 + "relatedGuides": [],
54 + "externalResources": [],
55 + "updatedAt": "2026-06-24",
56 + "lastVerifiedAt": "2026-08-17",
57 + "reviewAfter": "2026-11-15",
58 + "freshness": "evergreen",
59 + "state": "published",
60 + "featured": false
61 +}
docs/kb/guides/toolkits-onenote.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "toolkits-onenote",
3 + "title": "Microsoft OneNote",
4 + "description": "Current authentication setup for the Microsoft OneNote toolkit.",
5 + "articlePath": "toolkits-onenote.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/onenote/public.md",
9 + "sourceHeading": "OneNote uses a customer-owned Microsoft OAuth app"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "microsoft",
20 + "onenote",
21 + "platform"
22 + ],
23 + "aliases": [],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-08-17",
27 + "lastVerifiedAt": "2026-08-17",
28 + "reviewAfter": "2026-11-15",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/toolkits-openai.json new
+58
@@ -0,0 +1,58 @@
1 +{
2 + "slug": "toolkits-openai",
3 + "title": "OpenAI",
4 + "description": "Public support knowledge for OpenAI.",
5 + "articlePath": "toolkits-openai.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/openai/public.md",
9 + "sourceHeading": "`OPENAI_CREATE_IMAGE` supports `gpt-image-2` in the latest toolkit version"
10 + },
11 + {
12 + "sourcePath": "toolkits/openai/public.md",
13 + "sourceHeading": "Use `OpenAIAgentsProvider` when wiring Composio tools into OpenAI Agents"
14 + },
15 + {
16 + "sourcePath": "toolkits/openai/public.md",
17 + "sourceHeading": "Pin auth config and connected account IDs in Tool Router sessions when a specific connection must be used"
18 + },
19 + {
20 + "sourcePath": "toolkits/openai/public.md",
21 + "sourceHeading": "Use `beforeExecute` modifiers to add a human approval layer before tool execution"
22 + },
23 + {
24 + "sourcePath": "toolkits/openai/public.md",
25 + "sourceHeading": "Provider/schema compatibility errors often require upgrading Composio SDK packages together"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "openai",
38 + "platform"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/openai-troubleshooting",
42 + "append-session-experimental-assistiveprompt-when-gpt-models-are-flaky",
43 + "openai-create-image-supports-gpt-image-2-in-the-latest-toolkit-version",
44 + "openai-troubleshooting",
45 + "pin-auth-config-and-connected-account-ids-in-tool-router-sessions-when",
46 + "provider-schema-bugs-often-require-upgrading-composio-sdk-packages-tog",
47 + "use-beforeexecute-modifiers-to-add-a-human-approval-layer-before-tool",
48 + "use-openaiagentsprovider-when-wiring-composio-tools-into-openai-agents"
49 + ],
50 + "relatedGuides": [],
51 + "externalResources": [],
52 + "updatedAt": "2026-06-24",
53 + "lastVerifiedAt": "2026-08-17",
54 + "reviewAfter": "2026-11-15",
55 + "freshness": "evergreen",
56 + "state": "published",
57 + "featured": false
58 +}
docs/kb/guides/toolkits-outlook.json new
+79
@@ -0,0 +1,79 @@
1 +{
2 + "slug": "toolkits-outlook",
3 + "title": "Outlook",
4 + "description": "Public support knowledge for Outlook.",
5 + "articlePath": "toolkits-outlook.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/outlook/public.md",
9 + "sourceHeading": "Outlook desktop users still need to authenticate the cloud Microsoft account in browser"
10 + },
11 + {
12 + "sourcePath": "toolkits/outlook/public.md",
13 + "sourceHeading": "Connect MCP exposes meta-tools, not individual Outlook tools, by design"
14 + },
15 + {
16 + "sourcePath": "toolkits/outlook/public.md",
17 + "sourceHeading": "For Outlook shared mailboxes, pass the shared mailbox address as `user_id`/mailbox target"
18 + },
19 + {
20 + "sourcePath": "toolkits/outlook/public.md",
21 + "sourceHeading": "Remove obsolete or invalid Outlook tool slugs from MCP configs and patch `allowed_tools`"
22 + },
23 + {
24 + "sourcePath": "toolkits/outlook/public.md",
25 + "sourceHeading": "Outlook multi-account sessions require explicit per-call `account` selection and aliases"
26 + },
27 + {
28 + "sourcePath": "toolkits/outlook/public.md",
29 + "sourceHeading": "Use `get_scopes_required` with Outlook tool slugs, then refresh/reconnect after scope changes"
30 + },
31 + {
32 + "sourcePath": "toolkits/outlook/public.md",
33 + "sourceHeading": "Outlook/Microsoft apps may need admin consent from App Registration or Enterprise Applications"
34 + },
35 + {
36 + "sourcePath": "toolkits/outlook/public.md",
37 + "sourceHeading": "Outlook/Gmail email attachments through SDK should be passed as file paths"
38 + },
39 + {
40 + "sourcePath": "toolkits/outlook/public.md",
41 + "sourceHeading": "Incomplete Outlook auth links expire after about 10 minutes and mark the connection `EXPIRED`"
42 + }
43 + ],
44 + "topics": [
45 + "auth-config",
46 + "authentication",
47 + "errors-and-troubleshooting",
48 + "sessions-and-execution",
49 + "toolkits-and-providers"
50 + ],
51 + "tags": [
52 + "for-you",
53 + "outlook",
54 + "platform"
55 + ],
56 + "aliases": [
57 + "/kb/authentication/outlook-troubleshooting",
58 + "an-active-outlook-connection-can-have-a-disabled-webhook-trigger",
59 + "connect-mcp-exposes-meta-tools-not-individual-outlook-tools-by-design",
60 + "incomplete-outlook-auth-links-expire-after-about-10-minutes-and-mark-t",
61 + "outlook-desktop-users-still-need-to-authenticate-the-cloud-microsoft-a",
62 + "outlook-email-categories-and-send-draft-pin-email-support-may-need-too",
63 + "outlook-gmail-email-attachments-through-sdk-should-be-passed-as-file-p",
64 + "outlook-microsoft-apps-may-need-admin-consent-from-app-registration-or",
65 + "outlook-multi-account-sessions-require-explicit-per-call-account-selec",
66 + "outlook-troubleshooting",
67 + "remove-old-bad-outlook-tool-slugs-from-mcp-configs-and-patch-allowed-t",
68 + "target-outlook-shared-mailboxes-by-address",
69 + "use-get-scopes-required-with-outlook-tool-slugs-then-refresh-reconnect"
70 + ],
71 + "relatedGuides": [],
72 + "externalResources": [],
73 + "updatedAt": "2026-07-16",
74 + "lastVerifiedAt": "2026-08-17",
75 + "reviewAfter": "2026-11-15",
76 + "freshness": "evergreen",
77 + "state": "published",
78 + "featured": false
79 +}
docs/kb/guides/toolkits-perplexityai.json new
+31
@@ -0,0 +1,31 @@
1 +{
2 + "slug": "toolkits-perplexityai",
3 + "title": "Perplexity AI authentication",
4 + "description": "Current API-key setup for the Perplexity AI toolkit.",
5 + "articlePath": "toolkits-perplexityai.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/perplexityai/public.md",
9 + "sourceHeading": "Perplexity AI uses the `generic_api_key` connection field"
10 + }
11 + ],
12 + "topics": [
13 + "authentication",
14 + "errors-and-troubleshooting",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "perplexityai",
20 + "platform"
21 + ],
22 + "aliases": [],
23 + "relatedGuides": [],
24 + "externalResources": [],
25 + "updatedAt": "2026-08-17",
26 + "lastVerifiedAt": "2026-08-17",
27 + "reviewAfter": "2026-11-15",
28 + "freshness": "evergreen",
29 + "state": "published",
30 + "featured": false
31 +}
docs/kb/guides/toolkits-pipedrive.json new
+61
@@ -0,0 +1,61 @@
1 +{
2 + "slug": "toolkits-pipedrive",
3 + "title": "Pipedrive",
4 + "description": "Public support knowledge for Pipedrive.",
5 + "articlePath": "toolkits-pipedrive.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/pipedrive/public.md",
9 + "sourceHeading": "Pipedrive requires custom OAuth or API-key credentials"
10 + },
11 + {
12 + "sourcePath": "toolkits/pipedrive/public.md",
13 + "sourceHeading": "Pipedrive OAuth initiation requires the workspace subdomain"
14 + },
15 + {
16 + "sourcePath": "toolkits/pipedrive/public.md",
17 + "sourceHeading": "Do not install the Pipedrive app directly from Pipedrive OAuth settings"
18 + },
19 + {
20 + "sourcePath": "toolkits/pipedrive/public.md",
21 + "sourceHeading": "Hosted auth links can collect Pipedrive required fields"
22 + },
23 + {
24 + "sourcePath": "toolkits/pipedrive/public.md",
25 + "sourceHeading": "Pass `callback_url` when initiating Pipedrive auth to redirect users after authentication"
26 + },
27 + {
28 + "sourcePath": "toolkits/pipedrive/public.md",
29 + "sourceHeading": "Pipedrive has trigger support"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "sessions-and-execution",
36 + "toolkits-and-providers"
37 + ],
38 + "tags": [
39 + "for-you",
40 + "pipedrive",
41 + "platform"
42 + ],
43 + "aliases": [
44 + "/kb/toolkits/pipedrive-troubleshooting",
45 + "claude-may-block-pipedrive-because-payment-processing-toolkits-are-res",
46 + "do-not-install-the-pipedrive-app-directly-from-pipedrive-oauth-setting",
47 + "hosted-auth-links-can-collect-pipedrive-required-fields",
48 + "pass-callback-url-when-initiating-pipedrive-auth-to-redirect-users-aft",
49 + "pipedrive-oauth-initiation-requires-the-workspace-subdomain",
50 + "pipedrive-troubleshooting",
51 + "use-custom-credentials-or-api-key-when-composio-s-default-pipedrive-oa"
52 + ],
53 + "relatedGuides": [],
54 + "externalResources": [],
55 + "updatedAt": "2026-06-24",
56 + "lastVerifiedAt": "2026-08-24",
57 + "reviewAfter": "2026-11-22",
58 + "freshness": "evergreen",
59 + "state": "published",
60 + "featured": false
61 +}
docs/kb/guides/toolkits-posthog.json new
+58
@@ -0,0 +1,58 @@
1 +{
2 + "slug": "toolkits-posthog",
3 + "title": "PostHog",
4 + "description": "Public support knowledge for PostHog.",
5 + "articlePath": "toolkits-posthog.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/posthog/public.md",
9 + "sourceHeading": "PostHog is API-key based; use the PostHog API key when creating the connection"
10 + },
11 + {
12 + "sourcePath": "toolkits/posthog/public.md",
13 + "sourceHeading": "Configure PostHog subdomain for EU or self-hosted instances"
14 + },
15 + {
16 + "sourcePath": "toolkits/posthog/public.md",
17 + "sourceHeading": "Pass auth config into Tool Router sessions; platform-created auth configs are not automatically usable"
18 + },
19 + {
20 + "sourcePath": "toolkits/posthog/public.md",
21 + "sourceHeading": "Create a PostHog integration/auth config before expecting it in auth_configs API results"
22 + },
23 + {
24 + "sourcePath": "toolkits/posthog/public.md",
25 + "sourceHeading": "Fetch PostHog tool schema to see required fields for a tool call"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "platform",
38 + "posthog"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/posthog-troubleshooting",
42 + "api-key-connections-may-show-active-without-live-credential-validation",
43 + "configure-posthog-subdomain-for-eu-or-self-hosted-instances",
44 + "create-a-posthog-integration-auth-config-before-expecting-it-in-auth-c",
45 + "fetch-posthog-tool-schema-to-see-required-fields-for-a-tool-call",
46 + "pass-auth-config-into-tool-router-sessions-platform-created-auth-confi",
47 + "posthog-is-api-key-based-use-the-posthog-api-key-when-creating-the-con",
48 + "posthog-troubleshooting"
49 + ],
50 + "relatedGuides": [],
51 + "externalResources": [],
52 + "updatedAt": "2026-06-24",
53 + "lastVerifiedAt": "2026-08-17",
54 + "reviewAfter": "2026-11-15",
55 + "freshness": "evergreen",
56 + "state": "published",
57 + "featured": false
58 +}
docs/kb/guides/toolkits-quickbooks.json new
+73
@@ -0,0 +1,73 @@
1 +{
2 + "slug": "toolkits-quickbooks",
3 + "title": "QuickBooks",
4 + "description": "Public support knowledge for QuickBooks.",
5 + "articlePath": "toolkits-quickbooks.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/quickbooks/public.md",
9 + "sourceHeading": "Use the sandbox QuickBooks API base URL for sandbox connections"
10 + },
11 + {
12 + "sourcePath": "toolkits/quickbooks/public.md",
13 + "sourceHeading": "QuickBooks auth configs need QuickBooks credentials and matching redirect URL"
14 + },
15 + {
16 + "sourcePath": "toolkits/quickbooks/public.md",
17 + "sourceHeading": "QuickBooks auth can accept custom auth and token URLs for sandbox/custom flows"
18 + },
19 + {
20 + "sourcePath": "toolkits/quickbooks/public.md",
21 + "sourceHeading": "QuickBooks payment scope requires payment module access"
22 + },
23 + {
24 + "sourcePath": "toolkits/quickbooks/public.md",
25 + "sourceHeading": "Realm ID mapping fixes may require the latest QuickBooks toolkit version"
26 + },
27 + {
28 + "sourcePath": "toolkits/quickbooks/public.md",
29 + "sourceHeading": "Multiple QuickBooks accounts can be selected in Claude/MCP by using separate user IDs or connected account IDs"
30 + },
31 + {
32 + "sourcePath": "toolkits/quickbooks/public.md",
33 + "sourceHeading": "QuickBooks tokens are refreshed periodically with retries before expiring the connection"
34 + },
35 + {
36 + "sourcePath": "toolkits/quickbooks/public.md",
37 + "sourceHeading": "QuickBooks hosted auth screen can be skipped by sending users directly to the OAuth provider"
38 + }
39 + ],
40 + "topics": [
41 + "auth-config",
42 + "authentication",
43 + "errors-and-troubleshooting",
44 + "sessions-and-execution",
45 + "toolkits-and-providers"
46 + ],
47 + "tags": [
48 + "for-you",
49 + "platform",
50 + "quickbooks"
51 + ],
52 + "aliases": [
53 + "/kb/toolkits/quickbooks-disabled-for-this-session",
54 + "/kb/toolkits/quickbooks-troubleshooting",
55 + "connect-a-quickbooks-sandbox-company",
56 + "connect-multiple-quickbooks-companies",
57 + "missing-quickbooks-expense-bill-tools-should-be-filed-with-the-exact-i",
58 + "quickbooks-disabled-for-this-session",
59 + "quickbooks-hosted-auth-screen-can-be-skipped-by-sending-users-directly",
60 + "quickbooks-oauth-fails-with-payments-scope",
61 + "quickbooks-requests-resolve-to-company-none",
62 + "quickbooks-tokens-are-refreshed-periodically-with-retries-before-expir",
63 + "quickbooks-troubleshooting"
64 + ],
65 + "relatedGuides": [],
66 + "externalResources": [],
67 + "updatedAt": "2026-07-16",
68 + "lastVerifiedAt": "2026-08-12",
69 + "reviewAfter": "2026-11-10",
70 + "freshness": "evergreen",
71 + "state": "published",
72 + "featured": false
73 +}
docs/kb/guides/toolkits-reddit.json new
+51
@@ -0,0 +1,51 @@
1 +{
2 + "slug": "toolkits-reddit",
3 + "title": "Reddit",
4 + "description": "Public support knowledge for Reddit.",
5 + "articlePath": "toolkits-reddit.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/reddit/public.md",
9 + "sourceHeading": "Use Connect MCP for Reddit OAuth callback failures in Claude Code"
10 + },
11 + {
12 + "sourcePath": "toolkits/reddit/public.md",
13 + "sourceHeading": "Reddit supports managed and customer-owned OAuth 2.0"
14 + },
15 + {
16 + "sourcePath": "toolkits/reddit/public.md",
17 + "sourceHeading": "Reddit toolkit behavior can change when Reddit changes its API or enforcement policies"
18 + },
19 + {
20 + "sourcePath": "toolkits/reddit/public.md",
21 + "sourceHeading": "Older Reddit Create Post tool versions may require `flair_id`"
22 + }
23 + ],
24 + "topics": [
25 + "auth-config",
26 + "authentication",
27 + "errors-and-troubleshooting",
28 + "sessions-and-execution",
29 + "toolkits-and-providers"
30 + ],
31 + "tags": [
32 + "for-you",
33 + "platform",
34 + "reddit"
35 + ],
36 + "aliases": [
37 + "/kb/toolkits/reddit-troubleshooting",
38 + "connect-reddit-with-your-own-oauth-credentials",
39 + "reddit-create-post-requires-flair-id",
40 + "reddit-troubleshooting",
41 + "use-connect-mcp-for-reddit-oauth-callback-failures-in-claude-code"
42 + ],
43 + "relatedGuides": [],
44 + "externalResources": [],
45 + "updatedAt": "2026-06-24",
46 + "lastVerifiedAt": "2026-08-24",
47 + "reviewAfter": "2026-11-22",
48 + "freshness": "evergreen",
49 + "state": "published",
50 + "featured": false
51 +}
docs/kb/guides/toolkits-salesforce.json new
+92
@@ -0,0 +1,92 @@
1 +{
2 + "slug": "toolkits-salesforce",
3 + "title": "Salesforce",
4 + "description": "Public support knowledge for Salesforce.",
5 + "articlePath": "toolkits-salesforce.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/salesforce/public.md",
9 + "sourceHeading": "Use customer-owned Salesforce credentials when you need app-level control"
10 + },
11 + {
12 + "sourcePath": "toolkits/salesforce/public.md",
13 + "sourceHeading": "Salesforce connection initiation needs instance endpoint and My Domain subdomain fields"
14 + },
15 + {
16 + "sourcePath": "toolkits/salesforce/public.md",
17 + "sourceHeading": "Salesforce subdomain defaults to `login`; use the My Domain/API prefix when needed"
18 + },
19 + {
20 + "sourcePath": "toolkits/salesforce/public.md",
21 + "sourceHeading": "`URL_NOT_RESET` usually means Salesforce subdomain was not configured and defaulted to `login`"
22 + },
23 + {
24 + "sourcePath": "toolkits/salesforce/public.md",
25 + "sourceHeading": "Use hosted auth for Salesforce required fields, or direct `.initiate()` when you want to prefill them yourself"
26 + },
27 + {
28 + "sourcePath": "toolkits/salesforce/public.md",
29 + "sourceHeading": "Use `SALESFORCE_GET_ALL_FIELDS_FOR_OBJECT` to inspect a Salesforce object's fields"
30 + },
31 + {
32 + "sourcePath": "toolkits/salesforce/public.md",
33 + "sourceHeading": "Salesforce org admins may need to install/approve the connected app before users can authenticate"
34 + },
35 + {
36 + "sourcePath": "toolkits/salesforce/public.md",
37 + "sourceHeading": "Salesforce allows only five active refresh tokens per user per app"
38 + },
39 + {
40 + "sourcePath": "toolkits/salesforce/public.md",
41 + "sourceHeading": "Use Proxy Execute for Salesforce Frontdoor/UI bridge flows instead of reading tokens from connected accounts"
42 + },
43 + {
44 + "sourcePath": "toolkits/salesforce/public.md",
45 + "sourceHeading": "Migrate deprecated Salesforce retrieve tools to the current get/list tools"
46 + },
47 + {
48 + "sourcePath": "toolkits/salesforce/public.md",
49 + "sourceHeading": "Retrieve a specific Salesforce contact by listing contacts and then fetching by ID"
50 + },
51 + {
52 + "sourcePath": "toolkits/salesforce/public.md",
53 + "sourceHeading": "The Salesforce custom auth redirect URL is Composio's toolkit auth callback endpoint"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "toolkits-and-providers"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "platform",
66 + "salesforce"
67 + ],
68 + "aliases": [
69 + "/kb/toolkits/salesforce-troubleshooting",
70 + "migrate-deprecated-salesforce-retrieve-tools-to-the-newer-get-list-too",
71 + "retrieve-a-specific-salesforce-contact-by-first-listing-contacts-and-t",
72 + "salesforce-action-to-scope-mapping-is-not-granular-include-refresh-tok",
73 + "salesforce-allows-only-five-active-refresh-tokens-per-user-per-app",
74 + "salesforce-connection-initiation-needs-instance-endpoint-and-my-domain",
75 + "salesforce-requires-customer-owned-developer-credentials",
76 + "salesforce-subdomain-defaults-to-login-use-the-my-domain-api-prefix-wh",
77 + "salesforce-troubleshooting",
78 + "the-salesforce-custom-auth-redirect-url-is-composio-s-toolkit-auth-cal",
79 + "url-not-reset-usually-means-salesforce-subdomain-was-not-configured-an",
80 + "use-hosted-auth-for-salesforce-required-fields-or-direct-initiate-when",
81 + "use-proxy-execute-for-salesforce-frontdoor-ui-bridge-flows-instead-of",
82 + "use-salesforce-get-all-fields-for-object-to-inspect-a-salesforce-objec"
83 + ],
84 + "relatedGuides": [],
85 + "externalResources": [],
86 + "updatedAt": "2026-06-24",
87 + "lastVerifiedAt": "2026-08-17",
88 + "reviewAfter": "2026-11-15",
89 + "freshness": "evergreen",
90 + "state": "published",
91 + "featured": false
92 +}
docs/kb/guides/toolkits-serpapi.json new
+48
@@ -0,0 +1,48 @@
1 +{
2 + "slug": "toolkits-serpapi",
3 + "title": "SerpApi",
4 + "description": "Public support knowledge for SerpApi.",
5 + "articlePath": "toolkits-serpapi.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/serpapi/public.md",
9 + "sourceHeading": "Control SerpAPI availability in a Session"
10 + },
11 + {
12 + "sourcePath": "toolkits/serpapi/public.md",
13 + "sourceHeading": "Use toolkit details to inspect SerpAPI required auth fields"
14 + },
15 + {
16 + "sourcePath": "toolkits/serpapi/public.md",
17 + "sourceHeading": "Search and scraping use cases can use SerpAPI alongside Firecrawl, Exa, Tavily, or Composio Search"
18 + }
19 + ],
20 + "topics": [
21 + "authentication",
22 + "errors-and-troubleshooting",
23 + "sessions-and-execution",
24 + "toolkits-and-providers"
25 + ],
26 + "tags": [
27 + "for-you",
28 + "platform",
29 + "serpapi"
30 + ],
31 + "aliases": [
32 + "/kb/toolkits/serpapi-troubleshooting",
33 + "avoid-serpapi-ebay-search-when-its-schema-causes-field-errors",
34 + "disable-serpapi-by-listing-premium-toolkit-slugs-in-session-config",
35 + "search-and-scraping-use-cases-can-use-serpapi-alongside-firecrawl-exa",
36 + "serpapi-api-key-validation-was-not-available-in-the-connection-flow",
37 + "serpapi-troubleshooting",
38 + "use-toolkit-details-to-inspect-serpapi-required-auth-fields"
39 + ],
40 + "relatedGuides": [],
41 + "externalResources": [],
42 + "updatedAt": "2026-06-24",
43 + "lastVerifiedAt": "2026-08-12",
44 + "reviewAfter": "2026-11-10",
45 + "freshness": "evergreen",
46 + "state": "published",
47 + "featured": false
48 +}
docs/kb/guides/toolkits-servicenow.json new
+31
@@ -0,0 +1,31 @@
1 +{
2 + "slug": "toolkits-servicenow",
3 + "title": "ServiceNow authentication",
4 + "description": "Current instance-specific authentication setup for ServiceNow.",
5 + "articlePath": "toolkits-servicenow.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/servicenow/public.md",
9 + "sourceHeading": "ServiceNow credentials and instance subdomain are collected at different stages"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "toolkits-and-providers"
16 + ],
17 + "tags": [
18 + "for-you",
19 + "platform",
20 + "servicenow"
21 + ],
22 + "aliases": [],
23 + "relatedGuides": [],
24 + "externalResources": [],
25 + "updatedAt": "2026-08-17",
26 + "lastVerifiedAt": "2026-08-17",
27 + "reviewAfter": "2026-11-15",
28 + "freshness": "evergreen",
29 + "state": "published",
30 + "featured": false
31 +}
docs/kb/guides/toolkits-sharepoint.json new
+87
@@ -0,0 +1,87 @@
1 +{
2 + "slug": "toolkits-sharepoint",
3 + "title": "SharePoint",
4 + "description": "Public support knowledge for SharePoint.",
5 + "articlePath": "toolkits-sharepoint.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/sharepoint/public.md",
9 + "sourceHeading": "SharePoint REST APIs and SharePoint Graph are separate API families"
10 + },
11 + {
12 + "sourcePath": "toolkits/sharepoint/public.md",
13 + "sourceHeading": "`/teams/` SharePoint sites require the server-relative Subsite path"
14 + },
15 + {
16 + "sourcePath": "toolkits/sharepoint/public.md",
17 + "sourceHeading": "SharePoint REST app-only client credentials use certificate auth"
18 + },
19 + {
20 + "sourcePath": "toolkits/sharepoint/public.md",
21 + "sourceHeading": "SharePoint `.default` scope uses the tenant domain placeholder"
22 + },
23 + {
24 + "sourcePath": "toolkits/sharepoint/public.md",
25 + "sourceHeading": "Pass the SharePoint tenant/subdomain during connection initiation"
26 + },
27 + {
28 + "sourcePath": "toolkits/sharepoint/public.md",
29 + "sourceHeading": "The SharePoint subsite field is not a permission boundary"
30 + },
31 + {
32 + "sourcePath": "toolkits/sharepoint/public.md",
33 + "sourceHeading": "Retrieve SharePoint site name from connected account state"
34 + },
35 + {
36 + "sourcePath": "toolkits/sharepoint/public.md",
37 + "sourceHeading": "Use `SHARE_POINT_SEARCH_QUERY` for KQL/FQL SharePoint search"
38 + },
39 + {
40 + "sourcePath": "toolkits/sharepoint/public.md",
41 + "sourceHeading": "SharePoint toolkit slug is `share_point`"
42 + },
43 + {
44 + "sourcePath": "toolkits/sharepoint/public.md",
45 + "sourceHeading": "Disable destructive SharePoint tools with `destructiveHint` or explicit tool filters"
46 + },
47 + {
48 + "sourcePath": "toolkits/sharepoint/public.md",
49 + "sourceHeading": "`SHARE_POINT_UPLOAD_FROM_URL` needs a server-fetchable URL"
50 + }
51 + ],
52 + "topics": [
53 + "auth-config",
54 + "authentication",
55 + "errors-and-troubleshooting",
56 + "sessions-and-execution",
57 + "toolkits-and-providers"
58 + ],
59 + "tags": [
60 + "for-you",
61 + "platform",
62 + "sharepoint"
63 + ],
64 + "aliases": [
65 + "/kb/toolkits/after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati",
66 + "/kb/toolkits/sharepoint-troubleshooting",
67 + "after-certain-sharepoint-auth-fixes-create-a-new-auth-config-integrati",
68 + "create-folder-odata-type-name-error",
69 + "disable-destructive-sharepoint-tools-with-destructivehint-or-explicit",
70 + "set-the-sharepoint-tenant-on-the-connection",
71 + "share-point-upload-from-url-needs-a-server-fetchable-url",
72 + "sharepoint-rest-and-graph-need-separate-connections",
73 + "sharepoint-rest-app-only-client-credentials-use-certificate-auth",
74 + "sharepoint-teams-site-returns-404",
75 + "sharepoint-troubleshooting",
76 + "the-sharepoint-subsite-field-is-not-a-permission-boundary",
77 + "use-share-point-search-query-for-kql-fql-sharepoint-search"
78 + ],
79 + "relatedGuides": [],
80 + "externalResources": [],
81 + "updatedAt": "2026-10-13",
82 + "lastVerifiedAt": "2026-08-12",
83 + "reviewAfter": "2026-11-10",
84 + "freshness": "evergreen",
85 + "state": "published",
86 + "featured": false
87 +}
docs/kb/guides/toolkits-shopify.json new
+86
@@ -0,0 +1,86 @@
1 +{
2 + "slug": "toolkits-shopify",
3 + "title": "Shopify",
4 + "description": "Public support knowledge for Shopify.",
5 + "articlePath": "toolkits-shopify.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/shopify/public.md",
9 + "sourceHeading": "Shopify API-key/admin-token auth is deprecated; use OAuth2 or S2S auth instead"
10 + },
11 + {
12 + "sourcePath": "toolkits/shopify/public.md",
13 + "sourceHeading": "Use Composio's toolkit auth callback as the Shopify OAuth redirect URL"
14 + },
15 + {
16 + "sourcePath": "toolkits/shopify/public.md",
17 + "sourceHeading": "Custom Shopify credentials keep the same hosted auth UX and Composio still manages refresh"
18 + },
19 + {
20 + "sourcePath": "toolkits/shopify/public.md",
21 + "sourceHeading": "Shopify OAuth 400s are commonly caused by incorrect client secrets or unverified gated scopes"
22 + },
23 + {
24 + "sourcePath": "toolkits/shopify/public.md",
25 + "sourceHeading": "Shopify subdomain should be only the store name, not the full `.myshopify.com` host"
26 + },
27 + {
28 + "sourcePath": "toolkits/shopify/public.md",
29 + "sourceHeading": "Use `SHOPIFY_GRAPH_QL_QUERY` for Shopify GraphQL queries"
30 + },
31 + {
32 + "sourcePath": "toolkits/shopify/public.md",
33 + "sourceHeading": "Fetch more than the default 20 Shopify tools and enable the tool in MCP config"
34 + },
35 + {
36 + "sourcePath": "toolkits/shopify/public.md",
37 + "sourceHeading": "Use `SHOPIFY_GET_ORDERS_WITH_FILTERS` to confirm orders and retrieve order IDs"
38 + },
39 + {
40 + "sourcePath": "toolkits/shopify/public.md",
41 + "sourceHeading": "Shopify order update 403s can be caused by missing `read_all_orders` scope"
42 + },
43 + {
44 + "sourcePath": "toolkits/shopify/public.md",
45 + "sourceHeading": "Custom Shopify tools can call GraphQL with Composio-injected auth"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "platform",
58 + "shopify"
59 + ],
60 + "aliases": [
61 + "/kb/authentication/shopify-troubleshooting",
62 + "choose-current-shopify-app-auth-flow",
63 + "custom-shopify-credentials-keep-the-same-hosted-auth-ux-and-composio-s",
64 + "custom-shopify-tools-can-call-graphql-with-composio-injected-auth",
65 + "dashboard-claude-shopify-flow-does-not-currently-support-multiple-conn",
66 + "fetch-more-than-the-default-20-shopify-tools-and-enable-the-tool-in-mc",
67 + "for-you-shopify-oauth-scopes-cannot-currently-be-customized",
68 + "if-shopify-mcp-auth-completes-but-tools-fail-append-the-configured-use",
69 + "shopify-managed-default-oauth-is-not-available-use-your-own-shopify-oa",
70 + "shopify-oauth-400s-are-commonly-caused-by-bad-client-secrets-or-unveri",
71 + "shopify-order-update-403s-can-be-caused-by-missing-read-all-orders-sco",
72 + "shopify-subdomain-should-be-only-the-store-name-not-the-full-myshopify",
73 + "shopify-troubleshooting",
74 + "use-composio-s-toolkit-auth-callback-as-the-shopify-oauth-redirect-url",
75 + "use-shopify-get-order-list-to-confirm-orders-and-retrieve-order-ids",
76 + "use-shopify-graph-ql-query-for-shopify-graphql-queries"
77 + ],
78 + "relatedGuides": [],
79 + "externalResources": [],
80 + "updatedAt": "2026-06-24",
81 + "lastVerifiedAt": "2026-08-17",
82 + "reviewAfter": "2026-11-15",
83 + "freshness": "evergreen",
84 + "state": "published",
85 + "featured": false
86 +}
docs/kb/guides/toolkits-slack.json new
+76
@@ -0,0 +1,76 @@
1 +{
2 + "slug": "toolkits-slack",
3 + "title": "Slack",
4 + "description": "Public support knowledge for Slack.",
5 + "articlePath": "toolkits-slack.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/slack/public.md",
9 + "sourceHeading": "Use `user_scopes` for Slack user-token permissions"
10 + },
11 + {
12 + "sourcePath": "toolkits/slack/public.md",
13 + "sourceHeading": "Download Slack file content using file ID"
14 + },
15 + {
16 + "sourcePath": "toolkits/slack/public.md",
17 + "sourceHeading": "Slack `assistant.search.context` requires Agents & AI Apps and Business+"
18 + },
19 + {
20 + "sourcePath": "toolkits/slack/public.md",
21 + "sourceHeading": "Use Slack V2 trigger slugs for channel and direct messages"
22 + },
23 + {
24 + "sourcePath": "toolkits/slack/public.md",
25 + "sourceHeading": "Slack trigger delivery depends on the Slack app event subscription webhook URL"
26 + },
27 + {
28 + "sourcePath": "toolkits/slack/public.md",
29 + "sourceHeading": "Slack short connect links are not the OAuth redirect URI"
30 + },
31 + {
32 + "sourcePath": "toolkits/slack/public.md",
33 + "sourceHeading": "Slack scheduled-message attachments are not file uploads"
34 + },
35 + {
36 + "sourcePath": "toolkits/slack/public.md",
37 + "sourceHeading": "`admin.conversations:write` requires Slack Enterprise"
38 + }
39 + ],
40 + "topics": [
41 + "auth-config",
42 + "authentication",
43 + "errors-and-troubleshooting",
44 + "sessions-and-execution",
45 + "toolkits-and-providers"
46 + ],
47 + "tags": [
48 + "for-you",
49 + "platform",
50 + "slack"
51 + ],
52 + "aliases": [
53 + "/kb/toolkits/slack-troubleshooting",
54 + "download-slack-file-content-using-file-id",
55 + "revoked-slack-tokens-can-remain-active-briefly-before-expiring",
56 + "slack-admin-conversation-writes-require-enterprise",
57 + "slack-assistant-search-context-requires-agents-ai-apps-and-business",
58 + "slack-marketplace-warning-on-composio-managed-app-does-not-block-oauth",
59 + "slack-scheduled-message-attachments-are-not-file-uploads",
60 + "slack-short-connect-links-are-not-the-oauth-redirect-uri",
61 + "slack-trigger-delivery-depends-on-the-slack-app-event-subscription-web",
62 + "slack-troubleshooting",
63 + "slackbot-token-rotation-can-make-externally-cached-tokens-expire-quick",
64 + "use-slack-v2-trigger-slugs-for-channel-and-direct-messages",
65 + "use-user-scopes-for-slack-user-token-permissions",
66 + "use-your-own-slack-oauth-app-for-production-quota-isolation"
67 + ],
68 + "relatedGuides": [],
69 + "externalResources": [],
70 + "updatedAt": "2026-06-24",
71 + "lastVerifiedAt": "2026-08-12",
72 + "reviewAfter": "2026-11-10",
73 + "freshness": "evergreen",
74 + "state": "published",
75 + "featured": false
76 +}
docs/kb/guides/toolkits-slackbot.json new
+69
@@ -0,0 +1,69 @@
1 +{
2 + "slug": "toolkits-slackbot",
3 + "title": "Slackbot",
4 + "description": "Public support knowledge for Slackbot.",
5 + "articlePath": "toolkits-slackbot.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/slackbot/public.md",
9 + "sourceHeading": "Use Slack for user actions and Slackbot for bot-token/bot-scope actions"
10 + },
11 + {
12 + "sourcePath": "toolkits/slackbot/public.md",
13 + "sourceHeading": "Slackbot triggers require the verification token in custom auth"
14 + },
15 + {
16 + "sourcePath": "toolkits/slackbot/public.md",
17 + "sourceHeading": "Private Slack channels and DMs require extra history scopes"
18 + },
19 + {
20 + "sourcePath": "toolkits/slackbot/public.md",
21 + "sourceHeading": "Slack file downloads use `SLACK_DOWNLOAD_SLACK_FILE` with a Slack file ID"
22 + },
23 + {
24 + "sourcePath": "toolkits/slackbot/public.md",
25 + "sourceHeading": "Slack short auth links are not the OAuth redirect URI"
26 + },
27 + {
28 + "sourcePath": "toolkits/slackbot/public.md",
29 + "sourceHeading": "Use `SLACKBOT_SEND_MESSAGE` to post a bot message"
30 + },
31 + {
32 + "sourcePath": "toolkits/slackbot/public.md",
33 + "sourceHeading": "Slackbot trigger payloads include `connection_id` and `trigger_id`"
34 + }
35 + ],
36 + "topics": [
37 + "auth-config",
38 + "authentication",
39 + "errors-and-troubleshooting",
40 + "sessions-and-execution",
41 + "toolkits-and-providers"
42 + ],
43 + "tags": [
44 + "for-you",
45 + "platform",
46 + "slackbot"
47 + ],
48 + "aliases": [
49 + "/kb/toolkits/slackbot-troubleshooting",
50 + "revoked-slack-tokens-may-stay-active-for-two-refresh-cycles-before-exp",
51 + "slack-file-downloads-use-slack-download-slack-file-with-a-slack-file-i",
52 + "slack-private-conversations-require-separate-history-scopes",
53 + "slack-short-auth-links-are-not-the-oauth-redirect-uri",
54 + "slackbot-trigger-payloads-include-connection-id-and-trigger-id",
55 + "slackbot-trigger-setup-needs-team-read-on-the-user-token",
56 + "slackbot-triggers-require-a-verification-token-or-subscription-id-in-c",
57 + "slackbot-troubleshooting",
58 + "use-slack-for-user-actions-and-slackbot-for-bot-token-bot-scope-action",
59 + "with-slack-token-rotation-enabled-fetch-connected-account-data-frequen"
60 + ],
61 + "relatedGuides": [],
62 + "externalResources": [],
63 + "updatedAt": "2026-07-16",
64 + "lastVerifiedAt": "2026-08-17",
65 + "reviewAfter": "2026-11-15",
66 + "freshness": "evergreen",
67 + "state": "published",
68 + "featured": false
69 +}
docs/kb/guides/toolkits-snapchat.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "toolkits-snapchat",
3 + "title": "Snapchat authentication",
4 + "description": "Current customer-owned OAuth setup for the Snapchat toolkit.",
5 + "articlePath": "toolkits-snapchat.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/snapchat/public.md",
9 + "sourceHeading": "Snapchat uses customer-owned OAuth credentials"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "errors-and-troubleshooting",
16 + "toolkits-and-providers"
17 + ],
18 + "tags": [
19 + "for-you",
20 + "platform",
21 + "snapchat"
22 + ],
23 + "aliases": [],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-08-17",
27 + "lastVerifiedAt": "2026-08-17",
28 + "reviewAfter": "2026-11-15",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/toolkits-snowflake.json new
+59
@@ -0,0 +1,59 @@
1 +{
2 + "slug": "toolkits-snowflake",
3 + "title": "Snowflake",
4 + "description": "Public support knowledge for Snowflake.",
5 + "articlePath": "toolkits-snowflake.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/snowflake/public.md",
9 + "sourceHeading": "Use one Snowflake auth config per customer account for multi-tenant SaaS OAuth"
10 + },
11 + {
12 + "sourcePath": "toolkits/snowflake/public.md",
13 + "sourceHeading": "Snowflake Basic auth was deprecated in favor of OAuth2"
14 + },
15 + {
16 + "sourcePath": "toolkits/snowflake/public.md",
17 + "sourceHeading": "Configure Snowflake OAuth refresh tokens and expect periodic reconnects"
18 + },
19 + {
20 + "sourcePath": "toolkits/snowflake/public.md",
21 + "sourceHeading": "Fetch connected-account fields or toolkit metadata to discover Snowflake account details"
22 + },
23 + {
24 + "sourcePath": "toolkits/snowflake/public.md",
25 + "sourceHeading": "Snowflake statement results may require checking each partition"
26 + },
27 + {
28 + "sourcePath": "toolkits/snowflake/public.md",
29 + "sourceHeading": "Use processors or tool description overrides to reduce Snowflake tool output/token load"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "platform",
42 + "snowflake"
43 + ],
44 + "aliases": [
45 + "/kb/authentication/snowflake-troubleshooting",
46 + "configure-snowflake-oauth-refresh-tokens-and-expect-periodic-reconnect",
47 + "snowflake-account-id-uses-org-account-format",
48 + "snowflake-basic-auth-was-deprecated-in-favor-of-oauth2",
49 + "snowflake-troubleshooting"
50 + ],
51 + "relatedGuides": [],
52 + "externalResources": [],
53 + "updatedAt": "2026-06-24",
54 + "lastVerifiedAt": "2026-08-12",
55 + "reviewAfter": "2026-11-10",
56 + "freshness": "evergreen",
57 + "state": "published",
58 + "featured": false
59 +}
docs/kb/guides/toolkits-spotify.json new
+62
@@ -0,0 +1,62 @@
1 +{
2 + "slug": "toolkits-spotify",
3 + "title": "Spotify",
4 + "description": "Public support knowledge for Spotify.",
5 + "articlePath": "toolkits-spotify.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/spotify/public.md",
9 + "sourceHeading": "Spotify requires a customer-owned OAuth app"
10 + },
11 + {
12 + "sourcePath": "toolkits/spotify/public.md",
13 + "sourceHeading": "Spotify library scopes may need to be added to the auth config and then the user must reconnect"
14 + },
15 + {
16 + "sourcePath": "toolkits/spotify/public.md",
17 + "sourceHeading": "Custom Spotify toolkit names cannot collide with the built-in Spotify toolkit slug/name"
18 + },
19 + {
20 + "sourcePath": "toolkits/spotify/public.md",
21 + "sourceHeading": "Spotify can be added to an MCP server from the MCP configs page"
22 + },
23 + {
24 + "sourcePath": "toolkits/spotify/public.md",
25 + "sourceHeading": "Spotify has trigger support"
26 + },
27 + {
28 + "sourcePath": "toolkits/spotify/public.md",
29 + "sourceHeading": "Spotify playlist writes require playlist-modify scopes"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "platform",
42 + "spotify"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/spotify-troubleshooting",
46 + "custom-spotify-toolkit-names-cannot-collide-with-the-built-in-spotify",
47 + "spotify-can-be-added-to-an-mcp-server-from-the-mcp-configs-page",
48 + "spotify-has-trigger-support",
49 + "spotify-library-scopes-may-need-to-be-added-to-the-auth-config-and-the",
50 + "spotify-playlist-writes-require-playlist-modify-scopes",
51 + "spotify-tokens-may-need-manual-provider-side-removal-when-programmatic",
52 + "spotify-troubleshooting"
53 + ],
54 + "relatedGuides": [],
55 + "externalResources": [],
56 + "updatedAt": "2026-07-16",
57 + "lastVerifiedAt": "2026-08-24",
58 + "reviewAfter": "2026-11-22",
59 + "freshness": "evergreen",
60 + "state": "published",
61 + "featured": false
62 +}
docs/kb/guides/toolkits-stripe.json new
+64
@@ -0,0 +1,64 @@
1 +{
2 + "slug": "toolkits-stripe",
3 + "title": "Stripe",
4 + "description": "Public support knowledge for Stripe.",
5 + "articlePath": "toolkits-stripe.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/stripe/public.md",
9 + "sourceHeading": "Stripe is supported and offers OAuth2 and API-key auth modes"
10 + },
11 + {
12 + "sourcePath": "toolkits/stripe/public.md",
13 + "sourceHeading": "For Stripe API-key auth, use the Stripe secret key from Developers -> API Keys -> Standard keys"
14 + },
15 + {
16 + "sourcePath": "toolkits/stripe/public.md",
17 + "sourceHeading": "One Stripe MCP/API-key connection maps to one Stripe account unless the customer uses Stripe Connect"
18 + },
19 + {
20 + "sourcePath": "toolkits/stripe/public.md",
21 + "sourceHeading": "MRR can be calculated from `STRIPE_LIST_SUBSCRIPTIONS`"
22 + },
23 + {
24 + "sourcePath": "toolkits/stripe/public.md",
25 + "sourceHeading": "Stripe payment-success triggers are available"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "platform",
38 + "stripe"
39 + ],
40 + "aliases": [
41 + "/kb/authentication/stripe-troubleshooting",
42 + "/kb/toolkits/duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records",
43 + "/kb/toolkits/stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n",
44 + "a-stripe-trigger-should-create-a-corresponding-subscription-webhook-in",
45 + "additional-stripe-endpoints-can-be-added-as-toolkit-requests",
46 + "duplicate-stripe-trigger-events-can-be-caused-by-stale-webhook-records",
47 + "mrr-can-be-calculated-from-stripe-list-subscriptions",
48 + "one-stripe-mcp-api-key-connection-maps-to-one-stripe-account-unless-th",
49 + "some-stripe-triggers-worked-with-api-key-auth-but-failed-with-oauth-on",
50 + "stripe-api-key-connections-require-a-secret-key",
51 + "stripe-dispute-payment-success-triggers-may-need-feature-requests-if-n",
52 + "stripe-may-require-customer-owned-credentials-because-a-default-oauth",
53 + "stripe-tokens-may-not-be-revocable-programmatically-through-provider-a",
54 + "stripe-troubleshooting"
55 + ],
56 + "relatedGuides": [],
57 + "externalResources": [],
58 + "updatedAt": "2026-06-24",
59 + "lastVerifiedAt": "2026-08-12",
60 + "reviewAfter": "2026-11-10",
61 + "freshness": "evergreen",
62 + "state": "published",
63 + "featured": false
64 +}
docs/kb/guides/toolkits-supabase.json new
+83
@@ -0,0 +1,83 @@
1 +{
2 + "slug": "toolkits-supabase",
3 + "title": "Supabase",
4 + "description": "Public support knowledge for Supabase.",
5 + "articlePath": "toolkits-supabase.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/supabase/public.md",
9 + "sourceHeading": "Supabase authorization is usually organization-scoped"
10 + },
11 + {
12 + "sourcePath": "toolkits/supabase/public.md",
13 + "sourceHeading": "Supabase API-key connections pass `supabase_personal_token` during connected account creation"
14 + },
15 + {
16 + "sourcePath": "toolkits/supabase/public.md",
17 + "sourceHeading": "Supabase supports both OAuth2 and API_KEY auth through Composio APIs"
18 + },
19 + {
20 + "sourcePath": "toolkits/supabase/public.md",
21 + "sourceHeading": "Supabase MCP in Cursor may need an explicit initiate-connection step"
22 + },
23 + {
24 + "sourcePath": "toolkits/supabase/public.md",
25 + "sourceHeading": "`SUPABASE_BETA_RUN_SQL_QUERY` is still available when configured in an MCP server"
26 + },
27 + {
28 + "sourcePath": "toolkits/supabase/public.md",
29 + "sourceHeading": "Hosted Supabase should use `https://api.supabase.com` as base URL, not the project URL"
30 + },
31 + {
32 + "sourcePath": "toolkits/supabase/public.md",
33 + "sourceHeading": "Self-hosted Supabase requires toolkit support for a custom base URL"
34 + },
35 + {
36 + "sourcePath": "toolkits/supabase/public.md",
37 + "sourceHeading": "Configure Supabase Management API scopes on the Supabase OAuth app"
38 + },
39 + {
40 + "sourcePath": "toolkits/supabase/public.md",
41 + "sourceHeading": "Supabase permission errors are often provider-side access-control failures"
42 + },
43 + {
44 + "sourcePath": "toolkits/supabase/public.md",
45 + "sourceHeading": "Diagnose Supabase rate limits from the underlying error"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "platform",
58 + "supabase"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/supabase-troubleshooting",
62 + "composio-does-not-enforce-hard-service-rate-limits-check-the-underlyin",
63 + "cursor-mcp-server-name-length-limits-can-break-supabase-mcp",
64 + "hosted-supabase-should-use-https-api-supabase-com-as-base-url-not-the",
65 + "limit-supabase-scopes-in-the-customer-s-oauth-app-not-through-composio",
66 + "self-hosted-supabase-requires-toolkit-support-for-a-custom-base-url",
67 + "supabase-api-key-connections-pass-supabase-personal-token-during-conne",
68 + "supabase-authorization-is-usually-organization-scoped",
69 + "supabase-beta-run-sql-query-is-still-available-when-configured-in-an-m",
70 + "supabase-mcp-in-cursor-may-need-an-explicit-initiate-connection-step",
71 + "supabase-permission-errors-are-often-provider-side-access-control-fail",
72 + "supabase-supports-both-oauth2-and-api-key-auth-through-composio-apis",
73 + "supabase-troubleshooting"
74 + ],
75 + "relatedGuides": [],
76 + "externalResources": [],
77 + "updatedAt": "2026-06-24",
78 + "lastVerifiedAt": "2026-08-17",
79 + "reviewAfter": "2026-11-15",
80 + "freshness": "evergreen",
81 + "state": "published",
82 + "featured": false
83 +}
docs/kb/guides/toolkits-tavily.json new
+46
@@ -0,0 +1,46 @@
1 +{
2 + "slug": "toolkits-tavily",
3 + "title": "Tavily",
4 + "description": "Public support knowledge for Tavily.",
5 + "articlePath": "toolkits-tavily.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/tavily/public.md",
9 + "sourceHeading": "Use COMPOSIO_SEARCH_TAVILY for Tavily search"
10 + },
11 + {
12 + "sourcePath": "toolkits/tavily/public.md",
13 + "sourceHeading": "Initiate Tavily API-key connections in the legacy JS SDK with generic_api_key"
14 + },
15 + {
16 + "sourcePath": "toolkits/tavily/public.md",
17 + "sourceHeading": "Use composio_search for auth-free Exa/Tavily-style search"
18 + }
19 + ],
20 + "topics": [
21 + "auth-config",
22 + "authentication",
23 + "sessions-and-execution",
24 + "toolkits-and-providers"
25 + ],
26 + "tags": [
27 + "for-you",
28 + "platform",
29 + "tavily"
30 + ],
31 + "aliases": [
32 + "/kb/toolkits/tavily-troubleshooting",
33 + "initiate-tavily-api-key-connections-in-the-legacy-js-sdk-with-generic",
34 + "tavily-troubleshooting",
35 + "use-composio-search-for-auth-free-exa-tavily-style-search",
36 + "use-composio-search-tavily-for-tavily-search"
37 + ],
38 + "relatedGuides": [],
39 + "externalResources": [],
40 + "updatedAt": "2026-06-24",
41 + "lastVerifiedAt": "2026-08-12",
42 + "reviewAfter": "2026-11-10",
43 + "freshness": "evergreen",
44 + "state": "published",
45 + "featured": false
46 +}
docs/kb/guides/toolkits-tiktok.json new
+69
@@ -0,0 +1,69 @@
1 +{
2 + "slug": "toolkits-tiktok",
3 + "title": "TikTok",
4 + "description": "Public support knowledge for TikTok.",
5 + "articlePath": "toolkits-tiktok.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/tiktok/public.md",
9 + "sourceHeading": "TikTok is supported, but customers generally need their own TikTok developer app"
10 + },
11 + {
12 + "sourcePath": "toolkits/tiktok/public.md",
13 + "sourceHeading": "TikTok URL-prefix verification must be done on a customer-owned redirect domain, not Composio's shared callback domain"
14 + },
15 + {
16 + "sourcePath": "toolkits/tiktok/public.md",
17 + "sourceHeading": "TikTok OAuth uses `client_key`; credential mismatch or old `client_id` handling causes `client_key` errors"
18 + },
19 + {
20 + "sourcePath": "toolkits/tiktok/public.md",
21 + "sourceHeading": "TikTok app status, scopes, and sandbox/production mode determine who can complete OAuth"
22 + },
23 + {
24 + "sourcePath": "toolkits/tiktok/public.md",
25 + "sourceHeading": "Old TikTok-specific MCP URL patterns are deprecated; use Connect MCP"
26 + },
27 + {
28 + "sourcePath": "toolkits/tiktok/public.md",
29 + "sourceHeading": "Public TikTok posting requires the customer's own app to pass TikTok's content posting audit"
30 + },
31 + {
32 + "sourcePath": "toolkits/tiktok/public.md",
33 + "sourceHeading": "TikTok Ads/Marketing may require a separate approved app and test credentials"
34 + },
35 + {
36 + "sourcePath": "toolkits/tiktok/public.md",
37 + "sourceHeading": "TikTok custom auth must request only approved scopes"
38 + }
39 + ],
40 + "topics": [
41 + "auth-config",
42 + "authentication",
43 + "errors-and-troubleshooting",
44 + "sessions-and-execution",
45 + "toolkits-and-providers"
46 + ],
47 + "tags": [
48 + "for-you",
49 + "platform",
50 + "tiktok"
51 + ],
52 + "aliases": [
53 + "/kb/toolkits/tiktok-troubleshooting",
54 + "connect-tiktok-with-your-own-developer-app",
55 + "fix-tiktok-client-key-errors",
56 + "old-tiktok-specific-mcp-url-patterns-are-deprecated-use-connect-mcp",
57 + "request-only-approved-tiktok-scopes",
58 + "tiktok-ads-marketing-may-require-a-separate-approved-app-and-test-cred",
59 + "tiktok-troubleshooting"
60 + ],
61 + "relatedGuides": [],
62 + "externalResources": [],
63 + "updatedAt": "2026-07-16",
64 + "lastVerifiedAt": "2026-08-12",
65 + "reviewAfter": "2026-11-10",
66 + "freshness": "evergreen",
67 + "state": "published",
68 + "featured": false
69 +}
docs/kb/guides/toolkits-trello.json new
+63
@@ -0,0 +1,63 @@
1 +{
2 + "slug": "toolkits-trello",
3 + "title": "Trello",
4 + "description": "Public support knowledge for Trello.",
5 + "articlePath": "toolkits-trello.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/trello/public.md",
9 + "sourceHeading": "Trello supports managed and customer-owned OAuth1"
10 + },
11 + {
12 + "sourcePath": "toolkits/trello/public.md",
13 + "sourceHeading": "Route Trello MCP calls by appending user_id or connected_account_id"
14 + },
15 + {
16 + "sourcePath": "toolkits/trello/public.md",
17 + "sourceHeading": "Connect Trello to Cursor by creating a Trello MCP instance and running the generated command"
18 + },
19 + {
20 + "sourcePath": "toolkits/trello/public.md",
21 + "sourceHeading": "Get the authenticated Trello user with TRELLO_GET_MEMBERS_BY_ID_MEMBER and idMember=me"
22 + },
23 + {
24 + "sourcePath": "toolkits/trello/public.md",
25 + "sourceHeading": "Invalid Trello board ID can break Trello triggers"
26 + },
27 + {
28 + "sourcePath": "toolkits/trello/public.md",
29 + "sourceHeading": "Legacy mcp.composio.dev Trello endpoint should be migrated to Tool Router or Connect"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "platform",
42 + "trello"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/trello-troubleshooting",
46 + "connect-trello-to-cursor-by-creating-a-trello-mcp-instance-and-running",
47 + "get-the-authenticated-trello-user-with-trello-get-members-by-id-member",
48 + "invalid-trello-board-id-can-break-trello-triggers",
49 + "legacy-mcp-composio-dev-trello-endpoint-should-be-migrated-to-tool-rou",
50 + "old-trello-auth-configs-can-fail-after-oauth-app-changes-create-a-new",
51 + "route-trello-mcp-calls-by-appending-user-id-or-connected-account-id",
52 + "trello-supports-oauth1-and-bearer-token-authentication",
53 + "trello-troubleshooting"
54 + ],
55 + "relatedGuides": [],
56 + "externalResources": [],
57 + "updatedAt": "2026-06-24",
58 + "lastVerifiedAt": "2026-08-24",
59 + "reviewAfter": "2026-11-22",
60 + "freshness": "evergreen",
61 + "state": "published",
62 + "featured": false
63 +}
docs/kb/guides/toolkits-twitter.json new
+61
@@ -0,0 +1,61 @@
1 +{
2 + "slug": "toolkits-twitter",
3 + "title": "Twitter",
4 + "description": "Public support knowledge for Twitter.",
5 + "articlePath": "toolkits-twitter.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/twitter/public.md",
9 + "sourceHeading": "Twitter/X requires a customer-owned OAuth app"
10 + },
11 + {
12 + "sourcePath": "toolkits/twitter/public.md",
13 + "sourceHeading": "Use the current auth-config callback URI for Twitter OAuth callback mismatch errors"
14 + },
15 + {
16 + "sourcePath": "toolkits/twitter/public.md",
17 + "sourceHeading": "Twitter/X posts must stay within X's character counting rules"
18 + },
19 + {
20 + "sourcePath": "toolkits/twitter/public.md",
21 + "sourceHeading": "`client-not-enrolled` and `App not linked to project` usually point to Twitter developer app/project setup issues"
22 + },
23 + {
24 + "sourcePath": "toolkits/twitter/public.md",
25 + "sourceHeading": "If X v2 API support appears missing, check for an older Twitter toolkit version"
26 + },
27 + {
28 + "sourcePath": "toolkits/twitter/public.md",
29 + "sourceHeading": "Search and other app-only actions use the Application Bearer Token"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "platform",
42 + "twitter"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/twitter-troubleshooting",
46 + "connect-x-twitter-with-your-own-developer-app",
47 + "if-x-v2-api-support-appears-missing-check-for-an-older-twitter-toolkit",
48 + "search-and-other-app-only-actions-use-the-application-bearer-token",
49 + "twitter-troubleshooting",
50 + "twitter-x-posts-must-stay-within-x-s-character-counting-rules",
51 + "use-composio-s-v1-auth-app-redirect-uri-for-twitter-oauth-callback-mis"
52 + ],
53 + "relatedGuides": [],
54 + "externalResources": [],
55 + "updatedAt": "2026-07-16",
56 + "lastVerifiedAt": "2026-08-24",
57 + "reviewAfter": "2026-11-22",
58 + "freshness": "evergreen",
59 + "state": "published",
60 + "featured": false
61 +}
docs/kb/guides/toolkits-webflow.json new
+46
@@ -0,0 +1,46 @@
1 +{
2 + "slug": "toolkits-webflow",
3 + "title": "Webflow",
4 + "description": "Public support knowledge for Webflow.",
5 + "articlePath": "toolkits-webflow.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/webflow/public.md",
9 + "sourceHeading": "Create or update Webflow collection items with the draft/live flag"
10 + },
11 + {
12 + "sourcePath": "toolkits/webflow/public.md",
13 + "sourceHeading": "Use the current Webflow toolkit version for recently added page tools"
14 + },
15 + {
16 + "sourcePath": "toolkits/webflow/public.md",
17 + "sourceHeading": "Deprecated Webflow v1 endpoints caused publish-site integration failures"
18 + }
19 + ],
20 + "topics": [
21 + "errors-and-troubleshooting",
22 + "sessions-and-execution",
23 + "toolkits-and-providers"
24 + ],
25 + "tags": [
26 + "for-you",
27 + "platform",
28 + "webflow"
29 + ],
30 + "aliases": [
31 + "/kb/toolkits/webflow-troubleshooting",
32 + "create-or-update-webflow-collection-items-with-the-draft-live-flag",
33 + "deprecated-webflow-v1-endpoints-caused-publish-site-integration-failur",
34 + "use-a-custom-webflow-oauth-app-when-the-default-app-cannot-authorize-w",
35 + "use-the-current-webflow-toolkit-version-for-recently-added-page-tools",
36 + "webflow-troubleshooting"
37 + ],
38 + "relatedGuides": [],
39 + "externalResources": [],
40 + "updatedAt": "2026-06-24",
41 + "lastVerifiedAt": "2026-08-17",
42 + "reviewAfter": "2026-11-15",
43 + "freshness": "evergreen",
44 + "state": "published",
45 + "featured": false
46 +}
docs/kb/guides/toolkits-whatsapp.json new
+94
@@ -0,0 +1,94 @@
1 +{
2 + "slug": "toolkits-whatsapp",
3 + "title": "WhatsApp",
4 + "description": "Public support knowledge for WhatsApp.",
5 + "articlePath": "toolkits-whatsapp.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/whatsapp/public.md",
9 + "sourceHeading": "WhatsApp toolkit supports WhatsApp Business API accounts, not personal WhatsApp accounts"
10 + },
11 + {
12 + "sourcePath": "toolkits/whatsapp/public.md",
13 + "sourceHeading": "WABA ID is required for WhatsApp connections"
14 + },
15 + {
16 + "sourcePath": "toolkits/whatsapp/public.md",
17 + "sourceHeading": "WhatsApp API key auth needs both system user token and WABA ID"
18 + },
19 + {
20 + "sourcePath": "toolkits/whatsapp/public.md",
21 + "sourceHeading": "WhatsApp OAuth2 initiation still requires `generic_id` as the WABA ID"
22 + },
23 + {
24 + "sourcePath": "toolkits/whatsapp/public.md",
25 + "sourceHeading": "WhatsApp OAuth requires a Meta developer app with Business use case enabled and published"
26 + },
27 + {
28 + "sourcePath": "toolkits/whatsapp/public.md",
29 + "sourceHeading": "Meta OAuth errors can require adding the Composio redirect URI in the Meta app"
30 + },
31 + {
32 + "sourcePath": "toolkits/whatsapp/public.md",
33 + "sourceHeading": "WhatsApp template messages require an existing template before sending"
34 + },
35 + {
36 + "sourcePath": "toolkits/whatsapp/public.md",
37 + "sourceHeading": "`WHATSAPP_SEND_TEMPLATE_MESSAGE` supports `components` in newer toolkit versions"
38 + },
39 + {
40 + "sourcePath": "toolkits/whatsapp/public.md",
41 + "sourceHeading": "When sending WhatsApp messages, pass real `phone_number_id` and `to_number` values"
42 + },
43 + {
44 + "sourcePath": "toolkits/whatsapp/public.md",
45 + "sourceHeading": "Reading WhatsApp replies is better modeled as triggers/webhooks than a normal read API"
46 + },
47 + {
48 + "sourcePath": "toolkits/whatsapp/public.md",
49 + "sourceHeading": "Use Proxy Execute when a WhatsApp/Meta workflow needs direct provider API access with scoped credentials"
50 + },
51 + {
52 + "sourcePath": "toolkits/whatsapp/public.md",
53 + "sourceHeading": "WhatsApp Business app coexistence is enabled through Meta Embedded Signup"
54 + }
55 + ],
56 + "topics": [
57 + "auth-config",
58 + "authentication",
59 + "errors-and-troubleshooting",
60 + "sessions-and-execution",
61 + "toolkits-and-providers"
62 + ],
63 + "tags": [
64 + "for-you",
65 + "platform",
66 + "whatsapp"
67 + ],
68 + "aliases": [
69 + "/kb/toolkits/whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro",
70 + "/kb/toolkits/whatsapp-troubleshooting",
71 + "meta-oauth-errors-can-require-adding-the-composio-redirect-uri-in-the",
72 + "reading-whatsapp-replies-is-better-modeled-as-triggers-webhooks-than-a",
73 + "use-proxy-execute-when-a-whatsapp-meta-workflow-needs-direct-provider",
74 + "waba-id-is-required-for-whatsapp-connections",
75 + "whatsapp-api-key-auth-needs-both-system-user-token-and-waba-id",
76 + "whatsapp-business-app-coexistence-is-enabled-through-meta-embedded-sig",
77 + "whatsapp-has-limited-beta-support-and-some-requested-apis-must-go-thro",
78 + "whatsapp-oauth-requires-a-meta-developer-app-with-business-use-case-en",
79 + "whatsapp-oauth2-initiation-still-requires-generic-id-as-the-waba-id",
80 + "whatsapp-send-template-message-supports-components-in-newer-toolkit-ve",
81 + "whatsapp-template-messages-require-an-existing-template-before-sending",
82 + "whatsapp-toolkit-supports-whatsapp-business-api-accounts-not-personal",
83 + "whatsapp-troubleshooting",
84 + "when-sending-whatsapp-messages-pass-real-phone-number-id-and-to-number"
85 + ],
86 + "relatedGuides": [],
87 + "externalResources": [],
88 + "updatedAt": "2026-07-14",
89 + "lastVerifiedAt": "2026-08-12",
90 + "reviewAfter": "2026-11-10",
91 + "freshness": "evergreen",
92 + "state": "published",
93 + "featured": false
94 +}
docs/kb/guides/toolkits-wrike.json new
+61
@@ -0,0 +1,61 @@
1 +{
2 + "slug": "toolkits-wrike",
3 + "title": "Wrike",
4 + "description": "Public support knowledge for Wrike.",
5 + "articlePath": "toolkits-wrike.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/wrike/public.md",
9 + "sourceHeading": "Use the Wrike user id, not the account id, when assigning or updating task users"
10 + },
11 + {
12 + "sourcePath": "toolkits/wrike/public.md",
13 + "sourceHeading": "Wrike task responses expose multiple user-id fields and can resolve names"
14 + },
15 + {
16 + "sourcePath": "toolkits/wrike/public.md",
17 + "sourceHeading": "Assignee is not a native field in Wrike fetch-task API responses"
18 + },
19 + {
20 + "sourcePath": "toolkits/wrike/public.md",
21 + "sourceHeading": "Use the Composio proxy endpoint or SDK executeRequest for direct Wrike API calls"
22 + },
23 + {
24 + "sourcePath": "toolkits/wrike/public.md",
25 + "sourceHeading": "Pass entityId as a string when getConnections returns 404 in v3 SDK flows"
26 + },
27 + {
28 + "sourcePath": "toolkits/wrike/public.md",
29 + "sourceHeading": "Use the latest Wrike toolkit version for nested folder pagination"
30 + }
31 + ],
32 + "topics": [
33 + "authentication",
34 + "errors-and-troubleshooting",
35 + "sessions-and-execution",
36 + "toolkits-and-providers"
37 + ],
38 + "tags": [
39 + "for-you",
40 + "platform",
41 + "wrike"
42 + ],
43 + "aliases": [
44 + "/kb/toolkits/wrike-troubleshooting",
45 + "assignee-is-not-a-native-field-in-wrike-fetch-task-api-responses",
46 + "pass-entityid-as-a-string-when-getconnections-returns-404-in-v3-sdk-fl",
47 + "use-the-composio-proxy-endpoint-or-sdk-executerequest-for-direct-wrike",
48 + "use-the-wrike-user-id-not-the-account-id-when-assigning-or-updating-ta",
49 + "use-wrike-toolkit-version-20260204-00-or-latest-for-nested-folder-pagi",
50 + "wrike-task-responses-expose-multiple-user-id-fields-and-can-resolve-na",
51 + "wrike-troubleshooting"
52 + ],
53 + "relatedGuides": [],
54 + "externalResources": [],
55 + "updatedAt": "2026-06-24",
56 + "lastVerifiedAt": "2026-08-12",
57 + "reviewAfter": "2026-11-10",
58 + "freshness": "evergreen",
59 + "state": "published",
60 + "featured": false
61 +}
docs/kb/guides/toolkits-xero.json new
+58
@@ -0,0 +1,58 @@
1 +{
2 + "slug": "toolkits-xero",
3 + "title": "Xero",
4 + "description": "Public support knowledge for Xero.",
5 + "articlePath": "toolkits-xero.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/xero/public.md",
9 + "sourceHeading": "Xero redirect URI must match the current auth-config flow exactly"
10 + },
11 + {
12 + "sourcePath": "toolkits/xero/public.md",
13 + "sourceHeading": "Xero OAuth app should be a Web app and the client secret must match the auth config"
14 + },
15 + {
16 + "sourcePath": "toolkits/xero/public.md",
17 + "sourceHeading": "Remove deprecated Xero scopes that cause invalid-scope/CSP/login errors"
18 + },
19 + {
20 + "sourcePath": "toolkits/xero/public.md",
21 + "sourceHeading": "Connect MCP discovers Xero tools through meta-tools instead of preloading every tool"
22 + },
23 + {
24 + "sourcePath": "toolkits/xero/public.md",
25 + "sourceHeading": "Connect MCP and Platform MCP Xero connections are independent"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "platform",
38 + "xero"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/xero-troubleshooting",
42 + "connect-mcp-and-platform-mcp-xero-connections-are-independent",
43 + "connect-mcp-discovers-xero-tools-through-meta-tools-instead-of-preload",
44 + "connect-xero-with-your-own-oauth-app",
45 + "if-for-you-xero-connect-button-is-blocked-use-connect-mcp-directly-whi",
46 + "xero-can-be-blocked-in-claude-cowork-by-payment-processing-session-res",
47 + "xero-redirect-uri-must-match-exactly-v1-auth-apps-callback-can-be-requ",
48 + "xero-troubleshooting"
49 + ],
50 + "relatedGuides": [],
51 + "externalResources": [],
52 + "updatedAt": "2026-06-24",
53 + "lastVerifiedAt": "2026-08-12",
54 + "reviewAfter": "2026-11-10",
55 + "freshness": "evergreen",
56 + "state": "published",
57 + "featured": false
58 +}
docs/kb/guides/toolkits-ynab.json new
+32
@@ -0,0 +1,32 @@
1 +{
2 + "slug": "toolkits-ynab",
3 + "title": "YNAB authentication",
4 + "description": "Current OAuth setup for the YNAB toolkit.",
5 + "articlePath": "toolkits-ynab.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/ynab/public.md",
9 + "sourceHeading": "YNAB supports managed and customer-owned OAuth"
10 + }
11 + ],
12 + "topics": [
13 + "auth-config",
14 + "authentication",
15 + "errors-and-troubleshooting",
16 + "toolkits-and-providers"
17 + ],
18 + "tags": [
19 + "for-you",
20 + "platform",
21 + "ynab"
22 + ],
23 + "aliases": [],
24 + "relatedGuides": [],
25 + "externalResources": [],
26 + "updatedAt": "2026-08-17",
27 + "lastVerifiedAt": "2026-08-24",
28 + "reviewAfter": "2026-11-22",
29 + "freshness": "evergreen",
30 + "state": "published",
31 + "featured": false
32 +}
docs/kb/guides/toolkits-youtube.json new
+64
@@ -0,0 +1,64 @@
1 +{
2 + "slug": "toolkits-youtube",
3 + "title": "YouTube",
4 + "description": "Public support knowledge for YouTube.",
5 + "articlePath": "toolkits-youtube.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/youtube/public.md",
9 + "sourceHeading": "`YOUTUBE_UPLOAD_VIDEO` with `videoFilePath` is SDK-oriented and expects a full file path"
10 + },
11 + {
12 + "sourcePath": "toolkits/youtube/public.md",
13 + "sourceHeading": "Use direct file paths or the current multipart upload action for YouTube videos"
14 + },
15 + {
16 + "sourcePath": "toolkits/youtube/public.md",
17 + "sourceHeading": "Diagnose YouTube `processing abandoned` from the current upload and provider state"
18 + },
19 + {
20 + "sourcePath": "toolkits/youtube/public.md",
21 + "sourceHeading": "YouTube caption download requires `https://www.googleapis.com/auth/youtube.force-ssl`"
22 + },
23 + {
24 + "sourcePath": "toolkits/youtube/public.md",
25 + "sourceHeading": "YouTube has trigger support, but trigger creation errors may only surface at trigger setup time"
26 + },
27 + {
28 + "sourcePath": "toolkits/youtube/public.md",
29 + "sourceHeading": "`uploadLimitExceeded` is a YouTube channel limit, not an OAuth-app quota"
30 + }
31 + ],
32 + "topics": [
33 + "auth-config",
34 + "authentication",
35 + "errors-and-troubleshooting",
36 + "sessions-and-execution",
37 + "toolkits-and-providers"
38 + ],
39 + "tags": [
40 + "for-you",
41 + "platform",
42 + "youtube"
43 + ],
44 + "aliases": [
45 + "/kb/toolkits/youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran",
46 + "/kb/toolkits/youtube-troubleshooting",
47 + "use-a-custom-youtube-oauth-app-in-production-to-avoid-shared-default-a",
48 + "use-direct-file-paths-or-multipart-upload-for-youtube-videos-fileuploa",
49 + "youtube-caption-download-requires-https-www-googleapis-com-auth-youtub",
50 + "youtube-has-trigger-support-but-trigger-creation-errors-may-only-surfa",
51 + "youtube-processing-abandoned-can-be-provider-side-but-upload-byte-tran",
52 + "youtube-transcript-community-post-tools-may-need-feature-requests-or-c",
53 + "youtube-troubleshooting",
54 + "youtube-upload-video-with-videofilepath-is-sdk-oriented-and-expects-a"
55 + ],
56 + "relatedGuides": [],
57 + "externalResources": [],
58 + "updatedAt": "2026-06-24",
59 + "lastVerifiedAt": "2026-08-17",
60 + "reviewAfter": "2026-11-15",
61 + "freshness": "evergreen",
62 + "state": "published",
63 + "featured": false
64 +}
docs/kb/guides/toolkits-zendesk.json new
+77
@@ -0,0 +1,77 @@
1 +{
2 + "slug": "toolkits-zendesk",
3 + "title": "Zendesk",
4 + "description": "Public support knowledge for Zendesk.",
5 + "articlePath": "toolkits-zendesk.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/zendesk/public.md",
9 + "sourceHeading": "Zendesk OAuth setup does not require manually entering an access token"
10 + },
11 + {
12 + "sourcePath": "toolkits/zendesk/public.md",
13 + "sourceHeading": "Zendesk connections require the account subdomain"
14 + },
15 + {
16 + "sourcePath": "toolkits/zendesk/public.md",
17 + "sourceHeading": "Initiate Zendesk OAuth connections by passing `subdomain` in config values"
18 + },
19 + {
20 + "sourcePath": "toolkits/zendesk/public.md",
21 + "sourceHeading": "Zendesk API-key/basic auth initiation passes `subdomain` and base64 encoded credentials"
22 + },
23 + {
24 + "sourcePath": "toolkits/zendesk/public.md",
25 + "sourceHeading": "Include `toolkit_versions` when listing Zendesk tools through the API"
26 + },
27 + {
28 + "sourcePath": "toolkits/zendesk/public.md",
29 + "sourceHeading": "`ZENDESK_SEARCH_ZENDESK` was added for Zendesk search use cases"
30 + },
31 + {
32 + "sourcePath": "toolkits/zendesk/public.md",
33 + "sourceHeading": "`ZENDESK_UPDATE_ZENDESK_TICKET` is available for updating Zendesk tickets"
34 + },
35 + {
36 + "sourcePath": "toolkits/zendesk/public.md",
37 + "sourceHeading": "Zendesk get-ticket-by-id returns ticket details in one tool call"
38 + },
39 + {
40 + "sourcePath": "toolkits/zendesk/public.md",
41 + "sourceHeading": "Zendesk supports triggers in Composio"
42 + }
43 + ],
44 + "topics": [
45 + "auth-config",
46 + "authentication",
47 + "errors-and-troubleshooting",
48 + "sessions-and-execution",
49 + "toolkits-and-providers"
50 + ],
51 + "tags": [
52 + "for-you",
53 + "platform",
54 + "zendesk"
55 + ],
56 + "aliases": [
57 + "/kb/toolkits/zendesk-troubleshooting",
58 + "include-toolkit-versions-when-listing-zendesk-tools-through-the-api",
59 + "initiate-zendesk-oauth-connections-by-passing-subdomain-in-config-valu",
60 + "use-your-own-zendesk-oauth-app-for-production-or-when-the-default-app",
61 + "zendesk-api-key-basic-auth-initiation-passes-subdomain-and-base64-enco",
62 + "zendesk-connections-require-the-account-subdomain",
63 + "zendesk-get-ticket-by-id-returns-ticket-details-in-one-tool-call",
64 + "zendesk-is-not-officially-supported-in-langflow-connect-through-the-co",
65 + "zendesk-oauth-setup-does-not-require-manually-entering-an-access-token",
66 + "zendesk-troubleshooting",
67 + "zendesk-update-zendesk-ticket-is-available-for-updating-zendesk-ticket"
68 + ],
69 + "relatedGuides": [],
70 + "externalResources": [],
71 + "updatedAt": "2026-06-24",
72 + "lastVerifiedAt": "2026-08-12",
73 + "reviewAfter": "2026-11-10",
74 + "freshness": "evergreen",
75 + "state": "published",
76 + "featured": false
77 +}
docs/kb/guides/toolkits-zoho-books.json new
+54
@@ -0,0 +1,54 @@
1 +{
2 + "slug": "toolkits-zoho-books",
3 + "title": "Zoho Books",
4 + "description": "Public support knowledge for Zoho Books.",
5 + "articlePath": "toolkits-zoho-books.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/zoho_books/public.md",
9 + "sourceHeading": "Use Zoho Invoice for create estimate"
10 + },
11 + {
12 + "sourcePath": "toolkits/zoho_books/public.md",
13 + "sourceHeading": "Optional Zoho Books item rate filters do not have default values"
14 + },
15 + {
16 + "sourcePath": "toolkits/zoho_books/public.md",
17 + "sourceHeading": "Pin Zoho Books toolkit version when reproducing list-items behavior"
18 + },
19 + {
20 + "sourcePath": "toolkits/zoho_books/public.md",
21 + "sourceHeading": "Zoho domain suffix parameter expects the extension value"
22 + }
23 + ],
24 + "topics": [
25 + "authentication",
26 + "errors-and-troubleshooting",
27 + "sessions-and-execution",
28 + "toolkits-and-providers"
29 + ],
30 + "tags": [
31 + "for-you",
32 + "platform",
33 + "zoho_books"
34 + ],
35 + "aliases": [
36 + "/kb/toolkits/zoho-books-troubleshooting",
37 + "optional-zoho-books-item-rate-filters-do-not-have-default-values",
38 + "pin-zoho-books-toolkit-version-when-reproducing-list-items-behavior",
39 + "use-existing-bill-read-tools-or-file-a-request-for-missing-bill-creati",
40 + "zoho-books-troubleshooting",
41 + "zoho-domain-suffix-parameter-expects-the-extension-value"
42 + ],
43 + "relatedGuides": [],
44 + "externalResources": [],
45 + "updatedAt": "2026-06-24",
46 + "lastVerifiedAt": "2026-08-12",
47 + "reviewAfter": "2026-11-10",
48 + "freshness": "evergreen",
49 + "state": "published",
50 + "featured": false,
51 + "verifyIgnoreToolSlugs": [
52 + "ZOHO_BOOKS_CREATE_ESTIMATE"
53 + ]
54 +}
docs/kb/guides/toolkits-zoho-mail.json new
+51
@@ -0,0 +1,51 @@
1 +{
2 + "slug": "toolkits-zoho-mail",
3 + "title": "Zoho Mail",
4 + "description": "Public support knowledge for Zoho Mail.",
5 + "articlePath": "toolkits-zoho-mail.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/zoho_mail/public.md",
9 + "sourceHeading": "ZOHO_MAIL_MESSAGES_SEND_EMAIL supports sending attachments"
10 + },
11 + {
12 + "sourcePath": "toolkits/zoho_mail/public.md",
13 + "sourceHeading": "Pass the correct Zoho region when connecting Zoho Mail"
14 + },
15 + {
16 + "sourcePath": "toolkits/zoho_mail/public.md",
17 + "sourceHeading": "Zoho Mail account_id must be handled as a string to avoid JavaScript precision loss"
18 + },
19 + {
20 + "sourcePath": "toolkits/zoho_mail/public.md",
21 + "sourceHeading": "Connect MCP is agent-oriented; authenticate Zoho Mail in Connect dashboard before tool use"
22 + }
23 + ],
24 + "topics": [
25 + "errors-and-troubleshooting",
26 + "sessions-and-execution",
27 + "toolkits-and-providers"
28 + ],
29 + "tags": [
30 + "for-you",
31 + "platform",
32 + "zoho_mail"
33 + ],
34 + "aliases": [
35 + "/kb/toolkits/zoho-mail-troubleshooting",
36 + "connect-mcp-is-agent-oriented-authenticate-zoho-mail-in-connect-dashbo",
37 + "pass-the-correct-zoho-region-when-connecting-zoho-mail",
38 + "zoho-mail-account-id-must-be-handled-as-a-string-to-avoid-javascript-p",
39 + "zoho-mail-attachment-download-support-should-be-treated-as-a-feature-r",
40 + "zoho-mail-messages-send-email-supports-sending-attachments",
41 + "zoho-mail-troubleshooting"
42 + ],
43 + "relatedGuides": [],
44 + "externalResources": [],
45 + "updatedAt": "2026-06-24",
46 + "lastVerifiedAt": "2026-08-12",
47 + "reviewAfter": "2026-11-10",
48 + "freshness": "evergreen",
49 + "state": "published",
50 + "featured": false
51 +}
docs/kb/guides/toolkits-zoho.json new
+85
@@ -0,0 +1,85 @@
1 +{
2 + "slug": "toolkits-zoho",
3 + "title": "Zoho",
4 + "description": "Public support knowledge for Zoho.",
5 + "articlePath": "toolkits-zoho.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/zoho/public.md",
9 + "sourceHeading": "`ZOHO_MAIL_MESSAGES_SEND_EMAIL` supports attachments in newer versions"
10 + },
11 + {
12 + "sourcePath": "toolkits/zoho/public.md",
13 + "sourceHeading": "Zoho connections require the correct region/domain extension"
14 + },
15 + {
16 + "sourcePath": "toolkits/zoho/public.md",
17 + "sourceHeading": "Zoho Mail uses `suffix.one` as the connection initiation domain-extension field"
18 + },
19 + {
20 + "sourcePath": "toolkits/zoho/public.md",
21 + "sourceHeading": "Zoho auth config and connection required fields can be fetched from toolkit schema APIs/SDK"
22 + },
23 + {
24 + "sourcePath": "toolkits/zoho/public.md",
25 + "sourceHeading": "Zoho Books create-estimate moved to the `zoho_invoice` toolkit"
26 + },
27 + {
28 + "sourcePath": "toolkits/zoho/public.md",
29 + "sourceHeading": "`ZOHO_BOOKS_LIST_ITEMS` has no default `rate`; optional fields can be omitted"
30 + },
31 + {
32 + "sourcePath": "toolkits/zoho/public.md",
33 + "sourceHeading": "Use `ZOHO_GET_ZOHO_RECORDS` to find a `lead_id` before converting a Zoho lead"
34 + },
35 + {
36 + "sourcePath": "toolkits/zoho/public.md",
37 + "sourceHeading": "Zoho record listing can require page tokens and is subject to Zoho rate limits"
38 + },
39 + {
40 + "sourcePath": "toolkits/zoho/public.md",
41 + "sourceHeading": "Zoho MCP setup uses OAuth2 and should initiate a new connection from the client/dashboard"
42 + },
43 + {
44 + "sourcePath": "toolkits/zoho/public.md",
45 + "sourceHeading": "Zoho Mail account IDs should be treated as strings to avoid JS safe-integer precision loss"
46 + }
47 + ],
48 + "topics": [
49 + "auth-config",
50 + "authentication",
51 + "errors-and-troubleshooting",
52 + "sessions-and-execution",
53 + "toolkits-and-providers"
54 + ],
55 + "tags": [
56 + "for-you",
57 + "platform",
58 + "zoho"
59 + ],
60 + "aliases": [
61 + "/kb/toolkits/zoho-troubleshooting",
62 + "request-zoho-mail-attachment-download-if-the-current-toolkit-does-not",
63 + "some-zoho-surfaces-may-be-auth-only-or-lack-formal-tools-use-custom-to",
64 + "use-zoho-get-zoho-records-to-find-a-lead-id-before-converting-a-zoho-l",
65 + "zoho-auth-config-and-connection-required-fields-can-be-fetched-from-to",
66 + "zoho-books-bill-tools-exist-but-missing-purchase-order-bill-flows-may",
67 + "zoho-books-create-estimate-moved-to-the-zoho-invoice-toolkit",
68 + "zoho-books-list-items-has-no-default-rate-optional-fields-can-be-omitt",
69 + "zoho-connections-require-the-correct-region-domain-extension",
70 + "zoho-mail-account-ids-should-be-treated-as-strings-to-avoid-js-safe-in",
71 + "zoho-mail-messages-send-email-supports-attachments-in-newer-versions",
72 + "zoho-mail-uses-suffix-one-as-the-connection-initiation-domain-extensio",
73 + "zoho-mcp-setup-uses-oauth2-and-should-initiate-a-new-connection-from-t",
74 + "zoho-record-listing-can-require-page-tokens-and-is-subject-to-zoho-rat",
75 + "zoho-troubleshooting"
76 + ],
77 + "relatedGuides": [],
78 + "externalResources": [],
79 + "updatedAt": "2026-06-24",
80 + "lastVerifiedAt": "2026-08-12",
81 + "reviewAfter": "2026-11-10",
82 + "freshness": "evergreen",
83 + "state": "published",
84 + "featured": false
85 +}
docs/kb/guides/toolkits-zoom.json new
+59
@@ -0,0 +1,59 @@
1 +{
2 + "slug": "toolkits-zoom",
3 + "title": "Zoom",
4 + "description": "Public support knowledge for Zoom.",
5 + "articlePath": "toolkits-zoom.md",
6 + "sources": [
7 + {
8 + "sourcePath": "toolkits/zoom/public.md",
9 + "sourceHeading": "Zoom custom OAuth apps may only connect users in the app owner's Zoom organization unless configured/approved otherwise"
10 + },
11 + {
12 + "sourcePath": "toolkits/zoom/public.md",
13 + "sourceHeading": "Zoom should use the default Composio redirect URL unless the auth guide says otherwise"
14 + },
15 + {
16 + "sourcePath": "toolkits/zoom/public.md",
17 + "sourceHeading": "`ZOOM_GET_A_MEETING_SUMMARY` needs the correct past-meeting UUID and auto summary enabled"
18 + },
19 + {
20 + "sourcePath": "toolkits/zoom/public.md",
21 + "sourceHeading": "Zoom delete/summary tools may require extra scopes in a custom OAuth app"
22 + },
23 + {
24 + "sourcePath": "toolkits/zoom/public.md",
25 + "sourceHeading": "Zoom OAuth consent branding comes from the customer's OAuth app"
26 + }
27 + ],
28 + "topics": [
29 + "auth-config",
30 + "authentication",
31 + "errors-and-troubleshooting",
32 + "sessions-and-execution",
33 + "toolkits-and-providers"
34 + ],
35 + "tags": [
36 + "for-you",
37 + "platform",
38 + "zoom"
39 + ],
40 + "aliases": [
41 + "/kb/toolkits/use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav",
42 + "/kb/toolkits/zoom-troubleshooting",
43 + "create-a-new-zoom-auth-config-if-the-default-oauth-app-changed-after-t",
44 + "use-a-custom-zoom-oauth-app-when-the-composio-managed-zoom-app-is-unav",
45 + "zoom-custom-oauth-apps-may-only-connect-users-in-the-app-owner-s-zoom",
46 + "zoom-get-a-meeting-summary-needs-the-correct-past-meeting-uuid-and-aut",
47 + "zoom-oauth-consent-branding-comes-from-the-customer-s-oauth-app",
48 + "zoom-should-use-the-default-composio-redirect-url-unless-the-auth-guid",
49 + "zoom-troubleshooting"
50 + ],
51 + "relatedGuides": [],
52 + "externalResources": [],
53 + "updatedAt": "2026-06-24",
54 + "lastVerifiedAt": "2026-08-12",
55 + "reviewAfter": "2026-11-10",
56 + "freshness": "evergreen",
57 + "state": "published",
58 + "featured": false
59 +}
docs/kb/manifest.json
-6791
@@ -1,11 +1,5 @@
1 {
2 "schemaVersion": 2,
3 - "source": {
4 - "repository": "ComposioHQ/support-knowledge",
5 - "commit": "5eac683455ff252a7a3b62f33ab6566445009b52",
6 - "capturedAt": "2026-08-25",
7 - "contentHash": "sha256:491f469688b25190d96a01f233067b10c5027db25d1a4da5b754dfcb666ddcb4"
8 - },
3 "topics": [
4 {
5 "slug": "account-and-billing",
@@ -61,6790 +55,5 @@
55 "description": "Support guidance for workflows.",
56 "featuredRank": 9
57 }
64 - ],
65 - "guides": [
66 - {
67 - "slug": "consumer-project-boundaries-and-auth-selection",
68 - "title": "Consumer and Developer Project Boundaries",
69 - "description": "Public support knowledge for Consumer and Developer Project Boundaries.",
70 - "articlePath": "consumer-project-boundaries-and-auth-selection.md",
71 - "sources": [
72 - {
73 - "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
74 - "sourceHeading": "Rotate the Connect MCP consumer key"
75 - },
76 - {
77 - "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
78 - "sourceHeading": "Workspace members do not automatically share For You connections"
79 - },
80 - {
81 - "sourcePath": "consumer/project-boundaries-and-auth-selection/public.md",
82 - "sourceHeading": "Shared connections must be explicitly allowed and pinned"
83 - }
84 - ],
85 - "topics": [
86 - "authentication",
87 - "errors-and-troubleshooting",
88 - "getting-started",
89 - "sessions-and-execution"
90 - ],
91 - "tags": [
92 - "consumer",
93 - "for-you",
94 - "project-boundaries-and-auth-selection"
95 - ],
96 - "aliases": [
97 - "/kb/composio-for-you/workspace-members-do-not-automatically-share-for-you-connections",
98 - "workspace-members-do-not-automatically-share-for-you-connections"
99 - ],
100 - "relatedGuides": [],
101 - "externalResources": [],
102 - "updatedAt": "2026-07-16",
103 - "lastVerifiedAt": "2026-08-17",
104 - "reviewAfter": "2026-11-15",
105 - "freshness": "evergreen",
106 - "state": "published",
107 - "featured": false
108 - },
109 - {
110 - "slug": "dashboard-account-deletion",
111 - "title": "Delete a Composio organization",
112 - "description": "Current self-service path and safety checks for organization deletion.",
113 - "articlePath": "dashboard-account-deletion.md",
114 - "sources": [
115 - {
116 - "sourcePath": "dashboard/account-deletion/public.md",
117 - "sourceHeading": "Organization admins can use Delete this organization"
118 - }
119 - ],
120 - "topics": [
121 - "account-and-billing"
122 - ],
123 - "tags": [
124 - "account-deletion",
125 - "dashboard",
126 - "for-you",
127 - "platform"
128 - ],
129 - "aliases": [],
130 - "relatedGuides": [],
131 - "externalResources": [],
132 - "updatedAt": "2026-08-17",
133 - "lastVerifiedAt": "2026-08-17",
134 - "reviewAfter": "2026-11-15",
135 - "freshness": "evergreen",
136 - "state": "published",
137 - "featured": false
138 - },
139 - {
140 - "slug": "dashboard-auth-configs-navigation",
141 - "title": "Manage Platform auth configs",
142 - "description": "Current dashboard steps for creating and managing Platform auth configs.",
143 - "articlePath": "dashboard-auth-configs-navigation.md",
144 - "sources": [
145 - {
146 - "sourcePath": "dashboard/auth-configs-navigation/public.md",
147 - "sourceHeading": "Create an auth config from the selected Platform project"
148 - },
149 - {
150 - "sourcePath": "dashboard/auth-configs-navigation/public.md",
151 - "sourceHeading": "Connect Account on an auth config is a Playground test connection"
152 - },
153 - {
154 - "sourcePath": "dashboard/auth-configs-navigation/public.md",
155 - "sourceHeading": "Manage Config changes future authentication behavior"
156 - }
157 - ],
158 - "topics": [
159 - "auth-config",
160 - "authentication",
161 - "getting-started"
162 - ],
163 - "tags": [
164 - "auth-configs",
165 - "dashboard",
166 - "platform"
167 - ],
168 - "aliases": [],
169 - "relatedGuides": [],
170 - "externalResources": [],
171 - "updatedAt": "2026-08-17",
172 - "lastVerifiedAt": "2026-08-17",
173 - "reviewAfter": "2026-11-15",
174 - "freshness": "evergreen",
175 - "state": "published",
176 - "featured": false
177 - },
178 - {
179 - "slug": "dashboard-for-you-navigation",
180 - "title": "Composio For You navigation",
181 - "description": "Current navigation for connecting apps and agents in Composio For You.",
182 - "articlePath": "dashboard-for-you-navigation.md",
183 - "sources": [
184 - {
185 - "sourcePath": "dashboard/for-you-navigation/public.md",
186 - "sourceHeading": "Use Connect Apps for provider accounts and Connect my agent for clients"
187 - },
188 - {
189 - "sourcePath": "dashboard/for-you-navigation/public.md",
190 - "sourceHeading": "For You settings include Sessions & API Key"
191 - }
192 - ],
193 - "topics": [
194 - "account-and-billing",
195 - "authentication",
196 - "getting-started"
197 - ],
198 - "tags": [
199 - "dashboard",
200 - "for-you"
201 - ],
202 - "aliases": [],
203 - "relatedGuides": [],
204 - "externalResources": [],
205 - "updatedAt": "2026-08-17",
206 - "lastVerifiedAt": "2026-08-17",
207 - "reviewAfter": "2026-11-15",
208 - "freshness": "evergreen",
209 - "state": "published",
210 - "featured": false
211 - },
212 - {
213 - "slug": "dashboard-log-storage",
214 - "title": "Dashboard Log Storage",
215 - "description": "Public behavior of the project Log storage setting.",
216 - "articlePath": "dashboard-log-storage.md",
217 - "sources": [
218 - {
219 - "sourcePath": "dashboard/log-storage/public.md",
220 - "sourceHeading": "“Don't store data” removes new payload content, not the audit row"
221 - }
222 - ],
223 - "topics": [
224 - "errors-and-troubleshooting",
225 - "security-and-trust",
226 - "sessions-and-execution"
227 - ],
228 - "tags": [
229 - "dashboard",
230 - "data-retention",
231 - "logs",
232 - "platform"
233 - ],
234 - "aliases": [
235 - "/kb/dashboard-and-projects/don-t-store-data-removes-new-payload-content-not-the-audit-row",
236 - "don-t-store-data-removes-new-payload-content-not-the-audit-row"
237 - ],
238 - "relatedGuides": [],
239 - "externalResources": [],
240 - "updatedAt": "2026-07-16",
241 - "lastVerifiedAt": "2026-08-12",
242 - "reviewAfter": "2026-11-10",
243 - "freshness": "evergreen",
244 - "state": "published",
245 - "featured": false
246 - },
247 - {
248 - "slug": "dashboard-login-restrictions",
249 - "title": "Dashboard MFA Setup",
250 - "description": "Public guidance for completing dashboard MFA setup.",
251 - "articlePath": "dashboard-login-restrictions.md",
252 - "sources": [
253 - {
254 - "sourcePath": "dashboard/login-restrictions/public.md",
255 - "sourceHeading": "Use the manual setup key when QR scanning does not complete"
256 - }
257 - ],
258 - "topics": [
259 - "authentication",
260 - "errors-and-troubleshooting",
261 - "security-and-trust"
262 - ],
263 - "tags": [
264 - "login-restrictions",
265 - "platform"
266 - ],
267 - "aliases": [
268 - "/kb/dashboard-and-projects/mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails",
269 - "mfa-setup-qr-countdown-is-short-use-the-setup-key-if-scanning-fails"
270 - ],
271 - "relatedGuides": [],
272 - "externalResources": [],
273 - "updatedAt": "2026-06-24",
274 - "lastVerifiedAt": "2026-08-17",
275 - "reviewAfter": "2026-11-15",
276 - "freshness": "evergreen",
277 - "state": "published",
278 - "featured": false
279 - },
280 - {
281 - "slug": "dashboard-navigation-overview",
282 - "title": "Composio dashboard navigation",
283 - "description": "Current navigation map for Composio Platform and Composio For You.",
284 - "articlePath": "dashboard-navigation-overview.md",
285 - "sources": [
286 - {
287 - "sourcePath": "dashboard/navigation-overview/public.md",
288 - "sourceHeading": "Choose Platform for developer projects and For You for personal agent connections"
289 - },
290 - {
291 - "sourcePath": "dashboard/navigation-overview/public.md",
292 - "sourceHeading": "Current Platform project navigation"
293 - },
294 - {
295 - "sourcePath": "dashboard/navigation-overview/public.md",
296 - "sourceHeading": "Organization and project settings are separate"
297 - }
298 - ],
299 - "topics": [
300 - "getting-started",
301 - "workflows"
302 - ],
303 - "tags": [
304 - "dashboard",
305 - "for-you",
306 - "navigation",
307 - "platform"
308 - ],
309 - "aliases": [],
310 - "relatedGuides": [],
311 - "externalResources": [],
312 - "updatedAt": "2026-08-17",
313 - "lastVerifiedAt": "2026-08-17",
314 - "reviewAfter": "2026-11-15",
315 - "freshness": "evergreen",
316 - "state": "published",
317 - "featured": false
318 - },
319 - {
320 - "slug": "dashboard-org-members",
321 - "title": "Organization Members and Roles",
322 - "description": "What the Admin, Member (Developer), and Viewer roles can do in Composio For You and Platform, and how to transfer organization control.",
323 - "articlePath": "dashboard-org-members.md",
324 - "sources": [
325 - {
326 - "sourcePath": "dashboard/org-members/public.md",
327 - "sourceHeading": "What each organization role can do"
328 - },
329 - {
330 - "sourcePath": "dashboard/org-members/public.md",
331 - "sourceHeading": "Transfer organization control to another user"
332 - }
333 - ],
334 - "topics": [
335 - "account-and-billing",
336 - "getting-started"
337 - ],
338 - "tags": [
339 - "dashboard",
340 - "for-you",
341 - "members",
342 - "organizations",
343 - "permissions",
344 - "platform",
345 - "roles"
346 - ],
347 - "aliases": [
348 - "/kb/dashboard-and-projects/transfer-organization-control-to-another-user",
349 - "transfer-organization-control-to-another-user"
350 - ],
351 - "relatedGuides": [],
352 - "externalResources": [],
353 - "updatedAt": "2026-10-13",
354 - "lastVerifiedAt": "2026-10-13",
355 - "reviewAfter": "2026-11-15",
356 - "freshness": "evergreen",
357 - "state": "published",
358 - "featured": false
359 - },
360 - {
361 - "slug": "dashboard-project-settings-navigation",
362 - "title": "Platform project settings",
363 - "description": "Current navigation for Platform project configuration and organization settings.",
364 - "articlePath": "dashboard-project-settings-navigation.md",
365 - "sources": [
366 - {
367 - "sourcePath": "dashboard/project-settings-navigation/public.md",
368 - "sourceHeading": "Project settings control one project"
369 - },
370 - {
371 - "sourcePath": "dashboard/project-settings-navigation/public.md",
372 - "sourceHeading": "Organization settings control the organization"
373 - }
374 - ],
375 - "topics": [
376 - "account-and-billing",
377 - "authentication",
378 - "workflows"
379 - ],
380 - "tags": [
381 - "dashboard",
382 - "platform",
383 - "settings"
384 - ],
385 - "aliases": [],
386 - "relatedGuides": [],
387 - "externalResources": [],
388 - "updatedAt": "2026-08-17",
389 - "lastVerifiedAt": "2026-08-17",
390 - "reviewAfter": "2026-11-15",
391 - "freshness": "evergreen",
392 - "state": "published",
393 - "featured": false
394 - },
395 - {
396 - "slug": "dashboard-tool-trigger-logs-navigation",
397 - "title": "Debug Platform tools, triggers, users, and sessions",
398 - "description": "Current dashboard paths for inspecting Platform execution state and support identifiers.",
399 - "articlePath": "dashboard-tool-trigger-logs-navigation.md",
400 - "sources": [
401 - {
402 - "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
403 - "sourceHeading": "Use Logs for execution evidence"
404 - },
405 - {
406 - "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
407 - "sourceHeading": "Use Users and Sessions to explain retrieval and execution context"
408 - },
409 - {
410 - "sourcePath": "dashboard/tool-trigger-logs-navigation/public.md",
411 - "sourceHeading": "Disable a trigger when the goal is to pause it"
412 - }
413 - ],
414 - "topics": [
415 - "errors-and-troubleshooting",
416 - "sessions-and-execution",
417 - "workflows"
418 - ],
419 - "tags": [
420 - "dashboard",
421 - "logs",
422 - "platform",
423 - "triggers"
424 - ],
425 - "aliases": [],
426 - "relatedGuides": [],
427 - "externalResources": [],
428 - "updatedAt": "2026-08-17",
429 - "lastVerifiedAt": "2026-08-17",
430 - "reviewAfter": "2026-11-15",
431 - "freshness": "evergreen",
432 - "state": "published",
433 - "featured": false
434 - },
435 - {
436 - "slug": "faqs",
437 - "title": "Current Support FAQs",
438 - "description": "Public answers for recurring Composio support issues.",
439 - "articlePath": "faqs.md",
440 - "sources": [
441 - {
442 - "sourcePath": "faqs/public.md",
443 - "sourceHeading": "Route toolkit requests and toolkit partnership applications"
444 - },
445 - {
446 - "sourcePath": "faqs/public.md",
447 - "sourceHeading": "Security, privacy, data-retention, and compliance information"
448 - },
449 - {
450 - "sourcePath": "faqs/public.md",
451 - "sourceHeading": "Security reporting"
452 - },
453 - {
454 - "sourcePath": "faqs/public.md",
455 - "sourceHeading": "Google `access_not_configured` requires a Workspace for Education administrator"
456 - }
457 - ],
458 - "topics": [
459 - "authentication",
460 - "errors-and-troubleshooting",
461 - "security-and-trust",
462 - "sessions-and-execution",
463 - "toolkits-and-providers"
464 - ],
465 - "tags": [
466 - "faq",
467 - "faqs",
468 - "for-you",
469 - "platform"
470 - ],
471 - "aliases": [
472 - "/kb/sdk-and-api/misc-faqs",
473 - "misc-faqs",
474 - "request-a-missing-toolkit-tool-or-trigger",
475 - "security-privacy-data-retention-and-compliance-information"
476 - ],
477 - "relatedGuides": [],
478 - "externalResources": [],
479 - "updatedAt": "2026-07-14",
480 - "lastVerifiedAt": "2026-08-17",
481 - "reviewAfter": "2026-11-15",
482 - "freshness": "evergreen",
483 - "state": "published",
484 - "featured": false
485 - },
486 - {
487 - "slug": "mcp-mcp-hermes",
488 - "title": "Hermes MCP",
489 - "description": "Public support knowledge for Hermes MCP.",
490 - "articlePath": "mcp-mcp-hermes.md",
491 - "sources": [
492 - {
493 - "sourcePath": "mcp/mcp-hermes/public.md",
494 - "sourceHeading": "Production MCP API paths and direct transport tests"
495 - },
496 - {
497 - "sourcePath": "mcp/mcp-hermes/public.md",
498 - "sourceHeading": "Auth configs are project-scoped"
499 - }
500 - ],
501 - "topics": [
502 - "auth-config",
503 - "authentication",
504 - "errors-and-troubleshooting",
505 - "getting-started",
506 - "sessions-and-execution"
507 - ],
508 - "tags": [
509 - "for-you",
510 - "mcp",
511 - "mcp-hermes",
512 - "platform"
513 - ],
514 - "aliases": [
515 - "/kb/tool-router-and-mcp/mcp-mcp-hermes",
516 - "auth-configs-are-project-scoped",
517 - "production-mcp-api-paths-and-direct-transport-tests"
518 - ],
519 - "relatedGuides": [],
520 - "externalResources": [],
521 - "updatedAt": "2026-07-16",
522 - "lastVerifiedAt": "2026-11-10",
523 - "reviewAfter": "2027-02-08",
524 - "freshness": "evergreen",
525 - "state": "published",
526 - "featured": false
527 - },
528 - {
529 - "slug": "mcp-tool-router-files",
530 - "title": "Tool Router Files",
531 - "description": "Public guidance for passing Tool Router session files to toolkit actions.",
532 - "articlePath": "mcp-tool-router-files.md",
533 - "sources": [
534 - {
535 - "sourcePath": "mcp/tool-router-files/public.md",
536 - "sourceHeading": "Session paths are not `FileUploadable` storage keys"
537 - }
538 - ],
539 - "topics": [
540 - "errors-and-troubleshooting",
541 - "sessions-and-execution"
542 - ],
543 - "tags": [
544 - "files",
545 - "for-you",
546 - "mcp",
547 - "platform",
548 - "tool-router",
549 - "uploads"
550 - ],
551 - "aliases": [
552 - "/kb/tool-router-and-mcp/use-tool-router-session-files-as-tool-inputs",
553 - "use-tool-router-session-files-as-tool-inputs"
554 - ],
555 - "relatedGuides": [],
556 - "externalResources": [],
557 - "updatedAt": "2026-07-14",
558 - "lastVerifiedAt": "2026-08-12",
559 - "reviewAfter": "2026-11-10",
560 - "freshness": "evergreen",
561 - "state": "published",
562 - "featured": false
563 - },
564 - {
565 - "slug": "mcp-tool-router-sessions",
566 - "title": "Tool Router Sessions",
567 - "description": "Public setup guidance for creating and using Tool Router sessions.",
568 - "articlePath": "mcp-tool-router-sessions.md",
569 - "sources": [
570 - {
571 - "sourcePath": "mcp/tool-router-sessions/public.md",
572 - "sourceHeading": "Create Tool Router sessions through the SDK or API"
573 - },
574 - {
575 - "sourcePath": "mcp/tool-router-sessions/public.md",
576 - "sourceHeading": "Session lifetime and deletion"
577 - },
578 - {
579 - "sourcePath": "mcp/tool-router-sessions/public.md",
580 - "sourceHeading": "Select among multiple accounts with an alias or account ID"
581 - },
582 - {
583 - "sourcePath": "mcp/tool-router-sessions/public.md",
584 - "sourceHeading": "The session user must match the connected-account user"
585 - },
586 - {
587 - "sourcePath": "mcp/tool-router-sessions/public.md",
588 - "sourceHeading": "Connected-account selection is live unless pinned"
589 - },
590 - {
591 - "sourcePath": "mcp/tool-router-sessions/public.md",
592 - "sourceHeading": "Toolkit allowlists are enforced before connection lookup"
593 - },
594 - {
595 - "sourcePath": "mcp/tool-router-sessions/public.md",
596 - "sourceHeading": "A fresh task context is a new session runtime, not model memory"
597 - },
598 - {
599 - "sourcePath": "mcp/tool-router-sessions/public.md",
600 - "sourceHeading": "Auth links create project- and user-scoped connected accounts"
601 - },
602 - {
603 - "sourcePath": "mcp/tool-router-sessions/public.md",
604 - "sourceHeading": "Toolkit filters do not preload every matching tool"
605 - },
606 - {
607 - "sourcePath": "mcp/tool-router-sessions/public.md",
608 - "sourceHeading": "SDK custom tools and Custom MCP toolkits have different runtimes"
609 - },
610 - {
611 - "sourcePath": "mcp/tool-router-sessions/public.md",
612 - "sourceHeading": "Enhanced Control requires client support for MCP elicitation"
613 - },
614 - {
615 - "sourcePath": "mcp/tool-router-sessions/public.md",
616 - "sourceHeading": "Pin the intended auth config when a toolkit has multiple auth schemes"
617 - }
618 - ],
619 - "topics": [
620 - "auth-config",
621 - "authentication",
622 - "errors-and-troubleshooting",
623 - "sessions-and-execution",
624 - "workflows"
625 - ],
626 - "tags": [
627 - "for-you",
628 - "mcp",
629 - "platform",
630 - "sessions",
631 - "tool-router"
632 - ],
633 - "aliases": [
634 - "/kb/tool-router-and-mcp/mcp-tool-router-sessions",
635 - "choose-a-connected-account-for-a-session",
636 - "tool-router-session-lifetime-and-deletion",
637 - "toolkit-is-not-allowed-for-this-session"
638 - ],
639 - "relatedGuides": [],
640 - "externalResources": [],
641 - "updatedAt": "2026-07-16",
642 - "lastVerifiedAt": "2026-08-17",
643 - "reviewAfter": "2026-11-15",
644 - "freshness": "evergreen",
645 - "state": "published",
646 - "featured": false
647 - },
648 - {
649 - "slug": "platform-compliance-data-handling",
650 - "title": "Compliance, Data Retention, and Model Training",
651 - "description": "Public guidance for data retention, model training, compliance, and enterprise security reviews.",
652 - "articlePath": "platform-compliance-data-handling.md",
653 - "sources": [
654 - {
655 - "sourcePath": "platform/compliance-data-handling/public.md",
656 - "sourceHeading": "Canonical public sources"
657 - },
658 - {
659 - "sourcePath": "platform/compliance-data-handling/public.md",
660 - "sourceHeading": "Zero data retention and no-training requirements"
661 - },
662 - {
663 - "sourcePath": "platform/compliance-data-handling/public.md",
664 - "sourceHeading": "Model training"
665 - },
666 - {
667 - "sourcePath": "platform/compliance-data-handling/public.md",
668 - "sourceHeading": "FedRAMP"
669 - },
670 - {
671 - "sourcePath": "platform/compliance-data-handling/public.md",
672 - "sourceHeading": "Third-party providers"
673 - }
674 - ],
675 - "topics": [
676 - "security-and-trust"
677 - ],
678 - "tags": [
679 - "compliance",
680 - "platform",
681 - "privacy",
682 - "retention",
683 - "security"
684 - ],
685 - "aliases": [
686 - "/kb/sdk-and-api/platform-compliance-data-handling",
687 - "canonical-public-sources",
688 - "model-training",
689 - "third-party-providers",
690 - "zero-data-retention-and-no-training-requirements"
691 - ],
692 - "relatedGuides": [],
693 - "externalResources": [],
694 - "updatedAt": "2026-07-24",
695 - "lastVerifiedAt": "2026-08-12",
696 - "reviewAfter": "2026-11-10",
697 - "freshness": "evergreen",
698 - "state": "retired",
699 - "featured": false
700 - },
701 - {
702 - "slug": "platform-connected-accounts",
703 - "title": "Connected Accounts",
704 - "description": "Public support knowledge for Connected Accounts.",
705 - "articlePath": "platform-connected-accounts.md",
706 - "sources": [
707 - {
708 - "sourcePath": "platform/connected-accounts/public.md",
709 - "sourceHeading": "Prefer a new auth link session when a user must reconnect"
710 - },
711 - {
712 - "sourcePath": "platform/connected-accounts/public.md",
713 - "sourceHeading": "Same user ID does not prove same upstream account"
714 - },
715 - {
716 - "sourcePath": "platform/connected-accounts/public.md",
717 - "sourceHeading": "Hosted connect links expire after 10 minutes"
718 - },
719 - {
720 - "sourcePath": "platform/connected-accounts/public.md",
721 - "sourceHeading": "Connection status describes a lifecycle, not credential validity"
722 - },
723 - {
724 - "sourcePath": "platform/connected-accounts/public.md",
725 - "sourceHeading": "OAuth refresh failures have multiple causes"
726 - },
727 - {
728 - "sourcePath": "platform/connected-accounts/public.md",
729 - "sourceHeading": "Provider tokens are redacted from connected-account responses"
730 - },
731 - {
732 - "sourcePath": "platform/connected-accounts/public.md",
733 - "sourceHeading": "Revoke provider credentials before removing a connection when required"
734 - }
735 - ],
736 - "topics": [
737 - "authentication",
738 - "errors-and-troubleshooting"
739 - ],
740 - "tags": [
741 - "connected-accounts",
742 - "platform"
743 - ],
744 - "aliases": [
745 - "/kb/sdk-and-api/platform-connected-accounts",
746 - "connection-status-describes-a-lifecycle-not-credential-validity",
747 - "oauth-refresh-failures-have-multiple-causes",
748 - "public-refresh-endpoint-starts-a-new-auth-flow",
749 - "same-user-id-does-not-prove-same-upstream-account",
750 - "token-based-connections-are-not-always-validated-when-stored"
751 - ],
752 - "relatedGuides": [],
753 - "externalResources": [],
754 - "updatedAt": "2026-07-16",
755 - "lastVerifiedAt": "2026-08-17",
756 - "reviewAfter": "2026-11-15",
757 - "freshness": "evergreen",
758 - "state": "published",
759 - "featured": false
760 - },
761 - {
762 - "slug": "platform-custom-connection-data-fields",
763 - "title": "Custom Connection Data Field Names",
764 - "description": "Public support knowledge for Custom Connection Data Field Names.",
765 - "articlePath": "platform-custom-connection-data-fields.md",
766 - "sources": [
767 - {
768 - "sourcePath": "platform/custom-connection-data-fields/public.md",
769 - "sourceHeading": "Field names are toolkit-specific"
770 - }
771 - ],
772 - "topics": [
773 - "authentication",
774 - "errors-and-troubleshooting",
775 - "sessions-and-execution"
776 - ],
777 - "tags": [
778 - "custom-connection-data-fields",
779 - "platform"
780 - ],
781 - "aliases": [
782 - "/kb/authentication/custom-connection-data-fields-are-toolkit-specific",
783 - "custom-connection-data-fields-are-toolkit-specific"
784 - ],
785 - "relatedGuides": [],
786 - "externalResources": [],
787 - "updatedAt": "2026-06-24",
788 - "lastVerifiedAt": "2026-08-12",
789 - "reviewAfter": "2026-11-10",
790 - "freshness": "evergreen",
791 - "state": "published",
792 - "featured": false
793 - },
794 - {
795 - "slug": "platform-file-storage",
796 - "title": "File Download Storage and Expiry",
797 - "description": "Public guidance for staged files, signed download URLs, retention, and size questions.",
798 - "articlePath": "platform-file-storage.md",
799 - "sources": [
800 - {
801 - "sourcePath": "platform/file-storage/public.md",
802 - "sourceHeading": "Composio file URLs are short-lived staged downloads"
803 - }
804 - ],
805 - "topics": [
806 - "errors-and-troubleshooting",
807 - "sessions-and-execution"
808 - ],
809 - "tags": [
810 - "files",
811 - "platform",
812 - "signed-urls",
813 - "storage"
814 - ],
815 - "aliases": [
816 - "/kb/sdk-and-api/composio-file-urls-are-short-lived-staged-downloads",
817 - "composio-file-urls-are-short-lived-staged-downloads"
818 - ],
819 - "relatedGuides": [],
820 - "externalResources": [],
821 - "updatedAt": "2026-07-16",
822 - "lastVerifiedAt": "2026-08-12",
823 - "reviewAfter": "2026-11-10",
824 - "freshness": "evergreen",
825 - "state": "published",
826 - "featured": false
827 - },
828 - {
829 - "slug": "platform-google-oauth",
830 - "title": "Google OAuth setup and consent",
831 - "description": "Shared OAuth setup and consent guidance for Google toolkits.",
832 - "articlePath": "platform-google-oauth.md",
833 - "sources": [
834 - {
835 - "sourcePath": "platform/google-oauth/public.md",
836 - "sourceHeading": "An unapproved Google OAuth scope can block consent"
837 - },
838 - {
839 - "sourcePath": "platform/google-oauth/public.md",
840 - "sourceHeading": "A customer-owned OAuth app controls the provider consent-screen brand"
841 - }
842 - ],
843 - "topics": [
844 - "auth-config",
845 - "authentication",
846 - "errors-and-troubleshooting",
847 - "toolkits-and-providers"
848 - ],
849 - "tags": [
850 - "for-you",
851 - "google",
852 - "oauth",
853 - "platform"
854 - ],
855 - "aliases": [],
856 - "relatedGuides": [],
857 - "externalResources": [],
858 - "updatedAt": "2026-08-17",
859 - "lastVerifiedAt": "2026-08-17",
860 - "reviewAfter": "2026-11-15",
861 - "freshness": "evergreen",
862 - "state": "published",
863 - "featured": false
864 - },
865 - {
866 - "slug": "platform-health-endpoints",
867 - "title": "Platform Health Endpoints",
868 - "description": "Public reference for Composio on-prem and self-hosted health endpoints.",
869 - "articlePath": "platform-health-endpoints.md",
870 - "sources": [
871 - {
872 - "sourcePath": "platform/health-endpoints/public.md",
873 - "sourceHeading": "Apollo"
874 - },
875 - {
876 - "sourcePath": "platform/health-endpoints/public.md",
877 - "sourceHeading": "Thermos"
878 - }
879 - ],
880 - "topics": [
881 - "errors-and-troubleshooting",
882 - "sessions-and-execution"
883 - ],
884 - "tags": [
885 - "health-endpoints",
886 - "platform"
887 - ],
888 - "aliases": [
889 - "/kb/sdk-and-api/platform-health-endpoints",
890 - "apollo",
891 - "metrics-export",
892 - "thermos"
893 - ],
894 - "relatedGuides": [],
895 - "externalResources": [],
896 - "updatedAt": "2026-06-24",
897 - "lastVerifiedAt": "2026-08-17",
898 - "reviewAfter": "2026-11-15",
899 - "freshness": "evergreen",
900 - "state": "retired",
901 - "featured": false
902 - },
903 - {
904 - "slug": "platform-microsoft-oauth",
905 - "title": "Microsoft OAuth scopes and tenant consent",
906 - "description": "Shared OAuth scope and tenant-consent guidance for Microsoft toolkits.",
907 - "articlePath": "platform-microsoft-oauth.md",
908 - "sources": [
909 - {
910 - "sourcePath": "platform/microsoft-oauth/public.md",
911 - "sourceHeading": "Request `offline_access` when a delegated connection needs refresh tokens"
912 - },
913 - {
914 - "sourcePath": "platform/microsoft-oauth/public.md",
915 - "sourceHeading": "Some Microsoft tenant policies and permissions require administrator consent"
916 - }
917 - ],
918 - "topics": [
919 - "auth-config",
920 - "authentication",
921 - "errors-and-troubleshooting",
922 - "toolkits-and-providers"
923 - ],
924 - "tags": [
925 - "for-you",
926 - "microsoft",
927 - "oauth",
928 - "platform"
929 - ],
930 - "aliases": [],
931 - "relatedGuides": [],
932 - "externalResources": [],
933 - "updatedAt": "2026-08-17",
934 - "lastVerifiedAt": "2026-08-17",
935 - "reviewAfter": "2026-11-15",
936 - "freshness": "evergreen",
937 - "state": "published",
938 - "featured": false
939 - },
940 - {
941 - "slug": "platform-pagination",
942 - "title": "Platform Pagination",
943 - "description": "Public guidance for endpoint-specific list limits and cursor pagination.",
944 - "articlePath": "platform-pagination.md",
945 - "sources": [
946 - {
947 - "sourcePath": "platform/pagination/public.md",
948 - "sourceHeading": "Pagination limits are endpoint-specific"
949 - },
950 - {
951 - "sourcePath": "platform/pagination/public.md",
952 - "sourceHeading": "Auth-config list pages return at most 50 items"
953 - }
954 - ],
955 - "topics": [
956 - "auth-config",
957 - "errors-and-troubleshooting",
958 - "sessions-and-execution"
959 - ],
960 - "tags": [
961 - "api",
962 - "cursors",
963 - "pagination",
964 - "platform"
965 - ],
966 - "aliases": [
967 - "/kb/authentication/auth-config-list-pages-return-at-most-50-items",
968 - "/kb/sdk-and-api/pagination-limits-are-endpoint-specific",
969 - "auth-config-list-pages-return-at-most-50-items",
970 - "pagination-limits-are-endpoint-specific"
971 - ],
972 - "relatedGuides": [],
973 - "externalResources": [],
974 - "updatedAt": "2026-07-16",
975 - "lastVerifiedAt": "2026-08-12",
976 - "reviewAfter": "2026-11-10",
977 - "freshness": "evergreen",
978 - "state": "published",
979 - "featured": false
980 - },
981 - {
982 - "slug": "platform-production-readiness",
983 - "title": "Move a Composio Integration from Prototype to Production",
984 - "description": "Public guidance for production user identity, environment isolation, authentication, sessions, and trigger delivery.",
985 - "articlePath": "platform-production-readiness.md",
986 - "sources": [
987 - {
988 - "sourcePath": "platform/production-readiness/public.md",
989 - "sourceHeading": "Replace example user IDs with stable application user IDs"
990 - },
991 - {
992 - "sourcePath": "platform/production-readiness/public.md",
993 - "sourceHeading": "Isolate environments with separate Composio projects when needed"
994 - },
995 - {
996 - "sourcePath": "platform/production-readiness/public.md",
997 - "sourceHeading": "Use managed auth in production, and your own OAuth app when you need dedicated limits"
998 - },
999 - {
1000 - "sourcePath": "platform/production-readiness/public.md",
1001 - "sourceHeading": "Restrict the production session to the capabilities the agent needs"
1002 - },
1003 - {
1004 - "sourcePath": "platform/production-readiness/public.md",
1005 - "sourceHeading": "Reuse a stored session until the user or configuration changes"
1006 - },
1007 - {
1008 - "sourcePath": "platform/production-readiness/public.md",
1009 - "sourceHeading": "Test production trigger handling through the real webhook path"
1010 - }
1011 - ],
1012 - "topics": [
1013 - "auth-config",
1014 - "authentication",
1015 - "getting-started",
1016 - "security-and-trust",
1017 - "sessions-and-execution",
1018 - "workflows"
1019 - ],
1020 - "tags": [
1021 - "authentication",
1022 - "deployment",
1023 - "platform",
1024 - "production",
1025 - "projects",
1026 - "sessions",
1027 - "users"
1028 - ],
1029 - "aliases": [],
1030 - "relatedGuides": [],
1031 - "externalResources": [],
1032 - "updatedAt": "2026-08-24",
1033 - "lastVerifiedAt": "2026-08-24",
1034 - "reviewAfter": "2026-11-22",
1035 - "freshness": "evergreen",
1036 - "state": "published",
1037 - "featured": false
1038 - },
1039 - {
1040 - "slug": "platform-project-api-key-permissions",
1041 - "title": "Project API Key Permissions",
1042 - "description": "Public guidance for scoped Project API key permissions.",
1043 - "articlePath": "platform-project-api-key-permissions.md",
1044 - "sources": [
1045 - {
1046 - "sourcePath": "platform/project-api-key-permissions/public.md",
1047 - "sourceHeading": "Proxy Execute requires an explicitly allowed Project API key"
1048 - },
1049 - {
1050 - "sourcePath": "platform/project-api-key-permissions/public.md",
1051 - "sourceHeading": "Tool Router session creation requires Sessions write access"
1052 - },
1053 - {
1054 - "sourcePath": "platform/project-api-key-permissions/public.md",
1055 - "sourceHeading": "Tool execution requires Tool execution write access"
1056 - }
1057 - ],
1058 - "topics": [
1059 - "authentication",
1060 - "errors-and-troubleshooting",
1061 - "sessions-and-execution"
1062 - ],
1063 - "tags": [
1064 - "api-keys",
1065 - "permissions",
1066 - "platform",
1067 - "sessions",
1068 - "tool-router"
1069 - ],
1070 - "aliases": [
1071 - "/kb/sdk-and-api/platform-project-api-key-permissions",
1072 - "org-api-created-keys-do-not-currently-enable-proxy-execute",
1073 - "tool-router-session-creation-requires-sessions-write-access"
1074 - ],
1075 - "relatedGuides": [],
1076 - "externalResources": [],
1077 - "updatedAt": "2026-08-28",
1078 - "lastVerifiedAt": "2026-08-28",
1079 - "reviewAfter": "2026-11-26",
1080 - "freshness": "evergreen",
1081 - "state": "published",
1082 - "featured": false
1083 - },
1084 - {
1085 - "slug": "platform-rate-limits",
1086 - "title": "Platform API Rate Limits",
1087 - "description": "Public guidance for organization-level Composio API limits and 429 handling.",
1088 - "articlePath": "platform-rate-limits.md",
1089 - "sources": [
1090 - {
1091 - "sourcePath": "platform/rate-limits/public.md",
1092 - "sourceHeading": "Organization API limits and 429 handling"
1093 - }
1094 - ],
1095 - "topics": [
1096 - "account-and-billing",
1097 - "errors-and-troubleshooting",
1098 - "sessions-and-execution"
1099 - ],
1100 - "tags": [
1101 - "api",
1102 - "billing",
1103 - "platform",
1104 - "rate-limits"
1105 - ],
1106 - "aliases": [],
1107 - "relatedGuides": [],
1108 - "externalResources": [],
1109 - "updatedAt": "2026-07-16",
1110 - "lastVerifiedAt": "2026-08-12",
1111 - "reviewAfter": "2026-11-10",
1112 - "freshness": "evergreen",
1113 - "state": "published",
1114 - "featured": false
1115 - },
1116 - {
1117 - "slug": "platform-routing",
1118 - "title": "Support Routing",
1119 - "description": "Public routing for hiring, compliance, and toolkit feature requests.",
1120 - "articlePath": "platform-routing.md",
1121 - "sources": [
1122 - {
1123 - "sourcePath": "platform/routing/public.md",
1124 - "sourceHeading": "Hiring"
1125 - },
1126 - {
1127 - "sourcePath": "platform/routing/public.md",
1128 - "sourceHeading": "DPA, enterprise data handling, and compliance"
1129 - },
1130 - {
1131 - "sourcePath": "platform/routing/public.md",
1132 - "sourceHeading": "Tool or toolkit feature requests"
1133 - }
1134 - ],
1135 - "topics": [
1136 - "getting-started",
1137 - "security-and-trust",
1138 - "toolkits-and-providers"
1139 - ],
1140 - "tags": [
1141 - "compliance",
1142 - "platform",
1143 - "requests",
1144 - "routing"
1145 - ],
1146 - "aliases": [
1147 - "/kb/sdk-and-api/dpa-enterprise-data-handling-and-compliance",
1148 - "dpa-enterprise-data-handling-and-compliance"
1149 - ],
1150 - "relatedGuides": [],
1151 - "externalResources": [],
1152 - "updatedAt": "2026-07-24",
1153 - "lastVerifiedAt": "2026-08-17",
1154 - "reviewAfter": "2026-11-15",
1155 - "freshness": "evergreen",
1156 - "state": "published",
1157 - "featured": false
1158 - },
1159 - {
1160 - "slug": "platform-self-hosted-helm",
1161 - "title": "Self-hosted Helm",
1162 - "description": "Public support knowledge for Self-hosted Helm.",
1163 - "articlePath": "platform-self-hosted-helm.md",
1164 - "sources": [
1165 - {
1166 - "sourcePath": "platform/self-hosted-helm/public.md",
1167 - "sourceHeading": "Apollo S3 with IRSA / ServiceAccount credentials needs no static S3 secret keys"
1168 - },
1169 - {
1170 - "sourcePath": "platform/self-hosted-helm/public.md",
1171 - "sourceHeading": "Disable social login explicitly for self-hosted deployments"
1172 - }
1173 - ],
1174 - "topics": [
1175 - "authentication",
1176 - "errors-and-troubleshooting",
1177 - "getting-started"
1178 - ],
1179 - "tags": [
1180 - "platform",
1181 - "self-hosted-helm"
1182 - ],
1183 - "aliases": [
1184 - "/kb/sdk-and-api/platform-self-hosted-helm",
1185 - "apollo-s3-with-irsa-serviceaccount-credentials-needs-no-static-s3-secr",
1186 - "disable-social-login-explicitly-for-self-hosted-deployments"
1187 - ],
1188 - "relatedGuides": [],
1189 - "externalResources": [],
1190 - "updatedAt": "2026-06-24",
1191 - "lastVerifiedAt": "2026-08-12",
1192 - "reviewAfter": "2026-11-10",
1193 - "freshness": "evergreen",
1194 - "state": "published",
1195 - "featured": false
1196 - },
1197 - {
1198 - "slug": "platform-session-tool-policies",
1199 - "title": "Create Read-Only and Restricted Composio Sessions",
1200 - "description": "Public guidance for limiting session tool access with tags, exact tool allowlists, OAuth scopes, and sandbox controls.",
1201 - "articlePath": "platform-session-tool-policies.md",
1202 - "sources": [
1203 - {
1204 - "sourcePath": "platform/session-tool-policies/public.md",
1205 - "sourceHeading": "Filter a broad read-only session with behavior tags"
1206 - },
1207 - {
1208 - "sourcePath": "platform/session-tool-policies/public.md",
1209 - "sourceHeading": "Use exact tool allowlists for the narrowest policy"
1210 - },
1211 - {
1212 - "sourcePath": "platform/session-tool-policies/public.md",
1213 - "sourceHeading": "Combine provider scopes with session tool restrictions"
1214 - },
1215 - {
1216 - "sourcePath": "platform/session-tool-policies/public.md",
1217 - "sourceHeading": "Apply toolkit-specific exceptions without widening every toolkit"
1218 - },
1219 - {
1220 - "sourcePath": "platform/session-tool-policies/public.md",
1221 - "sourceHeading": "Disable the session sandbox when the workflow does not need code execution"
1222 - }
1223 - ],
1224 - "topics": [
1225 - "authentication",
1226 - "security-and-trust",
1227 - "sessions-and-execution"
1228 - ],
1229 - "tags": [
1230 - "least-privilege",
1231 - "oauth-scopes",
1232 - "platform",
1233 - "read-only",
1234 - "sessions",
1235 - "tool-policy"
1236 - ],
1237 - "aliases": [],
1238 - "relatedGuides": [],
1239 - "externalResources": [],
1240 - "updatedAt": "2026-08-24",
1241 - "lastVerifiedAt": "2026-08-24",
1242 - "reviewAfter": "2026-11-22",
1243 - "freshness": "evergreen",
1244 - "state": "published",
1245 - "featured": false
1246 - },
1247 - {
1248 - "slug": "platform-tool-router-workbench",
1249 - "title": "Tool Router Workbench Retention",
1250 - "description": "Public support knowledge for Tool Router Workbench Retention.",
1251 - "articlePath": "platform-tool-router-workbench.md",
1252 - "sources": [
1253 - {
1254 - "sourcePath": "platform/tool-router-workbench/public.md",
1255 - "sourceHeading": "A “fresh” client label can still reuse the same sandbox"
1256 - }
1257 - ],
1258 - "topics": [
1259 - "errors-and-troubleshooting",
1260 - "sessions-and-execution"
1261 - ],
1262 - "tags": [
1263 - "platform",
1264 - "tool-router-workbench"
1265 - ],
1266 - "aliases": [
1267 - "/kb/sdk-and-api/a-fresh-client-label-can-still-reuse-the-same-sandbox",
1268 - "a-fresh-client-label-can-still-reuse-the-same-sandbox"
1269 - ],
1270 - "relatedGuides": [],
1271 - "externalResources": [],
1272 - "updatedAt": "2026-07-16",
1273 - "lastVerifiedAt": "2026-08-17",
1274 - "reviewAfter": "2026-11-15",
1275 - "freshness": "evergreen",
1276 - "state": "published",
1277 - "featured": false
1278 - },
1279 - {
1280 - "slug": "platform-triggers",
1281 - "title": "Triggers",
1282 - "description": "Public trigger catalog and webhook delivery guidance.",
1283 - "articlePath": "platform-triggers.md",
1284 - "sources": [
1285 - {
1286 - "sourcePath": "platform/triggers/public.md",
1287 - "sourceHeading": "Find every toolkit that currently supports triggers"
1288 - },
1289 - {
1290 - "sourcePath": "platform/triggers/public.md",
1291 - "sourceHeading": "Trigger webhook delivery is at-least-once"
1292 - }
1293 - ],
1294 - "topics": [
1295 - "errors-and-troubleshooting",
1296 - "sessions-and-execution",
1297 - "workflows"
1298 - ],
1299 - "tags": [
1300 - "catalog",
1301 - "platform",
1302 - "retries",
1303 - "triggers",
1304 - "webhooks"
1305 - ],
1306 - "aliases": [
1307 - "/kb/triggers-and-webhooks/platform-triggers",
1308 - "deduplicate-trigger-webhook-deliveries",
1309 - "find-every-toolkit-that-currently-supports-triggers"
1310 - ],
1311 - "relatedGuides": [],
1312 - "externalResources": [],
1313 - "updatedAt": "2026-07-14",
1314 - "lastVerifiedAt": "2026-08-12",
1315 - "reviewAfter": "2026-11-10",
1316 - "freshness": "evergreen",
1317 - "state": "published",
1318 - "featured": false
1319 - },
1320 - {
1321 - "slug": "sdk-tool-execution-retries",
1322 - "title": "Tool Execution Retries",
1323 - "description": "Public support knowledge for Tool Execution Retries.",
1324 - "articlePath": "sdk-tool-execution-retries.md",
1325 - "sources": [
1326 - {
1327 - "sourcePath": "sdk/tool-execution-retries/public.md",
1328 - "sourceHeading": "Current SDKs do not automatically retry non-idempotent tool executions"
1329 - }
1330 - ],
1331 - "topics": [
1332 - "errors-and-troubleshooting",
1333 - "sessions-and-execution"
1334 - ],
1335 - "tags": [
1336 - "platform",
1337 - "sdk",
1338 - "tool-execution-retries"
1339 - ],
1340 - "aliases": [
1341 - "/kb/sdk-and-api/tool-execution-timeouts-can-retry-non-idempotent-actions",
1342 - "tool-execution-timeouts-can-retry-non-idempotent-actions"
1343 - ],
1344 - "relatedGuides": [],
1345 - "externalResources": [],
1346 - "updatedAt": "2026-06-24",
1347 - "lastVerifiedAt": "2026-08-12",
1348 - "reviewAfter": "2026-11-10",
1349 - "freshness": "evergreen",
1350 - "state": "published",
1351 - "featured": false
1352 - },
1353 - {
1354 - "slug": "sdk-tool-schemas",
1355 - "title": "TypeScript Tool Schema Definitions",
1356 - "description": "Public guidance for dangling JSON Schema references in older TypeScript SDK versions.",
1357 - "articlePath": "sdk-tool-schemas.md",
1358 - "sources": [
1359 - {
1360 - "sourcePath": "sdk/tool-schemas/public.md",
1361 - "sourceHeading": "Upgrade when `$ref` is present but root `$defs` is missing"
1362 - }
1363 - ],
1364 - "topics": [
1365 - "errors-and-troubleshooting",
1366 - "sessions-and-execution"
1367 - ],
1368 - "tags": [
1369 - "json-schema",
1370 - "platform",
1371 - "sdk",
1372 - "typescript"
1373 - ],
1374 - "aliases": [
1375 - "/kb/sdk-and-api/upgrade-when-ref-is-present-but-root-defs-is-missing",
1376 - "upgrade-when-ref-is-present-but-root-defs-is-missing"
1377 - ],
1378 - "relatedGuides": [],
1379 - "externalResources": [],
1380 - "updatedAt": "2026-07-16",
1381 - "lastVerifiedAt": "2026-08-12",
1382 - "reviewAfter": "2026-11-10",
1383 - "freshness": "evergreen",
1384 - "state": "published",
1385 - "featured": false
1386 - },
1387 - {
1388 - "slug": "toolkits-ahrefs",
1389 - "title": "Ahrefs",
1390 - "description": "Public support knowledge for Ahrefs.",
1391 - "articlePath": "toolkits-ahrefs.md",
1392 - "sources": [
1393 - {
1394 - "sourcePath": "toolkits/ahrefs/public.md",
1395 - "sourceHeading": "Ahrefs actions must call api.ahrefs.com, not ahrefs.com"
1396 - }
1397 - ],
1398 - "topics": [
1399 - "errors-and-troubleshooting",
1400 - "sessions-and-execution",
1401 - "toolkits-and-providers"
1402 - ],
1403 - "tags": [
1404 - "ahrefs",
1405 - "for-you",
1406 - "platform"
1407 - ],
1408 - "aliases": [
1409 - "/kb/toolkits/ahrefs-actions-use-the-api-host",
1410 - "ahrefs-actions-use-the-api-host"
1411 - ],
1412 - "relatedGuides": [],
1413 - "externalResources": [],
1414 - "updatedAt": "2026-06-24",
1415 - "lastVerifiedAt": "2026-08-12",
1416 - "reviewAfter": "2026-11-10",
1417 - "freshness": "evergreen",
1418 - "state": "published",
1419 - "featured": false
1420 - },
1421 - {
1422 - "slug": "toolkits-airtable",
1423 - "title": "Airtable",
1424 - "description": "Public support knowledge for Airtable.",
1425 - "articlePath": "toolkits-airtable.md",
1426 - "sources": [
1427 - {
1428 - "sourcePath": "toolkits/airtable/public.md",
1429 - "sourceHeading": "Connect Airtable to Claude using MCP"
1430 - },
1431 - {
1432 - "sourcePath": "toolkits/airtable/public.md",
1433 - "sourceHeading": "Use custom Airtable OAuth credentials for additional scopes"
1434 - },
1435 - {
1436 - "sourcePath": "toolkits/airtable/public.md",
1437 - "sourceHeading": "Connection initiation timeout after 10 minutes is not Airtable-specific"
1438 - },
1439 - {
1440 - "sourcePath": "toolkits/airtable/public.md",
1441 - "sourceHeading": "Missing Airtable tools may be caused by list limits or an older toolkit version"
1442 - },
1443 - {
1444 - "sourcePath": "toolkits/airtable/public.md",
1445 - "sourceHeading": "AIRTABLE_UPDATE_MULTIPLE_RECORDS updates at most 10 records per call"
1446 - },
1447 - {
1448 - "sourcePath": "toolkits/airtable/public.md",
1449 - "sourceHeading": "Use one of the current Airtable metadata triggers"
1450 - }
1451 - ],
1452 - "topics": [
1453 - "auth-config",
1454 - "authentication",
1455 - "errors-and-troubleshooting",
1456 - "sessions-and-execution",
1457 - "toolkits-and-providers"
1458 - ],
1459 - "tags": [
1460 - "airtable",
1461 - "for-you",
1462 - "platform"
1463 - ],
1464 - "aliases": [
1465 - "/kb/toolkits/airtable-troubleshooting",
1466 - "airtable-triggers-and-webhooks-were-not-yet-generally-available",
1467 - "airtable-troubleshooting",
1468 - "batch-airtable-record-updates-in-groups-of-10",
1469 - "connect-airtable-to-claude-using-mcp",
1470 - "connection-initiation-timeout-after-10-minutes-is-not-airtable-specifi",
1471 - "missing-airtable-tools-may-be-caused-by-default-list-limits-or-ts-sdk",
1472 - "use-custom-airtable-oauth-credentials-for-additional-scopes"
1473 - ],
1474 - "relatedGuides": [],
1475 - "externalResources": [],
1476 - "updatedAt": "2026-06-24",
1477 - "lastVerifiedAt": "2026-08-17",
1478 - "reviewAfter": "2026-11-15",
1479 - "freshness": "evergreen",
1480 - "state": "published",
1481 - "featured": false
1482 - },
1483 - {
1484 - "slug": "toolkits-apollo",
1485 - "title": "Apollo",
1486 - "description": "Public support knowledge for Apollo.",
1487 - "articlePath": "toolkits-apollo.md",
1488 - "sources": [
1489 - {
1490 - "sourcePath": "toolkits/apollo/public.md",
1491 - "sourceHeading": "Apollo 403s on search/enrichment endpoints can be key-permission or plan-access gated"
1492 - },
1493 - {
1494 - "sourcePath": "toolkits/apollo/public.md",
1495 - "sourceHeading": "Apollo people enrichment and bulk enrichment can behave differently"
1496 - },
1497 - {
1498 - "sourcePath": "toolkits/apollo/public.md",
1499 - "sourceHeading": "Apollo search results may mirror Apollo's official API behavior"
1500 - }
1501 - ],
1502 - "topics": [
1503 - "authentication",
1504 - "errors-and-troubleshooting",
1505 - "sessions-and-execution",
1506 - "toolkits-and-providers"
1507 - ],
1508 - "tags": [
1509 - "apollo",
1510 - "for-you",
1511 - "platform"
1512 - ],
1513 - "aliases": [
1514 - "/kb/toolkits/apollo-tools-have-had-missing-or-incorrect-request-schema-parameters",
1515 - "/kb/toolkits/apollo-troubleshooting",
1516 - "apollo-people-enrichment-and-bulk-enrichment-can-behave-differently",
1517 - "apollo-search-results-may-mirror-apollo-s-official-api-behavior",
1518 - "apollo-tools-have-had-missing-or-incorrect-request-schema-parameters",
1519 - "apollo-troubleshooting"
1520 - ],
1521 - "relatedGuides": [],
1522 - "externalResources": [],
1523 - "updatedAt": "2026-06-24",
1524 - "lastVerifiedAt": "2026-08-12",
1525 - "reviewAfter": "2026-11-10",
1526 - "freshness": "evergreen",
1527 - "state": "published",
1528 - "featured": false
1529 - },
1530 - {
1531 - "slug": "toolkits-asana",
1532 - "title": "Asana",
1533 - "description": "Public support knowledge for Asana.",
1534 - "articlePath": "toolkits-asana.md",
1535 - "sources": [
1536 - {
1537 - "sourcePath": "toolkits/asana/public.md",
1538 - "sourceHeading": "Use `ASANA_GET_STORIES_FOR_TASK` and pass the task ID as a string"
1539 - },
1540 - {
1541 - "sourcePath": "toolkits/asana/public.md",
1542 - "sourceHeading": "Use the current Asana task triggers"
1543 - }
1544 - ],
1545 - "topics": [
1546 - "authentication",
1547 - "sessions-and-execution",
1548 - "toolkits-and-providers"
1549 - ],
1550 - "tags": [
1551 - "asana",
1552 - "for-you",
1553 - "platform"
1554 - ],
1555 - "aliases": [
1556 - "/kb/toolkits/asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava",
1557 - "/kb/toolkits/asana-troubleshooting",
1558 - "asana-is-listed-among-supported-trigger-toolkits-but-exact-trigger-ava",
1559 - "asana-troubleshooting",
1560 - "deleted-asana-auth-configs-can-block-mcp-config-edits-create-a-new-mcp",
1561 - "older-sdk-connection-initiation-may-require-appname-integrationid-enti",
1562 - "verify-current-production-availability-before-using-asana-triggers"
1563 - ],
1564 - "relatedGuides": [],
1565 - "externalResources": [],
1566 - "updatedAt": "2026-06-24",
1567 - "lastVerifiedAt": "2026-08-12",
1568 - "reviewAfter": "2026-11-10",
1569 - "freshness": "evergreen",
1570 - "state": "published",
1571 - "featured": false
1572 - },
1573 - {
1574 - "slug": "toolkits-attio",
1575 - "title": "Attio",
1576 - "description": "Public support knowledge for Attio.",
1577 - "articlePath": "toolkits-attio.md",
1578 - "sources": [
1579 - {
1580 - "sourcePath": "toolkits/attio/public.md",
1581 - "sourceHeading": "Use $contains for partial text matching in ATTIO_FIND_RECORD filters"
1582 - },
1583 - {
1584 - "sourcePath": "toolkits/attio/public.md",
1585 - "sourceHeading": "Use custom tools when an Attio API object is not built into Composio yet"
1586 - },
1587 - {
1588 - "sourcePath": "toolkits/attio/public.md",
1589 - "sourceHeading": "Top-level $ parameter names were fixed for LLM provider compatibility in the latest schema version"
1590 - },
1591 - {
1592 - "sourcePath": "toolkits/attio/public.md",
1593 - "sourceHeading": "Attio toolkit defaults can stay on the base pinned version unless a version is explicitly selected"
1594 - }
1595 - ],
1596 - "topics": [
1597 - "authentication",
1598 - "errors-and-troubleshooting",
1599 - "sessions-and-execution",
1600 - "toolkits-and-providers"
1601 - ],
1602 - "tags": [
1603 - "attio",
1604 - "for-you",
1605 - "platform"
1606 - ],
1607 - "aliases": [
1608 - "/kb/toolkits/attio-troubleshooting",
1609 - "attio-meeting-and-call-recording-get-by-id-endpoints-were-a-feature-re",
1610 - "attio-oauth-tokens-cannot-be-programmatically-revoked-by-composio",
1611 - "attio-toolkit-defaults-can-stay-on-the-base-pinned-version-unless-a-ve",
1612 - "attio-troubleshooting",
1613 - "auth-config-names-can-carry-a-reference-id-but-custom-auth-config-meta",
1614 - "missing-attio-scopes-on-composio-managed-auth-require-confirming-the-a",
1615 - "use-contains-for-partial-text-matching-in-attio-find-record-filters",
1616 - "use-custom-tools-when-an-attio-api-object-is-not-built-into-composio-y"
1617 - ],
1618 - "relatedGuides": [],
1619 - "externalResources": [],
1620 - "updatedAt": "2026-06-24",
1621 - "lastVerifiedAt": "2026-08-12",
1622 - "reviewAfter": "2026-11-10",
1623 - "freshness": "evergreen",
1624 - "state": "published",
1625 - "featured": false
1626 - },
1627 - {
1628 - "slug": "toolkits-browser-tool",
1629 - "title": "Browser Tool",
1630 - "description": "Public support knowledge for Browser Tool.",
1631 - "articlePath": "toolkits-browser-tool.md",
1632 - "sources": [
1633 - {
1634 - "sourcePath": "toolkits/browser_tool/public.md",
1635 - "sourceHeading": "Browser Tool profiles do not work in Zero Data Retention projects"
1636 - }
1637 - ],
1638 - "topics": [
1639 - "security-and-trust",
1640 - "sessions-and-execution",
1641 - "toolkits-and-providers"
1642 - ],
1643 - "tags": [
1644 - "browser_tool",
1645 - "for-you",
1646 - "platform"
1647 - ],
1648 - "aliases": [
1649 - "/kb/toolkits/browser-tool-profiles-do-not-work-in-zero-data-retention-projects",
1650 - "browser-tool-profiles-do-not-work-in-zero-data-retention-projects"
1651 - ],
1652 - "relatedGuides": [],
1653 - "externalResources": [],
1654 - "updatedAt": "2026-06-24",
1655 - "lastVerifiedAt": "2026-08-12",
1656 - "reviewAfter": "2026-11-10",
1657 - "freshness": "evergreen",
1658 - "state": "published",
1659 - "featured": false
1660 - },
1661 - {
1662 - "slug": "toolkits-calendly",
1663 - "title": "Calendly",
1664 - "description": "Public support knowledge for Calendly.",
1665 - "articlePath": "toolkits-calendly.md",
1666 - "sources": [
1667 - {
1668 - "sourcePath": "toolkits/calendly/public.md",
1669 - "sourceHeading": "Use CALENDLY_POST_INVITEE instead of deprecated CALENDLY_CREATE_EVENT_INVITEE"
1670 - }
1671 - ],
1672 - "topics": [
1673 - "errors-and-troubleshooting",
1674 - "toolkits-and-providers"
1675 - ],
1676 - "tags": [
1677 - "calendly",
1678 - "for-you",
1679 - "platform"
1680 - ],
1681 - "aliases": [
1682 - "/kb/toolkits/use-calendly-post-invitee",
1683 - "use-calendly-post-invitee"
1684 - ],
1685 - "relatedGuides": [],
1686 - "externalResources": [],
1687 - "updatedAt": "2026-06-24",
1688 - "lastVerifiedAt": "2026-08-12",
1689 - "reviewAfter": "2026-11-10",
1690 - "freshness": "evergreen",
1691 - "state": "published",
1692 - "featured": false
1693 - },
1694 - {
1695 - "slug": "toolkits-canva",
1696 - "title": "Canva",
1697 - "description": "Public support knowledge for Canva.",
1698 - "articlePath": "toolkits-canva.md",
1699 - "sources": [
1700 - {
1701 - "sourcePath": "toolkits/canva/public.md",
1702 - "sourceHeading": "Use Canva autofill jobs when content must be populated into a design"
1703 - }
1704 - ],
1705 - "topics": [
1706 - "errors-and-troubleshooting",
1707 - "sessions-and-execution",
1708 - "toolkits-and-providers"
1709 - ],
1710 - "tags": [
1711 - "canva",
1712 - "for-you",
1713 - "platform"
1714 - ],
1715 - "aliases": [
1716 - "/kb/toolkits/use-canva-autofill-jobs-for-design-content",
1717 - "use-canva-autofill-jobs-for-design-content"
1718 - ],
1719 - "relatedGuides": [],
1720 - "externalResources": [],
1721 - "updatedAt": "2026-06-24",
1722 - "lastVerifiedAt": "2026-08-12",
1723 - "reviewAfter": "2026-11-10",
1724 - "freshness": "evergreen",
1725 - "state": "published",
1726 - "featured": false
1727 - },
1728 - {
1729 - "slug": "toolkits-canvas",
1730 - "title": "Canvas",
1731 - "description": "Public support knowledge for Canvas.",
1732 - "articlePath": "toolkits-canvas.md",
1733 - "sources": [
1734 - {
1735 - "sourcePath": "toolkits/canvas/public.md",
1736 - "sourceHeading": "Canvas triggers are available, and course selection can be driven from course IDs"
1737 - },
1738 - {
1739 - "sourcePath": "toolkits/canvas/public.md",
1740 - "sourceHeading": "Canvas triggers fire for users visible to the connected bearer-token user"
1741 - },
1742 - {
1743 - "sourcePath": "toolkits/canvas/public.md",
1744 - "sourceHeading": "Canvas Assignment Graded trigger is expected to work for Teacher accounts, not Student accounts"
1745 - },
1746 - {
1747 - "sourcePath": "toolkits/canvas/public.md",
1748 - "sourceHeading": "Canvas trigger payloads expose Canvas user ID separately as `canvas_user_id`"
1749 - },
1750 - {
1751 - "sourcePath": "toolkits/canvas/public.md",
1752 - "sourceHeading": "Canvas action 401/unauthorized errors can be caused by missing action-level scopes"
1753 - },
1754 - {
1755 - "sourcePath": "toolkits/canvas/public.md",
1756 - "sourceHeading": "Canvas OAuth credentials must match the configured Canvas base URL"
1757 - },
1758 - {
1759 - "sourcePath": "toolkits/canvas/public.md",
1760 - "sourceHeading": "Canvas account-level endpoints require admin permissions"
1761 - },
1762 - {
1763 - "sourcePath": "toolkits/canvas/public.md",
1764 - "sourceHeading": "`CANVAS_CREATE_CALENDAR_EVENT` can use a user ID, and Canvas API field names are preserved"
1765 - },
1766 - {
1767 - "sourcePath": "toolkits/canvas/public.md",
1768 - "sourceHeading": "Canvas list/fetch endpoints follow Canvas pagination behavior and may need `per_page`"
1769 - },
1770 - {
1771 - "sourcePath": "toolkits/canvas/public.md",
1772 - "sourceHeading": "Canvas discussion topics and announcements require `only_announcements` selection"
1773 - },
1774 - {
1775 - "sourcePath": "toolkits/canvas/public.md",
1776 - "sourceHeading": "Canvas 404s on course analytics usually mean the course or endpoint is unavailable"
1777 - },
1778 - {
1779 - "sourcePath": "toolkits/canvas/public.md",
1780 - "sourceHeading": "Canvas quiz matching question answers use unprefixed answer field keys"
1781 - },
1782 - {
1783 - "sourcePath": "toolkits/canvas/public.md",
1784 - "sourceHeading": "Older Canvas toolkit versions cannot be patched in place"
1785 - }
1786 - ],
1787 - "topics": [
1788 - "auth-config",
1789 - "authentication",
1790 - "errors-and-troubleshooting",
1791 - "sessions-and-execution",
1792 - "toolkits-and-providers"
1793 - ],
1794 - "tags": [
1795 - "canvas",
1796 - "for-you",
1797 - "platform"
1798 - ],
1799 - "aliases": [
1800 - "/kb/toolkits/canvas-troubleshooting",
1801 - "canvas-404s-on-course-analytics-usually-mean-the-course-or-endpoint-is",
1802 - "canvas-assignment-graded-trigger-is-expected-to-work-for-teacher-accou",
1803 - "canvas-create-calendar-event-can-use-a-user-id-and-canvas-api-field-na",
1804 - "canvas-discussion-topics-and-announcements-require-only-announcements",
1805 - "canvas-does-not-expose-webhooks-for-every-requested-trigger-use-case",
1806 - "canvas-oauth-credentials-must-match-the-configured-canvas-base-url",
1807 - "canvas-quiz-matching-question-answers-use-unprefixed-answer-field-keys",
1808 - "canvas-response-schemas-are-being-standardized-gradually-not-universal",
1809 - "canvas-trigger-payloads-expose-canvas-user-id-separately-as-canvas-use",
1810 - "canvas-triggers-are-available-and-course-selection-can-be-driven-from",
1811 - "canvas-troubleshooting",
1812 - "older-canvas-toolkit-versions-cannot-be-patched-in-place",
1813 - "paginate-canvas-list-results",
1814 - "resolve-canvas-account-endpoint-access-errors",
1815 - "toolkit-versioning-does-not-version-canvas-trigger-logic",
1816 - "use-shorter-polling-intervals-for-canvas-triggers-when-longer-interval"
1817 - ],
1818 - "relatedGuides": [],
1819 - "externalResources": [],
1820 - "updatedAt": "2026-06-24",
1821 - "lastVerifiedAt": "2026-08-17",
1822 - "reviewAfter": "2026-11-15",
1823 - "freshness": "evergreen",
1824 - "state": "published",
1825 - "featured": false
1826 - },
1827 - {
1828 - "slug": "toolkits-clickup",
1829 - "title": "ClickUp",
1830 - "description": "Public support knowledge for ClickUp.",
1831 - "articlePath": "toolkits-clickup.md",
1832 - "sources": [
1833 - {
1834 - "sourcePath": "toolkits/clickup/public.md",
1835 - "sourceHeading": "ClickUp supports managed OAuth, custom OAuth, and API-key credentials"
1836 - },
1837 - {
1838 - "sourcePath": "toolkits/clickup/public.md",
1839 - "sourceHeading": "ClickUp custom OAuth should use the Composio callback URL registered in the ClickUp app"
1840 - },
1841 - {
1842 - "sourcePath": "toolkits/clickup/public.md",
1843 - "sourceHeading": "ClickUp folders and tasks are supported through `CLICKUP_GET_FOLDERS` and `CLICKUP_GET_TASKS`"
1844 - }
1845 - ],
1846 - "topics": [
1847 - "auth-config",
1848 - "authentication",
1849 - "errors-and-troubleshooting",
1850 - "sessions-and-execution",
1851 - "toolkits-and-providers"
1852 - ],
1853 - "tags": [
1854 - "clickup",
1855 - "for-you",
1856 - "platform"
1857 - ],
1858 - "aliases": [
1859 - "/kb/toolkits/clickup-troubleshooting",
1860 - "clickup-custom-oauth-should-use-the-composio-callback-url-registered-i",
1861 - "clickup-folders-and-tasks-are-supported-through-clickup-get-folders-an",
1862 - "clickup-supports-default-auth-or-customer-owned-credentials-when-creat",
1863 - "clickup-tokens-may-require-manual-provider-side-removal-if-programmati",
1864 - "clickup-troubleshooting",
1865 - "cursor-may-fail-when-too-many-mcp-servers-are-configured-keep-clickup"
1866 - ],
1867 - "relatedGuides": [],
1868 - "externalResources": [],
1869 - "updatedAt": "2026-06-24",
1870 - "lastVerifiedAt": "2026-08-24",
1871 - "reviewAfter": "2026-11-22",
1872 - "freshness": "evergreen",
1873 - "state": "published",
1874 - "featured": false
1875 - },
1876 - {
1877 - "slug": "toolkits-confluence",
1878 - "title": "Confluence",
1879 - "description": "Public support knowledge for Confluence.",
1880 - "articlePath": "toolkits-confluence.md",
1881 - "sources": [
1882 - {
1883 - "sourcePath": "toolkits/confluence/public.md",
1884 - "sourceHeading": "Confluence custom OAuth should keep scopes aligned with Composio defaults and endpoint type"
1885 - },
1886 - {
1887 - "sourcePath": "toolkits/confluence/public.md",
1888 - "sourceHeading": "Add `offline_access` to Confluence auth configs when refresh tokens are needed"
1889 - },
1890 - {
1891 - "sourcePath": "toolkits/confluence/public.md",
1892 - "sourceHeading": "Use connected account ID, not auth config ID, when executing Confluence tools"
1893 - },
1894 - {
1895 - "sourcePath": "toolkits/confluence/public.md",
1896 - "sourceHeading": "Use `CONFLUENCE_GET_PAGE_BY_ID` to retrieve Confluence page content"
1897 - },
1898 - {
1899 - "sourcePath": "toolkits/confluence/public.md",
1900 - "sourceHeading": "`CONFLUENCE_UPDATE_PAGE` should be paired with `CONFLUENCE_GET_PAGE_VERSIONS` for versioned updates"
1901 - },
1902 - {
1903 - "sourcePath": "toolkits/confluence/public.md",
1904 - "sourceHeading": "Download Confluence attachments by first getting attachment IDs"
1905 - },
1906 - {
1907 - "sourcePath": "toolkits/confluence/public.md",
1908 - "sourceHeading": "Confluence tool scopes are exposed in MCP listTools annotations for supported deployments"
1909 - },
1910 - {
1911 - "sourcePath": "toolkits/confluence/public.md",
1912 - "sourceHeading": "For Atlassian/Confluence OAuth, use the same redirect URI in auth config and Atlassian app"
1913 - }
1914 - ],
1915 - "topics": [
1916 - "auth-config",
1917 - "authentication",
1918 - "sessions-and-execution",
1919 - "toolkits-and-providers"
1920 - ],
1921 - "tags": [
1922 - "confluence",
1923 - "for-you",
1924 - "platform"
1925 - ],
1926 - "aliases": [
1927 - "/kb/toolkits/confluence-troubleshooting",
1928 - "confluence-custom-oauth-should-keep-scopes-aligned-with-composio-defau",
1929 - "confluence-managed-oauth-failures-can-come-from-scope-mismatch-between",
1930 - "confluence-needs-offline-access-for-refresh",
1931 - "confluence-troubleshooting",
1932 - "download-confluence-attachments-by-first-getting-attachment-ids",
1933 - "for-atlassian-confluence-oauth-use-the-same-redirect-uri-in-auth-confi",
1934 - "page-created-triggers-can-auto-disable-after-repeated-cloud-id-lookup"
1935 - ],
1936 - "relatedGuides": [],
1937 - "externalResources": [],
1938 - "updatedAt": "2026-07-16",
1939 - "lastVerifiedAt": "2026-08-12",
1940 - "reviewAfter": "2026-11-10",
1941 - "freshness": "evergreen",
1942 - "state": "published",
1943 - "featured": false
1944 - },
1945 - {
1946 - "slug": "toolkits-databricks",
1947 - "title": "Databricks",
1948 - "description": "Public support knowledge for Databricks.",
1949 - "articlePath": "toolkits-databricks.md",
1950 - "sources": [
1951 - {
1952 - "sourcePath": "toolkits/databricks/public.md",
1953 - "sourceHeading": "Databricks OAuth client and secret setup reference"
1954 - },
1955 - {
1956 - "sourcePath": "toolkits/databricks/public.md",
1957 - "sourceHeading": "Enter Databricks API key credentials during connected account linking"
1958 - }
1959 - ],
1960 - "topics": [
1961 - "authentication",
1962 - "sessions-and-execution",
1963 - "toolkits-and-providers"
1964 - ],
1965 - "tags": [
1966 - "databricks",
1967 - "for-you",
1968 - "platform"
1969 - ],
1970 - "aliases": [
1971 - "/kb/toolkits/databricks-troubleshooting",
1972 - "databricks-oauth-client-and-secret-setup-reference",
1973 - "databricks-requires-custom-credentials-when-managed-auth-is-unavailabl",
1974 - "databricks-toolkit-does-not-yet-support-oauth-m2m",
1975 - "databricks-troubleshooting",
1976 - "enter-databricks-api-key-credentials-during-connected-account-linking"
1977 - ],
1978 - "relatedGuides": [],
1979 - "externalResources": [],
1980 - "updatedAt": "2026-06-24",
1981 - "lastVerifiedAt": "2026-08-12",
1982 - "reviewAfter": "2026-11-10",
1983 - "freshness": "evergreen",
1984 - "state": "published",
1985 - "featured": false
1986 - },
1987 - {
1988 - "slug": "toolkits-digital-ocean",
1989 - "title": "DigitalOcean authentication",
1990 - "description": "Current authentication choices for the DigitalOcean toolkit.",
1991 - "articlePath": "toolkits-digital-ocean.md",
1992 - "sources": [
1993 - {
1994 - "sourcePath": "toolkits/digital_ocean/public.md",
1995 - "sourceHeading": "DigitalOcean supports managed OAuth2, custom OAuth2, or a personal access token"
1996 - }
1997 - ],
1998 - "topics": [
1999 - "auth-config",
2000 - "authentication",
2001 - "toolkits-and-providers"
2002 - ],
2003 - "tags": [
2004 - "digital_ocean",
2005 - "for-you",
2006 - "platform"
2007 - ],
2008 - "aliases": [
2009 - "/kb/toolkits/managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva",
2010 - "managed-oauth-fails-before-consent-with-unsupported-parameters-or-inva"
2011 - ],
2012 - "relatedGuides": [],
2013 - "externalResources": [],
2014 - "updatedAt": "2026-08-17",
2015 - "lastVerifiedAt": "2026-08-24",
2016 - "reviewAfter": "2026-11-22",
2017 - "freshness": "evergreen",
2018 - "state": "published",
2019 - "featured": false
2020 - },
2021 - {
2022 - "slug": "toolkits-discord",
2023 - "title": "Discord",
2024 - "description": "Public support knowledge for Discord.",
2025 - "articlePath": "toolkits-discord.md",
2026 - "sources": [
2027 - {
2028 - "sourcePath": "toolkits/discord/public.md",
2029 - "sourceHeading": "Discord OAuth credentials do not have a fixed expiration period"
2030 - }
2031 - ],
2032 - "topics": [
2033 - "auth-config",
2034 - "authentication",
2035 - "errors-and-troubleshooting",
2036 - "toolkits-and-providers"
2037 - ],
2038 - "tags": [
2039 - "discord",
2040 - "for-you",
2041 - "platform"
2042 - ],
2043 - "aliases": [
2044 - "/kb/toolkits/discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio",
2045 - "/kb/toolkits/multiple-accounts-for-the-same-discord-app-were-not-supported-in-that",
2046 - "discordbot-401s-on-managed-oauth-were-a-known-managed-app-configuratio",
2047 - "multiple-accounts-for-the-same-discord-app-were-not-supported-in-that"
2048 - ],
2049 - "relatedGuides": [],
2050 - "externalResources": [],
2051 - "updatedAt": "2026-06-24",
2052 - "lastVerifiedAt": "2026-08-12",
2053 - "reviewAfter": "2026-11-10",
2054 - "freshness": "evergreen",
2055 - "state": "published",
2056 - "featured": false
2057 - },
2058 - {
2059 - "slug": "toolkits-discordbot",
2060 - "title": "Discord Bot",
2061 - "description": "Public support knowledge for Discord Bot.",
2062 - "articlePath": "toolkits-discordbot.md",
2063 - "sources": [
2064 - {
2065 - "sourcePath": "toolkits/discordbot/public.md",
2066 - "sourceHeading": "Discord and DiscordBot use different token types"
2067 - },
2068 - {
2069 - "sourcePath": "toolkits/discordbot/public.md",
2070 - "sourceHeading": "Verify Discord auth config scopes when bot actions do not respond"
2071 - }
2072 - ],
2073 - "topics": [
2074 - "auth-config",
2075 - "authentication",
2076 - "errors-and-troubleshooting",
2077 - "sessions-and-execution",
2078 - "toolkits-and-providers"
2079 - ],
2080 - "tags": [
2081 - "discordbot",
2082 - "for-you",
2083 - "platform"
2084 - ],
2085 - "aliases": [
2086 - "/kb/authentication/discord-bot-troubleshooting",
2087 - "/kb/toolkits/discord-message-triggers-need-bot-token-auth-which-is-not-available-th",
2088 - "/kb/toolkits/multiple-connected-accounts-for-the-same-app-are-not-supported",
2089 - "choose-discordbot-for-bot-token-operations",
2090 - "discord-bot-troubleshooting",
2091 - "discord-message-triggers-need-bot-token-auth-which-is-not-available-th",
2092 - "managed-discordbot-oauth-401s-can-be-worked-around-with-custom-credent",
2093 - "multiple-connected-accounts-for-the-same-app-are-not-supported",
2094 - "verify-discord-auth-config-scopes-when-bot-actions-do-not-respond"
2095 - ],
2096 - "relatedGuides": [],
2097 - "externalResources": [],
2098 - "updatedAt": "2026-06-24",
2099 - "lastVerifiedAt": "2026-08-12",
2100 - "reviewAfter": "2026-11-10",
2101 - "freshness": "evergreen",
2102 - "state": "published",
2103 - "featured": false
2104 - },
2105 - {
2106 - "slug": "toolkits-docusign",
2107 - "title": "DocuSign",
2108 - "description": "Public support knowledge for DocuSign.",
2109 - "articlePath": "toolkits-docusign.md",
2110 - "sources": [
2111 - {
2112 - "sourcePath": "toolkits/docusign/public.md",
2113 - "sourceHeading": "DocuSign auth guide URL"
2114 - }
2115 - ],
2116 - "topics": [
2117 - "authentication",
2118 - "toolkits-and-providers"
2119 - ],
2120 - "tags": [
2121 - "docusign",
2122 - "for-you",
2123 - "platform"
2124 - ],
2125 - "aliases": [
2126 - "/kb/toolkits/docusign-auth-guide-url",
2127 - "docusign-auth-guide-url"
2128 - ],
2129 - "relatedGuides": [],
2130 - "externalResources": [],
2131 - "updatedAt": "2026-06-24",
2132 - "lastVerifiedAt": "2026-08-12",
2133 - "reviewAfter": "2026-11-10",
2134 - "freshness": "evergreen",
2135 - "state": "published",
2136 - "featured": false
2137 - },
2138 - {
2139 - "slug": "toolkits-dropbox",
2140 - "title": "Dropbox",
2141 - "description": "Public support knowledge for Dropbox.",
2142 - "articlePath": "toolkits-dropbox.md",
2143 - "sources": [
2144 - {
2145 - "sourcePath": "toolkits/dropbox/public.md",
2146 - "sourceHeading": "Allow the Composio auth-app redirect URL in the Dropbox app"
2147 - },
2148 - {
2149 - "sourcePath": "toolkits/dropbox/public.md",
2150 - "sourceHeading": "Dropbox connections use Dropbox native OAuth, not Microsoft/Azure/Outlook login"
2151 - },
2152 - {
2153 - "sourcePath": "toolkits/dropbox/public.md",
2154 - "sourceHeading": "For Dropbox upload, `path` is the Dropbox destination and `content` is the local file path"
2155 - },
2156 - {
2157 - "sourcePath": "toolkits/dropbox/public.md",
2158 - "sourceHeading": "Pass file paths to SDK attachment arguments rather than base64/file metadata objects"
2159 - },
2160 - {
2161 - "sourcePath": "toolkits/dropbox/public.md",
2162 - "sourceHeading": "Use DROPBOX_GET_ABOUT_ME to confirm which Dropbox account is connected"
2163 - }
2164 - ],
2165 - "topics": [
2166 - "auth-config",
2167 - "authentication",
2168 - "errors-and-troubleshooting",
2169 - "sessions-and-execution",
2170 - "toolkits-and-providers"
2171 - ],
2172 - "tags": [
2173 - "dropbox",
2174 - "for-you",
2175 - "platform"
2176 - ],
2177 - "aliases": [
2178 - "/kb/toolkits/dropbox-triggers-are-not-currently-available",
2179 - "/kb/toolkits/dropbox-troubleshooting",
2180 - "allow-the-composio-auth-app-redirect-url-in-the-dropbox-app",
2181 - "dropbox-connections-use-dropbox-native-oauth-not-microsoft-azure-outlo",
2182 - "dropbox-triggers-are-not-currently-available",
2183 - "dropbox-troubleshooting",
2184 - "for-dropbox-upload-path-is-the-dropbox-destination-and-content-is-the",
2185 - "initiate-dropbox-oauth-connections-with-entityid-authmode-integrationi",
2186 - "pass-file-paths-to-sdk-attachment-arguments-rather-than-base64-file-me",
2187 - "recreate-older-dropbox-integrations-after-composio-updates-the-default",
2188 - "use-custom-dropbox-oauth-credentials-for-production-instead-of-the-def",
2189 - "use-dropbox-get-about-me-to-confirm-which-dropbox-account-is-connected"
2190 - ],
2191 - "relatedGuides": [],
2192 - "externalResources": [],
2193 - "updatedAt": "2026-06-24",
2194 - "lastVerifiedAt": "2026-08-12",
2195 - "reviewAfter": "2026-11-10",
2196 - "freshness": "evergreen",
2197 - "state": "published",
2198 - "featured": false
2199 - },
2200 - {
2201 - "slug": "toolkits-excel",
2202 - "title": "Excel",
2203 - "description": "Public support knowledge for Excel.",
2204 - "articlePath": "toolkits-excel.md",
2205 - "sources": [
2206 - {
2207 - "sourcePath": "toolkits/excel/public.md",
2208 - "sourceHeading": "EXCEL_UPDATE_RANGE values must be a 2D array"
2209 - },
2210 - {
2211 - "sourcePath": "toolkits/excel/public.md",
2212 - "sourceHeading": "Excel upload tools accept structured workbook data"
2213 - },
2214 - {
2215 - "sourcePath": "toolkits/excel/public.md",
2216 - "sourceHeading": "EXCEL_GET_RANGE failures can come from sheet name or item_id mismatches"
2217 - },
2218 - {
2219 - "sourcePath": "toolkits/excel/public.md",
2220 - "sourceHeading": "Use Excel toolkit actions for workbook operations on SharePoint-backed Excel files"
2221 - },
2222 - {
2223 - "sourcePath": "toolkits/excel/public.md",
2224 - "sourceHeading": "Excel uses the Microsoft auth guide at composio.dev/auth/outlook"
2225 - },
2226 - {
2227 - "sourcePath": "toolkits/excel/public.md",
2228 - "sourceHeading": "Upgrade if Excel schemas contain dollar-sign parameters"
2229 - },
2230 - {
2231 - "sourcePath": "toolkits/excel/public.md",
2232 - "sourceHeading": "Generic column formatting and wrapping are available in current versions"
2233 - }
2234 - ],
2235 - "topics": [
2236 - "authentication",
2237 - "errors-and-troubleshooting",
2238 - "sessions-and-execution",
2239 - "toolkits-and-providers"
2240 - ],
2241 - "tags": [
2242 - "excel",
2243 - "for-you",
2244 - "platform"
2245 - ],
2246 - "aliases": [
2247 - "/kb/toolkits/excel-troubleshooting",
2248 - "excel-get-range-failures-can-come-from-sheet-name-or-item-id-mismatche",
2249 - "excel-support-for-oauth2-client-credentials-may-vary-by-action",
2250 - "excel-troubleshooting",
2251 - "excel-update-range-values-must-be-a-2d-array",
2252 - "excel-upload-tools-accept-structured-workbook-data",
2253 - "excel-uses-the-microsoft-auth-guide-at-composio-dev-auth-outlook",
2254 - "generic-column-formatting-and-wrapping-support-was-added-in-the-may-13",
2255 - "shared-item-listing-cannot-reliably-search-for-a-specific-shared-file",
2256 - "upgrade-older-on-prem-versions-if-excel-schemas-contain-dollar-sign-pa",
2257 - "use-excel-toolkit-actions-for-workbook-operations-on-sharepoint-backed"
2258 - ],
2259 - "relatedGuides": [],
2260 - "externalResources": [],
2261 - "updatedAt": "2026-06-24",
2262 - "lastVerifiedAt": "2026-08-17",
2263 - "reviewAfter": "2026-11-15",
2264 - "freshness": "evergreen",
2265 - "state": "published",
2266 - "featured": false
2267 - },
2268 - {
2269 - "slug": "toolkits-facebook",
2270 - "title": "Facebook",
2271 - "description": "Public support knowledge for Facebook.",
2272 - "articlePath": "toolkits-facebook.md",
2273 - "sources": [
2274 - {
2275 - "sourcePath": "toolkits/facebook/public.md",
2276 - "sourceHeading": "FACEBOOK_DELETE_POST failure can be fixed by using the latest Facebook toolkit version"
2277 - },
2278 - {
2279 - "sourcePath": "toolkits/facebook/public.md",
2280 - "sourceHeading": "Meta OAuth issues can require adding the Composio redirect URI in the Meta app settings"
2281 - },
2282 - {
2283 - "sourcePath": "toolkits/facebook/public.md",
2284 - "sourceHeading": "Facebook or Instagram connections authenticate the account selected in Meta's picker and cannot be repointed server-side"
2285 - },
2286 - {
2287 - "sourcePath": "toolkits/facebook/public.md",
2288 - "sourceHeading": "WhatsApp connections require WABA ID as generic_id, with bearer_token for API-key auth"
2289 - }
2290 - ],
2291 - "topics": [
2292 - "auth-config",
2293 - "authentication",
2294 - "errors-and-troubleshooting",
2295 - "sessions-and-execution",
2296 - "toolkits-and-providers"
2297 - ],
2298 - "tags": [
2299 - "facebook",
2300 - "for-you",
2301 - "platform"
2302 - ],
2303 - "aliases": [
2304 - "/kb/toolkits/facebook-troubleshooting",
2305 - "change-the-connected-facebook-or-instagram-account",
2306 - "connect-meta-ads-with-your-own-credentials",
2307 - "facebook-delete-post-failure-can-be-fixed-by-using-the-latest-facebook",
2308 - "facebook-troubleshooting",
2309 - "instagram-webhook-verification-config-is-not-needed-if-composio-has-no",
2310 - "meta-ads-toolkit-exists-missing-apis-should-be-filed-as-feature-reques",
2311 - "meta-ads-toolkit-was-updated-to-api-version-v24-0",
2312 - "whatsapp-connections-require-waba-id-as-generic-id-with-bearer-token-f",
2313 - "whatsapp-template-sending-needs-an-existing-template-and-required-phon"
2314 - ],
2315 - "relatedGuides": [],
2316 - "externalResources": [],
2317 - "updatedAt": "2026-06-24",
2318 - "lastVerifiedAt": "2026-08-17",
2319 - "reviewAfter": "2026-11-15",
2320 - "freshness": "evergreen",
2321 - "state": "published",
2322 - "featured": false
2323 - },
2324 - {
2325 - "slug": "toolkits-fathom",
2326 - "title": "Fathom",
2327 - "description": "Public support knowledge for Fathom.",
2328 - "articlePath": "toolkits-fathom.md",
2329 - "sources": [
2330 - {
2331 - "sourcePath": "toolkits/fathom/public.md",
2332 - "sourceHeading": "Fathom and granola_mcp are supported meeting transcription toolkits; request unsupported tools separately"
2333 - },
2334 - {
2335 - "sourcePath": "toolkits/fathom/public.md",
2336 - "sourceHeading": "OAuth authorization URLs are provider-specific"
2337 - }
2338 - ],
2339 - "topics": [
2340 - "auth-config",
2341 - "authentication",
2342 - "errors-and-troubleshooting",
2343 - "sessions-and-execution",
2344 - "toolkits-and-providers"
2345 - ],
2346 - "tags": [
2347 - "fathom",
2348 - "for-you",
2349 - "platform"
2350 - ],
2351 - "aliases": [
2352 - "/kb/toolkits/fathom-troubleshooting",
2353 - "fathom-and-granola-mcp-are-supported-meeting-transcription-toolkits-re",
2354 - "fathom-troubleshooting",
2355 - "oauth-authorization-urls-are-provider-specific"
2356 - ],
2357 - "relatedGuides": [],
2358 - "externalResources": [],
2359 - "updatedAt": "2026-06-24",
2360 - "lastVerifiedAt": "2026-08-12",
2361 - "reviewAfter": "2026-11-10",
2362 - "freshness": "evergreen",
2363 - "state": "published",
2364 - "featured": false
2365 - },
2366 - {
2367 - "slug": "toolkits-figma",
2368 - "title": "Figma",
2369 - "description": "Public support knowledge for Figma.",
2370 - "articlePath": "toolkits-figma.md",
2371 - "sources": [
2372 - {
2373 - "sourcePath": "toolkits/figma/public.md",
2374 - "sourceHeading": "Figma token auth is handled by Composio; customers do not need a separate Bearer-token auth scheme"
2375 - },
2376 - {
2377 - "sourcePath": "toolkits/figma/public.md",
2378 - "sourceHeading": "`FIGMA_EXTRACT_DESIGN_TOKENS` variables may be limited by the customer's Figma plan"
2379 - },
2380 - {
2381 - "sourcePath": "toolkits/figma/public.md",
2382 - "sourceHeading": "Figma 429s can come from Figma/provider limits; use custom credentials for production"
2383 - },
2384 - {
2385 - "sourcePath": "toolkits/figma/public.md",
2386 - "sourceHeading": "Remove deprecated `file_read` from Figma auth configs and reconnect"
2387 - },
2388 - {
2389 - "sourcePath": "toolkits/figma/public.md",
2390 - "sourceHeading": "Figma tools are available across auth modes; fetch available tools dynamically"
2391 - },
2392 - {
2393 - "sourcePath": "toolkits/figma/public.md",
2394 - "sourceHeading": "Common Figma design-token tools include extract, Tailwind conversion, and node fetch"
2395 - }
2396 - ],
2397 - "topics": [
2398 - "auth-config",
2399 - "authentication",
2400 - "errors-and-troubleshooting",
2401 - "sessions-and-execution",
2402 - "toolkits-and-providers"
2403 - ],
2404 - "tags": [
2405 - "figma",
2406 - "for-you",
2407 - "platform"
2408 - ],
2409 - "aliases": [
2410 - "/kb/toolkits/figma-troubleshooting",
2411 - "figma-429s-can-come-from-figma-provider-limits-use-custom-credentials",
2412 - "figma-token-auth-is-handled-by-composio-customers-do-not-need-a-separa",
2413 - "figma-tools-are-available-across-auth-modes-fetch-available-tools-dyna",
2414 - "figma-troubleshooting",
2415 - "new-figma-scopes-may-require-custom-oauth-api-key-auth-because-default"
2416 - ],
2417 - "relatedGuides": [],
2418 - "externalResources": [],
2419 - "updatedAt": "2026-06-24",
2420 - "lastVerifiedAt": "2026-08-17",
2421 - "reviewAfter": "2026-11-15",
2422 - "freshness": "evergreen",
2423 - "state": "published",
2424 - "featured": false
2425 - },
2426 - {
2427 - "slug": "toolkits-firecrawl",
2428 - "title": "Firecrawl",
2429 - "description": "Public support knowledge for Firecrawl.",
2430 - "articlePath": "toolkits-firecrawl.md",
2431 - "sources": [
2432 - {
2433 - "sourcePath": "toolkits/firecrawl/public.md",
2434 - "sourceHeading": "Firecrawl uses API-key auth, not OAuth; provide a Firecrawl API key"
2435 - },
2436 - {
2437 - "sourcePath": "toolkits/firecrawl/public.md",
2438 - "sourceHeading": "Create a Firecrawl API-key connected account with generic_api_key"
2439 - },
2440 - {
2441 - "sourcePath": "toolkits/firecrawl/public.md",
2442 - "sourceHeading": "FIRECRAWL_SEARCH may be hidden by default tool list limits"
2443 - },
2444 - {
2445 - "sourcePath": "toolkits/firecrawl/public.md",
2446 - "sourceHeading": "Batch fewer URLs or raise timeout for long Firecrawl scrape jobs"
2447 - },
2448 - {
2449 - "sourcePath": "toolkits/firecrawl/public.md",
2450 - "sourceHeading": "Firecrawl API base URL is https://api.firecrawl.dev/v1"
2451 - },
2452 - {
2453 - "sourcePath": "toolkits/firecrawl/public.md",
2454 - "sourceHeading": "Use FIRECRAWL_SCRAPE or FIRECRAWL_EXTRACT for web-content retrieval"
2455 - },
2456 - {
2457 - "sourcePath": "toolkits/firecrawl/public.md",
2458 - "sourceHeading": "Connect MCP sessions are tied to individual consumer accounts, not a shared workspace"
2459 - }
2460 - ],
2461 - "topics": [
2462 - "authentication",
2463 - "errors-and-troubleshooting",
2464 - "sessions-and-execution",
2465 - "toolkits-and-providers"
2466 - ],
2467 - "tags": [
2468 - "firecrawl",
2469 - "for-you",
2470 - "platform"
2471 - ],
2472 - "aliases": [
2473 - "/kb/toolkits/firecrawl-troubleshooting",
2474 - "batch-fewer-urls-or-raise-timeout-for-long-firecrawl-scrape-jobs",
2475 - "connect-mcp-sessions-are-tied-to-individual-consumer-accounts-not-a-sh",
2476 - "create-a-firecrawl-api-key-connected-account-with-generic-api-key",
2477 - "firecrawl-api-base-url-is-https-api-firecrawl-dev-v1",
2478 - "firecrawl-search-may-be-hidden-by-default-tool-list-limits",
2479 - "firecrawl-troubleshooting",
2480 - "firecrawl-uses-api-key-auth-not-oauth-provide-a-firecrawl-api-key",
2481 - "use-firecrawl-scrape-or-firecrawl-extract-for-web-content-retrieval"
2482 - ],
2483 - "relatedGuides": [],
2484 - "externalResources": [],
2485 - "updatedAt": "2026-06-24",
2486 - "lastVerifiedAt": "2026-08-12",
2487 - "reviewAfter": "2026-11-10",
2488 - "freshness": "evergreen",
2489 - "state": "published",
2490 - "featured": false
2491 - },
2492 - {
2493 - "slug": "toolkits-gemini",
2494 - "title": "Gemini",
2495 - "description": "Public support knowledge for Gemini.",
2496 - "articlePath": "toolkits-gemini.md",
2497 - "sources": [
2498 - {
2499 - "sourcePath": "toolkits/gemini/public.md",
2500 - "sourceHeading": "Gemini no-auth/toolkit usage is counted as regular Composio tool calls"
2501 - },
2502 - {
2503 - "sourcePath": "toolkits/gemini/public.md",
2504 - "sourceHeading": "Use newer Gemini models such as `gemini-2.5-flash` instead of old `gemini-1.5-flash` defaults"
2505 - },
2506 - {
2507 - "sourcePath": "toolkits/gemini/public.md",
2508 - "sourceHeading": "Gemini video generation should use supported Veo model names"
2509 - },
2510 - {
2511 - "sourcePath": "toolkits/gemini/public.md",
2512 - "sourceHeading": "Use `GEMINI_WAIT_FOR_VIDEO` before using generated video output"
2513 - },
2514 - {
2515 - "sourcePath": "toolkits/gemini/public.md",
2516 - "sourceHeading": "Disable automatic file handling when Gemini generated files should remain as URLs/content"
2517 - },
2518 - {
2519 - "sourcePath": "toolkits/gemini/public.md",
2520 - "sourceHeading": "Gemini can use Composio Tool Router through any MCP client"
2521 - },
2522 - {
2523 - "sourcePath": "toolkits/gemini/public.md",
2524 - "sourceHeading": "Gemini CLI MCP issues may be client-side; Claude can be a more stable fallback"
2525 - },
2526 - {
2527 - "sourcePath": "toolkits/gemini/public.md",
2528 - "sourceHeading": "Gemini schema errors can come from Google's OpenAPI-vs-JSON-Schema limitations"
2529 - },
2530 - {
2531 - "sourcePath": "toolkits/gemini/public.md",
2532 - "sourceHeading": "Composio supports Google Gemini/Vertex AI providers, with Python support historically ahead of JS"
2533 - },
2534 - {
2535 - "sourcePath": "toolkits/gemini/public.md",
2536 - "sourceHeading": "LangChain MCP tools are not OpenAI-only and can work with Gemini-capable tool calling"
2537 - }
2538 - ],
2539 - "topics": [
2540 - "authentication",
2541 - "errors-and-troubleshooting",
2542 - "sessions-and-execution",
2543 - "toolkits-and-providers"
2544 - ],
2545 - "tags": [
2546 - "for-you",
2547 - "gemini",
2548 - "platform"
2549 - ],
2550 - "aliases": [
2551 - "/kb/toolkits/gemini-troubleshooting",
2552 - "composio-supports-google-gemini-vertex-ai-providers-with-python-suppor",
2553 - "disable-automatic-file-handling-when-gemini-generated-files-should-rem",
2554 - "gemini-can-use-composio-tool-router-through-any-mcp-client",
2555 - "gemini-cli-mcp-issues-may-be-client-side-claude-can-be-a-more-stable-f",
2556 - "gemini-schema-errors-can-come-from-google-s-openapi-vs-json-schema-lim",
2557 - "gemini-toolkit-quota-is-shared",
2558 - "gemini-troubleshooting",
2559 - "gemini-video-generation-should-use-supported-veo-model-names",
2560 - "gemini-wait-for-video-can-fail-with-missing-presigned-url-after-succes",
2561 - "langchain-mcp-tools-are-not-openai-only-and-can-work-with-gemini-capab",
2562 - "use-gemini-get-videos-operation-or-gemini-wait-for-video-before-using",
2563 - "use-newer-gemini-models-such-as-gemini-2-5-flash-instead-of-old-gemini"
2564 - ],
2565 - "relatedGuides": [],
2566 - "externalResources": [],
2567 - "updatedAt": "2026-06-24",
2568 - "lastVerifiedAt": "2026-08-17",
2569 - "reviewAfter": "2026-11-15",
2570 - "freshness": "evergreen",
2571 - "state": "published",
2572 - "featured": false
2573 - },
2574 - {
2575 - "slug": "toolkits-github",
2576 - "title": "GitHub",
2577 - "description": "Public support knowledge for GitHub.",
2578 - "articlePath": "toolkits-github.md",
2579 - "sources": [
2580 - {
2581 - "sourcePath": "toolkits/github/public.md",
2582 - "sourceHeading": "GitHub V2 triggers do not require creating a webhook endpoint first"
2583 - },
2584 - {
2585 - "sourcePath": "toolkits/github/public.md",
2586 - "sourceHeading": "List GitHub organizations and repositories for the authenticated user"
2587 - },
2588 - {
2589 - "sourcePath": "toolkits/github/public.md",
2590 - "sourceHeading": "GitHub connected-account tokens are redacted from API responses"
2591 - },
2592 - {
2593 - "sourcePath": "toolkits/github/public.md",
2594 - "sourceHeading": "GitHub organization access can require approval from an organization owner"
2595 - },
2596 - {
2597 - "sourcePath": "toolkits/github/public.md",
2598 - "sourceHeading": "Session-level tool allowlists are enforced server-side at execution time"
2599 - },
2600 - {
2601 - "sourcePath": "toolkits/github/public.md",
2602 - "sourceHeading": "Use custom OAuth credentials for branded GitHub consent and redirect flows"
2603 - }
2604 - ],
2605 - "topics": [
2606 - "auth-config",
2607 - "authentication",
2608 - "errors-and-troubleshooting",
2609 - "sessions-and-execution",
2610 - "toolkits-and-providers"
2611 - ],
2612 - "tags": [
2613 - "for-you",
2614 - "github",
2615 - "platform"
2616 - ],
2617 - "aliases": [
2618 - "/kb/toolkits/github-troubleshooting",
2619 - "access-token-freshness-when-retrieving-tokens-for-direct-github-operat",
2620 - "connect-a-github-app",
2621 - "github-troubleshooting",
2622 - "github-v2-triggers-do-not-require-creating-a-webhook-endpoint-first",
2623 - "list-github-organizations-and-repositories-for-the-authenticated-user",
2624 - "session-level-tool-allowlists-are-enforced-server-side-at-execution-ti",
2625 - "use-custom-oauth-credentials-for-branded-github-consent-and-redirect-f",
2626 - "why-github-connected-account-tokens-may-show-as-redacted"
2627 - ],
2628 - "relatedGuides": [],
2629 - "externalResources": [],
2630 - "updatedAt": "2026-06-24",
2631 - "lastVerifiedAt": "2026-08-17",
2632 - "reviewAfter": "2026-11-15",
2633 - "freshness": "evergreen",
2634 - "state": "published",
2635 - "featured": false
2636 - },
2637 - {
2638 - "slug": "toolkits-gmail",
2639 - "title": "Gmail",
2640 - "description": "Public support knowledge for Gmail.",
2641 - "articlePath": "toolkits-gmail.md",
2642 - "sources": [
2643 - {
2644 - "sourcePath": "toolkits/gmail/public.md",
2645 - "sourceHeading": "Use `latest` or v3.1 for newer Gmail settings tools"
2646 - },
2647 - {
2648 - "sourcePath": "toolkits/gmail/public.md",
2649 - "sourceHeading": "Create Gmail custom OAuth auth config, then initiate a connection with callback URL"
2650 - },
2651 - {
2652 - "sourcePath": "toolkits/gmail/public.md",
2653 - "sourceHeading": "Creating Gmail filters requires `gmail.settings.basic`"
2654 - },
2655 - {
2656 - "sourcePath": "toolkits/gmail/public.md",
2657 - "sourceHeading": "`gmail.send` is granular but sensitive; `mail.google.com` gives full access"
2658 - },
2659 - {
2660 - "sourcePath": "toolkits/gmail/public.md",
2661 - "sourceHeading": "Configure Gmail scopes on managed auth config as a comma-joined scopes string"
2662 - },
2663 - {
2664 - "sourcePath": "toolkits/gmail/public.md",
2665 - "sourceHeading": "Avoid `gmail.metadata` when fetching full Gmail email content"
2666 - },
2667 - {
2668 - "sourcePath": "toolkits/gmail/public.md",
2669 - "sourceHeading": "Use `me` for Gmail `user_id` in tool calls"
2670 - },
2671 - {
2672 - "sourcePath": "toolkits/gmail/public.md",
2673 - "sourceHeading": "`GMAIL_SEND_EMAIL` accepts at least one of `to`, `cc`, or `bcc`"
2674 - },
2675 - {
2676 - "sourcePath": "toolkits/gmail/public.md",
2677 - "sourceHeading": "For Gmail attachments over MCP, upload files before tool execution"
2678 - },
2679 - {
2680 - "sourcePath": "toolkits/gmail/public.md",
2681 - "sourceHeading": "Gmail attachment sends can outlast a client timeout; verify before retrying"
2682 - },
2683 - {
2684 - "sourcePath": "toolkits/gmail/public.md",
2685 - "sourceHeading": "Reduce Gmail fetch payload size with `include_payload=false`, `verbose=false`, `only_ids`, query, and limits"
2686 - },
2687 - {
2688 - "sourcePath": "toolkits/gmail/public.md",
2689 - "sourceHeading": "Use `from_email` to select Gmail send-as alias"
2690 - },
2691 - {
2692 - "sourcePath": "toolkits/gmail/public.md",
2693 - "sourceHeading": "Use Gmail label IDs, not label names, for label operations"
2694 - },
2695 - {
2696 - "sourcePath": "toolkits/gmail/public.md",
2697 - "sourceHeading": "Patch Gmail label colors with `background_color` and accepted color values"
2698 - },
2699 - {
2700 - "sourcePath": "toolkits/gmail/public.md",
2701 - "sourceHeading": "Filter Gmail new-message trigger by label/query instead of label IDs"
2702 - },
2703 - {
2704 - "sourcePath": "toolkits/gmail/public.md",
2705 - "sourceHeading": "Use `googlesuper` for one Google auth across Gmail, Calendar, Drive-style use cases"
2706 - }
2707 - ],
2708 - "topics": [
2709 - "auth-config",
2710 - "authentication",
2711 - "errors-and-troubleshooting",
2712 - "sessions-and-execution",
2713 - "toolkits-and-providers"
2714 - ],
2715 - "tags": [
2716 - "for-you",
2717 - "gmail",
2718 - "platform"
2719 - ],
2720 - "aliases": [
2721 - "/kb/toolkits/gmail-troubleshooting",
2722 - "configure-gmail-scopes-on-managed-auth-config-as-a-comma-joined-scopes",
2723 - "create-gmail-filters-scope",
2724 - "filter-gmail-new-message-trigger-by-label-query-instead-of-label-ids",
2725 - "for-gmail-attachments-over-mcp-upload-files-before-tool-execution",
2726 - "gmail-attachments-can-make-send-email-slow-enough-to-hit-sdk-request-t",
2727 - "gmail-send-email-accepts-at-least-one-of-to-cc-or-bcc",
2728 - "gmail-send-is-granular-but-sensitive-mail-google-com-gives-full-access",
2729 - "gmail-troubleshooting",
2730 - "patch-gmail-label-colors-with-background-color-and-accepted-color-valu",
2731 - "reduce-gmail-fetch-payload-size",
2732 - "send-gmail-from-a-send-as-alias",
2733 - "use-gmail-label-ids-not-label-names-for-label-operations",
2734 - "use-googlesuper-for-one-google-auth-across-gmail-calendar-drive-style",
2735 - "use-latest-or-v3-1-for-newer-gmail-settings-tools",
2736 - "verbose-gmail-thread-results-cannot-select-custom-fields-and-may-not-b"
2737 - ],
2738 - "relatedGuides": [],
2739 - "externalResources": [],
2740 - "updatedAt": "2026-07-14",
2741 - "lastVerifiedAt": "2026-08-17",
2742 - "reviewAfter": "2026-11-15",
2743 - "freshness": "evergreen",
2744 - "state": "published",
2745 - "featured": false
2746 - },
2747 - {
2748 - "slug": "toolkits-gong",
2749 - "title": "Gong",
2750 - "description": "Public support knowledge for Gong.",
2751 - "articlePath": "toolkits-gong.md",
2752 - "sources": [
2753 - {
2754 - "sourcePath": "toolkits/gong/public.md",
2755 - "sourceHeading": "Gong base URL differs by customer and should be provided at connection time"
2756 - },
2757 - {
2758 - "sourcePath": "toolkits/gong/public.md",
2759 - "sourceHeading": "Gong connection initiation can use Basic auth fields: access key, access key secret, and Gong URL"
2760 - },
2761 - {
2762 - "sourcePath": "toolkits/gong/public.md",
2763 - "sourceHeading": "Gong MCP tool scopes can be read from tool annotations in the tools API"
2764 - }
2765 - ],
2766 - "topics": [
2767 - "auth-config",
2768 - "authentication",
2769 - "sessions-and-execution",
2770 - "toolkits-and-providers"
2771 - ],
2772 - "tags": [
2773 - "for-you",
2774 - "gong",
2775 - "platform"
2776 - ],
2777 - "aliases": [
2778 - "/kb/toolkits/gong-triggers-were-planned-requested-but-may-not-be-available-for-ever",
2779 - "/kb/toolkits/gong-troubleshooting",
2780 - "gong-base-url-differs-by-customer-and-should-be-provided-at-connection",
2781 - "gong-connection-initiation-can-use-basic-auth-fields-access-key-access",
2782 - "gong-mcp-tool-scopes-can-be-read-from-tool-annotations-in-the-tools-ap",
2783 - "gong-oauth2-support-may-need-to-be-treated-as-a-feature-request-if-not",
2784 - "gong-triggers-were-planned-requested-but-may-not-be-available-for-ever",
2785 - "gong-troubleshooting"
2786 - ],
2787 - "relatedGuides": [],
2788 - "externalResources": [],
2789 - "updatedAt": "2026-06-24",
2790 - "lastVerifiedAt": "2026-08-12",
2791 - "reviewAfter": "2026-11-10",
2792 - "freshness": "evergreen",
2793 - "state": "published",
2794 - "featured": false
2795 - },
2796 - {
2797 - "slug": "toolkits-google-analytics",
2798 - "title": "Google Analytics",
2799 - "description": "Public support knowledge for Google Analytics.",
2800 - "articlePath": "toolkits-google-analytics.md",
2801 - "sources": [
2802 - {
2803 - "sourcePath": "toolkits/google_analytics/public.md",
2804 - "sourceHeading": "Use latest toolkit version when Google Analytics tools return ToolNotFound or only a few tools"
2805 - },
2806 - {
2807 - "sourcePath": "toolkits/google_analytics/public.md",
2808 - "sourceHeading": "Add Google Analytics to an MCP config as a selected tool/toolkit"
2809 - },
2810 - {
2811 - "sourcePath": "toolkits/google_analytics/public.md",
2812 - "sourceHeading": "Empty Google Analytics reports may be provider data availability rather than Composio failure"
2813 - }
2814 - ],
2815 - "topics": [
2816 - "authentication",
2817 - "errors-and-troubleshooting",
2818 - "sessions-and-execution",
2819 - "toolkits-and-providers"
2820 - ],
2821 - "tags": [
2822 - "for-you",
2823 - "google_analytics",
2824 - "platform"
2825 - ],
2826 - "aliases": [
2827 - "/kb/toolkits/google-analytics-troubleshooting",
2828 - "add-google-analytics-to-an-mcp-config-as-a-selected-tool-toolkit",
2829 - "empty-google-analytics-reports-may-be-provider-data-availability-rathe",
2830 - "google-analytics-troubleshooting",
2831 - "old-google-analytics-mcp-could-show-0-actions-because-it-was-auth-only",
2832 - "use-latest-toolkit-version-when-google-analytics-tools-return-toolnotf"
2833 - ],
2834 - "relatedGuides": [],
2835 - "externalResources": [],
2836 - "updatedAt": "2026-06-24",
2837 - "lastVerifiedAt": "2026-08-17",
2838 - "reviewAfter": "2026-11-15",
2839 - "freshness": "evergreen",
2840 - "state": "published",
2841 - "featured": false
2842 - },
2843 - {
2844 - "slug": "toolkits-google-calendar",
2845 - "title": "Google Calendar",
2846 - "description": "Public support knowledge for Google Calendar.",
2847 - "articlePath": "toolkits-google-calendar.md",
2848 - "sources": [
2849 - {
2850 - "sourcePath": "toolkits/google_calendar/public.md",
2851 - "sourceHeading": "Create a Google Calendar integration to access tools and triggers"
2852 - },
2853 - {
2854 - "sourcePath": "toolkits/google_calendar/public.md",
2855 - "sourceHeading": "Updating RSVP status has an attendee-list API limitation"
2856 - },
2857 - {
2858 - "sourcePath": "toolkits/google_calendar/public.md",
2859 - "sourceHeading": "Canceled/deleted event trigger sends payloads for canceled or deleted events"
2860 - },
2861 - {
2862 - "sourcePath": "toolkits/google_calendar/public.md",
2863 - "sourceHeading": "Multiple triggers for the same slug/user can target different calendar IDs"
2864 - },
2865 - {
2866 - "sourcePath": "toolkits/google_calendar/public.md",
2867 - "sourceHeading": "`calendar.events` scope is required for event list/fetch flows"
2868 - },
2869 - {
2870 - "sourcePath": "toolkits/google_calendar/public.md",
2871 - "sourceHeading": "Google Calendar triggers now return full event data instead of only an ID"
2872 - },
2873 - {
2874 - "sourcePath": "toolkits/google_calendar/public.md",
2875 - "sourceHeading": "Google Calendar trigger moved toward polling for more verbose payloads"
2876 - },
2877 - {
2878 - "sourcePath": "toolkits/google_calendar/public.md",
2879 - "sourceHeading": "Use trigger-types endpoint to retrieve Google Calendar trigger info programmatically"
2880 - },
2881 - {
2882 - "sourcePath": "toolkits/google_calendar/public.md",
2883 - "sourceHeading": "Use Find Free Slots when you need processed availability; free/busy does not do timezone processing"
2884 - },
2885 - {
2886 - "sourcePath": "toolkits/google_calendar/public.md",
2887 - "sourceHeading": "Use `primary` as calendar ID; `me` is not valid for calendar ID"
2888 - },
2889 - {
2890 - "sourcePath": "toolkits/google_calendar/public.md",
2891 - "sourceHeading": "Use latest Google Calendar toolkit version when filters are ignored"
2892 - },
2893 - {
2894 - "sourcePath": "toolkits/google_calendar/public.md",
2895 - "sourceHeading": "Google Calendar meeting link is returned in `hangout_link`"
2896 - }
2897 - ],
2898 - "topics": [
2899 - "auth-config",
2900 - "authentication",
2901 - "errors-and-troubleshooting",
2902 - "sessions-and-execution",
2903 - "toolkits-and-providers"
2904 - ],
2905 - "tags": [
2906 - "for-you",
2907 - "google_calendar",
2908 - "platform"
2909 - ],
2910 - "aliases": [
2911 - "/kb/authentication/google-calendar-troubleshooting",
2912 - "calendar-events-scope-is-required-for-event-list-fetch-flows",
2913 - "composio-does-not-support-org-wide-google-workspace-authentication-for",
2914 - "create-a-google-calendar-integration-to-access-tools-and-triggers",
2915 - "google-calendar-trigger-moved-toward-polling-for-more-verbose-payloads",
2916 - "google-calendar-troubleshooting",
2917 - "updating-rsvp-status-has-an-attendee-list-api-limitation",
2918 - "use-find-free-slots-when-you-need-processed-availability-free-busy-doe",
2919 - "use-latest-google-calendar-toolkit-version-when-filters-are-ignored",
2920 - "use-primary-for-google-calendar-id",
2921 - "use-trigger-types-endpoint-to-retrieve-google-calendar-trigger-info-pr"
2922 - ],
2923 - "relatedGuides": [],
2924 - "externalResources": [],
2925 - "updatedAt": "2026-06-24",
2926 - "lastVerifiedAt": "2026-08-12",
2927 - "reviewAfter": "2026-11-10",
2928 - "freshness": "evergreen",
2929 - "state": "published",
2930 - "featured": false
2931 - },
2932 - {
2933 - "slug": "toolkits-google-classroom",
2934 - "title": "Google Classroom",
2935 - "description": "Public OAuth and connection troubleshooting for Google Classroom.",
2936 - "articlePath": "toolkits-google-classroom.md",
2937 - "sources": [
2938 - {
2939 - "sourcePath": "toolkits/google_classroom/public.md",
2940 - "sourceHeading": "Set up custom Google OAuth credentials"
2941 - },
2942 - {
2943 - "sourcePath": "toolkits/google_classroom/public.md",
2944 - "sourceHeading": "Resolve an \"App is blocked\" connection error"
2945 - },
2946 - {
2947 - "sourcePath": "toolkits/google_classroom/public.md",
2948 - "sourceHeading": "Enable the Google Classroom API for custom OAuth"
2949 - },
2950 - {
2951 - "sourcePath": "toolkits/google_classroom/public.md",
2952 - "sourceHeading": "Resolve `Error 400: invalid_scope`"
2953 - },
2954 - {
2955 - "sourcePath": "toolkits/google_classroom/public.md",
2956 - "sourceHeading": "Choose managed or customer-owned Google OAuth"
2957 - },
2958 - {
2959 - "sourcePath": "toolkits/google_classroom/public.md",
2960 - "sourceHeading": "Resolve 401 errors on tool calls"
2961 - }
2962 - ],
2963 - "topics": [
2964 - "auth-config",
2965 - "authentication",
2966 - "errors-and-troubleshooting",
2967 - "sessions-and-execution",
2968 - "toolkits-and-providers"
2969 - ],
2970 - "tags": [
2971 - "for-you",
2972 - "google_classroom",
2973 - "oauth",
2974 - "platform",
2975 - "scopes"
2976 - ],
2977 - "aliases": [
2978 - "/kb/toolkits/google-classroom-troubleshooting",
2979 - "enable-the-google-classroom-api-for-custom-oauth",
2980 - "google-blocks-sensitive-gmail-scopes",
2981 - "google-classroom-troubleshooting",
2982 - "resolve-401-errors-on-tool-calls",
2983 - "resolve-an-app-is-blocked-connection-error",
2984 - "resolve-an-app-is-blocked-connection-error-2",
2985 - "resolve-error-400-invalid-scope",
2986 - "set-up-custom-google-oauth-credentials",
2987 - "this-app-is-blocked-means-the-requested-google-scope-is-not-verified-o"
2988 - ],
2989 - "relatedGuides": [],
2990 - "externalResources": [],
2991 - "updatedAt": "2026-07-24",
2992 - "lastVerifiedAt": "2026-08-24",
2993 - "reviewAfter": "2026-11-22",
2994 - "freshness": "evergreen",
2995 - "state": "published",
2996 - "featured": false
2997 - },
2998 - {
2999 - "slug": "toolkits-google-maps",
3000 - "title": "Google Maps",
3001 - "description": "Public support knowledge for Google Maps.",
3002 - "articlePath": "toolkits-google-maps.md",
3003 - "sources": [
3004 - {
3005 - "sourcePath": "toolkits/google_maps/public.md",
3006 - "sourceHeading": "Maps Embed API requires API-key authentication"
3007 - },
3008 - {
3009 - "sourcePath": "toolkits/google_maps/public.md",
3010 - "sourceHeading": "Google Maps OAuth can be blocked by sensitive cloud-platform scope"
3011 - },
3012 - {
3013 - "sourcePath": "toolkits/google_maps/public.md",
3014 - "sourceHeading": "Validate Places `includedTypes` against Google's supported place types"
3015 - },
3016 - {
3017 - "sourcePath": "toolkits/google_maps/public.md",
3018 - "sourceHeading": "Deprecated `GEOCODING_API` is not the Google Maps toolkit tool to use"
3019 - },
3020 - {
3021 - "sourcePath": "toolkits/google_maps/public.md",
3022 - "sourceHeading": "Google Maps APIs may require billing and quota management in GCP"
3023 - }
3024 - ],
3025 - "topics": [
3026 - "auth-config",
3027 - "authentication",
3028 - "errors-and-troubleshooting",
3029 - "sessions-and-execution",
3030 - "toolkits-and-providers"
3031 - ],
3032 - "tags": [
3033 - "for-you",
3034 - "google_maps",
3035 - "platform"
3036 - ],
3037 - "aliases": [
3038 - "/kb/toolkits/google-maps-troubleshooting",
3039 - "deprecated-geocoding-api-is-not-the-google-maps-toolkit-tool-to-use",
3040 - "google-maps-apis-may-require-billing-and-quota-management-in-gcp",
3041 - "google-maps-oauth-can-be-blocked-by-sensitive-cloud-platform-scope",
3042 - "google-maps-troubleshooting",
3043 - "maps-embed-api-requires-api-key-authentication",
3044 - "recreate-google-maps-auth-configs-after-default-oauth-app-updates",
3045 - "validate-places-includedtypes-against-google-s-supported-place-types"
3046 - ],
3047 - "relatedGuides": [],
3048 - "externalResources": [],
3049 - "updatedAt": "2026-06-24",
3050 - "lastVerifiedAt": "2026-08-12",
3051 - "reviewAfter": "2026-11-10",
3052 - "freshness": "evergreen",
3053 - "state": "published",
3054 - "featured": false
3055 - },
3056 - {
3057 - "slug": "toolkits-googleads",
3058 - "title": "Google Ads",
3059 - "description": "Public support knowledge for Google Ads.",
3060 - "articlePath": "toolkits-googleads.md",
3061 - "sources": [
3062 - {
3063 - "sourcePath": "toolkits/googleads/public.md",
3064 - "sourceHeading": "Google Ads developer token now belongs on the auth config, not connection initiation"
3065 - },
3066 - {
3067 - "sourcePath": "toolkits/googleads/public.md",
3068 - "sourceHeading": "Google Ads API requires both OAuth access token and developer token"
3069 - },
3070 - {
3071 - "sourcePath": "toolkits/googleads/public.md",
3072 - "sourceHeading": "Google Ads toolkit versions should be passed without the dashboard `v` prefix"
3073 - },
3074 - {
3075 - "sourcePath": "toolkits/googleads/public.md",
3076 - "sourceHeading": "Google Ads MCC/sub-account customer ID targeting is supported"
3077 - },
3078 - {
3079 - "sourcePath": "toolkits/googleads/public.md",
3080 - "sourceHeading": "Campaign mutate 400s can be caused by unsupported inline Campaign fields"
3081 - },
3082 - {
3083 - "sourcePath": "toolkits/googleads/public.md",
3084 - "sourceHeading": "Google Ads OAuth callback token-exchange failures usually point to incorrect credentials"
3085 - },
3086 - {
3087 - "sourcePath": "toolkits/googleads/public.md",
3088 - "sourceHeading": "Custom Google OAuth apps need callback routing through the customer's domain for branded consent"
3089 - }
3090 - ],
3091 - "topics": [
3092 - "auth-config",
3093 - "authentication",
3094 - "errors-and-troubleshooting",
3095 - "sessions-and-execution",
3096 - "toolkits-and-providers"
3097 - ],
3098 - "tags": [
3099 - "for-you",
3100 - "googleads",
3101 - "platform"
3102 - ],
3103 - "aliases": [
3104 - "/kb/toolkits/google-ads-troubleshooting",
3105 - "custom-google-oauth-apps-need-callback-routing-through-the-customer-s",
3106 - "google-ads-campaign-mutate-invalid-argument",
3107 - "google-ads-developer-token-belongs-on-the-auth-config",
3108 - "google-ads-oauth-callback-token-exchange-failures-usually-point-to-bad",
3109 - "google-ads-resource-exhausted-errors",
3110 - "google-ads-toolkit-versions-should-be-passed-without-the-dashboard-v-p",
3111 - "google-ads-troubleshooting",
3112 - "older-sdk-workaround-passed-google-ads-developer-token-and-customer-id",
3113 - "target-a-google-ads-sub-account"
3114 - ],
3115 - "relatedGuides": [],
3116 - "externalResources": [],
3117 - "updatedAt": "2026-07-14",
3118 - "lastVerifiedAt": "2026-08-17",
3119 - "reviewAfter": "2026-11-15",
3120 - "freshness": "evergreen",
3121 - "state": "published",
3122 - "featured": false
3123 - },
3124 - {
3125 - "slug": "toolkits-googlebigquery",
3126 - "title": "Google BigQuery",
3127 - "description": "Current authentication guidance for the Google BigQuery toolkit.",
3128 - "articlePath": "toolkits-googlebigquery.md",
3129 - "sources": [
3130 - {
3131 - "sourcePath": "toolkits/googlebigquery/public.md",
3132 - "sourceHeading": "BigQuery supports managed OAuth2, custom OAuth2, and service-account auth"
3133 - }
3134 - ],
3135 - "topics": [
3136 - "auth-config",
3137 - "authentication",
3138 - "errors-and-troubleshooting",
3139 - "toolkits-and-providers"
3140 - ],
3141 - "tags": [
3142 - "for-you",
3143 - "googlebigquery",
3144 - "oauth",
3145 - "platform"
3146 - ],
3147 - "aliases": [],
3148 - "relatedGuides": [],
3149 - "externalResources": [],
3150 - "updatedAt": "2026-08-17",
3151 - "lastVerifiedAt": "2026-08-24",
3152 - "reviewAfter": "2026-11-22",
3153 - "freshness": "evergreen",
3154 - "state": "published",
3155 - "featured": false
3156 - },
3157 - {
3158 - "slug": "toolkits-googledocs",
3159 - "title": "Google Docs",
3160 - "description": "Public support knowledge for Google Docs.",
3161 - "articlePath": "toolkits-googledocs.md",
3162 - "sources": [
3163 - {
3164 - "sourcePath": "toolkits/googledocs/public.md",
3165 - "sourceHeading": "`GOOGLEDOCS_CREATE_DOCUMENT_MARKDOWN` accepts GitHub-Flavored Markdown and HTML tables"
3166 - },
3167 - {
3168 - "sourcePath": "toolkits/googledocs/public.md",
3169 - "sourceHeading": "Google Docs tab-level read and edit is supported by specific Google Docs tools"
3170 - },
3171 - {
3172 - "sourcePath": "toolkits/googledocs/public.md",
3173 - "sourceHeading": "Google Docs supports managed and customer-owned OAuth2"
3174 - },
3175 - {
3176 - "sourcePath": "toolkits/googledocs/public.md",
3177 - "sourceHeading": "Google sensitive scopes can cause app-blocked errors unless the OAuth app is verified"
3178 - },
3179 - {
3180 - "sourcePath": "toolkits/googledocs/public.md",
3181 - "sourceHeading": "Google OAuth tokens are redacted from connected-account responses"
3182 - },
3183 - {
3184 - "sourcePath": "toolkits/googledocs/public.md",
3185 - "sourceHeading": "Multiple Google accounts require explicit multi-account selection"
3186 - },
3187 - {
3188 - "sourcePath": "toolkits/googledocs/public.md",
3189 - "sourceHeading": "Tool Router v2 sessions require connected accounts to belong to the same user/entity"
3190 - },
3191 - {
3192 - "sourcePath": "toolkits/googledocs/public.md",
3193 - "sourceHeading": "Specify Google auth config IDs at session creation so Manage Connection uses the intended configs"
3194 - },
3195 - {
3196 - "sourcePath": "toolkits/googledocs/public.md",
3197 - "sourceHeading": "Platform connections are isolated from For You / Connect MCP connections"
3198 - }
3199 - ],
3200 - "topics": [
3201 - "auth-config",
3202 - "authentication",
3203 - "errors-and-troubleshooting",
3204 - "sessions-and-execution",
3205 - "toolkits-and-providers"
3206 - ],
3207 - "tags": [
3208 - "for-you",
3209 - "googledocs",
3210 - "platform"
3211 - ],
3212 - "aliases": [
3213 - "/kb/toolkits/google-docs-troubleshooting",
3214 - "google-docs-tab-level-read-and-edit-is-supported-by-specific-google-do",
3215 - "google-docs-troubleshooting",
3216 - "google-sensitive-scopes-can-cause-app-blocked-errors-unless-the-oauth",
3217 - "googledocs-create-document-markdown-accepts-github-flavored-markdown-a",
3218 - "managed-google-oauth-tokens-stay-redacted-custom-oauth-is-needed-for-r",
3219 - "multiple-google-accounts-require-multi-account-support-or-distinct-con",
3220 - "platform-connections-are-isolated-from-for-you-connect-mcp-connections",
3221 - "specify-google-auth-config-ids-at-session-creation-so-manage-connectio",
3222 - "tool-router-v2-sessions-require-connected-accounts-to-belong-to-the-sa"
3223 - ],
3224 - "relatedGuides": [],
3225 - "externalResources": [],
3226 - "updatedAt": "2026-06-24",
3227 - "lastVerifiedAt": "2026-08-24",
3228 - "reviewAfter": "2026-11-22",
3229 - "freshness": "evergreen",
3230 - "state": "published",
3231 - "featured": false
3232 - },
3233 - {
3234 - "slug": "toolkits-googledrive",
3235 - "title": "Google Drive",
3236 - "description": "Public support knowledge for Google Drive.",
3237 - "articlePath": "toolkits-googledrive.md",
3238 - "sources": [
3239 - {
3240 - "sourcePath": "toolkits/googledrive/public.md",
3241 - "sourceHeading": "Google Drive upload tools can accept local file paths or URLs through SDK auto file handling"
3242 - },
3243 - {
3244 - "sourcePath": "toolkits/googledrive/public.md",
3245 - "sourceHeading": "Connect MCP exposes a curated Google Drive tool set and discovers the rest through meta-tools"
3246 - },
3247 - {
3248 - "sourcePath": "toolkits/googledrive/public.md",
3249 - "sourceHeading": "Google Drive watch/change webhooks require a public endpoint"
3250 - },
3251 - {
3252 - "sourcePath": "toolkits/googledrive/public.md",
3253 - "sourceHeading": "Google Drive downloads use temporary presigned URLs with configurable URL TTL and short-lived storage"
3254 - },
3255 - {
3256 - "sourcePath": "toolkits/googledrive/public.md",
3257 - "sourceHeading": "Disable SDK auto file handling when you need the raw Google Drive download output instead of a local path"
3258 - },
3259 - {
3260 - "sourcePath": "toolkits/googledrive/public.md",
3261 - "sourceHeading": "Use customer-owned Google OAuth credentials with verified scopes"
3262 - },
3263 - {
3264 - "sourcePath": "toolkits/googledrive/public.md",
3265 - "sourceHeading": "A missing Google Drive tool can be caused by passing an invalid toolkit version"
3266 - },
3267 - {
3268 - "sourcePath": "toolkits/googledrive/public.md",
3269 - "sourceHeading": "For a Google Drive file-browser UI, prefer direct tool execution over MCP as the primary integration layer"
3270 - },
3271 - {
3272 - "sourcePath": "toolkits/googledrive/public.md",
3273 - "sourceHeading": "Use `GOOGLEDRIVE_GET_ABOUT` to confirm which Google Drive account is connected"
3274 - },
3275 - {
3276 - "sourcePath": "toolkits/googledrive/public.md",
3277 - "sourceHeading": "Google Drive tool execution requests should include an `arguments` object, even when it is empty"
3278 - },
3279 - {
3280 - "sourcePath": "toolkits/googledrive/public.md",
3281 - "sourceHeading": "Tool Router v2 sessions require all connected accounts to belong to the same entity"
3282 - },
3283 - {
3284 - "sourcePath": "toolkits/googledrive/public.md",
3285 - "sourceHeading": "Choose the narrowest Google Drive scope that supports the workflow"
3286 - }
3287 - ],
3288 - "topics": [
3289 - "auth-config",
3290 - "authentication",
3291 - "errors-and-troubleshooting",
3292 - "sessions-and-execution",
3293 - "toolkits-and-providers"
3294 - ],
3295 - "tags": [
3296 - "for-you",
3297 - "googledrive",
3298 - "platform"
3299 - ],
3300 - "aliases": [
3301 - "/kb/toolkits/google-drive-troubleshooting",
3302 - "a-missing-google-drive-tool-can-be-caused-by-passing-an-invalid-toolki",
3303 - "disable-sdk-auto-file-handling-when-you-need-the-raw-google-drive-down",
3304 - "for-a-google-drive-file-browser-ui-prefer-direct-tool-execution-over-m",
3305 - "google-drive-downloads-use-temporary-presigned-urls-with-configurable",
3306 - "google-drive-tool-execution-requests-should-include-an-arguments-objec",
3307 - "google-drive-troubleshooting",
3308 - "google-drive-upload-tools-can-accept-local-file-paths-or-urls-through",
3309 - "google-drive-watch-change-webhooks-require-a-public-endpoint",
3310 - "managed-google-drive-scope-is-narrow",
3311 - "tool-router-v2-sessions-require-all-connected-accounts-to-belong-to-th",
3312 - "use-custom-google-oauth-credentials-when-managed-credentials-are-not-v"
3313 - ],
3314 - "relatedGuides": [],
3315 - "externalResources": [],
3316 - "updatedAt": "2026-06-24",
3317 - "lastVerifiedAt": "2026-08-17",
3318 - "reviewAfter": "2026-11-15",
3319 - "freshness": "evergreen",
3320 - "state": "published",
3321 - "featured": false
3322 - },
3323 - {
3324 - "slug": "toolkits-googlemeet",
3325 - "title": "Google Meet",
3326 - "description": "Public support knowledge for Google Meet.",
3327 - "articlePath": "toolkits-googlemeet.md",
3328 - "sources": [
3329 - {
3330 - "sourcePath": "toolkits/googlemeet/public.md",
3331 - "sourceHeading": "Use Google Super tool slugs with a Google Super connected account"
3332 - },
3333 - {
3334 - "sourcePath": "toolkits/googlemeet/public.md",
3335 - "sourceHeading": "Configure Meet scopes and enable the Google Meet API before creating Meet spaces"
3336 - },
3337 - {
3338 - "sourcePath": "toolkits/googlemeet/public.md",
3339 - "sourceHeading": "Fetch transcript entries by first resolving the conference record"
3340 - },
3341 - {
3342 - "sourcePath": "toolkits/googlemeet/public.md",
3343 - "sourceHeading": "403 permission errors usually mean the conference resource is inaccessible or missing"
3344 - },
3345 - {
3346 - "sourcePath": "toolkits/googlemeet/public.md",
3347 - "sourceHeading": "Recordings and transcripts require an eligible Google Workspace edition and enabled feature"
3348 - }
3349 - ],
3350 - "topics": [
3351 - "auth-config",
3352 - "authentication",
3353 - "errors-and-troubleshooting",
3354 - "sessions-and-execution",
3355 - "toolkits-and-providers"
3356 - ],
3357 - "tags": [
3358 - "for-you",
3359 - "googlemeet",
3360 - "platform"
3361 - ],
3362 - "aliases": [
3363 - "/kb/toolkits/google-meet-troubleshooting",
3364 - "403-permission-errors-usually-mean-the-conference-resource-is-inaccess",
3365 - "configure-meet-scopes-and-enable-the-google-meet-api-before-creating-m",
3366 - "google-meet-troubleshooting",
3367 - "google-workspace-enterprise-is-required-to-record-meetings-and-access",
3368 - "use-google-super-tool-slugs-with-a-google-super-connected-account"
3369 - ],
3370 - "relatedGuides": [],
3371 - "externalResources": [],
3372 - "updatedAt": "2026-06-24",
3373 - "lastVerifiedAt": "2026-08-17",
3374 - "reviewAfter": "2026-11-15",
3375 - "freshness": "evergreen",
3376 - "state": "published",
3377 - "featured": false
3378 - },
3379 - {
3380 - "slug": "toolkits-googlesheets",
3381 - "title": "Google Sheets",
3382 - "description": "Public support knowledge for Google Sheets.",
3383 - "articlePath": "toolkits-googlesheets.md",
3384 - "sources": [
3385 - {
3386 - "sourcePath": "toolkits/googlesheets/public.md",
3387 - "sourceHeading": "Platform Google Sheets connections are isolated from For You Connect MCP"
3388 - },
3389 - {
3390 - "sourcePath": "toolkits/googlesheets/public.md",
3391 - "sourceHeading": "Fetch more than the default 20 Google Sheets tools with `limit`"
3392 - },
3393 - {
3394 - "sourcePath": "toolkits/googlesheets/public.md",
3395 - "sourceHeading": "Google Sheets MCP may require the spreadsheet ID instead of searching by name"
3396 - },
3397 - {
3398 - "sourcePath": "toolkits/googlesheets/public.md",
3399 - "sourceHeading": "Use the current values tools to update, append, or create a populated sheet"
3400 - },
3401 - {
3402 - "sourcePath": "toolkits/googlesheets/public.md",
3403 - "sourceHeading": "Execute Google Sheets tools by passing the exact tool slug"
3404 - },
3405 - {
3406 - "sourcePath": "toolkits/googlesheets/public.md",
3407 - "sourceHeading": "Google Sheets 403s can be caused by an old placeholder toolkit version"
3408 - },
3409 - {
3410 - "sourcePath": "toolkits/googlesheets/public.md",
3411 - "sourceHeading": "Use Google Super when one Google connection should cover Gmail, Sheets, Docs, Drive, and other Google tools"
3412 - },
3413 - {
3414 - "sourcePath": "toolkits/googlesheets/public.md",
3415 - "sourceHeading": "Use full Google scope URLs such as `https://www.googleapis.com/auth/drive`, not shorthand `/drive`"
3416 - },
3417 - {
3418 - "sourcePath": "toolkits/googlesheets/public.md",
3419 - "sourceHeading": "Google Sheets provider quotas are separate from Composio plan limits"
3420 - }
3421 - ],
3422 - "topics": [
3423 - "auth-config",
3424 - "authentication",
3425 - "errors-and-troubleshooting",
3426 - "sessions-and-execution",
3427 - "toolkits-and-providers"
3428 - ],
3429 - "tags": [
3430 - "for-you",
3431 - "googlesheets",
3432 - "platform"
3433 - ],
3434 - "aliases": [
3435 - "/kb/authentication/google-sheets-troubleshooting",
3436 - "execute-google-sheets-tools-by-passing-the-exact-tool-slug",
3437 - "fetch-more-than-the-default-20-google-sheets-tools-with-limit",
3438 - "google-sheets-403s-can-be-caused-by-an-old-placeholder-toolkit-version",
3439 - "google-sheets-429s-are-google-s-api-quota-and-shared-default-oauth-can",
3440 - "google-sheets-auth-configs-require-full-scope-uris",
3441 - "google-sheets-mcp-may-require-the-spreadsheet-id-instead-of-searching",
3442 - "google-sheets-oauth-cannot-be-scoped-to-a-drive-folder",
3443 - "google-sheets-troubleshooting",
3444 - "old-google-sheets-integrations-may-need-a-new-integration-to-access-ne",
3445 - "platform-google-sheets-connections-are-isolated-from-for-you-connect-m",
3446 - "use-google-super-when-one-google-connection-should-cover-gmail-sheets",
3447 - "use-googlesheets-batch-update-or-googlesheets-sheet-from-json-to-add-v"
3448 - ],
3449 - "relatedGuides": [],
3450 - "externalResources": [],
3451 - "updatedAt": "2026-06-24",
3452 - "lastVerifiedAt": "2026-08-17",
3453 - "reviewAfter": "2026-11-15",
3454 - "freshness": "evergreen",
3455 - "state": "published",
3456 - "featured": false
3457 - },
3458 - {
3459 - "slug": "toolkits-googleslides",
3460 - "title": "Google Slides",
3461 - "description": "Public support knowledge for Google Slides.",
3462 - "articlePath": "toolkits-googleslides.md",
3463 - "sources": [
3464 - {
3465 - "sourcePath": "toolkits/googleslides/public.md",
3466 - "sourceHeading": "Use Google Drive search to list or discover Google Slides presentations"
3467 - },
3468 - {
3469 - "sourcePath": "toolkits/googleslides/public.md",
3470 - "sourceHeading": "`GOOGLESLIDES_PRESENTATIONS_GET` needs the presentation ID from the URL or Drive payload"
3471 - },
3472 - {
3473 - "sourcePath": "toolkits/googleslides/public.md",
3474 - "sourceHeading": "Use the same Google account when pairing Drive discovery with Google Slides reads"
3475 - },
3476 - {
3477 - "sourcePath": "toolkits/googleslides/public.md",
3478 - "sourceHeading": "Google Slide creation tools are available through Google Super"
3479 - },
3480 - {
3481 - "sourcePath": "toolkits/googleslides/public.md",
3482 - "sourceHeading": "Custom Google Slides OAuth apps must be verified for sensitive scopes"
3483 - },
3484 - {
3485 - "sourcePath": "toolkits/googleslides/public.md",
3486 - "sourceHeading": "Google Slides supports one trigger in Composio"
3487 - }
3488 - ],
3489 - "topics": [
3490 - "auth-config",
3491 - "authentication",
3492 - "errors-and-troubleshooting",
3493 - "sessions-and-execution",
3494 - "toolkits-and-providers"
3495 - ],
3496 - "tags": [
3497 - "for-you",
3498 - "googleslides",
3499 - "platform"
3500 - ],
3501 - "aliases": [
3502 - "/kb/toolkits/google-slides-troubleshooting",
3503 - "custom-google-slides-oauth-apps-must-be-verified-for-sensitive-scopes",
3504 - "google-slide-creation-tools-are-available-through-google-super",
3505 - "google-slides-may-require-a-custom-oauth-app-instead-of-default-compos",
3506 - "google-slides-troubleshooting",
3507 - "googledrive-create-file-from-text-cannot-create-native-google-slides-f",
3508 - "googleslides-presentations-get-needs-the-presentation-id-from-the-url",
3509 - "use-google-drive-search-to-list-or-discover-google-slides-presentation",
3510 - "use-the-same-google-account-when-pairing-drive-discovery-with-google-s"
3511 - ],
3512 - "relatedGuides": [],
3513 - "externalResources": [],
3514 - "updatedAt": "2026-06-24",
3515 - "lastVerifiedAt": "2026-08-12",
3516 - "reviewAfter": "2026-11-10",
3517 - "freshness": "evergreen",
3518 - "state": "published",
3519 - "featured": false
3520 - },
3521 - {
3522 - "slug": "toolkits-googlesuper",
3523 - "title": "Google Super",
3524 - "description": "Public support knowledge for Google Super.",
3525 - "articlePath": "toolkits-googlesuper.md",
3526 - "sources": [
3527 - {
3528 - "sourcePath": "toolkits/googlesuper/public.md",
3529 - "sourceHeading": "Google Super is a unified Google Workspace toolkit"
3530 - },
3531 - {
3532 - "sourcePath": "toolkits/googlesuper/public.md",
3533 - "sourceHeading": "Google Meet through Google Super needs Meet scopes and Google Meet API enabled"
3534 - },
3535 - {
3536 - "sourcePath": "toolkits/googlesuper/public.md",
3537 - "sourceHeading": "Google Super can be narrowed by removing unneeded scopes and tools"
3538 - },
3539 - {
3540 - "sourcePath": "toolkits/googlesuper/public.md",
3541 - "sourceHeading": "Gmail filter creation through Google Super also requires `gmail.settings.basic`"
3542 - },
3543 - {
3544 - "sourcePath": "toolkits/googlesuper/public.md",
3545 - "sourceHeading": "`GOOGLESUPER_LIST_LABELS` with `include_details=true` can be slow because it fans out per label"
3546 - },
3547 - {
3548 - "sourcePath": "toolkits/googlesuper/public.md",
3549 - "sourceHeading": "Gmail thread listing includes `resultSizeEstimate`"
3550 - },
3551 - {
3552 - "sourcePath": "toolkits/googlesuper/public.md",
3553 - "sourceHeading": "Use Gmail/Google Super query and label filters to find sent or labeled messages"
3554 - },
3555 - {
3556 - "sourcePath": "toolkits/googlesuper/public.md",
3557 - "sourceHeading": "Google Super Sheets 404s can mean wrong spreadsheet ID, missing access, or missing spreadsheet scope"
3558 - },
3559 - {
3560 - "sourcePath": "toolkits/googlesuper/public.md",
3561 - "sourceHeading": "`Connection initiation did not complete within 10 minutes` means OAuth consent was not completed, not token refresh failure"
3562 - },
3563 - {
3564 - "sourcePath": "toolkits/googlesuper/public.md",
3565 - "sourceHeading": "Google users can deselect scopes during consent; Composio marks active if token exchange succeeds"
3566 - }
3567 - ],
3568 - "topics": [
3569 - "auth-config",
3570 - "authentication",
3571 - "errors-and-troubleshooting",
3572 - "sessions-and-execution",
3573 - "toolkits-and-providers"
3574 - ],
3575 - "tags": [
3576 - "for-you",
3577 - "googlesuper",
3578 - "platform"
3579 - ],
3580 - "aliases": [
3581 - "/kb/toolkits/google-super-troubleshooting",
3582 - "connection-initiation-did-not-complete-within-10-minutes-means-oauth-c",
3583 - "gmail-filter-creation-through-google-super-also-requires-gmail-setting",
3584 - "google-meet-through-google-super-needs-meet-scopes-and-google-meet-api",
3585 - "google-super-can-be-narrowed-by-removing-unneeded-scopes-and-tools",
3586 - "google-super-cannot-schedule-gmail-emails-out-of-the-box",
3587 - "google-super-is-a-unified-google-workspace-toolkit",
3588 - "google-super-sheets-404s-can-mean-wrong-spreadsheet-id-missing-access",
3589 - "google-super-troubleshooting",
3590 - "google-users-can-deselect-scopes-during-consent-composio-marks-active",
3591 - "googlesuper-list-labels-with-include-details-true-can-be-slow-because",
3592 - "googlesuper-list-threads-verbose-behavior-trades-payload-latency-for-d",
3593 - "managed-google-super-oauth-issues-can-be-unblocked-by-switching-to-a-c",
3594 - "missing-google-super-endpoints-should-be-filed-as-tool-requests-not-to",
3595 - "resultsizeestimate-was-added-to-gmail-thread-listing-response",
3596 - "use-gmail-google-super-query-and-label-filters-to-find-sent-or-labeled"
3597 - ],
3598 - "relatedGuides": [],
3599 - "externalResources": [],
3600 - "updatedAt": "2026-06-24",
3601 - "lastVerifiedAt": "2026-08-17",
3602 - "reviewAfter": "2026-11-15",
3603 - "freshness": "evergreen",
3604 - "state": "published",
3605 - "featured": false
3606 - },
3607 - {
3608 - "slug": "toolkits-googletasks",
3609 - "title": "Google Tasks",
3610 - "description": "Public OAuth, connection, and quota troubleshooting for Google Tasks.",
3611 - "articlePath": "toolkits-googletasks.md",
3612 - "sources": [
3613 - {
3614 - "sourcePath": "toolkits/googletasks/public.md",
3615 - "sourceHeading": "Set up custom Google OAuth credentials"
3616 - },
3617 - {
3618 - "sourcePath": "toolkits/googletasks/public.md",
3619 - "sourceHeading": "Resolve an \"App is blocked\" connection error"
3620 - },
3621 - {
3622 - "sourcePath": "toolkits/googletasks/public.md",
3623 - "sourceHeading": "Enable the Google Tasks API for custom OAuth"
3624 - },
3625 - {
3626 - "sourcePath": "toolkits/googletasks/public.md",
3627 - "sourceHeading": "Resolve `Error 400: invalid_scope`"
3628 - },
3629 - {
3630 - "sourcePath": "toolkits/googletasks/public.md",
3631 - "sourceHeading": "Choose managed or customer-owned Google OAuth"
3632 - },
3633 - {
3634 - "sourcePath": "toolkits/googletasks/public.md",
3635 - "sourceHeading": "Resolve 401 errors on tool calls"
3636 - }
3637 - ],
3638 - "topics": [
3639 - "auth-config",
3640 - "authentication",
3641 - "errors-and-troubleshooting",
3642 - "sessions-and-execution",
3643 - "toolkits-and-providers"
3644 - ],
3645 - "tags": [
3646 - "for-you",
3647 - "googletasks",
3648 - "oauth",
3649 - "platform",
3650 - "quotas",
3651 - "scopes"
3652 - ],
3653 - "aliases": [
3654 - "/kb/toolkits/google-tasks-troubleshooting",
3655 - "enable-the-google-tasks-api-for-custom-oauth",
3656 - "google-tasks-troubleshooting",
3657 - "handle-quota-or-rate-limit-exhaustion",
3658 - "resolve-error-400-invalid-scope-2",
3659 - "set-up-custom-google-oauth-credentials-2"
3660 - ],
3661 - "relatedGuides": [],
3662 - "externalResources": [],
3663 - "updatedAt": "2026-07-24",
3664 - "lastVerifiedAt": "2026-08-24",
3665 - "reviewAfter": "2026-11-22",
3666 - "freshness": "evergreen",
3667 - "state": "published",
3668 - "featured": false
3669 - },
3670 - {
3671 - "slug": "toolkits-granola-mcp",
3672 - "title": "Granola MCP",
3673 - "description": "Public behavior and schema guidance for the official Granola MCP server.",
3674 - "articlePath": "toolkits-granola-mcp.md",
3675 - "sources": [
3676 - {
3677 - "sourcePath": "toolkits/granola_mcp/public.md",
3678 - "sourceHeading": "Composio mirrors Granola's official MCP server"
3679 - }
3680 - ],
3681 - "topics": [
3682 - "errors-and-troubleshooting",
3683 - "sessions-and-execution",
3684 - "toolkits-and-providers"
3685 - ],
3686 - "tags": [
3687 - "for-you",
3688 - "granola",
3689 - "mcp",
3690 - "platform",
3691 - "schemas"
3692 - ],
3693 - "aliases": [
3694 - "/kb/toolkits/granola-mcp-metadata-comes-from-the-upstream-server",
3695 - "granola-mcp-metadata-comes-from-the-upstream-server"
3696 - ],
3697 - "relatedGuides": [],
3698 - "externalResources": [],
3699 - "updatedAt": "2026-07-14",
3700 - "lastVerifiedAt": "2026-08-17",
3701 - "reviewAfter": "2026-11-15",
3702 - "freshness": "evergreen",
3703 - "state": "published",
3704 - "featured": false
3705 - },
3706 - {
3707 - "slug": "toolkits-hubspot",
3708 - "title": "HubSpot",
3709 - "description": "Public support knowledge for HubSpot.",
3710 - "articlePath": "toolkits-hubspot.md",
3711 - "sources": [
3712 - {
3713 - "sourcePath": "toolkits/hubspot/public.md",
3714 - "sourceHeading": "Minimum HubSpot contact scopes are contact read/write"
3715 - },
3716 - {
3717 - "sourcePath": "toolkits/hubspot/public.md",
3718 - "sourceHeading": "Use Composio scopes API or HubSpot docs to find required HubSpot scopes"
3719 - },
3720 - {
3721 - "sourcePath": "toolkits/hubspot/public.md",
3722 - "sourceHeading": "Create custom HubSpot tools through toolkit-authenticated API requests"
3723 - },
3724 - {
3725 - "sourcePath": "toolkits/hubspot/public.md",
3726 - "sourceHeading": "HubSpot trigger setup needs the HubSpot app ID"
3727 - },
3728 - {
3729 - "sourcePath": "toolkits/hubspot/public.md",
3730 - "sourceHeading": "Use custom HubSpot credentials for white-label auth"
3731 - },
3732 - {
3733 - "sourcePath": "toolkits/hubspot/public.md",
3734 - "sourceHeading": "HubSpot scopes must be predeclared in the HubSpot app config"
3735 - },
3736 - {
3737 - "sourcePath": "toolkits/hubspot/public.md",
3738 - "sourceHeading": "HubSpot OAuth token-fetch 400: check client secret and required-scope alignment"
3739 - },
3740 - {
3741 - "sourcePath": "toolkits/hubspot/public.md",
3742 - "sourceHeading": "Old HubSpot SDK/toolkit versions use old double-prefixed slugs"
3743 - },
3744 - {
3745 - "sourcePath": "toolkits/hubspot/public.md",
3746 - "sourceHeading": "HubSpot auth loops can be caused by HubSpot-side workspace/login state"
3747 - },
3748 - {
3749 - "sourcePath": "toolkits/hubspot/public.md",
3750 - "sourceHeading": "HubSpot marketing campaign objects do not expose a properties API like CRM objects"
3751 - },
3752 - {
3753 - "sourcePath": "toolkits/hubspot/public.md",
3754 - "sourceHeading": "HubSpot triggers require each customer’s own app ID and developer API key"
3755 - },
3756 - {
3757 - "sourcePath": "toolkits/hubspot/public.md",
3758 - "sourceHeading": "Deleting a HubSpot connected account disconnects it and stops token refresh"
3759 - }
3760 - ],
3761 - "topics": [
3762 - "auth-config",
3763 - "authentication",
3764 - "errors-and-troubleshooting",
3765 - "sessions-and-execution",
3766 - "toolkits-and-providers"
3767 - ],
3768 - "tags": [
3769 - "for-you",
3770 - "hubspot",
3771 - "platform"
3772 - ],
3773 - "aliases": [
3774 - "/kb/authentication/hubspot-troubleshooting",
3775 - "/kb/toolkits/after-hubspot-trigger-fixes-recreate-old-triggers",
3776 - "after-hubspot-trigger-fixes-recreate-old-triggers",
3777 - "composio-does-not-provide-hubspot-field-level-permissions-restrict-by",
3778 - "create-custom-hubspot-tools-through-toolkit-authenticated-api-requests",
3779 - "fix-hubspot-oauth-token-exchange-400-client-secret-and-scopes",
3780 - "hubspot-auth-loops-can-be-caused-by-hubspot-side-workspace-login-state",
3781 - "hubspot-managed-oauth-app-unverified-warning-has-no-reliable-eta-byoa",
3782 - "hubspot-marketing-campaign-objects-do-not-expose-a-properties-api-like",
3783 - "hubspot-scopes-must-be-predeclared-in-the-hubspot-app-config",
3784 - "hubspot-trigger-setup-needs-the-hubspot-app-id",
3785 - "hubspot-triggers-require-each-customer-s-own-app-id-and-developer-api",
3786 - "hubspot-troubleshooting",
3787 - "minimum-hubspot-contact-scopes-are-contact-read-write",
3788 - "some-hubspot-scopes-are-not-in-composio-managed-auth-use-own-oauth-app",
3789 - "use-composio-scopes-api-or-hubspot-docs-to-find-required-hubspot-scope",
3790 - "use-custom-hubspot-credentials-for-white-label-auth"
3791 - ],
3792 - "relatedGuides": [],
3793 - "externalResources": [],
3794 - "updatedAt": "2026-06-24",
3795 - "lastVerifiedAt": "2026-08-12",
3796 - "reviewAfter": "2026-11-10",
3797 - "freshness": "evergreen",
3798 - "state": "published",
3799 - "featured": false,
3800 - "verifyIgnoreToolSlugs": [
3801 - "HUBSPOT_HUBSPOT_LIST_CONTACTS"
3802 - ]
3803 - },
3804 - {
3805 - "slug": "toolkits-instagram",
3806 - "title": "Instagram",
3807 - "description": "Public support knowledge for Instagram.",
3808 - "articlePath": "toolkits-instagram.md",
3809 - "sources": [
3810 - {
3811 - "sourcePath": "toolkits/instagram/public.md",
3812 - "sourceHeading": "Instagram OAuth tokens are bound to the account selected in Facebook Login"
3813 - },
3814 - {
3815 - "sourcePath": "toolkits/instagram/public.md",
3816 - "sourceHeading": "Instagram uses Business Login and only supported/verified scopes should be configured"
3817 - },
3818 - {
3819 - "sourcePath": "toolkits/instagram/public.md",
3820 - "sourceHeading": "Instagram toolkit requires a Business/Creator account for supported business features"
3821 - },
3822 - {
3823 - "sourcePath": "toolkits/instagram/public.md",
3824 - "sourceHeading": "Use `INSTAGRAM_LIST_ALL_MESSAGES` to fetch Instagram messages"
3825 - },
3826 - {
3827 - "sourcePath": "toolkits/instagram/public.md",
3828 - "sourceHeading": "Instagram DM send failures with code 10/subcode 2534022 are Meta's 24-hour messaging window"
3829 - },
3830 - {
3831 - "sourcePath": "toolkits/instagram/public.md",
3832 - "sourceHeading": "For custom Instagram/Meta OAuth, configure the redirect URI in the Meta app"
3833 - },
3834 - {
3835 - "sourcePath": "toolkits/instagram/public.md",
3836 - "sourceHeading": "For Instagram DMs via n8n/Claude, Connect MCP can simplify setup"
3837 - },
3838 - {
3839 - "sourcePath": "toolkits/instagram/public.md",
3840 - "sourceHeading": "`INSTAGRAM_POST_IG_MEDIA_COMMENTS` failures can be caused by an incorrect `ig_media_id`"
3841 - },
3842 - {
3843 - "sourcePath": "toolkits/instagram/public.md",
3844 - "sourceHeading": "Instagram is available as a toolkit and can be connected via a new authConfig"
3845 - },
3846 - {
3847 - "sourcePath": "toolkits/instagram/public.md",
3848 - "sourceHeading": "Publish local media with `image_file` or `video_file`"
3849 - }
3850 - ],
3851 - "topics": [
3852 - "auth-config",
3853 - "authentication",
3854 - "errors-and-troubleshooting",
3855 - "sessions-and-execution",
3856 - "toolkits-and-providers"
3857 - ],
3858 - "tags": [
3859 - "for-you",
3860 - "instagram",
3861 - "platform"
3862 - ],
3863 - "aliases": [
3864 - "/kb/toolkits/instagram-troubleshooting",
3865 - "for-custom-instagram-meta-oauth-configure-the-redirect-uri-in-the-meta",
3866 - "for-instagram-dms-via-n8n-claude-connect-mcp-can-simplify-setup",
3867 - "instagram-dm-send-failures-with-code-10-subcode-2534022-are-meta-s-24",
3868 - "instagram-is-available-as-a-toolkit-and-can-be-connected-via-a-new-aut",
3869 - "instagram-oauth-tokens-are-bound-to-the-account-selected-in-facebook-l",
3870 - "instagram-post-ig-media-comments-failures-can-be-caused-by-an-incorrec",
3871 - "instagram-reply-to-comment-may-require-a-scope-not-available-in-the-ma",
3872 - "instagram-toolkit-requires-a-business-creator-account-for-supported-bu",
3873 - "instagram-troubleshooting",
3874 - "instagram-uses-business-login-and-only-supported-verified-scopes-shoul",
3875 - "stage-local-instagram-media-before-publishing",
3876 - "use-instagram-list-all-messages-to-fetch-instagram-messages",
3877 - "use-your-own-meta-oauth-app-for-high-volume-instagram-production-usage"
3878 - ],
3879 - "relatedGuides": [],
3880 - "externalResources": [],
3881 - "updatedAt": "2026-07-14",
3882 - "lastVerifiedAt": "2026-08-12",
3883 - "reviewAfter": "2026-11-10",
3884 - "freshness": "evergreen",
3885 - "state": "published",
3886 - "featured": false
3887 - },
3888 - {
3889 - "slug": "toolkits-intercom",
3890 - "title": "Intercom",
3891 - "description": "Public support knowledge for Intercom.",
3892 - "articlePath": "toolkits-intercom.md",
3893 - "sources": [
3894 - {
3895 - "sourcePath": "toolkits/intercom/public.md",
3896 - "sourceHeading": "Use External Pages or a custom agent when connecting MCP knowledge to Intercom Fin"
3897 - },
3898 - {
3899 - "sourcePath": "toolkits/intercom/public.md",
3900 - "sourceHeading": "INTERCOM_LIST_ALL_COMPANIES per_page limit is 60"
3901 - },
3902 - {
3903 - "sourcePath": "toolkits/intercom/public.md",
3904 - "sourceHeading": "Update Python SDK packages when Intercom tool schemas fail on reserved parameter names"
3905 - }
3906 - ],
3907 - "topics": [
3908 - "errors-and-troubleshooting",
3909 - "sessions-and-execution",
3910 - "toolkits-and-providers"
3911 - ],
3912 - "tags": [
3913 - "for-you",
3914 - "intercom",
3915 - "platform"
3916 - ],
3917 - "aliases": [
3918 - "/kb/toolkits/intercom-troubleshooting",
3919 - "avoid-proxy-execute-for-slow-intercom-api-calls-that-can-hit-cloudflar",
3920 - "intercom-list-all-companies-per-page-limit-is-60",
3921 - "intercom-oauth-tokens-cannot-be-programmatically-revoked-by-composio",
3922 - "intercom-troubleshooting",
3923 - "update-python-sdk-packages-when-intercom-tool-schemas-fail-on-reserved",
3924 - "use-a-custom-intercom-developer-app-if-composio-s-hosted-oauth-app-is",
3925 - "use-external-pages-or-a-custom-agent-when-connecting-mcp-knowledge-to"
3926 - ],
3927 - "relatedGuides": [],
3928 - "externalResources": [],
3929 - "updatedAt": "2026-06-24",
3930 - "lastVerifiedAt": "2026-08-12",
3931 - "reviewAfter": "2026-11-10",
3932 - "freshness": "evergreen",
3933 - "state": "published",
3934 - "featured": false
3935 - },
3936 - {
3937 - "slug": "toolkits-jira",
3938 - "title": "Jira",
3939 - "description": "Public support knowledge for Jira.",
3940 - "articlePath": "toolkits-jira.md",
3941 - "sources": [
3942 - {
3943 - "sourcePath": "toolkits/jira/public.md",
3944 - "sourceHeading": "Keep Jira OAuth scopes within Atlassian's supported set"
3945 - },
3946 - {
3947 - "sourcePath": "toolkits/jira/public.md",
3948 - "sourceHeading": "Pin custom Jira authConfig when creating Tool Router sessions"
3949 - },
3950 - {
3951 - "sourcePath": "toolkits/jira/public.md",
3952 - "sourceHeading": "Jira custom token execution needs the Atlassian base URL/subdomain"
3953 - },
3954 - {
3955 - "sourcePath": "toolkits/jira/public.md",
3956 - "sourceHeading": "Jira search pagination tokens returned by current tools preserve search context"
3957 - },
3958 - {
3959 - "sourcePath": "toolkits/jira/public.md",
3960 - "sourceHeading": "Jira OAuth redirect URI must match the authConfig and Atlassian app"
3961 - },
3962 - {
3963 - "sourcePath": "toolkits/jira/public.md",
3964 - "sourceHeading": "Missing `audience=api.atlassian.com` can prevent Jira refresh tokens"
3965 - },
3966 - {
3967 - "sourcePath": "toolkits/jira/public.md",
3968 - "sourceHeading": "Use `JIRA_GET_CREATE_METADATA_ISSUE_TYPE_FIELDS` instead of deprecated create metadata behavior"
3969 - },
3970 - {
3971 - "sourcePath": "toolkits/jira/public.md",
3972 - "sourceHeading": "Download Jira attachments with `JIRA_GET_ATTACHMENT`"
3973 - },
3974 - {
3975 - "sourcePath": "toolkits/jira/public.md",
3976 - "sourceHeading": "Jira tool-call payload retention follows the project log-storage setting"
3977 - },
3978 - {
3979 - "sourcePath": "toolkits/jira/public.md",
3980 - "sourceHeading": "Jira service account use requires customer-owned credentials and scopes"
3981 - }
3982 - ],
3983 - "topics": [
3984 - "auth-config",
3985 - "authentication",
3986 - "errors-and-troubleshooting",
3987 - "sessions-and-execution",
3988 - "toolkits-and-providers"
3989 - ],
3990 - "tags": [
3991 - "for-you",
3992 - "jira",
3993 - "platform"
3994 - ],
3995 - "aliases": [
3996 - "/kb/toolkits/jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop",
3997 - "/kb/toolkits/jira-troubleshooting",
3998 - "composio-manages-jira-oauth-tokens-but-does-not-store-jira-api-respons",
3999 - "download-jira-attachments-with-jira-get-attachment",
4000 - "jira-credentials-expire-without-refresh",
4001 - "jira-custom-token-execution-needs-the-atlassian-base-url-subdomain",
4002 - "jira-managed-oauth-something-went-wrong-was-caused-by-managed-app-scop",
4003 - "jira-oauth-redirect-uri-must-match-the-authconfig-and-atlassian-app",
4004 - "jira-search-pagination-token-requires-the-original-jql-or-filters",
4005 - "jira-service-account-use-requires-customer-owned-credentials-and-scope",
4006 - "jira-troubleshooting",
4007 - "pin-custom-jira-authconfig-when-creating-tool-router-sessions",
4008 - "use-jira-get-create-metadata-issue-type-fields-instead-of-deprecated-c"
4009 - ],
4010 - "relatedGuides": [],
4011 - "externalResources": [],
4012 - "updatedAt": "2026-07-16",
4013 - "lastVerifiedAt": "2026-08-12",
4014 - "reviewAfter": "2026-11-10",
4015 - "freshness": "evergreen",
4016 - "state": "published",
4017 - "featured": false
4018 - },
4019 - {
4020 - "slug": "toolkits-kickbox",
4021 - "title": "Kickbox",
4022 - "description": "Public support knowledge for Kickbox.",
4023 - "articlePath": "toolkits-kickbox.md",
4024 - "sources": [
4025 - {
4026 - "sourcePath": "toolkits/kickbox/public.md",
4027 - "sourceHeading": "Single verification auth and EU endpoint checks"
4028 - }
4029 - ],
4030 - "topics": [
4031 - "authentication",
4032 - "errors-and-troubleshooting",
4033 - "sessions-and-execution",
4034 - "toolkits-and-providers"
4035 - ],
4036 - "tags": [
4037 - "for-you",
4038 - "kickbox",
4039 - "platform"
4040 - ],
4041 - "aliases": [],
4042 - "relatedGuides": [],
4043 - "externalResources": [],
4044 - "updatedAt": "2026-06-24",
4045 - "lastVerifiedAt": "2026-08-12",
4046 - "reviewAfter": "2026-11-10",
4047 - "freshness": "evergreen",
4048 - "state": "published",
4049 - "featured": false
4050 - },
4051 - {
4052 - "slug": "toolkits-klaviyo",
4053 - "title": "Klaviyo",
4054 - "description": "Public support knowledge for Klaviyo.",
4055 - "articlePath": "toolkits-klaviyo.md",
4056 - "sources": [
4057 - {
4058 - "sourcePath": "toolkits/klaviyo/public.md",
4059 - "sourceHeading": "Klaviyo schema keys that exceeded Claude's 64-character limit were fixed"
4060 - }
4061 - ],
4062 - "topics": [
4063 - "errors-and-troubleshooting",
4064 - "sessions-and-execution",
4065 - "toolkits-and-providers"
4066 - ],
4067 - "tags": [
4068 - "for-you",
4069 - "klaviyo",
4070 - "platform"
4071 - ],
4072 - "aliases": [],
4073 - "relatedGuides": [],
4074 - "externalResources": [],
4075 - "updatedAt": "2026-06-24",
4076 - "lastVerifiedAt": "2026-08-12",
4077 - "reviewAfter": "2026-11-10",
4078 - "freshness": "evergreen",
4079 - "state": "published",
4080 - "featured": false
4081 - },
4082 - {
4083 - "slug": "toolkits-kommo",
4084 - "title": "Kommo",
4085 - "description": "Public authentication and subdomain troubleshooting for Kommo.",
4086 - "articlePath": "toolkits-kommo.md",
4087 - "sources": [
4088 - {
4089 - "sourcePath": "toolkits/kommo/public.md",
4090 - "sourceHeading": "Enter only the Kommo account subdomain"
4091 - }
4092 - ],
4093 - "topics": [
4094 - "authentication",
4095 - "errors-and-troubleshooting",
4096 - "toolkits-and-providers"
4097 - ],
4098 - "tags": [
4099 - "for-you",
4100 - "kommo",
4101 - "oauth",
4102 - "platform",
4103 - "subdomain"
4104 - ],
4105 - "aliases": [
4106 - "/kb/toolkits/enter-only-the-kommo-account-subdomain",
4107 - "enter-only-the-kommo-account-subdomain"
4108 - ],
4109 - "relatedGuides": [],
4110 - "externalResources": [],
4111 - "updatedAt": "2026-07-24",
4112 - "lastVerifiedAt": "2026-08-12",
4113 - "reviewAfter": "2026-11-10",
4114 - "freshness": "evergreen",
4115 - "state": "published",
4116 - "featured": false
4117 - },
4118 - {
4119 - "slug": "toolkits-launch-darkly",
4120 - "title": "LaunchDarkly",
4121 - "description": "Public support knowledge for LaunchDarkly.",
4122 - "articlePath": "toolkits-launch-darkly.md",
4123 - "sources": [
4124 - {
4125 - "sourcePath": "toolkits/launch_darkly/public.md",
4126 - "sourceHeading": "LaunchDarkly currently uses a REST API access token"
4127 - },
4128 - {
4129 - "sourcePath": "toolkits/launch_darkly/public.md",
4130 - "sourceHeading": "OAuth client actions operate after toolkit authentication"
4131 - }
4132 - ],
4133 - "topics": [
4134 - "authentication",
4135 - "errors-and-troubleshooting",
4136 - "sessions-and-execution",
4137 - "toolkits-and-providers"
4138 - ],
4139 - "tags": [
4140 - "for-you",
4141 - "launch_darkly",
4142 - "platform"
4143 - ],
4144 - "aliases": [
4145 - "/kb/toolkits/launchdarkly-troubleshooting",
4146 - "feasibility-notes",
4147 - "launchdarkly-troubleshooting",
4148 - "oauth-client-actions-are-not-oauth-connection-support"
4149 - ],
4150 - "relatedGuides": [],
4151 - "externalResources": [],
4152 - "updatedAt": "2026-06-24",
4153 - "lastVerifiedAt": "2026-08-17",
4154 - "reviewAfter": "2026-11-15",
4155 - "freshness": "evergreen",
4156 - "state": "published",
4157 - "featured": false
4158 - },
4159 - {
4160 - "slug": "toolkits-linear",
4161 - "title": "Linear",
4162 - "description": "Public trigger configuration guidance for Linear.",
4163 - "articlePath": "toolkits-linear.md",
4164 - "sources": [
4165 - {
4166 - "sourcePath": "toolkits/linear/public.md",
4167 - "sourceHeading": "Linear triggers require a valid `team_id`"
4168 - }
4169 - ],
4170 - "topics": [
4171 - "errors-and-troubleshooting",
4172 - "sessions-and-execution",
4173 - "toolkits-and-providers"
4174 - ],
4175 - "tags": [
4176 - "for-you",
4177 - "linear",
4178 - "platform",
4179 - "team_id",
4180 - "triggers"
4181 - ],
4182 - "aliases": [
4183 - "/kb/toolkits/linear-triggers-require-a-valid-team-id",
4184 - "linear-triggers-require-a-valid-team-id"
4185 - ],
4186 - "relatedGuides": [],
4187 - "externalResources": [],
4188 - "updatedAt": "2026-07-24",
4189 - "lastVerifiedAt": "2026-08-12",
4190 - "reviewAfter": "2026-11-10",
4191 - "freshness": "evergreen",
4192 - "state": "published",
4193 - "featured": false
4194 - },
4195 - {
4196 - "slug": "toolkits-linkedin",
4197 - "title": "LinkedIn",
4198 - "description": "Public support knowledge for LinkedIn.",
4199 - "articlePath": "toolkits-linkedin.md",
4200 - "sources": [
4201 - {
4202 - "sourcePath": "toolkits/linkedin/public.md",
4203 - "sourceHeading": "Fix LinkedIn 426 NONEXISTENT_VERSION by using the latest toolkit version"
4204 - },
4205 - {
4206 - "sourcePath": "toolkits/linkedin/public.md",
4207 - "sourceHeading": "Fetch modern LinkedIn tools with `toolkit_slug=linkedin` and `toolkit_versions=latest`"
4208 - },
4209 - {
4210 - "sourcePath": "toolkits/linkedin/public.md",
4211 - "sourceHeading": "LinkedIn organization scopes depend on the toolkit and auth config"
4212 - },
4213 - {
4214 - "sourcePath": "toolkits/linkedin/public.md",
4215 - "sourceHeading": "LinkedIn post creation supports image arrays through SDK/API"
4216 - },
4217 - {
4218 - "sourcePath": "toolkits/linkedin/public.md",
4219 - "sourceHeading": "Use Connect MCP instead of legacy Platform MCP for consumer LinkedIn connector flows"
4220 - },
4221 - {
4222 - "sourcePath": "toolkits/linkedin/public.md",
4223 - "sourceHeading": "Fix LinkedIn Ads `redirect_uri` mismatch before debugging scopes"
4224 - },
4225 - {
4226 - "sourcePath": "toolkits/linkedin/public.md",
4227 - "sourceHeading": "LinkedIn Ads `unauthorized_scope_error` means a requested scope is unavailable"
4228 - }
4229 - ],
4230 - "topics": [
4231 - "auth-config",
4232 - "authentication",
4233 - "errors-and-troubleshooting",
4234 - "sessions-and-execution",
4235 - "toolkits-and-providers"
4236 - ],
4237 - "tags": [
4238 - "for-you",
4239 - "linkedin",
4240 - "platform"
4241 - ],
4242 - "aliases": [
4243 - "/kb/toolkits/linkedin-troubleshooting",
4244 - "fetch-modern-linkedin-tools-with-toolkit-slug-linkedin-and-toolkit-ver",
4245 - "fix-linkedin-426-nonexistent-version",
4246 - "fix-linkedin-ads-redirect-uri-mismatch-before-debugging-scopes",
4247 - "linkedin-ads-unauthorized-scope-error-means-a-requested-scope-is-unava",
4248 - "linkedin-company-actions-require-organization-scopes",
4249 - "linkedin-get-company-info-currently-returns-one-company-profile",
4250 - "linkedin-post-creation-supports-image-arrays-through-sdk-api",
4251 - "linkedin-troubleshooting",
4252 - "use-connect-mcp-instead-of-legacy-platform-mcp-for-consumer-linkedin-c"
4253 - ],
4254 - "relatedGuides": [],
4255 - "externalResources": [],
4256 - "updatedAt": "2026-07-16",
4257 - "lastVerifiedAt": "2026-08-12",
4258 - "reviewAfter": "2026-11-10",
4259 - "freshness": "evergreen",
4260 - "state": "published",
4261 - "featured": false
4262 - },
4263 - {
4264 - "slug": "toolkits-mailchimp",
4265 - "title": "Mailchimp",
4266 - "description": "Public support knowledge for Mailchimp.",
4267 - "articlePath": "toolkits-mailchimp.md",
4268 - "sources": [
4269 - {
4270 - "sourcePath": "toolkits/mailchimp/public.md",
4271 - "sourceHeading": "Mailchimp server prefix is the URL prefix before .admin.mailchimp.com"
4272 - },
4273 - {
4274 - "sourcePath": "toolkits/mailchimp/public.md",
4275 - "sourceHeading": "Use subdomain or dc, not server_prefix, for Mailchimp connectionConfig"
4276 - },
4277 - {
4278 - "sourcePath": "toolkits/mailchimp/public.md",
4279 - "sourceHeading": "Some Mailchimp tools require at least the Mailchimp Essentials plan"
4280 - },
4281 - {
4282 - "sourcePath": "toolkits/mailchimp/public.md",
4283 - "sourceHeading": "Mailchimp Proxy Execute with raw access token also needs subdomain"
4284 - },
4285 - {
4286 - "sourcePath": "toolkits/mailchimp/public.md",
4287 - "sourceHeading": "Mailchimp has trigger support in the supported-trigger toolkit list"
4288 - }
4289 - ],
4290 - "topics": [
4291 - "authentication",
4292 - "errors-and-troubleshooting",
4293 - "sessions-and-execution",
4294 - "toolkits-and-providers"
4295 - ],
4296 - "tags": [
4297 - "for-you",
4298 - "mailchimp",
4299 - "platform"
4300 - ],
4301 - "aliases": [
4302 - "/kb/toolkits/mailchimp-troubleshooting",
4303 - "mailchimp-has-trigger-support-in-the-supported-trigger-toolkit-list",
4304 - "mailchimp-proxy-execute-with-raw-access-token-also-needs-subdomain",
4305 - "mailchimp-server-prefix-is-the-url-prefix-before-admin-mailchimp-com",
4306 - "mailchimp-troubleshooting",
4307 - "some-mailchimp-tools-require-at-least-the-mailchimp-essentials-plan",
4308 - "use-subdomain-or-dc-not-server-prefix-for-mailchimp-connectionconfig"
4309 - ],
4310 - "relatedGuides": [],
4311 - "externalResources": [],
4312 - "updatedAt": "2026-06-24",
4313 - "lastVerifiedAt": "2026-08-12",
4314 - "reviewAfter": "2026-11-10",
4315 - "freshness": "evergreen",
4316 - "state": "published",
4317 - "featured": false
4318 - },
4319 - {
4320 - "slug": "toolkits-marketstack",
4321 - "title": "Marketstack",
4322 - "description": "Public support knowledge for Marketstack.",
4323 - "articlePath": "toolkits-marketstack.md",
4324 - "sources": [
4325 - {
4326 - "sourcePath": "toolkits/marketstack/public.md",
4327 - "sourceHeading": "API Coverage"
4328 - }
4329 - ],
4330 - "topics": [
4331 - "errors-and-troubleshooting",
4332 - "sessions-and-execution",
4333 - "toolkits-and-providers"
4334 - ],
4335 - "tags": [
4336 - "for-you",
4337 - "marketstack",
4338 - "platform"
4339 - ],
4340 - "aliases": [],
4341 - "relatedGuides": [],
4342 - "externalResources": [],
4343 - "updatedAt": "2026-06-24",
4344 - "lastVerifiedAt": "2026-08-12",
4345 - "reviewAfter": "2026-11-10",
4346 - "freshness": "evergreen",
4347 - "state": "published",
4348 - "featured": false
4349 - },
4350 - {
4351 - "slug": "toolkits-microsoft-teams",
4352 - "title": "Microsoft Teams",
4353 - "description": "Public support knowledge for Microsoft Teams.",
4354 - "articlePath": "toolkits-microsoft-teams.md",
4355 - "sources": [
4356 - {
4357 - "sourcePath": "toolkits/microsoft_teams/public.md",
4358 - "sourceHeading": "Microsoft Teams delegated permissions should be checked with `get_scopes_required` and `toolkit_versions[microsoft_teams]=latest`"
4359 - },
4360 - {
4361 - "sourcePath": "toolkits/microsoft_teams/public.md",
4362 - "sourceHeading": "Invalid OAuth scope: `ChannelMessage.Read.Group`"
4363 - },
4364 - {
4365 - "sourcePath": "toolkits/microsoft_teams/public.md",
4366 - "sourceHeading": "`MICROSOFT_TEAMS_CHATS_GET_ALL_CHATS` and `MICROSOFT_TEAMS_CREATE_MEETING` can work with delegated user scopes"
4367 - },
4368 - {
4369 - "sourcePath": "toolkits/microsoft_teams/public.md",
4370 - "sourceHeading": "Microsoft Teams often needs customer-owned Azure OAuth credentials and tenant admin consent"
4371 - },
4372 - {
4373 - "sourcePath": "toolkits/microsoft_teams/public.md",
4374 - "sourceHeading": "Microsoft Teams one-on-one chat creation needs two users and correct OData bind format"
4375 - },
4376 - {
4377 - "sourcePath": "toolkits/microsoft_teams/public.md",
4378 - "sourceHeading": "Microsoft Teams MCP access is tied to the connected account `user_id` used in the MCP URL"
4379 - },
4380 - {
4381 - "sourcePath": "toolkits/microsoft_teams/public.md",
4382 - "sourceHeading": "Teams chat tools return 400/403/404 when user IDs or chat membership do not match Microsoft Graph expectations"
4383 - },
4384 - {
4385 - "sourcePath": "toolkits/microsoft_teams/public.md",
4386 - "sourceHeading": "Microsoft Teams tool listing may return only 20 tools unless `limit` is increased"
4387 - },
4388 - {
4389 - "sourcePath": "toolkits/microsoft_teams/public.md",
4390 - "sourceHeading": "Some Microsoft Teams slugs were restored as deprecated aliases with replacement descriptions"
4391 - },
4392 - {
4393 - "sourcePath": "toolkits/microsoft_teams/public.md",
4394 - "sourceHeading": "Tool Router memory for Microsoft Teams should be a list under the toolkit key"
4395 - }
4396 - ],
4397 - "topics": [
4398 - "auth-config",
4399 - "authentication",
4400 - "errors-and-troubleshooting",
4401 - "sessions-and-execution",
4402 - "toolkits-and-providers"
4403 - ],
4404 - "tags": [
4405 - "for-you",
4406 - "microsoft_teams",
4407 - "platform"
4408 - ],
4409 - "aliases": [
4410 - "/kb/toolkits/microsoft-teams-troubleshooting",
4411 - "microsoft-teams-chats-get-all-chats-and-microsoft-teams-create-meeting",
4412 - "microsoft-teams-delegated-permissions-should-be-checked-with-get-scope",
4413 - "microsoft-teams-mcp-access-is-tied-to-the-connected-account-user-id-us",
4414 - "microsoft-teams-often-needs-customer-owned-azure-oauth-credentials-and",
4415 - "microsoft-teams-one-on-one-chat-creation-needs-two-users-and-correct-o",
4416 - "microsoft-teams-tool-listing-may-return-only-20-tools-unless-limit-is",
4417 - "microsoft-teams-troubleshooting",
4418 - "some-microsoft-teams-slugs-were-restored-as-deprecated-aliases-with-re",
4419 - "teams-chat-tools-return-400-403-404-when-user-ids-or-chat-membership-d",
4420 - "tool-router-memory-for-microsoft-teams-should-be-a-list-under-the-tool"
4421 - ],
4422 - "relatedGuides": [],
4423 - "externalResources": [],
4424 - "updatedAt": "2026-06-24",
4425 - "lastVerifiedAt": "2026-08-17",
4426 - "reviewAfter": "2026-11-15",
4427 - "freshness": "evergreen",
4428 - "state": "published",
4429 - "featured": false,
4430 - "verifyIgnoreToolSlugs": [
4431 - "MICROSOFT_TEAMS_TEAMS_GET_MESSAGE"
4432 - ]
4433 - },
4434 - {
4435 - "slug": "toolkits-monday",
4436 - "title": "Monday",
4437 - "description": "Public support knowledge for Monday.",
4438 - "articlePath": "toolkits-monday.md",
4439 - "sources": [
4440 - {
4441 - "sourcePath": "toolkits/monday/public.md",
4442 - "sourceHeading": "Monday requires the OAuth app to be installed in the workspace before user connections"
4443 - },
4444 - {
4445 - "sourcePath": "toolkits/monday/public.md",
4446 - "sourceHeading": "Add the Composio redirect URL to the Monday OAuth app"
4447 - },
4448 - {
4449 - "sourcePath": "toolkits/monday/public.md",
4450 - "sourceHeading": "`MONDAY_UPDATE_ITEM` body must be passed as a properly escaped string"
4451 - },
4452 - {
4453 - "sourcePath": "toolkits/monday/public.md",
4454 - "sourceHeading": "Tool Router may prefer `MONDAY_MCP` over `MONDAY` when both are available"
4455 - },
4456 - {
4457 - "sourcePath": "toolkits/monday/public.md",
4458 - "sourceHeading": "Monday scopes come from the OAuth app and do not need separate Composio-side setup in the common flow"
4459 - },
4460 - {
4461 - "sourcePath": "toolkits/monday/public.md",
4462 - "sourceHeading": "Monday trigger management is not handled by the agent at runtime"
4463 - }
4464 - ],
4465 - "topics": [
4466 - "auth-config",
4467 - "authentication",
4468 - "errors-and-troubleshooting",
4469 - "sessions-and-execution",
4470 - "toolkits-and-providers"
4471 - ],
4472 - "tags": [
4473 - "for-you",
4474 - "monday",
4475 - "platform"
4476 - ],
4477 - "aliases": [
4478 - "/kb/toolkits/monday-troubleshooting",
4479 - "add-the-composio-redirect-url-to-the-monday-oauth-app",
4480 - "monday-requires-the-oauth-app-to-be-installed-in-the-workspace-before",
4481 - "monday-scopes-come-from-the-oauth-app-and-do-not-need-separate-composi",
4482 - "monday-troubleshooting",
4483 - "monday-update-item-body-must-be-passed-as-a-properly-escaped-string"
4484 - ],
4485 - "relatedGuides": [],
4486 - "externalResources": [],
4487 - "updatedAt": "2026-06-24",
4488 - "lastVerifiedAt": "2026-08-12",
4489 - "reviewAfter": "2026-11-10",
4490 - "freshness": "evergreen",
4491 - "state": "published",
4492 - "featured": false,
4493 - "verifyIgnoreToolSlugs": [
4494 - "MONDAY_MCP"
4495 - ]
4496 - },
4497 - {
4498 - "slug": "toolkits-netsuite",
4499 - "title": "NetSuite",
4500 - "description": "Public support knowledge for NetSuite.",
4501 - "articlePath": "toolkits-netsuite.md",
4502 - "sources": [
4503 - {
4504 - "sourcePath": "toolkits/netsuite/public.md",
4505 - "sourceHeading": "NetSuite OAuth token exchange failures can be caused by generic OAuth endpoints"
4506 - }
4507 - ],
4508 - "topics": [
4509 - "authentication",
4510 - "errors-and-troubleshooting",
4511 - "toolkits-and-providers"
4512 - ],
4513 - "tags": [
4514 - "for-you",
4515 - "netsuite",
4516 - "platform"
4517 - ],
4518 - "aliases": [
4519 - "/kb/toolkits/netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth",
4520 - "netsuite-oauth-token-exchange-failures-can-be-caused-by-generic-oauth"
4521 - ],
4522 - "relatedGuides": [],
4523 - "externalResources": [],
4524 - "updatedAt": "2026-06-24",
4525 - "lastVerifiedAt": "2026-08-12",
4526 - "reviewAfter": "2026-11-10",
4527 - "freshness": "evergreen",
4528 - "state": "published",
4529 - "featured": false
4530 - },
4531 - {
4532 - "slug": "toolkits-notion",
4533 - "title": "Notion",
4534 - "description": "Public support knowledge for Notion.",
4535 - "articlePath": "toolkits-notion.md",
4536 - "sources": [
4537 - {
4538 - "sourcePath": "toolkits/notion/public.md",
4539 - "sourceHeading": "Use `NOTION_RETRIEVE_PAGE` instead of deprecated/invalid `NOTION_GET_PAGE`"
4540 - },
4541 - {
4542 - "sourcePath": "toolkits/notion/public.md",
4543 - "sourceHeading": "Use the current Notion page and data-source update triggers"
4544 - },
4545 - {
4546 - "sourcePath": "toolkits/notion/public.md",
4547 - "sourceHeading": "Notion page/database access is granted per integration, not per Composio auth config token"
4548 - },
4549 - {
4550 - "sourcePath": "toolkits/notion/public.md",
4551 - "sourceHeading": "Specifying a different auth config affects get/use lookup, not existing Notion token refresh"
4552 - },
4553 - {
4554 - "sourcePath": "toolkits/notion/public.md",
4555 - "sourceHeading": "Notion 401 can be caused by invalid refresh token after user/admin revokes integration"
4556 - },
4557 - {
4558 - "sourcePath": "toolkits/notion/public.md",
4559 - "sourceHeading": "Use `NOTION_FETCH_DATA`, not `NOTION_FETCH_NOTION_DATA`"
4560 - },
4561 - {
4562 - "sourcePath": "toolkits/notion/public.md",
4563 - "sourceHeading": "Large unfiltered Notion responses can hurt agent quality"
4564 - }
4565 - ],
4566 - "topics": [
4567 - "auth-config",
4568 - "authentication",
4569 - "errors-and-troubleshooting",
4570 - "sessions-and-execution",
4571 - "toolkits-and-providers"
4572 - ],
4573 - "tags": [
4574 - "for-you",
4575 - "notion",
4576 - "platform"
4577 - ],
4578 - "aliases": [
4579 - "/kb/toolkits/notion-troubleshooting",
4580 - "large-unfiltered-notion-responses-can-hurt-agent-quality",
4581 - "notion-401-can-be-caused-by-invalid-refresh-token-after-user-admin-rev",
4582 - "notion-database-trigger-fires-for-new-pages-not-updates",
4583 - "notion-page-database-access-is-granted-per-integration-not-per-composi",
4584 - "notion-troubleshooting",
4585 - "repeated-notion-reconnect-loops-may-be-a-rotating-refresh-token-issue",
4586 - "specifying-a-different-auth-config-affects-get-use-lookup-not-existing"
4587 - ],
4588 - "relatedGuides": [],
4589 - "externalResources": [],
4590 - "updatedAt": "2026-07-16",
4591 - "lastVerifiedAt": "2026-08-17",
4592 - "reviewAfter": "2026-11-15",
4593 - "freshness": "evergreen",
4594 - "state": "published",
4595 - "featured": false,
4596 - "verifyIgnoreToolSlugs": [
4597 - "NOTION_GET_PAGE",
4598 - "NOTION_FETCH_NOTION_DATA"
4599 - ]
4600 - },
4601 - {
4602 - "slug": "toolkits-odoo",
4603 - "title": "Odoo",
4604 - "description": "Public troubleshooting guidance for Odoo tools.",
4605 - "articlePath": "toolkits-odoo.md",
4606 - "sources": [
4607 - {
4608 - "sourcePath": "toolkits/odoo/public.md",
4609 - "sourceHeading": "JSON-RPC access errors can arrive inside HTTP 200 responses"
4610 - }
4611 - ],
4612 - "topics": [
4613 - "errors-and-troubleshooting",
4614 - "sessions-and-execution",
4615 - "toolkits-and-providers"
4616 - ],
4617 - "tags": [
4618 - "for-you",
4619 - "json-rpc",
4620 - "odoo",
4621 - "platform"
4622 - ],
4623 - "aliases": [
4624 - "/kb/toolkits/inspect-odoo-json-rpc-errors-inside-http-200-responses",
4625 - "inspect-odoo-json-rpc-errors-inside-http-200-responses"
4626 - ],
4627 - "relatedGuides": [],
4628 - "externalResources": [],
4629 - "updatedAt": "2026-07-16",
4630 - "lastVerifiedAt": "2026-08-12",
4631 - "reviewAfter": "2026-11-10",
4632 - "freshness": "evergreen",
4633 - "state": "published",
4634 - "featured": false
4635 - },
4636 - {
4637 - "slug": "toolkits-one-drive",
4638 - "title": "OneDrive",
4639 - "description": "Public support knowledge for OneDrive.",
4640 - "articlePath": "toolkits-one-drive.md",
4641 - "sources": [
4642 - {
4643 - "sourcePath": "toolkits/one_drive/public.md",
4644 - "sourceHeading": "OneDrive custom OAuth issues usually require verifying Azure app setup and recreating the integration"
4645 - },
4646 - {
4647 - "sourcePath": "toolkits/one_drive/public.md",
4648 - "sourceHeading": "Use the scopes-required endpoint to derive OneDrive/Microsoft Graph permissions"
4649 - },
4650 - {
4651 - "sourcePath": "toolkits/one_drive/public.md",
4652 - "sourceHeading": "Pass `version=latest` if OneDrive folder/list behavior looks stale"
4653 - },
4654 - {
4655 - "sourcePath": "toolkits/one_drive/public.md",
4656 - "sourceHeading": "Use file-uploadable or base64-compatible inputs for supported OneDrive actions"
4657 - },
4658 - {
4659 - "sourcePath": "toolkits/one_drive/public.md",
4660 - "sourceHeading": "Tool Router v2 sessions should keep all connected accounts under the same `user_id`"
4661 - },
4662 - {
4663 - "sourcePath": "toolkits/one_drive/public.md",
4664 - "sourceHeading": "Disable OneDrive destructive actions with `destructiveHint` or explicit tool disables"
4665 - }
4666 - ],
4667 - "topics": [
4668 - "auth-config",
4669 - "authentication",
4670 - "errors-and-troubleshooting",
4671 - "sessions-and-execution",
4672 - "toolkits-and-providers"
4673 - ],
4674 - "tags": [
4675 - "for-you",
4676 - "one_drive",
4677 - "platform"
4678 - ],
4679 - "aliases": [
4680 - "/kb/toolkits/onedrive-troubleshooting",
4681 - "deleting-a-onedrive-connection-may-not-revoke-provider-side-tokens",
4682 - "disable-onedrive-destructive-actions-with-destructivehint-or-explicit",
4683 - "onedrive-custom-oauth-issues-usually-require-verifying-azure-app-setup",
4684 - "onedrive-troubleshooting",
4685 - "tool-router-v2-sessions-should-keep-all-connected-accounts-under-the-s",
4686 - "use-the-scopes-required-endpoint-to-derive-onedrive-microsoft-graph-pe"
4687 - ],
4688 - "relatedGuides": [],
4689 - "externalResources": [],
4690 - "updatedAt": "2026-06-24",
4691 - "lastVerifiedAt": "2026-08-17",
4692 - "reviewAfter": "2026-11-15",
4693 - "freshness": "evergreen",
4694 - "state": "published",
4695 - "featured": false
4696 - },
4697 - {
4698 - "slug": "toolkits-onenote",
4699 - "title": "Microsoft OneNote",
4700 - "description": "Current authentication setup for the Microsoft OneNote toolkit.",
4701 - "articlePath": "toolkits-onenote.md",
4702 - "sources": [
4703 - {
4704 - "sourcePath": "toolkits/onenote/public.md",
4705 - "sourceHeading": "OneNote uses a customer-owned Microsoft OAuth app"
4706 - }
4707 - ],
4708 - "topics": [
4709 - "auth-config",
4710 - "authentication",
4711 - "toolkits-and-providers"
4712 - ],
4713 - "tags": [
4714 - "for-you",
4715 - "microsoft",
4716 - "onenote",
4717 - "platform"
4718 - ],
4719 - "aliases": [],
4720 - "relatedGuides": [],
4721 - "externalResources": [],
4722 - "updatedAt": "2026-08-17",
4723 - "lastVerifiedAt": "2026-08-17",
4724 - "reviewAfter": "2026-11-15",
4725 - "freshness": "evergreen",
4726 - "state": "published",
4727 - "featured": false
4728 - },
4729 - {
4730 - "slug": "toolkits-openai",
4731 - "title": "OpenAI",
4732 - "description": "Public support knowledge for OpenAI.",
4733 - "articlePath": "toolkits-openai.md",
4734 - "sources": [
4735 - {
4736 - "sourcePath": "toolkits/openai/public.md",
4737 - "sourceHeading": "`OPENAI_CREATE_IMAGE` supports `gpt-image-2` in the latest toolkit version"
4738 - },
4739 - {
4740 - "sourcePath": "toolkits/openai/public.md",
4741 - "sourceHeading": "Use `OpenAIAgentsProvider` when wiring Composio tools into OpenAI Agents"
4742 - },
4743 - {
4744 - "sourcePath": "toolkits/openai/public.md",
4745 - "sourceHeading": "Pin auth config and connected account IDs in Tool Router sessions when a specific connection must be used"
4746 - },
4747 - {
4748 - "sourcePath": "toolkits/openai/public.md",
4749 - "sourceHeading": "Use `beforeExecute` modifiers to add a human approval layer before tool execution"
4750 - },
4751 - {
4752 - "sourcePath": "toolkits/openai/public.md",
4753 - "sourceHeading": "Provider/schema compatibility errors often require upgrading Composio SDK packages together"
4754 - }
4755 - ],
4756 - "topics": [
4757 - "auth-config",
4758 - "authentication",
4759 - "errors-and-troubleshooting",
4760 - "sessions-and-execution",
4761 - "toolkits-and-providers"
4762 - ],
4763 - "tags": [
4764 - "for-you",
4765 - "openai",
4766 - "platform"
4767 - ],
4768 - "aliases": [
4769 - "/kb/toolkits/openai-troubleshooting",
4770 - "append-session-experimental-assistiveprompt-when-gpt-models-are-flaky",
4771 - "openai-create-image-supports-gpt-image-2-in-the-latest-toolkit-version",
4772 - "openai-troubleshooting",
4773 - "pin-auth-config-and-connected-account-ids-in-tool-router-sessions-when",
4774 - "provider-schema-bugs-often-require-upgrading-composio-sdk-packages-tog",
4775 - "use-beforeexecute-modifiers-to-add-a-human-approval-layer-before-tool",
4776 - "use-openaiagentsprovider-when-wiring-composio-tools-into-openai-agents"
4777 - ],
4778 - "relatedGuides": [],
4779 - "externalResources": [],
4780 - "updatedAt": "2026-06-24",
4781 - "lastVerifiedAt": "2026-08-17",
4782 - "reviewAfter": "2026-11-15",
4783 - "freshness": "evergreen",
4784 - "state": "published",
4785 - "featured": false
4786 - },
4787 - {
4788 - "slug": "toolkits-outlook",
4789 - "title": "Outlook",
4790 - "description": "Public support knowledge for Outlook.",
4791 - "articlePath": "toolkits-outlook.md",
4792 - "sources": [
4793 - {
4794 - "sourcePath": "toolkits/outlook/public.md",
4795 - "sourceHeading": "Outlook desktop users still need to authenticate the cloud Microsoft account in browser"
4796 - },
4797 - {
4798 - "sourcePath": "toolkits/outlook/public.md",
4799 - "sourceHeading": "Connect MCP exposes meta-tools, not individual Outlook tools, by design"
4800 - },
4801 - {
4802 - "sourcePath": "toolkits/outlook/public.md",
4803 - "sourceHeading": "For Outlook shared mailboxes, pass the shared mailbox address as `user_id`/mailbox target"
4804 - },
4805 - {
4806 - "sourcePath": "toolkits/outlook/public.md",
4807 - "sourceHeading": "Remove obsolete or invalid Outlook tool slugs from MCP configs and patch `allowed_tools`"
4808 - },
4809 - {
4810 - "sourcePath": "toolkits/outlook/public.md",
4811 - "sourceHeading": "Outlook multi-account sessions require explicit per-call `account` selection and aliases"
4812 - },
4813 - {
4814 - "sourcePath": "toolkits/outlook/public.md",
4815 - "sourceHeading": "Use `get_scopes_required` with Outlook tool slugs, then refresh/reconnect after scope changes"
4816 - },
4817 - {
4818 - "sourcePath": "toolkits/outlook/public.md",
4819 - "sourceHeading": "Outlook/Microsoft apps may need admin consent from App Registration or Enterprise Applications"
4820 - },
4821 - {
4822 - "sourcePath": "toolkits/outlook/public.md",
4823 - "sourceHeading": "Outlook/Gmail email attachments through SDK should be passed as file paths"
4824 - },
4825 - {
4826 - "sourcePath": "toolkits/outlook/public.md",
4827 - "sourceHeading": "Incomplete Outlook auth links expire after about 10 minutes and mark the connection `EXPIRED`"
4828 - }
4829 - ],
4830 - "topics": [
4831 - "auth-config",
4832 - "authentication",
4833 - "errors-and-troubleshooting",
4834 - "sessions-and-execution",
4835 - "toolkits-and-providers"
4836 - ],
4837 - "tags": [
4838 - "for-you",
4839 - "outlook",
4840 - "platform"
4841 - ],
4842 - "aliases": [
4843 - "/kb/authentication/outlook-troubleshooting",
4844 - "an-active-outlook-connection-can-have-a-disabled-webhook-trigger",
4845 - "connect-mcp-exposes-meta-tools-not-individual-outlook-tools-by-design",
4846 - "incomplete-outlook-auth-links-expire-after-about-10-minutes-and-mark-t",
4847 - "outlook-desktop-users-still-need-to-authenticate-the-cloud-microsoft-a",
4848 - "outlook-email-categories-and-send-draft-pin-email-support-may-need-too",
4849 - "outlook-gmail-email-attachments-through-sdk-should-be-passed-as-file-p",
4850 - "outlook-microsoft-apps-may-need-admin-consent-from-app-registration-or",
4851 - "outlook-multi-account-sessions-require-explicit-per-call-account-selec",
4852 - "outlook-troubleshooting",
4853 - "remove-old-bad-outlook-tool-slugs-from-mcp-configs-and-patch-allowed-t",
4854 - "target-outlook-shared-mailboxes-by-address",
4855 - "use-get-scopes-required-with-outlook-tool-slugs-then-refresh-reconnect"
4856 - ],
4857 - "relatedGuides": [],
4858 - "externalResources": [],
4859 - "updatedAt": "2026-07-16",
4860 - "lastVerifiedAt": "2026-08-17",
4861 - "reviewAfter": "2026-11-15",
4862 - "freshness": "evergreen",
4863 - "state": "published",
4864 - "featured": false
4865 - },
4866 - {
4867 - "slug": "toolkits-perplexityai",
4868 - "title": "Perplexity AI authentication",
4869 - "description": "Current API-key setup for the Perplexity AI toolkit.",
4870 - "articlePath": "toolkits-perplexityai.md",
4871 - "sources": [
4872 - {
4873 - "sourcePath": "toolkits/perplexityai/public.md",
4874 - "sourceHeading": "Perplexity AI uses the `generic_api_key` connection field"
4875 - }
4876 - ],
4877 - "topics": [
4878 - "authentication",
4879 - "errors-and-troubleshooting",
4880 - "toolkits-and-providers"
4881 - ],
4882 - "tags": [
4883 - "for-you",
4884 - "perplexityai",
4885 - "platform"
4886 - ],
4887 - "aliases": [],
4888 - "relatedGuides": [],
4889 - "externalResources": [],
4890 - "updatedAt": "2026-08-17",
4891 - "lastVerifiedAt": "2026-08-17",
4892 - "reviewAfter": "2026-11-15",
4893 - "freshness": "evergreen",
4894 - "state": "published",
4895 - "featured": false
4896 - },
4897 - {
4898 - "slug": "toolkits-pipedrive",
4899 - "title": "Pipedrive",
4900 - "description": "Public support knowledge for Pipedrive.",
4901 - "articlePath": "toolkits-pipedrive.md",
4902 - "sources": [
4903 - {
4904 - "sourcePath": "toolkits/pipedrive/public.md",
4905 - "sourceHeading": "Pipedrive requires custom OAuth or API-key credentials"
4906 - },
4907 - {
4908 - "sourcePath": "toolkits/pipedrive/public.md",
4909 - "sourceHeading": "Pipedrive OAuth initiation requires the workspace subdomain"
4910 - },
4911 - {
4912 - "sourcePath": "toolkits/pipedrive/public.md",
4913 - "sourceHeading": "Do not install the Pipedrive app directly from Pipedrive OAuth settings"
4914 - },
4915 - {
4916 - "sourcePath": "toolkits/pipedrive/public.md",
4917 - "sourceHeading": "Hosted auth links can collect Pipedrive required fields"
4918 - },
4919 - {
4920 - "sourcePath": "toolkits/pipedrive/public.md",
4921 - "sourceHeading": "Pass `callback_url` when initiating Pipedrive auth to redirect users after authentication"
4922 - },
4923 - {
4924 - "sourcePath": "toolkits/pipedrive/public.md",
4925 - "sourceHeading": "Pipedrive has trigger support"
4926 - }
4927 - ],
4928 - "topics": [
4929 - "auth-config",
4930 - "authentication",
4931 - "sessions-and-execution",
4932 - "toolkits-and-providers"
4933 - ],
4934 - "tags": [
4935 - "for-you",
4936 - "pipedrive",
4937 - "platform"
4938 - ],
4939 - "aliases": [
4940 - "/kb/toolkits/pipedrive-troubleshooting",
4941 - "claude-may-block-pipedrive-because-payment-processing-toolkits-are-res",
4942 - "do-not-install-the-pipedrive-app-directly-from-pipedrive-oauth-setting",
4943 - "hosted-auth-links-can-collect-pipedrive-required-fields",
4944 - "pass-callback-url-when-initiating-pipedrive-auth-to-redirect-users-aft",
4945 - "pipedrive-oauth-initiation-requires-the-workspace-subdomain",
4946 - "pipedrive-troubleshooting",
4947 - "use-custom-credentials-or-api-key-when-composio-s-default-pipedrive-oa"
4948 - ],
4949 - "relatedGuides": [],
4950 - "externalResources": [],
4951 - "updatedAt": "2026-06-24",
4952 - "lastVerifiedAt": "2026-08-24",
4953 - "reviewAfter": "2026-11-22",
4954 - "freshness": "evergreen",
4955 - "state": "published",
4956 - "featured": false
4957 - },
4958 - {
4959 - "slug": "toolkits-posthog",
4960 - "title": "PostHog",
4961 - "description": "Public support knowledge for PostHog.",
4962 - "articlePath": "toolkits-posthog.md",
4963 - "sources": [
4964 - {
4965 - "sourcePath": "toolkits/posthog/public.md",
4966 - "sourceHeading": "PostHog is API-key based; use the PostHog API key when creating the connection"
4967 - },
4968 - {
4969 - "sourcePath": "toolkits/posthog/public.md",
4970 - "sourceHeading": "Configure PostHog subdomain for EU or self-hosted instances"
4971 - },
4972 - {
4973 - "sourcePath": "toolkits/posthog/public.md",
4974 - "sourceHeading": "Pass auth config into Tool Router sessions; platform-created auth configs are not automatically usable"
4975 - },
4976 - {
4977 - "sourcePath": "toolkits/posthog/public.md",
4978 - "sourceHeading": "Create a PostHog integration/auth config before expecting it in auth_configs API results"
4979 - },
4980 - {
4981 - "sourcePath": "toolkits/posthog/public.md",
4982 - "sourceHeading": "Fetch PostHog tool schema to see required fields for a tool call"
4983 - }
4984 - ],
4985 - "topics": [
4986 - "auth-config",
4987 - "authentication",
4988 - "errors-and-troubleshooting",
4989 - "sessions-and-execution",
4990 - "toolkits-and-providers"
4991 - ],
4992 - "tags": [
4993 - "for-you",
4994 - "platform",
4995 - "posthog"
4996 - ],
4997 - "aliases": [
4998 - "/kb/toolkits/posthog-troubleshooting",
4999 - "api-key-connections-may-show-active-without-live-credential-validation",
5000 - "configure-posthog-subdomain-for-eu-or-self-hosted-instances",
5001 - "create-a-posthog-integration-auth-config-before-expecting-it-in-auth-c",
5002 - "fetch-posthog-tool-schema-to-see-required-fields-for-a-tool-call",
5003 - "pass-auth-config-into-tool-router-sessions-platform-created-auth-confi",
5004 - "posthog-is-api-key-based-use-the-posthog-api-key-when-creating-the-con",
5005 - "posthog-troubleshooting"
5006 - ],
5007 - "relatedGuides": [],
5008 - "externalResources": [],
5009 - "updatedAt": "2026-06-24",
5010 - "lastVerifiedAt": "2026-08-17",
5011 - "reviewAfter": "2026-11-15",
5012 - "freshness": "evergreen",
5013 - "state": "published",
5014 - "featured": false
5015 - },
5016 - {
5017 - "slug": "toolkits-quickbooks",
5018 - "title": "QuickBooks",
5019 - "description": "Public support knowledge for QuickBooks.",
5020 - "articlePath": "toolkits-quickbooks.md",
5021 - "sources": [
5022 - {
5023 - "sourcePath": "toolkits/quickbooks/public.md",
5024 - "sourceHeading": "Use the sandbox QuickBooks API base URL for sandbox connections"
5025 - },
5026 - {
5027 - "sourcePath": "toolkits/quickbooks/public.md",
5028 - "sourceHeading": "QuickBooks auth configs need QuickBooks credentials and matching redirect URL"
5029 - },
5030 - {
5031 - "sourcePath": "toolkits/quickbooks/public.md",
5032 - "sourceHeading": "QuickBooks auth can accept custom auth and token URLs for sandbox/custom flows"
5033 - },
5034 - {
5035 - "sourcePath": "toolkits/quickbooks/public.md",
5036 - "sourceHeading": "QuickBooks payment scope requires payment module access"
5037 - },
5038 - {
5039 - "sourcePath": "toolkits/quickbooks/public.md",
5040 - "sourceHeading": "Realm ID mapping fixes may require the latest QuickBooks toolkit version"
5041 - },
5042 - {
5043 - "sourcePath": "toolkits/quickbooks/public.md",
5044 - "sourceHeading": "Multiple QuickBooks accounts can be selected in Claude/MCP by using separate user IDs or connected account IDs"
5045 - },
5046 - {
5047 - "sourcePath": "toolkits/quickbooks/public.md",

This file is too large to show in full.

docs/lib/kb/repository.ts
+22 -3
@@ -1,12 +1,31 @@
1 -import { lstatSync, readFileSync, realpathSync, statSync } from 'node:fs';
1 +import { lstatSync, readdirSync, readFileSync, realpathSync, statSync } from 'node:fs';
2 import { dirname, isAbsolute, join, relative, resolve, sep } from 'node:path';
3 import { buildKbCatalog } from './catalog';
4 -import type { KbCatalog, KbGuide, KbManifest } from './types';
4 +import type { KbCatalog, KbGuide, KbGuideDefinition, KbManifest } from './types';
5
6 const KB_ROOT = join(process.cwd(), 'kb');
7 const KB_ARTICLES_ROOT = resolve(KB_ROOT, 'articles');
8 let cachedCatalog: KbCatalog | null = null;
9
10 +/**
11 + * Read the manifest (`kb/manifest.json`: schema version and topics) plus one
12 + * definition per guide (`kb/guides/<slug>.json`). Guides live in their own files
13 + * so publication PRs for different guides never touch the same file.
14 + */
15 +export function readKbManifest(kbRoot = KB_ROOT): KbManifest {
16 + const base = JSON.parse(readFileSync(join(kbRoot, 'manifest.json'), 'utf8')) as Omit<KbManifest, 'guides'>;
17 + const guidesRoot = join(kbRoot, 'guides');
18 + const guides = readdirSync(guidesRoot)
19 + .filter(name => name.endsWith('.json'))
20 + .sort()
21 + .map(name => {
22 + const guide = JSON.parse(readFileSync(join(guidesRoot, name), 'utf8')) as KbGuideDefinition;
23 + if (`${guide.slug}.json` !== name) throw new Error(`kb/guides/${name} defines ${guide.slug}`);
24 + return guide;
25 + });
26 + return { ...base, guides };
27 +}
28 +
29 export function createKbArticleReader(articlesRoot: string): (articlePath: string) => string {
30 return articlePath => {
31 const articlesRootStats = lstatSync(articlesRoot);
@@ -84,7 +103,7 @@ export function createKbSourceReader(sourceRoot: string): (sourcePath: string) =
103
104 export function getKbCatalog(): KbCatalog {
105 if (cachedCatalog) return cachedCatalog;
87 - const manifest = JSON.parse(readFileSync(join(KB_ROOT, 'manifest.json'), 'utf8')) as KbManifest;
106 + const manifest = readKbManifest();
107 cachedCatalog = buildKbCatalog(
108 manifest,
109 createKbSourceReader(resolve(KB_ROOT, 'source')),
docs/lib/kb/support-knowledge.ts deleted
-593
@@ -1,593 +0,0 @@
1 -import {
2 - cpSync,
3 - existsSync,
4 - lstatSync,
5 - mkdirSync,
6 - mkdtempSync,
7 - readdirSync,
8 - readFileSync,
9 - renameSync,
10 - rmSync,
11 - writeFileSync,
12 -} from 'node:fs';
13 -import { createHash } from 'node:crypto';
14 -import { spawnSync } from 'node:child_process';
15 -import { basename, dirname, join, parse, relative, resolve } from 'node:path';
16 -import type {
17 - KbFreshness,
18 - KbGuideDefinition,
19 - KbManifest,
20 - KbTopic,
21 -} from './types';
22 -
23 -const SOURCE_REPOSITORY = 'ComposioHQ/support-knowledge';
24 -const LEAF_FILENAMES = new Set(['public.md', 'customer-safe.md']);
25 -const REQUIRED_SCALARS = [
26 - 'type',
27 - 'title',
28 - 'description',
29 - 'classification',
30 - 'owner',
31 - 'timestamp',
32 - 'last_reviewed',
33 - 'review_by',
34 -] as const;
35 -const REQUIRED_LISTS = ['product', 'category', 'tags'] as const;
36 -
37 -export interface SupportKnowledgeDocument {
38 - relativePath: string;
39 - type: string;
40 - title: string;
41 - description: string;
42 - classification: 'public' | 'customer-safe';
43 - products: string[];
44 - categories: string[];
45 - tags: string[];
46 - timestamp: string;
47 - lastReviewed: string;
48 - reviewBy: string;
49 - body: string;
50 - headings: string[];
51 -}
52 -
53 -export interface SupportKnowledgeSnapshot {
54 - manifest: KbManifest;
55 - sourceFiles: Map<string, string>;
56 - articleFiles: Map<string, string>;
57 -}
58 -
59 -function gitOutput(sourceRoot: string, args: string[]): string {
60 - const result = spawnSync('git', args, {
61 - cwd: sourceRoot,
62 - encoding: 'utf8',
63 - stdio: ['ignore', 'pipe', 'pipe'],
64 - });
65 - if (result.status !== 0) {
66 - const details = result.stderr.trim();
67 - throw new Error(`could not verify support-knowledge checkout${details ? `: ${details}` : ''}`);
68 - }
69 - return result.stdout.trim();
70 -}
71 -
72 -function repositoryFromRemote(remote: string): string | undefined {
73 - return remote.match(/github\.com(?::|\/)([^/]+\/[^/]+?)(?:\.git)?$/i)?.[1];
74 -}
75 -
76 -/** Verify that the imported bytes are checked out from the repository and commit we record. */
77 -export function verifySupportKnowledgeCheckout(input: {
78 - sourceRoot: string;
79 - sourceCommit: string;
80 -}): string {
81 - const dirty = gitOutput(input.sourceRoot, [
82 - 'status',
83 - '--porcelain=v1',
84 - '--untracked-files=all',
85 - ]);
86 - if (dirty) {
87 - throw new Error('support-knowledge checkout has uncommitted changes');
88 - }
89 -
90 - const ignoredKnowledgeFiles = gitOutput(input.sourceRoot, [
91 - 'ls-files',
92 - '--others',
93 - '--ignored',
94 - '--exclude-standard',
95 - '--',
96 - ':(glob)**/public.md',
97 - ':(glob)**/customer-safe.md',
98 - ]);
99 - if (ignoredKnowledgeFiles) {
100 - throw new Error('support-knowledge checkout contains ignored knowledge files');
101 - }
102 -
103 - const head = gitOutput(input.sourceRoot, ['rev-parse', 'HEAD']);
104 - const requested = gitOutput(input.sourceRoot, [
105 - 'rev-parse',
106 - '--verify',
107 - `${input.sourceCommit}^{commit}`,
108 - ]);
109 - if (head !== requested) {
110 - throw new Error(
111 - `support-knowledge HEAD ${head} does not match requested commit ${requested}`,
112 - );
113 - }
114 -
115 - const remote = gitOutput(input.sourceRoot, ['remote', 'get-url', 'origin']);
116 - const repository = repositoryFromRemote(remote);
117 - if (repository?.toLowerCase() !== SOURCE_REPOSITORY.toLowerCase()) {
118 - throw new Error(
119 - `support-knowledge origin is ${remote}; expected ${SOURCE_REPOSITORY}`,
120 - );
121 - }
122 - return head;
123 -}
124 -
125 -function sourceContentHash(sourceFiles: Map<string, string>): string {
126 - const hash = createHash('sha256');
127 - for (const [relativePath, contents] of [...sourceFiles].sort(([left], [right]) =>
128 - left.localeCompare(right))) {
129 - hash.update(relativePath, 'utf8');
130 - hash.update('\0');
131 - hash.update(contents, 'utf8');
132 - hash.update('\0');
133 - }
134 - return `sha256:${hash.digest('hex')}`;
135 -}
136 -
137 -function unquote(value: string): string {
138 - const trimmed = value.trim();
139 - if (
140 - (trimmed.startsWith('"') && trimmed.endsWith('"')) ||
141 - (trimmed.startsWith("'") && trimmed.endsWith("'"))
142 - ) {
143 - return trimmed.slice(1, -1);
144 - }
145 - return trimmed;
146 -}
147 -
148 -function parseFrontmatter(raw: string, relativePath: string): {
149 - scalars: Map<string, string>;
150 - lists: Map<string, string[]>;
151 - body: string;
152 -} {
153 - if (!raw.startsWith('---\n')) {
154 - throw new Error(`${relativePath}: missing YAML frontmatter`);
155 - }
156 - const closing = raw.indexOf('\n---\n', 4);
157 - if (closing < 0) throw new Error(`${relativePath}: YAML frontmatter is not closed`);
158 -
159 - const scalars = new Map<string, string>();
160 - const lists = new Map<string, string[]>();
161 - let activeList: string | null = null;
162 -
163 - for (const line of raw.slice(4, closing).split('\n')) {
164 - const listItem = line.match(/^\s+-\s+(.+)$/);
165 - if (listItem && activeList) {
166 - lists.get(activeList)?.push(unquote(listItem[1] ?? ''));
167 - continue;
168 - }
169 -
170 - const field = line.match(/^([A-Za-z0-9_-]+):\s*(.*)$/);
171 - if (!field) continue;
172 - const key = field[1] ?? '';
173 - const value = field[2] ?? '';
174 - if ((REQUIRED_LISTS as readonly string[]).includes(key)) {
175 - lists.set(key, []);
176 - activeList = key;
177 - continue;
178 - }
179 - scalars.set(key, unquote(value));
180 - activeList = null;
181 - }
182 -
183 - return { scalars, lists, body: raw.slice(closing + 5).trim() };
184 -}
185 -
186 -function requiredScalar(values: Map<string, string>, key: string, path: string): string {
187 - const value = values.get(key)?.trim();
188 - if (!value) throw new Error(`${path}: missing frontmatter field ${key}`);
189 - return value;
190 -}
191 -
192 -function requiredList(values: Map<string, string[]>, key: string, path: string): string[] {
193 - const value = values.get(key)?.map(item => item.trim()).filter(Boolean) ?? [];
194 - if (value.length === 0) throw new Error(`${path}: frontmatter field ${key} must be a list`);
195 - return value;
196 -}
197 -
198 -function validateIsoDate(value: string, key: string, path: string): void {
199 - if (!/^\d{4}-\d{2}-\d{2}$/.test(value) || Number.isNaN(new Date(`${value}T00:00:00Z`).valueOf())) {
200 - throw new Error(`${path}: ${key} must be YYYY-MM-DD`);
201 - }
202 -}
203 -
204 -function leafClassification(
205 - scalars: Map<string, string>,
206 - relativePath: string,
207 -): 'public' | 'customer-safe' {
208 - const classification = requiredScalar(scalars, 'classification', relativePath);
209 - if (classification !== 'public' && classification !== 'customer-safe') {
210 - throw new Error(`${relativePath}: unsupported classification ${classification}`);
211 - }
212 - const expectedClassification = basename(relativePath) === 'public.md'
213 - ? 'public'
214 - : basename(relativePath) === 'customer-safe.md'
215 - ? 'customer-safe'
216 - : null;
217 - if (!expectedClassification || classification !== expectedClassification) {
218 - throw new Error(`${relativePath}: classification does not match filename`);
219 - }
220 - return classification;
221 -}
222 -
223 -export function parseSupportKnowledgeDocument(
224 - raw: string,
225 - relativePath: string,
226 -): SupportKnowledgeDocument {
227 - const { scalars, lists, body } = parseFrontmatter(raw, relativePath);
228 - for (const key of REQUIRED_SCALARS) requiredScalar(scalars, key, relativePath);
229 - const classification = leafClassification(scalars, relativePath);
230 -
231 - const lastReviewed = requiredScalar(scalars, 'last_reviewed', relativePath);
232 - const reviewBy = requiredScalar(scalars, 'review_by', relativePath);
233 - validateIsoDate(lastReviewed, 'last_reviewed', relativePath);
234 - validateIsoDate(reviewBy, 'review_by', relativePath);
235 -
236 - const levelOneHeadings = [...body.matchAll(/^#\s+(.+?)\s*$/gm)];
237 - if (levelOneHeadings.length !== 1) {
238 - throw new Error(`${relativePath}: requires exactly one level-one title`);
239 - }
240 -
241 - const sections = [...body.matchAll(/^##\s+(.+?)\s*$\n([\s\S]*?)(?=^##\s+|\s*$)/gm)];
242 - if (sections.length === 0) {
243 - throw new Error(`${relativePath}: requires at least one level-two answer section`);
244 - }
245 - for (const section of sections) {
246 - if (!(section[2] ?? '').trim()) {
247 - throw new Error(`${relativePath}: level-two answer section "${section[1]}" is empty`);
248 - }
249 - }
250 -
251 - return {
252 - relativePath,
253 - type: requiredScalar(scalars, 'type', relativePath),
254 - title: requiredScalar(scalars, 'title', relativePath),
255 - description: requiredScalar(scalars, 'description', relativePath),
256 - classification,
257 - products: requiredList(lists, 'product', relativePath),
258 - categories: requiredList(lists, 'category', relativePath),
259 - tags: requiredList(lists, 'tags', relativePath),
260 - timestamp: requiredScalar(scalars, 'timestamp', relativePath),
261 - lastReviewed,
262 - reviewBy,
263 - body,
264 - headings: sections.map(section => (section[1] ?? '').trim()),
265 - };
266 -}
267 -
268 -function discoverLeaves(root: string): string[] {
269 - const visit = (directory: string): string[] => readdirSync(directory, { withFileTypes: true })
270 - .flatMap(entry => {
271 - const path = join(directory, entry.name);
272 - if (entry.isDirectory()) return visit(path);
273 - return entry.isFile() && LEAF_FILENAMES.has(entry.name) ? [path] : [];
274 - });
275 - return visit(root).sort();
276 -}
277 -
278 -function slugify(value: string): string {
279 - return value
280 - .toLowerCase()
281 - .replace(/\.md$/i, '')
282 - .replace(/[_/]+/g, '-')
283 - .replace(/[^a-z0-9-]+/g, '-')
284 - .replace(/-+/g, '-')
285 - .replace(/^-|-$/g, '');
286 -}
287 -
288 -function titleize(value: string): string {
289 - return value
290 - .split('-')
291 - .filter(Boolean)
292 - .map(part => part.charAt(0).toUpperCase() + part.slice(1))
293 - .join(' ');
294 -}
295 -
296 -function articleBody(body: string): string {
297 - const lines = body.split('\n');
298 - const titleIndex = lines.findIndex(line => /^#\s+/.test(line));
299 - if (titleIndex >= 0) lines.splice(titleIndex, 1);
300 - return `${lines.join('\n').trim()}\n`;
301 -}
302 -
303 -function normalizedSource(document: SupportKnowledgeDocument): string {
304 - const frontmatter = [
305 - '---',
306 - `type: ${JSON.stringify(document.type)}`,
307 - `title: ${JSON.stringify(document.title)}`,
308 - `description: ${JSON.stringify(document.description)}`,
309 - `category: ${JSON.stringify(document.categories[0])}`,
310 - 'visibility: "public"',
311 - `timestamp: ${JSON.stringify(document.timestamp)}`,
312 - 'tags:',
313 - ...document.tags.map(tag => ` - ${JSON.stringify(tag)}`),
314 - '---',
315 - ];
316 - return `${frontmatter.join('\n')}\n${document.body.trim()}\n`;
317 -}
318 -
319 -function importedFreshness(document: SupportKnowledgeDocument): KbFreshness {
320 - const reviewed = new Date(`${document.lastReviewed}T00:00:00Z`).valueOf();
321 - const reviewBy = new Date(`${document.reviewBy}T00:00:00Z`).valueOf();
322 - const days = (reviewBy - reviewed) / 86_400_000;
323 - return days <= 45 ? 'time-sensitive' : 'evergreen';
324 -}
325 -
326 -function topicDefinitions(
327 - documents: SupportKnowledgeDocument[],
328 - previousManifest: KbManifest | undefined,
329 -): KbTopic[] {
330 - const previous = new Map(previousManifest?.topics.map(topic => [topic.slug, topic]) ?? []);
331 - const categorySlugs = new Set(documents.flatMap(document => document.categories));
332 - return [...categorySlugs]
333 - .sort()
334 - .map((slug, index) => previous.get(slug) ?? {
335 - slug,
336 - title: titleize(slug),
337 - description: `Support guidance for ${titleize(slug).toLowerCase()}.`,
338 - featuredRank: index + 1,
339 - });
340 -}
341 -
342 -function previousAliasesBySource(
343 - documents: SupportKnowledgeDocument[],
344 - previousManifest: KbManifest | undefined,
345 -): Map<string, string[]> {
346 - const currentPaths = new Set(documents.map(document => document.relativePath));
347 - const isInitialSupportImport =
348 - previousManifest?.source.repository !== SOURCE_REPOSITORY;
349 - const aliases = new Map<string, string[]>();
350 - for (const guide of previousManifest?.guides ?? []) {
351 - const counts = new Map<string, number>();
352 - for (const source of guide.sources) {
353 - if (currentPaths.has(source.sourcePath)) {
354 - counts.set(source.sourcePath, (counts.get(source.sourcePath) ?? 0) + 1);
355 - }
356 - }
357 - const owner = [...counts].sort(([leftPath, leftCount], [rightPath, rightCount]) => {
358 - const guideIdentity = slugify(`${guide.slug}-${guide.title}`).replaceAll('-', '');
359 - const affinity = (path: string): number => {
360 - const directory = path.replace(/\/public\.md$/, '').split('/').at(-1) ?? path;
361 - const identity = slugify(directory).replaceAll('-', '');
362 - return guideIdentity.includes(identity) ? identity.length : 0;
363 - };
364 - return rightCount - leftCount || affinity(rightPath) - affinity(leftPath) ||
365 - leftPath.localeCompare(rightPath);
366 - })[0]?.[0];
367 - if (!owner) continue;
368 - const primaryTopic = guide.topics[0];
369 - const primaryPath = primaryTopic ? `/kb/${primaryTopic}/${guide.slug}` : null;
370 - aliases.set(owner, [
371 - ...(aliases.get(owner) ?? []),
372 - ...(isInitialSupportImport && primaryPath ? [primaryPath] : []),
373 - guide.slug,
374 - ...guide.aliases,
375 - ]);
376 - }
377 - return new Map([...aliases].map(([path, values]) => [path, [...new Set(values)].sort()]));
378 -}
379 -
380 -function guideFor(
381 - document: SupportKnowledgeDocument,
382 - previousAliases: string[],
383 - previousGuide?: KbGuideDefinition,
384 -): KbGuideDefinition {
385 - const slug = slugify(document.relativePath.replace(/\/public\.md$/, ''));
386 - return {
387 - slug,
388 - title: document.title,
389 - description: document.description,
390 - articlePath: `${slug}.md`,
391 - sources: document.headings.map(sourceHeading => ({
392 - sourcePath: document.relativePath,
393 - sourceHeading,
394 - })),
395 - topics: [...document.categories].sort(),
396 - tags: [...new Set([...document.tags, ...document.products])].sort(),
397 - aliases: previousAliases.filter(value => value !== slug),
398 - relatedGuides: previousGuide?.relatedGuides ?? [],
399 - externalResources: previousGuide?.externalResources ?? [],
400 - updatedAt: document.timestamp.slice(0, 10),
401 - lastVerifiedAt: document.lastReviewed,
402 - reviewAfter: document.reviewBy,
403 - freshness: importedFreshness(document),
404 - state: previousGuide?.state === 'retired' ? 'retired' : 'published',
405 - featured: previousGuide?.featured ?? false,
406 - ...(previousGuide?.verifyIgnoreToolSlugs?.length
407 - ? { verifyIgnoreToolSlugs: previousGuide.verifyIgnoreToolSlugs }
408 - : {}),
409 - };
410 -}
411 -
412 -function previousGuideForSource(
413 - document: SupportKnowledgeDocument,
414 - previousManifest: KbManifest | undefined,
415 -): KbGuideDefinition | undefined {
416 - const expectedArticlePath = `${slugify(document.relativePath.replace(/\/public\.md$/, ''))}.md`;
417 - return previousManifest?.guides
418 - .filter((guide) => guide.sources.some((source) => source.sourcePath === document.relativePath))
419 - .sort((left, right) => {
420 - const leftExact = left.articlePath === expectedArticlePath ? 1 : 0;
421 - const rightExact = right.articlePath === expectedArticlePath ? 1 : 0;
422 - return rightExact - leftExact || left.slug.localeCompare(right.slug);
423 - })[0];
424 -}
425 -
426 -export function buildSupportKnowledgeSnapshot(input: {
427 - sourceRoot: string;
428 - sourceCommit: string;
429 - previousManifest?: KbManifest;
430 - previousSourceFiles?: Map<string, string>;
431 - previousArticleFiles?: Map<string, string>;
432 - now: Date;
433 -}): SupportKnowledgeSnapshot {
434 - if (!input.sourceCommit.trim()) throw new Error('sourceCommit is required');
435 -
436 - const documents = discoverLeaves(input.sourceRoot).flatMap(path => {
437 - const relativePath = relative(input.sourceRoot, path).replace(/\\/g, '/');
438 - const raw = readFileSync(path, 'utf8');
439 - const { scalars } = parseFrontmatter(raw, relativePath);
440 - if (leafClassification(scalars, relativePath) === 'customer-safe') return [];
441 - return [parseSupportKnowledgeDocument(raw, relativePath)];
442 - });
443 - const publicDocuments = documents
444 - .sort((left, right) => left.relativePath.localeCompare(right.relativePath));
445 - if (publicDocuments.length === 0) throw new Error('support-knowledge contains no public leaves');
446 -
447 - const sourceFiles = new Map<string, string>();
448 - const articleFiles = new Map<string, string>();
449 - const previousAliases = previousAliasesBySource(publicDocuments, input.previousManifest);
450 - const portalGuides = input.previousManifest?.guides
451 - .filter(guide => guide.managedBy === 'support-portal') ?? [];
452 - const portalSlugs = new Set(portalGuides.map(guide => guide.slug));
453 - const guides = publicDocuments.filter(document => !portalSlugs.has(
454 - slugify(document.relativePath.replace(/\/public\.md$/, '')),
455 - )).map(document => {
456 - const previousGuide = previousGuideForSource(document, input.previousManifest);
457 - const source = normalizedSource(document);
458 - const sourceIsUnchanged = input.previousSourceFiles?.get(document.relativePath) === source;
459 - const previousSourceHeadings = previousGuide?.sources
460 - .filter(previousSource => previousSource.sourcePath === document.relativePath)
461 - .map(previousSource => previousSource.sourceHeading);
462 - const previousGuideMatchesSource = previousSourceHeadings !== undefined
463 - && previousSourceHeadings.length === document.headings.length
464 - && previousSourceHeadings.every((heading, index) => heading === document.headings[index]);
465 - const canReusePreviousArticle = sourceIsUnchanged && previousGuideMatchesSource;
466 - const guide = guideFor(
467 - document,
468 - previousAliases.get(document.relativePath) ?? [],
469 - previousGuide,
470 - );
471 - sourceFiles.set(document.relativePath, source);
472 - const previousArticle = previousGuide?.articlePath
473 - ? input.previousArticleFiles?.get(previousGuide.articlePath)
474 - : undefined;
475 - articleFiles.set(
476 - guide.articlePath!,
477 - canReusePreviousArticle && previousArticle !== undefined
478 - ? previousArticle
479 - : articleBody(document.body),
480 - );
481 - return guide;
482 - });
483 -
484 - // An approval takes ownership of the complete guide, including its source snapshot.
485 - // Missing bytes are an error rather than permission to discard an approved edit.
486 - for (const guide of portalGuides) {
487 - for (const reference of guide.sources) {
488 - const source = input.previousSourceFiles?.get(reference.sourcePath);
489 - if (source === undefined) throw new Error(`Missing portal source: ${reference.sourcePath}`);
490 - sourceFiles.set(reference.sourcePath, source);
491 - }
492 - if (guide.articlePath) {
493 - const article = input.previousArticleFiles?.get(guide.articlePath);
494 - if (article === undefined) throw new Error(`Missing portal article: ${guide.articlePath}`);
495 - articleFiles.set(guide.articlePath, article);
496 - }
497 - guides.push(guide);
498 - }
499 - const topics = topicDefinitions(publicDocuments, input.previousManifest);
500 - const topicSlugs = new Set(topics.map(topic => topic.slug));
501 - const portalTopics = new Set(portalGuides.flatMap(guide => guide.topics));
502 - for (const topic of input.previousManifest?.topics ?? []) {
503 - if (portalTopics.has(topic.slug) && !topicSlugs.has(topic.slug)) topics.push(topic);
504 - }
505 -
506 - return {
507 - manifest: {
508 - schemaVersion: 2,
509 - source: {
510 - repository: SOURCE_REPOSITORY,
511 - commit: input.sourceCommit.trim(),
512 - capturedAt: input.now.toISOString().slice(0, 10),
513 - contentHash: sourceContentHash(sourceFiles),
514 - },
515 - topics,
516 - guides,
517 - },
518 - sourceFiles,
519 - articleFiles,
520 - };
521 -}
522 -
523 -function writeSnapshotDirectory(snapshot: SupportKnowledgeSnapshot, root: string): void {
524 - mkdirSync(root, { recursive: true });
525 - writeFileSync(
526 - join(root, 'manifest.json'),
527 - `${JSON.stringify(snapshot.manifest, null, 2)}\n`,
528 - 'utf8',
529 - );
530 - for (const [relativePath, contents] of snapshot.sourceFiles) {
531 - const target = join(root, 'source', relativePath);
532 - mkdirSync(dirname(target), { recursive: true });
533 - writeFileSync(target, contents, 'utf8');
534 - }
535 - for (const [relativePath, contents] of snapshot.articleFiles) {
536 - const target = join(root, 'articles', relativePath);
537 - mkdirSync(dirname(target), { recursive: true });
538 - writeFileSync(target, contents, 'utf8');
539 - }
540 -}
541 -
542 -export function writeSupportKnowledgeSnapshot(input: {
543 - snapshot: SupportKnowledgeSnapshot;
544 - targetRoot: string;
545 - validate: (stagedRoot: string) => void;
546 -}): void {
547 - const targetRoot = resolve(input.targetRoot);
548 - if (targetRoot === parse(targetRoot).root) {
549 - throw new Error(`Refusing to replace unsafe snapshot path: ${targetRoot}`);
550 - }
551 -
552 - const parent = dirname(targetRoot);
553 - mkdirSync(parent, { recursive: true });
554 - const stagedRoot = mkdtempSync(join(parent, '.kb-import-'));
555 - const backupRoot = join(parent, `.kb-backup-${process.pid}-${Date.now()}`);
556 - let movedPrevious = false;
557 -
558 - try {
559 - writeSnapshotDirectory(input.snapshot, stagedRoot);
560 - const externalSources = join(targetRoot, 'external-sources');
561 - if (existsSync(externalSources)) {
562 - if (lstatSync(externalSources).isSymbolicLink()) {
563 - throw new Error('KB external-sources must not be a symbolic link');
564 - }
565 - cpSync(externalSources, join(stagedRoot, 'external-sources'), { recursive: true });
566 - }
567 - const semanticIndex = join(targetRoot, 'semantic-index.json');
568 - if (existsSync(semanticIndex)) {
569 - const semanticIndexStats = lstatSync(semanticIndex);
570 - if (semanticIndexStats.isSymbolicLink() || !semanticIndexStats.isFile()) {
571 - throw new Error('KB semantic-index.json must be a regular file');
572 - }
573 - cpSync(semanticIndex, join(stagedRoot, 'semantic-index.json'));
574 - }
575 - input.validate(stagedRoot);
576 - if (existsSync(targetRoot)) {
577 - renameSync(targetRoot, backupRoot);
578 - movedPrevious = true;
579 - }
580 - renameSync(stagedRoot, targetRoot);
581 - if (movedPrevious) rmSync(backupRoot, { recursive: true, force: true });
582 - } catch (error) {
583 - if (movedPrevious && !existsSync(targetRoot) && existsSync(backupRoot)) {
584 - renameSync(backupRoot, targetRoot);
585 - }
586 - throw error;
587 - } finally {
588 - rmSync(stagedRoot, { recursive: true, force: true });
589 - if (existsSync(backupRoot) && existsSync(targetRoot)) {
590 - rmSync(backupRoot, { recursive: true, force: true });
591 - }
592 - }
593 -}
docs/lib/kb/types.ts
-6
@@ -62,12 +62,6 @@ export interface KbGuide extends KbGuideDefinition {
62
63 export interface KbManifest {
64 schemaVersion: 2;
65 - source: {
66 - repository: string;
67 - commit: string;
68 - capturedAt: string;
69 - contentHash: string;
70 - };
65 topics: KbTopic[];
66 guides: KbGuideDefinition[];
67 }
docs/lib/kb/verify.ts
-28
@@ -24,7 +24,6 @@ export type KbVerifyKind =
24 | 'review-window-cliff'
25 | 'verification-stale'
26 | 'unreachable-link'
27 - | 'source-pin-unresolvable'
27 | 'unedited-support-prose';
28
29 /**
@@ -55,15 +54,6 @@ const SUPPORT_PROSE_PATTERNS: Array<{ label: string; pattern: RegExp }> = [
54 },
55 ];
56
58 -/**
59 - * Whether `manifest.source.commit` can be resolved on the upstream remote.
60 - *
61 - * `unverifiable` is deliberately distinct from `missing`: a token without read
62 - * access to the upstream repository cannot tell the two apart, and reporting
63 - * "provenance is broken" every run in that case would be crying wolf.
64 - */
65 -export type SourcePinStatus = 'resolved' | 'missing' | 'unverifiable';
66 -
57 export interface KbVerifyFinding {
58 severity: KbVerifySeverity;
59 kind: KbVerifyKind;
@@ -95,8 +85,6 @@ export interface KbVerifyOptions {
85 reviewCliffThreshold: number;
86 /** Resolved external link statuses, keyed by URL. Absent when `--check-links` is off. */
87 linkStatuses?: Map<string, number | 'unreachable'>;
98 - /** Upstream resolution of `manifest.source.commit`. Absent when the check is off. */
99 - sourcePinStatus?: SourcePinStatus;
88 }
89
90 export const DEFAULT_VERIFY_OPTIONS: KbVerifyOptions = {
@@ -351,22 +339,6 @@ export function verifyKb(input: KbVerifyInput): KbVerifyReport {
339 }
340 }
341
354 - // The manifest sources are vendored under kb/source, so an unresolvable pin does
355 - // not break the build — it breaks the audit trail, and it blocks source-drift
356 - // detection, which has to diff the vendored copy against the upstream commit.
357 - if (options.sourcePinStatus === 'missing') {
358 - const { repository, commit } = input.manifest.source;
359 - findings.push({
360 - severity: 'warning',
361 - kind: 'source-pin-unresolvable',
362 - guideSlug: '',
363 - detail:
364 - `${repository}@${commit} does not resolve upstream, so the provenance of ` +
365 - 'every published guide is unverifiable. Push the commit or repin the manifest.',
366 - evidence: `manifest.source.commit=${commit}`,
367 - });
368 - }
369 -
342 // A cohort of guides sharing one reviewAfter date all expire together. When that
343 // day arrives the cheap move is bulk-bumping the dates rather than re-verifying,
344 // which quietly converts the review gate into a rubber stamp.
docs/lib/knowledge/search-service.ts
-5
@@ -10,7 +10,6 @@ import {
10 type AlgoliaDocsRecord,
11 } from '@/lib/search-index';
12 import { isHiddenApiTagUrl } from '@/lib/filter-api-version';
13 -import type { KbManifest } from '@/lib/kb/types';
13 import { embedTexts, embeddingContentHash } from './embeddings';
14 import {
15 fusePublicKbCandidates,
@@ -500,9 +499,6 @@ let semanticArtifact: KnowledgeSemanticArtifact | null = null;
499
500 async function loadSemanticArtifact(): Promise<KnowledgeSemanticArtifact> {
501 if (semanticArtifact) return semanticArtifact;
503 - const manifest = JSON.parse(
504 - readFileSync(join(process.cwd(), 'kb', 'manifest.json'), 'utf8'),
505 - ) as KbManifest;
502 const artifact = JSON.parse(
503 readFileSync(join(process.cwd(), 'kb', 'semantic-index.json'), 'utf8'),
504 ) as KnowledgeSemanticArtifact;
@@ -513,7 +509,6 @@ async function loadSemanticArtifact(): Promise<KnowledgeSemanticArtifact> {
509 records.map(record => [record.objectID, embeddingContentHash(record)]),
510 );
511 semanticArtifact = validateSemanticArtifact(artifact, {
516 - supportKnowledgeCommit: manifest.source.commit,
512 docsContentHash: docsContentHashFromRecords(semanticRecords),
513 contentHashes,
514 });
docs/lib/knowledge/semantic-artifact.ts
+1 -23
@@ -46,8 +46,6 @@ export interface KnowledgeSemanticArtifact {
46 model: typeof KB_EMBEDDING_MODEL;
47 dimensions: number;
48 source: {
49 - repository: string;
50 - supportKnowledgeCommit: string;
49 docsContentHash: string;
50 };
51 builtAt: string;
@@ -143,9 +141,6 @@ export function validateSemanticArtifact(
141 artifact: KnowledgeSemanticArtifact,
142 expected: {
143 dimensions?: number;
146 - supportKnowledgeCommit?: string;
147 - /** @deprecated Use supportKnowledgeCommit. */
148 - sourceCommit?: string;
144 docsContentHash?: string;
145 contentHashes?: ReadonlyMap<string, string>;
146 },
@@ -156,9 +151,6 @@ export function validateSemanticArtifact(
151 if (artifact.dimensions !== (expected.dimensions ?? KB_EMBEDDING_DIMENSIONS)) {
152 throw new Error('Semantic artifact dimension mismatch');
153 }
159 - if (artifact.source.repository !== 'ComposioHQ/support-knowledge') {
160 - throw new Error('Semantic artifact source repository mismatch');
161 - }
154 if (artifact.records.length === 0) throw new Error('Semantic artifact has no records');
155
156 const seen = new Set<string>();
@@ -187,10 +179,6 @@ export function validateSemanticArtifact(
179 }
180 }
181 // Check integrity first so advisory freshness checks cannot hide corrupt artifacts.
190 - const supportKnowledgeCommit = expected.supportKnowledgeCommit ?? expected.sourceCommit;
191 - if (!supportKnowledgeCommit || artifact.source.supportKnowledgeCommit !== supportKnowledgeCommit) {
192 - throw new SemanticArtifactStaleError('Semantic artifact source commit mismatch');
193 - }
182 if (expected.docsContentHash && artifact.source.docsContentHash !== expected.docsContentHash) {
183 throw new SemanticArtifactStaleError('Semantic artifact docs content hash mismatch');
184 }
@@ -247,9 +235,6 @@ export function rankSemanticCandidates(
235
236 export async function buildSemanticArtifact(input: {
237 records: AlgoliaDocsRecord[];
250 - supportKnowledgeCommit?: string;
251 - /** @deprecated Use supportKnowledgeCommit. */
252 - sourceCommit?: string;
238 docsContentHash?: string;
239 builtAt: string;
240 previousArtifact?: KnowledgeSemanticArtifact;
@@ -258,8 +243,6 @@ export async function buildSemanticArtifact(input: {
243 const records = [...input.records]
244 .sort((left, right) => left.objectID.localeCompare(right.objectID));
245 const metadata = records.map(semanticRecordFromSearchRecord);
261 - const supportKnowledgeCommit = input.supportKnowledgeCommit ?? input.sourceCommit;
262 - if (!supportKnowledgeCommit) throw new Error('Semantic artifact support-knowledge commit is required');
246 const docsContentHash = input.docsContentHash ?? docsContentHashFromRecords(metadata);
247 const previousVectors = input.previousArtifact &&
248 input.previousArtifact.provider === KB_EMBEDDING_PROVIDER &&
@@ -312,17 +295,12 @@ export async function buildSemanticArtifact(input: {
295 provider: KB_EMBEDDING_PROVIDER,
296 model: KB_EMBEDDING_MODEL,
297 dimensions: KB_EMBEDDING_DIMENSIONS,
315 - source: {
316 - repository: 'ComposioHQ/support-knowledge',
317 - supportKnowledgeCommit,
318 - docsContentHash,
319 - },
298 + source: { docsContentHash },
299 builtAt: input.builtAt,
300 records: metadata,
301 vectorsBase64: encodeVectors(vectors as number[][]),
302 };
303 return validateSemanticArtifact(artifact, {
325 - supportKnowledgeCommit,
304 docsContentHash,
305 contentHashes: new Map(metadata.map(record => [record.objectID, record.contentHash])),
306 });
docs/package.json
+1 -1
@@ -11,7 +11,6 @@
11 "build:kb-semantic": "bun run generate:kb && fumadocs-mdx && bun scripts/build-kb-semantic-index.ts",
12 "check:kb-semantic": "bun run check:kb && fumadocs-mdx && bun scripts/build-kb-semantic-index.ts --check",
13 "verify:kb": "bun scripts/verify-kb.ts",
14 - "import:kb": "bun scripts/import-support-knowledge.ts",
14 "generate:kb": "bun scripts/generate-kb.ts",
15 "check:kb": "bun scripts/generate-kb.ts --check",
16 "prebuild": "bun run generate:kb && bun scripts/build-agent-index.ts && bun run build:content-freshness",
@@ -30,6 +29,7 @@
29 "eval:agent": "eve eval docs-agent --skip-report",
30 "eval:agent:flows": "bun scripts/eval-agent-flows.ts",
31 "eval:kb-search": "bun scripts/eval-kb-search.ts",
32 + "test:kb-publish": "bun tests/e2e/kb-publish.ts",
33 "generate:toolkits": "bun scripts/generate-toolkits.ts",
34 "generate:toolkit-versions": "bun scripts/refresh-toolkit-versions.ts",
35 "generate:meta-tools": "bun scripts/generate-meta-tools.ts",
docs/scripts/README.md
+1 -6
@@ -101,9 +101,4 @@ warnings too. See `docs/decisions/kb-freshness-verification.md` for what is
101 checked and why placeholders, bare URLs, and 5xx responses are excluded.
102
103 A guide that deliberately cites a removed identifier declares it in
104 -`verifyIgnoreToolSlugs` in `kb/manifest.json`.
105 -
106 -`--check-source-pin` resolves `manifest.source.commit` against the upstream KB
107 -repository. It needs `GH_TOKEN`/`GITHUB_TOKEN` with read access there; without
108 -it the check reports "unverifiable" and emits nothing, so a narrow token
109 -degrades quietly instead of reporting false provenance breakage.
104 +`verifyIgnoreToolSlugs` in its `kb/guides/<slug>.json`.
docs/scripts/build-agent-index.ts
+4 -45
@@ -19,14 +19,13 @@
19 *
20 * Run manually with `bun scripts/build-agent-index.ts`.
21 */
22 -import { resolveToolkitCount } from '../lib/toolkit-count';
23 -import { existsSync, readdirSync, readFileSync, writeFileSync } from 'node:fs';
22 +import { readdirSync, readFileSync, writeFileSync } from 'node:fs';
23 import { join, relative } from 'node:path';
24 +import { resolveToolkitCount } from '../lib/toolkit-count';
25
26 const ROOT = process.cwd();
27 const CONTENT = join(ROOT, 'content');
28 -const KNOWLEDGE_FILE = join(ROOT, 'agent', 'knowledge.md');
29 -const COLLECTIONS = ['docs', 'reference', 'examples', 'toolkits'] as const;
28 +const COLLECTIONS = ['docs', 'reference', 'examples', 'toolkits', 'kb'] as const;
29 const LEGACY_URL_PATTERNS = [
30 '/docs/tools-direct',
31 '/docs/auth-configuration',
@@ -105,6 +104,7 @@ function urlFromContentPath(absPath: string): string | undefined {
104 if (collection === 'docs') return `/docs/${parts.join('/')}`.replace(/\/index$/, '');
105 if (collection === 'examples') return `/examples/${parts.join('/')}`.replace(/\/index$/, '');
106 if (collection === 'reference') return `/reference/${parts.join('/')}`.replace(/\/index$/, '');
107 + if (collection === 'kb') return `/kb/${parts.join('/')}`.replace(/\/index$/, '');
108 if (collection === 'toolkits') {
109 if (parts[0] === 'faq') return undefined;
110 return `/toolkits/${parts.join('/')}`.replace(/\/index$/, '');
@@ -214,35 +214,6 @@ function makeSearchPage(args: {
214 };
215 }
216
217 -function loadKnowledgePages(): BundlePage[] {
218 - if (!existsSync(KNOWLEDGE_FILE)) return [];
219 -
220 - const raw = readFileSync(KNOWLEDGE_FILE, 'utf8');
221 - const pages: BundlePage[] = [];
222 - const sectionRe = /^##\s+(.+?)\s*(?:\(([^)]+)\))?\s*$/gm;
223 - const matches = [...raw.matchAll(sectionRe)];
224 -
225 - for (let index = 0; index < matches.length; index++) {
226 - const match = matches[index];
227 - const title = match[1].trim();
228 - const url = (match[2] ?? '').trim() || '/docs';
229 - const bodyStart = match.index! + match[0].length;
230 - const bodyEnd = index + 1 < matches.length ? matches[index + 1].index! : raw.length;
231 - const body = raw.slice(bodyStart, bodyEnd).trim();
232 -
233 - pages.push({
234 - collection: 'knowledge',
235 - url,
236 - title,
237 - description: '',
238 - legacy: false,
239 - markdown: body,
240 - });
241 - }
242 -
243 - return pages;
244 -}
245 -
217 function searchPageForToolkit(tk: BundleToolkit): SearchPage {
218 const name = tk.name ?? tk.slug;
219 const body = `${tk.description ?? ''} Category: ${tk.category ?? ''}. Toolkit slug: ${tk.slug}.`;
@@ -346,21 +317,9 @@ const contentSearchPages = pages.map(page =>
317 body: page.markdown,
318 })
319 );
349 -const knowledgePages = loadKnowledgePages();
350 -pages.push(...knowledgePages);
351 -const knowledgeSearchPages = knowledgePages.map(page =>
352 - makeSearchPage({
353 - collection: page.collection,
354 - title: page.title,
355 - description: page.description,
356 - url: page.url,
357 - body: page.markdown,
358 - })
359 -);
320 const toolkitSearchPages = toolkits.map(searchPageForToolkit);
321 const search = buildSearchIndex([
322 ...contentSearchPages,
363 - ...knowledgeSearchPages,
323 ...toolkitSearchPages,
324 ]);
325
docs/scripts/build-kb-semantic-index.ts
-11
@@ -10,17 +10,8 @@ import {
10 validateSemanticArtifact,
11 type KnowledgeSemanticArtifact,
12 } from '@/lib/knowledge/semantic-artifact';
13 -import type { KbManifest } from '@/lib/kb/types';
13
14 const artifactPath = join(process.cwd(), 'kb', 'semantic-index.json');
16 -const manifest = JSON.parse(
17 - readFileSync(join(process.cwd(), 'kb', 'manifest.json'), 'utf8'),
18 -) as KbManifest;
19 -if (manifest.source.repository !== 'ComposioHQ/support-knowledge') {
20 - throw new Error(
21 - `Refusing to build embeddings for transitional source ${manifest.source.repository}; import support-knowledge first`,
22 - );
23 -}
15
16 const records = (await getAlgoliaSearchDocuments())
17 .filter(record => record.source_type === 'kb' || record.source_type === 'docs')
@@ -40,7 +31,6 @@ if (process.argv.includes('--check')) {
31 const artifact = JSON.parse(readFileSync(artifactPath, 'utf8')) as KnowledgeSemanticArtifact;
32 try {
33 validateSemanticArtifact(artifact, {
43 - supportKnowledgeCommit: manifest.source.commit,
34 docsContentHash,
35 contentHashes,
36 });
@@ -64,7 +54,6 @@ const previousArtifact = existsSync(artifactPath)
54
55 const artifact = await buildSemanticArtifact({
56 records,
67 - supportKnowledgeCommit: manifest.source.commit,
57 docsContentHash,
58 builtAt: new Date().toISOString(),
59 previousArtifact,
docs/scripts/eval-kb-search.ts
-10
@@ -9,7 +9,6 @@ import {
9 } from '@/lib/knowledge/evaluation';
10 import { searchKnowledgeRecords, type KnowledgeSearchResponse } from '@/lib/knowledge/search';
11 import { getAlgoliaSearchDocuments } from '@/lib/search-index';
12 -import type { KbManifest } from '@/lib/kb/types';
12
13 function argument(name: string): string | undefined {
14 const index = process.argv.indexOf(name);
@@ -21,17 +20,8 @@ const expectedMode = argument('--expect-mode');
20 const fixturePath = argument('--fixture') ?? join(process.cwd(), 'evals', 'kb-search-v1.json');
21 const jsonOutput = process.argv.includes('--json');
22 const fixture = JSON.parse(readFileSync(fixturePath, 'utf8')) as {
24 - sourceCommit: string;
23 cases: KbSearchEvalCase[];
24 };
27 -const manifest = JSON.parse(
28 - readFileSync(join(process.cwd(), 'kb', 'manifest.json'), 'utf8'),
29 -) as KbManifest;
30 -if (fixture.sourceCommit !== manifest.source.commit) {
31 - throw new Error(
32 - `KB search eval fixture targets ${fixture.sourceCommit}, but the snapshot is ${manifest.source.commit}; review and repin the eval cases`,
33 - );
34 -}
25 const cases = fixture.cases;
26 const rankings = new Map<string, KbSearchEvalRanking[]>();
27 const observedModes = new Set<string>();
docs/scripts/import-support-knowledge.ts deleted
-77
@@ -1,77 +0,0 @@
1 -import { existsSync, readFileSync, realpathSync } from 'node:fs';
2 -import { isAbsolute, join, resolve } from 'node:path';
3 -import { buildKbCatalog } from '@/lib/kb/catalog';
4 -import {
5 - buildSupportKnowledgeSnapshot,
6 - verifySupportKnowledgeCheckout,
7 - writeSupportKnowledgeSnapshot,
8 -} from '@/lib/kb/support-knowledge';
9 -import { createKbArticleReader, createKbSourceReader } from '@/lib/kb/repository';
10 -import type { KbManifest } from '@/lib/kb/types';
11 -
12 -const args = process.argv.slice(2);
13 -
14 -function argument(name: string): string | undefined {
15 - const index = args.indexOf(name);
16 - return index >= 0 ? args[index + 1] : undefined;
17 -}
18 -
19 -const sourceRootArgument = argument('--source-root');
20 -const sourceCommit = argument('--source-commit')?.trim();
21 -if (!sourceRootArgument || !isAbsolute(sourceRootArgument)) {
22 - throw new Error('--source-root must be an absolute path to a support-knowledge checkout');
23 -}
24 -if (!sourceCommit) throw new Error('--source-commit is required');
25 -
26 -const sourceRoot = realpathSync(sourceRootArgument);
27 -const verifiedSourceCommit = verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit });
28 -const targetRoot = resolve(process.cwd(), 'kb');
29 -const previousManifestPath = join(targetRoot, 'manifest.json');
30 -const previousManifest = existsSync(previousManifestPath)
31 - ? JSON.parse(readFileSync(previousManifestPath, 'utf8')) as KbManifest
32 - : undefined;
33 -const previousSourceFiles = new Map<string, string>();
34 -const previousArticleFiles = new Map<string, string>();
35 -const readPreviousSource = previousManifest
36 - ? createKbSourceReader(join(targetRoot, 'source'))
37 - : undefined;
38 -const readPreviousArticle = previousManifest
39 - ? createKbArticleReader(join(targetRoot, 'articles'))
40 - : undefined;
41 -for (const guide of previousManifest?.guides ?? []) {
42 - for (const source of guide.sources) {
43 - if (!previousSourceFiles.has(source.sourcePath)) {
44 - previousSourceFiles.set(source.sourcePath, readPreviousSource!(source.sourcePath));
45 - }
46 - }
47 - if (guide.articlePath) {
48 - previousArticleFiles.set(guide.articlePath, readPreviousArticle!(guide.articlePath));
49 - }
50 -}
51 -
52 -const now = new Date();
53 -const snapshot = buildSupportKnowledgeSnapshot({
54 - sourceRoot,
55 - sourceCommit: verifiedSourceCommit,
56 - previousManifest,
57 - previousSourceFiles,
58 - previousArticleFiles,
59 - now,
60 -});
61 -
62 -writeSupportKnowledgeSnapshot({
63 - snapshot,
64 - targetRoot,
65 - validate: stagedRoot => {
66 - buildKbCatalog(
67 - snapshot.manifest,
68 - sourcePath => readFileSync(join(stagedRoot, 'source', sourcePath), 'utf8'),
69 - now,
70 - articlePath => readFileSync(join(stagedRoot, 'articles', articlePath), 'utf8'),
71 - );
72 - },
73 -});
74 -
75 -console.log(
76 - `Imported ${snapshot.manifest.guides.length} public guides from ${verifiedSourceCommit}; run bun run generate:kb next.`,
77 -);
docs/scripts/publish-kb-guide.ts
+8 -10
@@ -1,15 +1,16 @@
1 /**
2 - * Publish one KB guide approved in the support portal: create it, rewrite it, or retire it.
2 + * Apply one KB guide change proposed by the support portal: create, rewrite, or retire a guide.
3 + * The pull request it lands in is the approval.
4 *
5 * Reads a JSON request from the path given as the first argument (the docs-kb-publish workflow writes
5 - * it from the repository_dispatch payload), updates kb/manifest.json, the guide's article and, for a new
6 - * guide, its public source page, and validates the result with the same catalog checks the site uses.
6 + * it from the repository_dispatch payload), writes the guide's definition (kb/guides/<slug>.json), its
7 + * article and, for a new guide, its public source page, and validates the result with the same catalog checks the site uses.
8 * Run `bun run generate:kb` afterwards.
9 */
10 import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
11 import { dirname, join, resolve } from 'node:path';
12 import { buildKbCatalog } from '@/lib/kb/catalog';
12 -import { createKbArticleReader, createKbSourceReader } from '@/lib/kb/repository';
13 +import { createKbArticleReader, createKbSourceReader, readKbManifest } from '@/lib/kb/repository';
14 import type { KbGuideDefinition } from '@/lib/kb/types';
15 import { z } from 'zod';
16
@@ -28,9 +29,6 @@ const requestSchema = z.object({
29
30 const manifestSchema = z.object({
31 schemaVersion: z.literal(2),
31 - source: z.object({
32 - repository: z.string(), commit: z.string(), capturedAt: z.string(), contentHash: z.string(),
33 - }),
32 topics: z.array(z.object({
33 slug: z.string(), title: z.string(), description: z.string(), featuredRank: z.number().nullable(),
34 })),
@@ -61,8 +59,7 @@ const REVIEW_DAYS = 90;
59 export function publishKbGuide(input: unknown, docsRoot = process.cwd(), now = new Date()): void {
60 const request = requestSchema.parse(input);
61 const root = resolve(docsRoot, 'kb');
64 - const manifestPath = join(root, 'manifest.json');
65 - const manifest = manifestSchema.parse(JSON.parse(readFileSync(manifestPath, 'utf8')));
62 + const manifest = manifestSchema.parse(readKbManifest(root));
63 const today = now.toISOString().slice(0, 10);
64 const reviewAfter = new Date(now.valueOf() + REVIEW_DAYS * 86_400_000).toISOString().slice(0, 10);
65 const existing = manifest.guides.find(guide => guide.slug === request.slug);
@@ -164,7 +161,8 @@ export function publishKbGuide(input: unknown, docsRoot = process.cwd(), now = n
161 mkdirSync(dirname(path), { recursive: true });
162 writeFileSync(path, content);
163 }
167 - writeFileSync(manifestPath, `${JSON.stringify(manifest, null, 2)}\n`);
164 + const definition = manifest.guides.find(guide => guide.slug === request.slug);
165 + writeFileSync(join(root, 'guides', `${request.slug}.json`), `${JSON.stringify(definition, null, 2)}\n`);
166 console.log(`${request.action === 'retire' ? 'Retired' : existing ? 'Updated' : 'Created'} ${request.slug}.`);
167 }
168
docs/scripts/resolve-kb-refresh-source.sh deleted
-61
@@ -1,61 +0,0 @@
1 -#!/usr/bin/env bash
2 -
3 -set -euo pipefail
4 -
5 -current_commit=$(jq -r '.source.commit' kb/manifest.json)
6 -echo "commit=$current_commit" >> "$GITHUB_OUTPUT"
7 -
8 -if [ "$EVENT_NAME" = "repository_dispatch" ] && [ -z "$REQUESTED_SOURCE_COMMIT" ]; then
9 - echo "::error::Dispatched support knowledge refresh is missing source_commit."
10 - exit 1
11 -fi
12 -
13 -if [ "$HAVE_UPSTREAM" != "true" ]; then
14 - if [ "$EVENT_NAME" = "repository_dispatch" ]; then
15 - echo "::error::Cannot process a dispatched support knowledge refresh without an upstream token."
16 - exit 1
17 - fi
18 - echo "upstream_changed=false" >> "$GITHUB_OUTPUT"
19 - echo "No upstream token; skipping support-knowledge sync check and treating upstream as unchanged."
20 - exit 0
21 -fi
22 -
23 -checkout_commit=$(git -C "$SOURCE_ROOT" rev-parse HEAD)
24 -if [ -n "$REQUESTED_SOURCE_COMMIT" ] && [ "$checkout_commit" != "$REQUESTED_SOURCE_COMMIT" ]; then
25 - echo "::error::Support knowledge HEAD $checkout_commit does not match dispatched commit $REQUESTED_SOURCE_COMMIT."
26 - exit 1
27 -fi
28 -
29 -if ! upstream_tip=$(git -C "$SOURCE_ROOT" rev-parse --verify refs/remotes/origin/main 2>/dev/null); then
30 - echo "::error::Cannot resolve the support knowledge main branch."
31 - exit 1
32 -fi
33 -
34 -if [ -n "$REQUESTED_SOURCE_COMMIT" ] && \
35 - ! git -C "$SOURCE_ROOT" merge-base --is-ancestor "$REQUESTED_SOURCE_COMMIT" "$upstream_tip"; then
36 - echo "::error::Dispatched support knowledge commit $REQUESTED_SOURCE_COMMIT is not on upstream main."
37 - exit 1
38 -fi
39 -
40 -if [ "$upstream_tip" = "$current_commit" ]; then
41 - echo "upstream_changed=false" >> "$GITHUB_OUTPUT"
42 - echo "Support knowledge is already current at $upstream_tip."
43 -elif ! git -C "$SOURCE_ROOT" cat-file -e "$current_commit^{commit}" 2>/dev/null; then
44 - echo "::error::Published support knowledge commit $current_commit is unavailable in the upstream history."
45 - exit 1
46 -elif ! git -C "$SOURCE_ROOT" merge-base --is-ancestor "$current_commit" "$upstream_tip"; then
47 - echo "::error::Published support knowledge commit $current_commit is not on upstream main."
48 - exit 1
49 -elif ! source_commit=$(git -C "$SOURCE_ROOT" log --first-parent -1 --format=%H \
50 - "$current_commit..$upstream_tip" -- ':(glob)**/public.md'); then
51 - echo "::error::Cannot inspect public support knowledge history."
52 - exit 1
53 -elif [ -z "$source_commit" ]; then
54 - echo "upstream_changed=false" >> "$GITHUB_OUTPUT"
55 - echo "No public support knowledge changed between $current_commit and $upstream_tip."
56 -else
57 - git -C "$SOURCE_ROOT" checkout --detach "$source_commit"
58 - echo "commit=$source_commit" >> "$GITHUB_OUTPUT"
59 - echo "upstream_changed=true" >> "$GITHUB_OUTPUT"
60 - echo "Refreshing support knowledge from $current_commit to $source_commit."
61 -fi
docs/scripts/verify-kb.ts
+4 -47
@@ -12,14 +12,13 @@
12 import { readFileSync, writeFileSync } from 'node:fs';
13 import { join } from 'node:path';
14 import { buildKbCatalog } from '@/lib/kb/catalog';
15 -import { createKbArticleReader } from '@/lib/kb/repository';
15 +import { createKbArticleReader, readKbManifest } from '@/lib/kb/repository';
16 import {
17 buildProductCatalog,
18 renderVerifyReport,
19 verifyKb,
20 type CatalogToolkit,
21 type KbVerifyReport,
22 - type SourcePinStatus,
22 } from '@/lib/kb/verify';
23 import type { KbManifest } from '@/lib/kb/types';
24
@@ -30,7 +29,6 @@ const LINK_TIMEOUT_MS = 10_000;
29
30 interface CliOptions {
31 checkLinks: boolean;
33 - checkSourcePin: boolean;
32 json: boolean;
33 markdownPath: string | null;
34 warningsAsErrors: boolean;
@@ -39,14 +37,12 @@ interface CliOptions {
37 function parseOptions(argumentsList: string[]): CliOptions {
38 const allowed = new Set([
39 '--check-links',
42 - '--check-source-pin',
40 '--json',
41 '--markdown',
42 '--warnings-as-errors',
43 ]);
44 const options: CliOptions = {
45 checkLinks: argumentsList.includes('--check-links'),
49 - checkSourcePin: argumentsList.includes('--check-source-pin'),
46 json: argumentsList.includes('--json'),
47 markdownPath: null,
48 warningsAsErrors: argumentsList.includes('--warnings-as-errors'),
@@ -73,7 +69,7 @@ function parseOptions(argumentsList: string[]): CliOptions {
69 * every published guide's review deadline against the real clock.
70 */
71 function loadCatalogIgnoringExpiry() {
76 - const manifest = JSON.parse(readFileSync(join(KB_ROOT, 'manifest.json'), 'utf8')) as KbManifest;
72 + const manifest = readKbManifest(KB_ROOT);
73 const catalog = buildKbCatalog(
74 manifest,
75 (sourcePath) => readFileSync(join(KB_ROOT, 'source', sourcePath), 'utf8'),
@@ -116,42 +112,6 @@ async function probe(url: string): Promise<number | 'unreachable'> {
112 return 'unreachable';
113 }
114
119 -/**
120 - * Resolve `manifest.source.commit` against the upstream repository.
121 - *
122 - * The upstream is a separate internal repo, so a token scoped to this repository
123 - * gets 403/404 whether or not the commit exists. Only an authenticated 422/404
124 - * with read access proves absence, so anything ambiguous returns `unverifiable`
125 - * and produces no finding.
126 - */
127 -async function resolveSourcePin(
128 - repository: string,
129 - commit: string
130 -): Promise<SourcePinStatus> {
131 - const token = process.env.GITHUB_TOKEN ?? process.env.GH_TOKEN;
132 - if (!token) return 'unverifiable';
133 - try {
134 - const response = await fetch(
135 - `https://api.github.com/repos/${repository}/commits/${commit}`,
136 - {
137 - headers: {
138 - authorization: `Bearer ${token}`,
139 - accept: 'application/vnd.github+json',
140 - 'user-agent': 'composio-docs-kb-verify',
141 - },
142 - signal: AbortSignal.timeout(LINK_TIMEOUT_MS),
143 - }
144 - );
145 - if (response.ok) return 'resolved';
146 - // 401/403 is "this token cannot see that repository", not "the commit is gone".
147 - if (response.status === 401 || response.status === 403) return 'unverifiable';
148 - if (response.status === 404 || response.status === 422) return 'missing';
149 - return 'unverifiable';
150 - } catch {
151 - return 'unverifiable';
152 - }
153 -}
154 -
115 function exitCodeFor(report: KbVerifyReport, options: CliOptions): number {
116 const failing = report.findings.filter(
117 (finding) => finding.severity === 'error' || options.warningsAsErrors
@@ -179,18 +139,15 @@ export async function runVerifyKb(argumentsList: string[]): Promise<number> {
139 const linkStatuses = options.checkLinks
140 ? await resolveLinkStatuses(dryRun.externalLinks)
141 : undefined;
182 - const sourcePinStatus = options.checkSourcePin
183 - ? await resolveSourcePin(catalog.manifest.source.repository, catalog.manifest.source.commit)
184 - : undefined;
142
143 const report =
187 - linkStatuses || sourcePinStatus
144 + linkStatuses
145 ? verifyKb({
146 manifest: catalog.manifest,
147 guides: catalog.guides,
148 catalog: productCatalog,
149 now: new Date(),
193 - options: { linkStatuses, sourcePinStatus },
150 + options: { linkStatuses },
151 })
152 : dryRun;
153
docs/tests/e2e/kb-publish.ts new
+169
@@ -0,0 +1,169 @@
1 +#!/usr/bin/env bun
2 +/**
3 + * Local end-to-end run of KB publication, docs side: `bun run test:kb-publish` from docs/.
4 + *
5 + * It replays what happens after the support portal sends `kb-guide-approved`, using the real
6 + * steps from .github/workflows/docs-kb-publish.yml (same scripts, same bash flags as Actions):
7 + * 1. two portal dispatches, each applied on its own branch off this checkout's HEAD (= two KB PRs);
8 + * 2. both "PRs" merged into the base in turn (proves open KB PRs don't conflict);
9 + * 3. the merged KB regenerated, and the new guides looked up through Ask AI's search_docs and read_doc.
10 + * Everything happens in a throwaway git worktree; this checkout is never modified.
11 + * Pass --keep to leave the worktree for previewing (it prints the path). `next dev` there needs a real
12 + * node_modules, not this symlink: `rm node_modules && cp -cR <docs>/node_modules node_modules` on macOS.
13 + */
14 +import { spawnSync } from 'node:child_process';
15 +import { mkdtempSync, readFileSync, rmSync, symlinkSync } from 'node:fs';
16 +import { tmpdir } from 'node:os';
17 +import { join, resolve } from 'node:path';
18 +
19 +const repo = resolve(import.meta.dir, '../../..');
20 +const keep = process.argv.includes('--keep');
21 +const runDir = mkdtempSync(join(tmpdir(), 'kb-e2e-'));
22 +const work = join(runDir, 'repo');
23 +// Branches live in the shared repo, so each run gets its own names.
24 +const prefix = `kb-e2e/${runDir.split('-').at(-1)}`;
25 +const base = `${prefix}/base`;
26 +const prBranch = (draftId: number) => `${prefix}/docs/kb-front-desk-${draftId}`;
27 +const branches = () => [base, ...dispatches.map(({ draft_id }) => prBranch(draft_id))];
28 +const docs = join(work, 'docs');
29 +const runnerTemp = mkdtempSync(join(tmpdir(), 'kb-e2e-runner-'));
30 +
31 +// The guide objects exactly as core/knowledge/kb.py `_checked()` builds them for client_payload.guide.
32 +const dispatches = [
33 + {
34 + draft_id: 9001,
35 + guide: {
36 + action: 'upsert', slug: 'sdk-e2e-webhook-retries', area: 'sdk',
37 + title: 'Webhook delivery retries',
38 + description: 'How trigger webhook deliveries are retried after a failed response.',
39 + body: '## When a delivery is retried\n\nA trigger webhook delivery is retried when your endpoint returns a 5xx status or times out.\n\n## Making your handler idempotent\n\nUse the event ID to ignore a delivery you already processed.',
40 + topics: ['workflows'], tags: ['triggers', 'webhooks'],
41 + },
42 + },
43 + {
44 + draft_id: 9002,
45 + guide: {
46 + action: 'upsert', slug: 'platform-e2e-session-limits', area: 'platform',
47 + title: 'Session tool call limits',
48 + description: 'What happens when a session reaches its tool call limit.',
49 + body: '## Hitting the limit\n\nA session that reaches its tool call limit returns a limit error for further calls.\n\n## Starting a new session\n\nCreate a new session for the user to continue.',
50 + topics: ['sessions-and-execution'], tags: ['sessions'],
51 + },
52 + },
53 +];
54 +
55 +type Step = { name: string; run?: string };
56 +const workflow = Bun.YAML.parse(
57 + readFileSync(join(repo, '.github/workflows/docs-kb-publish.yml'), 'utf8'),
58 +) as { jobs: { publish: { steps: Step[] } } };
59 +
60 +function sh(command: 'git' | 'bun', args: string[], cwd: string, env: Record<string, string> = {}) {
61 + const result = spawnSync(command, args, {
62 + cwd,
63 + encoding: 'utf8',
64 + env: { ...process.env, ...env },
65 + shell: false,
66 + });
67 + return { ok: result.status === 0, out: `${result.stdout ?? ''}${result.stderr ?? ''}`.trim() };
68 +}
69 +function must(command: 'git' | 'bun', args: string[], cwd = work, env: Record<string, string> = {}) {
70 + const result = sh(command, args, cwd, env);
71 + if (!result.ok) throw new Error(`${command} ${args.join(' ')} failed:\n${result.out}`);
72 + return result.out;
73 +}
74 +function workflowStep(name: string, env: Record<string, string>) {
75 + const script = workflow.jobs.publish.steps.find(step => step.name === name)?.run;
76 + if (!script) throw new Error(`docs-kb-publish.yml has no step "${name}"`);
77 + // The job's default shell is bash, which Actions runs with -e -o pipefail.
78 + const result = spawnSync('bash', ['--noprofile', '--norc', '-e', '-o', 'pipefail', '-s'], {
79 + cwd: docs,
80 + encoding: 'utf8',
81 + env: { ...process.env, RUNNER_TEMP: runnerTemp, ...env },
82 + input: script,
83 + shell: false,
84 + });
85 + return { ok: result.status === 0, out: `${result.stdout ?? ''}${result.stderr ?? ''}`.trim() };
86 +}
87 +
88 +let failed = false;
89 +const check = (ok: boolean, label: string, detail = '') => {
90 + console.log(`${ok ? 'PASS' : 'FAIL'} ${label}${detail ? `\n ${detail.replaceAll('\n', '\n ')}` : ''}`);
91 + if (!ok) failed = true;
92 +};
93 +
94 +try {
95 + must('git', ['-C', repo, 'worktree', 'add', '-q', '--detach', work, 'HEAD'], repo);
96 + symlinkSync(join(repo, 'docs/node_modules'), join(docs, 'node_modules'));
97 + must('git', ['switch', '-q', '-c', base]);
98 + const git = ['-c', 'user.name=kb-e2e', '-c', 'user.email=kb-e2e@localhost', '-c', 'commit.gpgsign=false'];
99 +
100 + // 1. Each dispatch becomes its own PR branch, built by the workflow's own steps.
101 + for (const { draft_id, guide } of dispatches) {
102 + const branch = prBranch(draft_id);
103 + must('git', ['switch', '-q', '-c', branch, base]);
104 + const apply = workflowStep('Apply the approved guide', { GUIDE: JSON.stringify(guide) });
105 + check(apply.ok, `${branch}: "Apply the approved guide"`, apply.ok ? '' : apply.out.slice(-1500));
106 + const regenerate = workflowStep('Regenerate KB pages', { GUIDE_SLUG: guide.slug });
107 + const errors = regenerate.ok ? [] : (() => {
108 + try {
109 + const report = JSON.parse(readFileSync(join(runnerTemp, 'kb-verify.json'), 'utf8')) as {
110 + findings: { severity: string; kind: string }[];
111 + };
112 + const counts = new Map<string, number>();
113 + for (const finding of report.findings.filter(item => item.severity === 'error')) {
114 + counts.set(finding.kind, (counts.get(finding.kind) ?? 0) + 1);
115 + }
116 + return [...counts].map(([kind, count]) => `${count} x ${kind}`);
117 + } catch {
118 + return [regenerate.out.slice(-1500)];
119 + }
120 + })();
121 + check(regenerate.ok, `${branch}: "Regenerate KB pages" (the PR is only opened if this passes)`,
122 + regenerate.ok ? '' : `verify:kb errors: ${errors.join(', ')}`);
123 + // Stage what create-pull-request would (add-paths: docs/kb/).
124 + must('git', ['add', 'docs/kb']);
125 + const files = must('git', ['diff', '--cached', '--name-only']).split('\n').filter(Boolean);
126 + const ownPaths = [guide.slug, `${guide.area}/${guide.slug.slice(guide.area.length + 1)}/`];
127 + check(files.every(file => ownPaths.some(path => file.includes(path))),
128 + `${branch}: the PR only touches this guide's own files`, files.join('\n'));
129 + must('git', [...git, 'commit', '-q', '-m', `docs(kb): ${guide.title}`]);
130 + }
131 +
132 + // 2. Both PRs wait for review side by side, then merge in turn.
133 + must('git', ['switch', '-q', base]);
134 + for (const { draft_id } of dispatches) {
135 + const merge = sh('git', [...git, 'merge', '-q', '--no-edit', prBranch(draft_id)], work);
136 + check(merge.ok, `merge ${prBranch(draft_id)} after the other`, merge.ok ? '' : merge.out);
137 + }
138 +
139 + // 3. After merge, the build regenerates content/kb and Ask AI's index and finds the guides.
140 + must('bun', ['run', 'generate:kb'], docs);
141 + must('bun', ['scripts/build-agent-index.ts'], docs);
142 + const probe = must('bun', ['-e', `
143 + const { searchDocs } = await import('./agent/lib/docs-search.ts');
144 + const { readPageByUrl } = await import('./agent/lib/docs.ts');
145 + const queries = ${JSON.stringify(dispatches.map(({ guide }) => [guide.slug, guide.title]))};
146 + console.log(JSON.stringify(queries.map(([slug, title]) => ({
147 + slug,
148 + found: searchDocs(title, { limit: 5 }).results.some(r => r.url === '/kb/guide/' + slug),
149 + readable: readPageByUrl('/kb/guide/' + slug)?.title === title,
150 + }))));
151 + `], docs, { EVE_FORCE_BUNDLE: '1' });
152 + for (const result of JSON.parse(probe.split('\n').at(-1)!) as { slug: string; found: boolean; readable: boolean }[]) {
153 + check(result.found, `Ask AI search_docs finds /kb/guide/${result.slug} (deployed bundle)`);
154 + check(result.readable, `Ask AI read_doc opens /kb/guide/${result.slug}`);
155 + }
156 +} catch (error) {
157 + check(false, 'run aborted', String(error));
158 +} finally {
159 + if (keep) {
160 + console.log(`\nWorktree kept at ${work}\nPreview: cd ${docs} && bun run dev, then open /kb/guide/${dispatches[0]!.guide.slug}`);
161 + console.log(`Remove with: git -C ${repo} worktree remove --force ${work} && git -C ${repo} branch -D ${branches().join(' ')}`);
162 + } else {
163 + sh('git', ['-C', repo, 'worktree', 'remove', '--force', work], repo);
164 + sh('git', ['-C', repo, 'branch', '-D', ...branches()], repo);
165 + }
166 + rmSync(runnerTemp, { recursive: true, force: true });
167 +}
168 +console.log(failed ? '\nE2E FAILED' : '\nE2E PASSED');
169 +process.exit(failed ? 1 : 0);
docs/tests/static/docs-data-workflow.test.ts
+2 -4
@@ -95,9 +95,8 @@ describe('docs data update workflow', () => {
95 }
96 });
97
98 - test('isolates the optional KB source path from every required data-sync step', () => {
99 - const sourceToken = stepNamed(steps, 'Generate read-only KB source token');
100 - expect(sourceToken['continue-on-error']).toBe(true);
98 + test('keeps the optional KB freshness check out of every required data-sync step', () => {
99 + expect(stepNamed(steps, 'Verify KB freshness against refreshed data')['continue-on-error']).toBe(true);
100
101 const requiredStepNames = [
102 'Generate GitHub App token',
@@ -112,7 +111,6 @@ describe('docs data update workflow', () => {
111 for (const name of requiredStepNames) {
112 const step = stepNamed(steps, name);
113 const dependencies = JSON.stringify({ if: step.if, env: step.env, with: step.with });
115 - expect(dependencies).not.toContain('steps.source-token');
114 expect(dependencies).not.toContain('steps.verify-kb');
115 }
116 });
docs/tests/static/eve-kb-retrieval.test.ts new
+15
@@ -0,0 +1,15 @@
1 +import { describe, expect, test } from 'bun:test';
2 +import { searchDocs } from '../../agent/lib/docs-search';
3 +import { readPageByUrl } from '../../agent/lib/docs';
4 +
5 +describe('docs agent knowledge base retrieval', () => {
6 + test('search_docs returns KB guides and read_doc can open them', () => {
7 + const { results } = searchDocs('organization API rate limits 429', { limit: 8 });
8 + const guide = results.find(result => result.url === '/kb/guide/platform-rate-limits');
9 +
10 + expect(guide).toBeDefined();
11 + expect(guide?.content).toContain('429');
12 + expect(readPageByUrl('/kb/guide/platform-rate-limits')?.title).toBe('Platform API Rate Limits');
13 + expect(readPageByUrl('/kb')).toBeDefined();
14 + });
15 +});
docs/tests/static/kb-catalog.test.ts
+1 -7
@@ -44,12 +44,6 @@ This is the second safe answer.
44 function manifest(overrides: Partial<KbManifest['guides'][number]> = {}): KbManifest {
45 return {
46 schemaVersion: 2,
47 - source: {
48 - repository: 'ComposioHQ/example-knowledge',
49 - commit: '5eed614',
50 - capturedAt: '2026-07-21',
51 - contentHash: 'sha256:fixture',
52 - },
47 topics: [
48 {
49 slug: 'platform',
@@ -399,7 +393,7 @@ This is the second safe answer.`);
393 }
394 }
395 const heldGuides = getKbCatalog().guides.filter(guide => guide.state === 'needs-review');
402 - // Reconciled support-knowledge contains only reviewed public leaves, so the
396 + // The published snapshot contains only reviewed public leaves, so the
397 // imported snapshot should not create downstream editorial holds.
398 expect(heldGuides).toHaveLength(0);
399 });
docs/tests/static/kb-generation.test.ts
+4 -43
@@ -15,7 +15,7 @@ import { join, relative } from 'node:path';
15 import GithubSlugger from 'github-slugger';
16 import { generateKbContent, markdownForMdx } from '@/lib/kb/generate';
17 import { buildKbCatalog } from '@/lib/kb/catalog';
18 -import { createKbArticleReader, getKbCatalog } from '@/lib/kb/repository';
18 +import { createKbArticleReader, getKbCatalog, readKbManifest } from '@/lib/kb/repository';
19 import type { KbManifest } from '@/lib/kb/types';
20 import { evaluate } from '@mdx-js/mdx';
21 import { createElement } from 'react';
@@ -300,9 +300,7 @@ describe('public KB content generation', () => {
300 expect(files.some(file => file.startsWith('toolkits/'))).toBe(false);
301 expect(files.some(file => file.startsWith('sdk-and-api/'))).toBe(false);
302
303 - const manifest = JSON.parse(
304 - readFileSync(join(process.cwd(), 'kb/manifest.json'), 'utf8'),
305 - ) as KbManifest;
303 + const manifest = readKbManifest();
304 const published = manifest.guides.filter(guide => guide.state === 'published');
305 const newlyAuthored = published.filter(guide => guide.articlePath !== undefined);
306 const held = manifest.guides.filter(guide => guide.state === 'needs-review');
@@ -315,8 +313,8 @@ describe('public KB content generation', () => {
313 expect(new Set(newlyAuthored.map(guide => `/kb/guide/${guide.slug}`)).size).toBe(
314 published.length
315 );
318 - // The reconciled support-knowledge snapshot only contains reviewed public
319 - // leaves. Importing it must not invent editorial holds downstream.
316 + // The published snapshot only contains reviewed public
317 + // leaves. Generating it must not invent editorial holds downstream.
318 expect(held).toHaveLength(0);
319
320 expect(JSON.parse(readFileSync(join(outputDir, 'meta.json'), 'utf8'))).toEqual({
@@ -348,31 +346,6 @@ describe('public KB content generation', () => {
346 }
347 });
348
351 - test('keeps generated page bytes independent of the source snapshot commit', () => {
352 - const originalDir = mkdtempSync(join(tmpdir(), 'composio-kb-original-'));
353 - const repinnedDir = mkdtempSync(join(tmpdir(), 'composio-kb-repinned-'));
354 - temporaryDirectories.push(originalDir, repinnedDir);
355 - const catalog = getKbCatalog();
356 - const repinnedCatalog = {
357 - ...catalog,
358 - manifest: {
359 - ...catalog.manifest,
360 - source: { ...catalog.manifest.source, commit: 'different-source-commit' },
361 - },
362 - };
363 -
364 - generateKbContent({ outputDir: originalDir, catalog });
365 - generateKbContent({ outputDir: repinnedDir, catalog: repinnedCatalog });
366 -
367 - const files = listFiles(originalDir);
368 - expect(listFiles(repinnedDir)).toEqual(files);
369 - for (const file of files) {
370 - expect(readFileSync(join(repinnedDir, file), 'utf8')).toBe(
371 - readFileSync(join(originalDir, file), 'utf8'),
372 - );
373 - }
374 - });
375 -
349 test('leaves unchanged generated files untouched', () => {
350 const outputDir = mkdtempSync(join(tmpdir(), 'composio-kb-'));
351 temporaryDirectories.push(outputDir);
@@ -422,12 +395,6 @@ describe('public KB content generation', () => {
395 );
396 const manifest: KbManifest = {
397 schemaVersion: 2,
425 - source: {
426 - repository: 'ComposioHQ/example-knowledge',
427 - commit: '5eed614',
428 - capturedAt: '2026-07-21',
429 - contentHash: 'sha256:fixture',
430 - },
398 topics: [
399 { slug: 'platform', title: 'Platform', description: 'Platform guidance.', featuredRank: 1 },
400 ],
@@ -476,12 +443,6 @@ describe('public KB content generation', () => {
443 temporaryDirectories.push(outputDir);
444 const manifest: KbManifest = {
445 schemaVersion: 2,
479 - source: {
480 - repository: 'ComposioHQ/example-knowledge',
481 - commit: '5eed614',
482 - capturedAt: '2026-07-21',
483 - contentHash: 'sha256:fixture',
484 - },
446 topics: [],
447 guides: [
448 {
docs/tests/static/kb-import.test.ts deleted
-524
@@ -1,524 +0,0 @@
1 -import { describe, expect, test } from 'bun:test';
2 -import { existsSync, mkdirSync, mkdtempSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
3 -import { spawnSync } from 'node:child_process';
4 -import { join } from 'node:path';
5 -import { tmpdir } from 'node:os';
6 -import {
7 - buildSupportKnowledgeSnapshot,
8 - parseSupportKnowledgeDocument,
9 - verifySupportKnowledgeCheckout,
10 - writeSupportKnowledgeSnapshot,
11 -} from '@/lib/kb/support-knowledge';
12 -import type { KbManifest } from '@/lib/kb/types';
13 -import { buildKbCatalog } from '@/lib/kb/catalog';
14 -import { createKbArticleReader, createKbSourceReader } from '@/lib/kb/repository';
15 -import { publishKbGuide } from '../../scripts/publish-kb-guide';
16 -
17 -const publicDocument = `---
18 -type: "reference"
19 -title: "GitHub"
20 -description: "Public support knowledge for GitHub."
21 -classification: "public"
22 -product:
23 - - "platform"
24 - - "for-you"
25 -category:
26 - - "authentication"
27 - - "errors-and-troubleshooting"
28 -owner: "support"
29 -timestamp: "2026-06-24T00:00:00Z"
30 -last_reviewed: "2026-08-12"
31 -review_by: "2026-11-10"
32 -tags:
33 - - "github"
34 ----
35 -# GitHub
36 -
37 -Use this for GitHub setup and troubleshooting.
38 -
39 -## Tokens are redacted
40 -
41 -Provider tokens are redacted from connected-account responses.
42 -
43 -## Create triggers directly
44 -
45 -Create the trigger instance directly; a separate webhook endpoint is not required.
46 -`;
47 -
48 -const customerSafeDocument = publicDocument
49 - .replace('title: "GitHub"', 'title: "Private GitHub guidance"')
50 - .replace('classification: "public"', 'classification: "customer-safe"')
51 - .replace('timestamp: "2026-06-24T00:00:00Z"\n', '');
52 -
53 -function writeDocument(root: string, relativePath: string, contents: string): void {
54 - const target = join(root, relativePath);
55 - mkdirSync(join(target, '..'), { recursive: true });
56 - writeFileSync(target, contents, 'utf8');
57 -}
58 -
59 -function git(root: string, ...args: string[]): string {
60 - const result = spawnSync('git', args, { cwd: root, encoding: 'utf8' });
61 - if (result.status !== 0) throw new Error(result.stderr);
62 - return result.stdout.trim();
63 -}
64 -
65 -function previousManifest(): KbManifest {
66 - return {
67 - schemaVersion: 2,
68 - source: {
69 - repository: 'ComposioHQ/public-kb',
70 - commit: 'old1234',
71 - capturedAt: '2026-07-26',
72 - contentHash: 'sha256:previous',
73 - },
74 - topics: [
75 - {
76 - slug: 'authentication',
77 - title: 'Authentication',
78 - description: 'Authentication guidance.',
79 - featuredRank: 1,
80 - },
81 - {
82 - slug: 'errors-and-troubleshooting',
83 - title: 'Errors and troubleshooting',
84 - description: 'Troubleshooting guidance.',
85 - featuredRank: 2,
86 - },
87 - ],
88 - guides: [
89 - {
90 - slug: 'github-troubleshooting',
91 - title: 'GitHub troubleshooting',
92 - description: 'Old grouped page.',
93 - articlePath: 'github-troubleshooting.md',
94 - sources: [
95 - { sourcePath: 'toolkits/github/public.md', sourceHeading: 'Tokens are redacted' },
96 - ],
97 - topics: ['authentication'],
98 - tags: ['github'],
99 - aliases: ['old-github-answer'],
100 - relatedGuides: ['related-guide'],
101 - externalResources: ['https://example.com/reference'],
102 - updatedAt: '2026-07-26',
103 - lastVerifiedAt: '2026-07-26',
104 - reviewAfter: '2026-12-31',
105 - freshness: 'evergreen',
106 - state: 'published',
107 - featured: true,
108 - verifyIgnoreToolSlugs: ['GITHUB_REMOVED_TOOL'],
109 - },
110 - ],
111 - };
112 -}
113 -
114 -describe('support-knowledge snapshot import', () => {
115 - test('preserves portal creations, rewrites and retirements through repeated upstream refreshes', () => {
116 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-portal-'));
117 - const docsRoot = mkdtempSync(join(tmpdir(), 'kb-publish-'));
118 - const targetRoot = join(docsRoot, 'kb');
119 - const now = new Date('2026-08-18T00:00:00Z');
120 - const validate = (stagedRoot: string) => buildKbCatalog(
121 - JSON.parse(readFileSync(join(stagedRoot, 'manifest.json'), 'utf8')),
122 - createKbSourceReader(join(stagedRoot, 'source')),
123 - now,
124 - createKbArticleReader(join(stagedRoot, 'articles')),
125 - );
126 - try {
127 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
128 - writeDocument(sourceRoot, 'toolkits/slack/public.md', publicDocument.replaceAll('GitHub', 'Slack'));
129 - writeDocument(sourceRoot, 'toolkits/gitlab/public.md', publicDocument.replaceAll('GitHub', 'GitLab'));
130 - const initial = buildSupportKnowledgeSnapshot({ sourceRoot, sourceCommit: 'initial', now });
131 - writeSupportKnowledgeSnapshot({ snapshot: initial, targetRoot, validate });
132 -
133 - publishKbGuide({
134 - action: 'upsert', slug: 'toolkits-github', title: 'Approved GitHub title',
135 - description: 'Approved description.', topics: ['authentication'], tags: [],
136 - body: '## Approved answer\n\nUse the approved instructions.',
137 - }, docsRoot, now);
138 - publishKbGuide({ action: 'retire', slug: 'toolkits-slack' }, docsRoot, now);
139 - publishKbGuide({
140 - action: 'upsert', slug: 'sdk-portal-guide', area: 'sdk', title: 'Portal guide',
141 - description: 'A guide created in the portal.', topics: ['authentication'], tags: [],
142 - body: '## Setup\n\nFollow these setup instructions.',
143 - }, docsRoot, now);
144 - const approved = validate(targetRoot);
145 -
146 - // Upstream changes metadata and headings, removes a retired source, and drops a topic.
147 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument
148 - .replaceAll('authentication', 'errors-and-troubleshooting')
149 - .replaceAll('Tokens are redacted', 'Changed upstream heading'));
150 - rmSync(join(sourceRoot, 'toolkits/slack'), { recursive: true });
151 - writeDocument(sourceRoot, 'toolkits/gitlab/public.md', publicDocument
152 - .replaceAll('GitHub', 'Updated GitLab')
153 - .replaceAll('authentication', 'errors-and-troubleshooting'));
154 -
155 - for (const sourceCommit of ['refresh-one', 'refresh-two']) {
156 - const previous = validate(targetRoot);
157 - const snapshot = buildSupportKnowledgeSnapshot({
158 - sourceRoot, sourceCommit, previousManifest: previous.manifest,
159 - previousSourceFiles: new Map(previous.guides.flatMap(guide => guide.sources.map(source => [
160 - source.sourcePath, readFileSync(join(targetRoot, 'source', source.sourcePath), 'utf8'),
161 - ]))),
162 - previousArticleFiles: new Map(previous.guides.map(guide => [
163 - guide.articlePath!, readFileSync(join(targetRoot, 'articles', guide.articlePath!), 'utf8'),
164 - ])),
165 - now,
166 - });
167 - writeSupportKnowledgeSnapshot({ snapshot, targetRoot, validate });
168 - const refreshed = validate(targetRoot);
169 - for (const slug of ['toolkits-github', 'toolkits-slack', 'sdk-portal-guide']) {
170 - expect(refreshed.guides.find(guide => guide.slug === slug))
171 - .toEqual(approved.guides.find(guide => guide.slug === slug));
172 - }
173 - expect(refreshed.guides.find(guide => guide.slug === 'toolkits-gitlab')?.title)
174 - .toBe('Updated GitLab');
175 - expect(refreshed.topics.some(topic => topic.slug === 'authentication')).toBe(true);
176 - expect(refreshed.manifest.source.commit).toBe(sourceCommit);
177 - }
178 - } finally {
179 - rmSync(sourceRoot, { recursive: true, force: true });
180 - rmSync(docsRoot, { recursive: true, force: true });
181 - }
182 - });
183 -
184 - test('keeps a retired guide unpublished when its public source is refreshed', () => {
185 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-retired-'));
186 - try {
187 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
188 - const previous = previousManifest();
189 - previous.guides[0]!.state = 'retired';
190 - const snapshot = buildSupportKnowledgeSnapshot({
191 - sourceRoot,
192 - sourceCommit: 'updated-source',
193 - previousManifest: previous,
194 - now: new Date('2026-08-18T00:00:00Z'),
195 - });
196 -
197 - expect(snapshot.manifest.guides[0]?.state).toBe('retired');
198 - } finally {
199 - rmSync(sourceRoot, { recursive: true, force: true });
200 - }
201 - });
202 -
203 - test('verifies the checkout repository and exact source commit', () => {
204 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-git-'));
205 - git(sourceRoot, 'init');
206 - git(sourceRoot, 'config', 'user.name', 'KB Import Test');
207 - git(sourceRoot, 'config', 'user.email', 'kb-import@example.com');
208 - writeFileSync(join(sourceRoot, 'README.md'), 'first\n', 'utf8');
209 - writeFileSync(join(sourceRoot, '.gitignore'), 'ignored/\n', 'utf8');
210 - git(sourceRoot, 'add', 'README.md', '.gitignore');
211 - git(sourceRoot, 'commit', '-m', 'first');
212 - const firstCommit = git(sourceRoot, 'rev-parse', 'HEAD');
213 - git(sourceRoot, 'remote', 'add', 'origin', 'git@github.com:OtherOrg/support-knowledge.git');
214 -
215 - expect(() => verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit: firstCommit }))
216 - .toThrow('expected ComposioHQ/support-knowledge');
217 -
218 - git(sourceRoot, 'remote', 'set-url', 'origin', 'https://github.com/ComposioHQ/support-knowledge.git');
219 - expect(verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit: firstCommit }))
220 - .toBe(firstCommit);
221 -
222 - writeFileSync(join(sourceRoot, 'README.md'), 'dirty\n', 'utf8');
223 - expect(() => verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit: firstCommit }))
224 - .toThrow('has uncommitted changes');
225 - git(sourceRoot, 'restore', 'README.md');
226 -
227 - writeDocument(sourceRoot, 'ignored/public.md', publicDocument);
228 - expect(() => verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit: firstCommit }))
229 - .toThrow('contains ignored knowledge files');
230 - rmSync(join(sourceRoot, 'ignored'), { recursive: true });
231 -
232 - writeFileSync(join(sourceRoot, 'README.md'), 'second\n', 'utf8');
233 - git(sourceRoot, 'add', 'README.md');
234 - git(sourceRoot, 'commit', '-m', 'second');
235 - expect(() => verifySupportKnowledgeCheckout({ sourceRoot, sourceCommit: firstCommit }))
236 - .toThrow('does not match requested commit');
237 - });
238 -
239 - test('copies only public leaves and preserves old public guide URLs as aliases', () => {
240 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
241 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
242 - writeDocument(sourceRoot, 'toolkits/github/customer-safe.md', customerSafeDocument);
243 -
244 - const snapshot = buildSupportKnowledgeSnapshot({
245 - sourceRoot,
246 - sourceCommit: 'abc1234',
247 - previousManifest: previousManifest(),
248 - now: new Date('2026-08-17T00:00:00Z'),
249 - });
250 -
251 - expect([...snapshot.sourceFiles.keys()]).toEqual(['toolkits/github/public.md']);
252 - expect([...snapshot.articleFiles.keys()]).toEqual(['toolkits-github.md']);
253 - expect(JSON.stringify(snapshot)).not.toContain('customer-safe');
254 - expect(snapshot.manifest.source).toEqual({
255 - repository: 'ComposioHQ/support-knowledge',
256 - commit: 'abc1234',
257 - capturedAt: '2026-08-17',
258 - contentHash: expect.stringMatching(/^sha256:[a-f0-9]{64}$/),
259 - });
260 - expect(snapshot.manifest.guides).toHaveLength(1);
261 - expect(snapshot.manifest.guides[0]).toMatchObject({
262 - slug: 'toolkits-github',
263 - articlePath: 'toolkits-github.md',
264 - aliases: [
265 - '/kb/authentication/github-troubleshooting',
266 - 'github-troubleshooting',
267 - 'old-github-answer',
268 - ],
269 - sources: [
270 - { sourcePath: 'toolkits/github/public.md', sourceHeading: 'Tokens are redacted' },
271 - { sourcePath: 'toolkits/github/public.md', sourceHeading: 'Create triggers directly' },
272 - ],
273 - lastVerifiedAt: '2026-08-12',
274 - reviewAfter: '2026-11-10',
275 - });
276 - expect(snapshot.articleFiles.get('toolkits-github.md')).toStartWith(
277 - 'Use this for GitHub setup and troubleshooting.',
278 - );
279 - });
280 -
281 - test('preserves curated articles and reviewed slug exceptions when the source is unchanged', () => {
282 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
283 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
284 - const initial = buildSupportKnowledgeSnapshot({
285 - sourceRoot,
286 - sourceCommit: 'initial',
287 - now: new Date('2026-08-17T00:00:00Z'),
288 - });
289 -
290 - const previous = previousManifest();
291 - previous.guides[0]!.sources.push({
292 - sourcePath: 'toolkits/github/public.md',
293 - sourceHeading: 'Create triggers directly',
294 - });
295 - const snapshot = buildSupportKnowledgeSnapshot({
296 - sourceRoot,
297 - sourceCommit: 'next',
298 - previousManifest: previous,
299 - previousSourceFiles: initial.sourceFiles,
300 - previousArticleFiles: new Map([
301 - ['github-troubleshooting.md', 'Curated reader-facing guidance.\n'],
302 - ]),
303 - now: new Date('2026-08-18T00:00:00Z'),
304 - });
305 -
306 - expect(snapshot.articleFiles.get('toolkits-github.md')).toBe(
307 - 'Curated reader-facing guidance.\n',
308 - );
309 - expect(snapshot.manifest.guides[0]?.verifyIgnoreToolSlugs).toEqual([
310 - 'GITHUB_REMOVED_TOOL',
311 - ]);
312 - expect(snapshot.manifest.guides[0]?.relatedGuides).toEqual(['related-guide']);
313 - expect(snapshot.manifest.guides[0]?.externalResources).toEqual([
314 - 'https://example.com/reference',
315 - ]);
316 - expect(snapshot.manifest.guides[0]?.featured).toBe(true);
317 - });
318 -
319 - test('regenerates an unchanged source when the previous guide recorded stale headings', () => {
320 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
321 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
322 - const initial = buildSupportKnowledgeSnapshot({
323 - sourceRoot,
324 - sourceCommit: 'initial',
325 - now: new Date('2026-08-17T00:00:00Z'),
326 - });
327 -
328 - const snapshot = buildSupportKnowledgeSnapshot({
329 - sourceRoot,
330 - sourceCommit: 'next',
331 - previousManifest: previousManifest(),
332 - previousSourceFiles: initial.sourceFiles,
333 - previousArticleFiles: new Map([
334 - ['github-troubleshooting.md', 'Stale curated guidance.\n'],
335 - ]),
336 - now: new Date('2026-08-18T00:00:00Z'),
337 - });
338 -
339 - expect(snapshot.articleFiles.get('toolkits-github.md')).toContain(
340 - 'Create the trigger instance directly',
341 - );
342 - expect(snapshot.articleFiles.get('toolkits-github.md')).not.toContain(
343 - 'Stale curated guidance',
344 - );
345 - });
346 -
347 - test('regenerates an article when its public source changes', () => {
348 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
349 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
350 - const initial = buildSupportKnowledgeSnapshot({
351 - sourceRoot,
352 - sourceCommit: 'initial',
353 - now: new Date('2026-08-17T00:00:00Z'),
354 - });
355 - writeDocument(
356 - sourceRoot,
357 - 'toolkits/github/public.md',
358 - publicDocument.replace('Provider tokens are redacted', 'Provider tokens stay redacted'),
359 - );
360 -
361 - const snapshot = buildSupportKnowledgeSnapshot({
362 - sourceRoot,
363 - sourceCommit: 'next',
364 - previousManifest: previousManifest(),
365 - previousSourceFiles: initial.sourceFiles,
366 - previousArticleFiles: new Map([
367 - ['github-troubleshooting.md', 'Stale curated guidance.\n'],
368 - ]),
369 - now: new Date('2026-08-18T00:00:00Z'),
370 - });
371 -
372 - expect(snapshot.articleFiles.get('toolkits-github.md')).toContain(
373 - 'Provider tokens stay redacted',
374 - );
375 - expect(snapshot.articleFiles.get('toolkits-github.md')).not.toContain(
376 - 'Stale curated guidance',
377 - );
378 - expect(snapshot.manifest.guides[0]?.verifyIgnoreToolSlugs).toEqual([
379 - 'GITHUB_REMOVED_TOOL',
380 - ]);
381 - expect(snapshot.manifest.guides[0]?.relatedGuides).toEqual(['related-guide']);
382 - expect(snapshot.manifest.guides[0]?.externalResources).toEqual([
383 - 'https://example.com/reference',
384 - ]);
385 - expect(snapshot.manifest.guides[0]?.featured).toBe(true);
386 - });
387 -
388 - test('assigns a consolidated guide legacy URLs to exactly one successor leaf', () => {
389 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
390 - writeDocument(
391 - sourceRoot,
392 - 'toolkits/discord/public.md',
393 - publicDocument.replaceAll('GitHub', 'Discord'),
394 - );
395 - writeDocument(
396 - sourceRoot,
397 - 'toolkits/discordbot/public.md',
398 - publicDocument.replaceAll('GitHub', 'Discord Bot'),
399 - );
400 - const previous = previousManifest();
401 - previous.guides = [{
402 - ...previous.guides[0]!,
403 - slug: 'discord-bot-troubleshooting',
404 - aliases: ['choose-discordbot-for-bot-token-operations'],
405 - sources: [
406 - { sourcePath: 'toolkits/discord/public.md', sourceHeading: 'Create triggers directly' },
407 - { sourcePath: 'toolkits/discordbot/public.md', sourceHeading: 'Tokens are redacted' },
408 - { sourcePath: 'toolkits/discordbot/public.md', sourceHeading: 'Create triggers directly' },
409 - ],
410 - }];
411 -
412 - const snapshot = buildSupportKnowledgeSnapshot({
413 - sourceRoot,
414 - sourceCommit: 'abc1234',
415 - previousManifest: previous,
416 - now: new Date('2026-08-17T00:00:00Z'),
417 - });
418 - const discord = snapshot.manifest.guides.find(guide => guide.slug === 'toolkits-discord');
419 - const discordBot = snapshot.manifest.guides.find(guide => guide.slug === 'toolkits-discordbot');
420 -
421 - expect(discord?.aliases).toEqual([]);
422 - expect(discordBot?.aliases).toEqual([
423 - '/kb/authentication/discord-bot-troubleshooting',
424 - 'choose-discordbot-for-bot-token-operations',
425 - 'discord-bot-troubleshooting',
426 - ]);
427 - });
428 -
429 - test('does not invent legacy category URLs after the support snapshot is established', () => {
430 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
431 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
432 - const previous = previousManifest();
433 - previous.source.repository = 'ComposioHQ/support-knowledge';
434 -
435 - const snapshot = buildSupportKnowledgeSnapshot({
436 - sourceRoot,
437 - sourceCommit: 'next',
438 - previousManifest: previous,
439 - now: new Date('2026-08-18T00:00:00Z'),
440 - });
441 -
442 - expect(snapshot.manifest.guides[0]?.aliases).toEqual([
443 - 'github-troubleshooting',
444 - 'old-github-answer',
445 - ]);
446 - expect(snapshot.manifest.guides[0]?.aliases).not.toContain(
447 - '/kb/authentication/github-troubleshooting',
448 - );
449 - });
450 -
451 - test('rejects a classification that does not match the leaf filename', () => {
452 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
453 - writeDocument(sourceRoot, 'toolkits/github/public.md', customerSafeDocument);
454 -
455 - expect(() => buildSupportKnowledgeSnapshot({
456 - sourceRoot,
457 - sourceCommit: 'abc1234',
458 - now: new Date('2026-08-17T00:00:00Z'),
459 - })).toThrow('classification does not match filename');
460 - });
461 -
462 - test('requires atomic level-two answer sections', () => {
463 - const withoutSections = publicDocument.replace(
464 - /## Tokens are redacted[\s\S]*/,
465 - 'Provider tokens are redacted.\n',
466 - );
467 -
468 - expect(() => parseSupportKnowledgeDocument(
469 - withoutSections,
470 - 'toolkits/github/public.md',
471 - )).toThrow('at least one level-two answer section');
472 - });
473 -
474 - test('keeps the previous snapshot intact until staged validation succeeds', () => {
475 - const sourceRoot = mkdtempSync(join(tmpdir(), 'support-knowledge-import-'));
476 - writeDocument(sourceRoot, 'toolkits/github/public.md', publicDocument);
477 - const snapshot = buildSupportKnowledgeSnapshot({
478 - sourceRoot,
479 - sourceCommit: 'abc1234',
480 - now: new Date('2026-08-17T00:00:00Z'),
481 - });
482 - const destinationParent = mkdtempSync(join(tmpdir(), 'support-knowledge-destination-'));
483 - const targetRoot = join(destinationParent, 'kb');
484 - mkdirSync(targetRoot, { recursive: true });
485 - writeFileSync(join(targetRoot, 'previous.txt'), 'keep me', 'utf8');
486 - mkdirSync(join(targetRoot, 'external-sources'), { recursive: true });
487 - writeFileSync(
488 - join(targetRoot, 'external-sources/auth-guides.json'),
489 - '{"preserve":true}\n',
490 - 'utf8',
491 - );
492 - writeFileSync(
493 - join(targetRoot, 'semantic-index.json'),
494 - '{"records":[{"id":"existing-vector"}]}\n',
495 - 'utf8',
496 - );
497 -
498 - expect(() => writeSupportKnowledgeSnapshot({
499 - snapshot,
500 - targetRoot,
501 - validate: () => { throw new Error('staged snapshot is invalid'); },
502 - })).toThrow('staged snapshot is invalid');
503 - expect(readFileSync(join(targetRoot, 'previous.txt'), 'utf8')).toBe('keep me');
504 -
505 - writeSupportKnowledgeSnapshot({ snapshot, targetRoot, validate: () => undefined });
506 - expect(existsSync(join(targetRoot, 'previous.txt'))).toBe(false);
507 - expect(JSON.parse(readFileSync(join(targetRoot, 'manifest.json'), 'utf8')).source).toEqual({
508 - repository: 'ComposioHQ/support-knowledge',
509 - commit: 'abc1234',
510 - capturedAt: '2026-08-17',
511 - contentHash: expect.stringMatching(/^sha256:[a-f0-9]{64}$/),
512 - });
513 - expect(readFileSync(join(targetRoot, 'articles/toolkits-github.md'), 'utf8')).toContain(
514 - '## Tokens are redacted',
515 - );
516 - expect(readFileSync(
517 - join(targetRoot, 'external-sources/auth-guides.json'),
518 - 'utf8',
519 - )).toBe('{"preserve":true}\n');
520 - expect(readFileSync(join(targetRoot, 'semantic-index.json'), 'utf8')).toBe(
521 - '{"records":[{"id":"existing-vector"}]}\n',
522 - );
523 - });
524 -});
docs/tests/static/kb-publish-workflow.test.ts
+44 -112
@@ -15,15 +15,10 @@ const workflows = {
15 publish: workflowSchema.parse(Bun.YAML.parse(readFileSync(
16 resolve(process.cwd(), '..', '.github/workflows/docs-kb-publish.yml'), 'utf8',
17 ))),
18 - refresh: workflowSchema.parse(Bun.YAML.parse(readFileSync(
19 - resolve(process.cwd(), '..', '.github/workflows/docs-update-kb.yml'), 'utf8',
20 - ))),
18 };
19
23 -function runStep(
24 - name: string, root: string, env: Record<string, string> = {}, job: 'publish' | 'refresh' = 'publish',
25 -) {
26 - const definition = workflows[job].jobs[job]!;
20 +function runStep(name: string, root: string, env: Record<string, string> = {}) {
21 + const definition = workflows.publish.jobs.publish!;
22 const step = definition.steps.find(step => step.name === name);
23 const script = step?.run;
24 if (!script) throw new Error(`Missing workflow step: ${name}`);
@@ -38,8 +33,6 @@ function runStep(
33 PATH: `${join(root, 'bin')}:${process.env.PATH}`,
34 FIXTURE_ROOT: root,
35 RUNNER_TEMP: root,
41 - GH_REPO: 'ComposioHQ/composio',
42 - PUBLISH_BRANCH: job === 'publish' ? 'docs/kb-front-desk-2' : 'docs/auto-update-kb',
36 GUIDE_SLUG: 'sdk-example',
37 ...env,
38 },
@@ -49,25 +42,6 @@ function runStep(
42 function fixture() {
43 const root = mkdtempSync(join(tmpdir(), 'kb-publication-'));
44 mkdirSync(join(root, 'bin'));
52 - writeFileSync(join(root, 'calls'), '');
53 - writeFileSync(join(root, 'sleeps'), '');
54 - writeFileSync(join(root, 'bin/gh'), `#!/bin/bash
55 -set -euo pipefail
56 -echo called >> "$FIXTURE_ROOT/calls"
57 -if [ "\${FAIL_API:-false}" = true ]; then exit 1; fi
58 -if [[ " $* " == *" --paginate "* ]]; then
59 - cat "$FIXTURE_ROOT/current.jsonl"
60 -else
61 - head -n 1 "$FIXTURE_ROOT/current.jsonl"
62 -fi | jq -r "\${@: -1}"
63 -`, { mode: 0o755 });
64 - writeFileSync(join(root, 'bin/sleep'), `#!/bin/bash
65 -set -euo pipefail
66 -echo slept >> "$FIXTURE_ROOT/sleeps"
67 -if [ -f "$FIXTURE_ROOT/after.jsonl" ]; then
68 - cp "$FIXTURE_ROOT/after.jsonl" "$FIXTURE_ROOT/current.jsonl"
69 -fi
70 -`, { mode: 0o755 });
45 writeFileSync(join(root, 'bin/bun'), `#!/bin/bash
46 set -euo pipefail
47 if [ "$2" = verify:kb ]; then
@@ -78,92 +52,37 @@ fi
52 return root;
53 }
54
81 -const earlierPublication = {
82 - head: { ref: 'docs/kb-front-desk-1', repo: { full_name: 'ComposioHQ/composio' } },
83 - html_url: 'https://github.com/ComposioHQ/composio/pull/1',
84 -};
85 -
55 describe('KB publication workflow', () => {
87 - test('waits for an earlier publication across pages while allowing the current draft and unrelated PRs', () => {
88 - const root = fixture();
89 - try {
90 - const unrelated = { head: { ref: 'docs/unrelated' }, html_url: 'unrelated' };
91 - const currentDraft = { head: { ref: 'docs/kb-front-desk-2', repo: { full_name: 'ComposioHQ/composio' } }, html_url: 'current' };
92 - writeFileSync(join(root, 'current.jsonl'),
93 - `${JSON.stringify([unrelated, currentDraft])}\n${JSON.stringify([earlierPublication])}\n`);
94 - writeFileSync(join(root, 'after.jsonl'), `${JSON.stringify([unrelated, currentDraft])}\n`);
95 -
96 - const result = runStep('Wait for earlier KB publications', root);
97 -
98 - expect(result.status).toBe(0);
99 - expect(result.stdout).toContain(earlierPublication.html_url);
100 - expect(result.stdout).not.toContain('unrelated');
101 - expect(result.stdout).not.toContain('current');
102 - expect(readFileSync(join(root, 'calls'), 'utf8').trim().split('\n')).toHaveLength(2);
103 - expect(readFileSync(join(root, 'sleeps'), 'utf8').trim().split('\n')).toHaveLength(1);
104 - } finally {
105 - rmSync(root, { recursive: true, force: true });
106 - }
107 - });
108 -
109 - test.each(['publish', 'refresh'] as const)('%s ignores fork PRs that imitate publication branches', job => {
110 - const root = fixture();
111 - try {
112 - const forkPrs = ['docs/kb-front-desk-hold', 'docs/auto-update-kb'].map(ref => ({
113 - head: { ref, repo: { full_name: 'outsider/composio' } }, html_url: 'fork-pr',
114 - }));
115 - writeFileSync(join(root, 'current.jsonl'), JSON.stringify(forkPrs));
116 - const result = runStep('Wait for earlier KB publications', root, {}, job);
117 - expect(result.status).toBe(0);
118 - expect(result.stdout).not.toContain('fork-pr');
119 - expect(readFileSync(join(root, 'sleeps'), 'utf8')).toBe('');
120 - } finally {
121 - rmSync(root, { recursive: true, force: true });
122 - }
123 - });
124 -
125 - test.each([
126 - ['publish', 'docs/auto-update-kb'],
127 - ['refresh', 'docs/kb-front-desk-1'],
128 - ] as const)('%s waits for the other publication path to merge', (job, ref) => {
129 - const root = fixture();
130 - try {
131 - writeFileSync(join(root, 'current.jsonl'), JSON.stringify([{
132 - head: { ref, repo: { full_name: 'ComposioHQ/composio' } }, html_url: 'earlier-kb-publication',
133 - }]));
134 - writeFileSync(join(root, 'after.jsonl'), '[]');
135 - const result = runStep('Wait for earlier KB publications', root, {}, job);
136 - expect(result.status).toBe(0);
137 - expect(result.stdout).toContain('earlier-kb-publication');
138 - expect(readFileSync(join(root, 'calls'), 'utf8').trim().split('\n')).toHaveLength(2);
139 - } finally {
140 - rmSync(root, { recursive: true, force: true });
141 - }
142 - });
143 -
144 - test('fails with a recovery instruction when an earlier publication stays open', () => {
145 - const root = fixture();
146 - try {
147 - writeFileSync(join(root, 'current.jsonl'), `${JSON.stringify([earlierPublication])}\n`);
148 -
149 - const result = runStep('Wait for earlier KB publications', root);
150 -
151 - expect(result.status).toBe(1);
152 - expect(result.stderr).toContain('Merge or close them, then rerun this workflow.');
153 - expect(readFileSync(join(root, 'calls'), 'utf8').trim().split('\n')).toHaveLength(60);
154 - } finally {
155 - rmSync(root, { recursive: true, force: true });
156 - }
56 + test('opens a PR for review and never merges it or waits on other KB PRs', () => {
57 + const steps = workflows.publish.jobs.publish!.steps;
58 + const raw = readFileSync(resolve(process.cwd(), '..', '.github/workflows/docs-kb-publish.yml'), 'utf8');
59 +
60 + expect(steps.map(step => step.name)).not.toContain('Wait for earlier KB publications');
61 + expect(steps.map(step => step.name)).not.toContain('Merge once checks pass');
62 + expect(raw).not.toContain('gh pr merge');
63 + expect(raw).not.toContain('docs/content/kb/');
64 });
65
159 - test('stops on an API failure instead of assuming no earlier publication exists', () => {
66 + test('names the PR branch from a checked portal or Zen request', () => {
67 const root = fixture();
68 try {
162 - const result = runStep('Wait for earlier KB publications', root, { FAIL_API: 'true' });
163 -
164 - expect(result.status).toBe(1);
165 - expect(readFileSync(join(root, 'calls'), 'utf8').trim().split('\n')).toHaveLength(1);
166 - expect(readFileSync(join(root, 'sleeps'), 'utf8')).toBe('');
69 + const branchFor = (env: Record<string, string>) => {
70 + writeFileSync(join(root, 'output'), '');
71 + const result = runStep('Check request', root, { GITHUB_OUTPUT: join(root, 'output'), ...env });
72 + return result.status === 0 ? readFileSync(join(root, 'output'), 'utf8').trim() : null;
73 + };
74 + const zen = {
75 + SOURCE: 'zen', REQUEST_ID: 'zen-composiohq-composio-5340-1',
76 + ORIGIN_URL: 'https://github.com/ComposioHQ/composio/pull/5340', ORIGIN_AUTHOR: 'octo-cat',
77 + };
78 +
79 + expect(branchFor({ DRAFT_ID: '12' })).toBe('branch=docs/kb-front-desk-12');
80 + expect(branchFor(zen)).toBe('branch=docs/kb-zen-composiohq-composio-5340-1');
81 + expect(branchFor({ DRAFT_ID: '12; rm -rf /' })).toBeNull();
82 + expect(branchFor({ ...zen, REQUEST_ID: 'Zen/../main' })).toBeNull();
83 + expect(branchFor({ ...zen, ORIGIN_URL: 'https://evil.example/pull/1' })).toBeNull();
84 + expect(branchFor({ ...zen, ORIGIN_AUTHOR: 'a b\nc' })).toBeNull();
85 + expect(branchFor({ SOURCE: 'other', DRAFT_ID: '12' })).toBeNull();
86 } finally {
87 rmSync(root, { recursive: true, force: true });
88 }
@@ -185,7 +104,7 @@ describe('KB publication workflow', () => {
104 }
105 });
106
188 - test('allows an approval when only another guide has support-facing prose', () => {
107 + test('allows a proposal when only another guide has support-facing prose', () => {
108 const root = fixture();
109 try {
110 writeFileSync(join(root, 'report.json'), JSON.stringify({
@@ -197,7 +116,7 @@ describe('KB publication workflow', () => {
116 }
117 });
118
200 - test('allows advisory review cohorts while retaining verification errors', () => {
119 + test("blocks on this guide's or KB-wide errors, not on other guides' errors", () => {
120 const root = fixture();
121 try {
122 writeFileSync(join(root, 'report.json'), JSON.stringify({
@@ -206,9 +125,22 @@ describe('KB publication workflow', () => {
125 expect(runStep('Regenerate KB pages', root).status).toBe(0);
126
127 writeFileSync(join(root, 'report.json'), JSON.stringify({
209 - findings: [{ severity: 'error', kind: 'unknown-tool-slug' }],
128 + findings: [{ severity: 'error', kind: 'review-window-expired', guideSlug: 'other-guide' }],
129 + }));
130 + expect(runStep('Regenerate KB pages', root, { VERIFY_EXIT: '1' }).status).toBe(0);
131 +
132 + writeFileSync(join(root, 'report.json'), JSON.stringify({
133 + findings: [{ severity: 'error', kind: 'unknown-tool-slug', guideSlug: 'sdk-example' }],
134 + }));
135 + expect(runStep('Regenerate KB pages', root, { VERIFY_EXIT: '1' }).status).toBe(1);
136 +
137 + writeFileSync(join(root, 'report.json'), JSON.stringify({
138 + findings: [{ severity: 'error', kind: 'manifest-error', guideSlug: '' }],
139 }));
140 expect(runStep('Regenerate KB pages', root, { VERIFY_EXIT: '1' }).status).toBe(1);
141 +
142 + writeFileSync(join(root, 'report.json'), 'crashed');
143 + expect(runStep('Regenerate KB pages', root, { VERIFY_EXIT: '1' }).status).not.toBe(0);
144 } finally {
145 rmSync(root, { recursive: true, force: true });
146 }
docs/tests/static/kb-publish.test.ts
+2 -3
@@ -17,17 +17,16 @@ function fixture(): string {
17 roots.push(root);
18 mkdirSync(join(root, 'kb/source'), { recursive: true });
19 mkdirSync(join(root, 'kb/articles'));
20 + mkdirSync(join(root, 'kb/guides'));
21 writeFileSync(join(root, 'kb/manifest.json'), JSON.stringify({
22 schemaVersion: 2,
22 - source: { repository: 'ComposioHQ/support-knowledge', commit: 'initial', capturedAt: '2026-08-18', contentHash: 'sha256:fixture' },
23 topics: [{ slug: 'authentication', title: 'Authentication', description: 'Authentication guidance.', featuredRank: 1 }],
24 - guides: [],
24 }));
25 return root;
26 }
27
28 function guide(root: string) {
30 - return JSON.parse(readFileSync(join(root, 'kb/manifest.json'), 'utf8')).guides[0];
29 + return JSON.parse(readFileSync(join(root, 'kb/guides/sdk-example.json'), 'utf8'));
30 }
31
32 function contents(root: string): Map<string, string> {
docs/tests/static/kb-resolve-refresh-source.test.ts deleted
-176
@@ -1,176 +0,0 @@
1 -import { describe, expect, test } from 'bun:test';
2 -import { spawnSync } from 'node:child_process';
3 -import { mkdirSync, mkdtempSync, readFileSync, rmSync, writeFileSync } from 'node:fs';
4 -import { tmpdir } from 'node:os';
5 -import { join, resolve } from 'node:path';
6 -
7 -const resolverPath = resolve(process.cwd(), 'scripts', 'resolve-kb-refresh-source.sh');
8 -
9 -function git(root: string, ...args: string[]): string {
10 - const result = spawnSync('git', args, { cwd: root, encoding: 'utf8' });
11 - if (result.status !== 0) throw new Error(result.stderr);
12 - return result.stdout.trim();
13 -}
14 -
15 -function runResolver(
16 - cwd: string,
17 - env: Record<string, string>,
18 -): { status: number | null; output: string; stdout: string; stderr: string } {
19 - const outputPath = join(cwd, 'github-output.txt');
20 - writeFileSync(outputPath, '', 'utf8');
21 - const result = spawnSync('bash', [resolverPath], {
22 - cwd,
23 - encoding: 'utf8',
24 - env: { ...process.env, ...env, GITHUB_OUTPUT: outputPath },
25 - });
26 - return {
27 - status: result.status,
28 - output: readFileSync(outputPath, 'utf8'),
29 - stdout: result.stdout,
30 - stderr: result.stderr,
31 - };
32 -}
33 -
34 -function createFixture(): {
35 - root: string;
36 - sourceRoot: string;
37 - docsRoot: string;
38 - currentCommit: string;
39 -} {
40 - const root = mkdtempSync(join(tmpdir(), 'kb-resolve-source-'));
41 - const sourceRoot = join(root, 'support-knowledge');
42 - const docsRoot = join(root, 'docs');
43 - mkdirSync(join(sourceRoot, 'toolkits', 'github'), { recursive: true });
44 - mkdirSync(join(docsRoot, 'kb'), { recursive: true });
45 -
46 - git(sourceRoot, 'init');
47 - git(sourceRoot, 'config', 'user.name', 'KB Workflow Test');
48 - git(sourceRoot, 'config', 'user.email', 'kb-workflow@example.com');
49 - writeFileSync(join(sourceRoot, 'toolkits/github/public.md'), 'public v1\n', 'utf8');
50 - writeFileSync(
51 - join(sourceRoot, 'toolkits/github/customer-safe.md'),
52 - 'customer-safe v1\n',
53 - 'utf8',
54 - );
55 - git(sourceRoot, 'add', '.');
56 - git(sourceRoot, 'commit', '-m', 'initial knowledge');
57 - const currentCommit = git(sourceRoot, 'rev-parse', 'HEAD');
58 - writeFileSync(
59 - join(docsRoot, 'kb/manifest.json'),
60 - `${JSON.stringify({ source: { commit: currentCommit } })}\n`,
61 - 'utf8',
62 - );
63 -
64 - return { root, sourceRoot, docsRoot, currentCommit };
65 -}
66 -
67 -describe('support knowledge refresh source resolver', () => {
68 - test('ignores customer-safe-only changes and coalesces delayed events to the newest public change', () => {
69 - const fixture = createFixture();
70 -
71 - try {
72 - writeFileSync(
73 - join(fixture.sourceRoot, 'toolkits/github/customer-safe.md'),
74 - 'customer-safe v2\n',
75 - 'utf8',
76 - );
77 - git(fixture.sourceRoot, 'add', '.');
78 - git(fixture.sourceRoot, 'commit', '-m', 'customer-safe only');
79 - git(fixture.sourceRoot, 'update-ref', 'refs/remotes/origin/main', 'HEAD');
80 -
81 - const privateOnly = runResolver(fixture.docsRoot, {
82 - SOURCE_ROOT: fixture.sourceRoot,
83 - HAVE_UPSTREAM: 'true',
84 - EVENT_NAME: 'schedule',
85 - REQUESTED_SOURCE_COMMIT: '',
86 - });
87 - expect(privateOnly.status).toBe(0);
88 - expect(privateOnly.output).toBe(
89 - `commit=${fixture.currentCommit}\nupstream_changed=false\n`,
90 - );
91 -
92 - writeFileSync(
93 - join(fixture.sourceRoot, 'toolkits/github/public.md'),
94 - 'public v2\n',
95 - 'utf8',
96 - );
97 - git(fixture.sourceRoot, 'add', '.');
98 - git(fixture.sourceRoot, 'commit', '-m', 'public knowledge');
99 - const publicCommit = git(fixture.sourceRoot, 'rev-parse', 'HEAD');
100 - writeFileSync(
101 - join(fixture.sourceRoot, 'toolkits/github/customer-safe.md'),
102 - 'customer-safe v3\n',
103 - 'utf8',
104 - );
105 - git(fixture.sourceRoot, 'add', '.');
106 - git(fixture.sourceRoot, 'commit', '-m', 'customer-safe after public knowledge');
107 - git(fixture.sourceRoot, 'update-ref', 'refs/remotes/origin/main', 'HEAD');
108 -
109 - const publicThenPrivate = runResolver(fixture.docsRoot, {
110 - SOURCE_ROOT: fixture.sourceRoot,
111 - HAVE_UPSTREAM: 'true',
112 - EVENT_NAME: 'schedule',
113 - REQUESTED_SOURCE_COMMIT: '',
114 - });
115 - expect(publicThenPrivate.status).toBe(0);
116 - expect(publicThenPrivate.output).toBe(
117 - `commit=${fixture.currentCommit}\ncommit=${publicCommit}\nupstream_changed=true\n`,
118 - );
119 -
120 - writeFileSync(
121 - join(fixture.sourceRoot, 'toolkits/github/public.md'),
122 - 'public v3\n',
123 - 'utf8',
124 - );
125 - git(fixture.sourceRoot, 'add', '.');
126 - git(fixture.sourceRoot, 'commit', '-m', 'newer public knowledge');
127 - const newestPublicCommit = git(fixture.sourceRoot, 'rev-parse', 'HEAD');
128 - git(fixture.sourceRoot, 'update-ref', 'refs/remotes/origin/main', 'HEAD');
129 - git(fixture.sourceRoot, 'checkout', '--detach', publicCommit);
130 -
131 - const delayedDispatch = runResolver(fixture.docsRoot, {
132 - SOURCE_ROOT: fixture.sourceRoot,
133 - HAVE_UPSTREAM: 'true',
134 - EVENT_NAME: 'repository_dispatch',
135 - REQUESTED_SOURCE_COMMIT: publicCommit,
136 - });
137 - expect(delayedDispatch.status).toBe(0);
138 - expect(delayedDispatch.output).toBe(
139 - `commit=${fixture.currentCommit}\ncommit=${newestPublicCommit}\nupstream_changed=true\n`,
140 - );
141 - expect(git(fixture.sourceRoot, 'rev-parse', 'HEAD')).toBe(newestPublicCommit);
142 - } finally {
143 - rmSync(fixture.root, { recursive: true, force: true });
144 - }
145 - });
146 -
147 - test('rejects dispatched refreshes without a pinned commit or upstream access', () => {
148 - const fixture = createFixture();
149 -
150 - try {
151 - const unpinned = runResolver(fixture.docsRoot, {
152 - SOURCE_ROOT: fixture.sourceRoot,
153 - HAVE_UPSTREAM: 'true',
154 - EVENT_NAME: 'repository_dispatch',
155 - REQUESTED_SOURCE_COMMIT: '',
156 - });
157 - expect(unpinned.status).toBe(1);
158 - expect(unpinned.stdout).toContain(
159 - 'Dispatched support knowledge refresh is missing source_commit.',
160 - );
161 -
162 - const unreadable = runResolver(fixture.docsRoot, {
163 - SOURCE_ROOT: fixture.sourceRoot,
164 - HAVE_UPSTREAM: 'false',
165 - EVENT_NAME: 'repository_dispatch',
166 - REQUESTED_SOURCE_COMMIT: fixture.currentCommit,
167 - });
168 - expect(unreadable.status).toBe(1);
169 - expect(unreadable.stdout).toContain(
170 - 'Cannot process a dispatched support knowledge refresh without an upstream token.',
171 - );
172 - } finally {
173 - rmSync(fixture.root, { recursive: true, force: true });
174 - }
175 - });
176 -});
docs/tests/static/kb-semantic-artifact.test.ts
+5 -21
@@ -86,11 +86,7 @@ function artifact(): KnowledgeSemanticArtifact {
86 provider: 'openai',
87 model: 'text-embedding-3-small',
88 dimensions: 2,
89 - source: {
90 - repository: 'ComposioHQ/support-knowledge',
91 - supportKnowledgeCommit: 'abc1234',
92 - docsContentHash: 'docs-hash',
93 - },
89 + source: { docsContentHash: 'docs-hash' },
90 builtAt: '2026-08-17T00:00:00.000Z',
91 records: [
92 semanticRecord('exact-x', 'Exact X', 'hash-x'),
@@ -165,7 +161,6 @@ Content: Provider tokens are redacted from connected-account responses.`);
161
162 describe('KB semantic artifact', () => {
163 test.each([
168 - { supportKnowledgeCommit: 'new-commit' },
164 { docsContentHash: 'new-docs-hash' },
165 { contentHashes: new Map([['exact-x', 'changed-hash']]) },
166 { contentHashes: new Map([
@@ -174,7 +169,6 @@ describe('KB semantic artifact', () => {
169 ])('classifies corpus drift as stale: %j', drift => {
170 expect(() => validateSemanticArtifact(artifact(), {
171 dimensions: 2,
177 - supportKnowledgeCommit: 'abc1234',
172 ...drift,
173 })).toThrow(SemanticArtifactStaleError);
174 });
@@ -191,7 +185,6 @@ describe('KB semantic artifact', () => {
185 try {
186 validateSemanticArtifact({ ...artifact(), ...corruption } as KnowledgeSemanticArtifact, {
187 dimensions: 2,
194 - supportKnowledgeCommit: 'new-commit',
188 docsContentHash: 'new-docs-hash',
189 });
190 } catch (error) {
@@ -210,7 +203,6 @@ describe('KB semantic artifact', () => {
203 const value = artifact();
204 expect(validateSemanticArtifact(value, {
205 dimensions: 2,
213 - supportKnowledgeCommit: 'abc1234',
206 docsContentHash: 'docs-hash',
207 contentHashes: new Map([
208 ['exact-x', 'hash-x'],
@@ -221,11 +213,10 @@ describe('KB semantic artifact', () => {
213
214 expect(() => validateSemanticArtifact(
215 { ...value, model: 'another-model' },
224 - { dimensions: 2, supportKnowledgeCommit: 'abc1234', docsContentHash: 'docs-hash' },
216 + { dimensions: 2, docsContentHash: 'docs-hash' },
217 )).toThrow('model mismatch');
218 expect(() => validateSemanticArtifact(value, {
219 dimensions: 2,
228 - supportKnowledgeCommit: 'abc1234',
220 docsContentHash: 'docs-hash',
221 contentHashes: new Map([
222 ['exact-x', 'tampered'],
@@ -237,11 +228,10 @@ describe('KB semantic artifact', () => {
228 const nonUnit = { ...value, vectorsBase64: encodeVectors([[2, 0], [0, 1], [0, 1]]) };
229 expect(() => validateSemanticArtifact(
230 nonUnit,
240 - { dimensions: 2, supportKnowledgeCommit: 'abc1234', docsContentHash: 'docs-hash' },
231 + { dimensions: 2, docsContentHash: 'docs-hash' },
232 )).toThrow('not normalized');
233 expect(() => validateSemanticArtifact(value, {
234 dimensions: 2,
244 - supportKnowledgeCommit: 'abc1234',
235 docsContentHash: 'tampered-docs-hash',
236 })).toThrow('docs content hash mismatch');
237
@@ -249,7 +239,6 @@ describe('KB semantic artifact', () => {
239 parsed.records[0]!.sourceType = 'toolkit' as never;
240 expect(() => validateSemanticArtifact(parsed, {
241 dimensions: 2,
252 - supportKnowledgeCommit: 'abc1234',
242 docsContentHash: 'docs-hash',
243 })).toThrow('source type');
244 });
@@ -318,11 +307,7 @@ describe('KB semantic artifact', () => {
307 provider: 'openai',
308 model: 'text-embedding-3-small',
309 dimensions: 256,
321 - source: {
322 - repository: 'ComposioHQ/support-knowledge',
323 - supportKnowledgeCommit: 'old-commit',
324 - docsContentHash: 'old-docs-hash',
325 - },
310 + source: { docsContentHash: 'old-docs-hash' },
311 builtAt: '2026-08-16T00:00:00.000Z',
312 records: [unchangedMetadata],
313 vectorsBase64: encodeVectors([[1, ...Array.from({ length: 255 }, () => 0)]]),
@@ -331,7 +316,6 @@ describe('KB semantic artifact', () => {
316
317 const built = await buildSemanticArtifact({
318 records: [changed, unchanged],
334 - supportKnowledgeCommit: 'new-commit',
319 docsContentHash: 'new-docs-hash',
320 builtAt: '2026-08-17T00:00:00.000Z',
321 previousArtifact: prior,
@@ -345,6 +329,6 @@ describe('KB semantic artifact', () => {
329 expect(built.records.map(record => record.objectID)).toEqual(['a', 'b']);
330 const vectors = decodeVectors(built.vectorsBase64, 2, 256);
331 expect([vectors[0], vectors[1], vectors[256], vectors[257]]).toEqual([1, 0, 0, 1]);
348 - expect(built.source.supportKnowledgeCommit).toBe('new-commit');
332 + expect(built.source).toEqual({ docsContentHash: 'new-docs-hash' });
333 });
334 });
docs/tests/static/kb-update-workflow.test.ts
+24 -76
@@ -24,7 +24,6 @@ const dataWorkflowPath = resolve(
24 'workflows',
25 'docs-update-data.yml',
26 );
27 -const importerPath = resolve(process.cwd(), 'scripts', 'import-support-knowledge.ts');
27
28 interface WorkflowStep {
29 name?: string;
@@ -54,7 +53,7 @@ function workflowSteps(path: string, job: string): WorkflowStep[] {
53 return workflow.jobs?.[job]?.steps ?? [];
54 }
55
57 -describe('support knowledge refresh workflow', () => {
56 +describe('KB semantic artifact workflows', () => {
57 test('allows stale embeddings in PR checks without ignoring artifact errors', () => {
58 const check = workflowSteps(docsTestsWorkflowPath, 'test')
59 .find(step => step.name === 'Check KB semantic artifact');
@@ -239,74 +238,33 @@ echo "head_ref=$live_head_ref" >> "$GITHUB_OUTPUT"`);
238 );
239 });
240
242 - test('imports the private upstream and proposes every generated KB artifact', () => {
241 + test('repairs the semantic artifact on a schedule without any upstream source', () => {
242 const workflow = readFileSync(workflowPath, 'utf8');
243 + const parsed = Bun.YAML.parse(workflow) as { on?: Record<string, unknown> };
244
245 - expect(workflow).toContain('repository: ComposioHQ/support-knowledge');
246 - expect(workflow).toContain('bun run import:kb');
245 + expect(Object.keys(parsed.on ?? {}).sort()).toEqual(['schedule', 'workflow_dispatch']);
246 + expect(workflow).not.toContain('support-knowledge');
247 expect(workflow).toContain('bun run build:kb-semantic');
248 - expect(workflow).toContain('bun run verify:kb');
249 - expect(workflow).toContain('docs/kb/');
250 - expect(workflow).toContain('docs/content/kb/');
248 + expect(workflow).toContain('bun run check:kb-semantic');
249 expect(workflow).toContain('branch: docs/auto-update-kb');
250 expect(workflow).toContain('base: next');
253 - expect(workflow).toContain('refresh:');
254 - expect(workflow).toContain('propose:');
255 - expect(workflow).toContain('needs: refresh');
256 - expect(workflow).toContain('id: upstream-token');
257 - expect(workflow).toContain('id: write-token');
258 - expect(workflow).toContain('permission-contents: read');
251 expect(workflow).toContain('persist-credentials: false');
260 - expect(workflow).toContain('actions/upload-artifact@');
261 - expect(workflow).toContain('actions/download-artifact@');
252 });
253
264 - test('passes dispatched source context to the tested resolver script', () => {
265 - const workflow = Bun.YAML.parse(readFileSync(workflowPath, 'utf8')) as {
266 - on?: {
267 - repository_dispatch?: { types?: string[] };
268 - workflow_dispatch?: unknown;
269 - };
270 - jobs?: Record<string, WorkflowJob>;
271 - };
272 - const steps = workflow.jobs?.refresh?.steps ?? [];
273 - const checkout = steps.find(step => step.name === 'Checkout support knowledge');
274 - const resolveSource = steps.find(step => step.name === 'Resolve upstream change');
275 -
276 - expect(workflow.on?.repository_dispatch?.types).toEqual(['support-knowledge-updated']);
277 - expect(workflow.on).toHaveProperty('workflow_dispatch');
278 - expect(checkout?.with?.ref).toBe(
279 - "${{ github.event_name == 'repository_dispatch' && github.event.client_payload.source_commit || 'main' }}",
280 - );
281 - expect(resolveSource?.env?.REQUESTED_SOURCE_COMMIT).toBe(
282 - "${{ github.event_name == 'repository_dispatch' && github.event.client_payload.source_commit || '' }}",
283 - );
284 - expect(resolveSource?.run).toBe('bash scripts/resolve-kb-refresh-source.sh');
285 - });
286 -
287 - test('serializes both KB writers before checkout and pins artifacts to their docs base', () => {
254 + test('serializes both KB writers and pins artifacts to their docs base', () => {
255 const workflow = Bun.YAML.parse(readFileSync(workflowPath, 'utf8')) as {
256 concurrency?: { group?: string; 'cancel-in-progress'?: boolean; queue?: string };
257 jobs?: Record<string, WorkflowJob>;
258 };
292 - const checkout = workflow.jobs?.refresh?.steps?.find(
293 - step => step.name === 'Checkout support knowledge',
294 - );
295 -
259 const publish = Bun.YAML.parse(readFileSync(
260 resolve(process.cwd(), '..', '.github/workflows/docs-kb-publish.yml'), 'utf8',
261 )) as { concurrency: { group: string }; jobs: Record<string, WorkflowJob> };
262 expect(workflow.concurrency?.group).toBe(publish.concurrency.group);
263 expect(workflow.concurrency?.['cancel-in-progress']).toBe(false);
264 expect(workflow.concurrency?.queue).toBe('max');
302 - expect(checkout?.with?.['fetch-depth']).toBe(0);
265 for (const job of [workflow.jobs?.refresh, publish.jobs.publish]) {
304 - const steps = job?.steps ?? [];
305 - const waitIndex = steps.findIndex(step => step.name === 'Wait for earlier KB publications');
306 - const checkoutIndex = steps.findIndex(step => step.name === 'Checkout docs repository');
307 - expect(waitIndex).toBeGreaterThanOrEqual(0);
308 - expect(waitIndex).toBeLessThan(checkoutIndex);
309 - expect(steps[checkoutIndex]?.with?.ref).toBe('next');
266 + const checkout = job?.steps?.find(step => step.name === 'Checkout docs repository');
267 + expect(checkout?.with?.ref).toBe('next');
268 }
269 const proposalCheckout = workflow.jobs?.propose?.steps?.find(
270 step => step.name === 'Checkout docs repository',
@@ -315,13 +273,13 @@ echo "head_ref=$live_head_ref" >> "$GITHUB_OUTPUT"`);
273 expect(proposalCheckout?.with?.ref).toBe('${{ needs.refresh.outputs.docs_base_sha }}');
274 });
275
318 - test('tracks failures until both refresh and PR proposal recover', () => {
276 + test('tracks failures until both rebuild and PR proposal recover', () => {
277 const workflow = Bun.YAML.parse(readFileSync(workflowPath, 'utf8')) as {
278 jobs?: Record<string, WorkflowJob>;
279 };
280 const reporter = workflow.jobs?.report;
323 - const failure = reporter?.steps?.find(step => step.name === 'Open KB refresh failure issue');
324 - const recovery = reporter?.steps?.find(step => step.name === 'Close KB refresh failure issue');
281 + const failure = reporter?.steps?.find(step => step.name === 'Open KB repair failure issue');
282 + const recovery = reporter?.steps?.find(step => step.name === 'Close KB repair failure issue');
283
284 expect(reporter?.needs).toEqual(['refresh', 'propose']);
285 expect(reporter?.if).toBe('always()');
@@ -339,14 +297,19 @@ echo "head_ref=$live_head_ref" >> "$GITHUB_OUTPUT"`);
297 expect(recovery?.run).toContain('gh issue close');
298 });
299
342 - test('downloads generated artifacts under the docs directory staged by the refresh PR', () => {
300 + test('transfers the semantic index to the exact path staged by the repair PR', () => {
301 + const upload = workflowSteps(workflowPath, 'refresh').find(
302 + step => step.name === 'Upload verified semantic artifact',
303 + );
304 const steps = workflowSteps(workflowPath, 'propose');
344 - const download = steps.find(step => step.name === 'Download verified KB artifacts');
345 - const createPullRequest = steps.find(step => step.name === 'Create refresh pull request');
346 -
347 - expect(download?.with?.path).toBe('docs');
348 - expect(String(createPullRequest?.with?.['add-paths'])).toContain('docs/kb/');
349 - expect(String(createPullRequest?.with?.['add-paths'])).toContain('docs/content/kb/');
305 + const download = steps.find(step => step.name === 'Download verified semantic artifact');
306 + const createPullRequest = steps.find(step => step.name === 'Create repair pull request');
307 +
308 + expect(upload?.with?.name).toBe('kb-semantic-repair');
309 + expect(download?.with?.name).toBe(upload?.with?.name);
310 + expect(upload?.with?.path).toBe('docs/kb/semantic-index.json');
311 + expect(download?.with?.path).toBe('docs/kb');
312 + expect(String(createPullRequest?.with?.['add-paths']).trim()).toBe(upload?.with?.path);
313 });
314
315 test('treats keyword-only production retrieval as a semantic health failure', () => {
@@ -360,14 +323,6 @@ echo "head_ref=$live_head_ref" >> "$GITHUB_OUTPUT"`);
323 expect(endpointCheck?.run).not.toContain('.mode == "keyword"');
324 });
325
363 - test('gives the existing freshness sweep read access to the pinned upstream', () => {
364 - const workflow = readFileSync(dataWorkflowPath, 'utf8');
365 -
366 - expect(workflow).toContain('repositories: support-knowledge');
367 - expect(workflow).toContain('id: source-token');
368 - expect(workflow).toContain('GH_TOKEN: ${{ steps.source-token.outputs.token }}');
369 - });
370 -
326 test('keeps verifier crashes separate from published-content freshness findings', () => {
327 const steps = workflowSteps(dataWorkflowPath, 'update-data');
328 const verifierHealth = steps.find(step => step.name === 'Track KB freshness verifier health');
@@ -380,11 +335,4 @@ echo "head_ref=$live_head_ref" >> "$GITHUB_OUTPUT"`);
335 expect(freshnessFindings?.if).toContain("steps.verify-kb.outputs.exit_code == '1'");
336 expect(freshnessFindings?.if).not.toContain("steps.verify-kb.outputs.exit_code != ''");
337 });
383 -
384 - test('treats upstream files as data instead of executing upstream code', () => {
385 - const importer = readFileSync(importerPath, 'utf8');
386 -
387 - expect(importer).not.toContain('scripts/validate-kb.py');
388 - expect(importer).not.toContain("spawnSync('python3'");
389 - });
338 });
docs/tests/static/kb-verify.test.ts
+2 -36
@@ -11,7 +11,7 @@ import {
11 verifyKb,
12 type CatalogToolkit,
13 } from '@/lib/kb/verify';
14 -import { getKbCatalog } from '@/lib/kb/repository';
14 +import { getKbCatalog, readKbManifest } from '@/lib/kb/repository';
15 import type { KbGuide, KbManifest } from '@/lib/kb/types';
16
17 const TOOLKITS: CatalogToolkit[] = [
@@ -39,12 +39,6 @@ const catalog = buildProductCatalog(TOOLKITS);
39
40 const MANIFEST: KbManifest = {
41 schemaVersion: 2,
42 - source: {
43 - repository: 'ComposioHQ/example-knowledge',
44 - commit: 'abc1234',
45 - capturedAt: '2026-07-22',
46 - contentHash: 'sha256:fixture',
47 - },
42 topics: [],
43 guides: [],
44 };
@@ -246,32 +240,6 @@ describe('verifyKb', () => {
240 expect(report.findings.some((entry) => entry.kind === 'verification-stale')).toBe(true);
241 });
242
249 - test('reports an unresolvable source pin', () => {
250 - const report = verifyKb({
251 - manifest: MANIFEST,
252 - catalog,
253 - now,
254 - guides: [guide({ slug: 'any', body: 'text' })],
255 - options: { sourcePinStatus: 'missing' },
256 - });
257 - const finding = report.findings.find((entry) => entry.kind === 'source-pin-unresolvable');
258 - expect(finding?.severity).toBe('warning');
259 - expect(finding?.detail).toContain('abc1234');
260 - });
261 -
262 - test('stays silent when the pin cannot be verified by this token', () => {
263 - for (const status of ['resolved', 'unverifiable'] as const) {
264 - const report = verifyKb({
265 - manifest: MANIFEST,
266 - catalog,
267 - now,
268 - guides: [guide({ slug: 'any', body: 'text' })],
269 - options: { sourcePinStatus: status },
270 - });
271 - expect(report.findings.some((entry) => entry.kind === 'source-pin-unresolvable')).toBe(false);
272 - }
273 - });
274 -
243 test('treats provider rate-limiting as inconclusive, not as rot', () => {
244 const body = 'see [docs](https://example.com/a) and [more](https://example.com/b)';
245 const report = verifyKb({
@@ -313,9 +281,7 @@ describe('live corpus', () => {
281 * Published prose belongs in `kb/articles`; `kb/source` must stay verbatim.
282 */
283 test('no published guide renders from the source snapshot', () => {
316 - const manifest = JSON.parse(
317 - readFileSync(join(process.cwd(), 'kb/manifest.json'), 'utf8')
318 - ) as { guides: Array<{ slug: string; state: string; articlePath?: string }> };
284 + const manifest = readKbManifest();
285 const rendersFromSource = manifest.guides
286 .filter((guide) => guide.state === 'published' && !guide.articlePath)
287 .map((guide) => guide.slug);
docs/tests/static/knowledge-corpus.test.ts
+2 -4
@@ -6,7 +6,7 @@ import { GET as getLlmsIndex } from '@/app/llms-index.txt/route';
6 import { getAlgoliaSearchDocuments, getDocsSearchIndexes } from '@/lib/search-index';
7 import * as searchIndexModule from '@/lib/search-index';
8 import { getLocalKnowledgeDiscoveryPaths } from '@/lib/knowledge/discovery';
9 -import { getPublishedKbGuides } from '@/lib/kb/repository';
9 +import { getPublishedKbGuides, readKbManifest } from '@/lib/kb/repository';
10 import type { KnowledgeSourceType } from '@/lib/knowledge/types';
11 import type { KbManifest } from '@/lib/kb/types';
12
@@ -208,9 +208,7 @@ describe('unified public knowledge corpus', () => {
208 });
209
210 test('accounts for every snapshot file and excludes retired guides from public discovery', async () => {
211 - const manifest = JSON.parse(
212 - readFileSync(join(process.cwd(), 'kb/manifest.json'), 'utf8'),
213 - ) as KbManifest;
211 + const manifest = readKbManifest();
212 const snapshotFiles = listFiles(join(process.cwd(), 'kb/source'));
213 const guideSourcePaths = [...new Set(
214 manifest.guides.flatMap(guide => guide.sources.map(source => source.sourcePath)),