@devries-cameron20 / composio Mirror · read-only / commits / c901397bc
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 21, 18:30 UTC

feat(docs): attribute dashboard sign-ups with UTM params on all docs links

Tag every dashboard.composio.dev link in authored docs content and components with utm_source=docs plus utm_medium/utm_campaign, and enforce the convention going forward: an ESLint no-restricted-syntax rule covers TS/TSX and a static bun test covers MDX (runs in docs-tests CI). - content links use utm_medium=content and utm_campaign=<page-slug> - content/reference is excluded (generated upstream) - delete unused landing-hero/_stub-links.ts - fix the no-html-link-for-pages errors; downgrade the pre-existing react-hooks compiler violations to warnings until burned down, so bun run lint exits with zero errors Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Sarah Simionescu committed Jul 21, 2026 at 16:05 UTC c901397bc56766efe5519b6ab107f22585200ad6
37 files changed +166 -63
docs/AGENTS.md
+1
@@ -39,3 +39,4 @@ bun run generate:api-index
39 - API reference pages and toolkit/meta-tool data are generated. Do not hand-edit generated data unless the local generator owns it.
40 - Changelog entries require `title` and `date` frontmatter, and dates use `YYYY-MM-DD`.
41 - Prefer cURL for API interactions because docs are consumed by humans and AI crawlers.
42 +- Links to `dashboard.composio.dev` must carry `utm_source=docs`, `utm_medium`, and `utm_campaign` (content links use `utm_medium=content` and `utm_campaign=<page-slug>`). ESLint enforces TS/TSX; `tests/static/utm-links.test.ts` enforces MDX.
docs/app/(home)/toolkits/[[...slug]]/page.tsx
+2 -1
@@ -1,4 +1,5 @@
1 import { toolkitsSource, getOgImageUrl } from '@/lib/source';
2 +import Link from 'next/link';
3 import { notFound } from 'next/navigation';
4 import { getMDXComponents } from '@/mdx-components';
5 import { ToolkitDetail } from '@/components/toolkits/toolkit-detail';
@@ -209,7 +210,7 @@ export default async function ToolkitsPage({ params }: { params: Promise<{ slug?
210 const MDXContent = page.data.body;
211 return (
212 <div>
212 - <a href="/toolkits" className="text-sm text-fd-muted-foreground no-underline hover:text-fd-foreground hover:underline">← All Toolkits</a>
213 + <Link href="/toolkits" className="text-sm text-fd-muted-foreground no-underline hover:text-fd-foreground hover:underline">← All Toolkits</Link>
214 <div className="mt-2 flex items-start justify-between gap-4">
215 <h1 className="text-3xl font-bold text-fd-foreground">{page.data.title}</h1>
216 <PageActions path={page.url} variant="inline" />
docs/app/global-error.tsx
+2
@@ -50,6 +50,8 @@ export default function GlobalError({
50 >
51 Try again
52 </button>
53 + {/* Client-side nav may be broken inside the global error boundary; a full reload is intentional. */}
54 + {/* eslint-disable-next-line @next/next/no-html-link-for-pages */}
55 <a
56 className="ge-btn-secondary"
57 href="/"
docs/components/landing-hero/_stub-links.ts deleted
-7
@@ -1,7 +0,0 @@
1 -/** Subset of the landing-page link table the hero needs. Kept in this
2 - * shape so the ported `hero-section.tsx` keeps reading `URLS.DASHBOARD`
3 - * and `URLS.DOCS` without code changes. */
4 -export const URLS = {
5 - DASHBOARD: "https://dashboard.composio.dev",
6 - DOCS: "/docs/quickstart",
7 -} as const;
docs/components/toolkits/toolkits-landing.tsx
+1 -1
@@ -158,7 +158,7 @@ export function ToolkitsLanding() {
158 <div className="flex flex-wrap items-center gap-2">
159 <PageActions path="/toolkits" variant="inline" />
160 <a
161 - href="https://dashboard.composio.dev/~/project/playground"
161 + href="https://dashboard.composio.dev/~/project/playground?utm_source=docs&utm_medium=toolkits&utm_campaign=playground"
162 target="_blank"
163 rel="noopener noreferrer"
164 className="inline-flex items-center gap-1.5 rounded-md border border-fd-border bg-fd-background px-3 py-1.5 text-sm font-medium text-fd-foreground transition-colors hover:bg-fd-accent"
docs/content/changelog/01-08-26-mcp-api-key-enforcement.mdx
+1 -1
@@ -54,7 +54,7 @@ curl -X POST "https://mcp.composio.dev/{your_mcp_server_url}" \
54
55 ### Via Dashboard
56
57 -1. Navigate to [Project Settings](https://dashboard.composio.dev/{workspace}/{project}/settings)
57 +1. Navigate to [Project Settings](https://dashboard.composio.dev/{workspace}/{project}/settings?utm_source=docs&utm_medium=content&utm_campaign=changelog-01-08-26-mcp-api-key-enforcement)
58 2. Go to the **Project Configuration** tab
59 3. Find the **"Require API Key for MCP"** toggle
60 4. Enable the toggle
docs/content/changelog/02-15-26-webhook-v3-default-new-orgs.mdx
+2 -2
@@ -21,7 +21,7 @@ Starting today, every new organization created on Composio will automatically us
21 Nothing changes for existing organizations. If your organization was created before today:
22
23 - You will continue to receive webhooks in your current format (V1 or V2)
24 -- You can opt-in to V3 at any time through your [project settings](https://dashboard.composio.dev)
24 +- You can opt-in to V3 at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs)
25
26 ## V3 Payload Recap
27
@@ -46,7 +46,7 @@ Nothing changes for existing organizations. If your organization was created bef
46
47 ## How to Switch to V3 (Existing Organizations)
48
49 -1. Go to your project settings in the [Composio dashboard](https://dashboard.composio.dev)
49 +1. Go to your project settings in the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-02-15-26-webhook-v3-default-new-orgs)
50 2. Navigate to the Webhooks section
51 3. Select **Webhook Payload Version: V3**
52 4. Update your webhook handlers using the [migration guide](/docs/changelog/2025/12/30#migration-guide)
docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
+1 -1
@@ -23,7 +23,7 @@ From **March 5, 2026**, all projects in newly created organizations will have `r
23 Nothing changes for existing organizations. If your organization was created before March 5, 2026:
24
25 - Your current `require_mcp_api_key` setting remains unchanged
26 -- You can opt in at any time through your [project settings](https://dashboard.composio.dev) or via the API
26 +- You can opt in at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-03-04-26-mcp-api-key-default-new-orgs) or via the API
27
28 ### Opting Out (New Organizations)
29
docs/content/changelog/03-25-26-mcp-endpoint-removed.mdx
+2 -2
@@ -6,7 +6,7 @@ date: "2026-03-25"
6
7 We've permanently removed the deprecated `mcp.composio.dev` endpoint that was deprecated in November 2025.
8
9 -This endpoint was part of our early MCP integration experiments and the latest MCP offering from Composio is [Composio For You](https://dashboard.composio.dev/~/org/connect) (access 1000+ apps through one MCP).
9 +This endpoint was part of our early MCP integration experiments and the latest MCP offering from Composio is [Composio For You](https://dashboard.composio.dev/~/org/connect?utm_source=docs&utm_medium=content&utm_campaign=changelog-03-25-26-mcp-endpoint-removed) (access 1000+ apps through one MCP).
10
11 ### What Changed
12
@@ -16,6 +16,6 @@ This endpoint was part of our early MCP integration experiments and the latest M
16
17 ### Migrating?
18
19 -If you were still using the old endpoint, head to [https://dashboard.composio.dev/~/org/connect](https://dashboard.composio.dev/~/org/connect) to get started with the new MCP.
19 +If you were still using the old endpoint, head to [https://dashboard.composio.dev/~/org/connect](https://dashboard.composio.dev/~/org/connect?utm_source=docs&utm_medium=content&utm_campaign=changelog-03-25-26-mcp-endpoint-removed) to get started with the new MCP.
20
21 Questions? Reach out to support@composio.dev
docs/content/changelog/04-24-26-trigger-disabled-event.mdx
+1 -1
@@ -21,7 +21,7 @@ The event does not fire when you disable a trigger yourself — neither through
21
22 ## Subscribe
23
24 -Add `composio.trigger.disabled` to your subscription's `enabled_events` — via the [dashboard webhook settings](https://dashboard.composio.dev/~/project/settings/webhook) or the Webhook Subscriptions API:
24 +Add `composio.trigger.disabled` to your subscription's `enabled_events` — via the [dashboard webhook settings](https://dashboard.composio.dev/~/project/settings/webhook?utm_source=docs&utm_medium=content&utm_campaign=changelog-04-24-26-trigger-disabled-event) or the Webhook Subscriptions API:
25
26 ```bash
27 curl -X PATCH https://backend.composio.dev/api/v3/webhook_subscriptions/ws_your-subscription-id \
docs/content/docs/auth-configuration/white-labeling.mdx
+2 -2
@@ -27,7 +27,7 @@ The Connect Link is the hosted page your users see when connecting their account
27
28 To replace it with your own branding:
29
30 -1. Go to **Project Settings** → [**Auth Screen**](https://dashboard.composio.dev/~/project/settings/auth-screen)
30 +1. Go to **Project Settings** → [**Auth Screen**](https://dashboard.composio.dev/~/project/settings/auth-screen?utm_source=docs&utm_medium=content&utm_campaign=docs-auth-configuration-white-labeling)
31 2. Upload your **Logo** and set your **App Title**
32
33 This applies to all Connect Link flows across all toolkits. Each project has one logo and app title, so if you need different branding per product, use separate projects.
@@ -68,7 +68,7 @@ Step-by-step guides: [Google](https://composio.dev/auth/googleapps) | [Slack](ht
68 <Step>
69 <StepTitle>Create an auth config in Composio</StepTitle>
70
71 -In the [Composio dashboard](https://dashboard.composio.dev):
71 +In the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-auth-configuration-white-labeling):
72
73 1. Go to **Authentication management** → **Create Auth Config**
74 2. Select the toolkit (e.g., GitHub)
docs/content/docs/composio-connect.mdx
+15 -15
@@ -23,7 +23,7 @@ To get started, pick your client below.
23 <Step>
24 <StepTitle>Get your API key</StepTitle>
25
26 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
26 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
27
28 </Step>
29 <Step>
@@ -53,7 +53,7 @@ Type `/mcp` in Claude Code to open the MCP server manager and confirm Composio a
53 <Step>
54 <StepTitle>Get your API key</StepTitle>
55
56 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
56 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
57
58 </Step>
59 <Step>
@@ -89,7 +89,7 @@ Run `codex mcp list` to confirm Composio appears as a registered MCP server.
89 <Step>
90 <StepTitle>Get your API key</StepTitle>
91
92 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
92 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
93
94 </Step>
95 <Step>
@@ -175,7 +175,7 @@ A browser window will open automatically. Sign in to authorize ChatGPT to access
175 <Step>
176 <StepTitle>Get your API key</StepTitle>
177
178 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
178 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
179
180 </Step>
181 <Step>
@@ -214,7 +214,7 @@ Restart Cursor. Composio tools are now available in Composer and Agent mode.
214 <Step>
215 <StepTitle>Get your API key</StepTitle>
216
217 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
217 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
218
219 </Step>
220 <Step>
@@ -252,7 +252,7 @@ Select **API Key** as the authentication type. Set the key to `x-consumer-api-ke
252 <Step>
253 <StepTitle>Get your API key</StepTitle>
254
255 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
255 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
256
257 </Step>
258 <Step>
@@ -294,7 +294,7 @@ Open a GitHub Copilot chat. Composio tools are now available.
294 <Step>
295 <StepTitle>Get your API key</StepTitle>
296
297 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
297 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
298
299 </Step>
300 <Step>
@@ -339,7 +339,7 @@ Restart Windsurf. Composio tools are now available in Cascade.
339 <Step>
340 <StepTitle>Get your API key</StepTitle>
341
342 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
342 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
343
344 </Step>
345 <Step>
@@ -383,7 +383,7 @@ Save the configuration. Composio tools are now available in Cline.
383 <Step>
384 <StepTitle>Get your API key</StepTitle>
385
386 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
386 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
387
388 </Step>
389 <Step>
@@ -415,7 +415,7 @@ Select **Custom headers**. Add a header with name `x-consumer-api-key` and paste
415 <Step>
416 <StepTitle>Get your API key</StepTitle>
417
418 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
418 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
419
420 </Step>
421 <Step>
@@ -447,7 +447,7 @@ Select **Header Auth** and create a new credential. Set the header name to `x-co
447 <Step>
448 <StepTitle>Get your API key</StepTitle>
449
450 -Open the [Composio dashboard](https://dashboard.composio.dev) and click **AI Clients** in the sidebar. Select your client and copy your API key.
450 +Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **AI Clients** in the sidebar. Select your client and copy your API key.
451
452 </Step>
453 <Step>
@@ -477,7 +477,7 @@ Use this config with any MCP-compatible client:
477
478 ## Connect your apps
479
480 -Your agent will prompt you to connect apps when needed. If you want to connect apps ahead of time, open the [Composio dashboard](https://dashboard.composio.dev) and click **Connect Apps** in the sidebar.
480 +Your agent will prompt you to connect apps when needed. If you want to connect apps ahead of time, open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **Connect Apps** in the sidebar.
481
482 ## Available MCP tools
483
@@ -503,17 +503,17 @@ Composio Connect exposes 7 meta-tools that orchestrate access to all supported a
503
504 ### The OAuth link expired or didn't open
505
506 -OAuth links are short-lived. If the browser window doesn't open or the link has expired, ask your agent to retry the action — Composio will generate a fresh link. You can also open the [Composio dashboard](https://dashboard.composio.dev), click **Connect Apps**, and start the flow manually.
506 +OAuth links are short-lived. If the browser window doesn't open or the link has expired, ask your agent to retry the action — Composio will generate a fresh link. You can also open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect), click **Connect Apps**, and start the flow manually.
507
508 ### An app action is failing with an auth error
509
510 -1. Open the [Composio dashboard](https://dashboard.composio.dev) and click **Connect Apps**.
510 +1. Open the [Composio dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **Connect Apps**.
511 2. Find the app in question. If the connection is unhealthy, click **Disconnect** and reconnect.
512 3. Retry the action in your agent.
513
514 ### I want to remove or reconnect an app
515
516 -Open [dashboard.composio.dev](https://dashboard.composio.dev) and click **Connect Apps**. From there you can disconnect, delete, or re-authorize any app.
516 +Open [dashboard.composio.dev](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-composio-connect) and click **Connect Apps**. From there you can disconnect, delete, or re-authorize any app.
517
518 ### I still need help
519
docs/content/docs/configuring-sessions.mdx
+1 -1
@@ -844,7 +844,7 @@ console.log(result.sessionId, result.deleted);
844
845 ## Browsing the catalog
846
847 -Before configuring a session, explore the toolkits and tools available. Browse them visually at [dashboard.composio.dev](https://dashboard.composio.dev) or in the [docs catalog](/toolkits), or fetch them programmatically:
847 +Before configuring a session, explore the toolkits and tools available. Browse them visually at [dashboard.composio.dev](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-configuring-sessions) or in the [docs catalog](/toolkits), or fetch them programmatically:
848
849 <Tabs groupId="language" items={['Python', 'TypeScript']} persist>
850 <Tab value="Python">
docs/content/docs/custom-app-vs-managed-app.mdx
+1 -1
@@ -40,7 +40,7 @@ The steps below use the dashboard. To create auth configs in code instead, for e
40 <Step>
41 <StepTitle>Create the auth config in the Composio dashboard</StepTitle>
42
43 -In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs):
43 +In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=docs-custom-app-vs-managed-app):
44
45 1. Click **Create Auth Config**
46 2. Select the toolkit
docs/content/docs/programmatic-auth-configs.mdx
+1 -1
@@ -4,7 +4,7 @@ description: Create auth configs in code and pass them to a session
4 keywords: [create auth config, auth config sdk, programmatic auth, provision auth config, auth config id]
5 ---
6
7 -An [auth config](/docs/authentication#behind-the-scenes) is a blueprint for how a toolkit authenticates: the method, scopes, and credentials. Most of the time you create one in the [dashboard](https://dashboard.composio.dev/~/project/auth-configs) and reuse it. Create them in code when you provision auth dynamically: a config per customer, per environment, or spun up and torn down as part of your app's lifecycle.
7 +An [auth config](/docs/authentication#behind-the-scenes) is a blueprint for how a toolkit authenticates: the method, scopes, and credentials. Most of the time you create one in the [dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=docs-programmatic-auth-configs) and reuse it. Create them in code when you provision auth dynamically: a config per customer, per environment, or spun up and torn down as part of your app's lifecycle.
8
9 `composio.authConfigs.create()` returns an auth config ID like `ac_xxxxxxxx`. Store that ID, then [pass it to a session](#use-the-auth-config-in-a-session) so the session authenticates with it.
10
docs/content/docs/providers/anthropic.mdx
+2 -2
@@ -38,7 +38,7 @@ The `AnthropicProvider` transforms Composio tools into the format the Claude Mes
38 **Configure API Keys**
39
40 <Callout type="info">
41 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
41 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-anthropic) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
42 </Callout>
43
44 ```txt title=".env"
@@ -183,7 +183,7 @@ The `ClaudeAgentSDKProvider` exposes your Composio tools to the Claude Agent SDK
183 **Configure API Keys**
184
185 <Callout type="info">
186 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
186 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-anthropic) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
187 </Callout>
188
189 ```txt title=".env"
docs/content/docs/providers/autogen.mdx
+1 -1
@@ -19,7 +19,7 @@ The provider runs on the [`ag2`](https://github.com/ag2ai/ag2) distribution, the
19 **Configure API Keys**
20
21 <Callout type="info">
22 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
22 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-autogen) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
23 </Callout>
24
25 ```txt title=".env"
docs/content/docs/providers/crewai.mdx
+1 -1
@@ -17,7 +17,7 @@ The CrewAI provider turns Composio tools into CrewAI [`BaseTool`](https://docs.c
17 **Configure API Keys**
18
19 <Callout type="info">
20 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
20 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-crewai) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
21 </Callout>
22
23 ```txt title=".env"
docs/content/docs/providers/google.mdx
+2 -2
@@ -33,7 +33,7 @@ In Python, the Gemini provider (`composio_gemini`) wraps Composio tools as typed
33 **Configure API Keys**
34
35 <Callout type="info">
36 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `GOOGLE_API_KEY` with your [Google API key](https://aistudio.google.com/apikey).
36 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-google) and `GOOGLE_API_KEY` with your [Google API key](https://aistudio.google.com/apikey).
37 </Callout>
38
39 ```txt title=".env"
@@ -139,7 +139,7 @@ The Google ADK provider transforms Composio tools into ADK's `FunctionTool` form
139 **Configure API Keys**
140
141 <Callout type="info">
142 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `GOOGLE_API_KEY` with your [Google API key](https://aistudio.google.com/apikey).
142 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-google) and `GOOGLE_API_KEY` with your [Google API key](https://aistudio.google.com/apikey).
143 </Callout>
144
145 ```txt title=".env"
docs/content/docs/providers/langchain.mdx
+2 -2
@@ -33,7 +33,7 @@ The LangChain provider transforms each Composio tool into a LangChain [`DynamicS
33 **Configure API Keys**
34
35 <Callout type="info">
36 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
36 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-langchain) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
37 </Callout>
38
39 ```txt title=".env"
@@ -139,7 +139,7 @@ The LangGraph provider transforms Composio tools into the same LangChain `Dynami
139 **Configure API Keys**
140
141 <Callout type="info">
142 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
142 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-langchain) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
143 </Callout>
144
145 ```txt title=".env"
docs/content/docs/providers/llamaindex.mdx
+1 -1
@@ -24,7 +24,7 @@ The LlamaIndex provider turns Composio tools into LlamaIndex [`FunctionTool`](ht
24 **Configure API Keys**
25
26 <Callout type="info">
27 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
27 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-llamaindex) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
28 </Callout>
29
30 ```txt title=".env"
docs/content/docs/providers/mastra.mdx
+1 -1
@@ -17,7 +17,7 @@ The Mastra provider transforms Composio tools into [Mastra's tool format](https:
17 **Configure API Keys**
18
19 <Callout type="info">
20 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
20 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-mastra) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
21 </Callout>
22
23 ```txt title=".env"
docs/content/docs/providers/openai.mdx
+3 -3
@@ -40,7 +40,7 @@ The `OpenAIResponsesProvider` transforms Composio tools into OpenAI's function-c
40 **Configure API Keys**
41
42 <Callout type="info">
43 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
43 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-openai) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
44 </Callout>
45
46 ```txt title=".env"
@@ -184,7 +184,7 @@ The `OpenAIProvider` targets the Chat Completions API and is the default provide
184 **Configure API Keys**
185
186 <Callout type="info">
187 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
187 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-openai) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
188 </Callout>
189
190 ```txt title=".env"
@@ -318,7 +318,7 @@ The `OpenAIAgentsProvider` transforms Composio tools into the Agents SDK tool fo
318 **Configure API Keys**
319
320 <Callout type="info">
321 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
321 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-openai) and `OPENAI_API_KEY` with your [OpenAI API key](https://platform.openai.com/api-keys).
322 </Callout>
323
324 ```txt title=".env"
docs/content/docs/providers/vercel.mdx
+1 -1
@@ -17,7 +17,7 @@ The Vercel AI SDK provider transforms Composio tools into Vercel's [tool format]
17 **Configure API Keys**
18
19 <Callout type="info">
20 -Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
20 +Set `COMPOSIO_API_KEY` with your API key from [Settings](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=docs-providers-vercel) and `ANTHROPIC_API_KEY` with your [Anthropic API key](https://console.anthropic.com/settings/keys).
21 </Callout>
22
23 ```txt title=".env"
docs/content/docs/single-toolkit-mcp.mdx
+1 -1
@@ -89,7 +89,7 @@ console.log(`Server created: ${server.id}`);
89 </Tabs>
90
91 <Callout type="info">
92 - You can also create and manage MCP configs from the [Composio dashboard](https://dashboard.composio.dev/~/org/connect/clients).
92 + You can also create and manage MCP configs from the [Composio dashboard](https://dashboard.composio.dev/~/org/connect/clients?utm_source=docs&utm_medium=content&utm_campaign=docs-single-toolkit-mcp).
93 </Callout>
94 </Step>
95
docs/content/docs/tools-direct/authenticating-tools.mdx
+1 -1
@@ -26,7 +26,7 @@ An **Auth Config** is a blueprint that defines how authentication works for a to
26 <Step>
27 <StepTitle>Selecting a toolkit</StepTitle>
28
29 -Navigate to [Auth Configs](https://dashboard.composio.dev/~/project/auth-configs) tab in your dashboard and click "**Create Auth Config**". Find and select the toolkit you want to integrate (e.g., **Gmail**, **Slack**, **GitHub**).
29 +Navigate to [Auth Configs](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=docs-tools-direct-authenticating-tools) tab in your dashboard and click "**Create Auth Config**". Find and select the toolkit you want to integrate (e.g., **Gmail**, **Slack**, **GitHub**).
30 </Step>
31
32 <Step>
docs/content/docs/tools-direct/executing-tools.mdx
+1 -1
@@ -211,7 +211,7 @@ If you just want to call a tool without using any framework or LLM provider, you
211 <Callout type="info">
212 **Finding tool parameters and types:**
213
214 -**Platform UI**: [Auth Configs](https://dashboard.composio.dev/~/project/auth-configs) → Select your toolkit → Tools & Triggers → Select the tool to see its required and optional parameters
214 +**Platform UI**: [Auth Configs](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=docs-tools-direct-executing-tools) → Select your toolkit → Tools & Triggers → Select the tool to see its required and optional parameters
215
216 **CLI**: For Python and TypeScript projects, run `composio generate` to generate types. [Learn more →](/docs/cli#generate-type-definitions)
217 </Callout>
docs/content/docs/tools-direct/fetching-tools.mdx
+1 -1
@@ -61,7 +61,7 @@ const tool = await composio.tools.getRawComposioToolBySlug("GMAIL_SEND_EMAIL");
61 Generate type-safe code for direct SDK execution with [`composio generate`](/docs/cli#generate-type-definitions). This creates TypeScript or Python types from tool schemas.
62
63 <Callout type="info">
64 -View tool parameters and schemas visually in the [Composio platform](https://dashboard.composio.dev). Navigate to any toolkit and select a tool to see its input/output parameters.
64 +View tool parameters and schemas visually in the [Composio platform](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-tools-direct-fetching-tools). Navigate to any toolkit and select a tool to see its input/output parameters.
65 </Callout>
66
67 ## Filtering tools
docs/content/docs/tools-direct/toolkit-versioning.mdx
+2 -2
@@ -12,7 +12,7 @@ If you're building an agent, we recommend using [sessions](/docs/configuring-ses
12
13 Toolkit versioning ensures your tools behave consistently across deployments. You can pin specific versions in production, test new releases in development, and roll back when needed.
14
15 -To view available versions, go to [Dashboard](https://dashboard.composio.dev) > **All Toolkits** > select a toolkit. The version dropdown shows the latest and all available versions:
15 +To view available versions, go to [Dashboard](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-tools-direct-toolkit-versioning) > **All Toolkits** > select a toolkit. The version dropdown shows the latest and all available versions:
16
17 ![Toolkit version selector on the Composio dashboard](/images/toolkit-version-dashboard.png)
18
@@ -25,7 +25,7 @@ Starting from Python SDK v0.9.0 and TypeScript SDK v0.2.0, specifying versions i
25 ## Default version behavior
26
27 <Callout type="warn">
28 -When no version is specified, the API defaults to the base version (`00000000_00`), **not** the latest version. This means the response may contain fewer tools than what's shown on the [platform UI](https://dashboard.composio.dev). To get all available tools including ones added in newer versions, explicitly set `toolkit_versions` to `"latest"` or a specific version.
28 +When no version is specified, the API defaults to the base version (`00000000_00`), **not** the latest version. This means the response may contain fewer tools than what's shown on the [platform UI](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=docs-tools-direct-toolkit-versioning). To get all available tools including ones added in newer versions, explicitly set `toolkit_versions` to `"latest"` or a specific version.
29 </Callout>
30
31 This applies to both the SDK and direct REST API calls:
docs/content/docs/white-labeling-authentication.mdx
+1 -1
@@ -19,7 +19,7 @@ The Connect Link is the hosted page your users see when connecting their account
19
20 To replace it with your own branding:
21
22 -1. Go to **Project Settings** → [**Auth Screen**](https://dashboard.composio.dev/~/project/settings/auth-screen)
22 +1. Go to **Project Settings** → [**Auth Screen**](https://dashboard.composio.dev/~/project/settings/auth-screen?utm_source=docs&utm_medium=content&utm_campaign=docs-white-labeling-authentication)
23 2. Upload your **Logo** and set your **App Title**
24
25 This applies to all Connect Link flows across all toolkits, for both [in-chat](/docs/authentication#in-chat-authentication) and [manual](/docs/manually-authenticating) authentication. Each project has one logo and app title, so if you need different branding per product, use separate projects.
docs/content/examples/general-agent-with-pi.mdx
+1 -1
@@ -26,7 +26,7 @@ Below you build the whole thing from scratch: a basic agent first, then a piece
26
27 ## Setup
28
29 -You need a [Composio API key](https://dashboard.composio.dev), a publicly reachable URL for your server, and [Bun](https://bun.sh).
29 +You need a [Composio API key](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=examples-general-agent-with-pi), a publicly reachable URL for your server, and [Bun](https://bun.sh).
30
31 <Accordions>
32 <Accordion title="No public URL? Use a Cloudflare tunnel">
docs/content/examples/imessage-agent.mdx
+1 -1
@@ -35,7 +35,7 @@ Below you build the integration core: the custom toolkit first, then the wiring
35
36 ## Setup
37
38 -You need a [Composio API key](https://dashboard.composio.dev) and macOS (the iMessage tools drive Messages.app, Contacts.app, and the local `chat.db`).
38 +You need a [Composio API key](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=examples-imessage-agent) and macOS (the iMessage tools drive Messages.app, Contacts.app, and the local `chat.db`).
39
40 <Steps>
41 <Step>
docs/content/examples/local-sandbox-pr-reviewer.mdx
+1 -1
@@ -30,7 +30,7 @@ Below you build the host orchestration from scratch: a bare client first, then a
30
31 ## Setup
32
33 -You need a [Composio API key](https://dashboard.composio.dev), an OpenAI API key for the reviewer agent, a GitHub connection for your `COMPOSIO_USER_ID`, and [Bun](https://bun.sh).
33 +You need a [Composio API key](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=examples-local-sandbox-pr-reviewer), an OpenAI API key for the reviewer agent, a GitHub connection for your `COMPOSIO_USER_ID`, and [Bun](https://bun.sh).
34
35 <Accordions>
36 <Accordion title="No sandbox provider? Use the E2B sample runner">
docs/content/examples/standup-slackbot.mdx
+2 -2
@@ -51,7 +51,7 @@ The Slack bot itself follows a deterministic flow: the same menu every day. When
51
52 ## Setup
53
54 -You need a [Composio API key](https://dashboard.composio.dev/~/project/settings/api-keys), a Slack workspace you can install an app into, and Node with [tsx](https://nodejs.org). The finished bot deploys to [Vercel](https://vercel.com) as two serverless functions, a cron and an interactivity handler, so there's no long-running server.
54 +You need a [Composio API key](https://dashboard.composio.dev/~/project/settings/api-keys?utm_source=docs&utm_medium=content&utm_campaign=examples-standup-slackbot), a Slack workspace you can install an app into, and Node with [tsx](https://nodejs.org). The finished bot deploys to [Vercel](https://vercel.com) as two serverless functions, a cron and an interactivity handler, so there's no long-running server.
55
56 <PackageInstall packages="@composio/core @composio/vercel ai dayjs" />
57
@@ -101,7 +101,7 @@ Rule of thumb: posting *as the bot* uses `slackbot`; doing something *as a perso
101
102 <Steps>
103 <Step>
104 -**Create an auth config and pick the `Slackbot` toolkit.** In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs), click **Create Auth Config** and search `slackbot`. Choose **Slackbot**, *not* `Slack`: `Slackbot` posts as the bot identity, while `Slack` acts as an individual user.
104 +**Create an auth config and pick the `Slackbot` toolkit.** In the [Composio dashboard](https://dashboard.composio.dev/~/project/auth-configs?utm_source=docs&utm_medium=content&utm_campaign=examples-standup-slackbot), click **Create Auth Config** and search `slackbot`. Choose **Slackbot**, *not* `Slack`: `Slackbot` posts as the bot identity, while `Slack` acts as an individual user.
105
106 <Figure src="/images/standup-slackbot/auth-config-slackbot.png" alt="Choosing the Slackbot toolkit, not Slack" caption="Pick Slackbot, not Slack" size="lg" />
107 </Step>
docs/eslint.config.mjs
+25
@@ -1,8 +1,33 @@
1 import { defineConfig, globalIgnores } from 'eslint/config';
2 import nextVitals from 'eslint-config-next/core-web-vitals';
3
4 +const utmMessage =
5 + 'Links to the Composio dashboard must carry utm_source=docs plus utm_medium and utm_campaign so sign-ups can be attributed to docs (MDX links are checked by tests/static/utm-links.test.ts).';
6 +
7 const eslintConfig = defineConfig([
8 ...nextVitals,
9 + {
10 + rules: {
11 + // Pre-existing violations across interactive components; warn until the
12 + // debt is burned down, then flip back to error.
13 + 'react-hooks/set-state-in-effect': 'warn',
14 + 'react-hooks/immutability': 'warn',
15 + 'react-hooks/purity': 'warn',
16 + 'no-restricted-syntax': [
17 + 'error',
18 + {
19 + selector:
20 + 'Literal[value=/dashboard\\.composio\\.dev/]:not([value=/utm_source=/])',
21 + message: utmMessage,
22 + },
23 + {
24 + selector:
25 + 'TemplateElement[value.raw=/dashboard\\.composio\\.dev/]:not([value.raw=/utm_source=/])',
26 + message: utmMessage,
27 + },
28 + ],
29 + },
30 + },
31 globalIgnores([
32 '.next/**',
33 'out/**',
docs/lib/llm-guardrails/direct-execution.ts
+1 -1
@@ -18,7 +18,7 @@ export const DIRECT_EXECUTION_GUARDRAILS = `
18
19 ### Authenticating Users
20
21 -Create an **Auth Config** on [dashboard.composio.dev](https://dashboard.composio.dev), then use the auth config ID to generate a hosted auth URL:
21 +Create an **Auth Config** on [dashboard.composio.dev](https://dashboard.composio.dev?utm_source=docs&utm_medium=llm-guardrails&utm_campaign=direct-execution), then use the auth config ID to generate a hosted auth URL:
22
23 \`\`\`python
24 from composio import Composio
docs/tests/static/utm-links.test.ts new
+81
@@ -0,0 +1,81 @@
1 +/**
2 + * UTM attribution tests.
3 + *
4 + * Every markdown link to dashboard.composio.dev in authored content must carry
5 + * utm_source, utm_medium, and utm_campaign so sign-ups can be attributed to
6 + * docs. Code fences and inline mentions are exempt; content/reference is
7 + * generated upstream and excluded. TS/TSX links are enforced by the
8 + * no-restricted-syntax rule in eslint.config.mjs.
9 + */
10 +import { describe, test, expect } from "bun:test";
11 +import { readdir, readFile } from "fs/promises";
12 +import { join, relative } from "path";
13 +
14 +const CONTENT_DIRS = ["docs", "examples", "changelog"].map((dir) =>
15 + join(import.meta.dir, "../../content", dir),
16 +);
17 +const CONTENT_ROOT = join(import.meta.dir, "../../content");
18 +
19 +const DASHBOARD_LINK_RE = /\]\((https:\/\/dashboard\.composio\.dev[^)\s]*)\)/g;
20 +const REQUIRED_PARAMS = ["utm_source=", "utm_medium=", "utm_campaign="];
21 +
22 +async function findMdxFiles(dir: string): Promise<string[]> {
23 + const results: string[] = [];
24 + let entries;
25 + try {
26 + entries = await readdir(dir, { withFileTypes: true });
27 + } catch {
28 + return results;
29 + }
30 +
31 + for (const entry of entries) {
32 + const fullPath = join(dir, entry.name);
33 + if (entry.isDirectory()) {
34 + results.push(...(await findMdxFiles(fullPath)));
35 + } else if (entry.name.endsWith(".mdx")) {
36 + results.push(fullPath);
37 + }
38 + }
39 + return results;
40 +}
41 +
42 +function findUntaggedLinks(content: string): { line: number; url: string }[] {
43 + const violations: { line: number; url: string }[] = [];
44 + let inFence = false;
45 + content.split("\n").forEach((line, index) => {
46 + if (/^\s*(```|~~~)/.test(line)) {
47 + inFence = !inFence;
48 + return;
49 + }
50 + if (inFence) return;
51 + for (const match of line.matchAll(DASHBOARD_LINK_RE)) {
52 + const url = match[1];
53 + if (!REQUIRED_PARAMS.every((param) => url.includes(param))) {
54 + violations.push({ line: index + 1, url });
55 + }
56 + }
57 + });
58 + return violations;
59 +}
60 +
61 +describe("Content - dashboard link UTM attribution", () => {
62 + test("all dashboard links carry utm params", async () => {
63 + const untagged: string[] = [];
64 +
65 + for (const dir of CONTENT_DIRS) {
66 + for (const file of await findMdxFiles(dir)) {
67 + const content = await readFile(file, "utf-8");
68 + for (const violation of findUntaggedLinks(content)) {
69 + untagged.push(
70 + `${relative(CONTENT_ROOT, file)}:${violation.line} ${violation.url}`,
71 + );
72 + }
73 + }
74 + }
75 +
76 + expect(
77 + untagged,
78 + `dashboard links missing utm_source=/utm_medium=/utm_campaign=:\n${untagged.join("\n")}`,
79 + ).toEqual([]);
80 + });
81 +});