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, 06:00 UTC
| 1 | ## Create an auth config from the selected Platform project |
| 2 | |
| 3 | Open **Platform → Auth Configs → Create Auth Config**, choose the toolkit and |
| 4 | supported authentication method, then select managed authentication when it is |
| 5 | available or enter customer-owned credentials. For custom OAuth, register the |
| 6 | exact callback URI shown by the current dashboard in the provider app; do not |
| 7 | copy a callback URI from an old example. |
| 8 | |
| 9 | Auth configs belong to one Platform project. If a config or connection is |
| 10 | missing, verify the selected organization and project before recreating it. |
| 11 | |
| 12 | ## Connect Account on an auth config is a Playground test connection |
| 13 | |
| 14 | Open an auth config and select **Connect Account** to authenticate the |
| 15 | project's Playground user for testing. This control does not ask for an |
| 16 | application user ID. To connect an actual application user, create a hosted |
| 17 | connection link through the SDK or API with that application's stable |
| 18 | `user_id` and the intended auth config. |
| 19 | |
| 20 | ## Manage Config changes future authentication behavior |
| 21 | |
| 22 | Use **Manage Config** to inspect the enabled state, credentials, and available |
| 23 | scope or execution settings for that config type. Changing credentials or |
| 24 | scopes can require users to create a fresh connection before the change is |
| 25 | reflected in their provider grant. Review dependent connections, sessions, and |
| 26 | triggers before disabling or deleting a config. |