Original local demonstration
Run six fictional reminder cases
This executable JavaScript prototype uses a fixed clock: September 14, 2026, 12:00 UTC. It checks eligibility, skips duplicates, and writes eligible reminders to an in-memory preview outbox. It does not run inside Make and sends no email.
Expected results and limits
First run: two previews; future, completed, invalid-date, and duplicate rows are skipped. Replay: no additional previews. Simulated failure: one preview on the first run, then one recovered preview on replay. The failure happens before acceptance; it does not model a provider accepting an email and then timing out.
State lasts only in this page. Reload resets it. This demonstrates local control flow, not durable idempotency, concurrent processing, scheduling, Make module integration, real email delivery, or savings.
Run the same source in Node.js with the downloadable runner: save both files in one folder and run node reminder-demo-runner.mjs.
Recorded first run · September 14, 2026
Download the observed first-run, replay, failure, and recovery results (JSON).
Original demonstration / Single-module scope
A synthetic preview, run in Make.
We ran the Tools → Set variable module using “Run this module”. Its output was reminder_preview = DEMO-001 | pending | preview only - no email sent. The run interface showed 1 operation and 1 credit.
Make a useful draft before automating delivery
For a small service business collecting files or approvals, begin with one weekly draft that lists exactly what is outstanding. Have a person check it before sending. The first goal is a correct list, not maximum message volume.
This is a workflow design based on Make documentation, not a working scenario export or a tested client deployment. The downloadable worksheet has completed example scenarios and blank observation rows so you can evaluate an implementation without uploading client material.
Bounded original demonstration: one Set variable run
On 2026-09-13 we ran Tools → Set variable with Run this module in a publisher Make Free account. Variable name reminder_preview. Value: DEMO-001 | pending | preview only - no email sent. The run interface showed 1 operation and 1 credit. Schedule remained off. No mailbox was connected and no email was sent.
This is a bounded original demonstration of one synthetic module, not an end-to-end reminder workflow. It does not establish due-date filtering, retries, idempotency, scheduling, or delivery. Do not treat the 1 credit as the cost of a weekly client digest.
A MailerLite welcome sequence responds to a new subscriber. This Make design groups client reminders into a draft for review. Test each step of the chosen workflow, including the connected service, duplicate handling and failures.
| Tested | Not tested |
|---|---|
| Tools → Set variable, Run this module, output reminder_preview = DEMO-001 | pending | preview only - no email sent | Due-date filtering or overdue selection |
| Interface showed 1 operation and 1 credit | Retries, incomplete executions, or duplicate-batch protection |
| No email sent; schedule toggle off; no connected mailbox | Idempotent weekly batch keys |
| Synthetic value only | End-to-end reminder delivery |
Match the plan to your needs and budget
Make's pricing source reviewed on September 13, 2026 listed 1,000 credits per month and a 15-minute minimum scheduled interval on Free. Paid-plan prices were not verified in the September 15 review; check the current Core or Pro invoice before budgeting.
| Requirement | Qualifying plan | Due now | Renewal | Exclusion |
|---|---|---|---|---|
| Weekly overdue-item digest with human review | Make Free | $0 (documented 1,000 credits/month) | $0 while within credits; paid billing at checkout if exceeded | Minimum 15-minute scheduled interval on Free; connected apps extra; Make is not an email platform |
| Polling faster than every 15 minutes, or more than the free credit envelope | Paid Make plan quoted at checkout | Check current Make pricing at checkout | Check renewal at checkout | Do not treat one credit from a Set variable run as the workflow cost |
| Spreadsheet plus calendar already produces the weekly list | Keep current tool | $0 additional | Existing tool renewal only | Identify the missing step before adding automation |
| End-to-end reminder email delivery | Not established in this guide | Not purchased for this guide | n/a | The original demo did not send email and does not prove delivery |
Define the record before choosing modules
Choose one timezone and one definition of overdue. A date with no time should not become overdue at a surprising hour because two systems use different timezones. Group by a stable client identifier, not a display name that two people may share.
| Field | Purpose | Example |
|---|---|---|
| request_id | Stable identity for one requested item | REQ-001 |
| client_id and email | Group the right recipient's items | DEMO-A / [email protected] |
| status | Decide whether the item still needs attention | pending, received, cancelled |
| due_date | Keep future items out of the overdue list | 2026-09-10 |
| last_draft_batch | Recognize a previously handled weekly batch | 2026-W37 |
| item_label | Tell the recipient what is actually missing | September attendance list |
The proposed processing order
- Read the request table and reject rows missing an identifier, valid status, recipient, or due date. Send rejected rows to a review list.
- Select pending items due before the chosen cutoff. Exclude received and cancelled items.
- Group by client, then create a consistent batch key from the client identifier and reporting week. Check whether that draft already exists.
- Create one draft with explicit item names and an owner for review. Save the returned draft identifier and batch key.
- Immediately before sending, recheck the current item statuses. Someone may have supplied a file after the weekly draft was prepared.
- Record approval and send status separately. A draft being created is not evidence that a message was delivered.
A retry must not create a second reminder
A failure can occur after a mail service creates a draft but before the spreadsheet records its identifier. Blindly repeating the create step can duplicate it. Your implementation needs a way to locate an existing draft using its stable batch reference, or to stop for human reconciliation when the outcome is uncertain.
Make's incomplete-execution feature can retain unfinished runs and support resolution; the documentation says it is disabled by default. Enabling it is not proof that a workflow is safe to retry. Decide what every side effect means before selecting an error handler.
| Test case | Expected behavior |
|---|---|
| Same batch runs twice | Existing draft is reused or second attempt is stopped |
| Item marked received before run | Item is absent |
| Item arrives after draft creation | Reviewer removes it before delivery |
| Two clients share a display name | Their records stay separate |
| Email service returns an ambiguous error | Review queue; no blind repeated sending |
Keep the first demonstration inexpensive
Make Free lists 1,000 credits a month and a 15-minute minimum scheduled interval. A weekly synthetic demonstration does not need fast polling. Credits depend on the actions actually executed; one workflow run does not necessarily equal one credit.
Measure a representative run, including searches, each processed row, draft creation, record updates, and retries. Multiply by the planned schedule, then leave headroom for errors. A free Make account does not make a connected mailbox, API, or business application free.
What this process cannot solve
Automation cannot make an unresponsive client cooperate or determine whether an uploaded document is complete. Keep financial judgments and document validation outside this administrative reminder design. Start with fictional data and the smallest useful scope. Publish a live scenario only after its actual modules, permissions, credits, and exception handling have been verified.
Watch demos / Official walkthroughs
See how the tools work.
Videos load from YouTube only when you press play. These are provider videos, not our own product tests.
Make / Official video
Make—Building Your First Automated Workflow from Scratch
What to look for: Follow how modules connect and how data moves through the first workflow.
Watch on YouTubeQuestions before you decide
Can I use Make as my email platform?
No. Make passes data between connected apps; email delivery requires a mail service. This guide's demonstration did not send email. Check both the workflow output and the delivery service before using it with real recipients.
Can I try a weekly reminder workflow on Make Free?
Make's 2026-09-13 pricing source lists 1,000 credits per month and a minimum scheduled interval of 15 minutes on Free. The official pricing page returned 403 on 2026-09-15, so those Free limits are reused, not recaptured. Weekly scheduling is compatible with that interval, but credits must cover actual actions, rows, and errors. Connected apps may have separate charges. Keep your current spreadsheet if it already meets the digest.
Did you send a real reminder email?
No. The original demonstration ran Tools → Set variable once. Output was reminder_preview = DEMO-001 | pending | preview only - no email sent. The run showed 1 operation and 1 credit. End-to-end reminder delivery was not tested.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Make pricing and free-plan limits Accessed 13 Sep 2026
- Make incomplete executions Accessed 13 Sep 2026
- Make Academy: incomplete executions Accessed 13 Sep 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.