Skip to main content

One-way sync between Telegram, Notion, Google Drive, and Google Sheets

Workflow preview

Workflow preview
100%
One-way sync between Telegram, Notion, Google Drive, and Google Sheets preview
Open on n8n.io

Important notice

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

1. Workflow Overview

One way sync between Telegram, Notion, Google Drive, and Google Sheets Who is this for? This workflow is perfect for productivity focused teams, remote workers, virtual assistants, and digital know...

Best for

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

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.telegramtrigger, n8n-nodes-base.switch, n8n-nodes-base.telegram, n8n-nodes-base.extractfromfile, n8n-nodes-base.httprequest, n8n-nodes-base.notion, n8n-nodes-base.googledrive

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
One-way sync between Telegram, Notion, Google Drive, and Google Sheets
Workflow name
One-way sync between Telegram, Notion, Google Drive, and Google Sheets

One-way sync between Telegram, Notion, Google Drive, and Google Sheets

Who is this for?

This workflow is perfect for productivity-focused teams, remote workers, virtual assistants, and digital knowledge managers who receive documents, images, or notes through Telegram and want to automatically organize and store them in Notion, Google Drive, and Google Sheets—without any manual work.

What problem is this workflow solving?

Managing Telegram messages and media manually across different tools like Notion, Drive, and Sheets can be tedious. This workflow automates the classification and storage of incoming Telegram content, whether it’s a text note, an image, or a document. It saves time, reduces human error, and ensures that media is stored in the right place with metadata tracking.

What this workflow does

  • Triggers on a new Telegram message using the Telegram Trigger node.
  • Classifies the message type using a Switch node:
    • Text messages are appended to a Notion block.
    • Images are converted to base64, uploaded to imgbb, and then added to Notion as toggle-image blocks.
    • Documents are downloaded, uploaded to Google Drive, and the metadata is logged in Google Sheets.
  • Sends a completion confirmation back to the original Telegram chat.

Setup

  1. Telegram Bot: Set up a bot and get the API token.
  2. Notion Integration:
    • Share access to your target Notion page/block.
    • Use the Notion API credentials and block ID where content should be appended.
  3. Google Drive & Sheets:
    • Connect the relevant accounts.
    • Select the destination folder and spreadsheet.
  4. imgbb API: Obtain a free API key from imgbb.

Replace placeholder credential IDs and asset URLs as needed in the imported workflow.

How to customize this workflow to your needs

  • Change Storage Locations:
    • Update the Notion block ID or Google Drive folder ID.
    • Switch Google Sheet to log in a different file or sheet.
  • Add More Filters:
    • Use additional Switch rules to handle other Telegram message types (like videos or voice messages).
  • Modify Response Message:
    • Personalize the Telegram confirmation text based on the file type or sender.
  • Use a different image hosting service if you don’t want to use imgbb.

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 - Main Description

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

Block 2 - 📱 Telegram Message Trigger

Type / Role
n8n-nodes-base.telegramTrigger - telegramTrigger
Config choices
Version 1.1

Block 3 - 🔀 Content Type Router

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

Block 4 - Image Path Description

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

Block 5 - 📥 Download Telegram Image

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

Block 6 - 🔄 Convert to Base64

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

Block 7 - 🌐 Upload to ImgBB

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

Block 8 - 📝 Add Image to Notion

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

Block 9 - Text Path Description

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

Block 10 - 📝 Add Text to Notion

Type / Role
n8n-nodes-base.notion - notion
Config choices
Version 2.2

Block 11 - File Path Description

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

Block 12 - 📥 Download Telegram File

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

Block 13 - ☁️ Upload to Google Drive

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 14 - 📊 Record in Google Sheets

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

Block 15 - Completion Description

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

Block 16 - ✅ Send Completion Message

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

3. Summary Table

Workflow One-way sync between Telegram, Notion, Google Drive, and Google Sheets
Complexity advanced
Nodes 16
Categories File Management
Author Lakshit Ukani
Published 26 May 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4404/4404.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 One-way sync between Telegram, Notion, Google Drive, and Google Sheets do?

One way sync between Telegram, Notion, Google Drive, and Google Sheets Who is this for? This workflow is perfect for productivity focused teams, remote workers, virtual assistants, and digital know...

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