Resources · Make integration

Google Calendar Make integrationAutomate Google Calendar with Make.

Your calendar can do the booking and the blocking on its own. A Google Calendar Make integration gives you 20 modules, the bricks you drop into Make, to read and write events without code. This page covers the 3 connection steps and a first working setup.

Try the Google Calendar integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can a Google Calendar Make integration actually do?

It lets Make read and write your calendar for you. The calendar joins a scenario, the automation you build in Make as a chain of modules that runs on a schedule or when an app calls Make. One module watches what happens, the next ones create, copy, move or clear entries, and the calendars your team relies on stop drifting apart.

The setup most people build first is a shared calendar that fills itself. Watch Events spots every entry landing in the booking calendar, and Create an Event writes the matching block on the calendar the whole team reads.

Then comes the end of double bookings. Get Free/Busy Information says whether a set of calendars is busy without opening a single event, and Search Events checks what is already on the day.

Third use: opening a client file. Create a Calendar gives the account its own calendar, Create an Access Control Rule hands the right people access, and the dates are visible on day one.

What Make will not do here is anything outside events, calendars and access rules: the list of 20 modules stops there. Make an API Call picks up the rest, reaching any endpoint of the Google Calendar API, the door Google opens to other software, with the connection you already made. The same calendar exists on the n8n side too: the Google Calendar n8n integration and the n8n vs Make comparison lay out the criteria, and Make training walks the editor slower.

Connect

How do you connect your Google account to Make?

  1. 01

    Add a module and start the connection

    Drop any Google Calendar module into a scenario, then click Create a connection. A connection is your Google account tied to Make once, and every Google Calendar module you add later reuses it. A Google account is the only prerequisite.

  2. 02

    Name it, leave the advanced part alone

    The Connection name field is optional, though a clear name saves you hunting later. The Show advanced settings toggle is optional too, and it only matters if you bring the client credentials of your own Google Cloud Platform project.

  3. 03

    Sign in and grant everything

    Click Sign in with Google, pick the account that owns the calendars, then authenticate if Google asks. Grant all the permissions it requests and confirm access: that screen is what gives Make the right to read and write your calendars.

First scenario

Your first scenario, start to finish

GoalWhen a new interview lands in the recruiting calendar, Make writes the same slot on the shared hiring calendar.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario, then click the + to add the first module. Search Google Calendar by name and pick Watch Events.

  2. 02

    Point the trigger at one calendar

    Once the connection exists, Make lists the calendars it can read. Pick the recruiting one from that list instead of typing anything, then fill the rest of the module fields.

  3. 03

    Add the action

    Click the + on the right of the trigger and add Create an Event. Map the data coming out of the first module into it, so the new slot carries what the original already holds.

  4. 04

    Test with Run once

    Click Run once, the button that runs the scenario a single time, then create a test event. Each module shows the bundles it received, one bundle per event that came through.

  5. 05

    Schedule it and switch it on

    Set the clock on the first module under Scheduling. A new scenario checks every 15 minutes, which is also the floor on the Free plan. Then switch the scenario on.

Triggers

What can start a Google Calendar scenario

1 module starts a scenario when something happens in Google Calendar. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Google Calendar as soon as it happens.

Google Calendar1Watch Events

Watch Events

Scheduled trigger

In Make“Triggers when an event is created, updated, deleted, started or ended in a selected calendar.”

One calendar, watched from the outside: Watch Events hands your scenario what happens there, an entry that appears, one that changes, one that disappears, plus the moment an event starts or ends.

How it fires
on a schedule. Make goes and checks the calendar at the pace you set on the first module, so nothing arrives the second it happens in Google Calendar.
When to use it
a booking calendar your clients write into, where every new slot has to reach the rest of the team.
Watch out
each pass that finds events costs operations, one per module run on one bundle, so a busy calendar on a short interval adds up.
Modules

What Google Calendar can do inside Make

Google Calendar gives you 19 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Event

6 modules
Google Calendar1

Search Events

Search

In Make“Searches for events on the specified calendar.”

Give it your criteria and Search Events combs one calendar for you. What comes back can be nothing, one event, or a long list, each result as its own bundle.

When to use it
before writing anything, to see whether the interview slot already has something on it.
Watch out
an empty result is not a failure, the scenario simply carries on empty handed, so decide what should happen then.
Google Calendar2

Get an Event

Action

In Make“Returns metadata for an event in the specific calendar.”

Point Get an Event at one event on a given calendar and it comes back with that event's full record, not a list.

When to use it
a later module needs the details of an interview the trigger only pointed at.
Google Calendar3

Create an Event

Action

In Make“Creates a new event.”

The workhorse of the app: Create an Event writes a new entry into whichever calendar you point it at, with whatever the earlier modules hand it.

When to use it
a signed deal turns into a kickoff call on the account manager's calendar.
Google Calendar4

Duplicate an Event

Action

In Make“Duplicates an event.”

Rather than rebuilding an entry field by field, Duplicate an Event copies one that already exists, so the copy starts from the same content and you adjust the rest in the module fields.

When to use it
a demo that keeps the same shape every time, with one or two things to change afterwards.
Google Calendar5

Update an Event

Action

In Make“Updates an existing event.”

Changing what is already booked is not the same as booking again. Update an Event edits the entry in place, so the calendar keeps one line instead of two.

When to use it
a candidate pushes an interview back and the slot has to follow, not multiply.
Watch out
it needs to know which event to touch, so something earlier in the scenario, the trigger or a search, has to point it there.
Google Calendar6

Delete an Event

Action

In Make“Deletes an event.”

Removing an entry from a calendar is all Delete an Event does, and it does not ask twice.

When to use it
a cancelled onboarding session that should stop holding the room.
Watch out
there is no undo here. Test it with Run once on a throwaway calendar before you let it loose on a real one.

Calendar

6 modules
Google Calendar7

List Calendars

Search

In Make“Returns the calendars on the user's calendar list.”

Every calendar your connection can reach comes back from List Calendars, one bundle per calendar, so a scenario can find its target instead of being told where to write.

When to use it
a setup that has to work across several team calendars without you naming each one by hand.
Google Calendar8

Get a Calendar

Action

In Make“Returns metadata for a calendar.”

One calendar, its details, nothing else: Get a Calendar brings back the record of the calendar you name.

When to use it
a check before a write, so the scenario is sure it is aiming at the client calendar and not the personal one.
Google Calendar9

Create a Calendar

Action

In Make“Creates a new calendar.”

No one has to click through Google Calendar to start a new one. Create a Calendar opens it from the scenario, empty and ready to receive events.

When to use it
every new account gets its own calendar the day the contract lands, not a week later when someone remembers.
Google Calendar10

Update a Calendar

Action

In Make“Updates an existing calendar.”

Already have the calendar and need it to say something else? Update a Calendar edits the calendar itself, not the events inside it.

When to use it
a product gets renamed and the calendar follows without anyone opening Google Calendar.
Google Calendar11

Delete a Calendar

Action

In Make“Deletes a calendar.”

The whole calendar goes, along with everything that was on it, and Delete a Calendar does not ask for a second opinion.

When to use it
an archive step once the engagement is over and its dates have been copied somewhere safe.
Watch out
nothing comes back afterwards, so keep this one out of any scenario running unattended on a schedule.
Google Calendar12

Clear a Calendar

Action

In Make“Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.”

This one empties the primary calendar of an account: Clear a Calendar deletes every event attached to it and leaves the calendar standing.

When to use it
a test account you reset between two builds.
Watch out
it hits the account's primary calendar, the one people actually live in. Read the connection twice before you run it.

Access Control Rule

5 modules
Google Calendar13

List Access Control Rules

Search

In Make“Returns the rules in the access control list for the calendar.”

Who can see what on a calendar comes back from List Access Control Rules, one rule per bundle, so the access list becomes something a scenario reads instead of something someone screenshots.

When to use it
a review of who still sees the leadership calendar, pulled by a scenario instead of by hand.
Google Calendar14

Get an Access Control Rule

Action

In Make“Returns metadata of an access control rule.”

Where the list gives you everyone, Get an Access Control Rule gives you one: the record of a single rule on a single calendar, fetched when the scenario asks.

When to use it
checking what one person was granted before you change it, so the next module is not working blind.
Google Calendar15

Create an Access Control Rule

Action

In Make“Creates a new access control rule.”

Sharing a calendar can happen inside the scenario rather than in someone's to-do list. Create an Access Control Rule grants the access, at the level you set in the module fields.

When to use it
a new hire lands and the team calendars open the same day.
Google Calendar16

Update an Access Control Rule

Action

In Make“Updates an existing access control rule.”

Access that already exists can change level, and Update an Access Control Rule is what changes it on a rule already in place.

When to use it
someone moves from reading the calendar to running it, and the rule should say so.
Google Calendar17

Delete an Access Control Rule

Action

In Make“Deletes an access control rule.”

Access comes back off the same way it went on, one rule at a time, and Delete an Access Control Rule is the module that does it.

When to use it
the offboarding scenario, closing calendars at the same time as the mailbox.
Watch out
a rule you remove does not come back from the scenario side, so make sure the module before it targets the right one.

Other

2 modules
Google Calendar18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other modules leave out is still reachable: Make an API Call hits any endpoint of the Google Calendar API through the connection you already made.

When to use it
what you need exists in Google's API but not in the list of 20 modules.
Watch out
Make's use and transfer of anything received from Google APIs follows the Google API Services User Data Policy, and you have to know the endpoint you are calling.
Google Calendar19

Get Free/Busy Information

Action

In Make“Returns free/busy information for a set of calendars.”

Occupied or free, nothing more, over the window you choose: Get Free/Busy Information answers for a set of calendars without opening a single event.

When to use it
finding a slot that works for four people before the scenario books anything.
Watch out
busy or free is all you get back, no titles and no guests, which is exactly what makes it safe to run across calendars you do not own.
Need help

Need help automating Google Calendar with Make?

A person reads every message.

FAQ

What people ask next

01Is the Google Calendar Make integration free?
Yes, within the limits of the Free plan. Google Calendar is a standard app, so it is available from the free tier with nothing extra to pay on Make's side. What the Free plan caps is the rest: 2 active scenarios, a floor 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 drop the interval to 1 minute, lift the cap on active scenarios and stretch execution to 40 minutes, with usage counted in credits, which are operations.
02What do you need to connect Google Calendar to Make?
A Google account, and that is the whole prerequisite. Add any Google Calendar module to a scenario, click Create a connection, give it a name if you want one, then click Sign in with Google and grant every permission it asks for before confirming access. The connection is made once and reused by every Google Calendar module in every scenario afterwards. If your company insists on its own Google Cloud Platform project, the Show advanced settings toggle takes your client credentials instead, which means creating the project, enabling the Google Calendar API and registering Make's redirect URI.
03Does Watch Events react in real time?
No. Watch Events is a scheduled trigger, which means Make goes and looks at the calendar at the interval set on the first module rather than being called by Google. A new scenario checks every 15 minutes, and 15 minutes is also the floor on the Free plan, down to 1 minute on paid plans. Google Calendar has no instant trigger in Make, the kind where the app warns Make the second something happens, so plan for a gap between the booking and the reaction. On a calendar, that gap almost never costs anything.
04What if a module is missing or a limit gets in the way?
Use Make an API Call. It exists for Google Calendar and reaches any endpoint of the Google Calendar API with the connection you already set up, so anything outside the 20 listed modules is still reachable from the same scenario. Two caveats. You need to know which endpoint you are calling, since that module asks for it rather than offering a list. And Make's use and transfer of information received from Google APIs follows the Google API Services User Data Policy, whichever route you take.
05Make or n8n for Google Calendar?
Whoever maintains the scenario later is the real decider, not the app itself. Make shows every module as a shape on a canvas, so a teammate who has never written code can follow the flow and spot what broke by looking at it. n8n expects more comfort with logic and hosting, in exchange for keeping automations in a code repository your developers already use. Google Calendar behaves the same on either tool, so build the same scenario on both and let whoever will actually maintain it make the call.
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