Webhook Workflow Reporting in ChatSyncs
How to read a Webhook Workflow's delivery stats, open the call-by-call report, and troubleshoot a workflow that isn't sending or shows a high failure rate.
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#
Go to Chatbot Manager → Automation → Webhook Workflows. Each row shows real-time counts for that workflow:
| Column | What it means |
|---|---|
| Sent | Messages ChatSyncs attempted to send. |
| Delivered | Messages successfully delivered to the recipient's WhatsApp. |
| Opened | Messages the recipient opened (for templates that support read receipts). |
| Failed | Messages that failed to send. |
| Skipped | Calls that didn't result in a message — usually because a condition rule wasn't met. |
| Unreached | Messages that couldn't reach the recipient. |
The full report#
Click Workflow Report on any workflow for a call-by-call breakdown:
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#
Frequently asked#
How do I know if a Webhook Workflow is actually working, not just saved?
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.
A workflow shows a lot of Skipped calls — why?
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.
Where can I see exactly what data a specific call sent?
Open Workflow Report and check the Webhook Data column on that row — it shows the raw payload received for that call.
My workflow shows 0 Sent — what should I check first?
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.
Was this page helpful?
Still stuck? Open a support ticket and our team will help.