AI agents for Telegram
The fastest channel between your agents and your phone. AGNT connects to Telegram so agents can read what happens there, reason about it, and act — with a receipt for every run.
Telegram and AGNT, in brief
| What it does | Lets an AGNT agent read from and act in Telegram. |
|---|---|
| Connects with | An API key held in the local vault |
| AGNT node | telegram-api, receive-telegram-update |
| Runs when | A message arrives |
| Typical build time | Two minutes |
| Where data goes | Nowhere by default — AGNT runs on your machine and credentials never leave it. |
What you can automate
Reacts when…
- a message arrives
- a command is sent
- a schedule fires
Agents can…
- send messages and alerts
- reply to commands
- deliver files and reports
Teams use it for
- approve agent actions from anywhere
- get briefed on the move
- command your workflows by chat
The Telegram workflow, to configure
Design goal for Telegram: approve agent actions from anywhere; get briefed on the move; command your workflows by chat. The template below supplies configurable nodes, not the complete logic for those goals.
Use this Telegram setup template to arrange the schedule, input review and API operation. Configure the account-specific fields and add your own decision and approval controls before activation.
This is a schema-checked starting point, not an end-to-end tested automation. Replace every CONFIGURE_ value, choose the operations you intend, connect credentials and map source outputs into later inputs. An edge orders steps; it does not supply a condition, an approval gate or a field mapping. Add and test those controls explicitly before any write. Cloud APIs and model providers may receive data. Keep the workflow inactive until tested with fixtures.
{
"id": "e40ec9eb-4173-4ae5-ad13-52b4fa483fba",
"name": "Telegram — read, decide, act",
"nodes": [
{
"id": "1cdf9f02-cd5f-4ee8-aaa5-6b16f92d1838",
"text": "Watch Telegram for activity",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-telegram-update",
"icon": "clock",
"category": "trigger",
"isSelected": false,
"parameters": {
"botToken": "CONFIGURE_BOTTOKEN",
"apiBaseUrl": "CONFIGURE_APIBASEURL",
"updateTypes": "messages_and_buttons",
"chatFilter": "CONFIGURE_CHATFILTER",
"commandFilter": "CONFIGURE_COMMANDFILTER",
"ignoreBotMessages": false,
"dropPendingUpdatesOnStart": false,
"deleteWebhookOnStart": false,
"pollTimeoutSeconds": 1,
"pollIntervalMs": 1,
"limit": 1,
"includeRaw": false
},
"description": "Setup template for Receive Telegram Update. Listen for incoming Telegram bot messages, commands, channel posts, and inline keyboard callback button clicks using long polling. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "808eb2cb-36b7-49cb-a9cd-79003570b2ea",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "agnt",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Telegram item and decide whether it warrants action. Explain your reasoning.\nSource input: CONFIGURE_SOURCE_INPUT. Produce a reviewable draft only; do not take external actions."
},
"description": "Setup template for Agent Chat. Chat with an AI agent from your agent library. Select an agent and send messages to interact with it within your workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "38ca23d7-a396-4965-a3af-0034ae9f7a2e",
"text": "Configure destination in Telegram",
"x": 512,
"y": 528,
"isEditing": false,
"type": "telegram-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_ME",
"botToken": "CONFIGURE_BOTTOKEN",
"apiBaseUrl": "CONFIGURE_APIBASEURL",
"includeRaw": false
},
"description": "Setup template for Telegram API. Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "f2861be5-8a9f-4f9a-ae34-e35fdc6d95e8",
"start": {
"id": "1cdf9f02-cd5f-4ee8-aaa5-6b16f92d1838",
"type": "output"
},
"end": {
"id": "808eb2cb-36b7-49cb-a9cd-79003570b2ea",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "84841b45-16ef-44f8-aa76-ed17e0d3b848",
"start": {
"id": "808eb2cb-36b7-49cb-a9cd-79003570b2ea",
"type": "output"
},
"end": {
"id": "38ca23d7-a396-4965-a3af-0034ae9f7a2e",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}
Configure Receive Telegram Update
Listen for incoming Telegram bot messages, commands, channel posts, and inline keyboard callback button clicks using long polling.
- botToken — Optional fallback Telegram bot token from @BotFather. If omitted, AGNT uses the connected Telegram provider token from Settings → Connections. Current example:
CONFIGURE_BOTTOKEN. - apiBaseUrl — Optional Bot API base URL. Use https://api.telegram.org by default, or a local Bot API server URL. Current example:
CONFIGURE_APIBASEURL. - updateTypes — Which Telegram updates should trigger the workflow. messages_and_buttons listens for messages, edited messages, and callback button clicks. Current example:
messages_and_buttons. - chatFilter — Optional chat ID or @username to listen to. Leave empty for all chats. Multiple values can be comma-separated or newline-separated. Current example:
CONFIGURE_CHATFILTER. - commandFilter — Optional command name such as start or summarize, without the slash. Multiple values can be comma-separated or newline-separated. Current example:
CONFIGURE_COMMANDFILTER. - ignoreBotMessages — Ignore updates sent by bots when Telegram includes sender metadata. Current example:
false. - dropPendingUpdatesOnStart — Start from fresh updates instead of replaying old queued Telegram updates when the workflow starts. Current example:
false. - deleteWebhookOnStart — Delete any existing Telegram webhook before long polling. Enable this if Telegram reports a webhook conflict. Current example:
false. - pollTimeoutSeconds — Telegram long-poll timeout in seconds. Higher values reduce API churn. Range: 1-50. Current example:
1. - pollIntervalMs — Delay between long-poll requests in milliseconds. Range: 0-60000. Current example:
1. - limit — Maximum updates to fetch per poll. Telegram allows 1-100. Current example:
1. - includeRaw — Include the full raw Telegram update object in raw/response outputs. Current example:
false.
Configure Telegram API
Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method.
- action — Telegram operation to perform. Current example:
GET_ME. - botToken — Optional fallback Telegram bot token from @BotFather. If omitted, AGNT uses the connected Telegram provider token from Settings → Connections. Current example:
CONFIGURE_BOTTOKEN. - apiBaseUrl — Optional Bot API base URL. Use https://api.telegram.org by default, or a local Bot API server URL. Current example:
CONFIGURE_APIBASEURL. - includeRaw — Include the full raw Telegram API response when available. Current example:
false.
Run this against your own Telegram
Free to download, local by default — your Telegram credentials stay in a vault on your own disk.
The shortest path between agents and your phone
Telegram is the most practical channel for agent output that needs to reach you away from a desk: briefings, alerts and — most usefully — approval requests you can accept or reject from anywhere.
Command your workflows by chat
It works inbound too. A message or command can start a run, which makes a chat thread a workable control surface for the workflows you trigger most often.
Telegram node reference
Use Telegram Bot API from a single AGNT node. Choose an action to validate a bot, send messages/media, edit/delete messages, download files, or call any raw Bot API method.
What it can do: GET_ME SEND_MESSAGE SEND_MEDIA EDIT_MESSAGE DELETE_MESSAGE DOWNLOAD_FILE RAW_METHOD
Full Telegram API parameter reference
| Parameter | Type | What it does |
|---|---|---|
actionrequired |
string | Telegram operation to perform. GET_ME · SEND_MESSAGE · SEND_MEDIA · EDIT_MESSAGE · DELETE_MESSAGE · DOWNLOAD_FILE · RAW_METHOD |
botTokenrequired |
string | Optional fallback Telegram bot token from @BotFather. If omitted, AGNT uses the connected Telegram provider token from Settings → Connections. |
apiBaseUrlrequired |
string | Optional Bot API base URL. Use https://api.telegram.org by default, or a local Bot API server URL. |
includeRawrequired |
boolean | Include the full raw Telegram API response when available. |
chatId |
string | Target chat ID, user ID, group/supergroup ID, or channel username like @mychannel. only when action is SEND_MESSAGE or SEND_MEDIA or EDIT_MESSAGE or DELETE_MESSAGE |
text |
string | Message text for SEND_MESSAGE or new message text for EDIT_MESSAGE when editType=text. Telegram sendMessage supports up to 4096 characters after entity parsing. only when action is SEND_MESSAGE or EDIT_MESSAGE |
parseMode |
string | Optional parse mode for message text or media captions. none · HTML · MarkdownV2 · Markdown only when action is SEND_MESSAGE or SEND_MEDIA or EDIT_MESSAGE |
disableNotification |
boolean | Send silently without notification sound. only when action is SEND_MESSAGE or SEND_MEDIA |
protectContent |
boolean | Protect message/media content from forwarding/saving where supported. only when action is SEND_MESSAGE or SEND_MEDIA |
disableLinkPreview |
boolean | Disable link previews for SEND_MESSAGE or EDIT_MESSAGE text edits. only when action is SEND_MESSAGE or EDIT_MESSAGE |
messageThreadId |
number | Optional forum topic/thread ID for supergroups. only when action is SEND_MESSAGE or SEND_MEDIA |
replyToMessageId |
number | Optional message ID to reply to. only when action is SEND_MESSAGE or SEND_MEDIA |
23 further parameters are available on the node itself.
Every parameter above is read from the shipped telegram-api node, so it cannot drift from the product.
Connect Telegram in two minutes
- Download AGNT Community Core — free, local-first, no account needed to run.
- Connect by pasting an API key into AGNT’s vault — stored encrypted on your machine, never uploaded.
- Drop the Telegram node into a workflow or hand it to an agent — the first run produces a receipt you can read line by line.
Telegram + AGNT — common questions
Can I approve agent actions from Telegram?
Yes — approval gates can surface as messages, and the run resumes once you respond.
Can a message trigger a workflow?
Yes, including commands with arguments.
How is it connected?
With a bot token stored encrypted in the local vault.