Telegram to Google Calendar, schedule from chat
You open Telegram, someone asks for “tomorrow at 3,” and you think you’ll add it to your calendar later. Then later turns into never. Or worse, you add it fast and get the details slightly wrong.
This Telegram calendar automation hits founders who live in chat all day. marketers juggling calls between campaigns feel it too. And if you run a small team, you’re probably the calendar “catch-all” by default.
This workflow lets you create and fetch Google Calendar events from a Telegram message, with an AI agent translating messy text into clean event details. You’ll see how it works, what you need, and what you can expect in real daily use.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram to Google Calendar, schedule from chat
flowchart LR
subgraph sg0["When chat message received Flow"]
direction LR
n0@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar1", pos: "b", h: 48 }
n1@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar", pos: "b", h: 48 }
n2@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", pos: "b", h: 48 }
n3@{ icon: "mdi:brain", form: "rounded", label: "Google Gemini Chat Model", pos: "b", h: 48 }
n4@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n5@{ icon: "mdi:play-circle", form: "rounded", label: "When chat message received", pos: "b", h: 48 }
n2 -.-> n4
n1 -.-> n4
n0 -.-> n4
n3 -.-> n4
n5 --> n4
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 n5 trigger
class n4 ai
class n3 aiModel
class n2 ai
The Problem: Scheduling Gets Lost in Chat
Chat is where work happens now. Meeting requests, quick follow-ups, “can we do Friday morning?” messages, even reminders you send to yourself. The problem is that chat is not a calendar, so details drift. You copy a time wrong, you forget the timezone, or you don’t capture the location link. Then you’re doing the awkward “sorry, I’m double-booked” message, which honestly feels unprofessional even when it’s a simple mistake.
It adds up fast. Not because one event is hard, but because the constant switching breaks your focus.
- You lose about 5 minutes every time you bounce between Telegram and Google Calendar just to add one event.
- Messages are vague (“after lunch”), which makes manual entry a guessing game and leads to back-and-forth.
- Small mistakes sneak in, like wrong dates, missing guests, or forgetting to add the meeting link.
- Checking your day shouldn’t require scrolling through chat history, but that’s what happens when the calendar isn’t kept current.
The Solution: Turn Telegram Messages Into Calendar Actions
This n8n workflow connects Telegram to Google Calendar through an AI agent. You send a natural message like “Book a call with Sam next Tuesday at 11, 30 minutes, Zoom” or “What’s on my calendar tomorrow afternoon?” The AI reads your prompt, keeps context using simple memory (so follow-up messages still make sense), and decides which action to take. If it’s a scheduling request, the workflow formats the details into a proper calendar event and sends it to Google Calendar through an HTTP request. If it’s a “what’s next?” request, it fetches matching events and replies back in Telegram with a clean summary and a confirmation.
The workflow starts in Telegram, where the message acts as the trigger. Then the AI agent interprets intent and fills in missing structure (title, date, start time, duration). Finally, n8n creates or retrieves the calendar events and sends you an instant response, so you know it worked.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you handle about 10 scheduling moments a week (new calls, reschedules, quick “hold this time” requests). Manually, it’s usually 5 minutes to open Calendar, find the slot, type details, and double-check. That’s roughly 50 minutes, plus the extra brain-switching that drags the day down. With this workflow, you send one Telegram message that takes maybe 30 seconds, wait for the confirmation, and move on. You’ve effectively turned “calendar admin” into something that fits between tasks.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram to send messages and receive confirmations.
- Google Calendar for event creation and retrieval.
- OpenAI (or Gemini-compatible) API key (get it from your model provider’s API dashboard).
Skill level: Intermediate. You’ll connect accounts, paste an API key, and adjust a couple of request fields if your calendar setup is unique.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Telegram message kicks it off. You send a plain-English request like “Schedule a call Friday at 2” or “What’s on my calendar this afternoon?” The Telegram node passes the message into n8n instantly.
The AI agent figures out intent and details. Using an AI chat model and simple memory, the workflow interprets what you meant, not just what you typed. If you follow up with “make it 45 minutes,” it can keep context instead of forcing you to retype everything.
Logic routes the request to the right action. n8n uses decision points (If/Switch) to choose between “create event” and “get events.” Then it sets the correct fields, so Google Calendar receives clean inputs instead of messy text.
You get a clear response back in chat. For new events, you receive a confirmation message (and optionally key details like time and title). For fetch requests, you get a short agenda-style list so you can make decisions quickly.
You can easily modify the message format and the calendar lookup window to match how you schedule. See the full implementation guide below for customization options.
Common Gotchas
- Telegram credentials can expire or get mismatched with the bot you’re messaging. If replies suddenly stop, check the Telegram node credentials and your bot permissions first.
- If you’re using Wait nodes or external processing, 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.
Frequently Asked Questions
About 30 minutes once your accounts and API key are ready.
No. You’ll connect Telegram and paste an API key. The only “technical” part is checking a couple of fields if your calendar requires a specific format.
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 (or your chosen model) API costs, which are usually a few cents per day for light scheduling.
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 want to be intentional. You can extend the AI Agent prompt to always ask for (or infer) “guest emails” and “meeting location,” then map those values in the Edit Fields (Set) node before the HTTP Request to Google Calendar. Common customizations include forcing your default timezone, adding a standard meeting description, and setting reminders like “10 minutes before.” If you already have a preferred video tool, you can also standardize the location field to your Zoom/Meet template link so every event is consistent.
Usually it’s the bot token or webhook setup drifting out of sync. Regenerate your Telegram bot token (if needed), update the Telegram credentials in n8n, and confirm you’re messaging the same bot the workflow is listening to. If it fails only sometimes, rate limits or long AI processing can also cause Telegram timeouts, so shorten the AI prompt or increase waits where appropriate.
A lot for typical small-team scheduling.
Often, yes, because this workflow depends on “interpret what I meant” logic, not rigid form fields. n8n handles branching (create vs. fetch, different parsing paths, fallbacks) without the same per-step cost pressure. You can also self-host, which is a big deal if you run many small automations all day. Zapier or Make can be quicker for a simple two-step “message triggers event” flow, but they get awkward when you want memory, prompt control, and more complex routing. Talk to an automation expert if you want help choosing.
Once this is running, scheduling stops being a separate chore and becomes a quick message you fire off between tasks. The workflow handles the repetitive stuff. You handle the day.
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.
