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: add callback URL FAQ, rename sections for clarity
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 11, 2026 at 15:41 UTC
effcbf163b9ad911419eeea24b03c1b46af34320
3 files changed
+9
-3
docs/content/docs/authenticating-users/manually-authenticating.mdx
+1
-1
@@ -50,7 +50,7 @@ Redirect the user to the redirect URL. After they authenticate, they'll return t
50
If the user closes the Connect Link without completing auth, the connection remains in `INITIATED` status until it expires.
51
</Callout>
52
53
-## Callback URL
53
+## Redirecting users after authentication
54
55
Pass a `callbackUrl` to control where users land after authenticating. You can include query parameters to carry context through the flow, for example to identify which user or session triggered the connection.
56
docs/content/docs/common-faq.mdx
+6
@@ -90,6 +90,12 @@ Every tool execution is logged in the [Composio dashboard](https://platform.comp
90
See [Troubleshooting tools](/docs/troubleshooting/tools) for how to use logs to debug failed executions.
91
</Accordion>
92
93
+<Accordion title="How do I redirect users back to my app after they connect?">
94
+Pass a `callbackUrl` when calling `link()`, `initiate()`, or `session.authorize()`. After authentication, Composio redirects the user to that URL with `status=success` or `status=failed` and the `connected_account_id` appended as query parameters.
95
+
96
+You can include your own query parameters in the callback URL (e.g., `?user_id=user_123&source=onboarding`) to carry context through the flow. Composio preserves them. See [sessions](/docs/authenticating-users/manually-authenticating#redirecting-users-after-authentication) or [direct tool setup](/docs/tools-direct/authenticating-tools#redirecting-users-after-authentication).
97
+</Accordion>
98
+
99
<Accordion title="Can Composio be self-hosted?">
100
Yes, Composio supports self-hosting on the Enterprise plan. See [pricing](https://composio.dev/pricing) for details or [talk to us](https://calendly.com/composiohq/enterprise).
101
</Accordion>
docs/content/docs/tools-direct/authenticating-tools.mdx
+2
-2
@@ -162,7 +162,7 @@ These settings will apply to all authentication flows using Connect Link, provid
162
For complete white-labeling including OAuth consent screens (removing Composio's domain), see [Custom Auth Configs - White-labeling](/docs/auth-configuration/custom-auth-configs#white-labeling-the-oauth-consent-screen).
163
</Callout>
164
165
-#### Passing query parameters in the callback URL
165
+#### Redirecting users after authentication
166
167
You can include custom query parameters in your callback URL to carry context through the auth flow, such as identifying which user or session triggered the connection. Composio preserves your parameters and appends its own after authentication completes:
168
@@ -249,7 +249,7 @@ console.log(`Connection established: ${connectedAccount.id}`);
249
</Tabs>
250
251
<Callout type="info">
252
-Your callback URL can include query parameters to carry context through the auth flow. Note that `initiate()` uses camelCase parameters (`connectedAccountId`, `appName`) in the redirect, unlike `link()` which uses snake_case (`connected_account_id`). See [Passing query parameters in the callback URL](#passing-query-parameters-in-the-callback-url) for details.
252
+Your callback URL can include query parameters to carry context through the auth flow. Note that `initiate()` uses camelCase parameters (`connectedAccountId`, `appName`) in the redirect, unlike `link()` which uses snake_case (`connected_account_id`). See [Redirecting users after authentication](#redirecting-users-after-authentication) for details.
253
</Callout>
254
255
#### Services with Additional Parameters