Make

You need a Calberry Pro workspace, owner/admin access to webhooks and a Make account with the modules your scenario uses. This recipe uses Make's generic Webhooks app, not a native Calberry connector.

Receive a sample

1. Create a Make scenario with Webhooks → Custom webhook and copy its generated HTTPS URL.
2. Start Run once so Make can detect a sample.
3. In Calberry, create a workspace webhook endpoint and select booking.created.
4. For initial payload discovery, point it at the Make URL and choose Send test event. Check both Calberry's delivery history and the captured Make bundle.

Before processing real data, implement signature verification. A Custom webhook module does not, by itself, prove Calberry authenticity. If you cannot verify the original bytes and header in your setup, change the Calberry endpoint to your verifying receiver and have it forward accepted events to Make. Keep the Make URL private.

Filter and map

Add filters before CRM actions:

• Accept only type = booking.created for this route.
• Exclude data.test = true from real business effects. Use a separate test destination while mapping.
• Deduplicate on event_id in a durable event store. A check-then-create sequence without a unique constraint can race; serialize or use a receiver with an atomic unique-key claim.

Find or create the contact using data.lead.email, within the correct workspace/customer context. Map the name and phone only when supplied. Create/update the meeting activity using data.booking.id as its external identity. Map start, end, zone and status from data.booking, answers from data.answers and campaign information from data.attribution.

Do not generate another activity for both lead.captured and booking.created. Do not send follow-up for an abandoned lead unless data.consent is true.

Extend to changes

Subscribe to booking.rescheduled and booking.cancelled, then route on type. Update the existing activity by booking ID; do not create a new deal for each change. Keep event IDs for effect deduplication and booking IDs for the business record: they serve different purposes.

Enable the scenario's schedule for live processing after testing. Confirm a deliberate real booking, a reschedule and a cancellation in the scenario history and CRM. Sandbox bookings do not send workspace events.

Recover failures

Make can acknowledge a webhook before every later module completes. Calberry may therefore show Delivered while a CRM step failed. Monitor Make's execution history and configure error handling/recovery for destination failures. Keep accepted events until processing is complete; replay from Calberry only with deduplication in place.

Module setup and scheduling details: Make's webhook documentation.