Resources · Make integration

Calendarlink Make integrationAutomate Calendarlink with Make.

Can Make react when someone answers your Calendarlink invitation? Yes. The Calendarlink Make integration gives you 9 modules: 3 triggers, 2 actions and 4 searches. This page walks you through the connection, a first working scenario and what each module is good for.

Try the Calendarlink integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Calendarlink Make integration let you automate?

The Calendarlink Make integration links your Calendarlink account to Make, a visual tool where you build a scenario (the automation itself, a chain of steps) without writing code. Each step is a module: a trigger that starts the flow, an action that creates something, or a search that looks something up. Make then passes events, contacts and RSVP answers from Calendarlink to the other apps you use.

Follow up on every RSVP. Watch New RSVP response starts the scenario when a guest answers, Search Event pulls the event it belongs to, and the next module can ping your team chat or update a spreadsheet row with the answer.

Feed your CRM with new contacts. Watch New Contacts picks up each contact added in Calendarlink, and Search Organization lets you look up the matching company before you push the record anywhere else.

Publish events from another tool. When an event is planned in a form or a project tool, Create a New Event builds it in Calendarlink, and Lists upcoming events gives you the agenda to share on a page or in a digest.

What Make does not give you here: Make's own documentation for Calendarlink is marked as limited, so the field lists are not described anywhere, and there is no Make an API Call module to reach what the 9 modules miss. If you are weighing tools, read the n8n vs Make comparison, and the Make review covers the editor in depth. When a scenario stops, Make troubleshooting lists the usual causes.

Connect

How do you connect Calendarlink to Make?

  1. 01

    Add a Calendarlink module

    In a scenario, click the +, type Calendarlink and pick any of its modules. The module opens with a Connection field; click Create a connection. A connection is your Calendarlink account linked to Make once, then reused by every Calendarlink module.

  2. 02

    Name the connection

    This step is optional, but a clear name such as the account owner or the workspace helps a lot the day you manage two Calendarlink accounts in the same Make organization.

  3. 03

    Authorize and save

    Depending on what Calendarlink asks, either approve Make on the Calendarlink page that opens, or paste the key your Calendarlink account gives you. Then click Save. The Calendarlink modules can now use your account.

First scenario

Your first scenario: find the event behind each new RSVP

GoalWhen a guest answers an invitation in Calendarlink, Make finds the matching event so the next module knows which one it is.

  1. 01

    Create the scenario

    Open the Scenarios page, click Create a new scenario, then click the large + in the middle of the canvas to add the first module.

  2. 02

    Set the trigger

    Search for Calendarlink, choose Watch New RSVP response and select your connection. Fill the fields the module shows; Make lists what it can read from your account once the connection exists.

  3. 03

    Add the search

    Click the + on the right of the trigger, add Search Event and map data from the RSVP into its fields, so Make looks up the event the answer belongs to.

  4. 04

    Test with Run once

    Answer a test invitation, then click Run once. Each module shows the bundles it received, one bundle per item, so you can check that the right event came back.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. You can add a module of another app after Search Event later.

Triggers

What can start a Calendarlink scenario?

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

Calendarlink1Watch New Contacts

Watch New Contacts

triggerIn the docs only

Watch New Contacts hands your scenario every contact that appears in your Calendarlink account, one bundle per person, so the rest of the flow can file, tag or greet that contact without you copying anything by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default and never faster than 15 minutes on the Free plan.
When to use it
you want new Calendarlink contacts to land in your CRM or mailing list as soon as the next check runs.
Watch out
the documentation does not describe the contact fields, so run the module once and read the bundle before mapping anything.
Calendarlink2Watch New Event

Watch New Event

triggerIn the docs only

With Watch New Event, each event created in Calendarlink becomes the starting point of a scenario, which lets you announce it, log it or prepare what the event needs in your other tools.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new event shows up at the next check rather than the second it is saved.
When to use it
your team publishes events in Calendarlink and wants a message in the team channel or a row in a tracking sheet for each one.
Watch out
if the same scenario also runs Create a New Event, the events it creates will start it again; keep the two in separate scenarios.
Calendarlink3Watch New RSVP response

Watch New RSVP response

triggerIn the docs only

Watch New RSVP response gives you each answer guests send to your invitations, which is the moment most follow-ups start: a thank-you, a reminder to the organizer, an updated head count.

How it fires
scheduled. Make checks the app on the scenario's schedule, not through a webhook, so answers arrive in batches at each check.
When to use it
you organize events and need the attendance list kept current in another app without opening Calendarlink.
Watch out
the answer alone may not say much about the event, so add Search Event after it when the next step needs the event details.
Modules

What can Make do in Calendarlink?

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

Calendarlink1

Create a New Event

ActionIn the docs only

Create a New Event turns data from another app into a Calendarlink event, ready to share, so a planned date in a form or a project tool no longer needs retyping.

When to use it
a webinar or a meeting is approved in another tool and should appear in Calendarlink right after.
Watch out
every run creates a new event, so a scenario that runs twice on the same input leaves a duplicate.
Calendarlink2

Lists upcoming events

ActionIn the docs only

Lists upcoming events returns the events still ahead in your account; judging by its name it hands them over as a list, which gives you a ready agenda to send elsewhere.

When to use it
you want to post the coming events on a page, in a newsletter draft or in a team message.
Watch out
each returned event costs an operation in the modules that follow, so filter the list before sending it further.
Calendarlink3

Search Contact

SearchIn the docs only

Search Contact finds people already saved in Calendarlink, so your scenario can check who someone is before creating or updating anything in another app.

When to use it
a lead arrives from a form and you want to know if that person is already a Calendarlink contact.
Watch out
a search can return zero, one or several contacts; plan the next step for each of those cases.
Calendarlink4

Search Event

SearchIn the docs only

Search Event looks up events in your Calendarlink account and brings their details into the scenario, where another module can use them in a message or a record.

When to use it
a trigger gives you an RSVP or a contact and the next step needs the event it relates to.
Watch out
if nothing matches, the module returns no bundle and the modules after it do not run for that item.
Calendarlink5

Search Event Collections

SearchIn the docs only

Search Event Collections reaches the collections that group your Calendarlink events, which helps when a scenario must work on a whole series instead of a single date.

When to use it
you run a series of sessions and want to pull the collection before sharing it or listing its content.
Watch out
the documentation does not say what a collection contains, so read the bundle from a Run once before mapping it.
Calendarlink6

Search Organization

SearchIn the docs only

Search Organization retrieves the organizations stored in Calendarlink, useful when a record in another app must carry the company name rather than a person.

When to use it
after Watch New Contacts, to attach each new contact to the right company in your CRM.
Watch out
several organizations can match the same query, so decide whether the scenario keeps the first result or handles them all.
Need help

Need help automating Calendarlink with Make?

A person reads every message.

FAQ

Calendarlink and Make: common questions

01Is the Calendarlink Make integration free?
Yes, Calendarlink is a standard app, available from the Make Free plan. That plan gives you 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, which are operations, per month. Make does not charge anything specific for Calendarlink.
02What do you need to connect Calendarlink to Make?
A Calendarlink account and a Make account. Make's documentation for Calendarlink gives no specific prerequisite and no dedicated steps, so the generic flow applies: add a Calendarlink module, click Create a connection, name it if you like, then either authorize Make on the Calendarlink page or paste the key the app gives you, and click Save. The same connection then works for all 9 modules. The connection is created once and reused, so adding a second Calendarlink module later needs no new login.
03Do Calendarlink triggers in Make work in real time?
No. The 3 Calendarlink triggers, Watch New Contacts, Watch New Event and Watch New RSVP response, are scheduled triggers: Make's documentation only lists them, and their type is read from their name ("Watch"). Make checks Calendarlink on the scenario's schedule, every 15 minutes by default. On the Free plan the interval cannot go below 15 minutes; paid plans allow checks every minute. None of the three is an instant trigger, so Calendarlink never calls Make through a webhook when something happens. In practice, the delay between a change in Calendarlink and the scenario run depends on the schedule you set on the first module.
04What if a Calendarlink module is missing in Make?
It depends on what you need. Calendarlink has no Make an API Call module in Make, so you cannot reach an endpoint outside the 9 existing modules from this app. Make's documentation for Calendarlink is also marked as limited. If a module you need is missing, look for another app that holds the same data, or ask the Hack'celeration team to review the case with you. Before looking elsewhere, run each existing module once and read its bundles: the data you need may already be there.
05Should you use Make or n8n for Calendarlink?
It depends on the tool your team already uses. On Make, Calendarlink offers 9 modules: 3 scheduled triggers, 2 actions and 4 searches, usable from the Free plan. The same app often has a node in n8n as well. The honest criterion is coverage: check that the triggers, actions and searches your scenario needs exist on the side you pick, then build where your other automations already live. Either way, test your first scenario with Run once before you commit to one side.
Same platform

Other docs you might need on this stack.

Browse all integrations