REST API
A push notification API — no app to build
One HTTP POST and a real push notification lands on your team’s phones — with sound, tap-to-acknowledge, and automatic escalation if nobody responds. No FCM or APNs setup, no device tokens to manage, no mobile app to ship: your team installs FlowAlert, you send events.
1,000 free events/month · No card required
Sending a push notification from code shouldn’t require building an app.
FCM and APNs are built for apps you ship yourself: certificates, device tokens, token refresh, per-platform payloads — a project, not a notification.
Push SDKs like OneSignal or Firebase solve pushing to your users inside your own app — not “make my phone buzz when my script fails.”
Hobbyist tools cover the single-phone case, but a team needs more than delivery: who was notified, did anyone see it, and what happens if they didn’t?
Email and chat messages technically arrive — buried, silent, and owned by nobody at 2 a.m.
FlowAlert is the missing middle: a REST API on one side, a polished iOS & Android app your team already has on the other. You POST an event with a key, title, and priority; FlowAlert routes it by your rules, pushes it to the right phones with sound, tracks acknowledgement, and escalates on silence.
1,000
Free events every month to start. No card required.
How it works
From event to acknowledged alert — the whole path, in order.
Create a workspace and grab your API key (free, no card)
Your team installs the FlowAlert app and joins with a QR code — that’s the entire “device registration”
POST an event: event_key, title, optional body and priority — from curl, Python, Node, PHP, Go, or anything with HTTP
FlowAlert matches your routing rules and pushes to the right people with the right sound
They tap to acknowledge — and if nobody does, it escalates to the next person automatically
See it in action
deploy.failed
→ DevOps · Raj
What you get
One POST — no FCM/APNs certificates, no device tokens
Real push notifications on iOS & Android, with sound
Routing by event key, priority, and team — not broadcast
Tap-to-acknowledge with a full delivery → opened → ack’d trail
Automatic escalation when nobody responds
Urgent alerts can break through silent mode
Free tier: 1,000 events/month, forever
Heartbeat monitors for cron jobs — silence becomes an alert
Use cases
Server & script alerts
Wrap any script: on failure, curl one event and the on-call phone buzzes. Exit code 1 finally has consequences.
Cron job monitoring
Flip it around with heartbeats — the job checks in when it runs, and FlowAlert alerts you when the check-in doesn’t come.
CI/CD notifications
A failed deploy pages the engineer on rotation — not a channel where it scrolls away.
Business events from your backend
New signups, failed charges, big orders — the same POST routes business moments to the people who act on them.
Internal tools
Give your admin panel a “page the team” button: one API call, with priority and escalation handled for you.
IoT & edge devices
Anything that can make an HTTPS request can page a human — sensors, kiosks, Raspberry Pis in the back office.
Every event, routed instantly
The signals this integration fires — each one routable to a different person, priority, or escalation chain.
deploy.failedCI/CD pipeline broke on the main branch
server.cpuResource threshold crossed on production
backup.missedNightly job didn’t check in (heartbeat)
payment.failedA charge was declined and revenue is waiting
signup.newA new customer just registered
form.submittedA lead came in from your website
How it compares to the usual approaches
FlowAlertTime to first push
Days of certificate & token plumbing (DIY)
Minutes — one POST
Team routing
Broadcast to one phone or everyone
Right person, by event key & priority
Acknowledgement & audit trail
Fire and forget
Delivered → opened → ack’d, timestamped
When nobody responds
Nothing happens
Escalates to backup automatically
Push into your own consumer app
Yes — that’s FCM/OneSignal’s job
No — not an SDK
Common questions
The things people ask before connecting this — the docs cover the rest.
POST to https://api.flowalert.io/v1/events with your API key and a JSON body: event_key (e.g. "deploy.failed"), title, and optionally body, priority, and data fields. FlowAlert matches the event against your routing rules and pushes to the right team members’ phones. The docs include copy-paste examples for curl, Python, Node.js, PHP, and Go.
No — that’s the point. FlowAlert owns the mobile apps and the push infrastructure. You never touch certificates, device tokens, or platform payloads; your team installs the app, and delivery is our job.
No — FlowAlert is not an SDK for your own consumer app. If you’re building push for your app’s end users, you want FCM, APNs, or a service like OneSignal. FlowAlert is for notifying you and your team on their phones, without building anything.
Those are excellent for one person’s phone. FlowAlert is built for teams: events route to the right person by key and priority instead of broadcasting, recipients acknowledge with a timestamped trail, and silence escalates to a backup automatically. It’s the difference between a beeper and an on-call system.
Four levels — LOW, NORMAL, HIGH, URGENT/CRITICAL — control sound and urgency. Urgent alerts can play an alarm that breaks through silent mode on Android, and respect per-person quiet hours for everything less.
Yes — 1,000 events and 100 notifications per month, free forever, no card required. Enough to wire up your servers and see the first real alert land tonight.
Events are accepted in milliseconds (typically ~40ms) and delivered through APNs and FCM with per-device delivery receipts. Delivery, opens, and acknowledgements are all logged so you can prove an alert was seen — or catch that it wasn’t.
Yes — heartbeat monitors are the dead-man’s-switch: your job pings a check-in URL on every run, and if the ping doesn’t arrive within the window, FlowAlert raises the alert and pages whoever is on call.
Stop missing what matters.
Set up FlowAlert in under two minutes: connect a source, define your first routing rule, and the right person’s phone knows from then on.
No card required · Free plan forever · REST API included