Working with Calendly?

Calendly routing or webhooks letting bookings slip? We sort it out.

Calendly is pleasant to set up and surprisingly hard to debug once routing forms, round robin pools and outbound webhooks are all firing at once. We follow the event ID from the booking page through to your CRM, find where the chain breaks, and leave you with a flow that no longer needs babysitting.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

calendly-webhook.log

still failing

What it is

Calendly at a glance

Calendly is a scheduling platform founded in 2013 by Tope Awotona. It replaces the back and forth of finding a meeting time by exposing a bookable calendar link that respects your availability, buffers, time zone and the rules you set around meeting types.

Beyond a personal link, the paid tiers add team event types, round robin and collective scheduling, routing forms that assign leads based on form answers, workflows that send SMS and email reminders, and a REST API with signed webhooks. It integrates directly with Google Calendar, Microsoft 365, Zoom, Google Meet, Teams, Salesforce, HubSpot and most of the usual CRMs, and gets embedded into marketing sites through a popup widget or inline iframe.

Type
Online scheduling and booking automation
First released
2013 as a consumer scheduling tool
License
Proprietary SaaS, free tier plus paid plans
Maintained by
Calendly, LLC (Atlanta, Georgia)
Typically used for
Sales demos, customer calls, interview scheduling, support bookings, consultant time

The honest version

Calendly pros and cons

No technology is all upside. This is where Calendly earns its place and where it tends to cause trouble.

Where Calendly is strong

  • Setup that non-technical teams can actually finishOperations and marketing can configure event types, buffers and availability without engineering help, so the booking flow ships in a day rather than a sprint.
  • Honest calendar integrationTwo way sync with Google and Microsoft calendars respects existing events and prevents double bookings, which matters more than any routing feature when a buyer is on the page.
  • Routing forms route by answerLead scoring, region, plan tier and account size can direct a prospect to the right rep instead of a shared pool, which usually lifts show rates.
  • Webhook payloads are well shapedThe v2 API gives you a signed webhook per event with the invitee, event type and tracking fields, so CRM automation is straightforward to wire up.
  • Embed widget handles the awkward bitsThe inline and popup embeds carry UTM parameters, hide fields and prefill names and emails from the parent page without a bespoke integration.
  • Workflows cut down no-showsSMS and email reminders, automated cancellation follow ups and post-meeting surveys run inside Calendly instead of inside another tool.

Where Calendly bites

  • Webhook subscriptions can quietly expireA v2 subscription tied to an OAuth token that gets revoked or rotated stops delivering with no dashboard warning, and bookings stop reaching your CRM until somebody notices.
  • Round robin has sharp edgesHost assignment uses current calendar load plus an internal tie-breaker, and when a pool is small or availability is tight, the same rep gets stacked while others sit idle.
  • Routing forms are a product in themselvesNon-trivial routing logic across multiple questions, salesforce lookups and fallbacks is easy to misconfigure, and a wrong answer silently drops the lead into a generic calendar.
  • Salesforce and HubSpot sync is not always losslessCustom fields, lead-to-contact conversion and activity logging each need mapping, and anything the native integration cannot handle has to be built on top with the API.
  • Embed scripts clash with strict CSPThe popup and inline widgets want inline scripts and third party domains that modern content security policies block by default, which makes the embed fail quietly in production.
  • Pricing climbs once teams and workflows arriveThe useful features, routing forms, Salesforce sync, SMS workflows and the API, sit behind Teams and Enterprise plans, and the per-seat cost adds up quickly for a sales floor.

Sound familiar?

Common Calendly problems we fix

The Calendly problems that bring people to us, and what you have once each one is fixed.

WebhookSubscription v2: 410 Gone

Webhooks stopped delivering to the CRM

A subscription tied to an OAuth token that was rotated, or an org-level v1 webhook that was migrated to v2 without being re-registered, so new bookings stop reaching your downstream pipeline.

Subscriptions re-registered and monitored

routing_form_submission did not match any route

Routing form drops leads into a default calendar

An answer combination that falls through every rule, or a Salesforce lookup that returns nothing because the email is unknown, sending the prospect to a generic page instead of the right rep.

Routes covering every answer path

round_robin: no hosts available

Round robin stacks the same rep every time

A small host pool, uneven calendar availability and a tie-breaker that keeps picking the first rep, so one person is booked solid and others are untouched.

Pool sized and weighted correctly

signature mismatch: webhook signature invalid

Webhook payloads are rejected as invalid

A signing key that was regenerated during a redeploy, or a handler using the raw body differently than Calendly's spec, so legitimate events are dropped as forgeries.

Signatures verified, events accepted

embed script blocked by CSP

Embed widget fails on the landing page

A content security policy that does not permit assets.calendly.com or an inline initialisation script, so the iframe never mounts and the booking button becomes a dead click.

Embed mounted under a tight CSP

invitee.canceled fired twice

Duplicate CRM activity from repeated webhooks

Calendly retries deliveries when your endpoint is slow, and a handler without idempotency writes two activities, two Slack messages or two Salesforce tasks for one cancellation.

Handlers idempotent, duplicates gone

OAuth token refresh failed: invalid_grant

API integration suddenly stops working

A refresh token that expired because the connected user left, or a scope change that invalidated the old grant, cutting off every API call the integration makes.

OAuth connection restored on a service account

What we do

Calendly help, from one broken webhook to a managed flow

Reach out when a single routing form is dropping leads, or hand over the whole booking surface.

Rescue
Bookings disappearing before they reach the CRM, embeds that will not render, or routing that sends every lead to the wrong team. We stabilise the pipeline first.
Webhook and API wiring
Signed v2 subscriptions, idempotent handlers and retry-safe downstream writes against Salesforce, HubSpot or an internal API.
Routing forms
Multi-step logic, Salesforce lookups, fallbacks and tracking parameters set up so every answer leads somewhere sensible.
Round robin and team setup
Pool sizing, weighting, collective events and interview panels tuned to real calendar patterns rather than defaults.
Embed hardening
Popup and inline widgets mounted under a strict CSP, with UTM capture, prefill and conversion tracking that survives a cookie banner.
Managed Tech
Delivery monitoring on every webhook, quarterly audit of routing coverage, and a named engineer when a sync silently falls over.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Calendly alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Calendly questions

Something else? Call+1 737 727 7327

Why have our Calendly webhooks stopped firing?

Almost always one of three reasons. The v2 subscription was tied to an OAuth token that got revoked, the signing secret was regenerated and the handler was never updated, or your endpoint has been returning non-2xx for long enough that Calendly gave up retrying. Each one shows up differently in delivery logs, and the fix is to re-register the subscription on an owned service user and wire in a dead-letter log so a future outage is visible within minutes.

How do we stop round robin from stacking the same rep?

Round robin picks the host with the most available capacity next, and a small pool with uneven calendars makes that look lopsided. Weight the pool explicitly, add buffers so a rep with a late meeting is skipped, and watch booking counts weekly rather than trusting the default to balance itself.

Can you connect Calendly to Salesforce with custom fields?

Yes. The native integration covers the basics; anything beyond standard contact and activity fields needs the Calendly API plus a middleware step or a Salesforce flow. We build the mapping, log every booking with the original routing answers, and make sure a failed sync lands in a queue rather than disappearing.

Why does our Calendly embed not render on the marketing site?

Usually the content security policy blocks assets.calendly.com or the inline init script. We relax the policy to the minimum that Calendly needs, move the init into an external bundle with a nonce, and verify the embed carries UTM parameters through the booking so attribution does not break.

How do we migrate from Calendly to another scheduler without losing bookings?

The event types, availability rules and workflows do not export cleanly, so the plan runs Calendly and the new tool in parallel for the overlap period. Existing bookings stay on Calendly, new ones go to the replacement, and the switch over happens once the parallel period shows the new tool is handling routing and reminders correctly.

How much does Calendly help cost?

Our estimate is free. Walk us through the routing, the integrations and what has stopped working, and we come back with a fixed price before anyone touches a configuration.

Free estimate

Calendly giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.