Gemin Get in touch

Calendly with Webflow

Calendly with Webflow

A booking link is easy. What usually goes missing is everything either side of it: which campaign brought them, whether the meeting was kept, and what your CRM knows the moment it is booked. I wire the booking so the record is complete without anyone retyping it.

Book a call

Scheduling work like this usually takes 1–3 days

What the integration covers

What syncs, and what needs a decision.

Wired up

  • Inline or popup embed on your own page rather than a link off-site
  • Name, email and campaign parameters prefilled, so the form is half done on arrival
  • UTM values carried through the booking and into the CRM record
  • Webhooks on booked and cancelled, so the CRM reflects reality rather than intent
  • The widget loaded on interaction, not on every page view

Flagged upfront

  • The embed is an iframe dropped into a Webflow embed element, so it brings its own script and is worth deferring until someone wants it
  • Webhooks and routing forms sit on paid tiers, so the plan decides how much of this is possible
  • Attribution has to be passed in deliberately; a bare embed loses the campaign at the handoff
  • Hiding the cookie banner does not stop the cookies, so on a consent-gated site the widget waits for the answer

Most Calendly setups on a marketing site are a link, and a link loses everything you knew about the visitor. The embed accepts prefill and UTM parameters, so the person arrives with their details filled in and the booking carries the campaign that produced it. That is usually the whole reason to embed rather than link.

Loading is the other half. The embed is an iframe with its own script, and on a page where most visitors never book, that is a cost paid for nothing. I render the button immediately and load the widget on the first click, which keeps the booking one tap away and off the critical path.

The consent parameter is worth knowing about, because it is widely misread. Hiding Calendly’s cookie banner hides the banner and nothing else — the cookies still set. On a site with a consent gate the honest build is the one Calendly itself recommends: do not load the widget until someone has said yes, which is the same deferred load the performance argument already wanted.

Webhooks close the loop. A booking creates or updates the CRM record as it happens rather than on the next sync, and a cancellation does the same, which is the difference between a pipeline that reflects reality and one that reflects intent.

Other integrations

Wire up something else?

Reach out and see if we are a good fit.

Start a conversation

Currently booking two to four weeks out.