Get a Demo Get Started

Deadline Reminders

Get Started

Ship this workflow

Pick how you want to build it.

Try it in the dashboard Fastest Go to Workflows → New Workflow → Use sample workflow in your workspace, and select this workflow. Try it
Build with the SuprSend Agent Try the agent
Build with SuprSend MCP Set up MCP

When to use this workflow

    Tasks need more than one reminder. One nudge is easy to miss, so the deadline passes with the task still open.

    Reminders keep going after the task is done. Completed or reassigned tasks still get reminded when they shouldn't.

    A reminder sent on just one channel gets missed. If the user isn't checking that channel, they never see it.

    Reminders keep firing for an old due date. When a deadline moves, the reminders for the old date don't stop.

How it works

1

Reminders start

A task is created with a due date (TASK_CREATED), and the reminder sequence begins.

Trigger
2

First reminder - a day before

A day before the deadline, the user gets an early reminder.

Wait UntilSmart Channel Routing
3

Second reminder - hours before

Four hours before the deadline, a sharper reminder follows.

Wait UntilSmart Channel Routing
4

Overdue alert - at the deadline

If the deadline passes with the task still open, one overdue alert goes out.

Wait UntilSmart Channel Routing
5

Stops when the task is handled

Finishing, reassigning, or rescheduling the task cancels every remaining reminder.

BranchExit

Best practices

    Don't send every channel at once

    A reminder shouldn't hit someone on email, Slack, and push at the same time. Send one channel, and try the next only if the first isn't seen - Smart Channel Routing handles this.

    Match the reminder timing to your deadline length

    The 24-hour and 4-hour defaults fit most teams. For same-day tasks, try 4 hours and 1 hour; for week-long ones, 2 days and 4 hours.

    Send within the user's working hours, in their timezone

    A reminder timed for hours before a 5 PM deadline should land at the right local time, not overnight. A time window handles both.

    Set the reminder with the task name and deadline

    "'Update homepage' is due tomorrow at 5 PM" gets acted on faster than "You have a task due soon."

Common mistakes to avoid

    Timing reminders by a fixed delay, not the deadline

    A task due in three hours shouldn't wait a full day for its first reminder. Time every reminder from the due date.

    Stopping reminders without matching the task

    The completion event has to point to the same task the reminders are for. Otherwise finishing one task quietly stops the reminders for all the user's other tasks.

    All three reminders say the same thing

    Each one should escalate: a day-before heads-up, an hours-before reminder, an overdue alert. If they all read alike, the escalation is lost.

    Repeating the overdue alert

    A daily overdue alert turns the warning into background noise. Send it once, when the deadline passes.

What users receive

The actual notifications this workflow sends, on each channel.

Deadline Due Tomorrow

Email
Deadline Due Tomorrow — Email
In-app inbox
Deadline Due Tomorrow — In-app inbox
Slack
Deadline Due Tomorrow — Slack

What good looks like

Primary signal On-time

On-time completion

More tasks get finished before the deadline once reminders are running, compared with tasks that have none.

Fatigue signal Fatigue

Rising mutes and ignored reminders

When people start muting deadline channels or reminders stop driving action, they're getting more reminders than the task needs.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

No. The moment a task is completed or reassigned, the reminders stop and anything not yet sent is cancelled.

In-app inbox, email, Slack, Microsoft Teams, and mobile or web push. A user only gets reminders on the channels they're set up for, and any they've turned off in their preferences are skipped automatically.

It moves to the next one. Smart Channel Routing sends on one channel at a time and only escalates if the reminder hasn't been seen, so a missed email or push still gets followed up, without firing every channel at once.

Yes. Add a Branch to route by priority, sending urgent tasks through this reminder sequence. For low-priority deadlines you'd rather not send one by one, add a Batch node so several arrive as a single reminder.

Trigger it with a payload shaped like the TASK_CREATED event: a recipient plus a due date in .due_time. You can do this from the Test button in the workflow editor, by asking the SuprSend Agent in the dashboard, or through the API, CLI, or MCP.

The workflow handles it automatically. The current run exits when it receives DUE_DATE_UPDATED, and a new TASK_CREATED event carrying the updated due date starts a fresh countdown with the correct timing.

Ship Deadline Reminders in under 5 minutes.

Try directly in SuprSend

Fastest

Sign up and test the workflow directly in the dashboard.

Get Started

Build with the SuprSend Agent

Copy the prompt, paste it into the Agent in your SuprSend dashboard, and the workflow gets built for you.

Try the agent

Build it with SuprSend MCP

Set up SuprSend MCP in Claude Code, Cursor or Windsurf, copy the prompt, and the workflow builds itself in your workspace.

Set up MCP