Resources · Zapier integration

CalendarLink Zapier integrationAutomate CalendarLink with Zapier.

The CalendarLink Zapier integration gives you 3 triggers, 3 actions and 2 searches. Two triggers fire the moment something happens, one waits for Zapier's next check, and every single step asks for your CalendarLink organization.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the CalendarLink Zapier integration does for you

Connecting CalendarLink to Zapier lets a Zap (an automation you build on Zapier: one trigger, then one or more actions that run each time) react to what happens in your CalendarLink organization, or write into it. Events, collections, RSVPs and contacts become things you set up once instead of copying by hand.

Events mirrored where they belong. New Upcoming Event spots each event added to an organization, and Create New Event writes a copy into another one, so a partner's public collection stays in step with yours.

Collections managed from outside the app. Create Event Collection and Update Event Collection open a new collection or change an existing one, sharing and registration switches included, without anyone logging in to CalendarLink.

Answers that start the next step. New RSVP fires as soon as someone RSVPs to one of your events, and Find Event or Find Contact fetch the full record behind an ID when a later step needs it.

What the integration does not do: there is no action to delete an event, a collection or a contact, and both searches work with an ID only, never with a name. If you are still choosing a tool, the CalendarLink Make integration covers the same app, and n8n vs Zapier sets out the criteria between those two.

Vocabulary

Zapier vocabulary in one minute

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

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event that starts the Zap, here a new RSVP, a new upcoming event or a contact change. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes something for you, such as a new event or an updated collection.
Task
The unit Zapier bills. One task is one action your Zap completed successfully, and the number on your plan counts those.
Instant vs polling
Instant: CalendarLink reports the event to Zapier itself. Polling: Zapier asks for new items on a timer and keeps only what it has not seen.
Filter
A step that lets the Zap carry on only when what arrived matches the condition you set, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in the app, here an event or a contact by its ID, so later steps can use it.
Connection
Your CalendarLink account linked to Zapier once, then reused by every step of every Zap that touches CalendarLink.
Cost

What a CalendarLink Zap really costs

Short version: you pay for actions that work, nothing else.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on the free planTwo: one trigger, one action
  • Premium appNo, works on the free plan
  • Cost of the trigger0 tasks

The trigger never costs a task, and neither does Zapier checking for new events, however often it looks. Each action that completes counts as one task; one that fails is not counted. CalendarLink is not a premium app, so it runs on the free plan: 100 tasks a month, unlimited Zaps, a check every 15 minutes on polling triggers. The catch nobody puts up front: the free plan stops at two steps, one trigger and one action. Add a filter, a search or a second action and you have a multi-step Zap, which needs a paid plan.

Connect

Connect your CalendarLink account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection (your account linked once) is then reused by every Zap that touches CalendarLink.

  2. 02

    Pick CalendarLink

    Type CalendarLink in the search box of the dialog, select it, then click Add connection. You need a CalendarLink account, plus access to any organization you do not own and want the Zap to touch.

  3. 03

    Sign in and grant access

    A tab opens on CalendarLink. Sign in with the account whose events the Zaps will read or write, then grant Zapier access to it. That is the last gesture before your first Zap.

First Zap

Your first Zap: share webinars with a partner organization

GoalCopy every new upcoming webinar of your organization into the collection of a partner organization.

  1. 01

    Build the trigger

    Start a new Zap, choose CalendarLink as the app and New Upcoming Event as the event. Select your connection, then the organization whose events the Zap should watch.

  2. 02

    Test it on real data

    Run the test. Zapier brings back the three most recent items of the connected account, so you pick a real event and map from it instead of guessing what one looks like.

  3. 03

    Add the filter

    Add a filter step: continue only when the title contains “Webinar”. Pick a text rule, since a number rule on text never passes. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create New Event

    Add CalendarLink again with Create New Event. Choose the partner organization and its collection, map the title, start and end from the test result, and set the RSVP switch.

  5. 05

    Test, then Publish

    Test the action once and check the copy in the partner collection. Then click Publish to switch the Zap on. Only events created after that moment get copied.

Triggers

CalendarLink triggers

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

1

New or Updated Contact

Instant trigger

In Zapier“Triggers when a new Contact is created or updated. Anonymous Contacts are ignored”

Starts a Zap each time a contact appears in your CalendarLink organization, and again every time an existing one changes. Anonymous contacts never set it off.

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 events team that wants each change to an attendee record to refresh something downstream, such as the settings of a collection.
Watch out
it fires on every edit, so never pair it with an action that creates, or each update makes a duplicate. It also requires your Organization ID.
2

New RSVP

Instant trigger

In Zapier“Triggers when someone RSVP to an event”

Fires when someone RSVPs to one of your events. A single answer becomes the starting point of a workflow, with no one checking the guest list by hand.

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 meetup organizer who wants each new attendee to open registration on the follow-up collection without logging in.
Watch out
the Organization ID is required, so have it at hand before the first test. One reply means one run, which keeps the task count easy to predict.
3

New Upcoming Event

Polling trigger

In Zapier“Triggers when a new upcoming event is created.”

Picks up each upcoming event newly created in the organization you choose. It is the natural starting point when an event has to be copied or announced somewhere else.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a training company that publishes sessions in its own organization and mirrors them into a reseller's collection.
Watch out
unlike the two others, this one waits for Zapier's next check. The type is set by CalendarLink, not by you: only a paid plan shortens the wait, down to 2 minutes on Professional.
Actions

CalendarLink actions

CalendarLink gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Event Collection

Action

In Zapier“Create a new event collection”

Opens a brand new event collection in the organization you pick, named and styled from the start, so the events that follow have a home.

When to use it
a conference organizer who starts each new season with an empty collection ready to receive talks.
Watch out
Appearance is required alongside the name and the organization, so decide on the look before the Zap runs.
2

Create New Event

Action

In Zapier“Create a new single event”

Adds one event to an existing collection, with a title, a start and an end. If the collection allows adding single events, its visitors can then put it in their own calendar.

When to use it
mirroring each new webinar into a partner's collection, as in the Zap above.
Watch out
six fields are required, the event collection ID and the RSVP setting among them, so the collection has to exist first.
3

Update Event Collection

Action

In Zapier“Update an existing event collection”

Changes a collection that already exists: its name, its appearance and switches such as sharing, registration or adding every event at once.

When to use it
turning registration on for a follow-up collection as soon as a new RSVP comes in.
Watch out
name and appearance are required even for a one-switch change, so fill them in every time.
Searches

CalendarLink searches

2 search steps look for data that already exists in CalendarLink, so a later step can use it.

A search step finds a record that already exists and hands it to the steps that follow. In the action event list, searches sit at the bottom under SEARCH. Three settings decide what happens when the result is not what you expected.

1

Find Contact

Search

In Zapier“Find a Contact in the system by ID”

Fetches one contact of your organization from its ID and passes the details to the next steps.

When to use it
an earlier step handed you a contact ID, and a later action needs more than that number.
Watch out
the lookup works by ID only, and both the Organization ID and the Contact ID are required.
2

Find Event

Search

In Zapier“Find an Event in the system by ID”

Retrieves a single event from its ID, so a later step can reuse its details without anyone retyping them.

When to use it
a step upstream only carried an event ID, and the next action needs the rest of that event.
Watch out
a name or a date will not do, only the Event ID, together with the Organization ID.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Neither CalendarLink search offers that variant, so a missing contact or event is never created on the fly.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When a CalendarLink Zap breaks

No limit specific to CalendarLink is documented on the Zapier side, so the risks are Zapier's general ones.

Four of them catch people on their first CalendarLink Zap. If one of your Zaps stalls anyway, Zapier troubleshooting is where to take it.

  • Older events are never picked up

    A Zap only reacts to what happens after you publish it. Events and RSVPs that existed before stay out, and moving that backlog is a separate job.

  • The Zap that feeds itself

    If Create New Event writes into the organization the trigger watches, each copy is a new upcoming event and starts the Zap again, eating tasks fast. Write into another organization.

  • A bulk import held back

    Importing a large batch of events at once can trip Zapier's flood protection, which holds the trigger back instead of running every Zap in one go.

  • The same event never runs twice

    On New Upcoming Event, Zapier remembers which events it has already seen, so one event never starts the Zap twice, however many checks pass.
Need help

Need help automating CalendarLink with Zapier?

A person reads every message.

FAQ

CalendarLink and Zapier: frequent questions

01Is the CalendarLink Zapier integration free?
Yes, as long as the Zap stays at two steps. CalendarLink is not a premium app, so it runs on the free Zapier plan, which gives 100 tasks a month and unlimited Zaps. The limit is the shape of the Zap: one trigger and one action, nothing more. The moment you add a filter, a search such as Find Event or a second action, the Zap becomes multi-step and needs a paid plan. Polling triggers are also checked only every 15 minutes on the free plan.
02How many tasks does a CalendarLink Zap use?
One task per action that completes, and nothing else. The trigger is free, and so are the checks Zapier runs to find new upcoming events, however often they happen. An action that fails is not counted. A Zap that copies each new event into a partner collection therefore uses one task per copy. Add a second action, for example Update Event Collection after Create New Event, and each run costs two tasks. A few apps take more than one task per action, so watch the counter during the first runs.
03Does the CalendarLink integration run in real time?
Two triggers out of three do. New RSVP and New or Updated Contact are instant: CalendarLink tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. New Upcoming Event works by polling instead: Zapier checks at a fixed interval, every 15 minutes on the free plan, every 2 minutes on Professional and every minute on Team and Enterprise. On a paid plan you can change how often it checks, and also run a check by hand from the editor.
04What do you need to connect CalendarLink to Zapier?
A CalendarLink account, plus access to any organization you do not own and want the Zap to touch. In Zapier, open Apps, click + Add connection, search for CalendarLink, click Add connection, then sign in and grant access in the tab that opens. Before building anything, note your organization: every CalendarLink operation asks for it. Create New Event also needs an existing collection, so create one first if the account is still empty.
05Why does New or Updated Contact create duplicates?
Because it fires on every change, not only on new contacts. A contact created and then edited three times starts the Zap four times. Paired with an action that creates something, that means four new items for one person. Keep this trigger for steps that update or look things up, such as Update Event Collection or Find Contact, and choose New RSVP when you want exactly one run per answer. Anonymous contacts never start it, which removes one source of noise.
06What if the operation you need is not on the list?
Then the integration does not offer it today: the 3 triggers, 3 actions and 2 searches on this page are what the Zap editor proposes. Two workarounds often close the gap. Chain a search and an action, for instance Find Event to fetch an event by its ID before an action reuses its details. Or run the step in the tool where the data really lives. If neither fits, the workflow needs another approach, and the Hack'celeration team can help scope it.
07Zapier, Make or n8n for CalendarLink?
It depends on criteria, not on a winner. On Zapier, CalendarLink offers 8 operations, two instant triggers, and it works on the free plan within two steps. Compare the same points on the other tools: which CalendarLink operations each one offers, how its triggers fire, what a run costs at your volume, and who will maintain the workflow once it is live. CalendarLink also has its own page in the Make integrations section of this site, so the two lists can sit side by side before you decide.
Same platform

Other docs you might need on this stack.

Browse all integrations