Telegram Channel Setup

Telegram works well for direct chats, groups, and forum topics. To use group discussion as context, you must configure the bot correctly in BotFather.

Prerequisites

• Create a bot with BotFather and get bot token.
• Dawn API URL must be publicly resolvable from Telegram.
• Access to the target Telegram chat, group, or supergroup where you want Dawn to respond.

Setup steps

1. Open Channels → Add channel → Telegram in Dawn.
2. Paste the bot token and optional webhook secret, then save the bot. Dawn validates the token and configures the Telegram webhook immediately.
3. Add the Dawn bot to the target Telegram chat, group, or supergroup.
4. Send one message in that target chat.
5. Add @RawDataBot to the same chat and copy the returned chat.id.
6. Paste that chat ID into the Telegram binding form in Dawn.
7. If you want Dawn to follow normal group discussion, open BotFather and disable privacy mode for the bot.
8. Choose trigger mode and context mode in Dawn. For groups and topics, enable recent discussion only if the bot is allowed to see those messages.
9. Save the binding, attach it to the target agent profile, then send a real Telegram message and confirm it creates a conversation in Dawn.

Finding chat ID (user-friendly options)

• The recommended path is message the target chat, then use @RawDataBot in that same chat and copy chat.id.
• Group and supergroup IDs usually look like -1001234567890.
• Avoid relying on getUpdates after saving the bot in Dawn because Telegram polling conflicts with the active webhook Dawn configures during setup.
• If you absolutely must use getUpdates, temporarily remove or disable the webhook first, then restore it from Dawn afterward.

How context works in Telegram

• Dawn can use messages it receives from Telegram as later context in the same chat or topic.
• In groups, this depends on Telegram actually delivering those messages to the bot. That usually means privacy mode must be disabled.
• Telegram support is forward-ingested. Dawn does not fetch older Telegram history it never received earlier.

Private chats and identity linking

• Telegram private chats with Dawn are supported as private conversations, not only as shared workspace bindings.
• If you want Dawn to recognize the same person in Telegram and Dawn Web, start the link flow from that private chat with /link [email protected].
• Use /link status later if you need to confirm whether the current Telegram identity is already linked.

Validation checklist

• A message in the target Telegram chat produces a visible reply there and a matching conversation in Dawn.
• The saved chat ID still matches the intended private chat, group, or topic after refresh.
• If group context matters, a follow-up message confirms privacy mode and context mode are configured correctly.
• If private linking matters, /link status confirms the same Telegram identity after the link flow completes.

Troubleshooting

• Bad webhook: failed to resolve host: DNS for webhook host is not resolvable publicly.
• Token validation 404: invalid token or wrong bot instance.
• Not sure what chat ID to enter: add @RawDataBot to the target chat and copy chat.id.
• No conversations created: binding might be saved but not attached to an active agent.
• Dawn only responds when directly pinged in groups: privacy mode is probably still enabled in BotFather.
• Dawn replies but ignores the surrounding chat: verify privacy mode is disabled and context mode is not set to Dawn-only.
• Reusing same bot token in multiple workspaces: Telegram webhook is token-level, not workspace-level; last configured webhook wins.

Validate Telegram webhook state for this workspace bot binding.

List Telegram delivery errors in the last 24 hours.