@devries-cameron20 / composio Mirror · read-only / commits / 57700a638
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.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 10:45 UTC

fix(docs): Fix broken internal links across documentation

Fixed broken links pointing to non-existent paths: - /docs/authenticating-tools → /docs/tools-direct/authenticating-tools - /docs/user-management → /docs/users-and-sessions - /docs/toolkit-versioning → /docs/tools-direct/toolkit-versioning - /docs/custom-auth-configs → /docs/auth-configuration/custom-auth-configs - /docs/connected-accounts → /docs/auth-configuration/connected-accounts - /docs/custom-tools → /docs/tools-direct/custom-tools - /docs/executing-tools → /docs/tools-direct/executing-tools - /docs/programmatic-auth-configs → /docs/auth-configuration/programmatic-auth-configs - /docs/modify-tool-behavior/* → /docs/tools-direct/modify-tool-behavior/* - /docs/guides/* → /docs/* (removed guides/ prefix) Fixes PLEN-995 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Sushmithamallesh committed Feb 2, 2026 at 12:48 UTC 57700a6383179c9d8eedeb9d3da22992951850d2
18 files changed +39 -39
docs/content/changelog/11-10-25.mdx
+1 -1
@@ -129,4 +129,4 @@ const composio = new Composio({
129 const trigger = await composio.triggers.create('user', 'GITHUB_COMMIT_EVENT', {...});
130 ```
131
132 -For more details on toolkit versioning, see the [Toolkit Versioning documentation](/docs/toolkit-versioning).
132 +For more details on toolkit versioning, see the [Toolkit Versioning documentation](/docs/tools-direct/toolkit-versioning).
docs/content/changelog/12-03-25.mdx
+1 -1
@@ -23,4 +23,4 @@ This is a **non-breaking change**. Your existing integrations and completed conn
23
24 ### Questions?
25
26 -If you have any questions about this change, please reach out to our support team or check our [Connected Accounts documentation](https://docs.composio.dev/docs/connected-accounts).
26 +If you have any questions about this change, please reach out to our support team or check our [Connected Accounts documentation](/docs/auth-configuration/connected-accounts).
docs/content/changelog/12-09-25.mdx
+1 -1
@@ -31,7 +31,7 @@ To continue using these applications with Composio:
31
32 1. **Create Developer Accounts**: Register for developer accounts on the platforms you need
33 2. **Generate API Credentials**: Create OAuth apps following each platform's documentation
34 -3. **Configure in Composio**: Add your credentials to Composio using [custom auth configs](https://docs.composio.dev/docs/custom-auth-configs)
34 +3. **Configure in Composio**: Add your credentials to Composio using [custom auth configs](/docs/auth-configuration/custom-auth-configs)
35 4. **Test Your Integration**: Test your integration with the new credentials
36
37 <Callout>
docs/content/docs/auth-configuration/connected-accounts.mdx
+2 -2
@@ -4,7 +4,7 @@ description: Manage and monitor user connections to toolkits
4 keywords: [list accounts, refresh token, disable, delete account]
5 ---
6
7 -Connected accounts are authenticated connections between your users and toolkits. After users authenticate (see [Authenticating tools](/docs/authenticating-tools)), you can manage these accounts throughout their lifecycle.
7 +Connected accounts are authenticated connections between your users and toolkits. After users authenticate (see [Authenticating tools](/docs/tools-direct/authenticating-tools)), you can manage these accounts throughout their lifecycle.
8
9 Composio automatically handles token refresh and credential management. This guide covers manual operations: listing, retrieving, refreshing, enabling, disabling, and deleting accounts.
10
@@ -225,7 +225,7 @@ Deletion is permanent. Users must re-authenticate to reconnect.
225 Users can connect multiple accounts for the same toolkit (e.g., personal and work Gmail).
226
227 <Callout type="info">
228 -Use `link()` for creating accounts, as it provides hosted authentication and allows multiple accounts by default. See [Connect Link authentication](/docs/authenticating-tools#hosted-authentication-connect-link).
228 +Use `link()` for creating accounts, as it provides hosted authentication and allows multiple accounts by default. See [Connect Link authentication](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link).
229 </Callout>
230
231 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
docs/content/docs/auth-configuration/custom-auth-params.mdx
+1 -1
@@ -98,7 +98,7 @@ Execute the tool using the custom authentication modifier. The `beforeExecute` h
98
99 Following is an example of how to execute a tool with a custom authentication modifier for Completion Providers.
100
101 -For Agentic Providers, read about [Modifying tool inputs](/docs/modify-tool-behavior/before-execution-modifiers).
101 +For Agentic Providers, read about [Modifying tool inputs](/docs/tools-direct/modify-tool-behavior/before-execution-modifiers).
102
103 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
104 <Tab value="Python">
docs/content/docs/authenticating-users/manually-authenticating.mdx
+1 -1
@@ -10,7 +10,7 @@ Manual authentication lets you connect users to toolkits outside of the chat flo
10
11 ## Authorize a toolkit
12
13 -Use `session.authorize()` to generate a [Connect Link](/docs/authenticating-tools#hosted-authentication-connect-link) URL, redirect the user, and wait for them to complete:
13 +Use `session.authorize()` to generate a [Connect Link](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link) URL, redirect the user, and wait for them to complete:
14
15 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
16 <Tab value="Python">
docs/content/docs/managing-multiple-connected-accounts.mdx
+1 -1
@@ -110,7 +110,7 @@ const session2 = await composio.create("user_123", {
110
111 ## Listing all user accounts
112
113 -To list all accounts a user has connected (not just the active one), see [List accounts](/docs/connected-accounts#list-accounts).
113 +To list all accounts a user has connected (not just the active one), see [List accounts](/docs/auth-configuration/connected-accounts#list-accounts).
114
115 ## Viewing session's active account
116
docs/content/docs/migration-guide/new-sdk.mdx
+6 -6
@@ -463,7 +463,7 @@ console.log(JSON.stringify(tools, null, 2));
463
464 #### Before Modifiers
465
466 -The following example shows creating and using a before modifier for a Chat Completion provider. For agentic frameworks, view the [complete before modifier documentation](/docs/modify-tool-behavior/before-execution-modifiers):
466 +The following example shows creating and using a before modifier for a Chat Completion provider. For agentic frameworks, view the [complete before modifier documentation](/docs/tools-direct/modify-tool-behavior/before-execution-modifiers):
467
468 <Tabs groupId="language" items={['Python (current)', 'TypeScript (current)']} persist>
469 <Tab value="Python (current)">
@@ -507,7 +507,7 @@ const result_1 = await composio.tools.execute(
507
508 #### After Modifiers
509
510 -The following example shows creating and using an after modifier for a Chat Completion provider. For agentic frameworks, view the [complete after modifier documentation](/docs/modify-tool-behavior/after-execution-modifiers):
510 +The following example shows creating and using an after modifier for a Chat Completion provider. For agentic frameworks, view the [complete after modifier documentation](/docs/tools-direct/modify-tool-behavior/after-execution-modifiers):
511
512 <Tabs groupId="language" items={['Python (current)', 'TypeScript (current)']} persist>
513 <Tab value="Python (current)">
@@ -557,7 +557,7 @@ const result_2 = await composio.tools.execute(
557
558 ### Custom Tools
559
560 -The SDK continues to support custom tools. [Creating tools from your methods](/docs/custom-tools#creating-a-custom-tool) remains possible. We recommend reviewing the [detailed custom tools documentation](/docs/custom-tools#creating-a-custom-tool) for more information.
560 +The SDK continues to support custom tools. [Creating tools from your methods](/docs/tools-direct/custom-tools#creating-a-custom-tool) remains possible. We recommend reviewing the [detailed custom tools documentation](/docs/tools-direct/custom-tools#creating-a-custom-tool) for more information.
561
562 Due to changes in the SDK architecture, creating custom tools that use Composio's managed authentication has been modified. In the previous SDK, you could create a custom tool as follows:
563
@@ -705,7 +705,7 @@ const tool = await composio.tools.createCustomTool({
705 </Tab>
706 </Tabs>
707
708 -For more information, including executing custom tools and defining custom headers and query parameters, refer to the [Custom Tools](/docs/custom-tools) documentation.
708 +For more information, including executing custom tools and defining custom headers and query parameters, refer to the [Custom Tools](/docs/tools-direct/custom-tools) documentation.
709
710 ### Auth configs (formerly integrations)
711
@@ -721,7 +721,7 @@ Auth configs now use nano IDs instead of UUIDs:
721
722 We recommend storing auth config nano IDs in your database for connecting users to the appropriate auth configuration.
723
724 -For most use cases, you will create auth configs through the dashboard, and this process remains unchanged. Read more about [creating auth configs](/docs/authenticating-tools#creating-an-auth-config) and [customizing auth configs](/docs/custom-auth-configs).
724 +For most use cases, you will create auth configs through the dashboard, and this process remains unchanged. Read more about [creating auth configs](/docs/tools-direct/authenticating-tools#creating-an-auth-config) and [customizing auth configs](/docs/auth-configuration/custom-auth-configs).
725
726 Creating auth configs programmatically in the previous SDK:
727
@@ -820,7 +820,7 @@ console.log(authConfig);
820 </Tab>
821 </Tabs>
822
823 -For using custom authentication credentials, refer to the [Programmatic Auth Configs](/docs/programmatic-auth-configs) documentation.
823 +For using custom authentication credentials, refer to the [Programmatic Auth Configs](/docs/auth-configuration/programmatic-auth-configs) documentation.
824
825 <Callout type="info">
826 The callback URL for creating custom OAuth configs is now `https://backend.composio.dev/api/v3/toolkits/auth/callback`. The previous URL was `https://backend.composio.dev/api/v1/auth-apps/add`.
docs/content/docs/migration-guide/tool-router-beta.mdx
+4 -4
@@ -64,7 +64,7 @@ const session = await composio.create('user_123');
64 If you have existing users on tool router and you don't want them to authenticate again:
65 - Tool Router will auto-detect auth configs and connected accounts it created (from the beta version).
66 - If you have custom auth configs (not created by Tool Router):
67 - - Search for the Auth config for that connected account. See [Connected Accounts](/docs/connected-accounts) to fetch existing accounts programmatically.
67 + - Search for the Auth config for that connected account. See [Connected Accounts](/docs/auth-configuration/connected-accounts) to fetch existing accounts programmatically.
68 - While creating a session configure to use this Auth config.
69 - You need to repeat this for each toolkit you want to enable for that session.
70
@@ -105,9 +105,9 @@ Check out these new features available in the stable version:
105
106 - **[Native tools](/docs/providers/openai-agents)**: Use Tool Router with any AI framework
107 - **Better [session](/docs/users-and-sessions) and [auth](/docs/authentication) config**
108 -- **[Multi-account support](/docs/guides/managing-multiple-connected-accounts)**: Manage multiple accounts per user seamlessly
108 +- **[Multi-account support](/docs/managing-multiple-connected-accounts)**: Manage multiple accounts per user seamlessly
109 - **[Manual authentication](/docs/authenticating-users/manually-authenticating)**: Control when and how users authenticate
110 -- **[Custom auth](/docs/guides/using-custom-auth-configuration)**: Support for toolkits that don't have composio managed auth
111 -- **[White labeling](/docs/guides/white-labeling-authentication)**: Customize authentication screens with your branding
110 +- **[Custom auth](/docs/using-custom-auth-configuration)**: Support for toolkits that don't have composio managed auth
111 +- **[White labeling](/docs/white-labeling-authentication)**: Customize authentication screens with your branding
112 </Step>
113 </Steps>
docs/content/docs/migration-guide/toolkit-versioning.mdx
+1 -1
@@ -158,4 +158,4 @@ The `dangerouslySkipVersionCheck` flag is only for migration or debugging. Never
158
159 ## Next steps
160
161 -For complete documentation on toolkit versioning, including best practices and advanced configuration, see [Toolkit versioning](/docs/toolkit-versioning).
161 +For complete documentation on toolkit versioning, including best practices and advanced configuration, see [Toolkit versioning](/docs/tools-direct/toolkit-versioning).
docs/content/docs/providers/openai.mdx
+4 -4
@@ -30,8 +30,8 @@ Read more about it in the [OpenAI documentation](https://platform.openai.com/doc
30
31 <Callout>
32 Before executing any tools that require authentication (like Gmail), you'll need to:
33 -1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your app
34 -2. [Set up a Connected Account](/docs/authenticating-tools#connecting-an-account) for the user.
33 +1. [Create an Auth Configuration](/docs/tools-direct/authenticating-tools#creating-an-auth-config) for your app
34 +2. [Set up a Connected Account](/docs/tools-direct/authenticating-tools#connecting-an-account) for the user.
35 </Callout>
36
37 <Tabs items={["Python", "TypeScript"]}>
@@ -118,8 +118,8 @@ The OpenAI Chat Provider is the default provider used by Composio SDK, but you c
118
119 <Callout>
120 Before executing any tools that require authentication (like Gmail), you'll need to:
121 -1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your app
122 -2. [Set up a Connected Account](/docs/authenticating-tools#connecting-an-account) for the user.
121 +1. [Create an Auth Configuration](/docs/tools-direct/authenticating-tools#creating-an-auth-config) for your app
122 +2. [Set up a Connected Account](/docs/tools-direct/authenticating-tools#connecting-an-account) for the user.
123 </Callout>
124
125 <Tabs items={["Python", "TypeScript"]}>
docs/content/docs/tools-direct/authenticating-tools.mdx
+6 -6
@@ -49,7 +49,7 @@ Depending on your authentication method, you may need to configure scopes:
49 You must provide your own credentials regardless of environment.
50
51 <Callout type="info">
52 -Want to remove Composio branding from OAuth screens? See [Custom Auth Configs](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen) for white-labeling options.
52 +Want to remove Composio branding from OAuth screens? See [Custom Auth Configs](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen) for white-labeling options.
53 </Callout>
54 </Step>
55
@@ -77,7 +77,7 @@ You should create multiple auth configs for the same toolkit when you need:
77 <Card title="Programmatic creation" href="/docs/programmatic-auth-configs">
78 For managing auth configs across multiple projects, you can create them programmatically via the API
79 </Card>
80 - <Card title="Production white-labeling" href="/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen">
80 + <Card title="Production white-labeling" href="/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen">
81 Remove Composio branding from OAuth screens for a fully white-labeled authentication experience
82 </Card>
83 </Cards>
@@ -89,7 +89,7 @@ With an auth config created, you're ready to authenticate your users!
89 You can either use [**Connect Link**](#hosted-authentication-connect-link) for a hosted authentication flow, or use [**Direct SDK Setup**](#direct-sdk-setup).
90
91 <Callout>
92 -User authentication requires a User ID - a unique identifier that groups connected accounts together. Learn more about [User Management](/docs/user-management) to understand how to structure User IDs for your application.
92 +User authentication requires a User ID - a unique identifier that groups connected accounts together. Learn more about [User Management](/docs/users-and-sessions) to understand how to structure User IDs for your application.
93 </Callout>
94
95 **Choose the section below that matches your toolkit's authentication method:**
@@ -159,7 +159,7 @@ By default, users will see a Composio-branded authentication experience when con
159 These settings will apply to all authentication flows using Connect Link, providing a white-labeled experience that maintains your brand identity throughout the authentication process.
160
161 <Callout>
162 -For complete white-labeling including OAuth consent screens (removing Composio's domain), see [Custom Auth Configs - White-labeling](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
162 +For complete white-labeling including OAuth consent screens (removing Composio's domain), see [Custom Auth Configs - White-labeling](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
163 </Callout>
164
165 ### Direct SDK Setup
@@ -381,7 +381,7 @@ Composio also supports a wide range of other auth schemas:
381 For any of these methods, [fetch the config parameter](#fetching-the-required-config-parameters-for-an-auth-config) to determine the exact fields required. Every toolkit has its own requirements, and understanding these is essential for successfully creating connections.
382 </Callout>
383
384 -Learn how to [Manage connected accounts](/docs/connected-accounts) after users authenticate.
384 +Learn how to [Manage connected accounts](/docs/auth-configuration/connected-accounts) after users authenticate.
385
386 ## Connection Statuses
387
@@ -493,4 +493,4 @@ Only connections with **ACTIVE** status can be used to execute tools. If a conne
493
494 ## Next Step
495
496 -With authentication set up, you can now fetch and execute tools. See [Executing Tools](/docs/executing-tools) to get started.
496 +With authentication set up, you can now fetch and execute tools. See [Executing Tools](/docs/tools-direct/executing-tools) to get started.
docs/content/docs/tools-direct/executing-tools.mdx
+3 -3
@@ -9,7 +9,7 @@ LLMs on their own can only do generation. Tool calling changes that by letting t
9 In Composio, every **tool** is a single API action—fully described with schema, parameters, and return type. Tools live inside **toolkits** like Gmail, Slack, or GitHub, and Composio handles authentication and user scoping.
10
11 <Callout type="info">
12 -**User Scoping**: All tools are scoped to a specific user - that's why every example includes a `user_id`. Learn how to structure User IDs in [User Management](/docs/user-management). Each user must authenticate with their respective services (Gmail, Calendar, etc.) - see [Authentication](/docs/authenticating-tools).
12 +**User Scoping**: All tools are scoped to a specific user - that's why every example includes a `user_id`. Learn how to structure User IDs in [User Management](/docs/users-and-sessions). Each user must authenticate with their respective services (Gmail, Calendar, etc.) - see [Authentication](/docs/tools-direct/authenticating-tools).
13 </Callout>
14
15 ## Using Chat Completions
@@ -238,7 +238,7 @@ console.log('GitHub stargazers:', JSON.stringify(result, null, 2));
238 </Tabs>
239
240 <Callout>
241 -The examples above configure toolkit versions at SDK initialization. You can also pass versions per-execution or use environment variables. See [toolkit versioning](/docs/toolkit-versioning) for all configuration options.
241 +The examples above configure toolkit versions at SDK initialization. You can also pass versions per-execution or use environment variables. See [toolkit versioning](/docs/tools-direct/toolkit-versioning) for all configuration options.
242 </Callout>
243
244 ### Proxy Execute
@@ -292,7 +292,7 @@ console.log(data);
292 </Tabs>
293
294 <Callout type="info">
295 -Need an API that isn't supported by any Composio toolkit, or want to extend an existing one? Learn how to [create custom tools](/docs/custom-tools).
295 +Need an API that isn't supported by any Composio toolkit, or want to extend an existing one? Learn how to [create custom tools](/docs/tools-direct/custom-tools).
296 </Callout>
297
298 ## Automatic File Handling
docs/content/docs/tools-direct/fetching-tools.mdx
+2 -2
@@ -30,7 +30,7 @@ const tools = await composio.tools.get(userId, {
30 </Tab>
31 </Tabs>
32
33 -Returns top 20 tools by default. Tools require a `user_id` because they're scoped to authenticated accounts. See [User management](/docs/user-management) and [Authentication](/docs/authenticating-tools).
33 +Returns top 20 tools by default. Tools require a `user_id` because they're scoped to authenticated accounts. See [User management](/docs/users-and-sessions) and [Authentication](/docs/tools-direct/authenticating-tools).
34
35 ## Tool schemas
36
@@ -234,5 +234,5 @@ const toolkitSearchRaw = await composio.tools.getRawComposioTools({
234 </Tabs>
235
236 <Callout type="info">
237 -Use specific toolkit versions in production to prevent breaking changes. See [toolkit versioning](/docs/toolkit-versioning).
237 +Use specific toolkit versions in production to prevent breaking changes. See [toolkit versioning](/docs/tools-direct/toolkit-versioning).
238 </Callout>
docs/content/docs/triggers.mdx
+2 -2
@@ -11,7 +11,7 @@ Each event is delivered as a structured payload to your webhook endpoint (via we
11 <Figure src="/images/triggers.png" alt="Triggers Overview" caption="Triggers through Composio" />
12
13 <Callout type="info" title="Prerequisites">
14 -Before proceeding, ensure you've created an [auth config](/docs/authenticating-tools#creating-an-auth-config) and [established a connection](/docs/authenticating-tools#hosted-authentication-connect-link) to an app (e.g., Slack, GitHub). Triggers are scoped to specific users - learn about [User Management](/docs/user-management) for guidance on structuring User IDs.
14 +Before proceeding, ensure you've created an [auth config](/docs/tools-direct/authenticating-tools#creating-an-auth-config) and [established a connection](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link) to an app (e.g., Slack, GitHub). Triggers are scoped to specific users - learn about [User Management](/docs/users-and-sessions) for guidance on structuring User IDs.
15 </Callout>
16
17 ## Creating a trigger
@@ -92,7 +92,7 @@ console.log(`Trigger created: ${trigger.triggerId}`);
92 </Tabs>
93
94 <Callout>
95 -To use a specific toolkit version when creating triggers, configure `toolkitVersions` during initialization. See [Toolkit Versioning](/docs/toolkit-versioning) for more details.
95 +To use a specific toolkit version when creating triggers, configure `toolkitVersions` during initialization. See [Toolkit Versioning](/docs/tools-direct/toolkit-versioning) for more details.
96 </Callout>
97
98 ## Subscribing to triggers
docs/content/docs/using-custom-auth-configuration.mdx
+1 -1
@@ -26,7 +26,7 @@ In the [Composio platform](https://platform.composio.dev), go to "All Toolkits"
26 Copy the auth config ID (e.g., `ac_1234abcd`).
27
28 <Callout type="info">
29 -For detailed instructions on getting credentials for specific toolkits, see [Custom auth configs](/docs/custom-auth-configs).
29 +For detailed instructions on getting credentials for specific toolkits, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
30 </Callout>
31 </Step>
32
docs/content/docs/white-labeling-authentication.mdx
+1 -1
@@ -38,7 +38,7 @@ Create an auth config in the [Composio dashboard](https://app.composio.dev):
38 Copy the auth config ID (e.g., `ac_1234abcd`).
39
40 <Callout type="info">
41 -For detailed instructions with screenshots, see [Custom auth configs](/docs/custom-auth-configs).
41 +For detailed instructions with screenshots, see [Custom auth configs](/docs/auth-configuration/custom-auth-configs).
42 </Callout>
43 </Step>
44
docs/content/examples/vercel-chat.mdx
+1 -1
@@ -20,7 +20,7 @@ repository to set up the project locally.
20 ## Creating auth configs
21
22 For all the apps you want to connect to the chatbot, you need to create their
23 -respective auth configs. Learn how to create auth configs [here](/docs/authenticating-tools#creating-an-auth-config).
23 +respective auth configs. Learn how to create auth configs [here](/docs/tools-direct/authenticating-tools#creating-an-auth-config).
24 Once done, your auth configs will be available in the [Composio dashboard](https://app.composio.dev/integrations).
25
26