This workflow follows the Google Drive → Telegram recipe pattern — see all workflows that pair these two integrations.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

My workflow 6. Uses telegramTrigger, telegram, googleDrive, dataTable. Event-driven trigger; 6 nodes.

Source: https://github.com/Hydralisk-zerg/first-project-n8n/blob/ee2608a989b3d0e1ecf9b16b6a752e3f3b8789de/files/workflows/E42M4trw91JP6TMI-My_workflow_6.json — original creator credit. Request a take-down →

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Telegram B-1 (Variant A): submit -> finalize in n8n. Uses telegramTrigger, telegram, googleDrive, dataTable. Event-driven trigger; 43 nodes.

Telegram Trigger, Telegram, Google Drive +2

Slack & Telegram

Telegram B-1 (Variant A): create sheet + send Submit button. Uses telegramTrigger, telegram, googleDrive, dataTable. Event-driven trigger; 14 nodes.

Telegram Trigger, Telegram, Google Drive +1

Slack & Telegram

N8N Complete Final. Uses telegramTrigger, dataTable, telegram, mqtt. Event-driven trigger; 58 nodes.

Telegram Trigger, Data Table, Telegram +3

Slack & Telegram

TextMain. Uses telegramTrigger, stopAndError, telegram, httpRequest. Event-driven trigger; 56 nodes.

Telegram Trigger, Stop And Error, Telegram +2

Slack & Telegram

Telegram B-1 (Variant A): create + submit (single webhook). Uses telegramTrigger, telegram, googleDrive, httpRequest. Event-driven trigger; 42 nodes.

Telegram Trigger, Telegram, Google Drive +1