Disconnections

introduction the whatsapp disconnection webhook feature allows sending a real time notification to an external platform whenever a whatsapp account is disconnected, logged out, or loses its active session this functionality is designed for monitoring account health and availability , ensuring that teams are immediately alerted when a whatsapp number goes offline and can take corrective action (re login, reassignment, or escalation) this is not a messaging or ai feature ; it is strictly a webhook based notification system triggered by a whatsapp session disconnection event configuration location the disconnection webhook is configured at number level in sub account panel navigate to whatsapp numbers select the specific whatsapp number open settings go to disconnection settings enable disconnected event paste the webhook url save changes each number must be configured independently trigger webhook event that can be configured session disconnected → triggered when the whatsapp account logs out, loses session, or is disconnected from the system webhook payload each webhook request will include basic identification data for the disconnected account, such as whatsapp account / phone number country (if applicable) event type disconnection / logout (exact fields may vary depending on platform version; workflows should be tolerant to minimal payloads ) how it works a whatsapp account is disconnected (manual logout, expired session, device change, or system issue) wazzap mx immediately sends an http request to the configured disconnection webhook url the webhook must be created in an automation platform such as gohighlevel (ghl) zapier pabbly n8n the external platform receives the webhook and executes predefined actions (alerts, logs, tasks, or workflows) testing the disconnection webhook to test this functionality create an inbound webhook in gohighlevel (or your automation platform) copy the webhook url paste the url into the disconnection settings → webhook url field save changes manually log out or disconnect the whatsapp account confirm that the inbound webhook is triggered and received ⚠️ important the webhook will only fire after a real disconnection event occurs highlevel (ghl) integration in docid\ qh5m7bg 7rf8ysjwwpjxm , the disconnection webhook is implemented using an inbound webhook trigger this feature is considered a premium action by highlevel and may incur additional costs please verify pricing in the official highlevel documentation recommended flow in highlevel trigger – inbound webhook activated when wazzap mx sends the disconnection event identify account / phone match the incoming phone number or whatsapp identifier update status mark whatsapp account as disconnected / offline optionally tag the account (e g , wa disconnected) notification actions (optional) send internal slack / email / sms alert create a task for reconnection notify the assigned agent or admin example (highlevel whatsapp disconnection) a whatsapp account is logged out due to session expiration wazzap mx sends a webhook to highlevel containing phone +521xxxxxxxxxx country mx event disconnected highlevel processes the webhook identifies the whatsapp account updates status to disconnected sends an internal alert to the operations team optionally creates a task to reconnect the account result whatsapp disconnections are detected in real time teams are immediately notified when an account goes offline downtime is reduced by faster response and reconnection operational visibility and system reliability are improved ⚠️ important notes this feature does not send messages ; it only reports session disconnections webhooks trigger only on real logout or disconnection events always test using a real whatsapp logout configure the webhook in a secure automation platform (highlevel, zapier, pabbly, n8n) design workflows to handle minimal payload data gracefully