Automate Gmail + Telegram
The inbox most operations still start in. 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.
Inbox Triage is a ready-made agent built around Gmail; point its last step at Telegram to finish this hand-off.
Automations teams run
These are not field mappings. An agent reads the Gmail side, works out what it means, and only then decides what — if anything — should happen in Telegram.
When a new email arrives in Gmail…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a label is applied in Gmail…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a thread goes unanswered in Gmail…
…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 send or draft a reply in Gmail — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can apply labels and archive in Gmail — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can extract attachments and fields in Gmail — with the reasoning recorded in the run’s receipt.
The Gmail and Telegram hand-off, in full
Gmail is reached through the gmail-api node and Telegram through the telegram-api node. Between them sits the agent, which is the part a field-mapping tool cannot do: it reads the item and decides whether the hand-off is warranted at all.
{
"id": "c4bdd6f9-624d-4c0f-ad96-59b6a5021346",
"name": "Gmail → Telegram",
"nodes": [
{
"id": "13b08b74-7b83-41a8-a598-8750bd8185ac",
"text": "Watch Gmail",
"x": 512,
"y": 144,
"isEditing": false,
"type": "gmail-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "A powerful tool to send, reply, read, organize, and manage attachments in Gmail.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "8418f0b8-53af-4fdb-ab0b-6f49c830208e",
"text": "Read it and decide",
"x": 512,
"y": 336,
"isEditing": false,
"type": "agnt-agent",
"icon": "connect",
"category": "action",
"isSelected": false,
"parameters": {
"instructions": "Read the Gmail item. Decide whether it warrants action in Telegram, and explain why."
},
"description": "Decides whether this Gmail item warrants anything in Telegram.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "4bf7fd7f-71cd-44e4-af3f-bf5d15692c6c",
"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": "e6126aa7-1398-478d-af2b-359808ad56b6",
"start": {
"id": "13b08b74-7b83-41a8-a598-8750bd8185ac",
"type": "output"
},
"end": {
"id": "8418f0b8-53af-4fdb-ab0b-6f49c830208e",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "7e225b34-5b24-47d0-aaa4-39b0512245dc",
"start": {
"id": "8418f0b8-53af-4fdb-ab0b-6f49c830208e",
"type": "output"
},
"end": {
"id": "4bf7fd7f-71cd-44e4-af3f-bf5d15692c6c",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Inbox Triage
Inbox Triage is a working agent built around Gmail. 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
Build it in AGNT
- Install AGNT — it runs on your own machine and needs no account to start.
- Authorise Telegram (an API key pasted into the vault) and Gmail (one OAuth sign-in). Nothing is stored anywhere but your disk.
- Describe the job in plain language, or paste the definition above; gmail-api does the reading and telegram-api the writing.
- Gate anything you would not want done unattended, then let it run and read the first receipt end to end.
Gmail and Telegram — common questions
Can I connect Gmail to Telegram without writing code?
No code is required. Add both connections in the vault (Gmail uses one OAuth sign-in, Telegram uses an API key pasted into the vault), then either install a marketplace workflow for this pair or drag the two nodes onto the canvas and put an agent between them.
How is this different from a field-mapping Gmail to Telegram automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Gmail 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 Gmail 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: Gmail, Telegram, and your chosen model provider — which can be a local one.
What does a Gmail and Telegram run leave behind?
Every run is recorded end to end — the Gmail items examined, the decision and its reasoning, the resulting Telegram write. That record is what makes it reasonable to let this run unattended, and what lets you widen its remit on evidence.
