Flows Webhooks
There are various webhook you should subscribe to and monitor which are related to WA Flows. Message webhook: Webhook to monitor the status of your business’ Flows: Webhooks to monitor performance of endpoint powered Flows : Flow Versions webhooks:Webhook Setup
Create an Endpoint
Before you can start receiving notifications you will need to create an endpoint on your server to receive notifications. Your endpoint must be able to process two types of HTTPS requests: Verification Requests and Event Notifications. Since both requests use HTTPs, your server must have a valid TLS or SSL certificate correctly configured and installed. Self-signed certificates are not supported. Learn more about Verifying Requests and Event NotificationsSample App Endpoints
To test your Webhooks, you can create a sample app with an endpoint for receiving notifications.Subscribe to Webhooks
Once your endpoint is ready, go to your App Dashboard. If you do not have app, create a Business Type App. In your App Dashboard, find the WhatsApp product and click Configuration. Then, find the webhooks section and select Configure a webhook. A dialog will then appear asking you for the following:- Callback URL: The URL WhatsApp will be sending the events to. This is the endpoint you have created above
- Verify Token: Set up when you create your webhook endpoint
- Add the
whatsapp_business_messagingpermission in your App Dashboard - Successfully complete Meta App Review – This step will take time but you can continue to test during the entire review process.
Flow Response Message Webhook
When user completes the flow, a message is sent to WhatsApp chat. You will receive that message through a webhook which you normally use to process chat messages from the user. Below is the structure of flow response message webhook payload:| Parameter | Description |
|---|---|
contextobject | Context of the message that the user replied to. Context object contains message_id of flows request message and sender number. |
context.fromstring | User’s WhatsApp account number |
context.idstring | Message ID |
context.typestring | Always interactive |
interactive.typestring | Always nfm_reply |
interactive.nfm_reply.namestring | flow |
interactive.nfm_reply.bodystring | Always Sent |
interactive.nfm_reply.response_jsonstring | Flow-specific data. The structure is either defined in flow JSON (see Complete action) or, if flow is using an endpoint, controlled by endpoint (see Final Response Payload in Data Exchange Request) |
timestampstring | Time of flow response message |
Flows Status and Performance Webhooks
Webhook Notification Object
A combination of nested objects of JSON arrays and objects that contain information about a change.| Name | Description |
|---|---|
objectstring | The webhook a business has subscribed to |
entryarray of objects | An array of entry objects. Entry objects have the following properties: - id - string. The WhatsApp Business Account ID for the business that is subscribed to the webhook.- changes - Array of objects. An array of change objects. Change objects have the following properties:1. value — Object. A value object. See Value Object.2. field — String. Notification type. Value will be flows. |
Value Object
Contains details for the change that triggered the webhook. This object is nested within thechanges array of the entry array.
| Name | Description |
|---|---|
flow_idstring | ID of the flow |
thresholdnumber | The alert threshold that was reached or recovered from |
eventstring | Type of webhook notification sent, value being one of: - FLOW_STATUS_CHANGE- CLIENT_ERROR_RATE- ENDPOINT_ERROR_RATE- ENDPOINT_LATENCY- ENDPOINT_AVAILABILITY |
messagestring | Detailed message describing webhook |
old_statusstring | Previous status of the flow, value being one of: - DRAFT- PUBLISHED- DEPRECATED- BLOCKED- THROTTLED |
new_statusstring | Previous status of the flow, value being one of: - DRAFT- PUBLISHED- DEPRECATED- BLOCKED- THROTTLED |
alert_statestring | Status of the alert, value being one of: - ACTIVATED- DEACTIVATED |
requests_countinteger | Number of requests used to calculate metric |
errorsarray of objects | An array of error objects describing each error included in the alert. Error objects have the following properties: - error_count — Integer. Number of occurrences of the error. Example: 29.- error_rate — Integer. Error specific error rate. Example: 16.- error_type — String. The name of the error. See Webhook Alerts and Endpoint Error Types section of Error Codes page for details and suggestions for resolutions. |
p50_latencyinteger | P50 latency of the endpoint requests |
p90_latencyinteger | P90 latency of the endpoint requests |
error_rateinteger | Overall error rate for the alert |
Types of Webhook Notifications
Status Change Webhook
A notification is sent when the status for the flow changes, specifically when the flow is eitherPublished, Throttled, Blocked or Deprecated.
Draft as a default status.
Client Error Rate Webhook
Client error rate is approximate as it’s not available for all the client devices and regions. A notification is sent to you when the error rate for screen navigations on the client goes over one of the following thresholds and then again when it goes below these thresholds. Error rate thresholds:- 5%
- 10%
- 50%
Possible resolutions
- Check the errors listed in the alert and check the error codes reference guide for possible resolutions.
Endpoint Error Rate Webhook
A notification is sent to you when the error rate for endpoint requests goes over one of the following thresholds and then again when it goes below these thresholds. Error rate thresholds:- 5%
- 10%
- 50%
Possible resolutions
- Check the errors listed in the alert and check the error codes reference guide for possible resolutions.
Endpoint Latency Webhook
A notification is sent to you when the p90 latency for endpoint requests goes over one of these thresholds and then again when it goes below these thresholds. p90 latency thresholds:- 1s
- 5s
- 7s
Possible resolutions
- Improve responsiveness of your endpoint and aim to return response in less than 1 second.
Endpoint Availability Webhook
A notification is sent to you when the the endpoint availability goes below 90% threshold and then again when it goes above the threshold. The detection period for the alert is 10 minutes.Possible resolutions
- Ensure that your endpoint is available all the time and reachable from the internet.
- Check that it can correctly responds to health check requests.
Flow Version Freeze/Expiry warning Webhook
A notification is sent to you on the flow creation event if any of the versions used is about to be frozen. You won’t be able to publish the Flow after the version freezes.Possible resolutions
- Please migrate to the recommended version as soon as possible.
Possible resolutions
- Please migrate to the recommended version as soon as possible.

