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, 23:30 UTC
docs: refine bearer token wording for coherence
Use natural language instead of bold "Important" callout. Frame the feature around importing existing OAuth connections into Composio. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
dhawal committed
Apr 11, 2026 at 06:00 UTC
55bda6e548f4d7a6367a5b4fa3b5ad15be901e75
1 file changed
+2
-2
docs/content/docs/importing-existing-connections.mdx
+2
-2
@@ -74,9 +74,9 @@ console.log('Connected:', connection.id);
74
75
## Bearer tokens
76
77
-If you manage your own OAuth flow and already have an access token for a service, you can pass it directly to Composio as a bearer token instead of setting up OAuth through Composio. This works with **all toolkits that support OAuth2 or S2S auth** — Gmail, GitHub, Slack, Google Docs, and more. Any additional parameters the toolkit supports (e.g., `subdomain`, `base_url`) work the same way.
77
+If you manage your own OAuth flow and already have an access token for a service, you can import it into Composio as a bearer token. This lets you bring existing OAuth connections into Composio without re-authenticating your users. It works with **all toolkits that support OAuth2 or S2S auth** — Gmail, GitHub, Slack, Google Docs, and more. Any additional parameters the toolkit supports (e.g., `subdomain`, `base_url`) work the same way.
78
79
-**Important:** When you import a bearer token this way, Composio will **not** handle OAuth token refresh for you. You are responsible for refreshing the token on your end and updating it in Composio via the [PATCH method](#updating-credentials) whenever it changes.
79
+Since you're providing your own token, Composio won't handle OAuth refresh — you're responsible for refreshing the token on your end and pushing the updated value to Composio via the [PATCH method](#updating-credentials) whenever it changes.
80
81
After [creating an auth config](/docs/auth-configuration/programmatic-auth-configs) with `authScheme: "BEARER_TOKEN"`, use the snippet below to create a connected account:
82