Webhook Logs
Every notification the addon sends is recorded in Webhook Logs. Use this screen to confirm that messages were delivered, troubleshoot failures, and inspect the exact payload that triggered each message.
Introduction
When an incoming webhook fires a WhatsApp notification, the addon stores a log entry with the recipient, the send and delivery status, the raw payload received, and the fields it extracted for the template. This gives you a complete audit trail without needing access to your ecommerce platform or the WhatsApp dashboard.
Open it from the sidebar under Ecommerce → Webhook Logs.
The Logs List
The list shows one row per notification, most recent first.
| Column | Description |
|---|---|
| # | Row number |
| Webhook Name | The webhook endpoint that triggered the notification |
| Recipient Phone | The phone number the WhatsApp message was sent to |
| Send Status | Whether the message was accepted and sent (e.g. Sent) |
| Delivery Status | The WhatsApp delivery state — Delivered, Read, etc. |
| Created At | When the notification was generated |
| Actions | View the full log details, or Delete the entry |
Send Status vs. Delivery Status
- Send Status reflects whether WhatsMark accepted and dispatched the message.
- Delivery Status reflects what happened on WhatsApp afterwards — Delivered (reached the device) or Read (opened by the recipient).
List Tools
| Tool | Purpose |
|---|---|
| Search | Filter logs by webhook name or recipient phone |
| Columns | Show or hide columns in the table |
| Default | Reset the table layout to its default view |
| Clear Logs | Remove all log entries at once |
Viewing Log Details
Click View on any row to open the full log. The details page is split into four panels.
Webhook Log Details
The message-level summary:
| Field | Description |
|---|---|
| Status | Send status of the message (e.g. Sent) |
| Date | Date and time the message was sent |
| Delivery Status | WhatsApp delivery state (e.g. Read) |
| Recipient Phone | The number the message was sent to |
| WhatsApp Message ID | The unique wamid returned by WhatsApp for the message |
Webhook Endpoint
Identifies which endpoint received the incoming request:
| Field | Description |
|---|---|
| Name | The webhook's display name |
| Webhook Endpoint ID | Internal ID of the endpoint |
| Webhook Endpoint | The full webhook URL that received the request |
| Method | The HTTP method used (e.g. POST) |
Webhook Payload
The complete JSON payload received from your ecommerce platform, exactly as it arrived. Use this to confirm the platform sent the data you expect and to find the correct paths for your merge fields.
Extracted Fields
Shows the fields the addon extracted from the payload and mapped into the template, with each value's original_path (the merge field you configured, e.g. @{contact.firstname}) and its normalized_path. A Processed badge confirms the mapping ran successfully.
Troubleshooting Tip
If a template variable comes through empty, compare the Extracted Fields panel against the Webhook Payload. A mismatch usually means the merge-field path doesn't match the JSON structure your platform actually sends.
Related
- Template & Media Mapping — configure the merge fields shown in Extracted Fields.
- Automatic Contact Save — create CRM contacts from the same payload.
- Webhook Management Dashboard — create and configure webhook endpoints.