Connect Zoom to Calendly: a room ready before the guest arrives

Someone books a call through a Calendly link, the confirmation email goes out, and the line where the meeting room should be is empty. Or the room is there but the passcode is missing, or the link points at a Zoom account that was closed two jobs ago. The fix is almost never in the booking page. It is in how the two accounts are joined, and in a handful of Zoom settings that decide what the generated link looks like.

This walks through connecting Zoom to Calendly, then through the failures that show up later: the ones that only appear on team event types, the ones that come from Zoom's own account limits, and the one that happens because a single variable was deleted from an email template.

What the connection actually does

Once Zoom is authorized, Zoom appears as a location option on event types. When an invitee picks a time, Calendly creates a real Zoom meeting through Zoom's API and writes the join details into the calendar invitation and the confirmation email. The meeting also shows up in the Upcoming Meetings list inside the Zoom account, which is the quickest way to confirm the handoff worked at all.

That last detail matters for diagnosis. If a meeting exists in Zoom but the link is missing from the email, the connection is fine and the problem is in the notification template. If nothing exists in Zoom, the authorization or the account itself is the problem. Checking Zoom first splits the work in half before any setting is touched.

The permissions Calendly requests are narrow and worth knowing before an IT review asks. On a personal connection it uses meetings:read to pull dial-in numbers, meetings:write to create and delete meetings that are marked as the Zoom type, and user:read to read the Zoom user's ID and email address. Admin-managed connections use the :admin variants of the same three. Nothing in that list reads meeting content or recordings.

The integration itself is not gated behind a paid tier. Calendly lists Zoom as available on all plans, so a free Calendly account can generate Zoom links. What a free Calendly account cannot do is hold more than one event type or connect more than one calendar, which is a different constraint and one that tends to bite later.

Connecting the two accounts

The path is short:

1. Open the Integrations and apps page in Calendly.
2. Select Zoom, then choose whether to connect Zoom for one user or for the whole organization.
3. Sign in to the Zoom account that should host the meetings.
4. Select Authorize.

Zoom then shows up as a location choice when editing an event type. Until the location is actually changed on the event type, nothing changes for invitees. This is the most common reason a connection looks finished and produces no links: the account is joined, but the event types still say "In-person meeting" or hold a static link pasted in months ago.

One practical note about sequencing. Meetings that were already booked before Zoom was connected do not retroactively gain a room. To add one, the meeting has to be rescheduled to the same date and time, which regenerates the location. It feels redundant, and it is the documented way to do it.

If the Zoom sign-in ends with a "Request pre-approve" message instead of an authorization screen, the Zoom account restricts third-party apps. Selecting Request pre-approve notifies the Zoom admin. Until that approval lands in the Zoom App Marketplace, the connection cannot be completed from the user side at all, so there is no point retrying it.

A Zoom admin has two ways to grant that approval. The prompt itself offers a review option during the connection attempt, which is the fastest route when the person connecting is also the admin. Otherwise it is done from the Zoom App Marketplace: sign in as the admin, search for the Calendly app, and pre-approve or enable it for the account. Once approved, everyone on that Zoom account can install it without a second request, so this is a one-time piece of work rather than a per-user step.

Where teams work differently

A single user connecting a single Zoom account is the easy case. Teams have three shapes, and each fails in its own way.

Event type	Who needs a Zoom connection	What breaks when it is missing
Personal	The owner	No link on any booking
Round robin	Every teammate in the rotation	Links appear for some bookings and not others
Collective	Only the designated Zoom organizer	No link, or a link owned by the wrong person
Admin-managed	Set once by an admin, org-wide	Users see pre-approval prompts instead

Round robin is the one that produces the confusing bug report. Bookings that land on a connected teammate get a room. Bookings that land on an unconnected teammate do not. From the outside it looks intermittent, when in fact it is perfectly deterministic and depends on whose turn it was.

Collective event types need the organizer chosen in the event type settings before any meeting is booked. Setting it afterwards does not repair the bookings that already exist. For organizations that would rather not chase individual connections, the admin-managed Zoom feature connects Zoom once for everyone, and users no longer do their own setup.

The limits that belong to Zoom

Several of the complaints filed against scheduling tools are really Zoom account settings, and no amount of work on the booking page will move them.

Meetings that cut off at 40 minutes. Zoom's free Basic plan caps each meeting at 40 minutes and 100 participants. Paid Workplace plans raise the per-meeting ceiling to 30 hours. If back-to-back discovery calls keep ending mid-sentence, the calendar is not the cause.

A hard ceiling on bookings per day. Zoom allows each user to schedule up to 100 meetings per day across every app connected to that account. High-volume booking links can reach it, and when they do the calendar page shows an "Action Needed" flag rather than an error the invitee sees.

Passcodes appearing without being asked for. On Zoom Basic, meeting passcodes are enabled and locked on by default, so every generated invite carries one. On paid Zoom plans the setting is optional and may be controlled by a Zoom admin. Either way the passcode is written into the invite automatically when it is on.

The same link every time. By default a fresh Zoom link is created per meeting. Turning on the Personal Meeting ID in Zoom makes every booking reuse one room, which is convenient for a recurring one-on-one and a liability for consecutive interviews with different candidates.

Dial-in numbers that should not be there. Zoom only prints one-tap mobile and dial-in numbers when the meeting audio type is set to Telephone, or to Telephone and Computer Audio. Switching the audio type to Computer Audio only removes them from every future invite. Which countries appear in that list is also a Zoom setting, controlled by the global dial-in countries and regions option, and the "Find your local number" line that some invites carry is a separate Zoom toggle again. None of these are editable from the scheduling side, which is why a support request filed there tends to come back unresolved.

A waiting room the host forgot about. Zoom's waiting room holds invitees until the host admits them. It is a Zoom-level setting, and when it is on, a guest who joins two minutes early sees a holding screen rather than an empty room. That is usually the intent, but it is worth knowing which behavior is configured before assuming the link is broken.

When the link is genuinely missing

Assume Zoom shows the meeting in Upcoming Meetings and the invitee still sees no room. In that case the location variable has been removed from a template, usually while someone was rewriting the confirmation copy.

Inside the event type, under notifications and automations, both the calendar invitation and the email confirmation are editable, and both need the Location variable in the body. It is added from the variables menu while editing. Workflows are a third, separate place with the same requirement: an automated reminder built before Zoom was connected will keep sending reminders with no room in them.

There is a milder version of this that is not a bug. Zoom details can take a moment to populate after a booking, so a guest who opened the confirmation instantly may need to add the event to a calendar again.

Two more specific failures are worth naming. If meetings carry links that belong to a different account, the wrong Zoom account is connected, and the repair is to disconnect and reconnect from a private browsing window so the previous Zoom session is not silently reused. And if Zoom returns an error about being unable to assign an alternative host, someone configured as a host has left the Zoom account. Removing that host from the Personal Meeting Room settings, or turning off Enable Personal Meeting ID, clears it.

The part the scheduling link cannot fix

A booking link solves one problem well: letting a stranger take a slot without an email thread. It does not know what sits on either side of that slot. The room opens on time, and the person hosting it is still in transit, or still in the previous call, because the calendar allowed two things to touch.

This is where the work moves back to the calendar itself. A desktop calendar that reads the travel time between a physical appointment and the next commitment, and that blocks the gap instead of trusting a buffer rule, catches the conflicts a booking page cannot see. How a Mac calendar can calculate that travel and place a departure reminder is covered in Travel time, and the wider set of behaviors, including detecting meeting links already present in an event and issuing Zoom or Google Meet rooms directly from the calendar, is listed in Features.

There is also a sequencing point. Calendly's free tier connects one calendar. If work and personal calendars are separate, availability is computed from one of them, and the other one is invisible to the booking page. Consolidating both into a single desktop view first, then pointing the booking link at the calendar that holds everything, prevents the class of double booking that no integration setting will catch. A side-by-side view of how native Mac calendars differ on multi-account handling is in Compared with other calendars.

What to change first

Open the event type and confirm two things before anything else: that the location is set to Zoom, and that the Location variable is still present in the calendar invitation and the email confirmation. Those two account for most reports of a missing room. After that, decide which calendar the booking link is allowed to read, and make sure that calendar is the one showing every commitment, which is the job Caltimate is built for on macOS.