Real-time booking events for your stack

skdul pushes signed webhooks to your endpoint the instant a booking is created, cancelled, or rescheduled. No polling, no lag.

TL;DR

Scheduling webhooks push real-time events to your endpoint when a booking is created, cancelled, or rescheduled. skdul signs every payload, retries with exponential backoff, and includes every custom question answer in the body. Webhook-integrated teams eliminate CRM sync lag entirely.

Key takeaways

  • skdul fires webhooks for booking.created, booking.cancelled, and booking.rescheduled events within 500 milliseconds.
  • Every payload is signed with HMAC SHA-256 so your endpoint can verify it came from skdul before processing.
  • Failed deliveries retry automatically with exponential backoff for up to 24 hours before giving the endpoint up.
  • Custom booking question answers, guest metadata, and event type details are all included in the payload.
  • Webhook-integrated teams eliminate CRM sync lag entirely and see data flow to Salesforce or HubSpot in real time.
  • Multiple endpoints can subscribe to the same event, so you can fan out to your CRM, data warehouse, and Slack at once.
0msTypical webhook delivery time
0hRetry window after failure
0Event types supported
0%Payloads signed with HMAC SHA-256

Why polling is broken

Polling the API for updates

You are running cron jobs every five minutes just to catch new bookings. That is wasted compute and stale data.

Delayed CRM sync

New meetings take 30 minutes to show up in Salesforce. Your SDRs chase cold leads while warm ones sit in the queue.

Manual handoffs that break

You rely on a Zapier filter that triggers on calendar events. Half the time it misses the update and nothing happens.

Webhooks built for production

Other schedulers treat webhooks as an afterthought with weak signing and no retries. skdul treats them as production infrastructure with HMAC signatures, 24 hour retry windows, and full custom field payloads. That is why teams replace their Zapier glue with a direct integration.

What real webhooks should do

Three event types

Subscribe to booking.created, booking.cancelled, and booking.rescheduled. Every event fires within 500 milliseconds.

HMAC SHA-256 signatures

Every payload is signed so your endpoint can verify authenticity before processing. Never trust an unsigned webhook.

Automatic retries

Failed deliveries retry with exponential backoff for up to 24 hours. Your endpoint can go down and still catch up.

Full payload context

Every payload includes guest info, custom question answers, event type metadata, and the full booking timestamp.

Fan-out to multiple endpoints

Subscribe multiple URLs to the same event. Send to your CRM, data warehouse, and Slack channel in parallel.

Three steps to live events

Go from signup to your first booking in no time.

1

Register your endpoint

Add your webhook URL in settings and pick which events to subscribe to. skdul returns a signing secret you store on your side.

2

skdul fires on every event

When a booking is created, cancelled, or rescheduled, skdul sends a signed POST to your endpoint within 500 milliseconds.

3

Verify and process

Your endpoint verifies the HMAC signature, processes the payload, and returns 200. Failed calls retry automatically.

skdul vs. Generic schedulers

Feature
skdul
Generic schedulers
HMAC SHA-256 signing
Sometimes
Automatic retries with backoff
Custom question answers in payload
Multiple endpoints per event
One only
Sub-second delivery
24h retry window
24h
None

Teams that replaced their glue code

We replaced three Zapier workflows with a single webhook endpoint. CRM sync dropped from five minutes to under a second.
AM

Alicia Moreno

RevOps Lead, Finch

Sync lag 5 min to 1 sec

HMAC signing was table stakes for our security review. skdul was the only scheduler that shipped it without a workaround.
RM

Raj Menon

Staff Engineer, Harbor

Passed SOC 2 review

Retries saved us during a two hour endpoint outage. Every booking still landed in our database when we came back online.
TW

Tamar Weiss

Backend Lead, Modulus

Zero lost events

AI-ready scheduling

Your calendar speaks two languages.

People book through your beautiful booking page. AI agents book through skdul's MCP server, browsing availability, scoring 100+ slots, and confirming the best time. Both paths lead to the same confirmed booking.

Ready to try it yourself?

Set up your booking page in two minutes. No credit card required.

Configure webhooks
Free forever plan MCP server included

Frequently asked questions

What events are available?

skdul supports booking.created, booking.cancelled, and booking.rescheduled. Each event includes the full booking payload, guest info, and custom question answers. More event types are added quarterly.

How do I verify a webhook is from skdul?

Every payload includes an HMAC SHA-256 signature in the X-Skdul-Signature header. Your endpoint computes the same signature using your signing secret and rejects the call if they do not match.

What happens if my endpoint is down?

skdul retries failed deliveries with exponential backoff for up to 24 hours. If your endpoint comes back within that window, you catch every event. After 24 hours the webhook is marked failed and logged.

Can multiple endpoints receive the same event?

Yes. You can register multiple webhook URLs and subscribe each to any combination of events. This lets you fan out to your CRM, warehouse, and Slack at the same time.

Are custom booking question answers included in the payload?

Yes. Every answer to a custom booking question is included in the webhook payload under the custom_answers field, keyed by question slug. No separate API call required.

How fast are webhooks delivered?

skdul fires webhooks within 500 milliseconds of the triggering event. In practice most teams see payloads arrive in their CRM or Slack within one second of a booking.

Ready to start?

Free to use. Set up in two minutes.

No credit card Free forever plan MCP server included
Ask AI about skdul