Automations

Let an event
send the next notification.

An automation is a workflow for one app and one environment. The canvas saves a draft. Publish is the copy that runs. A later edit does not change a run that has already started.

01

Start from what happened

A published workflow can start on a schedule, a matching event, a webhook, a new subscriber, a new tag, or a notification that was delivered, failed, opened, or clicked. Stripe and RevenueCat can start it from a signed webhook.

02

Wait, filter, and send

Steps can wait, branch, walk subscribers one at a time, and send or schedule a notification. A send can skip quiet hours for that subscriber. A failed run can start another workflow.

03

Test before it is live

Execute runs the draft on the board and does not publish it. A draft does not start on its own. Publish copies the board into the graph that runs, and Unpublish stops new runs.

04

Ask for a first draft

An empty board can start from a journey, such as a trial ending or a payment that failed. A prompt can build the trigger, the waits, and the messages. The result stays a draft until you publish it.

Ready to send?

Your app users one notification away.

Connect your app and send your first Notification in minutes.