Skip to content
ExpertEnterpriseEmail AutomationScheduled trigger32 nodes

Follow up with Telegram

Runs on a schedule across Telegram, Google Sheets and Notion, routes each kind of record down its own branch, then drops anything it has already handled. Built for newsletters, around a "Normalize Email Payload" step, in 32 documented nodes.

Follow up with leads with PostgreSQL and Telegram in real time. An original, ready-to-import n8n workflow built around the 'Drip Sequence' pattern for marketing & advertising. It runs on a schedule and orchestrates 32 nodes across Telegram, Google Sheets, Notion. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. The result is a hands-off process that just works.

Key benefits

  • Keeps Telegram and Google Sheets in step for newsletters, without anyone re-typing a row
  • Safe to re-run: records already in Telegram or Google Sheets are skipped, across all 32 nodes of this newsletters build
  • A failed Telegram or Google Sheets call is retried rather than dropped, at any of the 32 nodes in this newsletters build
  • Branches rejoin before Telegram, so a newsletters run reports once rather than 32 times
  • Every newsletters run leaves an audit row behind, alongside Telegram

Use cases

  • Teams keeping Telegram and Google Sheets aligned by hand for newsletters
  • Newsletters work where "Normalize Email Payload" is still a manual step before Telegram
  • Newsletters work that only reaches Telegram on a schedule, when someone remembers to start it

Integrations

TelegramGoogle SheetsNotionPostgreSQLSlackHTTP / REST APIAnthropic

Workflow preview (32 nodes)

The template's actual node layout and connections. Node parameters and credential slots unlock with the download.

Hourly ScheduleSchedule TriggerNormalize Email PayloadCodeScore the LeadCodeAssign Round-Robin OwnerCodeRoute by HeatSwitchHot → PostgreSQL + Inst…PostgresNotify Assigned OwnerSlackWarm → Drip via TelegramTelegramCold → Park in Nurture …NotionCombine Lead PathsMergeSerialize Run Output (C…Convert To FileArchive Row SnapshotGoogle SheetsEnrich with Reference D…Http RequestFold In Enrichment Fiel…SetLoad Previous SnapshotNotionCompute Drift vs Snapsh…CodeOffload to Post-Process…Execute WorkflowRecord Sub-workflow Res…Execution DataStamp Completion TimeDate TimePersist Run MetadataExecution DataFingerprint for Idempot…CodeDrop Already-Processed …Remove DuplicatesSave Execution MetadataExecution DataStamp Processing TimeDate TimeAlign Field NamesRename KeysSort Emails Newest FirstSortSummarize Run StatsSetAppend Audit Row (Postg…PostgresSend Summary to TelegramTelegramCapture Failure ContextSetEscalate Failure to Tel…TelegramPark in Dead-Letter Que…Google Sheets

What's inside (32 nodes)

A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.

CodeConvert To FileDate TimeExecute WorkflowExecution DataGoogle SheetsHttp RequestMergeNotionPostgresRemove DuplicatesRename KeysSchedule TriggerSetSlackSortSwitchTelegram

From download to running in 3 steps

  1. 1
    Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
  2. 2
    Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
  3. 3
    Activate. Run it once to test, then toggle Active. The automation is live.

What you'll learn

Architect level

The deepest tier - sub-workflow delegation, state snapshots, and full observability.

  • Checking for conversion before every step so the drip stops
  • Segmenting the audience up front
  • Moving data between PostgreSQL, Slack and Telegram in a single run

Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.

Common questions

What exactly do I get?

The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.

How do I import it into n8n?

In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.

Do I need anything else for it to work?

You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Telegram, Google Sheets, Notion, PostgreSQL, …). No coding is required.

What if it doesn't work for me?

If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.

Can I modify or resell it?

You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.

Original n8n workflow template created and owned by WorkflowCrate. After purchase you receive the ready-to-import JSON file and a license to use and adapt it in your own projects.