Notion to Telegram, milestone emails sent on cue

If you’ve ever promised “we’ll follow up in a week” and then… didn’t, you already know the damage. Milestone emails slip, someone sends a duplicate, and your onboarding feels messy even when your work is solid.

This Notion Telegram automation hits when you’re juggling real clients and real deadlines. A service business owner feels it when onboarding gets chaotic. A lifecycle marketer feels it when “Day 7” turns into “whenever.” A small agency lead feels it when the team can’t agree on what was sent.

You’ll set up an n8n workflow that checks your Notion contact records, sends the right milestone email (Day 7, 30, or 60), and posts a Telegram ping so you always know what went out.

How This Automation Works

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

n8n Workflow Template: Notion to Telegram, milestone emails sent on cue

Click to explore

flowchart LR

    subgraph sg0["Manual Start Flow"]
        direction LR
        n1@{ icon: "mdi:play-circle", form: "rounded", label: "Manual Start", pos: "b", h: 48 }
        n2@{ icon: "mdi:play-circle", form: "rounded", label: "Morning Schedule Trigger", 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/>Compute Current 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/>Retrieve Notion Records"]
        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/>Derive Milestone Days"]
        n6@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Day 7", pos: "b", h: 48 }
        n7@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Day 30", pos: "b", h: 48 }
        n8@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Check Day 60", pos: "b", h: 48 }
        n9@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch 7-Day Email", pos: "b", h: 48 }
        n10@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch 30-Day Email", pos: "b", h: 48 }
        n11@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch 60-Day Email", 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 Alert"]
        n6 --> n9
        n7 --> n10
        n8 --> n11
        n2 --> n3
        n1 --> n3
        n3 --> n4
        n9 --> n12
        n10 --> n12
        n11 --> n12
        n4 --> n5
        n5 --> n6
        n5 --> n7
        n5 --> n8
    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/>Testimonial Intake 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/>Extract Testimonial Data"]
        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/>Telegram Testimonial Notice"]
        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/>Return Webhook Reply"]
        n13 --> n14
        n15 --> n16
        n14 --> n15
    end

    subgraph sg2["Flow 3"]
        direction LR
        n0@{ icon: "mdi:swap-vertical", form: "rounded", label: "Utility: Setup Variables", pos: "b", h: 48 }
    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 n1,n2 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: Milestone follow-ups get missed (or doubled)

Milestone messaging sounds simple until it lives in a dozen places. A Notion database holds your contacts, a Gmail draft holds your “Day 7 check-in,” and a sticky note says “ask for a testimonial around Day 60.” Then Monday happens. You forget to check Notion, or you check it but don’t remember who needs what, or you send the email and don’t tell anyone on the team. The result is quiet churn: leads go cold, new customers feel ignored, and your “onboarding system” becomes a game of catch-up.

It adds up fast. Here’s where it breaks down in day-to-day work.

You end up scanning Notion records manually, which is slow and easy to misread when you’re in a rush.
People get the wrong message at the wrong time because “Day 30” depends on someone remembering to do the math.
Teams lose visibility since emails are sent from one inbox, and nobody knows what actually went out.
Testimonial requests get postponed until it feels awkward, even though the timing was perfect weeks earlier.

What You’ll Build: Notion milestones that send emails and Telegram alerts

This workflow turns your Notion contact list into a timed follow-up engine. It runs on a schedule (with an optional manual “run now” button), calculates today’s date, then pulls your contact records from Notion via an HTTP request. Next, it figures out how many days it has been since each contact’s start date, and checks whether they’ve hit a milestone like Day 7, Day 30, or Day 60. When a milestone matches, n8n sends the correct email automatically. Right after that, it posts a Telegram alert so you and your team have a clear paper trail of what was sent and when.

There’s also a second track: a testimonial intake webhook. When someone submits a testimonial, the workflow extracts the details and sends a Telegram notice, then replies to the webhook so your form (or tool) gets a clean success response.

What You’re Building

What Gets Automated

What You’ll Achieve

A scheduled daily run that checks Notion contacts for milestone timing.
Date math and milestone detection (Day 7, Day 30, Day 60) without spreadsheets or manual counting.
Automatic email sending for each milestone using n8n’s email node.
Telegram notifications when milestone emails or testimonials are received.

Save about 2 hours a week compared to manual checking and sending.
Consistent onboarding touchpoints even when you’re busy or away.
Fewer “Did we already email them?” moments because Telegram becomes your audit log.
Cleaner handoffs inside your team since everyone sees the same alerts.
More timely testimonial collection, when customers are still excited.

Expected Results

Say you onboard 10 new clients a month and you send three milestone emails each (Day 7, 30, and 60). Manually, that’s about 5 minutes to check Notion, 5 minutes to find the right template, and a couple minutes to log it or message the team, so roughly 10 minutes per email (around 5 hours a month). With this workflow, you spend about 10 minutes setting up the templates once, then the weekly effort drops to a quick glance at Telegram. Most weeks, that’s basically zero.

Before You Start

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Notion to store contacts and start dates.
Telegram to receive “email sent” notifications.
Notion integration token (create it in Notion Integrations).

Skill level: Intermediate. You’ll connect accounts, add an API token, and map a few fields like start date and email address.

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

Step by Step

A scheduled (or manual) run kicks things off. The workflow can start from a morning schedule trigger for “set it and forget it,” and it also includes a manual trigger for testing or catch-up runs.

Today’s date gets calculated. A small code step computes the current date so the rest of the logic can compare “start date” vs. “right now” in a consistent way.

Notion records are fetched and evaluated. n8n retrieves your Notion contact records via HTTP request, then a code step derives milestone day counts and routes each contact through checks for Day 7, Day 30, and Day 60.

Emails go out and Telegram gets the receipt. When a contact hits a milestone, n8n sends the appropriate email and immediately posts a Telegram alert so you can see the send event without digging through inboxes.

You can easily modify the milestone days to match your own onboarding timeline based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Schedule Trigger

Set up the time-based trigger and the manual test trigger that both start the milestone email flow.

Add the Morning Schedule Trigger node and define your preferred schedule (e.g., daily at a specific time).
Keep the Manual Start node connected to Compute Current Date for ad‑hoc testing.
Ensure both Morning Schedule Trigger and Manual Start connect to Compute Current Date.

Tip: Use Manual Start for dry runs before enabling the schedule in production.

Step 2: Configure the Webhook Trigger

Set up the webhook pathway for incoming testimonials, which runs independently from the scheduled email flow.

Open Testimonial Intake Webhook and copy the Production URL to your testimonial form or source system.
Confirm Testimonial Intake Webhook is connected to Extract Testimonial Data, then to Telegram Testimonial Notice, and finally to Return Webhook Reply.

⚠️ Common Pitfall: The webhook will not respond unless Return Webhook Reply stays connected at the end of this branch.

Step 3: Connect Notion

Configure the Notion data source used to determine client milestones.

Open Retrieve Notion Records and configure the API request to your Notion database.
Credential Required: Connect your notionApi credentials in Retrieve Notion Records.
Verify Compute Current Date outputs to Retrieve Notion Records.

⚠️ Common Pitfall: If Notion returns empty data, check that your database access permissions are shared with the connected integration.

Step 4: Set Up Processing Nodes

Compute dates, derive milestone logic, and split the flow into parallel checks for 7-, 30-, and 60-day messaging.

Configure Utility: Setup Variables to define any static values or defaults used in the workflow.
Implement date calculations in Compute Current Date and feed the results into Retrieve Notion Records.
Use Derive Milestone Days to compute days since onboarding from Notion data.
Ensure Derive Milestone Days outputs to Check Day 7, Check Day 30, and Check Day 60 in parallel.

Tip: Derive Milestone Days outputs to both Check Day 7 and Check Day 30 and Check Day 60 in parallel, so verify each IF condition is mutually exclusive to avoid multiple emails.

Step 5: Configure Output/Action Nodes

Send milestone emails and notify the team in Telegram for each successful dispatch.

Configure Dispatch 7-Day Email, Dispatch 30-Day Email, and Dispatch 60-Day Email with the appropriate recipients, subject lines, and message bodies.
Credential Required: Connect your smtp credentials in each email node: Dispatch 7-Day Email, Dispatch 30-Day Email, and Dispatch 60-Day Email.
Connect each email node to Telegram Alert to send a delivery notification.
Credential Required: Connect your telegramApi credentials in Telegram Alert and Telegram Testimonial Notice.

⚠️ Common Pitfall: If Telegram messages fail, ensure the bot is added to the target chat and has permission to post.

Step 6: Test & Activate Your Workflow

Run end-to-end tests for both the scheduled email flow and the testimonial webhook before activating.

Click Execute Workflow using Manual Start to validate Compute Current Date, Retrieve Notion Records, and the milestone checks.
Trigger Testimonial Intake Webhook using a sample payload and verify Telegram Testimonial Notice plus a response from Return Webhook Reply.
Confirm that a successful run results in an email from the appropriate Dispatch node and a follow-up Telegram Alert.
Turn on the workflow by setting the toggle to Active once tests pass.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Troubleshooting Tips

Notion credentials can expire or need specific permissions. If things break, check your Notion Integration token access and the database share settings 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 automation?

About 30 minutes if your Notion database is ready.

Is coding required for this milestone follow-up automation?

No. You’ll mostly connect Notion and Telegram, then map fields like email and start date.

Is n8n free to use for this Notion Telegram automation 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 and email provider costs (usually $0 if you’re using what you already have).

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 automation workflow for different use cases?

Yes, and you should. You can change the Day 7/30/60 checks in the “Check Day 7/30/60” IF nodes, or adjust the milestone calculation in the “Derive Milestone Days” code step. Common customizations include adding a Day 1 welcome email, sending Slack instead of Telegram, and filtering contacts by plan type so VIP customers get different messaging.

Why is my Notion connection failing in this workflow?

Usually it’s an integration token or database permissions issue. Confirm the Notion database is shared with your integration, then regenerate the token if needed and update the HTTP Request headers in n8n. If it fails only sometimes, you may be hitting a Notion rate limit when pulling a lot of records at once, so add pagination or narrow the query to “active onboarding” contacts only. Also double-check date formats, because an invalid start date can make the milestone calculation crash.

What volume can this Notion Telegram automation workflow process?

A few thousand contacts is typically fine as long as your Notion query is filtered, because the heavy work is simple date checks and a small number of emails.

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

Often, yes, if you care about control and transparency. n8n makes it easier to run “one workflow, multiple branches” for Day 7 vs. Day 30 vs. Day 60 without paying extra for every path. You also get a real self-hosting option, which matters when you want unlimited runs or stricter data handling. Zapier and Make can still do this, but the logic tends to sprawl across filters and scenarios, and it’s harder to see the full picture later. If you’re unsure, Talk to an automation expert and get a straight recommendation for your setup.

Once this is live, your onboarding stops depending on memory. The workflow sends the right email, then tells you it happened, so you can get back to the work that actually needs you.

Notion to Telegram, milestone emails sent on cue

How This Automation Works

n8n Workflow Template: Notion to Telegram, milestone emails sent on cue

Why This Matters: Milestone follow-ups get missed (or doubled)