Automate What Happens After a Booking with Chronock Webhooks

The work around a meeting often starts after the booking is created.

Someone may need to update a CRM record, notify a Slack channel, create a follow-up task, start an onboarding workflow, or sync the booking into an internal system. If those steps depend on someone checking Chronock and copying details by hand, the process becomes easy to miss.

Chronock outbound webhooks give your workspace a direct way to send booking lifecycle events to the tools you already use. When a booking is created, canceled, or rescheduled, Chronock can send a signed HTTPS request to your endpoint.

That turns scheduling from a standalone action into a trigger for the rest of your workflow.

What Chronock webhooks do

A webhook is an automated HTTP request sent from Chronock to a URL you control.

In the first version, Chronock webhooks focus on booking lifecycle events.

Event	When it is sent	Example workflow
booking.created	A new booking is confirmed	Add a CRM activity, notify the sales team, or create an onboarding task
booking.canceled	A booking is canceled	Close a task, notify the owner, or update an internal record
booking.rescheduled	A booking time changes through calendar ingestion	Update a downstream schedule, alert the team, or refresh a reminder

Each webhook endpoint belongs to a Chronock workspace. Workspace owners and admins can create endpoints, choose which booking events the endpoint receives, send a test event, and review delivery history.

Why this matters for scheduling operations

Scheduling tools are often connected to real business processes.

For a sales team, a booked demo may need to update the opportunity stage. For a recruiting team, a confirmed interview may need to notify a coordinator and update an applicant tracking workflow. For customer success, a canceled kickoff call may need to pause the next task.

Without webhooks, these steps usually become one of three things:

• A manual checklist someone has to remember
• A scheduled polling job that checks for changes later
• A direct integration that only works for one specific tool

Webhooks give you a more flexible starting point. Chronock sends the event when the scheduling change happens, and your receiving system decides what to do next.

That receiver can be a small internal API, an automation platform webhook trigger, a serverless function, or a workflow tool that accepts inbound webhooks.

Useful workflows to automate

Chronock webhooks are most useful when booking data needs to move into another system quickly.

Workflow	How a webhook helps
CRM activity updates	Attach booked meetings to leads, contacts, opportunities, or accounts
Team notifications	Post important bookings, cancellations, or time changes to Slack or another internal channel
Recruiting operations	Notify coordinators when candidate interviews are booked or moved
Customer onboarding	Start a kickoff checklist when a customer schedules the first meeting
Internal dashboards	Send booking events to a data pipeline or operational database
Custom reminders	Trigger reminders or preparation tasks from your own system

The important point is that the webhook is not limited to one destination.

If your team already has a custom admin system, you can receive Chronock events directly. If you prefer no-code automation, you can start with a platform that provides a webhook trigger and connect it to the tools you use.

What data is included

Chronock sends webhook payloads as JSON.

Booking lifecycle payloads include an event envelope with an event ID, event type, API version, creation time, and booking data.

{
  "id": "evt_7Z4A2rXh2B4V8nYcH9pQmN",
  "type": "booking.created",
  "api_version": "2026-07-06",
  "created_at": "2026-07-06T03:04:05.000Z",
  "data": {
    "booking": {
      "id": "7Z4A2rXh2B4V8nYcH9pQmN",
      "status": "confirmed",
      "start_time": "2026-07-07T01:00:00.000Z",
      "end_time": "2026-07-07T01:30:00.000Z",
      "timezone": "Asia/Tokyo",
      "slot": {
        "id": "2dK8eV6hKp9mQr4ZyT1xAb",
        "title": "Product Demo"
      },
      "meeting_tool": "google_meet",
      "meeting_url": "https://meet.google.com/example"
    }
  }
}

For rescheduled bookings, Chronock also includes the previous start and end time. That makes it easier for your receiving system to update the right downstream record instead of treating the change as a brand-new meeting.

By default, payloads avoid participant names and email addresses. If an endpoint needs those details, an owner or admin can enable participant details for that endpoint.

That default matters. Many automations only need to know that a booking exists, when it happens, which slot it belongs to, and where the meeting URL is. Keeping personal details opt-in reduces accidental data exposure.

Delivery logs make webhook behavior visible

Webhook automation is only useful if you can see what happened.

Chronock records webhook deliveries so admins can review whether an event succeeded, failed, or is waiting for a retry. This is useful when you are building a new workflow and want to confirm that Chronock sent the request your receiver expected.

The test delivery action helps with setup before real bookings start flowing. Create the endpoint, send a test event, verify the receiver, then enable the workflow with more confidence.

The manual test uses the endpoint.verification event with endpoint data instead of booking data. It is sent regardless of which booking events are selected for the endpoint.

When a delivery fails, Chronock retries it with backoff. A temporary outage in your receiving system should not mean the booking event is lost immediately.

Chronock stores each completed booking event payload durably with the corresponding booking lifecycle operation before asynchronous delivery begins. Delivery uses at-least-once, not exactly-once, processing, so the same request can arrive more than once after a timeout or another ambiguous delivery outcome. Make your receiver idempotent and deduplicate retries with Chronock-Webhook-Id.

How to set up a webhook endpoint

You need workspace owner or admin permissions to manage webhooks.

The basic setup flow is:

1. Open Chronock and go to the workspace integration settings
2. Create a webhook endpoint with an HTTPS URL
3. Choose which booking events the endpoint should receive
4. Copy the endpoint secret when it is shown
5. Configure your receiver to verify Chronock signatures
6. Send a test webhook and check the delivery log

Endpoint secrets are shown once when the endpoint is created. Store the secret in your receiving service or automation platform so it can verify webhook signatures.

Verifying that a webhook came from Chronock

Chronock signs webhook requests with HMAC-SHA256.

Your receiver should verify the signature before trusting the payload. Chronock sends headers such as:

Header	Purpose
Chronock-Webhook-Id	Identifies the delivery
Chronock-Webhook-Event-Id	Identifies the webhook event
Chronock-Webhook-Event-Type	Shows the event type, such as booking.created
Chronock-Webhook-Timestamp	Helps protect against replayed requests
Chronock-Webhook-Signature	Contains the HMAC signature

For production workflows, verify the signature and reject old timestamps. This protects your receiver from accepting requests that did not come from Chronock or were replayed later.

Chronock also requires webhook endpoint URLs to use HTTPS and validates endpoint addresses to reduce server-side request forgery risk.

What webhooks are not

Webhooks are a flexible integration point, but they are not the same as a full native integration.

The first Chronock webhook implementation does not include:

• Inbound webhooks from other services
• A Zapier REST Hooks app with subscribe and unsubscribe APIs
• A packaged n8n community node
• Make or Yoom marketplace listings
• Per-room or per-slot filters
• Participant details enabled by default

That boundary is intentional. The first step is a durable webhook core: endpoint management, persisted booking events, signed delivery, bounded endpoint-delivery retries, test delivery, and delivery logs.

Native marketplace integrations can build on top of that foundation later.

Start with one high-value automation

The easiest way to use webhooks is not to automate everything at once.

Start with one workflow where a missed booking update costs time. For example:

• Notify a sales channel when a demo is booked
• Add a CRM note when a booking is created
• Close an internal task when a booking is canceled
• Update a customer onboarding record when a kickoff call is rescheduled

Once that workflow is reliable, add the next one.

Turn bookings into workflow triggers

Chronock already helps people find and book available times from connected Google Calendar and Microsoft Outlook calendars. Webhooks extend that value after the booking happens.

Instead of treating a confirmed meeting as the end of the scheduling flow, you can use it as the start of the next step: notifying the right people, updating the right records, and keeping downstream systems in sync.

If your team wants scheduling changes to trigger the rest of your operation, Chronock webhooks give you a practical place to start.

Get started with Chronock for free →