Wafly International

Reliable operations

Monitor your WhatsApp connection in South Africa

Monitor WhatsApp connection status in South Africa and create disconnection alerts with webhooks, n8n and Wafly.

Start a free 3-day trial · API docs

Direct answer

Monitoring combines disconnection events with a scheduled status endpoint check. The workflow waits to reduce false positives, confirms the state and alerts with the instance, client and reconnection procedure.

A useful automation does not end after sending a message. It observes instance status, records failures and alerts the right person before a disconnection affects operations.

What you can automate

  • Receive connection and disconnection events
  • Alert through email, Slack, Telegram or another channel
  • Separate temporary incidents from issues that require a new QR scan

Before you start

  • A configured disconnection webhook
  • An authenticated status request
  • A team alert channel
  • An owner for each instance

A production-ready approach

Combine events and polling

The webhook is fast while polling catches missed events. A scheduled run can check every instance without alerting while status remains healthy.

Confirm before alerting

After an event, wait and query status again. Alert only when the disconnection remains, so an automatic recovery does not wake the team.

Make the alert actionable

Include client, instance, first failure, last check and a dashboard link. Separate a temporary warning from an incident that requires another QR scan.

Direct status check

GET https://wafly.io/api-bridge-whats/instances/{instance}/token/{token}/status
Accept: application/json

Production checklist

  • Webhook plus scheduled polling
  • A delay before escalation
  • One open alert per incident
  • Automatic resolution after recovery
  • A reconnection runbook

How to build the workflow

  1. Configure the instance status webhook.
  2. Add waiting and retry rules to prevent unnecessary alerts.
  3. Escalate with the instance identifier and a link to the dashboard.

QR connection, not the official Meta API. Use opt-in contacts and increase volume gradually.

Frequently asked questions

Does every disconnection require a new QR scan?

Not necessarily. Some sessions recover; use the API status and a waiting period before escalating.

Can I monitor multiple instances?

Yes. Include the instance identifier and client in every alert so it reaches the right owner.

Does Wafly guarantee absolute availability?

No connection of this kind should be treated as infallible. Design retries, alerts and contingency procedures.

Verifiable resources