Integrations

Integration: Calendly

Calendly integration for Webflow, Framer and Next.js sites

A Calendly integration puts booking on your website instead of behind a link: the right embed on the right page, details prefilled from your form, campaign data carried into the booking, and every scheduled meeting tracked as a conversion. We set it up on Webflow, Framer and Next.js sites as part of our $8,000 website package, so a demo request ends in a real meeting.

Why Designify

  • Inline, popup or link: the embed chosen per page, not pasted everywhere
  • Name, email and UTMs carried from your form and URL into the booking
  • Booked meetings tracked as conversions, not just clicks on a button
  • Routing set up when different visitors should meet different people
  • ATQLeads
  • Update AI
  • LeanScale
  • CSSinc.ai
  • HeyInterests
  • JuPay
  • PowerPulse
  • WireFox
  • Reactive Growth
  • Minexa.ai
  • SmileJoy
  • LFG Business Group
  • ORBITX
  • Funnels.com
  • Sentipi
  • UNIVIT Research
  • LifeLink
  • Wolf Automation
  • Shaqir Hussyin
  • Q-TARO
  • MainPlume

What does a Calendly integration do on a marketing site?

A Calendly integration lets visitors pick a meeting time without leaving your site, and it tells your analytics and CRM that the meeting happened. Without it, a demo button sends people to a separate Calendly page, campaign data is lost on the way, and your reports show clicks rather than booked calls.

  • Booking on the page: the scheduler sits inside your demo or contact page, or opens over it.
  • Prefill: details the visitor already typed, such as name and email, appear in the booking form so they don't type them twice.
  • Campaign data: UTM parameters from the landing page travel into the booking, so you can see which campaign produced each meeting.
  • Conversion events: a scheduled meeting fires an event your analytics can count.
  • Routing: answers to a few questions decide which rep, team or event type the visitor sees.

Most of this is configuration, not code. The work is deciding where booking belongs in the journey and making sure the data survives each step. Our guide to conversion tracking for lead-gen websites covers the measurement side.

Which Calendly embed should you use on each page?

Use an inline embed where booking is the page's main job, and a popup where booking is one option among several. Calendly's developer docs describe three embed styles: an inline widget, a popup widget that floats on the page, and a popup opened from your own button or link.

Embed

Best for

Watch out for

Inline

A dedicated demo or book-a-call page

Heavy on load, so keep it off pages where most visitors won't book

Popup from your button

Pricing, product and home pages with a demo CTA

Load the script when the button is used, not on every page view

Floating popup widget

Sites where booking is the single goal

It competes with chat widgets and cookie banners for the same corner

Plain link to Calendly

Emails, signatures, low-stakes pages

Visitors leave your site and campaign data can be lost

On most startup sites we use one inline embed on the demo page and a button-triggered popup everywhere else. That keeps the scheduler's script off pages where it slows things down, which matters for INP. Our audit method for third-party scripts explains why each embed should earn its place.

How does Calendly work on Webflow, Framer and Next.js?

All three platforms can host every Calendly embed. The difference is how much control you get over loading, styling and the events the embed sends back.

Task

Webflow

Framer

Next.js

Inline embed

Embed element with Calendly's code

Embed component with Calendly's code

A client component that loads Calendly's widget

Popup from a button

Custom code on the page or site

Custom code or a code component

Loaded on click with the Script component or dynamic import

Prefill from a form

Custom script reading the form values

Code component or custom script

Passed directly from form state

Booking event to analytics

Custom script listening for Calendly's message

Custom script or code component

Listener in the same component as the embed

Script loading control

Limited

Limited

Full

Webflow and Framer handle the embed itself well. The extras, such as prefill and event tracking, need a few lines of custom code on both, which we write and test. On Next.js we load the widget only when it's needed and keep the listener next to it, the pattern described in our guide to forms and integrations on Next.js marketing sites. Platform options change, so we check Webflow's and Framer's current embed features at the start of each project.

How do you track Calendly bookings as conversions?

Track the booking itself, not the click on the button that opens Calendly. Calendly's developer docs describe how the embed posts messages to your page, including a calendly.event_scheduled message when a meeting is booked, and that's the event to send to GA4 and your ad platforms.

  • Listen for the scheduled event and push it to your data layer as a named conversion.
  • Check the message origin so only messages from Calendly are counted.
  • Carry UTMs into the booking. Calendly's help center says you can add UTM parameters to the embed code, and they show up in your reports. If the visitor lands on one page and books on another, store the UTMs on arrival and pass them in.
  • Keep one source of truth. Count the meeting once, in one tool, and let the others import it.

Our guides to UTM parameters and GA4 not tracking conversions cover the naming and the debugging side.

You need routing once different visitors should meet different people. Routing asks a few qualifying questions, or reads an existing form, and then shows the right event type, rep or team. A single shared link sends an enterprise lead and a student to the same calendar.

Calendly's help center documents routing from HubSpot, Marketo and Pardot forms, and routing forms you build inside Calendly and embed on your site. Those form integrations may need a higher-tier plan, so check Calendly's current plan page before you design around them. When routing outgrows a scheduler, for example round-robin with account ownership from Salesforce, a dedicated tool like the one on our Chili Piper integration page may fit better.

Hypothetical example: routing a demo form

For example, suppose a SaaS company asks two questions on its demo form: company size and region. Under 50 employees books a 20-minute product walkthrough with any available rep. Over 50 in North America goes to the US enterprise team, and everyone else goes to the international team. Each path ends in Calendly, with the visitor's name, email and answers already filled in.

What are the common Calendly embed mistakes?

Most Calendly problems are invisible: the scheduler works, but the data or the speed doesn't. These are the ones we check for.

  1. Counting clicks as conversions: the demo button fires a goal, so reports look healthy while bookings stay flat.
  2. Asking twice: a form collects name and email, then the scheduler asks again because nothing was prefilled.
  3. Lost attribution: UTMs dropped between the landing page and the booking page.
  4. Script on every page: the widget loaded site-wide, slowing pages where nobody books.
  5. Corner clutter: the floating widget, a chat bubble and a cookie banner stacked on top of each other on mobile.
  6. No next step after booking: a dead confirmation screen with nothing to prepare.

How do we set up Calendly on your site, and what does it cost?

  1. Map the booking paths

    We agree which pages offer booking, which embed each one uses, and whether visitors need routing.

  2. Design the moment

    The demo page, form and confirmation are designed together, so booking feels like part of the site.

  3. Wire it up

    Embeds, prefill, UTM capture and the booking event, on Webflow, Framer or Next.js.

  4. Test every path

    Real bookings from tagged and untagged visits, checked in Calendly, GA4 and your CRM.

  5. Hand over

    A short note on changing event types, routing rules and where to see booked meetings in your reports.

Calendly setup is part of our website package, $8,000 fixed for up to six pages including copy, design and the build. We designed and built the site for LeanScale, a data company. If you need only the demo page, see landing page design. If your CRM is HubSpot, our HubSpot integration page covers that side. The next step is a free 30-minute call.

Related work

What our clients had to say

Pricing

Fixed prices for fixed scopes, agreed before we start, or a monthly retainer when you need a team on call. All prices in USD.

Website

A multi-page marketing site, written and designed by us, developed in Next.js and animated.

What’s included

  • Up to 6 pages, written, designed and developed
  • Custom design, never a template
  • Built in Next.js, fully responsive
  • Animations and interactions
One-time, up to 6 pages

$8,000

+$500 for each extra page
Book a call
4.92 on Contra · 11 reviews

Free 30-minute intro call, no commitment

Not sure yet? Try a week together.

One week of design and development, so you can see how we work before you commit.

$1,000Book a trial week

Frequently asked questions

Do I need a paid Calendly plan to embed it on my website?
No. Calendly's embeds work on its free plan, which covers a basic inline or popup scheduler. Features such as multiple event types, routing forms, team scheduling and some integrations sit on paid tiers. Plan contents change, so check Calendly's current pricing page, and tell us on the intro call which plan you're on so we design the booking flow around what you actually have.
Will a Calendly embed slow down my website?
It can, because the widget loads its own scripts and styles. The fix is to load it only where it's used: an inline embed on the demo page, and on other pages a popup that loads when someone clicks the button. Done that way, the scheduler doesn't affect pages where nobody books, and your Core Web Vitals stay where they were.
Can I style the Calendly embed to match my brand?
Partly. Depending on your plan, Calendly lets you set colors, and its embed options can hide some page details, but the scheduler's layout and fonts stay Calendly's. We design the space around it, the heading, the copy and the confirmation, so the page feels like yours. If full visual control matters more, you'd need a custom booking flow built on a scheduling API.
Can Calendly bookings go straight into my CRM?
Yes. Calendly has native integrations with CRMs such as HubSpot and Salesforce, so a booking can create or update a contact and log the meeting. The website's job is to pass clean data into Calendly: prefilled name and email, campaign parameters and form answers. We set up the site side and check the record that lands in your CRM after a test booking.
What's the difference between Calendly and a form followed by an email?
A form followed by an email asks the visitor to wait while someone replies and suggests times. Calendly lets them book in the same visit, while they're still interested. For high-intent pages like a demo request, booking straight away usually removes a step. For low-intent enquiries, a simple form is often enough and keeps your team in control of who gets a call.

Ready to qualify better leads and boost brand perception?

We take craft seriously over at Designify Studio. We do deep research and do what we do best - pay attention to the smallest details and make sure we speak to the right audience.

Schedule Call