docs: add toolkit versioning guidance for third-party integrations#2988
docs: add toolkit versioning guidance for third-party integrations#2988
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Claude finished @zen-agent's task in 50s —— View job Docs Review
The changes are clear and actionable. A developer following this guidance would understand the problem and know what to do. One issue worth flagging: Issue:
Version numbers in troubleshooting docs age poorly and mislead users who are trying to determine whether their installed version is affected. If these numbers are wrong or change, users on older versions will misread the situation. Recommend either removing the version callout or verifying them against the changelog. Everything else looks good — the callout placement in |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| ```bash | ||
| # REST API — list all tools for a toolkit (including newer versions) | ||
| curl 'https://backend.composio.dev/api/v3/tools?toolkit_slug=gladia&toolkit_versions=latest' \ |
There was a problem hiding this comment.
🛑 Gitleaks has detected a secret with rule-id curl-auth-header in commit b65f5daf1f60bcc654782fa67473ee59cf66a754.
If this secret is a true positive, please rotate the secret ASAP.
If this secret is a false positive, you can add the fingerprint below to your .gitleaksignore file and commit the change to this branch.
echo b65f5daf1f60bcc654782fa67473ee59cf66a754:docs/content/docs/tools-direct/toolkit-versioning.mdx:curl-auth-header:202 >> .gitleaksignore
cc @zen-agent
There was a problem hiding this comment.
Resolved — the commit referenced here (b65f5daf) was squashed out. The curl example now uses $COMPOSIO_API_KEY (env var reference) instead of a literal placeholder, so gitleaks no longer flags it. The secrets / Detect Secrets with Gitleaks check is passing on the current commit.
|
|
Claude finished @zen-agent's task in 59s —— View job Docs Review
One issue remains unaddressed from the previous review cycle: Issue:
If these versions are wrong or already outdated, users on older versions will misread the situation and draw wrong conclusions ("my SDK version is newer so why doesn't this work?"). The exact version cutoff isn't load-bearing for the user's action — they just need to know the SDK defaults to Fix — drop the version callout entirely: Everything else looks good — |
|
|
Claude finished @zen-agent's task in 58s —— View job Docs Review
One issue remains unaddressed from the previous two review cycles: Issue:
If these versions are wrong, users on older versions will misread the situation. The exact version cutoff isn't needed — users just need to know the SDK defaults to I made the fix locally (commit Fix to apply — change line 220 from: To: Everything else looks good — the |
|
…olkit versioning Users integrating via third-party platforms (MindPal, n8n, Make) see fewer tools than expected because the REST API defaults to the base version when toolkit_versions is not specified. Add explicit guidance for third-party integrations, a troubleshooting section, and a callout in the fetching-tools page clarifying the SDK vs REST API default behavior difference. Resolves T-9303. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Zen Agent <zen@composio.dev>
zen-agent
force-pushed
the
zen/docs-toolkit-versions-xso0s7
branch
from
8a5b4a1 to
47df94a
Compare
|
Claude finished @zen-agent's task in 1m 8s —— View job Docs Review
The changes in One issue remains from previous review cycles —
I made the fix locally (removing Fix — Everything else looks good — the |
Post-PR Status
|
|
Claude finished @Sushmithamallesh's task in 51s —— View job Docs Review
One issue remains from previous review cycles. The fix is straightforward — apply it manually: Issue:
Fix — remove the version callout. Change line 220 to: I made this change locally (commit Everything else looks good — |
3 participants
Description
Add documentation to help users who integrate Composio through third-party platforms (MindPal, n8n, Make, etc.) understand why they may see fewer tools than expected and how to fix it.
The REST API defaults to the base version (
00000000_00) whentoolkit_versionsis not specified, which means tools added in newer versions are hidden. The SDK defaults tolatest, so SDK users aren't affected — but third-party platforms that call the REST API directly often omit this parameter.Changes:
Resolves support ticket T-9303 (Gladia tools not visible in MindPal).
How did I test this PR
20260310_00)ConfigDefaults.node.tsdefaults tolatest) and Apollo versioning logic (versioning.tsdefaults toPINNED_VERSIONfor HTTP)