Notion + Telegram: launch follow ups sent on cue

Launch follow-ups fall apart in the boring moments. Someone forgets to check Notion, an email goes out late (or not at all), and your “smooth launch plan” turns into frantic catch-up.

Marketing managers feel it when the calendar is packed. A course creator feels it when they’re also support, sales, and content. Even agency owners end up chasing “did we send the 7‑day follow up?” This Notion Telegram followups automation keeps those sends on schedule and visible.

You’ll set up an n8n workflow that checks your Notion launch database, triggers the right email follow ups (7/30/60 days), and posts a Telegram status alert so the team always knows what happened.

How This Automation Works

Here’s the complete workflow you’ll be setting up:

n8n Workflow Template: Notion + Telegram: launch follow ups sent on cue

Click to explore

flowchart LR

    subgraph sg0["Manual Flow"]
        direction LR
        n0@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Trigger", pos: "b", h: 48 }
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
        n2@{ icon: "mdi:swap-vertical", form: "rounded", label: "Settings", pos: "b", h: 48 }
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Get Date"]
        n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Query Notion"]
        n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Calculate"]
        n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF Day 7", pos: "b", h: 48 }
        n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF Day 30", pos: "b", h: 48 }
        n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "IF Day 60", pos: "b", h: 48 }
        n9@{ icon: "mdi:message-outline", form: "rounded", label: "Email Day 7", pos: "b", h: 48 }
        n10@{ icon: "mdi:message-outline", form: "rounded", label: "Email Day 30", pos: "b", h: 48 }
        n11@{ icon: "mdi:message-outline", form: "rounded", label: "Email Day 60", pos: "b", h: 48 }
        n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Telegram Notify"]
        n3 --> n4
        n6 --> n9
        n2 --> n3
        n5 --> n6
        n5 --> n7
        n5 --> n8
        n7 --> n10
        n8 --> n11
        n9 --> n12
        n10 --> n12
        n11 --> n12
        n4 --> n5
        n0 --> n2
        n1 --> n2
    end

    subgraph sg1["Flow 2"]
        direction LR
        n13["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Webhook"]
        n14["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse"]
        n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/telegram.svg' width='40' height='40' /></div><br/>Notify Testimonial"]
        n16["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Respond"]
        n14 --> n15
        n13 --> n14
        n15 --> n16
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0,n1 trigger
    class n6,n7,n8 decision
    class n4,n13,n16 api
    class n3,n5,n14 code
    classDef customIcon fill:none,stroke:none
    class n3,n4,n5,n12,n13,n14,n15,n16 customIcon

Why This Matters: Launch follow ups slip when you’re busy

Most launches don’t fail because you didn’t plan. They wobble because the plan lives in too many places. Notion has the schedule, your email tool has the audience, Telegram has the internal chatter, and nobody has the mental space to keep them synced during a launch week. You might remember the Day 1 email, but Day 7 and Day 30 are where revenue gets recovered and testimonials get collected. Miss those, and you’re leaving results on the table without realizing it.

It adds up fast. Here’s where it breaks down.

Someone has to manually check Notion every day to see what’s due, and that habit falls apart the moment meetings pile up.
Follow up emails get sent late, which means fewer replies, fewer testimonials, and more “sorry, just seeing this” responses.
Internal visibility is weak, so you waste time asking if the message went out instead of moving to the next launch task.
One small date mistake in a database turns into a whole day of confusion because there’s no automated guardrail.

What You’ll Build: A milestone-based launch follow up system

This workflow turns your Notion launch database into a simple “source of truth” that actually triggers action. On a schedule (or on-demand), n8n generates the current date, pulls your launch items from Notion, and computes milestone timing like Day 7, Day 30, and Day 60. When an item matches a milestone, the workflow sends the correct follow up email automatically. After each send, it posts a Telegram status alert so you (and your team) can see what happened without digging through inboxes. There’s also an incoming webhook path that can capture a payload (like a testimonial submission) and immediately push an alert to Telegram.

The workflow starts with a scheduled trigger (daily is typical), then checks your Notion data against milestone rules. If a milestone hits, the matching email goes out and Telegram confirms it. Separately, a webhook can fire at any time to route inbound feedback to a Telegram channel.

What You’re Building

What Gets Automated

What You’ll Achieve

A daily (or manual) check of your Notion launch database for items due today.
Milestone calculations that decide if a 7-day, 30-day, or 60-day follow up should fire.
Email sends for each milestone, without you rebuilding the same campaign logic repeatedly.
Telegram alerts after each send, plus webhook-driven alerts for inbound events like testimonials.

Get back about 2 hours per launch week that usually disappears into checking, copying, and verifying.
Fewer missed sends because dates are checked consistently every day.
Cleaner internal communication since Telegram becomes the “proof” channel.
More predictable follow ups, which tends to lift replies and social sharing.
A calmer launch cadence, because the workflow nags the system, not your brain.

Expected Results

Say your launch has 20 scheduled follow ups sitting in Notion, and you normally spend maybe 5 minutes per item to check dates, find the right email draft, send it, then tell your team it’s done. That’s about 100 minutes of busywork spread across the week, and it’s also where mistakes sneak in. With this workflow, the daily trigger runs in the background, the right 7/30/60‑day emails fire automatically, and Telegram posts the receipt. You spend a few minutes reviewing exceptions, not chasing every task.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Notion for your launch database and schedule.
Email sending tool to deliver milestone follow ups (the workflow includes Send Email; many teams map this to Mailchimp).
Telegram Bot to post internal status alerts.
Notion API access (create an integration in Notion, then copy the secret).

Skill level: Beginner. You will connect credentials, paste a database ID, and tweak a few fields for your own follow up timing.

Want someone to build this for you? Talk to an automation expert (free 15-minute consultation).

Step by Step

A schedule (or manual run) kicks things off. The workflow can run daily via a Schedule Trigger, and it also includes a Manual Trigger for testing when you’re setting it up.

Your current date is generated, then Notion is checked. n8n creates a “today” value, calls Notion via an HTTP Request, and pulls launch items you’ve planned inside your database.

Milestones are computed and routed. A small code step calculates whether each record hits Day 7, Day 30, or Day 60, then three separate checks decide which follow up path should run.

Emails go out and Telegram confirms. The workflow sends the appropriate milestone email, then posts a Telegram status alert so you can see what sent (and when) without opening your email tool.

You can easily modify the milestone rules to match your launch plan (for example, Day 3 and Day 14 instead). See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Trigger Type

Set up the workflow’s entry points so it can run on demand, on a schedule, and from incoming webhook calls.

Open Manual Execution Start to enable manual test runs during setup.
Configure Scheduled Automation Trigger to define your production run cadence (e.g., daily or weekly).
Configure Incoming Webhook Trigger for inbound testimonial payloads and note its webhook URL for external integrations.

Use Manual Execution Start for initial validation, then rely on Scheduled Automation Trigger for ongoing automation.

Step 2: Connect Notion

Pull client data from Notion and prepare it for milestone checks.

Open Configure Defaults and set any default fields you need for downstream nodes.
Open Generate Current Date to create the reference date used in milestone calculations.
Open Notion Data Request and configure it to query your Notion database for active clients.
Credential Required: Connect your Notion API credentials in Notion Data Request.

⚠️ Common Pitfall: If Notion Data Request has no credentials, the workflow will return authorization errors and milestone checks will not run.

Step 3: Set Up Processing and Parallel Milestone Logic

Compute milestones and branch logic to determine which emails should be sent.

Open Compute Milestones to calculate the number of days since each client’s start date.
Confirm the execution flow: Compute Milestones outputs to both Check Day Seven and Check Day Thirty and Check Day Sixty in parallel.
Configure Check Day Seven, Check Day Thirty, and Check Day Sixty to evaluate the correct day thresholds.

Parallel checks ensure multiple milestone emails can be evaluated in a single run without waiting for other branches.

Step 4: Configure Output and Notification Nodes

Set up emails for each milestone and notifications for status and testimonials.

Configure Send 7-Day Email, Send 30-Day Email, and Send 60-Day Email with the subject and body for each milestone.
Credential Required: Connect your SMTP credentials in Send 7-Day Email, Send 30-Day Email, and Send 60-Day Email.
Configure Telegram Status Alert to post confirmations after each email is sent.
Credential Required: Connect your Telegram API credentials in Telegram Status Alert and Testimonial Alert.
Review the webhook flow: Incoming Webhook Trigger → Extract Payload → Testimonial Alert → Return Webhook Reply.

⚠️ Common Pitfall: Missing SMTP or Telegram credentials will cause email and alert nodes to fail silently during scheduled runs.

Step 5: Test and Activate Your Workflow

Validate each branch and then turn on automation for production use.

Click Execute Workflow on Manual Execution Start to run a test with sample Notion data.
Confirm that Send 7-Day Email, Send 30-Day Email, or Send 60-Day Email fire only when their respective conditions are met.
Verify that Telegram Status Alert receives messages after email sends, and that Testimonial Alert triggers on webhook calls.
Switch the workflow to Active to enable Scheduled Automation Trigger for ongoing production runs.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Notion credentials can expire or lack database permissions. If things break, check your Notion integration access to the specific database first.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.

Quick Answers

What’s the setup time for this Notion Telegram followups automation?

About 30 minutes if your Notion database is ready.

Is coding required for this Notion Telegram followups?

No. You’ll mostly connect accounts and map a few fields from Notion to your email and Telegram steps.

Is n8n free to use for this Notion Telegram followups workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Notion API usage (typically negligible) and your email provider costs.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I modify this Notion Telegram followups workflow for different use cases?

Yes, and you should. Most people adjust the milestone logic in the Compute Milestones code step, then update the Check Day Seven/Thirty/Sixty rules to match their cadence. You can also swap the Send Email steps to your preferred provider, and keep Telegram as the visibility layer. Another common tweak is filtering Notion records by Status (for example, only “To Do” items) so you never resend a follow up by accident.

Why is my Notion connection failing in this workflow?

Usually it’s permissions. Make sure your Notion integration has been invited to the specific database, then confirm the database ID is correct in the Notion Data Request HTTP step. If it used to work and suddenly doesn’t, regenerate the Notion secret and update the credential in n8n. Rate limits are possible, but for normal launch volumes it’s honestly uncommon.

What volume can this Notion Telegram followups workflow process?

For most small launches, it’s plenty. On n8n Cloud, the Starter plan covers a typical solo or small-team volume, and higher plans handle more. If you self-host, there’s no execution limit (it depends on your server). In practice, pulling a day’s worth of Notion items and checking milestones is quick, so the main constraint becomes your email provider’s sending limits.

Is this Notion Telegram followups automation better than using Zapier or Make?

Sometimes. This workflow uses conditional branching (7/30/60-day paths), code-based date logic, and a webhook side-route for inbound alerts, which n8n handles cleanly without turning into a mess of separate “Zaps” or scenarios. n8n also gives you a real self-host option when you don’t want usage-based pricing to creep up mid-launch. Zapier or Make can still be great if you only need one simple “Notion record created → send a message” automation and you want the quickest setup. If you’re unsure, Talk to an automation expert and we’ll help you pick the right approach.

Once this is running, follow ups stop being a daily mental tax. The workflow handles the repetitive timing and notifications so you can focus on the launch itself.

Notion + Telegram: launch follow ups sent on cue

How This Automation Works

n8n Workflow Template: Notion + Telegram: launch follow ups sent on cue

Why This Matters: Launch follow ups slip when you’re busy