Skip to main content

Automate meeting scheduling through Telegram with Google Calendar & Notion CRM

Workflow preview

Workflow preview
100%
Automate meeting scheduling through Telegram with Google Calendar & Notion CRM preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Graceful Scheduler Bot — Client & Affiliate Booking Automation The Graceful Scheduler Bot transforms scheduling into an elegant, automated process. Clients and affiliates simply send a message i...

Best for

  • Support Chatbot automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.emailsend

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Shelly-Ann Davy.

Original n8n.io source

1.1 Workflow description

Title
Automate meeting scheduling through Telegram with Google Calendar & Notion CRM
Workflow name
Automate meeting scheduling through Telegram with Google Calendar & Notion CRM

💼 Graceful Scheduler Bot — Client & Affiliate Booking Automation

The Graceful Scheduler Bot transforms scheduling into an elegant, automated process.
Clients and affiliates simply send a /book message in Telegram, and the workflow manages everything:
conflict checks, calendar booking, confirmations, CRM logging, and reminders. ✨


🌸 Features

  • 📲 Telegram Intake: Accepts /book command with meeting type, date, time, and email.
  • 📅 Google Calendar Integration: Checks if the requested time is free and creates a 30-minute event.
  • 💌 Confirmations: Sends instant confirmation by Email and Telegram.
  • 🗂️ Notion CRM Log: Records details (Name, Email, Meeting Type, Date, Status).
  • Reminders: Sends polite reminders 24h before the meeting via Email and Telegram.

⚙️ Setup Instructions

  1. Telegram Bot:
    • Create a bot with BotFather
    • Add your token into n8n credentials
  2. Google Calendar:
    • Connect your account in n8n credentials
    • Use primary or specify your calendar ID
  3. Email Send Node:
    • Configure SMTP or Gmail OAuth
  4. Notion Database:
    • Create a database with properties:
      • Name (title)
      • Email (email)
      • Meeting Type (select)
      • Date (date)
      • Status (select)
    • Replace YOUR_NOTION_DATABASE_ID in the workflow
  5. Customize Messages:
    • Update confirmation + reminder copy to match your tone
  6. Test Example:
    /book client 2025-09-20 14:00 [email protected] Jane Doe

🧩 Node List

  • Telegram Trigger → listens for /book messages
  • Function (Parse Command) → extracts meeting type, date/time, email, name
  • IF Valid? → routes to help or booking flow
  • Google Calendar (Get Events) → checks for conflicts
  • IF Time Free? → prevents double booking
  • Google Calendar (Create Event) → books slot + invites guest
  • Email Send (Confirmation) → elegant confirmation email
  • Telegram (Confirmation) → graceful in-chat confirmation
  • Notion (Create Page) → logs details into CRM
  • Wait → pauses until 24h before meeting
  • Email Send (Reminder) → gentle email reminder
  • Telegram (Reminder) → in-chat reminder

🧪 Testing Tips

  • Start with a test booking command using today’s date/time.
  • Check Google Calendar → event should appear with guest invite.
  • Confirm both email and Telegram confirmations are sent.
  • Verify a new page is created in your Notion database.
  • Let the Wait node trigger → reminders should arrive 24h before.

🏷️ Tags

Automation, Scheduling, Calendars, CRM, Telegram, Notion


✨ With the Graceful Scheduler Bot, scheduling feels less like admin work and more like having your own digital assistant — polished, timely, and beautifully automated.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Setup Guide

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Configuration Instructions

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Manual Trigger

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 4 - Schedule Daily

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 5 - Settings

Type / Role
n8n-nodes-base.set - set
Config choices
Version 2

Block 6 - Get Today Date

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 7 - Query Notion

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.1

Block 8 - Calculate Days

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - IF Day 7

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 10 - IF Day 30

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 11 - IF Day 60

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 12 - Email Day 7

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2

Block 13 - Email Day 30

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2

Block 14 - Email Day 60

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2

Block 15 - Telegram Notify

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1

Block 16 - Testimonial Webhook

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 1

Block 17 - Parse Testimonial

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 18 - Notify Testimonial

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1

Block 19 - Respond

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1

3. Summary Table

Workflow Automate meeting scheduling through Telegram with Google Calendar & Notion CRM
Complexity advanced
Nodes 19
Categories Support Chatbot, AI Chatbot
Author Shelly-Ann Davy
Published 15 Sept 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8593/8593.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Automate meeting scheduling through Telegram with Google Calendar & Notion CRM do?

Graceful Scheduler Bot — Client & Affiliate Booking Automation The Graceful Scheduler Bot transforms scheduling into an elegant, automated process. Clients and affiliates simply send a message i...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Support Chatbot, AI Chatbot use case.