Telegram to Google Calendar, scheduling without tab hops
Calendar admin sounds simple until you’re doing it mid-call, between meetings, or while your phone is buzzing. You jump from chat to Google Calendar, copy details, fix time zones, then second-guess if you saved it.
This is where Telegram calendar automation makes a real difference. Founders feel it when every interruption breaks focus. Client-facing teams feel it when you need an instant “Yes, you’re booked” reply. And assistants get stuck doing the same scheduling clicks all day.
This n8n workflow turns Telegram into a Google Calendar assistant. You’ll see how it works, what you need, and the outcomes you can expect once it’s running.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Telegram to Google Calendar, scheduling without tab hops
flowchart LR
subgraph sg0["Incoming Chat Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Incoming Chat Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Dialogue Model", pos: "b", h: 48 }
n2@{ icon: "mdi:memory", form: "rounded", label: "Conversation Window Memory", pos: "b", h: 48 }
n3@{ icon: "mdi:location-exit", form: "rounded", label: "Calendar Events Lookup", pos: "b", h: 48 }
n4@{ icon: "mdi:location-exit", form: "rounded", label: "Calendar Event Creator", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "Calendar Assistant Agent", pos: "b", h: 48 }
n1 -.-> n5
n2 -.-> n5
n0 --> n5
n3 -.-> n5
n4 -.-> n5
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 n5 ai
class n1 aiModel
class n2 ai
The Problem: Scheduling Gets Slow (and Error-Prone) in Chat
You’re already having the conversation in Telegram, but the action happens somewhere else. So you context-switch, open Google Calendar, scan for conflicts, create an event, then return to chat to confirm. It’s not hard work. It’s fragile work. One wrong date format, an AM/PM mistake, or a missed conflict check and you’ve created a small fire you’ll put out later. Multiply that by a week of “Can you do Tuesday?” messages and it’s honestly exhausting.
It adds up fast. Here’s where it breaks down in real life:
- Checking availability manually takes a few minutes each time, especially when you’re scanning multiple days.
- Event details get copied incorrectly, so you end up resending confirmations or moving meetings after the fact.
- You delay replies because you want to “check the calendar later,” and the slot gets taken.
- Repeating the same calendar steps drains attention, which means less energy for the work that actually pays.
The Solution: A Telegram-Based Google Calendar Assistant
This workflow gives you a simple AI agent inside n8n that can read a Telegram message and either create a Google Calendar event or retrieve upcoming events. You message it like you would a human assistant: “Book a call with Sam on Friday at 2pm for 30 minutes” or “What’s on my calendar tomorrow?” Behind the scenes, the agent uses an OpenAI chat model to understand the request, keeps short-term conversational context with memory, and then calls Google Calendar tools to do the real work. The final result comes back as a reply in Telegram, so you can confirm details without leaving the chat.
The workflow starts with an incoming Telegram chat trigger. Then the AI agent interprets your intent, checks Google Calendar when needed, and either returns availability details or creates the event for you. You stay in one place, which means fewer delays and fewer “wait, did I book that?” moments.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you handle scheduling for five meetings a week through Telegram. Manually, each one usually takes about 10 minutes (check availability, create the event, copy the invite details, confirm in chat), which is close to an hour weekly. With this workflow, you send a single message that takes maybe 30 seconds, then wait for the assistant’s reply and confirmation. Even if you budget a couple minutes for review, you’re still cutting the effort down to around 10 minutes total for the week’s scheduling.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Telegram to send requests and receive replies.
- Google Calendar to store and retrieve events.
- OpenAI API Key (get it from your OpenAI account dashboard).
Skill level: Beginner. You’ll connect accounts, paste an API key, and test with 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 kicks it off. You send a natural-language request in Telegram, like “Create a meeting tomorrow at 11” or “What’s on Friday?” The workflow listens for new incoming chat messages.
The assistant interprets intent with AI. The OpenAI chat model helps the agent figure out what you mean, pull out dates and times, and decide which action is required. This is where “tool calling” matters: the model doesn’t just chat, it can trigger calendar actions.
Short-term memory keeps the conversation coherent. The workflow uses a conversation window memory so follow-ups like “make it 30 minutes” still make sense. You get a more natural back-and-forth instead of rigid commands.
Google Calendar does the real work. If you’re checking availability, the calendar lookup tool retrieves relevant events. If you’re booking, the event creator tool adds the meeting to Google Calendar and returns details you can confirm in chat.
You can easily modify what the assistant “counts” as a valid request, and how it formats confirmations, based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Chat Trigger
This workflow begins when a chat message arrives, which is then passed directly to the agent.
- Add the Incoming Chat Trigger node as the trigger.
- Keep default options unless you need custom webhook behaviors.
- Confirm the execution flow: Incoming Chat Trigger → Calendar Assistant Agent.
Step 2: Connect Google Calendar
The agent uses two Google Calendar tools for retrieval and event creation. These tools require Google Calendar credentials and are attached as AI tools to the agent.
- Open Calendar Events Lookup and select the calendar to query.
- Set Operation to
getAlland keep Tool Description asUse this tool when you’re asked to retrieve events data. - Set Time Min to
={{ $fromAI('start_date') }}and Time Max to={{ $fromAI('end_date') }}. - Open Calendar Event Creator and select the target calendar.
- Set Start to
={{ $fromAI('start_date') }}and End to={{ $fromAI('end_date') }}. - In Additional Fields, set Summary to
={{ $fromAI('event_title') }}and Description to={{ $fromAI('event_description') }}. - Credential Required: Connect your googleCalendarOAuth2Api credentials in both Calendar Events Lookup and Calendar Event Creator.
⚠️ Common Pitfall: If the calendar is not selected in either tool, the agent will fail to read or write events.
Step 3: Set Up the AI Agent and Memory
The agent interprets chat input, calls Google Calendar tools, and uses memory to maintain conversation context.
- Open Calendar Assistant Agent and set Text to
={{ $json.chatInput }}. - In System Message, keep the provided assistant instructions to guide event creation and retrieval logic.
- Connect OpenAI Dialogue Model to Calendar Assistant Agent as the language model.
- Credential Required: Connect your openAiApi credentials in OpenAI Dialogue Model.
- Connect Conversation Window Memory to Calendar Assistant Agent as memory to preserve context.
Step 4: Configure Output Actions
The agent will choose between retrieving events or creating new ones based on user intent, using the attached tools.
- Ensure both Calendar Events Lookup and Calendar Event Creator are connected to Calendar Assistant Agent as AI tools.
- Verify tool descriptions:
Use this tool when you’re asked to retrieve events data.andUse this Google Calendar tool when you are asked to create an event. - Confirm Use Default Reminders is set to
falsein Calendar Event Creator if you plan to control reminders manually.
Step 5: Test and Activate Your Workflow
Test the workflow to ensure the agent correctly interprets chat input and creates or retrieves events.
- Click Execute Workflow and send a chat message like “Create a meeting tomorrow at 10am for 1 hour.”
- Confirm the agent requests missing details and then triggers Calendar Event Creator with populated fields.
- Test retrieval with a prompt like “Show me my events for next week” and confirm Calendar Events Lookup runs.
- When successful, toggle the workflow to Active to accept live chat requests.
Common Gotchas
- Google Calendar credentials can expire or need specific permissions. If things break, check the connected account and scopes in n8n’s Credentials area first.
- If your Telegram bot isn’t responding, it’s usually a chat ID or bot token issue. Verify the Telegram credential in n8n and confirm your bot can read messages in the chat you’re testing.
- Default AI instructions are polite but generic. Add your preferred date format, time zone rules, and confirmation style early or you’ll be correcting little things constantly.
Frequently Asked Questions
About 30 minutes if your accounts are ready.
No. You’ll mostly connect credentials and test a few messages.
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 usage costs, which are usually a few cents for light weekly 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, and you should. Adjust the instructions given to the Calendar Assistant Agent so it always confirms the time zone, meeting length, and title format before creating events. You can also tweak the memory window if you want shorter or longer context, which changes how it handles follow-up messages like “make it next week instead.”
Usually the bot token is wrong, expired, or saved under the wrong n8n credential. Double-check the Telegram credential in n8n, then confirm the bot is allowed to read messages in the chat you’re testing (group permissions trip people up). If it works in one chat but not another, it’s almost always a chat context issue, not the workflow logic.
On n8n Cloud Starter, you can handle thousands of executions per month, which is plenty for most small teams. If you self-host, there’s no platform execution cap; it depends on your server. In practice, this workflow can comfortably handle many messages per minute, but OpenAI rate limits and Google API quotas become the real ceiling if you push volume.
Often, yes, because this is not a simple “message in, event out” zap. You’re using an AI agent with memory and tool calling, which needs branching logic and richer control than most basic automations. n8n also gives you a self-hosted path, so you’re not paying per tiny step as you scale. Zapier or Make can still be fine if you only want a rigid form-style command and you don’t care about conversation. If you’re unsure, Talk to an automation expert and describe your exact scheduling flow.
Once this is set up, your calendar stops being a separate chore you “get to later.” The workflow handles the repetitive scheduling loop so you can stay in the conversation and move faster.
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.
