Flows

Five flows, one of them still in the editor. Open one to see the graph it runs.

Live
3

of 5 flows

Runs
4,3439.2%

Last 7 days

Failed
64

All on one step

Success rate
99.86%

Last 7 days

FlowStatusRuns (7d)
Order paid → fulfilmentScores the order, writes a fulfilment row, and emails the customer.live4,128
Refund requested → reviewAnything over £200 waits for a human; the rest refunds itself.live214
Weekly revenue digestQueries the warehouse on Monday and posts the numbers to #leadership.live1
Failed payment dunningThree emails over ten days, then the subscription is cancelled.paused0
New customer onboardingNothing is wired up yet — it has never left the editor.draft0

On a schedule

The two flows nothing triggers but the clock.

  • Weekly revenue digest0 8 * * 1

    Monday, 08:00 UTC

    Next Last · succeededTook 42s
  • Failed payment dunning0 */6 * * *Paused

    Every six hours

    Last · succeededTook 5s

New flow

A flow starts as a draft. Nothing runs until you publish it.

Changeable later, but it decides the first step.

Navigate
Go to Flows
Go to Runs
Go to Library
Go to Connections
Flows
Order paid → fulfilment
Refund requested → review
Weekly revenue digest
Failed payment dunning
New customer onboarding
Runs
r-88214 — Order paid → fulfilment
r-88213 — Order paid → fulfilment
r-88212 — Refund requested → review
r-88211 — Order paid → fulfilment
Back to examples