Resources · Make integration

Cal.com Make integrationAutomate Cal.com with Make.

Your calendar can trigger the work, not just record it. The Cal.com Make integration ships 6 modules, the bricks you chain inside a scenario, the automation Make runs for you: 4 fire when a booking changes, one lists bookings, one reaches the API.

Try the Cal.com integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Cal.com Make integration actually do?

It links your Cal.com account to Make once, then lets Make act on whatever moves in your calendar. Someone books, someone shifts a slot, someone cancels, a video call wraps up: Cal.com tells Make right away, and the rest happens without you, whether that means a row in a sheet, a message to the team or a draft invoice.

Three shapes come back all the time. The consultant who wants a prepared folder waiting before the call: Watch Booking Created opens the march. The support desk that loses an hour mid-morning: Watch Booking Cancelled grabs the free slot and offers it to whoever was waiting. The studio that bills once the work is discussed: Watch Meeting Ended fires the recap and the invoice while the conversation is still fresh.

Where it stops matters just as much. The Cal.com modules watch and list, they never create or move a booking for you: that part stays in Cal.com, and anything beyond it goes through Make an API call. The ceiling you meet first is your Make plan, which counts an operation, one run of one module on one item, every time something moves.

The same app lives on the other side too. If the choice is still open, the n8n vs Make comparison lays out the criteria, and the Cal.com n8n integration page covers the node over there. If you would rather learn the editor before wiring your calendar to anything real, Make training starts from the basics.

Connect

How do you connect Cal.com to Make?

  1. 01

    Generate your API key in Cal.com

    Sign in to Cal.com, open Apps in the left sidebar, find the Make app and click +Install. Pick the account it applies to, click Generate API key and keep that value somewhere safe.

  2. 02

    Create the connection from a module

    In Make, add any Cal.com module to a scenario and click Create a connection. A connection is your Cal.com account linked to Make once, then reused by every Cal.com module. Connection name is optional.

  3. 03

    Fill the two fields and save

    Leave Cal Url on https://app.cal.com unless you host Cal.com yourself, where you point it at your own address. Paste the key into API Key, click Save, then confirm access if a window asks.

First scenario

Your first scenario, step by step

GoalWhen someone books a slot in Cal.com, Make wakes up and pulls the list of bookings for the day.

  1. 01

    Create the scenario

    Open the scenarios page, create a new one and click the + to place the first module. Type Cal.com in the search and the app comes up with its modules.

  2. 02

    Drop in the trigger

    Choose Watch Booking Created. It carries the instant tag, so Make asks for Create a webhook first, then the connection you set up.

  3. 03

    Add List Bookings

    Click the + on the right of the trigger and add List Bookings. It returns 10 bookings by default, each one arriving as its own bundle, a single item handed to the next module.

  4. 04

    Test with Run once

    Click Run once and book a test slot on your own page. The scenario runs a single time and shows what each module received, which beats guessing at the data.

  5. 05

    Switch the scenario on

    Leave the test behind and flip the scenario on. Cal.com then calls Make on every new booking, and each run lands in the history where you can open it.

Triggers

What can start a Cal.com scenario?

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

Cal.com1Watch Booking Cancelled

Watch Booking Cancelled

Instant trigger

In Make“Triggers when a booking is cancelled”

Someone drops out of a slot and this trigger passes the cancelled booking to your scenario, with what the calendar held on it. The hole in the day turns into something you can act on instead of something you notice three hours later.

How it fires
instant. Cal.com calls Make through a webhook the second the cancellation goes through, with no check to wait for.
When to use it
a sales team that wants the freed hour announced in its channel while there is still time to fill it.
Watch out
cancelling and moving are not the same event. If the client picks another date, the reschedule trigger speaks and this one stays quiet.
Cal.com2Watch Booking Created

Watch Booking Created

Instant trigger

In Make“Triggers when a booking is created”

Every new booking taken on your Cal.com page reaches Make as soon as it is confirmed, so the work that follows can start on its own. This is the trigger most first scenarios are built on.

How it fires
instant. The booking leaves Cal.com for Make through a webhook at the moment it is created.
When to use it
an agency that wants the brief form, the shared folder and the reminder ready before the client joins the call.
Watch out
the webhook only exists from the moment you set the module up, so bookings taken earlier are never replayed. List Bookings is what goes back for those.
Cal.com3Watch Booking Rescheduled

Watch Booking Rescheduled

Instant trigger

In Make“Triggers when a booking is rescheduled”

When a client moves an existing booking, this one hands you the updated version. You get the change itself, not a fresh booking you then have to match against the old one.

How it fires
instant. Make gets the call from Cal.com as soon as the new date is saved.
When to use it
a training company whose reminders, room and trainer all have to follow the new time.
Watch out
a move does not fire the created trigger. A scenario listening only for new bookings misses half of what happens in a busy week.
Cal.com4Watch Meeting Ended

Watch Meeting Ended

Instant trigger

In Make“Triggers when a video meeting has ended”

This one waits for the video call to finish, then sends the meeting over to Make. It is the closing signal of the appointment, useful when the real work starts once everyone has hung up.

How it fires
instant. Cal.com reaches Make through a webhook once the meeting is over.
When to use it
a recruiter who wants the scorecard, the notes template and the next email queued without thinking about it.
Watch out
it covers video meetings. An appointment held in person or over the phone never reaches it.
Modules

What else Cal.com does inside Make

Cal.com gives you 2 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

1 module
Cal.com1

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

This module is the way out for everything the four watchers and the list do not cover: it sends an authorized request of your own to the Cal.com API, through the same connection.

When to use it
the endpoint you need has no module of its own, and you have the Cal.com API reference open next to the editor.
Watch out
nothing is guided here. Read what comes back in Run once before you build the rest of the scenario on top of it.

Searches

1 module
Cal.com2

List Bookings

Search

In Make“List all bookings from cal.com. Default limit is 10 bookings.”

It reads the bookings in the account and hands them to the scenario, 10 by default. Each one arrives as its own bundle. That matters, because every module placed after it then runs once per booking.

When to use it
the morning round-up for the team, or a check on what already exists before you write anything anywhere else.
Watch out
a search can come back empty. The scenario stops right there, so plan for the day nobody booked.
Need help

Need help automating Cal.com with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Cal.com Make integration free?
Yes, from the Free plan. Cal.com is a standard app in Make, not an enterprise one, so you get it at no extra cost on the Make side. What the Free plan caps is the size of what you run: 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the interval down to 1 minute, lift the active scenario count and allow 40 minutes of execution. That interval applies to scheduled scenarios, and the Cal.com triggers are instant ones.
02What do you need to connect Cal.com to Make?
A Cal.com account and an API key taken from it. The key is generated inside Cal.com: open Apps in the left sidebar, find the Make app, install it, pick the account it applies to and click Generate API key. Keep the value, because Make asks for it in the API Key field when the connection is created. The other field, Cal Url, already holds app.cal.com and only changes if you host Cal.com yourself. If the module carries the instant tag, you create the webhook first and the connection after.
03Do the Cal.com triggers react in real time?
Yes. All four Cal.com triggers are instant ones: Cal.com calls Make through a webhook the moment a booking is created, cancelled or moved, and when a meeting ends. Make is not rereading the calendar on a timer, so there is no interval to shorten and no lag to explain to a client. The practical consequence is that the scenario has to be switched on to catch the call. A scenario that sits off has nobody listening. Turn it back on and the bookings that follow flow again.
04What if a module is missing or a limit gets in the way?
You go through Make an API call. The five other modules watch bookings and list them, which leaves a good part of the Cal.com API untouched, and that module reaches it with the connection you already have. If the blocker sits on the Make side, it is usually the plan: an operation is counted for every module that runs on every item, so a scenario that fires on each booking and then walks through a list burns more than it looks.
05Make or n8n for Cal.com?
It depends on what you are optimizing for. Make is the faster road if you want the four instant triggers in place without thinking about hosting, and the visual editor keeps a first scenario readable to someone who has never automated anything. n8n fits better if you want to host it yourself, keep the data on your own machines or write code in the middle of the flow. Both cover Cal.com. The deciding question is usually who maintains the thing in six months, not which tool is technically stronger.
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