n8n Telegram Broadcast Workflow w/ Google Sheets & Jitterflow

Broadcast to Telegram subscribers from Google Sheets—with rate limiting, retries, and daily cleanup

This n8n Telegram Broadcast workflow keeps your subscriber list in Google Sheets, sends scheduled broadcasts from a Broadcasts tab, and delivers messages through Jitterflow for rate-limited delivery with deduplication and a daily dead-letter queue (DLQ) cleanup.

What this workflow does

• Subscriber capture (Telegram trigger): When someone messages your Telegram bot, the workflow extracts chat details and the command.
• Update Google Sheets: It writes/updates the row in the Subscribers tab—marking Subscribed for /start and Unsubscribed for /stop—and replies back in Telegram.
• Broadcast processing (every 15 minutes): It reads the Broadcasts tab and selects the next row with Status set to Ready (or Sending).
• Message validation: It checks the broadcast text against Telegram’s 1–4,096 character limit. If invalid, the row is marked Needs edit; otherwise it updates the row to Sending with a broadcast ID.
• Rate-limited delivery via Jitterflow: For each Subscribed entry, it queues a sendMessage payload in Jitterflow using an idempotency key to prevent duplicate deliveries.
• Status updates in Google Sheets: After queueing, it marks the broadcast row as Sent and records how many subscribers were queued (including already-queued subscribers from earlier runs).
• Daily DLQ cleanup (8:00): It lists unresolved Jitterflow DLQ entries, marks subscribers as Blocked or Chat not found (based on entries and whether they exist in Google Sheets), and resolves the DLQ items.

Use cases

• Send recurring Telegram announcements managed entirely through a Google Sheets UI.
• Maintain accurate subscriber states (/start//stop) without manual spreadsheet editing.
• Safely broadcast at scale with deduplication, rate limiting, and automatic handling of blocked or missing chats.

Technical details

• n8n nodes/logic: if, set, limit, filter, switch, Telegram.
• Integrations: Telegram bot (including @BotFather token credential in n8n), Google Sheets tabs (“Subscribers”, “Broadcasts”), and Jitterflow for delivery control, retries, and DLQ resolution.