Integrations · Calendar & scheduling

Google Meet in the conversation.

Google’s video calls, attached to the calendar teams already run on. Connect it once and your copilot works with meetings, conference links, participants and recordings without leaving the thread — and your workflows can act on it while the customer is still typing.

No credit card required · 7-day free trial

Google Meet
Calendar & scheduling
01 · COPILOT

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

Copilot rides inside the inbox. With Google Meet connected it reads meetings, conference links, participants and recordings and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Create a meeting with a join link
  • Read a meeting and its participants
  • List recordings where they exist

What a specific connection exposes is decided by Google Meet, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.

02 · WORKFLOWS

Something happens in Google Meet. A workflow starts.

Once Google Meet 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.

  • A meeting ends

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

03 · THE AI AGENT STEP

One step that decides which Google Meet 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 Meet 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 Meet tools you left enabled and nothing else.

What teams do with it

Two ways Google Meet earns its connection.

01

Calendar and call in one step

Booking the event and generating the Meet link happen together, so the invite the customer gets is complete.

02

Follow-ups that remember the call

A workflow opens the follow-up conversation after the call with what was discussed already attached.

Setup

Connect Google Meet in about a minute.

  1. 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. 2

    Find Google Meet in Browse

    The catalogue runs to hundreds of apps and is searchable. Connect Google Meet from its card.

  3. 3

    Authorize with your own Google Meet account

    You sign in on Google Meet's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.

  4. 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.

Google Meet questions.

How do I connect Google Meet to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Google Meet. Connecting it opens Google Meet'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.
What can Cloodot do in Google Meet?
Work of this kind: create a meeting with a join link; read a meeting and its participants; list recordings where they exist. The exact list depends on what your Google Meet account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Google Meet 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 Meet connection is a matter of leaving the writes off.
Can an event in Google Meet start a Cloodot workflow?
Yes. Events like a meeting ends appear in the workflow editor's trigger picker once Google Meet is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Google Meet?
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 Meet account that authorized it, so a calendar & scheduling connection is only ever as broad as the account behind it.
See it on your own inbox

Try the whole thing, today.

Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.