Webhooks represent a system of automated communications between applications, functioning when a particular event occurs. These communications consist of a payload, essentially a message that is dispatched to a designated URL – a unique address that is equipped to handle such transmissions.

The purpose of webhooks is to establish a bridge between disparate applications, allowing them to communicate effectively. When an event is triggered within the initiating application, it packages information pertaining to this event into a serialized format, which is then conveyed to the webhook URL associated with the receiving application. The latter application is the one intended to take a specific action in response to the event data procured from the initiating application.Upon receiving the data, the action application typically issues a callback response.

To illustrate the process of webhooks in action, consider this scenario: An individual visits your online store, places an order for stationery valued at $10, and completes the purchase. At this juncture, an event has been triggered—a signal that something of significance has occurred which necessitates notification. This is the cue for the webhook.

The question then arises: to whom does the application transmit this information? In the context of webhooks, it is imperative that the originating application—the eCommerce platform, in this scenario—is configured with the URL of the destination application. This is the endpoint that is poised to receive the data and, based on this information, enact the subsequent requisite processes.

At present, to set up a custom webhook, initiate a request through the Integrations page.

After your request has been submitted, a product specialist will be assigned to your case. They will reach out to you to discuss the next steps.

In case you have any further queries, feel free to write to us at [email protected] and we’ll respond at the earliest.