I built an n8n workflow for collecting public Telegram channel posts into Google Sheets—for things like a news tracker or research feed.
The part I focused on was recovery: if collection succeeds but the Sheets step fails, you need a way to import those collected posts again.
Here’s how it works:
- An Apify Actor collects posts from readable public Telegram previews.
- n8n reads the resulting dataset and matches spreadsheet rows by post ID.
- If the Sheets step fails, you can supply the original run ID and retry that import without starting another collection.
In a live test, importing 34 posts twice left 34 unique rows. I also tested a missing destination tab, restored it, and successfully imported the original dataset.
Free workflow, setup guide, and 90-second captioned demo →
You’ll need n8n, an Apify account, and a Google Sheets connection. No Telegram login is required.
Costs and disclosure: I built and maintain the paid Apify Actor this workflow uses. The workflow download is free; the Actor charges $0.005 per collection run plus $0.001 per delivered post. For example, a run delivering 25 posts costs $0.03 in Actor events. n8n hosting and other platform charges may apply.
A few limits: public web previews only, no edit or deletion tracking, and one import writing to the sheet at a time. Row matching doesn’t protect against simultaneous writers.
If you already collect Telegram posts into Sheets, what causes you more trouble: setting up the connection, duplicate rows, or recovering missed imports?