One-way sync between Telegram, Notion, Google Drive, and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on Telegram events (message). Along the way it connects Telegram, Notion, Google Drive and Google Sheets. It also calls api.imgbb.com and api.notion.com over HTTP.
How it runs
Trigger: On Telegram events (message).
- 🔀 Content Type Router (Switch): routes items into 3 branches
- 📥 Download Telegram Image (Telegram): work with file
- 📝 Add Text to Notion (Notion): work with block
- 📥 Download Telegram File (Telegram): work with file
- 🔄 Convert to Base (Extract from File): extracts data from a file (binary to propery)
- ✅ Send Completion Message (Telegram): uses Telegram
- ☁️ Upload to Google Drive (Google Drive): uses Google Drive
- 🌐 Upload to ImgBB (HTTP Request): calls api.imgbb.com (POST)
- 📊 Record in Google Sheets (Google Sheets): append
- 📝 Add Image to Notion (HTTP Request): calls api.notion.com (PATCH)
Services it uses
HTTP calls to: api.imgbb.com, api.notion.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Telegram Trigger
n8n-nodes-base.telegramTrigger - Switch
n8n-nodes-base.switch - Telegram
n8n-nodes-base.telegram - Extract from File
n8n-nodes-base.extractFromFile - HTTP Request
n8n-nodes-base.httpRequest - Notion
n8n-nodes-base.notion - Google Drive
n8n-nodes-base.googleDrive - Google Sheets
n8n-nodes-base.googleSheets
From the author
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…