Resources · Make integration

Cal ID Make integrationAutomate Cal ID with Make.

Every booking in Cal ID can start work somewhere else. The Cal ID Make integration gives you 4 modules: 3 triggers that watch new, cancelled and rescheduled bookings, plus one API call. This guide shows how to link your account and build a first scenario.

Try the Cal ID integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cal ID Make integration do for you?

The Cal ID Make integration lets Make notice what happens to your bookings and react for you. A booking gets created, cancelled or moved, and a scenario (the automation you build in Make, a chain of bricks called modules) passes that booking on to the rest of your tools, with no code to write.

A follow-up that starts itself. Watch Created Booking picks up each new appointment, so a scenario can hand its details to your CRM, your spreadsheet or your team chat through a module of that other app.

Freed slots that do not go unnoticed. Watch Cancelled Booking catches cancellations, which is the moment to warn whoever prepares the meeting or to reopen the slot in your own planning. Watch Reschedule Booking does the same for moved appointments, so the new date travels everywhere the old one went.

Anything the list does not cover. Make an API Call reaches any endpoint of the Cal ID API with the same connection. Keep in mind that Make says its documentation for Cal ID is limited, because little public information exists about the app: expect to test more than usual, and keep the Make troubleshooting guide close.

If you are still choosing a tool, the n8n vs Make comparison lays out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect Cal ID to Make?

  1. 01

    Add a Cal ID module

    Open your scenario, click the +, search for Cal ID and pick any of its modules. Then click Create a connection. A connection is your Cal ID account linked to Make once, and every Cal ID module reuses it.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you run a work account and a test account, a clear name tells you at a glance which calendar a scenario is reading.

  3. 03

    Authorize and save

    Make either opens a Cal ID page where you approve access, or asks for the key that Cal ID gives you. Follow what the window asks for, then click Save. The module is now ready to be configured.

First scenario

Your first scenario with Cal ID

GoalWhen a booking is created in Cal ID, Make sends a request to the Cal ID API with the booking data.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas to add your first module.

  2. 02

    Set the trigger

    Search for Cal ID, choose Watch Created Booking and link your account with Create a connection. Each new booking will enter the scenario as one bundle, an item passed from module to module.

  3. 03

    Add the API call

    Click the + to the right of the trigger and add Make an API Call from Cal ID. Pick the endpoint you need and map fields from the booking into the request.

  4. 04

    Test with Run once

    Create a test booking in Cal ID, then click Run once. Read the bundles each module received and check that the request went out as planned.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. Make will now check Cal ID at that rhythm.

Triggers

Which Cal ID triggers start a scenario?

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

Cal ID1Watch Cancelled Booking

Watch Cancelled Booking

triggerIn the docs only

This trigger brings every cancelled booking into your scenario, so the people and tools that expected the meeting learn that it is off. Each cancellation arrives as one bundle you can map into later modules.

How it fires
scheduled (deduced from its name), Make checks the app on the scenario's schedule, not the second the guest cancels.
When to use it
a sales rep prepares demos and needs to drop the ones that will not happen.
Watch out
Make lists this module without any description, so run a test cancellation first and read what the bundle actually contains.
Cal ID2Watch Created Booking

Watch Created Booking

triggerIn the docs only

You get each new booking at the next check, ready to be copied, announced or enriched by the modules you add after it. It is the natural starting point for most Cal ID scenarios.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
a consultant wants every new appointment logged in a client file before the call takes place.
Watch out
on the Free plan the shortest interval between two checks is 15 minutes, so a booking can wait that long before your scenario sees it.
Cal ID3Watch Reschedule Booking

Watch Reschedule Booking

triggerIn the docs only

With this trigger, a moved appointment updates everywhere without anyone retyping the new date. The scenario receives the rescheduled booking and passes it to whatever tool still holds the old slot.

How it fires
scheduled, Make checks the app on the scenario's schedule, so a moved booking shows up at the next run.
When to use it
a coach keeps session notes in another tool and wants the date there to follow the calendar.
Watch out
a reschedule is not a new booking, so pair this trigger with Watch Created Booking if both events matter to you.
Modules

What else can you do with Cal ID in Make?

Cal ID gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Cal ID1

Make an API Call

ActionIn the docs only

This module opens the whole Cal ID API to your scenario, reusing the connection you already created, so you are not limited to the three watch triggers. It counts as one operation, a single execution Make bills on your plan, each time it runs.

When to use it
the action you need, such as acting on a booking rather than watching it, has no dedicated module.
Watch out
you choose the endpoint and write the request yourself, so test each request with Run once before you rely on it.
Need help

Need help automating Cal ID with Make?

A person reads every message.

FAQ

Cal ID and Make: frequent questions

01Is the Cal ID Make integration free?
Yes. Cal ID is a standard app, so it works on the Free plan of Make, alongside the 3,000+ standard apps offered on every plan. The Free plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in credits, one per operation.
02What do you need to connect Cal ID to Make?
You need a Cal ID account and a Make account. Make's documentation lists no specific prerequisite for Cal ID and gives no dedicated connection steps, so the generic flow applies: add a Cal ID module, click Create a connection, optionally name it, authorize Make on the Cal ID page or paste the key the app provides, then save. Once saved, the same connection serves the three triggers and the API call module, so you only do it once per account.
03Do Cal ID triggers fire instantly in Make?
No. The three Cal ID triggers, Watch Created Booking, Watch Cancelled Booking and Watch Reschedule Booking, are listed as scheduled triggers. Make gives no detail on them, so this type is deduced from their names: check for the clock badge on the module. Make checks Cal ID on the scenario's schedule instead of being called by the app the moment a booking changes. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can go down to 1 minute, which shortens the wait between a booking and your scenario.
04What if the Cal ID module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Cal ID API with the connection you already have, which covers what the three triggers do not, such as acting on a booking. Be aware that Make describes its Cal ID documentation as limited, because little public information about the app exists. Plan to test each request with Run once and read the bundles returned before you switch the scenario on.
05Should you use Make or n8n for Cal ID?
It depends on what you need to build. In Make, Cal ID offers 4 modules: three scheduled triggers for created, cancelled and rescheduled bookings, and Make an API Call for everything else, all usable from the Free plan. Before choosing n8n, check whether it has a node for Cal ID and which operations that node covers. Then compare the two against your own scenario: the events you watch, the actions you need and how comfortable your team is with each editor.
Same platform

Other docs you might need on this stack.

Browse all integrations