Skip to main content
Bridge a Telegram bot or a Slack app to an agent: a message to the bot runs an agent turn and the answer comes back in the same chat. The bridge is identical to the WhatsApp guide — only the channel plugin, its env group, and the webhook wiring differ. Every route still runs its turn as a least-privilege execution_key — mint and bind one exactly as in WhatsApp to an agent before creating the route.

​
Pick a channel and wire it

The channel package and its env group, the webhook wiring, and the our_identity format live on the plugin page:

channel-telegram

CHANNEL_TELEGRAM_*, the automatic setWebhook registration, and the bot’s numeric id as our_identity.

channel-slack

CHANNEL_SLACK_*, the Events-API Request URL to set by hand, and the required CHANNEL_SLACK_BOT_USER_ID as our_identity.
Once the channel is configured, create the route binding the bot to the agent:

​
Test it and add more

Message the bot and watch the agent reply in the same chat. Read a record with tai conversations get-message <route> <message_id>; list failed deliveries with tai conversations failed. To hand a thread to a human — or let the agent do so — see control mode and operator messages. More bots or workspaces are more rows — one route per (channel, our_identity) pair.

​
See also