FlowAlert Documentation
FlowAlert makes sure the right person's phone buzzes the moment something happens in your business — a new order, a failed payment, a backup that went silent.
The idea is simple: your systems send events, FlowAlert routes each one to the right people, proves it reached their phones, and escalates when nobody responds.
How it works
Your system → FlowAlert API → Routing rules → Staff phones- Send an event — Your website, app, or plugin sends an event to
POST /v1/eventswith an API key - Rules match — FlowAlert checks your routing rules against the event key
- Notifications delivered — Matched groups receive push notifications on the FlowAlert mobile app
Example use cases
| Event | Routed to |
|---|---|
booking.created | Booking staff |
payment.failed | Finance team |
order.created | Warehouse staff |
form.submitted | Sales team |
maintenance.urgent | On-duty manager |
Key concepts
- Events — Things that happen in your connected systems
- Routing Rules — Decide who gets notified for which events
- Groups — Collections of staff who receive notifications together
- Delivery & Receipts — How FlowAlert proves an alert reached a phone
- Acknowledgements — One tap answers for the whole team; escalation when nobody does
- On-Call Schedules — Alert only whoever is on duty right now
- Heartbeats — Get alerted when a job stops checking in