@devries-cameron20 / composio Mirror · read-only / commits / a932295de
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, 07:00 UTC

docs: add cross-linking to practical guides and getting started pages

Adds "What to read next" sections to 9 practical guide pages so readers aren't left at dead ends. Links point forward to sibling guides rather than back to concept pages. Also adds "How Composio works" to quickstart next steps, fixes an unclosed code block in in-chat-authentication, adds multi-tenancy keywords to projects page, and replaces em dashes with colons in projects. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Sushmitha Mallesh committed Feb 23, 2026 at 20:11 UTC a932295de3b2b678b893e1feaf69459c69c0aeb7
11 files changed +73 -8
docs/content/docs/authenticating-users/in-chat-authentication.mdx
+10 -1
@@ -183,4 +183,13 @@ Assistant: What would you like me to do today? Type 'exit' to end the conversati
183 Assistant: I need you to connect your GitHub account first.
184 Please click here to authorize: https://connect.composio.dev/link/ln_abc123
185
186 -> Done
\ No newline at end of file
186 +> Done
187 +```
188 +
189 +## What to read next
190 +
191 +<Cards>
192 + <Card icon={<ShieldCheck />} title="Manual authentication" href="/docs/authenticating-users/manually-authenticating" description="Pre-authenticate users before chat using Connect Links and session.authorize()" />
193 + <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" />
194 + <Card icon={<Wrench />} title="Configuring Sessions" href="/docs/configuring-sessions" description="Restrict toolkits, set custom auth configs, and select connected accounts" />
195 +</Cards>
\ No newline at end of file
docs/content/docs/authenticating-users/manually-authenticating.mdx
+9
@@ -147,6 +147,7 @@ const session = await composio.create("user_123", {
147
148 ## Putting it together
149
150 +
151 A common pattern is to verify all required connections before starting the agent:
152
153 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
@@ -212,3 +213,11 @@ console.log(`All toolkits connected! MCP URL: ${session.mcp.url}`);
213 ```
214 </Tab>
215 </Tabs>
216 +
217 +## What to read next
218 +
219 +<Cards>
220 + <Card icon={<MessageCircle />} title="In-chat authentication" href="/docs/authenticating-users/in-chat-authentication" description="Let the agent prompt users to connect accounts during conversation instead" />
221 + <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" />
222 + <Card icon={<Database />} title="Managing multiple accounts" href="/docs/managing-multiple-connected-accounts" description="Handle users with multiple accounts for the same toolkit (e.g., work and personal Gmail)" />
223 +</Cards>
docs/content/docs/configuring-sessions.mdx
+9
@@ -271,3 +271,12 @@ toolkits.items.forEach((toolkit) => {
271 </Tabs>
272
273 Returns the first 20 toolkits by default.
274 +
275 +## What to read next
276 +
277 +<Cards>
278 + <Card icon={<MessageCircle />} title="In-chat authentication" href="/docs/authenticating-users/in-chat-authentication" description="Let the agent prompt users to connect accounts during conversation" />
279 + <Card icon={<ShieldCheck />} title="Manual authentication" href="/docs/authenticating-users/manually-authenticating" description="Pre-authenticate users before chat using Connect Links and session.authorize()" />
280 + <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" />
281 + <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" />
282 +</Cards>
docs/content/docs/projects.mdx
+6 -6
@@ -1,10 +1,10 @@
1 ---
2 title: Projects
3 -description: Organize your Composio resources with projects and manage team access
4 -keywords: [projects, organizations, teams, api keys, environments]
3 +description: Isolate resources across environments or clients using projects for multi-tenancy
4 +keywords: [projects, organizations, teams, api keys, environments, multi-tenancy, multitenancy, tenant isolation]
5 ---
6
7 -Every Composio account belongs to an **organization**. Inside an organization, **projects** are isolated environments that scope your API keys, connected accounts, auth configs, and webhook configurations. Resources in one project are not accessible from another.
7 +Projects are Composio's multi-tenancy primitive. Every Composio account belongs to an **organization**. Inside an organization, **projects** are isolated environments that scope your API keys, connected accounts, auth configs, and webhook configurations. Resources in one project are not accessible from another.
8
9 ```mermaid
10 graph LR
@@ -19,9 +19,9 @@ graph LR
19 ```
20
21 Common reasons to use multiple projects:
22 -- **Separate environments** — keep production and staging isolated
23 -- **Separate products** — keep resources for different apps independent
24 -- **Client isolation** — give each client their own project with separate credentials and data
22 +- **Separate environments**: keep production and staging isolated
23 +- **Separate products**: keep resources for different apps independent
24 +- **Client isolation**: give each client their own project with separate credentials and data
25
26 ## Managing projects
27
docs/content/docs/quickstart.mdx
+1
@@ -831,5 +831,6 @@ readline.close();
831 <Cards>
832 <Card icon={<Wrench />} title="Configuring Sessions" href="/docs/configuring-sessions" description="Restrict toolkits, set custom auth configs, and select connected accounts" />
833 <Card icon={<Key />} title="Authenticating Users" href="/docs/authentication" description="Learn how users connect their accounts via Connect Links, OAuth, and API keys" />
834 + <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" />
835 </Cards>
836
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+7
@@ -85,3 +85,10 @@ The trigger instance uses the toolkit version configured during Composio initial
85 5. Click **Create Trigger**
86
87 <Video src="/videos/triggers-creation.mp4" caption="Creating a GitHub Star Added trigger from the dashboard" />
88 +
89 +## What to read next
90 +
91 +<Cards>
92 + <Card icon={<Zap />} title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="Receive trigger events via webhooks or SDK subscriptions" />
93 + <Card icon={<Zap />} title="Managing triggers" href="/docs/setting-up-triggers/managing-triggers" description="List, enable, disable, and delete trigger instances" />
94 +</Cards>
docs/content/docs/setting-up-triggers/managing-triggers.mdx
+8
@@ -121,3 +121,11 @@ await composio.triggers.delete('ti_abcd123');
121 <Callout type="warn">
122 Deleting a trigger is permanent. Use `disable()` instead to temporarily stop receiving events.
123 </Callout>
124 +
125 +## What to read next
126 +
127 +<Cards>
128 + <Card icon={<Zap />} title="Creating triggers" href="/docs/setting-up-triggers/creating-triggers" description="Create trigger instances to start receiving events from connected apps" />
129 + <Card icon={<Zap />} title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="Set up webhooks or SDK subscriptions to handle trigger events" />
130 + <Card icon={<ShieldCheck />} title="Verifying webhooks" href="/docs/webhook-verification" description="Validate webhook signatures to ensure payloads are authentic" />
131 +</Cards>
docs/content/docs/setting-up-triggers/subscribing-to-events.mdx
+5 -1
@@ -222,6 +222,10 @@ Every webhook event includes a `metadata` object that tells you exactly where it
222
223 Use `trigger_id` to match events to a specific trigger instance, or `trigger_slug` to handle all events of a certain type. These fields can also be passed as filters when using [SDK subscriptions](#sdk-subscriptions).
224
225 +## What to read next
226 +
227 <Cards>
226 - <Card title="Troubleshooting triggers" href="/docs/troubleshooting/triggers" description="Not receiving events? Check common trigger issues and how to fix them" />
228 + <Card icon={<ShieldCheck />} title="Verifying webhooks" href="/docs/webhook-verification" description="Validate webhook signatures to ensure payloads are authentic" />
229 + <Card icon={<Zap />} title="Managing triggers" href="/docs/setting-up-triggers/managing-triggers" description="List, enable, disable, and delete trigger instances" />
230 + <Card icon={<Zap />} title="Troubleshooting triggers" href="/docs/troubleshooting/triggers" description="Not receiving events? Check common trigger issues and how to fix them" />
231 </Cards>
docs/content/docs/toolkits/enable-and-disable-toolkits.mdx
+6
@@ -267,3 +267,9 @@ const session = await composio.create("user_123", {
267 </Tab>
268 </Tabs>
269
270 +## What to read next
271 +
272 +<Cards>
273 + <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" />
274 +</Cards>
275 +
docs/content/docs/toolkits/fetching-tools-and-toolkits.mdx
+6
@@ -172,3 +172,9 @@ console.log(tool.outputParameters);
172 ```
173 </Tab>
174 </Tabs>
175 +
176 +## What to read next
177 +
178 +<Cards>
179 + <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" />
180 +</Cards>
docs/content/docs/white-labeling-authentication.mdx
+6
@@ -155,3 +155,9 @@ export default function handler(req: NextApiRequest, res: NextApiResponse) {
155 3. Update your auth config in the Composio dashboard to use your custom redirect URI.
156
157 This makes the OAuth flow go through your domain first, then to Composio for token storage.
158 +
159 +## What to read next
160 +
161 +<Cards>
162 + <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" />
163 +</Cards>