Get a Demo Get Started

Approval Notifications

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

    A pending approval stalls the work behind it. Until the approver decides, whatever needs their sign-off has to wait.

    A single request is easy to forget. One notification gets buried, and the approval sits for days.

    Reminders keep chasing an approver who already decided. Once it is approved or rejected, the nudges should stop.

    An approval sent on one channel is missed. If the approver is not checking that channel, they never see it.

How it works

1

Approval is requested

A request is raised (APPROVAL_REQUESTED), and the approver is notified.

TriggerSmart Channel Routing
2

Reminded each day

If the request stays open, the approver is reminded daily, up to three times.

Wait UntilSmart Channel Routing
3

Stops when resolved

Approving, rejecting, or withdrawing the request cancels the reminders.

Wait UntilExit

Best practices

    Lead with what needs approving and who asked

    "Sarah needs your sign-off on the Q3 budget" gets a faster decision than "You have an approval request."

    Tell the requester when the request is resolved

    Add an Invoke Workflow step on the resolved path to notify the requester with its own message, so they learn the decision without chasing it.

    Don't notify every channel at once

    Once the approver has seen the request, sending it on the remaining channels adds nothing. Smart Channel Routing goes one channel at a time and stops as soon as it is seen.

    Plan for an approval no one answers

    After the last reminder the workflow stops. Route a still-open request to a backup approver so it is not lost.

Common mistakes to avoid

    Reminding too often

    Several reminders a day for one approval become noise the approver ignores.

    Making reminders read like the first request

    If a reminder looks identical to the original, the approver cannot tell it is a nudge to act.

    Sending an approval with no way to act

    With no approve or reject action and no link, the approver has to go find the request, and the decision waits.

    Reminding outside the approver's working hours

    A reminder that lands at 2 AM is missed by morning. Keep it in the approver's timezone with a time window.

What users receive

The actual notifications this workflow sends, on each channel.

Approval Reminder

Email
Approval Reminder — Email
In-app inbox
Approval Reminder — In-app inbox
Slack
Approval Reminder — Slack

What good looks like

Primary signal Faster decisions

Approvals get resolved sooner

Requests get approved or rejected faster once reminders are running, instead of sitting open.

Fatigue signal Opt-outs

Approvers muting reminders

When approvers start muting the reminders, they are being chased more than the decision needs.

Support

Frequently Asked Questions

Quick answers about setting up and running this workflow.

Requests can go out on in-app inbox, email, Slack, Microsoft Teams, and mobile or web push. Smart Channel Routing sends them one channel at a time, lowest-cost first, and stops the moment the approver has seen the request, so paid channels are only used when needed. Any channel a user has turned off in their preferences is skipped.

By default the approver gets up to three reminders, one day apart. Adjust the Wait Until delays or the number of reminders in the workflow editor, or ask the SuprSend MCP to change them.

Yes. Trigger the workflow with more than one recipient, and each approver gets their own request and reminder sequence.

Yes. Each Wait Until ends the run once the request is resolved. Add or change the resolution events in the workflow editor, or ask the SuprSend MCP.

Trigger it with a payload shaped like the APPROVAL_REQUESTED event: an approver as the recipient plus a request_id. To check that reminders stop, fire APPROVAL_APPROVED with the same request_id. 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.

Ship Approval Notifications 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