Automate Asana + Telegram
Team tasks, due dates and the follow-through between them. 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.
Meeting Follow-Through is a ready-made agent built around Asana; point its last step at Telegram to finish this hand-off.
Automations teams run
Each of these runs with a reasoning step between the two tools, so what reaches Telegram is a decision about the Asana event rather than a transcription of it.
When a task is created or completed in Asana…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a due date nears in Asana…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a project updates in Asana…
…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 create tasks with owners in Asana — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can update status and comments in Asana — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can roll up project summaries in Asana — with the reasoning recorded in the run’s receipt.
Copy this Asana → Telegram workflow
Start with a custom-api call to app.asana.com and the telegram-api node. Configure the Asana source payload, the agent input, and the Telegram operation. The sequential template does not implement conditional writes or approval by itself.
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": "6c824bbc-8a0d-4bee-aa3a-3b6e783bbf54",
"name": "Asana → Telegram",
"nodes": [
{
"id": "2e58ca2f-9261-41c6-aef8-806fd2a79d00",
"text": "Run on a schedule",
"x": 512,
"y": 144,
"isEditing": false,
"type": "trigger-timer",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"fireOnStart": "No",
"scheduleType": "Interval",
"schedule": "Every 15 Minutes"
},
"description": "Setup template for Timer Trigger. This trigger node fires the workflow at specified intervals or at a specific time. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "9989e7d8-893d-4563-a634-9821d40a24d2",
"text": "Review source and draft",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"agentId": "CONFIGURE_AGENTID",
"message": "Read the Asana item. Decide whether it warrants action in Telegram, and explain why.\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": "5f6655f2-3ec0-431c-af48-119abcaedbb8",
"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": "f33efcfb-6b7c-475f-a02d-4d6e1ce7e04e",
"start": {
"id": "2e58ca2f-9261-41c6-aef8-806fd2a79d00",
"type": "output"
},
"end": {
"id": "9989e7d8-893d-4563-a634-9821d40a24d2",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "8986f8aa-6f98-4334-ad2a-d6caaf98b730",
"start": {
"id": "9989e7d8-893d-4563-a634-9821d40a24d2",
"type": "output"
},
"end": {
"id": "5f6655f2-3ec0-431c-af48-119abcaedbb8",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": 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.
Install Meeting Follow-Through
Meeting Follow-Through is a working agent built around Asana. 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 — Asana takes one OAuth sign-in, Telegram takes an API key pasted into the vault.
- Configure the 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.
Asana and Telegram — common questions
Can I connect Asana to Telegram without writing code?
Yes. Asana 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 task is created or completed, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Asana to Telegram automation?
The difference shows up on the messy inputs. A rule chain needs every case enumerated in advance; an agent handles meeting decisions become assigned tasks the way a colleague would — reading the Asana context, judging it, then writing to Telegram with the reasoning recorded.
Does my Asana and Telegram data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Asana or Telegram tokens. The runtime talks directly to both services. Choose a local model and the content of what it reads never leaves the machine at all.
What does a Asana and Telegram run leave behind?
A receipt: what was read in Asana, which tools ran with which arguments, what the agent concluded, and what it wrote to Telegram. Anything consequential can sit behind an approval gate so a person signs off before it happens.
