Google Sheets reminders, without calendar workarounds.
Connect a spreadsheet, map your due-date and email columns, and SheetDue sends reminder emails before deadlines are missed.
Sheet monitors
Create due-date monitors from Drive files, review inferred values, and keep delivery logs close to active watches.
Plan
Daily scans while in sandbox.
free
Active sheets
0 configured watches
0 / 1
Reminders
Current monthly usage.
0 / 50
New monitor
One guided flow: source, worksheet, mapped values, then schedule.
Sheet1
8 detected headers
Review the mapped values
SheetDue guessed the task, date, and recipient. Change only what looks wrong.
Auto-mapped fields
Reminder preview
QueuedSubject
Reminder: Collect W-9 is due 2026-06-13
This is a quick reminder that Collect W-9 is due on 2026-06-13.
Workflow
From spreadsheet to reminders in four decisions.
SheetDue is built for people who already run operations in Google Sheets. The setup flow avoids spreadsheet IDs and guesses sensible defaults from real row samples.
New SheetDue watch
No spreadsheet IDs required
Drive search
Operations Tracker
Google Sheet
Client Renewals.xlsx
Excel workbook
Invoice Follow-ups
Google Sheet
Sheet
native
.xlsx
copy
Tabs
preview
Mapping review
Task
AutoA - Task
Header + text samples
Due date
AutoB - Due date
ISO date detected
Recipient
AutoC - Owner Email
Email samples found
Ready to activate
3 days before + due date reminders, skipping completed rows.
Reminder rules
Send at the right moment, not whenever someone remembers.
Configure before-due reminders, due-date reminders, and repeat overdue reminders. SheetDue reads the spreadsheet timezone and skips rows marked complete.
Rule preview for “Collect W-9”
Due on 2026-06-13, spreadsheet timezone respected
3 days before
Queue reminder
Due date
Send if still open
Overdue repeat
Repeat every 7 days
Reliability
Designed for reruns, sorting, and real spreadsheet behavior.
SheetDue manages a stable row identity column, stores reminder events with idempotency keys, and queues delivery before sending so overlapping cron runs do not double-send the same reminder.
Duplicate-send simulation
Two cron runs find the same due row. Only one reminder is allowed.
Free
Daily scan
Pro
Hourly scan
Sheet row being scanned
_sheetdue_row_id
row_8f21
Task
Collect W-9
Due date
2026-06-13
Recipient
ops@example.com
Rule
3 days before
The row can move, but the key does not.
Sorting or filtering the sheet changes row position, not the hidden row id used to identify this reminder.
watch_ops + row_8f21 + 2026-06-13 + before_3_days + ops@example.com
reminder_events
unique index
Cron run A
10:00:01Insert reminder event
Cron run B
10:00:04Insert same event
Delivery record
1 row
stable id
1 event
unique key
1 email
provider log
Use cases
For the sheets that quietly run the business.
SheetDue does not care whether a row is a client request, invoice, renewal, or compliance item. It needs the same three operational fields: task, due date, and recipient.
Common operating sheets
Same reminder engine, different row labels
| Sheet type | Task | Due date | Recipient | Status |
|---|---|---|---|---|
| Client docs | Collect W-9 | 2026-06-13 | ops@example.com | Open |
| Invoices | Follow up ACME | 2026-06-17 | ap@example.com | Open |
| Contracts | Renew vendor MSA | 2026-06-24 | legal@example.com | Open |
| Compliance | File quarterly report | 2026-06-30 | admin@example.com | Done |
Pricing
Start with one sheet. Upgrade when reminders become operational.
SheetDue pricing is tied to the two things that matter in the product: how many sheets are active and how often reminders need to be checked.
Choose by operating volume
The limits match the app entitlement checks.
Free
$0
Pro
$19/mo
When Pro makes sense
Three practical upgrade triggers
2+ active sheets
Free monitors one active spreadsheet.
More than 50 reminders
Monthly reminder volume moves to 2,500.
Same-day urgency
Hourly scans replace daily checks.
Subscription state is synced
Polar webhooks update the shared labs database, so future apps can use the same account and billing foundation.