How to Connect Booking Events to Your CRM with Webhooks

Flat fields you can map in any automation tool

In addition to these flat fields, the payload includes nested objects: customer (id, name, email, phone, address), staff, location, product, plan and metadata (e.g. the old date/time on a reschedule). Most automation platforms expose both the flat fields and the nested ones in their mapping UI.

1. 1

   Create a new Zap with a Webhooks trigger.

   Choose Webhooks by Zapier → Catch Hook as the trigger. Zapier generates a unique URL for you.

2. 2

   Copy that URL into Clickobook.

   Paste it into the matching Webhook URL field in Settings → Webhooks (e.g. Booking Created URL) and tick the event. Save.

3. 3

   Trigger a test booking.

   Make a real test booking. Zapier "catches" the payload and lets you confirm the trigger fired.

4. 4

   Map the fields and add an action.

   In the Zap editor, pick the flat fields like customer_name, customer_email, total_price and booking_date, then add an action — create a contact in HubSpot, a row in Google Sheets, or an invoice in QuickBooks.

5. 5

   Publish the Zap.

   Turn the Zap on. From now on, every matching booking event runs your automation automatically.

1. 1

   Create a workflow with a Webhook trigger.

   Add a Webhook trigger node and set the HTTP method to POST. n8n shows you a Webhook URL (plus a Test URL).

2. 2

   Paste the Production URL into Clickobook.

   Copy the workflow's Production URL into the matching Clickobook webhook field. The Test URL only works while the workflow is set to "Listen for test event", so use the Production URL for a stable integration.

3. 3

   Activate the workflow.

   Publish/activate the workflow so it is listening. Then make a test booking in Clickobook to capture a real payload.

4. 4

   Access the fields with n8n expressions.

   Right after the Webhook trigger you can reference incoming data directly, e.g. the customer name and price. From anywhere in the workflow, refer to the webhook's captured item by name.

5. 5

   Add your downstream actions.

   Connect the webhook to any nodes you need — log the booking, notify a chat channel, create a CRM record, or write to a database.

1. 1

   Create a scenario starting with a Webhook module.

   Add the Webhooks module with the Custom webhook option. Make generates a webhook URL and asks you to send a sample payload to "reclaim" it.

2. 2

   Paste the URL into Clickobook and trigger a test booking.

   Put the Make webhook URL into the matching Clickobook webhook field, then make a test booking. Make captures the JSON as the sample — confirm it and the module's data structure is set.

3. 3

   Map the fields into your next module.

   You can map the webhook's values — e.g. customer_name, total_price — into a Google Sheets "Add a row" module, a Slack "Post a message" module, or a CRM module.

4. 4

   Turn the scenario on.

   Save and run the scenario. Make listens continuously and fires it each time Clickobook sends an event.

1. 1

   Add a Webhook trigger to your Pabbly workflow.

   Search for the Webhook app and pick the trigger. Capture method POST. Pabbly shows you a webhook URL.

2. 2

   Paste the URL into Clickobook.

   Put the Pabbly URL into the matching Clickobook webhook field and enable the event. Save.

3. 3

   Capture the test payload.

   Click "Capture Webhook Response" and make a test booking in Clickobook. Pabbly stores the sample and makes the fields available in the mapper.

4. 4

   Map fields into your action steps.

   Map customer_email, service_name, total_price etc. into apps like Google Sheets, Gmail, Slack or a CRM action.

Recommended — verify the replay-proof signature (V2)

The V2 header is the strongest check: reject anything older than 5 minutes, then recompute the digest over <timestamp>.<body>. Because the timestamp is part of the signed string, an intercepted request cannot be replayed with a fresh t=.

$header = $_SERVER['HTTP_X_BOOKING_SIGNATURE_V2'] ?? '';

if (preg_match('/^t=(\d+),v1=([a-f0-9]{64})$/', $header, $m)) {
    $timestamp = (int) $m[1];

    if (abs(time() - $timestamp) > 300) {
        http_response_code(400); // too old — possible replay
        exit;
    }

    $expected = hash_hmac('sha256', $timestamp.'.'.$payload, $secret);

    if (! hash_equals($expected, $m[2])) {
        http_response_code(401); // bad signature
        exit;
    }
}

// Authentic and fresh — process the booking

Keep verifying X-Booking-Signature if you already do — it is still sent, unchanged.