Automate Slack + Telegram
Team chat where operations actually surface. The fastest channel between your agents and your phone. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Support First Responder is a ready-made agent built around Slack; point its last step at Telegram to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Slack side, works out what it means, and only then decides what — if anything — should happen in Telegram.
When a message hits a channel in Slack…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a keyword or mention fires in Slack…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a reaction is added in Slack…
…an agent can deliver files and reports in Telegram — after reading the context and deciding it should.
When a message arrives in Telegram…
…an agent can post a rich channel message in Slack — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can DM a teammate in Slack — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can open a thread with findings in Slack — with the reasoning recorded in the run’s receipt.
Slack to Telegram, in three nodes
The two ends are the slack-api node and the telegram-api node. What makes this different from a zap is the middle node — it forms a view about the Slack item before anything reaches Telegram.
{
"id": "86be49b0-1981-4ce3-adb3-46515a0cb3ce",
"name": "Slack → Telegram",
"nodes": [
{
"id": "714f7bf1-6a74-466c-a3eb-5531001cb860",
"text": "Watch Slack",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-slack-message",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for incoming Slack messages in a specified channel and trigger the workflow when a new message is received.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "efad72e5-c55a-41ed-a83e-23defea312d6",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Slack item. Decide whether it warrants action in Telegram, and explain why."
},
"description": "Decides whether this Slack item warrants anything in Telegram.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "4ed94bde-a542-4ada-a41b-e57861ae8ef0",
"text": "Act in Telegram",
"x": 512,
"y": 528,
"isEditing": false,
"type": "telegram-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"action": "GET_ME"
},
"description": "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.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "9c67b403-443d-4ac7-a1d0-67bcbb049b96",
"start": {
"id": "714f7bf1-6a74-466c-a3eb-5531001cb860",
"type": "output"
},
"end": {
"id": "efad72e5-c55a-41ed-a83e-23defea312d6",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "2c9c2e1d-32fd-4fa8-a258-461ddad5ffa4",
"start": {
"id": "efad72e5-c55a-41ed-a83e-23defea312d6",
"type": "output"
},
"end": {
"id": "4ed94bde-a542-4ada-a41b-e57861ae8ef0",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Support First Responder
Support First Responder is a working agent built around Slack. Install it, point its last step at Telegram, and you have this hand-off without building it from an empty canvas.
Runs on your own machine · See what it does
What building this looks like
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Slack takes one OAuth sign-in, Telegram takes an API key pasted into the vault.
- Build the three nodes above, or start from a marketplace workflow and edit it. The agent in the middle is the part worth spending time on.
- Run it once with an approval gate in place. The receipt tells you what it read, what it concluded, and what it changed in Telegram.
Slack and Telegram — common questions
Can I connect Slack to Telegram without writing code?
Yes. Slack connects with one OAuth sign-in and Telegram with an API key pasted into the vault, both from the local credential vault. You then describe the job in plain language — “when a message hits a channel, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Slack to Telegram automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Slack item in full and decides — whether it matters, how to summarise it, and what belongs in Telegram. Deciding to do nothing is a valid outcome, which no mapping can express.
Does my Slack and Telegram data leave my machine?
Your credentials stay in a vault on your own disk rather than in someone else’s cloud. The only calls made are the ones the workflow needs: Slack, Telegram, and your chosen model provider — which can be a local one.
What does a Slack and Telegram run leave behind?
You get an auditable trail rather than a success flag. It shows the Slack context the agent worked from, the judgment it made about approve agent actions from anywhere, and the exact change applied in Telegram, with approvals attached where you required them.
