Skip to Content
Docs are being rebuilt — start at Introduction → How it works.
IntegrationsCustom integrations

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

ApproachUse it for
ChannelsLetting people reach an agent (Slack, Teams, WhatsApp, voice, email). See Channels overview.
Composio app libraryThe fastest way to give an agent tools in popular apps. See Composio app library.
MCP serversWorkspace-wide tools from any MCP server. See MCP servers (workspace-wide).
Custom integrationsConnecting an app with its native credentials, or one not covered above.

Authentication methods

The custom integration form supports the connection types most apps use:

MethodWhat you provide
OAuth 2.0Authorize through the provider’s consent screen.
API keyA single API key or token.
Basic authA username and password.
Key pairA public/private key pair.

Connecting an app

  1. Open the integration form
    From the agent builder’s Integrations tab (or the workspace integrations area), pick the app to connect.
  2. Choose the auth method
    Select OAuth, API key, basic auth, or key pair, depending on what the app supports.
  3. Enter credentials
    Fill in the fields for that method.
  4. Test the connection
    Use Test connection to confirm the credentials work before saving.
  5. Save
    Save 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.