Skip to main content
Every Webhook Workflow tracks its own delivery stats, so you can confirm messages are actually going out — not just assume the workflow is working because it saved successfully.

​
Viewing the stats

Webhook Workflows list under Chatbot Manager Automation, with several workflows and their Sent, Delivered, Opened, Failed, Skipped, and Unreached stats, and a Workflow Report button
Go to Chatbot Manager → Automation → Webhook Workflows. Each row shows real-time counts for that workflow:

​
The full report

Click Workflow Report on any workflow for a call-by-call breakdown:
WhatsApp Webhook Workflow Report table with columns Workflow, Phone Number, Status, Response, Triggered at, Scheduled at, Response, and Webhook Data
Each row shows the Workflow it belongs to, the Phone Number the message went to, its Status (e.g. Completed), Response (e.g. Success), the Triggered at / Scheduled at timestamps, and the raw Webhook Data payload — useful for confirming exactly what data a specific call sent.

​
Troubleshooting common issues

  • High Failed count — check that your WhatsApp number is active, your message template is still approved, and the Phone Number field in the workflow’s response mapping is correctly set.
  • Everything shows as Skipped — review the conditional rules in the workflow’s automation settings — the webhook data may not match the format or values your rules expect.
  • Nothing is arriving at all (0 Sent) — confirm the callback URL is entered correctly in the third-party app’s webhook settings, and that a test webhook has been captured and verified.

​
Frequently asked

Check its row in Chatbot Manager → Automation → Webhook Workflows — a rising Sent / Delivered count confirms real calls are coming through and messages are going out.
Its conditional rules are filtering most calls out. Open Webhook Automation Settings on that workflow and check whether the rule’s field/operator/value actually matches what the third-party app sends.
Open Workflow Report and check the Webhook Data column on that row — it shows the raw payload received for that call.
Confirm the callback URL is pasted correctly into the third-party app’s webhook settings, and that you’ve successfully captured and verified a test webhook — see Create a Webhook Workflow.