Google Calendar meets Telegram for meeting reminders
You set the calendar reminder. You still miss the meeting. The alert shows up at the worst time, gets buried under other notifications, and suddenly you’re joining late and apologizing.
Executive assistants feel it first, because they’re the ones protecting everyone else’s time. But founders running from call to call and marketing leads juggling campaigns get hit too. This Calendar Telegram reminders automation gives you one clear message, in one place, about 1 hour before the event.
You’ll see how the workflow checks your Google Calendar, prevents duplicate nudges, writes a friendly reminder using AI, then sends it to Telegram with the details you actually need.
How This Automation Works
Here’s the complete workflow you’ll be setting up:
n8n Workflow Template: Google Calendar meets Telegram for meeting reminders
flowchart LR
subgraph sg0["Scheduled Automation Start Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Automation Start", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Conversation Model", pos: "b", h: 48 }
n2@{ icon: "mdi:location-exit", form: "rounded", label: "Retrieve Upcoming Event", pos: "b", h: 48 }
n3@{ icon: "mdi:cog", form: "rounded", label: "Deduplicate Alerts", pos: "b", h: 48 }
n4@{ icon: "mdi:robot", form: "rounded", label: "Assistant Agent", pos: "b", h: 48 }
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Dispatch Telegram Alert"]
n3 --> n4
n4 --> n5
n0 --> n2
n1 -.-> n4
n2 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n4 ai
class n1 aiModel
class n0 disabled
classDef customIcon fill:none,stroke:none
class n5 customIcon
Why This Matters: Calendar reminders that get ignored
Most missed meetings aren’t caused by “forgetting.” They happen because the reminder isn’t strong enough to cut through the noise. A generic pop-up with a title like “Catch up” doesn’t tell you where to go, what to bring, or why it matters, so your brain postpones it for “later.” Then Slack pings, emails stack up, someone calls, and that tiny calendar alert is gone. The cost isn’t just embarrassment. It’s lost momentum, late starts, rushed prep, and the constant feeling you’re reacting instead of running your day.
It adds up fast. Here’s where the system usually breaks down:
- You get reminders in multiple places, so you stop trusting any single notification.
- The default alert is too dry to prompt action, especially when the event title is vague.
- Important context (location, link, notes) is missing, which means frantic searching right before the call.
- If you try to “fix it manually,” you end up rewriting event descriptions and still forgetting sometimes.
What You’ll Build: Friendly Telegram reminders from Google Calendar
This workflow acts like a lightweight assistant sitting between your calendar and your chat. Every minute, it checks Google Calendar for events that are starting within the next hour. When it finds one, it makes sure you haven’t already been reminded about that exact event (so you don’t get spammed). Then an AI agent takes the event details you already have, like the title, description, location, start and end time, and the organizer, and turns them into a warm, human reminder you’ll actually read. Finally, it sends that message to your chosen Telegram chat, so the nudge lands where you’re already paying attention.
The workflow starts on a schedule, not on guesswork. Google Calendar provides the raw facts, the agent shapes them into something clear, and Telegram becomes the single delivery channel. One hour of runway, and much less scrambling.
What You’re Building
| What Gets Automated | What You’ll Achieve |
|---|---|
|
|
Expected Results
Say you have 6 meetings in a busy day. Without automation, you might spend about 5 minutes before each one finding the link, re-reading notes, and checking where it is. That’s roughly 30 minutes of “where is everything?” time, plus the occasional late join. With this workflow, the reminder arrives in Telegram about 1 hour before, already summarized in plain language. You glance, you’re ready, and you keep moving.
Before You Start
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Calendar for upcoming event data.
- Telegram to receive reminders in a chat.
- OpenAI API key (get it from the OpenAI platform dashboard).
Skill level: Beginner. You’ll connect accounts and paste a chat ID, then test once.
Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).
Step by Step
A scheduled check runs in the background. The workflow starts with a schedule trigger that runs every minute, which means you don’t have to remember to “run” anything.
Google Calendar is queried for the next hour. It pulls events that start between “now” and “one hour from now,” using your calendar and timezone settings so the timing stays consistent.
Duplicates are blocked before messaging. If the workflow has already sent a reminder for a specific event, it filters it out so you don’t get repeat nudges when the schedule runs again.
The reminder is written and delivered. An AI agent (using an OpenAI chat model) turns the event details into a friendly message, then Telegram sends it to your chosen chat ID with the name, time, location, and any helpful context.
You can easily modify the “1 hour before” window to 30 minutes or 2 hours based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set up the scheduled trigger so the workflow checks for upcoming calendar events on a fixed interval.
- Add or open Scheduled Automation Start.
- Set the schedule rule to run every minute by configuring Rule to minutes interval
1. - Ensure Scheduled Automation Start is enabled (it is currently disabled in the workflow).
- Confirm the connection flows from Scheduled Automation Start to Retrieve Upcoming Event.
Tip: The workflow timezone is set to Europe/Rome, so your scheduled checks will follow that timezone.
Step 2: Connect Google Calendar
Configure calendar retrieval so upcoming events are fetched in a specific time window.
- Open Retrieve Upcoming Event and set Operation to
getAll. - Set Limit to
5. - Set Time Min to
={{ $now.plus({ hour: 1 }) }}and Time Max to={{ $now.plus({ hour: 1, minute:1 }) }}. - Select the calendar Calendar value
[YOUR_EMAIL]. - Credential Required: Connect your googleCalendarOAuth2Api credentials.
- Verify the flow continues from Retrieve Upcoming Event to Deduplicate Alerts.
⚠️ Common Pitfall: If the time window is too narrow, you may not fetch any events. Adjust Time Min and Time Max carefully when testing.
Step 3: Set Up Assistant Agent
Filter duplicate alerts, craft a friendly reminder message with AI, and ensure the language model is connected.
- Open Deduplicate Alerts and set Operation to
removeItemsSeenInPreviousExecutions. - Set Dedupe Value to
={{ $json.id }}so only new events pass through. - Open Assistant Agent and confirm Prompt Type is
definewith Has Output Parser enabled. - Set the Text prompt to the event template:
=These are the details of the event/appointment: Event Name: {{ $('Retrieve Upcoming Event').item.json.summary }} Description: {{ $('Retrieve Upcoming Event').item.json.description }} Location: {{ $('Retrieve Upcoming Event').item.json.location }} Start: {{ $('Retrieve Upcoming Event').item.json.start.dateTime }} End: {{ $('Retrieve Upcoming Event').item.json.end.dateTime }} Created by: {{ $('Retrieve Upcoming Event').item.json.creator.email }}. - Ensure OpenAI Conversation Model is connected as the language model for Assistant Agent.
- Credential Required: Connect your openAiApi credentials in OpenAI Conversation Model (AI credentials are set on the parent model node, not the agent).
Step 4: Configure Telegram Alerts
Send the AI-generated reminder to Telegram with the configured chat ID.
- Open Dispatch Telegram Alert and set Text to
={{ $json.output }}. - Set Chat ID to
[YOUR_ID]. - Credential Required: Connect your telegramApi credentials.
Step 5: Test and Activate Your Workflow
Run a manual test and then enable the workflow for production scheduling.
- Click Execute Workflow to run a manual test from Scheduled Automation Start.
- Verify that Retrieve Upcoming Event returns events, Deduplicate Alerts passes only new ones, and Assistant Agent produces output.
- Confirm a Telegram message arrives from Dispatch Telegram Alert with the formatted reminder.
- Toggle the workflow to Active to enable scheduled reminders in production.
Troubleshooting Tips
- Google Calendar permissions matter. If events aren’t being found, check the connected Google account in n8n credentials and confirm the right calendar is selected.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Quick Answers
About 30 minutes if your accounts are ready.
No coding required. You’ll mainly connect Google Calendar, Telegram, and paste your OpenAI key.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API costs (often just a few cents per day at low volume).
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s the part people customize most. You can change the “next hour” window in the Google Calendar event lookup to 30 minutes, 2 hours, or even “tomorrow morning.” You can also tweak the Assistant Agent instructions so it writes in your voice (more formal, more direct, or even a short checklist). Some teams send reminders to a shared Telegram channel, while others route personal events to a private chat ID.
Usually it’s the chat ID or bot permissions. Confirm the bot is allowed to message that chat, then re-check the Telegram credentials in n8n and make sure you’re sending to the right CHAT_ID. If you recently regenerated the bot token, update it in n8n. Also watch for rate limits if you’re sending lots of reminders at once.
For most small teams, plenty.
It depends on how “smart” you want the reminder to be. n8n is a better fit when you want branching logic (like deduplication) and AI-generated messages without paying extra per feature, and self-hosting can be a big cost win if you run automations constantly. Zapier and Make can feel simpler for basic two-step alerts, but they get clunky when you add memory, filtering, and prompt tuning. If you’re trying to standardize reminders across a team, n8n’s flexibility is honestly hard to beat. Talk to an automation expert if you’re not sure which fits.
Once this is live, your calendar stops whispering and starts communicating. The workflow handles the nudge so you can show up ready.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
