Google Calendar to Telegram, never miss new meetings
You add a meeting to Google Calendar… and somehow you still find out about it late. Or worse, someone else adds it, and you only notice when you’re already double-booked.
Marketing managers trying to protect focus time feel this fast. A business owner juggling calls and delivery work feels it too. Same story for an ops lead coordinating a small team. This Calendar Telegram alerts automation sends new events to Telegram so you see schedule changes instantly.
You’ll see what the workflow does, what you need to run it, and where teams usually tweak it for their own schedule habits.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Google Calendar to Telegram, never miss new meetings
flowchart LR
subgraph sg0["Calendar Event Watcher Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Calendar Event Watcher", pos: "b", h: 48 }
n1["<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/>Telegram Notification Sender"]
n0 --> n1
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
classDef customIcon fill:none,stroke:none
class n1 customIcon
The Problem: New Meetings Sneak Up on You
Google Calendar is great at storing your schedule. It’s not always great at making sure you actually notice what changed. New events get added by clients, teammates, booking tools, or even your past self… and they blend into the calendar like everything else. Then you’re checking the app more than you want, switching context, and still missing details like location or who created the event. Over a week, that turns into small surprises that cause real damage: rushed prep, late joins, and awkward “sorry, I didn’t see it” messages.
It adds up fast. Here’s where it usually breaks down.
- You end up checking Google Calendar several times a day “just in case,” which quietly eats focus time.
- When someone else creates the event, you often miss the description and context until you’re already in the meeting.
- Last-minute calendar changes get buried under other notifications, especially on busy phones.
- Manual “FYI, I booked you” messages are inconsistent, and sometimes nobody sends them.
The Solution: Instant Telegram Alerts for New Calendar Events
This workflow watches a specific Google Calendar for newly created events. The moment an event appears, n8n pulls out the useful details (title, description, creator, start and end times, plus location if it exists) and formats them into a clean Telegram message. That message is then sent to a Telegram chat you choose, which can be your own private chat or a team group. The end result is simple: you learn about new meetings where you already spend time, without opening Calendar to “double-check.” Honestly, it’s one of those automations that feels small until you run it for a week.
The workflow starts when a new Google Calendar event is created. It packages the key fields into a readable update. Finally, Telegram delivers it instantly to your chosen chat so the schedule change doesn’t hide in plain sight.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say your week involves about 20 new events that get created by other people (client calls, internal meetings, vendor check-ins). Manually, you might check Calendar 6 times a day at roughly 2 minutes each, which is about an hour a week, plus another hour lost to “wait, what’s this meeting?” re-checking details. With this workflow, you spend maybe 10 minutes once to connect accounts, then Telegram pings you instantly when something new appears. The checking disappears, and you stay ahead of surprises.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Calendar for the event source you want monitored
- Telegram to receive alerts in a chat or group
- Telegram Bot Token (get it from BotFather in Telegram)
Skill level: Beginner. You’ll connect Google via OAuth2 and paste a bot token plus chat ID.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A new calendar event is created. n8n listens to your chosen Google Calendar using the Google Calendar Trigger, so it reacts as soon as the event exists.
The workflow pulls the important fields. It grabs the event title, description, creator, start time, end time, and location (when it’s present), then prepares them for a readable alert.
Telegram gets a clean notification. The Telegram node sends the message to a chat ID you choose, which means you can use a private chat for personal alerts or a group for team visibility.
You keep the loop tight. As soon as the message lands, you can confirm you saw it, ask a teammate a question, or forward it. No hunting through Calendar screens.
You can easily modify the message format to match your style (for example, a shorter alert or one that highlights location). See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Google Calendar Trigger
Set up the workflow to watch for new Google Calendar events.
- Add the Calendar Event Watcher node as your trigger.
- Set Trigger On to
eventCreated. - In Poll Times, keep the default item set to
everyMinutefor frequent checks. - Select your target calendar in Calendar ID.
- Credential Required: Connect your googleCalendarOAuth2Api credentials.
⚠️ Common Pitfall: If Calendar ID is left empty, no events will be detected.
Step 2: Configure the Telegram Notification Sender
Send a formatted message to Telegram when a new calendar event is created.
- Add the Telegram Notification Sender node and connect it to Calendar Event Watcher.
- Set Text to
=Event Name: {{ $json.summary }} Description: {{ $json.description }} Event Location: {{ $json.location }} Start Date: {{ $json.start.dateTime }} End Date: {{ $json.end.dateTime }} Creator: {{ $json.creator.email }}. - Enter the target Telegram chat in Chat ID.
- Under Additional Fields, keep Append Attribution set to
falseif you want a clean message. - Credential Required: Add Telegram credentials in Telegram Notification Sender (none are configured yet).
⚠️ Common Pitfall: If Chat ID is empty, Telegram will reject the message. Use the numeric chat ID or channel ID.
Step 3: Test and Activate Your Workflow
Validate the trigger and notification before enabling the workflow.
- Click Execute Workflow and create a new event in the selected Google Calendar.
- Confirm that Telegram Notification Sender posts a message with the event details.
- If the message is missing fields, verify the event has values for
summary,description,location,start.dateTime, andend.dateTime. - Once verified, toggle the workflow to Active to run in production.
Common Gotchas
- Google Calendar OAuth credentials can expire or lose permissions after password changes. If alerts stop, check the Google Calendar credentials inside n8n first.
- Telegram bots can message groups only after being added, and some groups require admin permission. If messages never arrive, confirm the bot is in the chat and your Chat ID is the right one.
- Event descriptions can be empty or messy depending on who created the meeting. Adjust the Telegram message template so it gracefully handles missing fields instead of sending confusing blank lines.
Frequently Asked Questions
About 20 minutes if you already have a Telegram bot and your Google account ready.
No. You’ll authenticate Google Calendar, paste your Telegram bot token, and choose the chat ID.
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 Telegram and Google usage (this workflow doesn’t require paid AI calls).
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, but you’ll need to add the bot to the group and use that group’s Chat ID in the Telegram Send Message node. Many teams also tweak the message template to include the organizer name first, then the start time and location. If you want filtering, you can add an If node after the Google Calendar trigger to only alert on certain keywords or specific creators. It’s a small change, and it makes the alerts feel “smart” instead of noisy.
Usually it’s the wrong bot token or an incorrect Chat ID. Also check that the bot is allowed to post in the target chat (groups can block it), and confirm the workflow is using the same Telegram credentials you tested in n8n.
For most small teams, hundreds of events a week is fine.
It depends on what you value. Zapier and Make can absolutely send a “new event” message, and they may feel simpler for a two-step setup. n8n wins when you want control: adding filters, formatting logic, multiple chats, or routing certain events to different places without paying extra for every branch. Self-hosting is also a big deal if you dislike per-task pricing. If you’re unsure, Talk to an automation expert and you’ll get a straight recommendation.
New meetings shouldn’t be a surprise. Set this up once, and Telegram becomes your early-warning system for schedule changes.
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.
