You can use different methods to verify if a webhook is configured correctly: 

• As an initial check, make a change in the table that is set in the event definition and check if this action triggers the webhook to send a message. 
• In the list of events for a given webhook, view statistics for messages, calls, and errors related to a specific event: 
  
  1. In the Activity period list, select the timeframe for which you want to view the delivery statistics. 
  2. In the Messages column, check how many webhook messages were created. 
  3. In the Calls column, verify how many POST requests the webhook sent. 
  4. In the Errors column, confirm whether any errors occurred for this event. 
• For detailed analysis, use the prefiltered logs for webhooks and events available in the More menu for webhooks and events. You can also click the values in the Messages, Calls, and Errors columns to open the logs filtered for that event (applies only to values that are other than 0). In the logs, you can then view the details of any webhook message, including the request and response content, by hovering over a row and clicking the Details button. Learn more about logs.

Note: If you set short retention for logs, the numbers of messages, calls, and errors in the lists of webhooks and events might be different than the number of corresponding logs.

Note: In rare cases, the confirmation that a webhook message has been received might not arrive before the webhook times out. As a result, the logs might show a failed status, even though the webhook was delivered successfully. To avoid this situation, configure your target service to send the confirmation first, before verifying the payload.