- Composio managed apps: Composio registers and maintains OAuth apps for popular toolkits such as GitHub, Gmail, and Slack. You do not need to register your own OAuth app.
- Custom auth configs: You provide your own OAuth app, API key, bearer token, or other credentials and tell Composio to use them for a toolkit.
When to use Composio managed apps
Managed apps are the default when they are available. Keep them in production when their consent branding, scopes, and shared provider quotas fit your product. Use them when:- You’re building and iterating. No OAuth app registration, no credentials to manage. Create a session and start testing immediately.
- Default scopes cover your needs. Composio requests sensible defaults for each toolkit.
- Composio branding on consent screens fits your product. Users see Composio’s app name during OAuth. You can still white-label the Connect Link page with your logo and app title without needing your own OAuth app.
When to use a custom auth config
Bring your own credentials when any of these apply:- You need your app name on OAuth consent screens. Use your own OAuth app when your product’s branding requirements call for it.
- You need custom scopes. Composio’s default scopes may not include everything you need (e.g., write access to a specific Google API).
- You’re hitting rate limits. Managed apps share quota across all Composio users. Your own app gets a dedicated quota.
- You need faster polling triggers. Managed auth enforces a 2-minute minimum polling interval; your own app can use shorter polling intervals where supported.
- You’re connecting to a custom instance. Self-hosted or regional variants (e.g., a private Salesforce subdomain) need their own OAuth app.
- Enterprise customers require your branding end-to-end.
Create a custom auth config
To check whether Composio provides the OAuth app for a toolkit, see Managed OAuth apps. You can still create a custom auth config for branding, scopes, rate limits, polling intervals, or custom instances. The steps below use the dashboard. To create auth configs in code instead, for example one per customer, see Programmatic auth configs.1
Create the auth config in the Composio dashboard
In the Composio dashboard:
- Click Create Auth Config
- Select the toolkit
- Choose the auth scheme (OAuth2, API Key, Bearer Token, etc.)
- Follow the dashboard instructions for the required credential fields
2
Collect credentials from the provider
For OAuth toolkits, register an app in the provider’s developer portal and add the redirect URI from the dashboard. Then copy the Client ID and Client Secret back into Composio.For API key, bearer token, basic auth, or other auth schemes, collect the credential fields the toolkit requires and enter them in the dashboard.Step-by-step OAuth guides: Google | GitHub | Slack | HubSpot | All toolkits
3
Save and copy the auth config ID
After you enter the required credentials, click Create and copy the auth config ID (for example,
ac_1234abcd).4
Pass the auth config ID in your session
Creating the auth config isn’t enough on its own. A session uses your config only when you pass its ID to
authConfigs, keyed by toolkit. Toolkits you leave out keep using Composio managed auth.- Python
- TypeScript
- API
Mixing per toolkit
You don’t have to pick one approach for all toolkits. Use your own credentials for toolkits where users see consent screens (GitHub, Google, Slack) and Composio managed auth for the rest. Each toolkit gets its own auth config independently.- Python
- TypeScript
- API