Webhooks in a CRM system are a mechanism for automated, real-time data transmission between services triggered by specific events.

Essentially, it acts as a "callback": instead of the CRM continuously polling external systems ("Any updates?"), either the CRM or the third-party services proactively dispatch a notification the moment a predefined event occurs.

How It Works

  1. An event occurs within our service (e.g., status change, user reassignment, courier change, etc.).

  2. A custom data packet (payload) is generated containing relevant information extracted from the order.

  3. An HTTP request (typically POST) is dispatched to a pre-configured destination URL (webhook) belonging to third-party systems.

Adding a Webhook

To add a new webhook, navigate to:
Settings — Webhooks — click the "+" icon in the bottom right corner — Add Webhook.

Webhook Architecture (What a Webhook Consists of)

  • Metadata — General information regarding the webhook.

  • Execution Conditions — Specific criteria that must be met for the request to be generated and dispatched.

  • Request — The recipient's destination URL where the data is sent, along with the designated HTTP method.

  • Payload and Headers — Key-value pairs containing transmission data, such as Order ID, Order Number, or Tracking Number.