How to Automate Notion Reminders with Make: Setup, Pricing, Limits, and When to Use It

Key takeaways (TL;DR)

• Make can automate due-date reminders if you build "a scheduled scenario + a Notion search + a filter + an email module." Its strength is designing branching and loops visually.
• But Notion's trigger (Watch Database Items) is polling-based (it detects create/update), so "the due date arrived" can't be the direct trigger. You build due-date reminders with a schedule + a date filter.
• Pricing is billed per operation (renamed "credits" in 2026). There's a free tier, but processing many rows every day burns through it, and the cost gets hard to predict.
• Where Make struggles: external recipients who don't use Notion, not sending once something is done/paid, and the recipient's click updating Notion (two-way). None are impossible, but each takes custom building and upkeep.
• What Kapsel is: a notification tool that watches Notion's due dates, assignees, and statuses, emails reminders to recipients (including people outside your workspace), and writes the status back to Notion from the recipient's one click. It doesn't send to done/paid items. This article compares it with Make fairly.

"I heard Make is cheaper, so I started building—then the scenario ballooned." That's where many people stall when automating Notion due-date reminders in Make. This article is for anyone who wants to build due-date reminders in Make (formerly Integromat), or who already tried and hit a wall. It walks through the concrete setup using a scheduled scenario, and the real cost model—operation billing and polling intervals. By the end you'll know where the three walls are—external recipients, "stop once it's done," and reply-driven Notion updates—and how Make stacks up against Zapier, GAS, native Notion, and Kapsel.

Question	How Make handles it
Trigger for the due-date reminder	Notion's trigger (Watch Database Items) detects create/update (polling). "Due date arrived" is built from a scheduled scenario + date filter
Where it sends	Email and many SaaS. But it tends to be one-way for external recipients
Stop once it's done	Branch on status with a filter (you design and maintain the condition)
Two-way (reply updates Notion)	Update a Database Item can update Notion, but "recipient's click → Notion update" needs a separate form/webhook you build
Pricing	Billed per operation (credit). Each run consumes operations; cost grows with rows × frequency

---

What Make can do: the basic Notion reminder setup

Make is a no-code automation tool where you connect processing blocks (modules) with lines to build a scenario. Its hallmark is designing branching (routers), loops, and error handling visually, and Notion is one element inside that. First, the basics of Make's Notion integration.

Notion's trigger detects "create" and "update" (polling)

The Notion trigger you'll use most in Make is "Watch Database Items." It checks Notion at a set interval and fires when an item is created or updated (polling).

The key point: the passage of time itself—"the due date arrived"—can't be the trigger. "3 days before" or "past the deadline" is just time moving forward, unrelated to an item being created or updated, so Watch-type triggers can't catch it.

Build due-date reminders with "a schedule + a filter"

So a due-date reminder takes this shape:

1. Set the scenario's schedule (run daily at a set time)
2. A Notion search module (e.g., Search Objects to pull items from the target database)
3. A filter (narrow to "due in 3 days," "status ≠ done," etc.)
4. A send module (send via email, etc.)

In other words: "check Notion every morning and send only the rows that match." That's sound, but as covered below, every run consumes operations, and scenarios with more modules consume more per run.

Lots of flexibility for sending and branching

Make's strength is how freely you can arrange sends and branches. Beyond email and many SaaS, you can split paths with a router ("3 days before → person A, overdue → person B") or handle multiple rows with an Iterator/Aggregator. It's especially strong for internal automation like "push Notion updates into an internal tool."

Setting up a reminder in Make (example: email 3 days before the due date)

To make it concrete, here's the minimal flow for "email the assignee 3 days before the due date" (screen and module names can change as Make updates its product).

1. Create a new scenario, then use the clock icon (bottom) to set the schedule to "Every day, at a set time (e.g., 9 a.m.)."
2. Add "Notion → Search Objects" (or Watch Database Items) as the first module and connect your Notion account (create a Connection). Point it at the target database.
3. Add a filter between modules with conditions like "due date = today + 3 days" AND "status ≠ done."
4. Add an "Email → Send an Email" module; set the recipient to the assignee's email and merge the Notion task name and due date into the body.
5. Run the scenario once to confirm only the intended rows get emailed, then turn the schedule on.

At this point you have 3–4 modules. Each run consumes one operation per module it passes through.

💡 Tip: A due-date reminder is designed to "run every day and pick only the rows due that day." That means even on empty days with nothing to send, the watch/search operations are still consumed. The more databases and rows you target, the more it consumes.

The real cost model (operation / credit billing)

Make is a capable tool, and it's often said to be cheaper than Zapier thanks to per-operation billing. Still, for reminders the cost tends to get hard to predict. Pricing changes, so always confirm the latest on Make's official pricing. Here are the general tendencies at the time of writing (2026).

• Operation (credit) billing: each module run consumes one operation (in 2026 the unit was renamed from "operations" to "credits," but the mechanism is the same). A reminder that loops over many rows every day tends to consume a lot.
• Free plan limits: the free plan caps monthly operations and the number of scenarios you can run at once (roughly 1,000 operations/month and ~2 active scenarios at the time of writing). Fine for trying it out, but you hit the ceiling quickly in real use.
• Polling interval: the minimum run interval is around 15 minutes on the free plan and 1 minute on paid plans (at the time of writing). Since due-date reminders run on a schedule, "how often you run it" directly drives consumption.
• Paid plans: paid plans (e.g., Core) are billed monthly—roughly from about $9/month on annual billing—and include more operations (at the time of writing, 2026; plan structure and prices change, so confirm the latest on the official page).

The thing that trips people up: cost is decided by "how many times and how many modules run each day," not "how many emails you send per month."

What Make struggles with (three reminder-specific walls)

Make itself is a flexible automation platform, but narrowed to the single job of "delivering a Notion due date to a person," these three take effort. This isn't about Make being better or worse—it's about fit for the job.

Wall 1: it tends to be one-way for external recipients who don't use Notion

Sending email reaches external recipients fine. But completing "the recipient replies with their status and it flows back into Notion" with Make alone isn't easy. It tends to be fire-and-forget (one-way), and pulling replies back in needs a separate mechanism.

Wall 2: "don't send to done/paid" is yours to maintain

Double-chasing is the accident you most want to avoid with external recipients. In Make you can prevent it by branching on status with a filter, but you have to design that condition and maintain it as Notion's values drift (renamed options, new statuses). Rename a property and the scenario can quietly stop working.

Wall 3: click-to-update-Notion (two-way) means building it yourself

Make has "Update a Database Item," so updating Notion is possible. But to make "the recipient taps a button in the email → the Notion status changes," you need to build the form or webhook the button points to and wire it into your Make scenario. That goes beyond no-code into real assembly.

How it compares with Zapier, GAS, and native Notion

The alternatives each have different strengths.

• Native Notion: date-property reminders and mention notifications are easy, but they only reach people who have a Notion account. They don't reach external recipients.
• Zapier: no-code automation similar to Make with a very large app catalog. But a practical reminder tends to be multi-step = a paid plan, and task-based billing makes cost hard to predict. See How to Automate Notion Reminders with Zapier for the step-by-step.
• Google Apps Script (GAS): you can hit the Notion API and build free, time-triggered notifications. Flexible, but it assumes you maintain code and tends to become person-dependent.

There's a separate article comparing all of these side by side. For a bird's-eye view of tool selection, see Automate Notion Reminders and Notifications.

Where Kapsel fits (built for external + two-way)

Where Make is a general-purpose automation platform that connects any app, Kapsel is a notification tool focused on the single job of delivering a Notion due date to a person. The difference is that it handles the three walls above as standard features, not setup.

• Reaches people who don't use Notion: all the recipient needs is email—no app, no sign-up, no login.
• Doesn't send to done/paid items: it checks the latest status right before sending and skips the item if it's done or paid, preventing double-chasing by design.
• The recipient's one click writes back to Notion (two-way): tapping the button in the email updates the Notion status—no form or webhook to build.
• Overdue follow-ups, target filtering, recurring digests, a send log, merge fields: the pieces a reminder needs, chosen in a settings screen instead of stacking scenario modules.

In practice, that means you get the external + two-way reminder Make makes you assemble by hand, already built in and ready from a settings screen.

Pricing starts at a free plan ($0) that lets you try sending to external recipients on a limited monthly quota. Standard, built for real-world external-recipient volume, is $12/month. See Pricing for details. Note that Kapsel isn't an invoicing tool—it automates the "announce, confirm, and chase" that comes after an invoice is issued.

⚠️ Note: This doesn't make Make unnecessary. Complex internal automation that spans many SaaS beyond Notion is exactly what Make and Zapier are good at. Narrowed to "external due-date reminders plus reply-driven Notion updates," Kapsel is the better fit—a division of labor.

Which should you choose (by case)

• Internal task notifications are enough → native Notion + Slack, or a light Make/Zapier setup.
• You need complex automation spanning many SaaS beyond Notion → Make / Zapier.
• You have an engineer and want to build it for free → GAS.
• You want to reach clients/customers who don't use Notion and update Notion from their reply, or automate payment chasing → Kapsel.

FAQ

Can Make trigger directly on "the Notion due date arrived"?

No. Make's Notion trigger (Watch Database Items) detects create/update (polling); the passage of time itself can't be the trigger. Run the scenario on a daily schedule and filter by date.

Can I build Notion reminders on Make's free plan?

You can, but the free plan caps monthly operations and how many scenarios run at once, and the polling interval bottoms out at 15 minutes (at the time of writing). Processing many rows every day hits the ceiling quickly, so real use tends to require a paid plan. Check the official page for current limits.

Which is cheaper, Make or Zapier?

Generally Make tends to be cheaper on a per-operation (credit) basis, but it depends on the complexity of your scenario and how often it runs. Both change pricing, so confirm the latest official information.

Can Make "not send once it's done"?

Yes. Use a filter to exclude items whose status is done. But you design the condition and maintain it as Notion's values change.

Can a recipient's button tap update Notion, in Make?

Updating Notion (Update a Database Item) is possible, but making "email button → Notion update" work requires building a form or webhook for the button and wiring it into your Make scenario. It isn't complete with standard modules alone.

How do I remind a client who doesn't use Notion?

Sending email is possible in Make itself. But once you include "the reply updates Notion," custom building is needed. If you want external + two-way as standard, a purpose-built tool like Kapsel becomes an option.

---

This article is produced by Kapsel. The specs and pricing of Make and Notion are best confirmed on each company's official sources. Information reflects the time of writing (2026).