Telegram to Google Calendar, bookings handled in chat
You know the dance. Someone messages “Can we do Tuesday at 2?” and suddenly you’re juggling time zones, re-typing details into a calendar, and chasing confirmation like it’s your second job.
Marketing leads feel it when calls pile up. Consultants get it when every booking is custom. And if you run a small service business, Telegram Calendar booking is the difference between smooth scheduling and constant back-and-forth.
This workflow turns simple Telegram messages into real Google Calendar actions (create or cancel), then replies with a clean confirmation. Below you’ll see how it works, what you get, and the common tripwires to avoid.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram to Google Calendar, bookings handled in chat
flowchart LR
subgraph sg0["Telegram Flow"]
direction LR
n0@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n2@{ icon: "mdi:memory", form: "rounded", label: "Simple Memory", pos: "b", h: 48 }
n3@{ icon: "mdi:location-exit", form: "rounded", label: "Google Calendar1", pos: "b", h: 48 }
n4["<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 Trigger"]
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/>Telegram"]
n0 --> n5
n2 -.-> n0
n3 -.-> n0
n4 --> n0
n1 -.-> n0
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 n4 trigger
class n0 ai
class n1 aiModel
class n2 ai
classDef customIcon fill:none,stroke:none
class n4,n5 customIcon
The Problem: Scheduling Lives in Too Many Places
Booking a meeting should be quick. Instead, it turns into a mini project: read a message, interpret what they mean, open Google Calendar, create an event, double-check the title, then message back with details. Now multiply that by a few bookings a day and the small mistakes start creeping in. A wrong date. A vague event title you can’t search later. A cancellation you forgot to apply, so you still show up. It’s not hard work. It’s draining work, and it steals attention from the things you actually get paid for.
It adds up fast. Here’s where it breaks down in real life.
- You end up copying the same details from chat into Calendar over and over, which is how typos sneak in.
- Cancellations get buried in message threads, so “please cancel” becomes “oops, I forgot.”
- Event naming is inconsistent, which makes search and reporting way harder later.
- You spend mental energy confirming basics instead of prepping for the meeting itself.
The Solution: Telegram Messages That Actually Schedule
This n8n workflow listens to messages sent to your Telegram bot and treats them like scheduling requests. When someone types “Book Friday 10am with Sam” (or “Cancel my Monday call”), an AI Agent reads the message, figures out the intent, and pulls out the details you’d normally have to clarify. Then it takes the right action in Google Calendar: create a new event for bookings, or find and delete an existing event for cancellations. Finally, the workflow sends a confirmation back in Telegram, so the user knows exactly what happened. Clean, consistent, and fast.
The workflow starts with a Telegram trigger, then the AI Agent interprets the request using an OpenAI chat model plus short-term conversation memory. After that, a Google Calendar tool creates or cancels the event, and Telegram sends the final confirmation message.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you handle 15 bookings and 5 cancellations in a typical week. Manually, even a “quick” booking is about 5 minutes to interpret the message, create the event, and send a confirmation (and cancellations take similar time), so you’re spending roughly 1.5 to 2 hours on pure admin. With this workflow, it’s closer to 30 seconds to type a request in Telegram, then a minute or two while the automation processes and replies. You still glance at edge cases, but the busywork mostly disappears.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram Bot to receive scheduling messages
- Google Calendar to create and cancel events
- OpenAI API key (get it from the OpenAI platform dashboard)
Skill level: Beginner. You’ll connect accounts, paste an API key, and test a few real messages.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A Telegram message hits your bot. The Telegram Trigger listens for new inbound messages and passes the text into the workflow instantly.
The AI interprets what the person wants. The Scheduling AI Assistant uses an OpenAI chat model to identify if this is a booking or a cancellation, then pulls out key details like date, time, and participant names. Conversation Memory helps when the user sends follow-ups like “make it 30 minutes later.”
Google Calendar gets updated. For bookings, the Calendar tool creates the event using the extracted details. For cancellations, it searches for the matching event and removes it, so your calendar reflects reality instead of “maybe.”
Telegram confirms the result. The Telegram Reply Sender posts a clear message back to the user with what was booked or canceled, which reduces “did it go through?” messages.
You can easily modify event titles to include your naming rules, or route cancellations to a manual review path based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Telegram Incoming Trigger
This workflow begins when a user sends a Telegram message, so the trigger must be connected to your Telegram bot.
- Add and open Telegram Incoming Trigger.
- Ensure Updates includes
message. - Credential Required: Connect your telegramApi credentials.
Step 2: Connect Calendar Scheduling Tools
The AI agent will use the calendar tool to create events, so the calendar configuration must be set accurately.
- Open Calendar Event Tool and select the target calendar under Calendar (e.g.,
[YOUR_EMAIL]). - Set Start to
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }}. - Set End to
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}. - Under Additional Fields, set Summary to
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Summary', ``, 'string') }}and Attendees to{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('attendees0_Attendees', ``, 'string') }}. - Set Use Default Reminders to
{{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Use_Default_Reminders', ``, 'boolean') }}. - Credential Required: Connect your googleCalendarOAuth2Api credentials.
Note: Calendar Event Tool is an AI tool connected to Scheduling AI Assistant, so tool usage is controlled by the agent.
Step 3: Set Up the Scheduling AI Assistant
This agent interprets user messages and decides when to create a calendar event.
- Open Scheduling AI Assistant and set Text to
{{ $json.message.text }}. - Keep Prompt Type as
define. - In System Message, confirm the rules include
{{ $now }}for time reference and GMT+08 (SGT). - Ensure OpenAI Chat Engine is connected as the language model for Scheduling AI Assistant and that credentials are added to OpenAI Chat Engine.
- Ensure Conversation Memory is connected as memory for Scheduling AI Assistant and uses session key
{{ $json.message.chat.id }}.
Credential Required: Connect your openAiApi credentials in OpenAI Chat Engine. Conversation Memory does not require credentials and should be configured within the agent.
Step 4: Configure Telegram Reply Sender
The workflow sends the AI’s response back to the same Telegram chat.
- Open Telegram Reply Sender and set Text to
{{ $json.output }}. - Set Chat ID to
{{ $('Telegram Incoming Trigger').item.json.message.chat.id }}. - Credential Required: Connect your telegramApi credentials.
⚠️ Common Pitfall: If the chat ID expression references a different trigger name, the reply will fail. Use the exact node name Telegram Incoming Trigger in the expression.
Step 5: Test and Activate Your Workflow
Run a live test to confirm that scheduling requests create calendar events and return a reply to Telegram.
- Click Test workflow in n8n and send a Telegram message like “Book a meeting next Tuesday at 2pm.”
- Verify Scheduling AI Assistant receives the message and triggers Calendar Event Tool.
- Confirm a new event appears in your selected Google Calendar.
- Check that Telegram Reply Sender returns a confirmation message.
- When successful, switch the workflow to Active to enable production usage.
Common Gotchas
- Telegram bot credentials can expire or be mis-copied. If things break, check the BotFather token and the Telegram Trigger credentials in n8n first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Google Calendar deletions can fail if the workflow can’t find the exact event. Tighten your event naming pattern (and keep it consistent) so “cancel with Sam” maps to a searchable title.
Frequently Asked Questions
About 30 minutes if your Telegram bot and Google account are ready.
No. You’ll connect Telegram and Google Calendar, then paste your OpenAI API 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 (usually a few cents per booking request, depending on your prompt and message length).
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 point the Calendar Event Tool to a different calendar ID, or add a simple routing rule so specific keywords (like “sales” or “support”) book into different calendars. Common customizations include adding a required “duration” rule, forcing a title template (Client Name + Service), and sending an extra confirmation to Slack or Gmail for internal visibility.
Usually it’s an incorrect or rotated bot token, so the Telegram Trigger can’t authenticate. Double-check the token in BotFather and update the Telegram credentials inside n8n. If it connects but doesn’t trigger, make sure your bot is allowed to receive messages (and you’re messaging the correct bot). Occasionally Telegram webhooks get stuck; re-saving credentials and reactivating the workflow often clears it.
A lot. On n8n Cloud, capacity depends on your plan’s monthly executions, and each booking or cancellation is typically one execution. If you self-host, there’s no platform execution cap, so the limit is basically your server size and how quickly Google Calendar and OpenAI respond.
Often, yes. This workflow relies on an AI Agent plus conversation memory, and n8n is simply more flexible for that kind of logic without turning every branch into a paid “task.” You also have the option to self-host for scale, which can matter once bookings ramp up. Zapier or Make can still be fine for very basic “form submission → create event” flows. If you’re unsure, Talk to an automation expert and sanity-check the best approach for your volume and edge cases.
Set it up once, then let Telegram handle the scheduling noise while your calendar stays accurate. Honestly, getting that mental space back is the real win.
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.
