@devries-cameron20 / composio Mirror · read-only
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, 03:37 UTC

next
mdx 95 lines 5.03 KB
Raw
1 ---
2 title: Managed OAuth apps
3 description: Check whether Composio provides the OAuth app for a toolkit or you need to register your own
4 keywords: [managed OAuth, OAuth app, auth config, client credentials, toolkit list]
5 ---
6
7 Composio can provide the OAuth app that your users authorize when they connect a toolkit. You do not need to register an OAuth app or supply its client ID and client secret.
8
9 <Callout type="info">
10 Managed OAuth apps work in production. Because the OAuth app is shared, you may run into shared provider rate limits as your usage grows. For higher volume, we recommend your own OAuth app. See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) and [Avoid and recover from rate limits](/docs/poc-to-prod/avoid-rate-limits).
11 </Callout>
12
13 Your users still authorize their accounts through a [Connect Link](/docs/tools-direct/authenticating-tools#hosted-authentication-connect-link). Composio stores and refreshes the resulting tokens. See [Authentication](/docs/authentication) for the full connection flow.
14
15 This catalog identifies who provides the OAuth app, not which execution framework you must use. For per-user OAuth with application-owned tools, follow [Managed authentication for your own tools](/docs/authentication/managed-auth-for-custom-tools). Your code can call provider endpoints through the authenticated proxy without predefined tools, MCP, or an LLM.
16
17 This page covers only toolkits that support OAuth. It does not list toolkits that use only API keys, bearer tokens, Basic auth, or no authentication.
18
19 ## When Composio provides the OAuth app
20
21 For a toolkit with managed OAuth, Composio maintains the OAuth app registration, client credentials, and redirect URI. Your users sign in to the provider and approve the requested permissions.
22
23 ## When you provide the OAuth app
24
25 Register your own OAuth app when a toolkit does not have managed OAuth. Then create a custom auth config with the app's client ID and client secret.
26
27 You can also provide your own OAuth app to show your app name on the consent screen, request custom scopes, or use a separate rate-limit quota.
28
29 See [Managed vs custom auth](/docs/authentication/custom-app-vs-managed-app) for setup steps and trade-offs.
30
31 ## Slack managed apps
32
33 Slack is the one toolkit with two Composio managed apps. You don't register anything with Slack for either one. Slack has approved Standard but not Legacy. The two apps get different Slack rate limits and receive different triggers.
34
35 | App | Approved by Slack | Slack rate limits | Triggers |
36 |---|---|---|---|
37 | Standard | Yes | Higher | Every Slack trigger except the four below |
38 | Legacy | No | Lower | Every Slack trigger |
39
40 Slack gives approved apps higher limits on its API methods than unapproved ones. See [Slack's rate limits](https://docs.slack.dev/apis/web-api/rate-limits) for the numbers.
41
42 Standard does not receive these message triggers:
43
44 - `SLACK_CHANNEL_MESSAGE_RECEIVED`
45 - `SLACK_DIRECT_MESSAGE_RECEIVED`
46 - `SLACK_RECEIVE_BOT_MESSAGE`
47 - `SLACK_RECEIVE_MESSAGE`
48
49 Use Standard unless your product reacts to new Slack messages. Pick Legacy when you need one of these four triggers and your traffic fits under the lower limits.
50
51 Use your own Slack app when you need message triggers and your app name on the Slack consent screen, or scopes that neither managed app requests. Follow the [Slack OAuth guide](https://composio.dev/auth/slack), then [create a custom auth config](/docs/authentication/custom-app-vs-managed-app#create-a-custom-auth-config).
52
53 ## Find an OAuth toolkit
54
55 Search for a toolkit to check whether Composio provides a managed OAuth app.
56
57 - **Composio-managed OAuth available** means that you can use Composio's OAuth app.
58 - **Bring your own OAuth app** means that you must register an OAuth app with the provider and create a custom auth config.
59
60 Some toolkits support more than one authentication method. A toolkit appears under **Composio-managed OAuth available** when Composio manages at least one OAuth method. Open the toolkit page to check each method.
61
62 <ManagedAuthList />
63
64 ## Check with the API
65
66 Fetch the toolkit and read its managed auth schemes (`composio_managed_auth_schemes` in the API and Python, `composioManagedAuthSchemes` in TypeScript):
67
68 <Tabs groupId="language" items={['Python', 'TypeScript', 'API']} persist>
69 <Tab value="Python">
70 ```python
71 from composio import Composio
72
73 composio = Composio()
74 toolkit = composio.toolkits.get("gmail")
75 print(toolkit.composio_managed_auth_schemes)
76 ```
77 </Tab>
78 <Tab value="TypeScript">
79 ```typescript
80 import { Composio } from '@composio/core';
81
82 const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY });
83 const toolkit = await composio.toolkits.get('gmail');
84 console.log(toolkit.composioManagedAuthSchemes);
85 ```
86 </Tab>
87 <Tab value="API">
88 ```bash
89 curl -X GET https://backend.composio.dev/api/v3.1/toolkits/gmail \
90 -H "x-api-key: $COMPOSIO_API_KEY"
91 ```
92 </Tab>
93 </Tabs>
94
95 If `composio_managed_auth_schemes` contains the toolkit's OAuth method, Composio provides the OAuth app. If the field does not contain that method, register your own OAuth app and supply its client ID and client secret.