Automate Telegram + Trello
The fastest channel between your agents and your phone. Boards and cards — simple enough to automate deeply. Put an agent between them and the hand-off stops being manual: it reads, decides, acts, and shows its work.
Automations teams run
These are not field mappings. An agent reads the Telegram side, works out what it means, and only then decides what — if anything — should happen in Trello.
When a message arrives in Telegram…
…an agent can create and move cards in Trello — after reading the context and deciding it should.
When a command is sent in Telegram…
…an agent can update checklists and labels in Trello — after reading the context and deciding it should.
When a schedule fires in Telegram…
…an agent can summarise a board in Trello — after reading the context and deciding it should.
When a card is created or moved in Trello…
…an agent can send messages and alerts in Telegram — with the reasoning recorded in the run’s receipt.
When a due date approaches in Trello…
…an agent can reply to commands in Telegram — with the reasoning recorded in the run’s receipt.
When a checklist completes in Trello…
…an agent can deliver files and reports in Telegram — with the reasoning recorded in the run’s receipt.
Copy this Telegram → Trello workflow
Start with the telegram-api node and a custom-api call to api.trello.com. Configure the Telegram source payload, the agent input, and the Trello 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": "c8981c2b-d605-4785-af41-efdaeb147cd6",
"name": "Telegram → Trello",
"nodes": [
{
"id": "0313bcf3-a9a6-4563-a0de-3734e8ef3a2e",
"text": "Watch Telegram",
"x": 512,
"y": 144,
"isEditing": false,
"type": "receive-telegram-update",
"icon": "connect",
"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": "75e853d7-51f4-4041-a42f-30927e793b02",
"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 Telegram item. Decide whether it warrants action in Trello, 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": "efaf1287-341f-4de6-a51d-24558ea30b18",
"text": "Call Trello",
"x": 512,
"y": 528,
"isEditing": false,
"type": "custom-api",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"url": "https://api.trello.com/1/cards?key={key}&token={token}",
"method": "GET",
"authType": "None",
"query": "",
"headers": "{}"
},
"description": "Setup template for Custom API Request. This action node makes a custom API request to any endpoint with configurable method, headers, and authentication. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
}
],
"edges": [
{
"id": "19d8b007-eb48-4383-a291-1fc8cce584a6",
"start": {
"id": "0313bcf3-a9a6-4563-a0de-3734e8ef3a2e",
"type": "output"
},
"end": {
"id": "75e853d7-51f4-4041-a42f-30927e793b02",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b8b555c8-654a-494c-aa49-419af9b81798",
"start": {
"id": "75e853d7-51f4-4041-a42f-30927e793b02",
"type": "output"
},
"end": {
"id": "efaf1287-341f-4de6-a51d-24558ea30b18",
"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 Custom API Request
This action node makes a custom API request to any endpoint with configurable method, headers, and authentication.
- url — The URL of the API endpoint Current example:
https://api.trello.com/1/cards?key={key}&token={token}. - method — The HTTP method for the request Current example:
GET. - authType — The type of authentication Current example:
None. - query — Query parameters for the request (e.g., 'key1=value1&key2=value2') Current example:
. - headers — Optional headers for the request. e.g., {"Content-Type": "application/json"} Current example:
{}.
Build this hand-off
Free and local. It asks for Telegram and Trello, and nothing else.
Wiring Telegram to Trello
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Telegram takes an API key pasted into the vault, Trello 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 Trello.
Telegram and Trello — common questions
Can I connect Telegram to Trello without writing code?
You can build it entirely from the canvas. Authorise Telegram with an API key pasted into the vault, Trello with an API key pasted into the vault, then tell the agent what approve agent actions from anywhere should look like once Trello is involved. Code is an option for the unusual cases, never a requirement for the common ones.
How is this different from a field-mapping Telegram to Trello automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Trello, the agent can weigh what arrived from Telegram, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Telegram and Trello data leave my machine?
Not to us. AGNT runs locally and both sets of credentials are encrypted on your own disk. Outbound traffic goes only to Telegram, Trello and whichever model you chose — and pointing that at Ollama or LM Studio keeps everything on your hardware.
What does a Telegram and Trello run leave behind?
Every run is recorded end to end — the Telegram items examined, the decision and its reasoning, the resulting Trello write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
