Automate Google Sheets + Telegram
The database every team already has open. 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.
Report Assembler is a ready-made agent built around Google Sheets; point its last step at Telegram to finish this hand-off.
Automations teams run
Unlike field-mapping automation, the step in the middle is an agent: it can summarise, classify, judge and draft, not merely copy values from Google Sheets into Telegram.
When a row is added or edited in Google Sheets…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a sheet crosses a threshold in Google Sheets…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a schedule fires in Google Sheets…
…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 append and update rows in Google Sheets — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can read ranges for reporting in Google Sheets — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can maintain a rolling dashboard tab in Google Sheets — with the reasoning recorded in the run’s receipt.
The Google Sheets and Telegram hand-off, in full
The two ends are the google-sheets-api node and the telegram-api node. What makes this different from a zap is the middle node — it forms a view about the Google Sheets item before anything reaches Telegram.
{
"id": "a32ff01a-23ff-4c96-adad-34b84195c870",
"name": "Google Sheets → Telegram",
"nodes": [
{
"id": "c5b3b531-f73a-41ce-a94d-21e5634ea538",
"text": "Watch Google Sheets",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-sheets-new-row",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Listen for new rows added to a specified Google Sheet and trigger the workflow when a new row is detected.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "50c66ecc-f584-4aa8-a616-b6f4c5500a58",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Google Sheets item. Decide whether it warrants action in Telegram, and explain why."
},
"description": "Decides whether this Google Sheets item warrants anything in Telegram.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "90b7725f-afd1-408f-a59e-377c2292bb66",
"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": "a17c0d76-d4b6-43c4-a38a-f3842260d154",
"start": {
"id": "c5b3b531-f73a-41ce-a94d-21e5634ea538",
"type": "output"
},
"end": {
"id": "50c66ecc-f584-4aa8-a616-b6f4c5500a58",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "006e9093-274c-499b-a98b-d3b286897a5e",
"start": {
"id": "50c66ecc-f584-4aa8-a616-b6f4c5500a58",
"type": "output"
},
"end": {
"id": "90b7725f-afd1-408f-a59e-377c2292bb66",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Report Assembler
Report Assembler is a working agent built around Google Sheets. 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
Wiring Google Sheets to Telegram
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Sheets 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.
Google Sheets and Telegram — common questions
Can I connect Google Sheets to Telegram without writing code?
Yes. Google Sheets 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 row is added or edited, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Google Sheets to Telegram automation?
Mapping tools move data; this reasons about it. Rather than copying a field into Telegram, the agent can weigh what arrived from Google Sheets, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Sheets 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: Google Sheets, Telegram, and your chosen model provider — which can be a local one.
What does a Google Sheets and Telegram run leave behind?
A receipt: what was read in Google Sheets, 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.
