Custom integrations
Beyond channels and the Composio app library, TeamMate has its own integration layer for connecting apps directly with their native credentials. Use it when an app isn’t in the Composio library, or when you’d rather authenticate with your own keys.
When to use which
| Approach | Use it for |
|---|---|
| Channels | Letting people reach an agent (Slack, Teams, WhatsApp, voice, email). See Channels overview. |
| Composio app library | The fastest way to give an agent tools in popular apps. See Composio app library. |
| MCP servers | Workspace-wide tools from any MCP server. See MCP servers (workspace-wide). |
| Custom integrations | Connecting an app with its native credentials, or one not covered above. |
Authentication methods
The custom integration form supports the connection types most apps use:
| Method | What you provide |
|---|---|
| OAuth 2.0 | Authorize through the provider’s consent screen. |
| API key | A single API key or token. |
| Basic auth | A username and password. |
| Key pair | A public/private key pair. |
Connecting an app
- Open the integration formFrom the agent builder’s Integrations tab (or the workspace integrations area), pick the app to connect.
- Choose the auth methodSelect OAuth, API key, basic auth, or key pair, depending on what the app supports.
- Enter credentialsFill in the fields for that method.
- Test the connectionUse Test connection to confirm the credentials work before saving.
- SaveSave the integration so the agent can use the app’s actions.
Inbound webhooks
If you’re handling incoming events (a provider calling TeamMate when something happens), that’s the webhook side of integrations. See Webhooks overview for the per-agent callback URLs and how each provider verifies them.