Zapier

You need Calberry Pro and owner/admin access to webhooks, plus a Zapier plan that supports the apps used by your Zap. This uses Webhooks by Zapier, not an official Calberry app.

Capture the event shape

1. Create a Zap with Webhooks by Zapier → Catch Hook and copy its webhook URL.
2. Create a Calberry workspace webhook endpoint, initially selecting booking.created.
3. Use the Zapier URL for an initial synthetic sample and choose Send test event in Calberry.
4. Return to the Zap's Test tab and load the captured request. Check type, event_id and the nested data fields.

Do not create real CRM records from this sample. The payload has data.test=true.

Verify before business actions

Catch Hook parses incoming data; it does not automatically verify Calberry's HMAC protocol. Catch Raw Hook can expose raw input, but availability of the exact bytes, headers and a correct verifier still needs to be established.

For a clear production boundary, put your verifying receiver before Zapier, durably deduplicate there and forward only verified events to the Zapier URL. Change Calberry's endpoint URL to that receiver. Keep the Zap URL private, and do not expose the signing secret in public fields.

Build the Zap

Add filters that accept only the event types for this workflow and exclude data.test=true. Use a test CRM account for the synthetic sample.

For a booking workflow:

1. Find or create the contact using data.lead.email; map available name/phone fields.
2. Find or create the appointment activity with data.booking.id as its external key.
3. Map start/end, time zone and booking status. Add relevant answers and attribution, keeping missing values from overwriting existing data with blanks.
4. Record completion of the effect for this event_id.

Keep deduplication durable and safe under parallel execution. A separate search followed by create is not an atomic uniqueness guarantee. On failure, allow recovery rather than permanently marking an incomplete CRM action as done.

For reschedules and cancellations, subscribe to those events and update the same booking activity. For abandoned inquiries, require data.consent=true before follow-up.

Publish and monitor

Publish/turn on the Zap after testing. An off or deleted Zap can return a failed webhook response. Check Calberry's delivery history as well as Zapier's run history; HTTP acceptance does not prove a later action succeeded.

Test a deliberate real booking and changes, and recover destination failures from the retained event. Sandbox bookings do not trigger workspace webhooks. Replay keeps the event ID, so it must not create duplicate activities.

Current trigger details: Zapier's webhook-trigger guide.