Help for owners
Calendly bookings are not showing up in my CRM
Short answer
Calendly tells other systems about bookings through webhooks. If your receiving address is down, slow or returns an error, Calendly retries for 24 hours and then disables the webhook, and it has to be recreated. Webhooks also only cover the people and events they were subscribed for. Check which of these applies before you re-enter leads by hand.
Does this sound like your situation?
- A meeting is on my calendar but the contact or deal is missing in the CRM.
- It works for some team members and not for others.
- It worked until the website, the CRM or a plug-in was changed.
- Cancellations and reschedules never update the CRM.
- Bookings from the routing form do not create anything.
Why does this happen?
The webhook was disabled after repeated failures
If Calendly gets a 3xx, 4xx or 5xx answer from your receiving address, it retries with growing gaps for 24 hours, and stops earlier if the booked event has already passed by then. If no message is delivered in that period the webhook is disabled and must be recreated. A server that was down, or a changed address, is enough.
Confirmed by developer.calendly.com
Your receiver answers too slowly
Calendly's webhook has a 10 second connection timeout and a 15 second read timeout, and recommends acknowledging at once and doing the slow work afterwards. An endpoint that talks to the CRM before answering can time out on a busy day.
Confirmed by developer.calendly.com
The subscription does not cover everyone or every event
A webhook subscription has a scope, either one user or the whole organization, and a list of events: invitee created, invitee canceled, and routing form submission. Only owners and admins can subscribe at organization scope, and routing form submissions support only organization scope. A subscription made by one team member covers that person's meetings only.
Confirmed by developer.calendly.com
The data arrives but the CRM rejects or duplicates it
The webhook only says who booked. A mapping that expects a field the booking form never asked for, or looks up contacts by an email that differs in case or spelling, ends in a rejected record or a second contact.
What can I do about it today?
- Make a test bookingBook a test meeting yourself with a fresh email address and see whether anything reaches the CRM. Note the time.
- List the missing bookingsNames, emails and booking times, from your Calendly scheduled events page. Enter them in the CRM by hand if the sales team is waiting.
- Find out who set up the connectionA person, a native integration or a tool such as an automation platform. Whose account created it matters, because a subscription can stop when that person leaves or loses access.
- Check whether anything changed on the receiving sideA new website, a moved server, a renewed certificate or a changed CRM field. Ask whoever manages them.
- Do not delete and re-create the connection yetThat removes the evidence of what failed. Send your developer the time of the test booking first.
When should I bring someone in?
- The connection was built by someone who has left.
- Bookings are missing from the CRM for days and leads are being lost.
- You have several team members and routing forms and cannot tell which ones are covered.
How do I handle it?
- List the webhook subscriptionsI read which subscriptions exist, their scope, events and state, using the Calendly API, and compare them with who and what should be covered.
- Trace one test booking end to endFrom the booking to the receiving address to the CRM call, I note where it stops: not sent, not received, answered with an error, or refused by the CRM.
- Answer at once, work afterwardsThe receiver acknowledges Calendly straight away and does the CRM work from a queue with retries, so timeouts and short outages lose nothing.
- Match contacts safelyContacts are matched by a normalised email and updated instead of duplicated.
- Alert when it stopsA message reaches you if bookings stop arriving, and the subscription state is checked on a schedule so a disabled webhook is noticed within hours, not weeks.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will Calendly resend bookings that failed?
Calendly retries a failing delivery for 24 hours. After that the webhook is disabled and you must recreate it. The page does not describe resending messages that were missed, so missing bookings are filled in from the Calendly scheduled events list.
Does this need a paid Calendly plan?
Calendly's webhook guide does not state which plan is required. Check the current plan page or ask Calendly support.
Is this the same problem as a native CRM integration failing?
It can look the same, but a native integration is managed inside the two products. This page is about connections made with webhooks or the API.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.