Resources · Zapier integration

Cal ID Zapier integrationAutomate Cal ID with Zapier.

The Cal ID Zapier integration gives you 4 triggers, 0 actions and 0 searches. Cal ID can start a Zap when a meeting is booked, moved or cancelled, but nothing can write back into it. Here is what that means for your calendar.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Cal ID Zapier integration actually does

Cal ID is a booking tool: people pick a slot, and the meeting lands in your calendar. Zapier, an automation service, can listen to Cal ID and pass each booking event to another app. One way only. Cal ID announces what happened in your calendar, and it never takes orders back from Zapier or anything else.

Three results people usually build with it.

A live log of every meeting. Booking Created fires for each new appointment, and the next step adds a line to a spreadsheet or a CRM. Your sales team sees the pipeline fill up without copying anything.

A clean follow-up when plans change. Booking Rescheduled and Booking Cancelled let you update that same record, warn a colleague, or stop a reminder sequence that no longer makes sense.

Team awareness of who is away. Out of Office Created fires when someone logs time off in Cal ID, so a team channel or a shared calendar can hear about it.

Now the limits, because they matter. Zapier cannot create a booking in Cal ID, cannot cancel one, and cannot look one up: the app exposes no action and no search. If your plan is to book meetings from a form in another tool, this integration will not do it (Cal ID only reports what already happened inside it).

Every trigger here is instant, which is good news on a small budget. Comparing tools first? The Cal ID Make integration covers the same app on Make, and our Make vs Zapier comparison lays out the differences criterion by criterion.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are, in plain English.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts your Zap. Once the Zap is switched on, Zapier waits for it and does nothing else.
Action
What the Zap does after it starts: the step that writes a row, sends a message or moves something for you.
Task
The unit Zapier bills. One task equals one action your Zap finished successfully; your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app itself, the second the event happens.
Filter
A step that lets the Zap continue only when the incoming data matches a rule you set, and quietly stops it otherwise.
Connection
Your Cal ID account linked to Zapier once, then reused by every step and every Zap that touches Cal ID.
Cost

What it really costs

Cal ID is not a premium app, so it works on the free plan. The bill depends on the steps after it, not on Cal ID.

  • Premium appNo, works on Free
  • Free plan100 tasks a month
  • Free plan Zap size2 steps: 1 trigger + 1 action
  • Cal ID triggers4, all instant

A trigger never costs a task. Listening for bookings is free; only an action that succeeds is counted, and a failed one is not. Each successful action counts separately, so a Zap with three actions uses three tasks per booking. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger, one action. Add a second action or a filter and the Zap becomes multi-step, which needs a paid plan. Since all four Cal ID triggers are instant, the interval grid below does not slow you down.

Connect

Connect Cal ID to Zapier in 3 steps

  1. 01

    Open your Apps page

    In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. You need an existing Cal ID account before you start.

  2. 02

    Find Cal ID and add it

    Type Cal ID in the dialog, pick it from the results, then click Add connection. Zapier then opens a new browser tab pointing to Cal ID, where the rest happens.

  3. 03

    Sign in and grant access

    Log in to Cal ID in that tab and allow Zapier to reach the account. The connection is then listed on your Apps page, ready to be picked in any Zap you build next.

First Zap

Your first Zap: log every new booking

GoalEach new Cal ID booking adds a row to a Google Sheets tracker.

  1. 01

    Create the Zap

    Start a new Zap from the editor. Pick Cal ID as the app that starts everything, then Booking Created as the event to watch.

  2. 02

    Choose the connection

    Select the Cal ID connection you just added, so the trigger listens to the right account before you move on to the test.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent bookings from your account, so you can pick a real one to map from.

  4. 04

    Add the action

    Add Google Sheets as the next step, choose the spreadsheet, then map the booking details from the test into the columns.

  5. 05

    Test, then publish

    Run the action once and check the new row in the sheet, column by column. If it looks right, click Publish to switch the Zap on.

Triggers

The 4 Cal ID triggers

4 events start a Zap when something happens in Cal ID, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Booking Cancelled

Instant trigger

In Zapier“Triggers when new booking is cancelled.”

Someone drops a meeting, and your Zap hears about it at once. The step that follows can mark the deal as lost, free up a resource, or tell the host that the slot is open again.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a consultant who sends prep material before calls wants that sequence halted as soon as a client backs out.
Watch out
this trigger cannot undo anything in Cal ID itself; every cleanup happens in the other app.
2

Booking Created

Instant trigger

In Zapier“Triggers when new booking is created.”

This is the one most Zaps start with. Every fresh appointment in Cal ID starts the Zap, carrying the booking details into whatever comes next: a spreadsheet, a CRM record, a Slack note.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales team logging every demo request in one tracker, without anyone copying data by hand.
Watch out
on the free plan you get one action after it, so pick the destination that matters most.
3

Booking Rescheduled

Instant trigger

In Zapier“Triggers when a new booking is rescheduled.”

When an invitee moves a meeting to another slot, this trigger passes the change along. It keeps your records honest, since a tracker built on new bookings alone would still show the old date.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a coaching practice updating its client sheet and alerting the coach whenever a session shifts.
Watch out
updating an existing row usually needs a lookup step in the other app, which makes the Zap multi-step.
4

Out of Office Created

Instant trigger

In Zapier“Triggers when a new Out Of Office entry is created.”

Different from the other three: it has nothing to do with clients. It fires when a Cal ID user records a period of absence, so the rest of the team can learn about it without checking the calendar.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an operations lead who wants each new absence posted in a team channel or added to a shared leave tracker.
When it breaks

When it breaks

Zapier publishes no help article and no specific limit for Cal ID. What breaks here is the same as on any Zap, so these cases come from Zapier's general rules.

Most problems show up in the first week. Check these four before you go looking for a bug, or browse our Zapier troubleshooting page for broader fixes.

  • Old bookings never show up

    A Zap only sees events that happen after you publish it. Meetings booked last month stay where they are; importing them is a separate project.

  • A loop that eats your tasks

    If a Zap writes into the very place its own trigger watches, it sets itself off again and again. With Cal ID this is rare, but watch chained Zaps.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after a migration for example, Zapier's flood protection can hold it back instead of running it.

  • The free plan stops at two steps

    Adding a filter to keep only some event types, or a second action, turns the Zap multi-step. On the free plan it simply will not publish.
Need help

Need help automating Cal ID with Zapier?

A person reads every message.

FAQ

Cal ID Zapier integration: FAQ

01Is the Cal ID Zapier integration free?
Yes, it works on the free plan because Cal ID is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like. The catch is size: each free Zap holds one trigger and one action only. As soon as you need a filter, a second action or a lookup, you need a paid plan. Cal ID's own pricing is a separate matter that Zapier does not cover.
02How many Zapier tasks does a Cal ID Zap use?
The Cal ID trigger itself uses none. Zapier counts one task per action that completes successfully, so a Zap with one action uses one task per booking event, and a Zap with three actions uses three. Actions that fail are not counted. If you get many bookings, cancellations and reschedules each day, multiply the number of events by the number of actions to estimate your monthly use against the 100 free tasks.
03Do Cal ID triggers run in real time?
Yes. All four Cal ID triggers are instant: Cal ID tells Zapier the moment a booking is created, moved or cancelled, or an absence is logged. The plan interval grid, 15 minutes on Free, does not apply to them. That makes Cal ID one of the cases where the free plan is just as fast as Enterprise. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does it take to connect Cal ID to Zapier?
An existing Cal ID account and a Zapier account. From the Apps page in Zapier, you add a connection, search for Cal ID, then sign in to Cal ID in the tab that opens and grant access. If the Zap needs to react to bookings on calendars you do not own, you also need read access on those. The connection is then reused by every Zap that involves Cal ID.
05Can Zapier create or cancel a booking in Cal ID?
No. Cal ID offers no action and no search on Zapier, only four triggers. Zapier can react to what happens in Cal ID, but it cannot book a slot, move a meeting, cancel one or look up an existing booking. Every result of your Zap happens in another app: a sheet, a CRM, a chat tool. If writing into Cal ID is essential, check whether another automation tool supports it.
06What if the Cal ID event or action required is missing?
Then Zapier cannot provide it, since the list of operations is set by Cal ID's own integration and cannot be extended from the editor. The four available triggers cover new, cancelled and rescheduled bookings plus out-of-office entries. Anything else, such as reminders or no-shows, is not offered. The honest options are to check what another platform offers for Cal ID, or to ask Cal ID about it. Before building, read the trigger list on this page so you know exactly what Cal ID can report.
07Zapier, Make or n8n for Cal ID?
It depends on what you value. On Zapier, the facts are on this page: four Cal ID triggers, all instant even on the free plan, no action, and tasks billed per successful action. Put the same questions to Make and n8n before choosing. Check which Cal ID operations each tool exposes before choosing, since the catalogues differ from one platform to the next. Your team's comfort with each editor matters too.
Same platform

Other docs you might need on this stack.

Browse all integrations