Notion + Telegram: follow ups that never slip
Your follow-ups start with good intentions. Then a client reply comes in, a renewal date slides by, and suddenly you’re digging through Notion pages trying to remember who needed a nudge.
This hits agency owners and account managers hardest. But consultants running on referrals feel it too. With Notion Telegram followups automation, your Day 7, Day 30, and Day 60 check-ins go out on time, and you get a Telegram alert for every message sent.
Below you’ll see how the workflow runs daily, how it decides who gets emailed, and what you can tweak so it matches your tone and timing.
The Problem: Follow-Ups Get Forgotten (Even With a CRM)
Most teams don’t lose renewals because they’re bad at service. They lose them because the follow-up system lives in someone’s head, a Notion view, and maybe a calendar reminder that gets snoozed three times. You tell yourself you’ll check your “Follow-ups” database every morning. Then the day fills up. A week passes. Now you’re sending an awkward “just circling back” message that should have gone out days ago. It’s not just time wasted. It’s trust and momentum leaking out, quietly.
It adds up fast. Here’s where it breaks down in real life:
- You have to manually calculate when Day 7 or Day 30 is for every client, and that mental math gets old.
- Notion reminders are easy to ignore because they don’t land where you actually react (like Telegram).
- One missed follow-up can stall a renewal conversation for weeks, especially with quiet clients.
- You lose the “paper trail” of what was sent and when, so you hesitate and send less.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Notion + Telegram: follow ups that never slip
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 Daily", 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 Today 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 Days"]
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"]
n6 --> n9
n2 --> n3
n7 --> n10
n8 --> n11
n9 --> n12
n10 --> n12
n11 --> n12
n4 --> n5
n5 --> n6
n5 --> n7
n5 --> n8
n3 --> n4
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/>Testimonial 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 Testimonial"]
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
n15 --> n16
n13 --> n14
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
The Solution: Timed Notion Follow-Ups + Telegram Proof
This workflow runs automatically every day (or whenever you manually trigger it) and checks your Notion database for records that are due a follow-up. It pulls the list of contacts, calculates how many days it’s been since the relevant date, and then routes each person into the right message path. Day 7 gets one email, Day 30 gets another, Day 60 gets a final check-in. After each email is sent, you get a Telegram alert so you know it happened and can jump in if a reply comes back. There’s also a separate webhook path for testimonials or reviews, which posts a Telegram notice when feedback arrives.
The workflow starts with a daily schedule trigger and loads defaults like your Notion database ID and email settings. Then it fetches today’s date, retrieves Notion records via an HTTP request, computes day offsets, and checks Day 7, Day 30, and Day 60 conditions. When a condition matches, it sends the right email and logs the send by notifying you in Telegram.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you manage 40 active client or partner records in Notion. Manually, even a “quick check” takes maybe 3 minutes per record once you open pages, check dates, and decide what to send, so you’re looking at about 2 hours each week just to keep follow-ups from slipping. With this workflow, the daily run is automatic: you spend about 5 minutes up front setting your templates and database fields, then you only jump in when Telegram pings you that something was sent (or when a testimonial arrives). That’s a lot less mental load.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Notion for your follow-up database records.
- Telegram to receive send alerts and notices.
- Email account (SMTP or Gmail OAuth) (configure inside n8n credentials)
Skill level: Intermediate. You’ll paste a Notion database ID, map a few fields, and test with a small set of records.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A daily (or manual) trigger kicks it off. The workflow can run on a schedule every morning, and there’s also a manual trigger for testing so you don’t have to wait a day to see results.
Notion records are pulled and evaluated. n8n retrieves the relevant Notion database entries via an HTTP request, then a short code step computes how many days have passed since the date you track (like “Last Contacted” or “Start Date”).
Logic routes each contact to Day 7, Day 30, or Day 60. Three separate checks decide which template should be used, so you don’t accidentally send the wrong message at the wrong time. Clean. Predictable.
Emails go out, and Telegram keeps you in the loop. When an email sends, the workflow posts a Telegram alert so you have a real-time trail. A separate webhook flow also parses incoming testimonial payloads and pings Telegram when reviews land.
You can easily modify the follow-up days to match your sales cycle. Some teams prefer Day 3, Day 14, and Day 45. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Manual Trigger
Set up the workflow entry points so you can run tests manually and automate daily execution.
- Add the Manual Start Trigger node as a trigger for on-demand runs.
- Add the Daily Schedule Trigger node to run the workflow on a daily cadence.
- Connect both Manual Start Trigger and Daily Schedule Trigger to Configure Defaults as shown in the execution flow.
Step 2: Connect Notion Records Retrieval
Prepare the workflow to read client records and compute follow-up dates.
- In Configure Defaults, define any base fields or defaults your workflow requires (leave as-is if your template already includes fields).
- In Fetch Current Date, confirm the code returns the current date for calculations.
- Open Retrieve Notion Records and configure the HTTP request to your Notion database endpoint.
- Credential Required: Connect your notionApi credentials in Retrieve Notion Records.
Step 3: Set Up Date Calculations and Branching Logic
Compute day offsets and route records to the correct follow-up paths.
- In Compute Day Offsets, verify the code calculates day differences between the current date and client dates.
- Confirm that Compute Day Offsets outputs to Check Day 7, Check Day 30, and Check Day 60 in parallel.
- Configure conditions in Check Day 7, Check Day 30, and Check Day 60 so only matching records pass through.
Step 4: Configure Email Follow-ups and Telegram Notifications
Send timed emails and notify your team in Telegram whenever a follow-up is sent.
- In Send Day 7 Email, configure the email fields (To, Subject, Body) and connect SMTP.
- In Send Day 30 Email and Send Day 60 Email, configure the appropriate follow-up templates.
- Credential Required: Connect your smtp credentials in Send Day 7 Email, Send Day 30 Email, and Send Day 60 Email.
- Open Post Telegram Alert and configure the message to notify when any email is sent.
- Credential Required: Connect your telegramApi credentials in Post Telegram Alert.
Step 5: Configure the Webhook Testimonial Intake
Capture incoming testimonials and notify your team immediately.
- In Incoming Testimonial Hook, set the webhook path and HTTP method to match your testimonial form or service.
- Use Parse Review Payload to normalize incoming data into fields for messaging.
- Configure Telegram Review Notice to post the parsed testimonial to your Telegram channel.
- Credential Required: Connect your telegramApi credentials in Telegram Review Notice.
- In Return Webhook Reply, set the response content to confirm receipt to the caller.
Step 6: Test and Activate Your Workflow
Verify that data flows through the follow-up checks and notification paths, then switch to production use.
- Click Execute Workflow on Manual Start Trigger and ensure records flow through Fetch Current Date → Retrieve Notion Records → Compute Day Offsets.
- Confirm that Compute Day Offsets outputs to Check Day 7, Check Day 30, and Check Day 60 in parallel, and that only matching branches send emails.
- Verify each email node triggers Post Telegram Alert with the expected message.
- Send a sample payload to Incoming Testimonial Hook and confirm Telegram Review Notice and Return Webhook Reply both execute.
- When satisfied, switch the workflow Active to enable Daily Schedule Trigger for production runs.
Common Gotchas
- Notion credentials can expire or need specific permissions. If things break, check the integration connection in n8n Credentials and confirm the database is shared with that integration.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Telegram bot tokens get rotated more often than people expect, especially after bot edits in BotFather. If alerts stop, re-check the bot token and the chat ID the workflow is posting to.
Frequently Asked Questions
About 30 minutes if your Notion database and email credentials are ready.
No. You’ll mostly connect accounts and map fields in n8n. There is a small code step already included, but you don’t have to write it from scratch.
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 your email provider costs (often $0 if you use Gmail OAuth).
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.
Yes, and it’s one of the easiest tweaks. You can change the Day 7, Day 30, and Day 60 checks to any offsets you want, then update the matching “Send Day X Email” nodes with your copy. Common customizations include adding a Day 3 “welcome” email, skipping Day 60 for low-ticket clients, or sending a different message based on a Notion “Status” field.
Usually it’s an invalid bot token or the workflow is posting to the wrong chat ID. Re-check the Telegram credentials in n8n, then send a test message to the bot and confirm the chat ID you’re using matches where you want alerts. If it used to work and suddenly stopped, regenerating the token in BotFather and updating n8n often fixes it.
On n8n Cloud Starter, you can typically handle a few thousand workflow executions per month, which is plenty for most small databases. If you self-host, there’s no hard execution cap; it mainly depends on your server and how many Notion records you fetch each run. Practically, hundreds of records per day is a comfortable starting point.
Sometimes. If you want multiple timing rules (Day 7, Day 30, Day 60), branching logic, and the option to self-host, n8n is usually a better fit and won’t punish you for every extra path. Zapier or Make can still work if your setup is very simple, like “when a status changes, send one email,” and you prefer a more guided UI. The other big difference is control: in n8n you can compute dates, filter records, and add a webhook for testimonials in the same workflow. If you’re on the fence, Talk to an automation expert and you’ll get a straight recommendation.
Once this is running, follow-ups stop being a fragile habit. They become a system you can actually rely on.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
