Automate Google Calendar + Telegram
The shared clock your workflows can read and write. 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 Google Calendar; 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 Calendar event rather than a transcription of it.
When an event starts or ends in Google Calendar…
…an agent can send messages and alerts in Telegram — after reading the context and deciding it should.
When a meeting is created in Google Calendar…
…an agent can reply to commands in Telegram — after reading the context and deciding it should.
When a day begins in Google Calendar…
…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 or move events in Google Calendar — with the reasoning recorded in the run’s receipt.
When a command is sent in Telegram…
…an agent can add agendas to invites in Google Calendar — with the reasoning recorded in the run’s receipt.
When a schedule fires in Telegram…
…an agent can block focus time in Google Calendar — with the reasoning recorded in the run’s receipt.
Copy this Google Calendar → Telegram workflow
Start with the google-calendar-api node and the telegram-api node. Configure the Google Calendar 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": "4cb5795a-661b-4270-ae15-79b628ffdcdc",
"name": "Google Calendar → Telegram",
"nodes": [
{
"id": "2304e074-5bfa-4189-aa43-efff5cf38246",
"text": "Watch Google Calendar",
"x": 512,
"y": 144,
"isEditing": false,
"type": "google-calendar-new-event",
"icon": "connect",
"category": "trigger",
"isSelected": false,
"parameters": {
"calendarId": "CONFIGURE_CALENDARID"
},
"description": "Setup template for Google Calendar New Event. Listen for events created or updated on a Google Calendar and trigger the workflow. Configure credentials, inputs and output mapping before use.",
"error": null,
"isActive": false,
"output": null,
"outputs": {}
},
{
"id": "b4dac5dc-914e-4b0a-a84e-39a6eb328754",
"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 Google Calendar 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": "41e9da9b-49dd-41f9-ace6-5156225006de",
"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": "47bc9a97-0f52-458c-a144-2ae519e21f54",
"start": {
"id": "2304e074-5bfa-4189-aa43-efff5cf38246",
"type": "output"
},
"end": {
"id": "b4dac5dc-914e-4b0a-a84e-39a6eb328754",
"type": "input"
},
"startX": 800,
"startY": 168,
"endX": 512,
"endY": 360
},
{
"id": "b741c1e0-c233-49f4-a59d-77fcd60f9f00",
"start": {
"id": "b4dac5dc-914e-4b0a-a84e-39a6eb328754",
"type": "output"
},
"end": {
"id": "41e9da9b-49dd-41f9-ace6-5156225006de",
"type": "input"
},
"startX": 800,
"startY": 360,
"endX": 512,
"endY": 552
}
],
"zoomLevel": 1,
"canvasOffsetX": 0,
"canvasOffsetY": 0,
"isTinyNodeMode": false
}Configure Google Calendar New Event
Listen for events created or updated on a Google Calendar and trigger the workflow.
- calendarId — Calendar ID to monitor (defaults to 'primary') Current example:
CONFIGURE_CALENDARID.
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 Google Calendar. 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
- Get AGNT Community Core. Free, local, no sign-up needed to run a workflow.
- Add both connections to the vault — Google Calendar 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.
Google Calendar and Telegram — common questions
Can I connect Google Calendar to Telegram without writing code?
Yes. Google Calendar 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 an event starts or ends, send messages and alerts” — and the agent handles the rest.
How is this different from a field-mapping Google Calendar to Telegram automation?
A field mapping copies values and breaks on the first record nobody anticipated. The middle step here reads the Google Calendar 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 Google Calendar and Telegram data leave my machine?
AGNT Community Core is local-first, so there is no vendor middleman holding your Google Calendar 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 Google Calendar and Telegram run leave behind?
A receipt: what was read in Google Calendar, 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.
