🔓 Unlock all 10,000+ workflows & prompts free Join Newsletter →
✅ Full access unlocked — explore all 10,000 AI workflow and prompt templates Browse Templates →
Home › n8n › Workflow
January 22, 2026

Telegram + Google Calendar, bookings confirmed for you

Telegram + Google Calendar, bookings confirmed for you - n8n workflow automation template
Lisa Granqvist Partner Workflow Automation Expert
Telegram + Google Calendar, bookings confirmed for you - n8n workflow automation template
Get a free AI assessment → Get a free AI assessment → ⬇️ Use template

You get a “Can I come in tomorrow?” message… then another… then five more. Suddenly you’re scrolling, checking your calendar, asking follow-up questions, and still worrying you’ll double book someone.

This is where Telegram booking automation pays for itself. Salon owners feel it first, honestly, but clinic managers and consultants doing appointments in chat get stuck in the same loop. The outcome is simple: bookings get confirmed inside Telegram, and the slot lands in Google Calendar without you babysitting it.

This workflow turns messages (text, voice, even photos and PDFs) into scheduled appointments, then sends confirmations and reminders. You’ll see how it works, what you need, and what to tweak so it fits your business rules.

How This Automation Works

See how this solves the problem:

n8n Workflow Template: Telegram + Google Calendar, bookings confirmed for you

The Challenge: Booking Requests Get Lost (and Messy) in Chat

Booking through Telegram sounds convenient until you’re the one running it. People message in fragments (“Tomorrow afternoon?” then “Actually 4?”), they send voice notes while you’re with a client, and you end up playing human router between your calendar and your inbox. The real cost isn’t one message. It’s the constant context switching, the missed follow-ups, and the awkward “sorry, that time is gone” when you accidentally confirm two people for the same slot. Even worse, you’re doing all this work just to get to the starting line of the service.

It adds up fast. Here’s where it breaks down in real life.

  • You waste about 10 minutes per booking just collecting the basics (service, date, time, name, phone).
  • Checking availability manually invites mistakes, especially when you’re replying between appointments.
  • People don’t show if there’s no reminder, and you usually remember reminders when it’s already too late.
  • Spam and “price-check” messages clog the same channel as paying customers, which makes you slower with everyone.

The Fix: Confirm Appointments in Telegram, Sync to Google Calendar

This workflow acts like a booking coordinator living inside Telegram. A message comes in, it gets queued safely (so you don’t process the same conversation twice), and an AI booking agent takes over the back-and-forth: what service they want, who it’s for (including “book for my friend Sarah”), and which time they’re asking about. While the customer is chatting, the automation checks Google Calendar for availability, follows your limits (like a maximum number of appointments per customer), and sends a clear confirmation once a slot is secured. Later, it runs a scheduled check and pushes reminders at a consistent time (like 8 PM for next-day visits). No more sticky notes. No more “did I confirm that already?”

The workflow starts when a customer messages your Telegram bot. From there, it interprets the request (text, voice transcription, image analysis, or PDF extraction), checks your live Google Calendar events, and then confirms the booking back in Telegram. Finally, a separate scheduled trigger sends automatic reminders for upcoming appointments.

What Changes: Before vs. After

Real-World Impact

Say you handle 8 booking requests a day through Telegram. Manually, you spend maybe 10 minutes per request asking questions, checking Google Calendar, confirming, and logging details, which is about 80 minutes daily. With this workflow, you glance at exceptions only: the bot acknowledges instantly, the agent confirms using live calendar availability, and reminders happen automatically at night. In practice, you’re often down to about 10 minutes total per day, mostly for edge cases.

Requirements

  • n8n instance (try n8n Cloud free)
  • Self-hosting option if you prefer (Hostinger works well)
  • Telegram to receive messages and send confirmations.
  • Google Calendar for real-time availability and scheduling.
  • Redis for rate limiting, locks, and chat memory.
  • OpenAI API key (get it from your OpenAI dashboard) for chat, image, and voice processing.

Skill level: Intermediate. You’ll connect accounts, paste API keys, and adjust a few business rules like hours and booking limits.

Need help implementing this? Talk to an automation expert (free 15-minute consultation).

The Workflow Flow

A Telegram message kicks things off. The bot receives a new message and quickly checks if it’s the business owner/admin or a customer, because those conversations should be handled differently.

Messages are queued and controlled. Redis stores incoming messages briefly, applies rate limits (the default is about 100 messages per hour), and creates a processing lock so the same chat doesn’t get processed twice when things get busy.

Content gets interpreted in plain language. Text goes straight to the booking agent, voice gets downloaded and transcribed, images can be analyzed for context, and PDFs can be extracted (with checks to reject unsupported formats). The workflow keeps short-term memory so the agent can ask follow-ups without starting over.

Availability is checked, then confirmations go out. The workflow pulls Google Calendar events, proposes valid times, and once a slot is selected it sends a booking confirmation back to Telegram. A scheduled trigger later looks at upcoming events and sends next-day reminders at a consistent time.

You can easily modify booking limits and business hours to match how you operate. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Telegram Trigger

This workflow begins when a message arrives in Telegram. You’ll configure the incoming trigger and the owner check before any processing begins.

  1. Add and open Telegram Incoming Trigger.
  2. Credential Required: Connect your Telegram credentials.
  3. Confirm the flow from Telegram Incoming Trigger to Confirm Owner Status.
  4. In Confirm Owner Status, review your owner-check logic to route only authorized chats to Initialize Payload.
⚠️ Common Pitfall: If Telegram credentials are missing, the trigger will not receive updates, and no messages will be processed.

Step 2: Connect Redis and Rate Control

Redis is used for message batching, locking, and hourly rate limits. This ensures messages are processed safely and within your usage thresholds.

  1. Open Initialize Payload and confirm it passes into Rate Control Logic.
  2. In Rate Control Logic, confirm it routes to Hourly Redis Key and then to Increment Hourly Count.
  3. Review Validate Usage Limit and ensure it feeds Check Rate Limit Flag then Should Send Message.
  4. Credential Required: Connect your Redis credentials to all Redis nodes (8 nodes handle queueing, locks, and counters).
Ensure the Redis instance has persistent storage enabled to avoid losing locks and queued messages during restarts.

Step 3: Set Up Content Routing and Payload Preparation

Messages are routed by content type (text, audio, image, or file), then prepared into a standard payload for the AI assistant.

  1. Verify Limit Threshold Check routes into Route by Content Type after Retrieve Calendar Events.
  2. In Route by Content Type, confirm the branches go to Prepare Text Payload, Fetch Audio URL, Fetch Image URL, Validate PDF Only, or Unsupported Content Notice.
  3. Open Prepare Text Payload and confirm it connects directly to Reservation Assistant Agent.

Step 4: Configure File, Audio, and Image Processing

Audio, images, and documents are downloaded, parsed, and converted into assistant-ready payloads.

  1. Verify the audio flow: Fetch Audio URL → Download Audio File → Transcribe Audio → Audio Payload → Reservation Assistant Agent.
  2. Verify the image flow: Fetch Image URL → Analyze Image Content → Image Payload → Reservation Assistant Agent.
  3. Verify the file flow: Validate PDF Only → Fetch File URL → Download Document File → Extract Document Data → File Payload → Reservation Assistant Agent.
  4. Confirm the non-PDF branch of Validate PDF Only routes to Invalid Format Alert.
  5. Credential Required: Connect your OpenAI credentials in Analyze Image Content and Transcribe Audio.
⚠️ Common Pitfall: If your file validation allows non-PDFs through, Extract Document Data may fail silently and produce empty payloads.

Step 5: Set Up the AI Reservation Assistant

The AI agent uses chat models, tools, and memory to interpret requests and confirm bookings.

  1. Open Reservation Assistant Agent and verify it receives inputs from Prepare Text Payload, Audio Payload, Image Payload, and File Payload.
  2. Ensure GPT Mini Model and Gemini Flash Model are connected as language models to Reservation Assistant Agent.
  3. Credential Required: Connect your OpenAI credentials in GPT Mini Model and your Google Gemini credentials in Gemini Flash Model.
  4. Confirm Cancel Agent Tool, Booking MCP Connector, Redis Chat Memory Store, and Send Acknowledgement are attached to Reservation Assistant Agent.
  5. Credential Required: Connect your MCP credentials for Booking MCP Connector on Reservation Assistant Agent.
  6. Credential Required: Connect Redis credentials for Redis Chat Memory Store on Reservation Assistant Agent.
  7. Credential Required: Connect Telegram credentials for Send Acknowledgement on Reservation Assistant Agent.
For AI tool sub-nodes (tools and memory), add credentials on the parent node Reservation Assistant Agent, not the sub-nodes themselves.

Step 6: Connect Google Calendar Scheduling

The workflow pulls calendar availability for booking decisions and sends scheduled reminders.

  1. Configure Retrieve Calendar Events to pull live availability for Limit Threshold Check.
  2. Set up the reminder flow: Scheduled Trigger → Compute Next Day → Get Scheduled Events → Format Reminder Details → Send Client Reminder.
  3. Credential Required: Connect your Google Calendar credentials in Retrieve Calendar Events and Get Scheduled Events.

Step 7: Configure Telegram Outputs

Messages are sent to users and owners for confirmations, alerts, and reminders.

  1. Confirm the dispatch chain: Should Send Message → Dispatch User Message → Dispatch Owner Message.
  2. Verify Reservation Assistant Agent routes to Send Booking Confirmation.
  3. Ensure Unsupported Content Notice, Invalid Format Alert, and Send Client Reminder are configured with message templates.
  4. Credential Required: Connect your Telegram credentials to all Telegram nodes (6 nodes handle user and admin messaging).

Step 8: Test and Activate Your Workflow

Run a full test cycle to validate routing, AI responses, and notifications before enabling production.

  1. Click Execute Workflow and send a Telegram message with text, audio, image, and PDF to validate all branches.
  2. Confirm that Queue Incoming Message → Create Processing Lock → Delay Execution → Retrieve Current Lock completes without Redis errors.
  3. Verify a successful run produces a response from Send Booking Confirmation and optional notifications from Dispatch User Message and Dispatch Owner Message.
  4. Activate the workflow by toggling it to Active once results match your expectations.
🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Watch Out For

  • Google Calendar credentials can expire or be missing scope permissions. If bookings stop confirming, check the Google Calendar node’s account connection in n8n first.
  • If you’re using Wait nodes or relying on external processing (like audio transcription), 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 and your exact service list early or you’ll be editing outputs forever.

Similar Automations

If your team also books through WhatsApp, WhatsApp + Google Calendar: bookings handled for you helps you keep the same “chat-to-calendar” experience across both channels.

For operations that care most about reducing no-shows, WhatsApp + Google Calendar: confirmations handled is a good companion because it leans into confirmations and follow-ups.

When bookings start as a form submission instead of a chat, Jotform + Gmail: approved appointment emails sent fits nicely alongside this workflow for approvals, routing, and clean email notifications.

Need scheduling that’s built around a dedicated booking link and availability rules? WhatsApp to Cal.com, bookings handled for you is useful when you want Cal.com to be the source of truth instead of Google Calendar.

Finally, if you like the Telegram channel but want a slightly different “in-chat” booking approach, Telegram to Google Calendar, bookings handled in chat is worth comparing for a simpler chat-first scheduling flow.


Quick reference:

Common Questions

How quickly can I implement this Telegram booking automation automation?

About an hour if your Telegram bot and Google Calendar are ready.

Can non-technical teams implement this booking automation?

Yes, but you’ll want one person comfortable with connecting accounts and API keys. Once it’s wired up, daily use is just “reply in Telegram like normal.”

Is n8n free to use for this Telegram booking automation workflow?

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 a few dollars a month for smaller teams, more if you transcribe lots of voice notes).

Where can I host n8n to run this automation?

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.

How do I adapt this Telegram booking automation solution to my specific challenges?

You can adjust the rate limit and booking caps in the Redis and “Validate Usage Limit” logic, then refine how the Reservation Assistant Agent asks questions (service, duration, staff member). Many teams also tweak the “Retrieve Calendar Events” logic to respect buffers like “no bookings within 2 hours,” and they customize the confirmation and reminder messages sent by the Telegram nodes.

Why is my Telegram connection failing in this workflow?

Most of the time it’s a Telegram bot token or permission issue, not the workflow. Recheck the credentials used by the Telegram Trigger and send nodes, then confirm your bot can actually receive messages in the chat you’re testing. If failures happen only during busy periods, you may also be hitting rate limits and should review the Redis rate control and your Telegram API limits.

What’s the capacity of this Telegram booking automation solution?

If you self-host, there’s no execution limit (it mainly depends on your server and how much AI processing you do). On n8n Cloud, capacity depends on your plan’s monthly executions, and busy bots can reach that faster than you expect. Practically, this workflow can handle lots of chats because it queues messages in Redis, but voice and document processing will slow things down a bit. If you expect heavy volume, consider limiting supported media types or pushing transcription to off-peak hours.

Is this Telegram booking automation automation better than using Zapier or Make?

Often, yes, because this isn’t just “message in, event out.” You’re doing queuing, rate limiting, conversation memory, and AI-based interpretation (including voice transcription and image/PDF handling), which is awkward and expensive in simpler builders. n8n also gives you a self-hosting option, so you’re not paying more every time a customer sends three messages in a row. Zapier or Make can still be fine for basic two-step flows, like “form submission → create calendar event,” but chat-based booking is a different animal. If you’re torn, map your real conversation flow first, then choose the tool. Talk to an automation expert and we’ll sanity-check it with you.

Once this is running, Telegram stops being a chaotic inbox and becomes a reliable booking channel tied to your real availability. Set it up once, then let confirmations and reminders happen in the background.

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.

Talk to Automation Expert →

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

×

Use template

Get instant access to this n8n workflow Json file

Copy and import json workflow into your n8n workflow

💬
Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.

Get a free quote today!
Get a free quote today!

Tell us what you need and we'll get back to you within one working day.