Integrations · Calendar & scheduling

Google Calendar in the conversation.

The calendar most teams run on, and the source of truth for who is free when. Connect it once and your copilot works with calendars, events, attendees, invitations and free/busy without leaving the thread — and your workflows can act on it while the customer is still typing.

Start free trial →All integrations

No credit card required · 7-day free trial

Google Calendar

Calendar & scheduling

01 · COPILOT

Ask for it in plain language. It does the Google Calendar part.

Copilot rides inside the inbox. With Google Calendar connected it reads calendars, events, attendees, invitations and free/busy and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Find free time across one or more calendars
Create an event and invite the customer
Read an event with its attendees and conferencing link
Move or cancel an existing event
List what is on a calendar for a date range

What a specific connection exposes is decided by Google Calendar, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch. Google Calendar also has a first-party Cloodot integration with its own settings screen — the two are independent, and you can run either or both.

02 · WORKFLOWS

Something happens in Google Calendar. A workflow starts.

Once Google Calendar is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.

An event is created
An event starts soon
An event is cancelled

The picker is the authority on which events your Google Calendar connection publishes — these are the kinds that apps of this sort emit.

03 · THE AI AGENT STEP

One step that decides which Google Calendar tools to call.

A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.

You declare the output

The rows you name become the variables downstream steps read, so a branch can test what Google Calendar said.

You cap the effort

A step budget and a model tier per node — the loop stops where you told it to.

Only what you switched on

The loop can call the Google Calendar tools you left enabled and nothing else.

What teams do with it

Two ways Google Calendar earns its connection.

Book it inside the conversation

The customer says Thursday afternoon — the agent finds the free slot, creates the event and sends the invite without leaving the thread.

The reminder they will actually read

A workflow fires before an event and sends the reminder on WhatsApp, where a calendar email would have gone unopened.

Setup

Connect Google Calendar in about a minute.

1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
2
Find Google Calendar in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Google Calendar from its card.
3
Authorize with your own Google Calendar account
You sign in on Google Calendar's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.

Open Settings → Apps →

Google Calendar questions.

How do I connect Google Calendar to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Google Calendar. Connecting it opens Google Calendar's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot. Google Calendar also has a first-party Cloodot integration with its own settings screen — the two are independent, and you can run either or both.

What can Cloodot do in Google Calendar?

Work of this kind: find free time across one or more calendars; create an event and invite the customer; read an event with its attendees and conferencing link; move or cancel an existing event; list what is on a calendar for a date range. The exact list depends on what your Google Calendar account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Google Calendar tools Cloodot may use?

Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Google Calendar connection is a matter of leaving the writes off.

Can an event in Google Calendar start a Cloodot workflow?

Yes. Events like an event is created, an event starts soon, an event is cancelled appear in the workflow editor's trigger picker once Google Calendar is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Google Calendar?

Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Google Calendar account that authorized it, so a calendar & scheduling connection is only ever as broad as the account behind it.

More calendar & scheduling