Skip to main content

Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

Workflow preview

Workflow preview
100%
Sync check due dates from Google Sheets to Google Calendar with Telegram alerts preview
Open on n8n.io

1. Workflow Overview

Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all day events in Google Calendar, then posts a creation or update notice to a Telegram gro...

Best for

  • Project Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.googlesheetstrigger, n8n-nodes-base.if, n8n-nodes-base.googlecalendar, n8n-nodes-base.googlesheets, n8n-nodes-base.merge, n8n-nodes-base.aggregate, n8n-nodes-base.telegram

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Kristian.

Original n8n.io source

1.1 Workflow description

Title
Sync check due dates from Google Sheets to Google Calendar with Telegram alerts
Workflow name
Sync check due dates from Google Sheets to Google Calendar with Telegram alerts

Quick overview

This workflow watches a Google Sheets check inventory list and creates or updates matching all-day events in Google Calendar, then posts a creation or update notice to a Telegram group.

How it works

  1. Polls Google Sheets every hour for any updates in the “Check Inventory” sheet.
  2. Checks whether the updated row already contains a Google Calendar Event ID.
  3. If the Event ID is empty, searches Google Calendar for an existing event whose text matches the check number and backfills the found Event ID to Google Sheets.
  4. If no matching calendar event exists, creates an all-day Google Calendar event using the check date and details from the Google Sheets row, then writes the new Event ID back to the sheet.
  5. If an Event ID exists, fetches the corresponding Google Calendar event and compares its date, summary, and description to the latest Google Sheets values.
  6. When differences are detected, updates the Google Calendar event to match the sheet and sends a Telegram message summarizing the created or updated events.

Setup

  1. Connect credentials for Google Sheets (including Google Sheets Trigger), Google Calendar OAuth2, and a Telegram Bot API account.
  2. Replace YOUR_CHECK_INVENTORY_SHEET_ID in all Google Sheets nodes and ensure the “Check Inventory” sheet contains the required columns (including “Check Number” and “Event ID”).
  3. Set the target Google Calendar ID (for example [email protected] or a shared calendar ID) in the Google Calendar nodes.
  4. Replace YOUR_TELEGRAM_GROUP_CHAT_ID in the Telegram nodes and edit the message text to use the correct @mentions for your team.

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 - Sticky Note

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

Block 2 - Sticky Note1

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

Block 3 - Sticky Note2

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

Block 4 - Sticky Note3

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

Block 5 - Sticky Note4

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

Block 6 - Sticky Note5

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

Block 7 - Sticky Note6

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

Block 8 - Trigger on Inventory Update

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

Block 9 - Check If Event ID is Empty

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

Block 10 - Find Existing Calendar Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 11 - Verify Event Found

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

Block 12 - Update Sheet with Event ID

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 13 - Merge Event Paths

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 14 - Create Calendar Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 15 - Append Event ID to Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.7

Block 16 - Aggregate New Events

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

Block 17 - Notify New Event Created

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

Block 18 - Retrieve Event by ID

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 19 - Check for Event Changes

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

Block 20 - Update Calendar Event

Type / Role
n8n-nodes-base.googleCalendar - googleCalendar
Config choices
Version 1.3

Block 21 - Consolidate Event Updates

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

Block 22 - Notify Event Update Sent

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

3. Summary Table

Workflow Sync check due dates from Google Sheets to Google Calendar with Telegram alerts
Complexity advanced
Nodes 22
Categories Project Management
Author Kristian
Published 18 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16474/16474.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 Sync check due dates from Google Sheets to Google Calendar with Telegram alerts do?

Quick overview This workflow watches a Google Sheets check inventory list and creates or updates matching all day events in Google Calendar, then posts a creation or update notice to a Telegram gro...

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 Project Management use case.