Critical alerts and monitoring via WhatsApp

For IT teams, SaaS builders, IoT and operations

Nobody reads an email at 2 am; a Slack ping drowns in the channel. When the production server is down or a payment fails, you want the message on the screen that lights up anyway: WhatsApp.

TextMeFlow turns any monitoring tool or cron job into an alert channel: one HTTP call, no SDK needed. And because it's two-way, you can even attach actions — reply "ACK" and the alert is claimed.

What it looks like

Green = sent via TextMeFlow (your number) · white = the customer's reply, delivered to you via webhook.

Why this works

  • WhatsApp gets through where email and dashboards fail: at night, on weekends, on the road.
  • One curl from cron, systemd, Zabbix, Grafana or GitHub Actions — no app or SDK to install.
  • Two-way: let your team claim alerts ("ACK") or start a runbook action with a reply.
  • Rate limiting in the pipeline stops an alert storm from harming your number — though we recommend deduplication at the source anyway.

How to set it up

1

Alert script

Add a curl to your monitoring tool or healthcheck script (example below). Grafana, Zabbix and UptimeRobot support webhook notifications you forward 1-to-1.

2

Escalation ladder

Send to the on-call first, then to the rest of the team after X minutes without ACK — a simple loop in your own code or an n8n scenario.

3

ACK flow (optional)

Catch replies via the inbound webhook and mark the alert as claimed in your monitoring system.

example
# In your healthcheck or CI pipeline:
curl -X POST https://api.textmeflow.eu/v1/messages \
  -H "Authorization: Bearer $TMF_API_KEY" \
  -d "{
    \"to\": \"+32479777888\",
    \"text\": \"CRITICAL: $SERVICE down since $(date +%H:%M). Reply ACK to claim.\"
  }"

Ready-made message templates

Copy, replace the {placeholders} with your own variables, done.

CRITICAL: {service} not responding ({detail}). Since {time}. Reply ACK to claim.

WARNING: disk usage on {server} above 90% ({percentage}%). Action needed within 24h.

Payment failed for customer {customer} ({amount}) — {reason}. Check the dashboard: {link}

RESOLVED: {service} is back online. Downtime: {duration}.

GDPR tip

Alerts to your own team fall outside the consumer opt-in debate, but your team members' numbers are still personal data: include the channel in your internal privacy notice and use a shared on-call number where possible.

Further reading

Want to send WhatsApp messages via API yourself?

Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.

Free forever