Resources · Make integration

Calendly Make integrationAutomate Calendly with Make.

Your calendar knows who booked. The rest of your tools have no idea. The Calendly Make integration closes that gap with 20 modules, the bricks you drop into a scenario, the automation you build in Make. You test it once, switch it on, and it runs without you.

Try the Calendly integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Calendly Make integration do for you?

Make links your Calendly account to the other apps you work in, then handles everything that happens after a booking. A new meeting, a cancellation, a reschedule: each one can start a chain of steps that fetches the details, tells the right person and files the result where your team looks. You build that chain once in the editor and leave it running.

Three shapes come back over and over. A sales team wants every booked call sitting in the CRM before the rep opens the confirmation email: Watch Events catches the booking, Get an Event returns the full record behind it.

A recruiter running group sessions wants the sign-up list without opening Calendly, and List Event Invitees returns it for one event. A consultant selling a paid hour does not want the booking link forwarded to a whole team, so Create a Single-Use Scheduling Link produces one meant to be used once.

What Make will not do here is invent your availability rules. The doc draws a few hard lines, better to know them now. Updating availability rules replaces every rule already set on that event type, so read the current schedule, change it, then send it back. A date range between Start time and End time cannot exceed 31 days. And the webhook, that call Calendly sends to Make the moment something happens, is not part of free Calendly plans.

The same app usually exists as an n8n node, so the door stays open: the n8n vs Make comparison lays out the criteria, and the Calendly n8n integration page covers the other side. If you would rather hand the build to someone, the Make agency page explains how the team works.

Connect

How do you connect Calendly to Make?

  1. 01

    Add a Calendly module

    Open a scenario, click the plus, search Calendly by name and pick the module you want. Under the field list, click Create a connection. That connection is your Calendly account linked to Make once, then reused by every Calendly module after it.

  2. 02

    Name the connection

    The Connection name field is optional, though a name your teammates recognize saves questions later. Show advanced settings is optional too: you only open it if you bring your own Calendly client credentials, with the redirect URI https://www.integromat.com/oauth/cb/calendly.

  3. 03

    Save and confirm access

    Click Save. Calendly opens its authorization window: sign in if you are asked, then confirm access. The window closes and the module can finally read what your account holds.

First scenario

Your first scenario, step by step

GoalWhen a call is booked in Calendly, Make fetches the event behind it and hands you the details.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario, then click the plus to place the first module. Search Calendly by name and pick Watch Events: bookings and cancellations are what will start the run.

  2. 02

    Link your account

    Click Create a webhook, then Create a connection, and confirm access in the Calendly window. Without that webhook, Calendly has no way to tell Make anything.

  3. 03

    Add the second module

    Click the plus on the right of Watch Events and add Get an Event. Fill its field with the event coming out of the trigger, so every run works on the booking that just landed.

  4. 04

    Test with Run once

    Click Run once, the button that runs the scenario a single time, then book a test meeting on your own link. Each module shows the bundles it received, one bundle being one item going through, here one booking.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, while an instant trigger starts on its own. Flip the switch and leave it alone.

Triggers

What starts a Calendly scenario?

2 modules start a scenario when something happens in Calendly. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Calendly as soon as it happens.

Calendly1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an event is created or canceled.”

Watch Events sits on your Calendly account and starts the scenario when an event is created or canceled. The booking moves straight to the next module, ready to be filed, answered or checked.

How it fires
instant, the app calls Make through a webhook as soon as it happens.
When to use it
a sales team wants the call in the CRM before the rep even reads the confirmation email.
Watch out
the doc says the webhook feature is not included in free Calendly plans, so this trigger assumes a paid Calendly subscription.
Calendly2Watch

Watch

triggerIn the docs only

Watch is the other trigger listed in the Calendly documentation, the one Make goes and queries. No official description comes with it, so treat it as the door you push when you want Make to look for itself instead of waiting for a call.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
a quiet catch-up run, where a pass at a fixed interval is enough and nobody is counting the minutes.
Watch out
nothing is documented about what it returns, so give it a Run once and read the output before you build anything on top.
Modules

What Calendly can do inside a scenario

Calendly gives you 18 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Calendly1

Cancel an Event

Action

In Make“Cancels an event.”

Cancel an Event calls off a booking from inside the scenario, without anyone opening Calendly. You hand it the event and it does the rest.

When to use it
a deal dies in the CRM and leaves a discovery call on the books that nobody will take.
Watch out
a cancellation is not something the next run takes back, so put a filter in front of it before you switch anything on.
Calendly3

Get an Event

Action

In Make“Returns information about an event.”

Get an Event returns the record behind one booking, so the rest of the scenario works on the meeting itself rather than on a bare reference.

When to use it
right after a booking arrives, when the next step needs the whole event.
Watch out
it reads one event per run; for several at once, the search modules are the right door.
Calendly4

Get an Event Invitee

Action

In Make“Returns information about an invitee.”

Get an Event Invitee returns one invitee, the person on the other side of the booking. Handy when your scenario cares about the human rather than the slot.

When to use it
before a welcome message goes out, to pull what the invitee record holds.
Watch out
one invitee per run, so a group session goes through the list module instead.
Calendly5

Get an Event Type

Action

In Make“Returns information about an event type.”

Get an Event Type returns one of the meeting formats you set up in Calendly: the demo, the intro call, the follow-up.

When to use it
the scenario has to behave differently depending on which kind of meeting was booked.
Watch out
it describes the format, not the bookings made on it.
Calendly6

Get an Organization Membership

Action

In Make“Returns information about a user's Organization Membership.”

Get an Organization Membership returns what ties one user to your Calendly organization, the membership record itself.

When to use it
an onboarding check, to confirm a new joiner really sits in the workspace before the scenario gives them anything.
Watch out
it answers about one person, while the wider view belongs to the list module.
Calendly7

Invite a User to Organization

Action

In Make“Invites a user to an organization.”

Invite a User to Organization sends the invitation to join your Calendly organization from the scenario, so nobody types it out by hand.

When to use it
the day a hire signs, at the same moment their other accounts get created.
Watch out
the invitation goes out for real, so keep it behind a filter while you are testing.
Calendly8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Calendly API with the connection you already set up. It is the way out when no module covers what you need.

When to use it
a corner of Calendly with no module of its own, spotted in the Calendly developer documentation.
Watch out
nothing comes prefilled here, so it asks more of you than a ready-made module.
Calendly9

List Event Invitees

Search

In Make“Returns a list of Invitees for an event.”

List Event Invitees returns the invitees attached to one event, one bundle per person, so the scenario can walk through them.

When to use it
a group workshop, when everyone who signed up has to land in the same place.
Watch out
a search returns zero, one or several items, so plan for the empty case as much as the full one.
Calendly10

List Events

Search

In Make“Returns a list of events.”

List Events brings back the bookings that match what you ask for, instead of waiting for the next one to happen.

When to use it
a catch-up pass, to pick up what was booked while a scenario sat switched off.
Watch out
the doc caps a date range between Start time and End time at 31 days, so a long history goes in slices.
Calendly11

List Event Types

Search

In Make“Returns all event types associated with a specified user.”

List Event Types returns every meeting format tied to one user, each in its own bundle.

When to use it
building a menu of booking options somewhere else, kept in step with Calendly instead of retyped.
Watch out
it works on the user you name, so a teammate means another run.
Calendly12

List Organization Memberships

Search

In Make“Return a list of organization memberships”

List Organization Memberships gives you who belongs to the organization, one membership per bundle.

When to use it
a clean-up of the seats in use, or a check against the internal directory.
Watch out
the bigger the organization, the longer the list, and that weighs on the run.
Calendly13

Event

ActionIn the docs only

Event shows up in the Calendly documentation without a line of explanation. The name points at the booking object, and the module list comes flat, so the honest answer is to open it in the editor and look at the fields it asks for.

When to use it
nothing above fits and you accept a bit of trial and error with a test run.
Watch out
undocumented means unpredictable, so keep it away from a scenario touching real bookings until Run once shows what comes back.
Calendly14

Schedule

ActionIn the docs only

Schedule is another module the documentation lists with no explanation. Going by the name alone, it looks toward the hours you open for booking rather than toward a single meeting.

When to use it
exploratory work, while you map what the app exposes before settling on a design.
Watch out
with no description to lean on, test it on a trial account rather than on the calendar your team lives in.
Calendly15

Organization

ActionIn the docs only

Organization carries the name of the workspace and little else, since the documentation does not develop it. The two membership modules above are documented, this one is not.

When to use it
the membership modules stop short of what an admin task needs.
Watch out
anything touching the organization touches your teammates, so try it where a mistake costs nothing.
Calendly16

Availability

ActionIn the docs only

Availability comes without a description as well. Its name lands on the hours you make bookable, the part of Calendly people notice fastest when it goes wrong.

When to use it
your open slots have to follow something else, a closed office, a pipeline already full.
Watch out
the doc is firm on this ground, an update to availability rules replaces all the rules already set on the event type, so fetch the schedule, edit it, push it back.
Calendly17

No Show Management

ActionIn the docs only

No Show Management is the module named after the invitee who never turned up. The documentation stops at the name, so what it changes on the booking has to be seen in the editor.

When to use it
a follow-up routine for the slots that stayed empty, once a test has shown what the module writes.
Watch out
marking a meeting one way or the other changes a real record, not a note in your own tracker.
Calendly18

Other

ActionIn the docs only

Other closes the Calendly list, with no description behind it. When a module has no documented job, Make an API Call stays clearer, because at least the Calendly developer documentation describes what you are calling.

When to use it
rarely, and only once the named modules have been ruled out.
Need help

Need help automating Calendly with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Calendly Make integration free?
Yes on the Make side, within the ceilings of the Free plan. Calendly is a standard app, so it is available from the free plan: 2 active scenarios, 15 minutes minimum between two scheduled runs, 5 minutes of execution, files up to 5 MB and 512 MB of transfer. Make counts operations, one run of one module on one item, against your plan. Paid plans bring the interval down to 1 minute, lift the active scenario count and stretch execution to 40 minutes. On the Calendly side, the doc flags that some modules require a paid subscription.
02What do you need to connect Calendly to Make?
A Calendly account, and the doc asks for nothing else. You add a Calendly module to a scenario, click Create a connection, give it a name if you want one, then Save and confirm access in the Calendly window. Show advanced settings only matters when you bring your own Calendly client credentials, and the doc then gives the redirect URI to register with them. Modules tagged instant ask for Create a webhook before the connection, and that route assumes a paid Calendly subscription, since free plans do not include the webhook feature.
03Does the Calendly trigger react in real time?
It depends which one you put first. Watch Events is instant: Calendly calls Make through a webhook as soon as an event is created or canceled, and the run starts right behind it. Watch is scheduled: Make goes and checks on the scenario's schedule, every 15 minutes by default, and no faster than that on the free plan. Paid plans go down to 1 minute. Pick instant when someone is waiting on the other end, scheduled when a regular pass does the job.
04What if a Calendly module is missing or a limit gets in the way?
Make an API Call is the spare wheel. It reaches any endpoint of the Calendly API with the connection you already created, so a gap in the module list is not a wall. For the documented limits, work with them rather than around them: a range between Start time and End time cannot exceed 31 days, so long periods get split; an update to availability rules replaces the ones already set on the event type, so you read the schedule, change it, then send it back. And the webhook route needs a paid Calendly plan.
05Make or n8n for Calendly?
Both cover the app, so the answer says more about your team than about the tools. Make is quicker to pick up: the editor is visual, the modules carry the Calendly names, and a first scenario takes a handful of minutes. n8n speaks to people who want to host it themselves, slip some code into the middle of a flow, or keep the data on their own machines. If nobody around you writes code and the goal is bookings landing where the work happens, start with Make.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations