Workspace webhooks

Workspace webhooks send supported events from your workspace to an external tool. They are configured once per endpoint, independently of email sequences. You need Pro, access to webhooks and an owner/admin role to make changes.

Create an endpoint

1. Prepare a publicly reachable HTTPS receiver. It must accept requests directly; Calberry does not follow redirects or allow private-network destinations.
2. Open the workspace menu → Development → Webhooks.
3. Choose Create endpoint and enter the HTTPS destination URL.
4. Select the events you need. All nine active events are selected by default; at least one is required.
5. Save the endpoint and copy the secret shown now. Store it securely in your receiver for signature verification. It is not shown in endpoint lists or delivery logs.

Choose the smallest event set that serves your integration. A CRM that only needs confirmed booking creation may not need incomplete-form events.

Test the receiver

Choose Send test event. Calberry queues a synthetic event with data.test=true; it contains no real contact or booking data. The queued confirmation does not mean the destination accepted it.

Open Delivery history and inspect the payload, HTTP result and attempts. The test uses the same signing and delivery path as normal webhooks. Test the receiver's signature check and test-event branch before enabling business actions.

Dashboard sandbox bookings do not trigger workspace webhooks. Use Send test event for this test, then make a deliberate real booking if you need to validate a complete business workflow.

Filters and history

Events are delivered only from the time the endpoint is created. There is no historical backfill. Review event-specific conditions in the event reference.

In Delivery history, filter by endpoint and status. Pending is queued, Delivering is in progress, Delivered records an HTTP success, and Dead-Letter needs investigation. A successful HTTP response proves acceptance by the receiver, not that a downstream CRM action completed.

Use replay only after checking the receiver's deduplication and correcting the failure.

Pause, delete and rotate

Pause an endpoint to stop delivery attempts. Activate it again before sending a test or replay. Deleting an endpoint stops further deliveries while retaining its history.

Rotate secret replaces the current signing secret immediately. Update the receiver with the new secret. An attempt already running may still use the old one, so accept both during the transition and remove the old one afterwards. Rotation does not rewrite event IDs or previously signed bodies.

If Pro ends, keys and endpoints pause instead of being deleted. After an upgrade, webhooks continue without backfilling events from the paused period.

Personal data

Calberry stores lead and booking data in the EU. Webhooks send contact details, answers and attribution to destinations chosen by you. Those copies are stored wherever the destination stores them and may leave the EU. Restrict access and retention in the receiving tool.

For endpoint-management request schemas, use the generated API reference.