Connectors Overview
Connect your agents to Slack, Microsoft Teams, Telegram, WhatsApp, SMS, and other chat platforms
Connectors bridge your deployed agents to external chat platforms, letting end-users interact with agents directly from their messaging apps.
Connectors vs Integrations — Integrations are API tools your agents use during execution (e.g., querying Jira or sending an email). Connectors are chat platform channels that route user messages to your agent and deliver responses back.
How Connectors Work
- Create a Connector — Add a connector to your agent revision in Agent Studio. Choose a provider, enter your credentials, and set an access policy.
- Configure Inbound Route — Set up optional filters for which messages the connector accepts (e.g., specific channels, users, or phone numbers).
- Configure Outbound Route — Set up where and how your agent sends responses. Enable use sender as receiver to reply in the same conversation, or specify an explicit target.
- Deploy — When you deploy the revision, some providers auto-configure their webhooks (Telegram, 360Dialog, Twilio). Others require you to manually paste the webhook URL into the provider's dashboard (Slack, Microsoft Teams).
- Interact — Users send messages in their chat app. The inbound route delivers the message to your agent, the agent processes it, and the outbound route sends the response back.
Connectors and the Agent Workflow
Connectors tie directly into your agent's workflow nodes:
- Entry Point — When a message arrives through a connector, the message content is passed as input to the agent's entry point node. The connector metadata (provider, user, conversation) is available as context.
- Exit Point — The output from the agent's exit point node is sent back to the user through the connector's outbound route.
This means the same agent workflow handles messages from any connector — Slack, Teams, WhatsApp, or SMS. The connector layer handles the platform-specific routing while your agent logic stays platform-agnostic.
Connector Configuration
Each connector card in Agent Studio includes these fields:
| Field | Description |
|---|---|
| Active | Toggle to enable or disable the connector |
| Connector Name | Identifier for this connector — lowercase with underscores only (e.g., production_slack_bot) |
| Provider | The chat platform to connect to |
| Provider Parameters | Credentials and settings specific to the selected provider (see each provider's page) |
| Onboarding | Toggle to enable the onboarding approval workflow. When disabled, all users can interact immediately (AllowAll policy) |
| Onboarding Message | Custom message shown to unapproved users (only visible when onboarding is enabled) |
| Test | Validate the configuration before deploying |
Connector Architecture
A connector is made up of three configuration layers:
Connector Parameters
Provider-specific credentials needed to authenticate with the chat platform:
| Provider | Required Parameters |
|---|---|
| Slack | Signing Secret, Bot Token (xoxb-) |
| Microsoft Teams | App ID, App Password (client secret) |
| Telegram | Bot Token |
| 360Dialog | API Key. Optional: API URL (defaults to waba.360dialog.io), Phone Number, Webhook Verify Token |
| Twilio | Account SID, Auth Token, From Phone Number |
Inbound Route
Controls which messages the connector accepts. All inbound parameters are optional filters — leave them empty to accept all messages.
| Provider | Filter Parameters |
|---|---|
| Slack | Team ID, Channel ID, User ID |
| Microsoft Teams | Channel ID, User AAD Object ID |
| Telegram | Chat ID, User ID, Reply To Message |
| 360Dialog | From Number |
| Twilio | From Number, To Number |
Outbound Route
Controls where responses are sent. All providers share a use sender as receiver toggle — when enabled, the agent replies to the same conversation that triggered the message. When disabled, you must provide a specific target:
| Provider | Target Parameters |
|---|---|
| Slack | Channel ID |
| Microsoft Teams | Conversation ID, Service URL |
| Telegram | Chat ID |
| 360Dialog | To Number |
| Twilio | To Number |
Deployment & Activation
When you deploy an agent revision, each configured connector goes through activation:
| Status | Meaning |
|---|---|
| Connected | Connector is live and receiving messages |
| Manual Setup | Connector deployed but requires manual webhook configuration in the provider's dashboard |
| Pending | Connector activation is in progress |
| Failed | Connector encountered an error during activation — check the error message for details |
Webhook Setup
Only Slack and Microsoft Teams require manual webhook configuration after deployment. The other providers auto-configure their webhooks during deployment:
| Provider | Webhook Setup |
|---|---|
| Slack | Manual — paste webhook URL into Event Subscriptions → Request URL in the Slack App Dashboard |
| Microsoft Teams | Manual — paste webhook URL into Configuration → Messaging Endpoint in the Azure Portal |
| Telegram | Automatic on deploy |
| 360Dialog | Automatic on deploy |
| Twilio | Automatic on deploy |
Supported Providers
| Provider | Description | Webhook |
|---|---|---|
| Slack | Messaging via Slack API — channels and DMs | Manual setup |
| Microsoft Teams | Messaging via Azure Bot Framework — chats and channels | Manual setup |
| Telegram | Group and direct messaging via Telegram Bot API | Auto-configured |
| 360Dialog (WhatsApp) | WhatsApp messaging via 360Dialog API | Auto-configured |
| Twilio | SMS and WhatsApp messaging via Twilio API | Auto-configured |
Next Steps
- Slack Connector — Set up your first connector
- Access Control — Configure who can interact with your agent
- Conversations — View and manage chat histories across all connectors