Telegram to Google Calendar, bookings without back-and-forth
Booking appointments shouldn’t feel like playing email tennis. But the reality is a steady stream of “Does Tuesday at 3 work?”, missed replies, and the occasional double-book that turns your day into damage control.
Dental assistants feel this first, honestly. A practice manager juggling phones and walk-ins feels it too. And if you run a small clinic, this Telegram booking automation gives you back the time you usually lose to confirmations and calendar checking.
This workflow turns Telegram chat into confirmed Google Calendar bookings, then logs everything to Google Sheets. You’ll see what it fixes, what you need, and how the flow works before you implement it.
How This Automation Works
See how this solves the problem:
n8n Workflow Template: Telegram to Google Calendar, bookings without back-and-forth
flowchart LR
subgraph sg0["When chat message received Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "When chat message received", pos: "b", h: 48 }
n1@{ icon: "mdi:robot", form: "rounded", label: "AI Agent", pos: "b", h: 48 }
n2@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n3@{ icon: "mdi:memory", form: "rounded", label: "Window Buffer Memory", pos: "b", h: 48 }
n4@{ icon: "mdi:location-exit", form: "rounded", label: "Check Availability", pos: "b", h: 48 }
n5@{ icon: "mdi:location-exit", form: "rounded", label: "Creat event", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "Add data", pos: "b", h: 48 }
n6 -.-> n1
n5 -.-> n1
n2 -.-> n1
n4 -.-> n1
n3 -.-> n1
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
class n1 ai
class n2 aiModel
class n3 ai
class n6 database
The Challenge: Appointment Scheduling That Steals Your Day
Most appointment booking systems break down the moment a patient wants something slightly specific. They ask for a time. You check the calendar. You reply. They respond later. Meanwhile, another patient books the slot, or the dentist adds a block, or someone changes the schedule for a procedure. Now you’re untangling a mess that never needed to exist. The worst part is the mental load: you’re constantly “holding” times in your head, re-checking availability, and trying not to sound annoyed while you chase a simple yes.
It adds up fast. Here’s where it breaks down in day-to-day clinic life.
- You end up checking Google Calendar over and over because patients reply on their own schedule.
- Double bookings happen when a slot looks free at 10:02 and disappears by 10:06.
- Alternatives take forever to propose because you’re manually scanning for open gaps.
- Record-keeping becomes an afterthought, so you’re piecing together who booked what from chat history.
The Fix: Telegram Chat That Books Into Google Calendar Automatically
This workflow acts like an appointment coordinator living inside Telegram. A patient messages the bot to request a booking, and the AI agent collects the needed details in a normal conversation (no clunky forms). Once it has a date and time, it checks your Google Calendar availability before anything gets confirmed. If the slot is open, it creates the booking in Google Calendar right away. If it’s not open, the workflow suggests alternative time slots so the patient can pick a workable option without you jumping in. After a successful booking, it appends the appointment details to Google Sheets so you have a clean, searchable log you can hand off to your team.
The workflow starts with an incoming Telegram chat, then uses an AI appointment coordinator backed by an OpenAI chat model and conversation memory. Next, Google Calendar tools verify availability and create the event. Finally, Google Sheets captures the final booking details for tracking.
What Changes: Before vs. After
| What This Eliminates | Impact You’ll See |
|---|---|
|
|
Real-World Impact
Say you handle about 15 booking requests a week through chat. Manually, each one usually takes roughly 10 minutes of messaging plus another 5 minutes of calendar checking and logging, so you’re at about 4 hours weekly. With this workflow, the patient chats with Telegram, the system checks Google Calendar instantly, and Google Sheets logging happens in the background. You might still spend a minute reviewing edge cases, but the routine bookings basically disappear from your to-do list.
Requirements
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram to collect booking requests via chat
- Google Calendar for availability checks and event creation
- Google Sheets to store a reliable appointment log
- OpenAI API key (get it from your OpenAI dashboard)
Skill level: Intermediate. You’ll connect accounts, choose the right calendar and sheet, and test a few booking conversations.
Need help implementing this? Talk to an automation expert (free 15-minute consultation).
The Workflow Flow
Telegram message triggers the workflow. A patient starts a chat (or replies in an existing thread), and n8n captures the message as the kickoff for the booking conversation.
The AI coordinator gathers details and remembers context. The agent uses an OpenAI chat model plus a conversation buffer, which means it can ask follow-up questions and keep track of what the patient already provided.
Google Calendar is checked before anything is confirmed. The workflow verifies the requested time slot, then either books it immediately or proposes alternatives when the time is taken.
Confirmed bookings are logged to Google Sheets. Once the event exists in Google Calendar, a row is appended to your sheet so staff can filter by date, provider, or appointment type later.
You can easily modify the questions the bot asks to match your intake process. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
Set up the workflow entry point that receives incoming chat sessions and hands them to the agent.
- Add the Incoming Chat Trigger node as the trigger for the workflow.
- Open Incoming Chat Trigger and keep default Options unless you need a custom chat configuration.
- Ensure Incoming Chat Trigger connects to Appointment AI Coordinator as shown in the execution flow.
Step 2: Connect Google Calendar and Google Sheets
Link the calendar and spreadsheet services used by the AI tools to check availability, book appointments, and log patient details.
- For Verify Calendar Slots, set Calendar to
[YOUR_EMAIL]and keep Resource ascalendar. - Set Time Min to
={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start_Time', ``, 'string') }}and Time Max to={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End_Time', ``, 'string') }}in Verify Calendar Slots. - For Create Calendar Booking, set Calendar to
[YOUR_EMAIL], Start to={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Start', ``, 'string') }}, and End to={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('End', ``, 'string') }}. - In Append Sheet Entry, set Document ID to
[YOUR_ID], Sheet Name to[YOUR_ID], and Operation toappend. - Map the columns in Append Sheet Entry to: Nom complet →
={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Nom_complet', ``, 'string') }}, Date / heure →={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Date___heure_', ``, 'string') }}, Numéro de telephone →={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('Num_ro_de_telephone', ``, 'string') }}. - Credential Required: Connect your googleCalendarOAuth2Api credentials for calendar access and your googleSheetsOAuth2Api credentials for spreadsheet access. These AI tools are attached to Appointment AI Coordinator, so add credentials at the parent node where required.
⚠️ Common Pitfall: Replace [YOUR_EMAIL] and [YOUR_ID] with your actual Google Calendar and Google Sheets identifiers, or the tools will fail to locate the resources.
Step 3: Set Up Appointment AI Coordinator
Configure the AI agent that orchestrates the conversation, availability checks, booking, and logging.
- Open Appointment AI Coordinator and review the System Message to confirm office hours, duration, and booking rules. Keep the dynamic date expression
{{ $now }}in place. - Connect OpenAI Dialogue Model as the language model and keep the Model set to
gpt-4o-mini. - Attach Conversation Buffer Memory as the memory tool with Session Key set to
={{ $('Incoming Chat Trigger').item.json.sessionId }}and Session ID Type set tocustomKey. - Credential Required: Connect your openAiApi credentials for OpenAI Dialogue Model. This model is used by Appointment AI Coordinator.
Tip: The Conversation Buffer Memory session key ensures each chat session stays isolated. If you change the trigger, update the expression accordingly.
Step 4: Configure Output and AI Tools
Confirm the agent can call the tools to verify availability, book the event, and log the booking details.
- Ensure Verify Calendar Slots, Create Calendar Booking, and Append Sheet Entry are connected as AI tools to Appointment AI Coordinator.
- Validate that Verify Calendar Slots and Create Calendar Booking point to the correct calendar and time fields via their AI expressions.
- Confirm Append Sheet Entry uses the defined column mappings for patient details and appointment time.
Step 5: Test and Activate Your Workflow
Validate the chat flow end-to-end before enabling the automation in production.
- Click Test Workflow and start a chat via Incoming Chat Trigger with a sample appointment request.
- Confirm Appointment AI Coordinator asks for name, phone, and preferred time, then checks availability before booking.
- Verify a calendar event is created by Create Calendar Booking and a row is appended by Append Sheet Entry.
- Once confirmed, toggle the workflow to Active for live use.
Watch Out For
- Google Calendar credentials can expire or need specific permissions. If things break, check the n8n Credentials panel and Google account access first.
- Time zones can quietly ruin scheduling. Confirm your n8n instance, Google Calendar, and the clinic’s “business hours” assumption all match before you go live.
- Default AI prompts are generic. Add your clinic rules early (appointment length, provider availability, what info you require) or you will be editing conversations forever.
Common Questions
About 30 minutes if your Google and Telegram accounts are ready.
Yes. You won’t write code, but you will connect accounts and choose the right calendar and Google Sheet.
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, which are usually pennies per conversation for typical scheduling chats.
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.
You can adjust the Appointment AI Coordinator’s instructions so it asks your exact intake questions (provider, reason for visit, insurance, anything). If you want longer or shorter appointments, change the Google Calendar booking settings used by the Create Calendar Booking tool. Many clinics also customize the “alternative times” behavior by narrowing business hours and adding buffer time between appointments.
Usually it’s a bot token issue or the bot isn’t allowed to receive the right updates. Regenerate your Telegram bot token if needed and re-save it in n8n credentials, then confirm the bot is added correctly and can receive messages. If the workflow triggers sometimes but not always, check Telegram privacy settings for the bot and confirm you’re testing in the same chat type (direct message vs group).
If you self-host n8n, there’s no execution limit (it depends on your server). On n8n Cloud, your plan sets the monthly execution cap, and this workflow typically uses one execution per booking conversation plus a few tool calls. In practice, most small clinics can handle normal booking volume comfortably on entry-level plans.
Often, yes, because this isn’t just “Telegram message in, calendar event out.” You need a real conversation, short-term memory, and branching logic for unavailable time slots, and n8n handles that kind of flow without turning into a brittle pile of zaps. It’s also easier to self-host if you want more control over patient messages. Zapier or Make can still work if you keep it simple, like collecting requests and forwarding them to staff for manual booking. If you’re on the fence, Talk to an automation expert and we’ll map it to your exact workflow.
This setup keeps your calendar clean, your log reliable, and your front desk out of the confirmation spiral. Set it up once, then let the workflow do the repetitive part.
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.
