Automate Google Drive + Telegram
Where the documents live — and pile up. 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.
Document Extractor is a ready-made agent built around Google Drive; 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 Google Drive event rather than a transcription of it.
When a file lands in a folder in Google Drive…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a doc is updated in Google Drive…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a file is shared in Google Drive…
…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 read and summarise documents in Google Drive — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can file outputs into folders in Google Drive — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can export and convert formats in Google Drive — with the reasoning recorded in the run’s receipt.
Google Drive to Telegram, in three nodes
The two ends are the google-drive-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 Drive item before anything reaches Telegram.
{
"id": "7562e14d-f9c8-4117-a2a7-406efca33eba",
"name": "Google Drive → Telegram",
"nodes": [
{
"id": "450f263b-aa7e-4749-a450-33ce1f6dea76",
"text": "Watch Google Drive",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-drive-api",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {},
"description": "Interact with Google Drive to perform various operations on files and folders.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "d9f3f177-735e-426c-aff7-995377baaa4c",
"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 Drive item. Decide whether it warrants action in Telegram, and explain why."
},
"description": "Decides whether this Google Drive item warrants anything in Telegram.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "699273f0-97a3-48d5-ac09-2267c4706962",
"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": "f0439f41-9922-42ee-a825-552953862e00",
"start": {
"id": "450f263b-aa7e-4749-a450-33ce1f6dea76",
"type": "output"
},
"end": {
"id": "d9f3f177-735e-426c-aff7-995377baaa4c",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "6ce8ede2-cc82-4bfd-a1f3-d21f1d916822",
"start": {
"id": "d9f3f177-735e-426c-aff7-995377baaa4c",
"type": "output"
},
"end": {
"id": "699273f0-97a3-48d5-ac09-2267c4706962",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Install Document Extractor
Document Extractor is a working agent built around Google Drive. 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 Drive to Telegram
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Drive 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 Drive and Telegram — common questions
Can I connect Google Drive to Telegram without writing code?
Yes. Google Drive 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 file lands in a folder, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Google Drive 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 Drive, classify it against criteria you wrote in prose, draft something new, and act only when it is warranted.
Does my Google Drive 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 Drive, Telegram, and your chosen model provider — which can be a local one.
What does a Google Drive and Telegram run leave behind?
Every run is recorded end to end — the Google Drive 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.
