Telegram
Send and receive Telegram messages — trigger workflows from incoming bot messages
Telegram is a fast, privacy-focused messaging app. CipherSense Agents integrates via the Telegram Bot API for bidirectional messaging: send notifications to individuals, groups, or channels, and trigger workflows automatically when your bot receives a message. Webhook support means your bot can power interactive AI assistants, command processors, and real-time alert systems without polling.
Setup
Create a Telegram bot with BotFather
Create a Telegram bot with BotFather
Open Telegram and search for @BotFather. Send /newbot, choose a name and username for your bot, and copy the API token provided.
BotFather on TelegramGet your Chat ID (for sending messages)
Get your Chat ID (for sending messages)
Send a message to your bot, then open this URL in a browser (replace TOKEN with your bot token): https://api.telegram.org/bot<TOKEN>/getUpdates Find the chat.id field in the JSON response. For groups: add the bot to the group first, then send a message, then check the updates.
Add the integration in CipherSense Agents
Add the integration in CipherSense Agents
Go to Project > Integrations > Add Integration > Telegram. Enter your Bot Token and (optionally) a default Chat ID. Click Save & Test.
Enable webhook to receive messages (optional)
Enable webhook to receive messages (optional)
To trigger workflows from incoming bot messages, enable the webhook in one of two places: • Integration settings: Project > Integrations > Edit Telegram > Enable button under Webhook. • Workflow canvas: open the Telegram node settings panel and click Enable under Webhook. Webhook registration requires your app to be deployed at an HTTPS URL. Once enabled, any message sent to your bot will trigger active workflows that start with a Telegram Receive Message node.
Use the Receive Message node as a workflow trigger
Use the Receive Message node as a workflow trigger
In the workflow canvas, add a Telegram integration node and set its mode to Trigger – Receive Message. This node captures the incoming message and exposes its data (chat ID, text, sender info, etc.) to downstream nodes via output variables such as {{NodeName.chatId}}, {{NodeName.text}}, and {{NodeName.from.username}}.
Connection Fields
Fields required when adding this integration in your Project › Integrations.
| Field | Required | Description |
|---|---|---|
| Bot Token | Required | Your Telegram Bot API token from @BotFather. |
| Default Chat ID (Optional) | Optional | Default chat, group, or channel ID to send messages to. Can be overridden per workflow node. Supergroups use a negative number prefixed with -100. |
Common Use Cases
Common Errors
Known errors and how to resolve them.
Telegram webhooks require an HTTPS URLTest & ExecutionWhy this happens
How to fix
Webhook registration only works when your app is deployed behind HTTPS. For local development, use a tunnel such as ngrok to expose localhost over HTTPS, then set NEXT_PUBLIC_APP_URL to the ngrok URL before enabling the webhook.
Bot Token is not configured on this integrationTest & ExecutionWhy this happens
How to fix
Open Project > Integrations, edit the Telegram integration, and make sure a valid Bot Token is saved.
No Chat ID providedTest & ExecutionWhy this happens
How to fix
Set a Default Chat ID on the integration, or supply a chatId input on the Send Message node in the workflow canvas.
Ready to connect Telegram?
Add this integration from your project dashboard and wire it into a workflow.