Skip to content

Automation · Workflows

Push notification automations that run without you.

A workflow is a trigger and a short chain of steps. Someone subscribes, or your site reports an event, and from there they wait, get a notification, get tagged, on their own clock, whether or not you are at your desk.

app.notifypress.com

Subscriber Joins

Wait 2 hr(s)

Send Notification

Your 10% welcome code

Add Tag

welcomed

Wait

Draft

Delay (minutes)

120

1 – 43200 min (max 1 month) · 1440 = 1 day · 60 = 1 hr

Add a step

WaitSend NotificationAdd TagWebhook
The builder: the trigger at the top, the steps beneath it in the order they run, and the panel where the step you clicked is configured.

What a workflow is made of

Four parts, and you can hold all four in your head at once.

A trigger

One per workflow, and it decides who gets in. Subscriber Joins enrolls people the moment they opt in. Custom Event enrolls them when your site reports a named event to the API. A first order, a stalled checkout, whatever you track.

Steps, in the order you add them

Four kinds: wait anywhere from a minute to thirty days, send a notification, add a tag, or POST to a webhook. Use as many as the sequence needs, in whatever order it needs them.

One run per subscriber

Someone is enrolled in a given workflow once, and moves through it on their own clock. One person's two-day wait never holds up the people behind them.

Messages you reuse

Send steps pull from a Messages library kept separate from your campaigns, so an automated message can never be blasted to your whole list by accident.

Steps run in a straight line. Condition branches and A/B splits are not configurable yet, so a workflow is a sequence rather than a decision tree. Worth knowing before you plan one around a fork that is not there.

How a workflow gets built

Start from a template, walk through the guided wizard, or open a blank canvas. All three land in the same three moves.

01

Trigger

Name the workflow and choose what starts it. It begins life as a draft, so nobody is enrolled while you are still deciding what it should do.

02

Steps

Add a step and it joins the end of the chain. Click a node and its settings open beside the canvas. The delay in minutes, the message to send, the tag to apply, the URL to call.

03

Activate

A workflow needs at least one step before it can go live. Activating it starts enrollment from that moment onward: it works on the next person who matches, not retroactively on the ones who already subscribed.

Pausing stops the door, not the people

Pause a workflow and new enrollments stop immediately, while the subscribers already inside finish the sequence. Wait timers and all. Stopping one behaves the same way and is permanent, so duplicate a workflow when you want a changed version rather than lose the original. The list keeps the count either way: how many started, how many are still moving, how many finished.

See the full trigger and step reference

Every trigger and every step type, with what each one does and when to reach for it.

Triggers & Actions

Questions, answered.

Write the welcome message once.

Workflows come with every paid plan, starting at five on Starter. Open a free account, connect your site, and upgrade when you are ready to stop sending it by hand.