Skip to content
Public beta — Swift, Android and Flutter SDKs are liveRead the source
Notifie

Durable workflows

Product events in.
Reliable actions out.

Compose notification logic from events, waits, conditions, schedules, and push actions. Every run is durable, inspectable, and safe to retry.

TRIAL CONVERSION · VERSION 3ACTIVE
EVENTtrial_started137 runs
WAIT48 hours82 resumed
CONDITIONplan = free41 matched
ACTIONSend reminder39 accepted
RUN EVIDENCEEvery branch records the value it observed and the path it chose.

Built for process failure

Assume the worker can run it again.

Notifie’s workflow runtime treats stale locks, retries, provider timeouts, and post-side-effect crashes as normal operating conditions—not edge cases.

Explicit flow graph

Versioned event, wait, condition, and action nodes with cycle rejection.

Wall-clock scheduling

One-time, recurring, cron, delayed, and inactivity triggers.

Durable waits

Resume jobs are stored in Postgres rather than tied to a web request or process.

Idempotent actions

Stable invocation keys preserve at-most-once and at-least-once guarantees.

Delivery safeguards

Frequency caps, local delivery windows, and audience policy before provider handoff.

Replay without side effects

Re-evaluate logic and inspect branches without executing external actions.

From template to evidence

Start with a proven pattern. Keep the exact run history.

Templates bind to observed event names. Once active, run steps record why a user entered, what each condition observed, and which branch fired.

Draft flows receive nothing. Activation creates the subscription. Replay evaluates the graph but never executes an external action.
Flow safety model

Public beta — no credit card

Turn one observed event into a durable flow.

Start with a compatible template or build the exact notification path your product needs.

Connect a real app