Webhooks
Create, edit, delete webhooks.
Last updated
Create, edit, delete webhooks.
Last updated
The Webhooks page (found under 'Settings') inthe ZAP~APP allows you to create webhooks as well as edit and delete them.
A webhook is a way for an application to provide other applications with real-time information. Webhooks provide a powerful mechanism for integrating different services and enabling automation in a streamlined manner.
Any created webhooks also have the option to view the logs giving you more insight into any successes and errors.
To add a webhook, simply click 'Add New Webhook'. A slide out will then appear allowing you to create your webhook. You'll have the ability to set the following values.
Name - An easily recognisable name for the webhook being created. Target URL - The URL endpoint to which events should be sent. Event Trigger - When the specific event happens in the ZAP APP, it triggers the webhook. Basic Auth Username - The username built into the HTTP protocol. Basic Auth Password - The password built into the HTTP protocol. HTTP Headers - These let you and the server pass additional information with an HTTP request or response. They're most often used for authentication purposes. Status - Determines if the webhook is active or inactive.
Once you're done, click 'Create Webhook' and your details will be saved.
When creating a webhook, you have different options for Event Trigger.
New Submission - This triggers when a new submission is uploaded to the ZAP~APP either manually or via the ZAP API. Records Rejected - This triggers during the PAF and Cleanse process and includes any records removed from the send due to failing these checks. Zap Returned - This triggers when a ZAP is returned to sender and includes the recipients details. QR Code Scanned - This triggers if your design contained a QR code, when scanned by the recipient it'll confirm who scanned it and when.
To edit a webhook, click on the edit icon on the webhooks page and you can amend any details you need.
To delete a webhook, click on the bin incon on the webhooks page, you'll see a pop up asking if you're sure you want to delete.
To view the logs for one of your webhooks, click on 'View' from the webhooks page. This will then give you an overview of all logs for that webhook with a quick visual of the Status Code for each event.
You can filter this page based on Target URL, Status Code, From and To Dates and Time.
To see the request and response for each log, click on the view logs icon.
When viewing a log, you'll be able to see the request header, a webhook request header is part of the HTTP request sent to a specified URL endpoint when an event triggers the webhook. These headers contain data about the request and help ensure that the receiving server can interpret the incoming data correctly and securely.
You'll also be able to view the request body, a webhook request body contains the actual data payload sent from the source application to the receiving server when an event triggers the webhook. This payload includes detailed information about the event and any relevant data associated with it.
You're also able to view the webhook response header, A webhook response header is part of the HTTP response sent by the server that receives a webhook request. These headers provide information about the response and can include status information, content type, and other metadata.
A webhook response body is the data returned by the server receiving a webhook request. It provides feedback about the result of the webhook processing.
