Skip to content

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

docs: improve cross-linking across all documentation pages

Sushmitha Mallesh26e39ba99538
diff --git a/docs/content/docs/auth-configuration/connected-accounts.mdx b/docs/content/docs/auth-configuration/connected-accounts.mdx
index 5de3c2640..49c37b148 100644
--- a/docs/content/docs/auth-configuration/connected-accounts.mdx
+++ b/docs/content/docs/auth-configuration/connected-accounts.mdx
@@ -331,6 +331,10 @@ try {
</Tab>
</Tabs>
+<Callout type="info">
+For session-based apps, see [Managing multiple connected accounts](/docs/managing-multiple-connected-accounts) for how sessions handle account selection automatically.
+</Callout>
+
### Execute with a specific account
When you have multiple accounts, specify which one to use with `connected_account_id`:
@@ -367,3 +371,11 @@ console.log('Tool executed:', result);
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+ <Card icon={<Palette />} title="Custom auth configs" href="/docs/auth-configuration/custom-auth-configs" description="Use your own OAuth apps for white-labeled authentication" />
+ <Card icon={<Wrench />} title="Programmatic auth configs" href="/docs/auth-configuration/programmatic-auth-configs" description="Create auth configs programmatically via the SDK" />
+</Cards>
diff --git a/docs/content/docs/auth-configuration/custom-auth-configs.mdx b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
index 5df8f7f6d..74742c261 100644
--- a/docs/content/docs/auth-configuration/custom-auth-configs.mdx
+++ b/docs/content/docs/auth-configuration/custom-auth-configs.mdx
@@ -254,3 +254,11 @@ The custom redirect endpoint is a simple passthrough that preserves all OAuth pa
</Accordion>
</Accordions>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Database />} title="Connected accounts" href="/docs/auth-configuration/connected-accounts" description="Manage and monitor user connections to toolkits" />
+ <Card icon={<Wrench />} title="Programmatic auth configs" href="/docs/auth-configuration/programmatic-auth-configs" description="Create auth configs programmatically via the SDK" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+</Cards>
diff --git a/docs/content/docs/auth-configuration/custom-auth-params.mdx b/docs/content/docs/auth-configuration/custom-auth-params.mdx
index 496093784..7b7952065 100644
--- a/docs/content/docs/auth-configuration/custom-auth-params.mdx
+++ b/docs/content/docs/auth-configuration/custom-auth-params.mdx
@@ -147,3 +147,11 @@ console.log(JSON.stringify(result, null, 2));
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Before execution modifiers" href="/docs/tools-direct/modify-tool-behavior/before-execution-modifiers" description="Modify tool arguments before execution" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+</Cards>
diff --git a/docs/content/docs/auth-configuration/programmatic-auth-configs.mdx b/docs/content/docs/auth-configuration/programmatic-auth-configs.mdx
index 5435f083a..88c512962 100644
--- a/docs/content/docs/auth-configuration/programmatic-auth-configs.mdx
+++ b/docs/content/docs/auth-configuration/programmatic-auth-configs.mdx
@@ -252,3 +252,11 @@ console.log("Required auth config fields:", authFields);
</Tabs>
Then inspect the required fields and specify them in the `credentials` object.
+
+## What to read next
+
+<Cards>
+ <Card icon={<Palette />} title="Custom auth configs" href="/docs/auth-configuration/custom-auth-configs" description="Use your own OAuth apps for white-labeled authentication" />
+ <Card icon={<Database />} title="Connected accounts" href="/docs/auth-configuration/connected-accounts" description="Manage and monitor user connections to toolkits" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+</Cards>
diff --git a/docs/content/docs/authenticating-users/in-chat-authentication.mdx b/docs/content/docs/authenticating-users/in-chat-authentication.mdx
index 9b35e159d..e30ae61dd 100644
--- a/docs/content/docs/authenticating-users/in-chat-authentication.mdx
+++ b/docs/content/docs/authenticating-users/in-chat-authentication.mdx
@@ -4,7 +4,7 @@ description: Let your agent prompt users to connect accounts during conversation
keywords: [automatic auth, dynamic auth, agent prompts]
---
-In-chat authentication lets your agent prompt users to connect accounts during chat. When a tool requires authentication, the agent returns a Connect Link URL. The user authenticates, confirms in chat, and the agent retries.
+In-chat authentication lets your agent prompt users to connect accounts during chat. When a tool requires authentication, the agent returns a Connect Link URL. The user authenticates, confirms in chat, and the agent retries. For an overview of all auth approaches, see [Authentication](/docs/authentication).
## How it works
diff --git a/docs/content/docs/cli.mdx b/docs/content/docs/cli.mdx
index eb516a563..cb662487f 100644
--- a/docs/content/docs/cli.mdx
+++ b/docs/content/docs/cli.mdx
@@ -61,7 +61,11 @@ composio logout
## Generate type definitions
-Generate TypeScript or Python type definitions for all Composio tools. These types provide type safety when using direct tool execution (`composio.tools.execute()`), helping you pass the correct parameters and catch errors early.
+<Callout type="info">
+Type generation is only useful if you're using [direct tool execution](/docs/tools-direct/executing-tools). If you're using sessions with meta tools, you don't need this.
+</Callout>
+
+Generate TypeScript or Python type definitions for all Composio tools. These types provide type safety when using `composio.tools.execute()`, helping you pass the correct parameters and catch errors early.
### Auto-detect and generate
@@ -130,3 +134,4 @@ For explicit control, use language-specific commands:
```
</Tab>
</Tabs>
+
diff --git a/docs/content/docs/debugging-info.mdx b/docs/content/docs/debugging-info.mdx
index 6501d8865..e37cd7efb 100644
--- a/docs/content/docs/debugging-info.mdx
+++ b/docs/content/docs/debugging-info.mdx
@@ -4,7 +4,7 @@ description: Share your debugging info with Composio team for faster issue resol
keywords: [debug, support, troubleshoot]
---
-Your debugging info is tied to your project and it helps us trace what happened and debug the issue faster.
+Your debugging info is tied to your [project](/docs/projects) and it helps us trace what happened and debug the issue faster. Before reaching out, check the [troubleshooting guide](/docs/troubleshooting) and [common FAQ](/docs/common-faq) for solutions to frequent issues.
## Finding Your Debugging Info
diff --git a/docs/content/docs/glossary.mdx b/docs/content/docs/glossary.mdx
index b0d3af687..2ca5a80d7 100644
--- a/docs/content/docs/glossary.mdx
+++ b/docs/content/docs/glossary.mdx
@@ -8,7 +8,7 @@ keywords: [glossary, definitions, terminology]
<Glossary>
<GlossaryTerm name="Auth Config">
-A blueprint defining how authentication works for a toolkit: auth method (OAuth2, API key, Bearer token, Basic Auth), scopes, and credentials. Created automatically by a session when needed. You can create a custom one to use your own OAuth credentials or non-default scopes.
+A blueprint defining how authentication works for a toolkit: auth method (OAuth2, API key, Bearer token, Basic Auth), scopes, and credentials. Created automatically by a [session](/docs/users-and-sessions) when needed. You can [create a custom one](/docs/auth-configuration/custom-auth-configs) to use your own OAuth credentials or non-default scopes.
</GlossaryTerm>
<GlossaryTerm name="Auth Scheme">
@@ -28,11 +28,11 @@ The default mode where Composio provides its own OAuth app credentials for each
</GlossaryTerm>
<GlossaryTerm name="Connect Link">
-A hosted page where a user authorizes access to a toolkit. Returned as a `redirect_url` from `session.authorize()` or `connectedAccounts.initiate()`. Composio manages the full OAuth flow.
+A hosted page where a user authorizes access to a toolkit. Returned as a `redirect_url` from `session.authorize()` or `connectedAccounts.initiate()`. Composio manages the full OAuth flow. See [Authentication](/docs/authentication).
</GlossaryTerm>
<GlossaryTerm name="Connected Account">
-Created when a user authenticates with a toolkit. Stores credentials (OAuth tokens or API keys) linked to a user ID. Composio automatically refreshes OAuth tokens. A user can have multiple connected accounts for the same toolkit. IDs are prefixed `ca_`.
+Created when a user authenticates with a toolkit. Stores credentials (OAuth tokens or API keys) linked to a user ID. Composio automatically refreshes OAuth tokens. A user can have [multiple connected accounts](/docs/managing-multiple-connected-accounts) for the same toolkit. IDs are prefixed `ca_`.
</GlossaryTerm>
<GlossaryTerm name="Connection Request">
@@ -40,11 +40,11 @@ The object returned when you initiate authentication. Contains the Connect Link
</GlossaryTerm>
<GlossaryTerm name="Custom Tool">
-A user-defined tool used alongside Composio's built-in tools. Can be standalone (no auth) or toolkit-based (authenticated API requests). Stored in memory, must be recreated on restart.
+A user-defined tool used alongside Composio's built-in tools. Can be standalone (no auth) or toolkit-based (authenticated API requests). Stored in memory, must be recreated on restart. See [Creating custom tools](/docs/tools-direct/custom-tools).
</GlossaryTerm>
<GlossaryTerm name="In-Chat Authentication">
-A flow where the AI agent handles authentication by calling `COMPOSIO_MANAGE_CONNECTIONS` to generate a Connect Link and send it to the user in the conversation.
+A flow where the AI agent handles authentication by calling `COMPOSIO_MANAGE_CONNECTIONS` to generate a Connect Link and send it to the user in the conversation. See [In-chat authentication](/docs/authenticating-users/in-chat-authentication).
</GlossaryTerm>
<GlossaryTerm name="MCP (Model Context Protocol)">
@@ -52,15 +52,15 @@ An open protocol for connecting AI models to external tools. Every session expos
</GlossaryTerm>
<GlossaryTerm name="Manual Authentication">
-Authenticating users from your own code using `session.authorize()` or `connectedAccounts.initiate()`, as opposed to letting the AI agent handle it via in-chat authentication.
+Authenticating users from your own code using `session.authorize()` or `connectedAccounts.initiate()`, as opposed to letting the AI agent handle it via in-chat authentication. See [Manual authentication](/docs/authenticating-users/manually-authenticating).
</GlossaryTerm>
<GlossaryTerm name="Meta Tools">
-A set of tools included in every session, including `COMPOSIO_SEARCH_TOOLS`, `COMPOSIO_MANAGE_CONNECTIONS`, `COMPOSIO_MULTI_EXECUTE_TOOL`, `COMPOSIO_REMOTE_WORKBENCH`, and `COMPOSIO_REMOTE_BASH_TOOL`. They let the agent discover tools, manage auth, execute in parallel, and run code without loading hundreds of tool definitions upfront.
+A set of tools included in every session, including `COMPOSIO_SEARCH_TOOLS`, `COMPOSIO_MANAGE_CONNECTIONS`, `COMPOSIO_MULTI_EXECUTE_TOOL`, `COMPOSIO_REMOTE_WORKBENCH`, and `COMPOSIO_REMOTE_BASH_TOOL`. They let the agent discover tools, manage auth, execute in parallel, and run code without loading hundreds of tool definitions upfront. See [Tools and toolkits](/docs/tools-and-toolkits#meta-tools).
</GlossaryTerm>
<GlossaryTerm name="Modifiers">
-Middleware that transforms tool behavior: **schema modifiers** change a tool's schema before the agent sees it, **before-execution modifiers** modify arguments before a tool runs, **after-execution modifiers** transform the result.
+Middleware that transforms tool behavior: [schema modifiers](/docs/tools-direct/modify-tool-behavior/schema-modifiers) change a tool's schema before the agent sees it, [before-execution modifiers](/docs/tools-direct/modify-tool-behavior/before-execution-modifiers) modify arguments before a tool runs, [after-execution modifiers](/docs/tools-direct/modify-tool-behavior/after-execution-modifiers) transform the result.
</GlossaryTerm>
<GlossaryTerm name="Native Tools">
@@ -76,7 +76,7 @@ A key (`x-org-api-key`) for organization-level operations like creating and mana
</GlossaryTerm>
<GlossaryTerm name="Project">
-An isolated environment within an organization that scopes API keys, connected accounts, auth configs, and webhooks. Resources in one project are inaccessible from another. IDs are prefixed `proj_`.
+An isolated environment within an organization that scopes API keys, connected accounts, auth configs, and webhooks. Resources in one project are inaccessible from another. IDs are prefixed `proj_`. See [Projects](/docs/projects).
</GlossaryTerm>
<GlossaryTerm name="Proxy Execute">
@@ -84,11 +84,11 @@ Making authenticated HTTP requests through a toolkit's connected account without
</GlossaryTerm>
<GlossaryTerm name="Provider">
-An adapter package that transforms Composio tools into the format expected by an AI framework (OpenAI, Anthropic, LangChain, Vercel AI SDK, etc.).
+An adapter package that transforms Composio tools into the format expected by an AI framework (OpenAI, Anthropic, LangChain, Vercel AI SDK, etc.). See [Providers](/docs/providers).
</GlossaryTerm>
<GlossaryTerm name="Session">
-An ephemeral configuration object from `composio.create(userId)`. Ties together a user ID, available toolkits, auth config, and connected accounts. Immutable. Exposes `tools()`, `mcp.url`, `authorize()`, and `toolkits()`.
+An ephemeral configuration object from `composio.create(userId)`. Ties together a user ID, available toolkits, auth config, and connected accounts. Immutable. Exposes `tools()`, `mcp.url`, `authorize()`, and `toolkits()`. See [Users and sessions](/docs/users-and-sessions).
</GlossaryTerm>
<GlossaryTerm name="Session ID">
@@ -112,11 +112,11 @@ The lowercase identifier for a toolkit, e.g. `github`, `gmail`, `slack`. Used wh
</GlossaryTerm>
<GlossaryTerm name="Toolkit Versioning">
-Pinning a toolkit to a specific version so your integration uses a consistent set of tools even as Composio updates definitions.
+Pinning a toolkit to a specific version so your integration uses a consistent set of tools even as Composio updates definitions. See [Toolkit versioning](/docs/tools-direct/toolkit-versioning).
</GlossaryTerm>
<GlossaryTerm name="Trigger">
-Sends structured payloads to your application when something happens in a connected app. Two delivery types: **webhook** (the app pushes events in real time, e.g. GitHub, Slack) and **polling** (Composio periodically checks for new data, e.g. Gmail).
+Sends structured payloads to your application when something happens in a connected app. Two delivery types: **webhook** (the app pushes events in real time, e.g. GitHub, Slack) and **polling** (Composio periodically checks for new data, e.g. Gmail). See [Triggers](/docs/triggers).
</GlossaryTerm>
<GlossaryTerm name="Trigger Instance">
@@ -124,15 +124,15 @@ A specific, active trigger scoped to a user's connected account.
</GlossaryTerm>
<GlossaryTerm name="User ID">
-An identifier from your application that Composio uses to scope connected accounts, tool executions, and authorizations. Connections are fully isolated between user IDs.
+An identifier from your application that Composio uses to scope connected accounts, tool executions, and authorizations. Connections are fully isolated between user IDs. See [Users and sessions](/docs/users-and-sessions).
</GlossaryTerm>
<GlossaryTerm name="White-Labeling">
-Customizing the auth experience so users see your brand during the OAuth flow. You provide your own OAuth credentials, redirect URIs, and branding.
+Customizing the auth experience so users see your brand during the OAuth flow. You provide your own OAuth credentials, redirect URIs, and branding. See [White-labeling authentication](/docs/white-labeling-authentication).
</GlossaryTerm>
<GlossaryTerm name="Workbench">
-A persistent Python sandbox via the `COMPOSIO_REMOTE_WORKBENCH` meta tool. State persists across calls within a session. Used for bulk operations, data transformations, and processing large tool responses.
+A persistent Python sandbox via the `COMPOSIO_REMOTE_WORKBENCH` meta tool. State persists across calls within a session. Used for bulk operations, data transformations, and processing large tool responses. See [Workbench](/docs/workbench).
</GlossaryTerm>
</Glossary>
diff --git a/docs/content/docs/managing-multiple-connected-accounts.mdx b/docs/content/docs/managing-multiple-connected-accounts.mdx
index 7ecc93d6f..50f3d2b0a 100644
--- a/docs/content/docs/managing-multiple-connected-accounts.mdx
+++ b/docs/content/docs/managing-multiple-connected-accounts.mdx
@@ -4,7 +4,7 @@ description: Handle users with multiple accounts for the same toolkit
keywords: [multiple accounts, work personal, switch account]
---
-Users can connect multiple accounts for the same toolkit (e.g., personal and work Gmail accounts). This is useful when users need to manage different email accounts, GitHub organizations, or separate work and personal contexts. This guide explains how to connect, select, and manage multiple accounts.
+Users can connect multiple accounts for the same toolkit (e.g., personal and work Gmail accounts). This is useful when users need to manage different email accounts, GitHub organizations, or separate work and personal contexts. This guide explains how to connect, select, and manage multiple accounts. For background on how users, sessions, and connected accounts relate, see [Users & Sessions](/docs/users-and-sessions).
## Default account behavior
@@ -142,3 +142,11 @@ for (const toolkit of toolkits.items) {
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Configuring sessions" href="/docs/configuring-sessions" description="Pass connectedAccounts, auth configs, and toolkit restrictions to sessions" />
+ <Card icon={<ShieldCheck />} title="Manual authentication" href="/docs/authenticating-users/manually-authenticating" description="Pre-authenticate users with session.authorize() and Connect Links" />
+ <Card icon={<Key />} title="Authentication overview" href="/docs/authentication" description="Connect Links, OAuth, API keys, and how Composio manages auth" />
+</Cards>
diff --git a/docs/content/docs/migration-guide/toolkit-versioning.mdx b/docs/content/docs/migration-guide/toolkit-versioning.mdx
index ca7aa30b2..6c8a7fe4a 100644
--- a/docs/content/docs/migration-guide/toolkit-versioning.mdx
+++ b/docs/content/docs/migration-guide/toolkit-versioning.mdx
@@ -156,6 +156,10 @@ const result = await composio.tools.execute({
The `dangerouslySkipVersionCheck` flag is only for migration or debugging. Never use in production.
</Callout>
-## Next steps
+## What to read next
-For complete documentation on toolkit versioning, including best practices and advanced configuration, see [Toolkit versioning](/docs/tools-direct/toolkit-versioning).
+<Cards>
+ <Card icon={<Blocks />} title="Toolkit versioning" href="/docs/tools-direct/toolkit-versioning" description="Complete guide to version formats, resolution order, and managing versions" />
+ <Card icon={<Rocket />} title="Migrate to sessions" href="/docs/migration-guide/direct-to-sessions" description="Move from direct tool execution to the sessions pattern" />
+ <Card icon={<Play />} title="Quickstart" href="/docs/quickstart" description="Build your first agent with the sessions API" />
+</Cards>
diff --git a/docs/content/docs/projects.mdx b/docs/content/docs/projects.mdx
index fe4ec2b8c..653f3e36c 100644
--- a/docs/content/docs/projects.mdx
+++ b/docs/content/docs/projects.mdx
@@ -86,3 +86,11 @@ curl -X PATCH https://backend.composio.dev/api/v3/org/project/config \
```
You can also view and update these from **Settings > Project Settings** in the [dashboard](https://platform.composio.dev?next_page=/settings). See the [Projects API reference](/reference/api-reference/projects) for all available settings.
+
+## What to read next
+
+<Cards>
+ <Card icon={<Key />} title="Authentication" href="/docs/authentication" description="Auth configs are scoped to projects — learn how Composio manages auth" />
+ <Card icon={<Database />} title="Users & Sessions" href="/docs/users-and-sessions" description="Connected accounts and sessions live within a project" />
+ <Card icon={<Zap />} title="Triggers" href="/docs/triggers" description="Webhook configurations are project-scoped" />
+</Cards>
diff --git a/docs/content/docs/quickstart.mdx b/docs/content/docs/quickstart.mdx
index 73266d165..9d93bfd7e 100644
--- a/docs/content/docs/quickstart.mdx
+++ b/docs/content/docs/quickstart.mdx
@@ -4,7 +4,7 @@ description: Build an AI agent with access to 1000+ tools
keywords: [tutorial, setup, first agent]
---
-Build your first AI agent with Composio Tools.
+Build your first AI agent with Composio Tools. You'll create a [session](/docs/users-and-sessions) for a user, give your agent access to [tools](/docs/tools-and-toolkits), and let it take action across 1000+ apps.
<QuickstartFlow>
@@ -836,5 +836,6 @@ By default, sessions have access to **all available toolkits** in the Composio c
<Card icon={<Wrench />} title="Configuring Sessions" href="/docs/configuring-sessions" description="Restrict toolkits, set custom auth configs, and select connected accounts" />
<Card icon={<Key />} title="Authenticating Users" href="/docs/authentication" description="Learn how users connect their accounts via Connect Links, OAuth, and API keys" />
<Card icon={<BookOpen />} title="How Composio works" href="/docs/how-composio-works" description="Understand what happens under the hood: sessions, meta tools, and the tool execution lifecycle" />
+ <Card icon={<Play />} title="Build a chat app" href="/cookbooks/chat-app" description="Full Next.js tutorial: tool discovery, auth, and multi-turn conversations" />
</Cards>
diff --git a/docs/content/docs/setting-up-triggers/creating-triggers.mdx b/docs/content/docs/setting-up-triggers/creating-triggers.mdx
index cfb1b0d92..f2493fccc 100644
--- a/docs/content/docs/setting-up-triggers/creating-triggers.mdx
+++ b/docs/content/docs/setting-up-triggers/creating-triggers.mdx
@@ -4,7 +4,7 @@ description: Create trigger instances via the dashboard or SDK
keywords: [triggers, create trigger, trigger config]
---
-Create a trigger to start receiving events. A trigger watches for a specific event (e.g., `GITHUB_COMMIT_EVENT`) on a specific user's connected account.
+Create a trigger to start receiving events. A trigger watches for a specific event (e.g., `GITHUB_COMMIT_EVENT`) on a specific user's connected account. For an overview of how triggers work, see [Triggers](/docs/triggers).
<Callout type="info" title="Prerequisites">
Before creating triggers, ensure you have:
diff --git a/docs/content/docs/subscribing-to-connection-expiry-events.mdx b/docs/content/docs/subscribing-to-connection-expiry-events.mdx
index 664d5ada4..fbefae1b8 100644
--- a/docs/content/docs/subscribing-to-connection-expiry-events.mdx
+++ b/docs/content/docs/subscribing-to-connection-expiry-events.mdx
@@ -162,3 +162,11 @@ console.log(`Re-connected: ${connectedAccount.id}`);
<Callout>
Always [verify webhook signatures](/docs/webhook-verification) before processing events in production.
</Callout>
+
+## What to read next
+
+<Cards>
+ <Card icon={<ShieldCheck />} title="Verifying webhooks" href="/docs/webhook-verification" description="Validate webhook signatures to ensure payloads are authentic" />
+ <Card icon={<Zap />} title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="Set up webhooks and SDK subscriptions to receive trigger events" />
+ <Card icon={<Key />} title="Authentication overview" href="/docs/authentication" description="How Composio manages OAuth, token refresh, and connected accounts" />
+</Cards>
diff --git a/docs/content/docs/toolkits/enable-and-disable-toolkits.mdx b/docs/content/docs/toolkits/enable-and-disable-toolkits.mdx
index d89401ca0..82af7f377 100644
--- a/docs/content/docs/toolkits/enable-and-disable-toolkits.mdx
+++ b/docs/content/docs/toolkits/enable-and-disable-toolkits.mdx
@@ -271,5 +271,7 @@ const session = await composio.create("user_123", {
<Cards>
<Card icon={<Wrench />} title="Fetching tools and toolkits" href="/docs/toolkits/fetching-tools-and-toolkits" description="List enabled toolkits, get meta tools, and browse the catalog" />
+ <Card icon={<Wrench />} title="Configuring sessions" href="/docs/configuring-sessions" description="Auth configs, connected accounts, and other session options" />
+ <Card icon={<Wrench />} title="Tools and toolkits" href="/docs/tools-and-toolkits" description="How meta tools discover, authenticate, and execute tools at runtime" />
</Cards>
diff --git a/docs/content/docs/toolkits/fetching-tools-and-toolkits.mdx b/docs/content/docs/toolkits/fetching-tools-and-toolkits.mdx
index fcfa48848..82aeafd9d 100644
--- a/docs/content/docs/toolkits/fetching-tools-and-toolkits.mdx
+++ b/docs/content/docs/toolkits/fetching-tools-and-toolkits.mdx
@@ -177,4 +177,6 @@ console.log(tool.outputParameters);
<Cards>
<Card icon={<Wrench />} title="Enable & disable toolkits" href="/docs/toolkits/enable-and-disable-toolkits" description="Control which toolkits and individual tools are available in sessions" />
+ <Card icon={<Wrench />} title="Tools and toolkits" href="/docs/tools-and-toolkits" description="How meta tools discover, authenticate, and execute tools at runtime" />
+ <Card icon={<Blocks />} title="Browse toolkits" href="/toolkits" description="Explore all available toolkits and their tools" />
</Cards>
diff --git a/docs/content/docs/tools-direct/authenticating-tools.mdx b/docs/content/docs/tools-direct/authenticating-tools.mdx
index adb6a95a7..959eb6811 100644
--- a/docs/content/docs/tools-direct/authenticating-tools.mdx
+++ b/docs/content/docs/tools-direct/authenticating-tools.mdx
@@ -522,6 +522,10 @@ filteredConnections.items.forEach(connection => {
Only connections with **ACTIVE** status can be used to execute tools. If a connection is in any other state, you'll need to take appropriate action (re-authenticate, wait for processing, etc.) before using it.
</Callout>
-## Next Step
+## What to read next
-With authentication set up, you can now fetch and execute tools. See [Executing Tools](/docs/tools-direct/executing-tools) to get started.
+<Cards>
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+ <Card icon={<Database />} title="Connected accounts" href="/docs/auth-configuration/connected-accounts" description="Manage and monitor user connections to toolkits" />
+ <Card icon={<Palette />} title="Custom auth configs" href="/docs/auth-configuration/custom-auth-configs" description="Use your own OAuth apps for white-labeled authentication" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/custom-tools.mdx b/docs/content/docs/tools-direct/custom-tools.mdx
index 9e6d8aa4f..22c7162a4 100644
--- a/docs/content/docs/tools-direct/custom-tools.mdx
+++ b/docs/content/docs/tools-direct/custom-tools.mdx
@@ -6,7 +6,7 @@ llmGuardrails: "direct-execution"
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Tools and toolkits](/docs/tools-and-toolkits) for how sessions discover and execute tools automatically.
</Callout>
Custom tools allow you to create your own tools that can be used with Composio.
@@ -370,3 +370,11 @@ const result = await composio.tools.execute('TOOL_SLUG', {
3. Toolkit-based tools require a valid connected account with the specified toolkit
4. `executeToolRequest` can only execute tools from the same toolkit that the custom tool belongs to
5. Each toolkit-based tool can only use one connected account at a time
+
+## What to read next
+
+<Cards>
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+ <Card icon={<Wrench />} title="Fetching tools" href="/docs/tools-direct/fetching-tools" description="Fetch and filter tools, inspect schemas, and search semantically" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/executing-tools.mdx b/docs/content/docs/tools-direct/executing-tools.mdx
index 50d78b225..c50dcfd70 100644
--- a/docs/content/docs/tools-direct/executing-tools.mdx
+++ b/docs/content/docs/tools-direct/executing-tools.mdx
@@ -6,7 +6,7 @@ llmGuardrails: "direct-execution"
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically. See the [quickstart](/docs/quickstart) to build your first agent with sessions.
</Callout>
LLMs on their own can only do generation. Tool calling changes that by letting them interact with external services. Instead of just drafting an email, the model can call `GMAIL_SEND_EMAIL` to actually send it. The tool's results feed back to the LLM, closing the loop so it can decide, act, observe, and adapt.
@@ -401,3 +401,11 @@ const fileData = await composio.files.upload({
toolkitSlug: 'googledrive'
});
```
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Fetching tools" href="/docs/tools-direct/fetching-tools" description="Fetch and filter tools, inspect schemas, and search semantically" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+ <Card icon={<Wrench />} title="Custom tools" href="/docs/tools-direct/custom-tools" description="Create your own standalone or toolkit-based tools" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/fetching-tools.mdx b/docs/content/docs/tools-direct/fetching-tools.mdx
index 61138a376..64cdffbe6 100644
--- a/docs/content/docs/tools-direct/fetching-tools.mdx
+++ b/docs/content/docs/tools-direct/fetching-tools.mdx
@@ -241,3 +241,11 @@ const toolkitSearchRaw = await composio.tools.getRawComposioTools({
<Callout type="info">
Use specific toolkit versions in production to prevent breaking changes. See [toolkit versioning](/docs/tools-direct/toolkit-versioning).
</Callout>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+ <Card icon={<Key />} title="Authenticating tools" href="/docs/tools-direct/authenticating-tools" description="Create auth configs and connect user accounts" />
+ <Card icon={<Blocks />} title="Toolkit versioning" href="/docs/tools-direct/toolkit-versioning" description="Pin specific tool versions for consistent behavior in production" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/modify-tool-behavior/after-execution-modifiers.mdx b/docs/content/docs/tools-direct/modify-tool-behavior/after-execution-modifiers.mdx
index 00701f332..267897d3a 100644
--- a/docs/content/docs/tools-direct/modify-tool-behavior/after-execution-modifiers.mdx
+++ b/docs/content/docs/tools-direct/modify-tool-behavior/after-execution-modifiers.mdx
@@ -5,7 +5,7 @@ llmGuardrails: "direct-execution"
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Tools and toolkits](/docs/tools-and-toolkits#meta-tools) for how sessions handle tool discovery and execution automatically.
</Callout>
After execution modifiers are part of Composio SDK's powerful middleware capabilities that allow you to customize and extend the behavior of tools.
@@ -182,3 +182,11 @@ const agenticTools = await composio.tools.get(
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Before execution modifiers" href="/docs/tools-direct/modify-tool-behavior/before-execution-modifiers" description="Modify tool arguments before execution" />
+ <Card icon={<Wrench />} title="Schema modifiers" href="/docs/tools-direct/modify-tool-behavior/schema-modifiers" description="Customize how tools appear to agents" />
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/modify-tool-behavior/before-execution-modifiers.mdx b/docs/content/docs/tools-direct/modify-tool-behavior/before-execution-modifiers.mdx
index 484730633..c9c8e3f05 100644
--- a/docs/content/docs/tools-direct/modify-tool-behavior/before-execution-modifiers.mdx
+++ b/docs/content/docs/tools-direct/modify-tool-behavior/before-execution-modifiers.mdx
@@ -5,7 +5,7 @@ llmGuardrails: "direct-execution"
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Tools and toolkits](/docs/tools-and-toolkits#meta-tools) for how sessions handle tool discovery and execution automatically.
</Callout>
Before execution modifiers are part of Composio SDK's powerful middleware capabilities that allow you to customize and extend the behavior of tools.
@@ -177,3 +177,11 @@ const agenticTools = await composio.tools.get(
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="After execution modifiers" href="/docs/tools-direct/modify-tool-behavior/after-execution-modifiers" description="Transform tool results after execution" />
+ <Card icon={<Wrench />} title="Schema modifiers" href="/docs/tools-direct/modify-tool-behavior/schema-modifiers" description="Customize how tools appear to agents" />
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/modify-tool-behavior/schema-modifiers.mdx b/docs/content/docs/tools-direct/modify-tool-behavior/schema-modifiers.mdx
index e3c07c940..06c14fbb8 100644
--- a/docs/content/docs/tools-direct/modify-tool-behavior/schema-modifiers.mdx
+++ b/docs/content/docs/tools-direct/modify-tool-behavior/schema-modifiers.mdx
@@ -5,7 +5,7 @@ llmGuardrails: "direct-execution"
---
<Callout type="info">
-If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. Sessions handle tool fetching, authentication, and execution automatically.
+If you're building an agent, we recommend using [sessions](/docs/configuring-sessions) instead. See [Tools and toolkits](/docs/tools-and-toolkits#meta-tools) for how sessions handle tool discovery and execution automatically.
</Callout>
Schema modifiers are part of Composio SDK's powerful middleware capabilities that allow you to customize and extend the behavior of tools.
@@ -267,3 +267,11 @@ console.log(tools);
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Before execution modifiers" href="/docs/tools-direct/modify-tool-behavior/before-execution-modifiers" description="Modify tool arguments before execution" />
+ <Card icon={<Wrench />} title="After execution modifiers" href="/docs/tools-direct/modify-tool-behavior/after-execution-modifiers" description="Transform tool results after execution" />
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+</Cards>
diff --git a/docs/content/docs/tools-direct/toolkit-versioning.mdx b/docs/content/docs/tools-direct/toolkit-versioning.mdx
index 89ea3e72e..d04bfdf68 100644
--- a/docs/content/docs/tools-direct/toolkit-versioning.mdx
+++ b/docs/content/docs/tools-direct/toolkit-versioning.mdx
@@ -166,3 +166,11 @@ console.log("Latest Version:", toolkit.meta.availableVersions?.[0]);
```
</Tab>
</Tabs>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Wrench />} title="Fetching tools" href="/docs/tools-direct/fetching-tools" description="Fetch and filter tools, inspect schemas, and search semantically" />
+ <Card icon={<Play />} title="Executing tools" href="/docs/tools-direct/executing-tools" description="Run tools with providers, agentic frameworks, or direct execution" />
+ <Card icon={<Terminal />} title="CLI" href="/docs/cli" description="Generate type-safe code from tool schemas with the Composio CLI" />
+</Cards>
diff --git a/docs/content/docs/triggers.mdx b/docs/content/docs/triggers.mdx
index f69935987..79fd90c15 100644
--- a/docs/content/docs/triggers.mdx
+++ b/docs/content/docs/triggers.mdx
@@ -26,7 +26,7 @@ There are two delivery types:
A trigger type is a template that defines what event to listen for and what configuration is required. For example, `GITHUB_COMMIT_EVENT` requires an `owner` and `repo`. Each toolkit exposes its own set of trigger types.
</Accordion>
<Accordion title="What happens when you create an active trigger?">
-When you create a trigger from a type, it's scoped to a specific user and connected account. For example, creating a `GITHUB_COMMIT_EVENT` trigger for user `alice` on the `composio` repo produces a trigger with its own ID.
+When you create a trigger from a type, it's scoped to a specific [user and connected account](/docs/users-and-sessions). For example, creating a `GITHUB_COMMIT_EVENT` trigger for user `alice` on the `composio` repo produces a trigger with its own ID.
</Accordion>
</Accordions>
@@ -41,4 +41,5 @@ Triggers are scoped to a connected account. If you haven't set up authentication
<Card title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="Receive trigger events via webhooks or SDK subscriptions" />
<Card title="Verifying webhooks" href="/docs/webhook-verification" description="Verify webhook signatures and understand payload versions" />
<Card title="Managing triggers" href="/docs/setting-up-triggers/managing-triggers" description="Discover, list, enable, disable, and delete triggers" />
+ <Card title="Example: Gmail labeler" href="/cookbooks/gmail-labeler" description="Build an automated email labeling agent using triggers" />
</Cards>
diff --git a/docs/content/docs/using-custom-auth-configuration.mdx b/docs/content/docs/using-custom-auth-configuration.mdx
index 077866f82..0d0acce01 100644
--- a/docs/content/docs/using-custom-auth-configuration.mdx
+++ b/docs/content/docs/using-custom-auth-configuration.mdx
@@ -63,3 +63,11 @@ const session = await composio.create("user_123", {
Your session will now use this auth config when users connect to this toolkit.
</Step>
</Steps>
+
+## What to read next
+
+<Cards>
+ <Card icon={<Palette />} title="White-labeling authentication" href="/docs/white-labeling-authentication" description="Use your own OAuth apps so users see your branding on consent screens" />
+ <Card icon={<Key />} title="Authentication overview" href="/docs/authentication" description="Connect Links, OAuth, API keys, and how Composio manages auth" />
+ <Card icon={<Wrench />} title="Configuring sessions" href="/docs/configuring-sessions" description="Pass auth configs, connected accounts, and toolkit restrictions to sessions" />
+</Cards>
diff --git a/docs/content/docs/webhook-verification.mdx b/docs/content/docs/webhook-verification.mdx
index 44707ae01..f91c51ec8 100644
--- a/docs/content/docs/webhook-verification.mdx
+++ b/docs/content/docs/webhook-verification.mdx
@@ -193,3 +193,11 @@ Metadata fields are mixed into the `data` object alongside event data.
</Tab>
</Tabs>
+## What to read next
+
+<Cards>
+ <Card icon={<Zap />} title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="Set up webhooks and SDK subscriptions to receive trigger events" />
+ <Card icon={<Zap />} title="Triggers overview" href="/docs/triggers" description="How Composio delivers event data from connected apps" />
+ <Card icon={<Zap />} title="Connection expiry events" href="/docs/subscribing-to-connection-expiry-events" description="Detect when OAuth connections expire and prompt re-authentication" />
+</Cards>
+
diff --git a/docs/content/docs/white-labeling-authentication.mdx b/docs/content/docs/white-labeling-authentication.mdx
index 02f107524..adc81b1a3 100644
--- a/docs/content/docs/white-labeling-authentication.mdx
+++ b/docs/content/docs/white-labeling-authentication.mdx
@@ -160,4 +160,6 @@ This makes the OAuth flow go through your domain first, then to Composio for tok
<Cards>
<Card icon={<Key />} title="Using custom auth configuration" href="/docs/using-custom-auth-configuration" description="Set up auth configs for toolkits that don't have Composio managed authentication" />
+ <Card icon={<Key />} title="Authentication overview" href="/docs/authentication" description="Connect Links, OAuth, API keys, and how Composio manages auth" />
+ <Card icon={<Wrench />} title="Configuring sessions" href="/docs/configuring-sessions" description="Pass auth configs, connected accounts, and toolkit restrictions to sessions" />
</Cards>
diff --git a/docs/content/docs/workbench.mdx b/docs/content/docs/workbench.mdx
index b0849b113..b5432d72b 100644
--- a/docs/content/docs/workbench.mdx
+++ b/docs/content/docs/workbench.mdx
@@ -4,15 +4,15 @@ description: A persistent Python sandbox for writing code, calling tools program
keywords: [workbench, sandbox, remote execution, bulk operations, data processing]
---
-The workbench is a persistent Python sandbox where your agent can write and execute code. It has access to all Composio tools programmatically, plus helper functions for calling LLMs, uploading files, and making API requests. State persists across calls within a session. The `COMPOSIO_REMOTE_BASH_TOOL` meta tool also runs commands in the same sandbox.
+The workbench is a persistent Python sandbox where your agent can write and execute code. It has access to all Composio tools programmatically, plus helper functions for calling LLMs, uploading files, and making API requests. State persists across calls within a [session](/docs/users-and-sessions). The `COMPOSIO_REMOTE_BASH_TOOL` meta tool also runs commands in the same sandbox.
<Callout>
-The workbench is part of the meta tools system. It's available when you create sessions, not when [executing tools directly](/docs/tools-direct/executing-tools).
+The workbench is part of the [meta tools](/docs/tools-and-toolkits#meta-tools) system. It's available when you create sessions, not when [executing tools directly](/docs/tools-direct/executing-tools).
</Callout>
## Where it fits
-Your agent starts with `SEARCH_TOOLS` to find the right tools, then uses `MULTI_EXECUTE` for straightforward calls. When the task involves bulk operations, data transformations, or multi-step logic, the agent uses `COMPOSIO_REMOTE_WORKBENCH` instead.
+Your agent starts with [`SEARCH_TOOLS` to find the right tools, then uses `MULTI_EXECUTE`](/docs/tools-and-toolkits#meta-tools) for straightforward calls. When the task involves bulk operations, data transformations, or multi-step logic, the agent uses `COMPOSIO_REMOTE_WORKBENCH` instead.
```mermaid
graph TD
@@ -72,7 +72,7 @@ The sandbox preserves variables and files across calls. The agent can paginate t
## What to read next
<Cards>
- <Card icon={<Zap />} title="Triggers" href="/docs/triggers" description="Event-driven payloads from connected apps" />
+ <Card icon={<Database />} title="Users & Sessions" href="/docs/users-and-sessions" description="How sessions scope tools, auth, and workbench state to a user" />
<Card icon={<Wrench />} title="Tools and toolkits" href="/docs/tools-and-toolkits" description="How meta tools discover, authenticate, and execute tools at runtime" />
- <Card icon={<Blocks />} title="Browse toolkits" href="/toolkits" description="Explore all available toolkits" />
+ <Card icon={<Zap />} title="Triggers" href="/docs/triggers" description="Event-driven payloads from connected apps" />
</Cards>