Integrations · Messaging & email

Gmail in the conversation.

The mailbox most business email still starts and ends in. Connect it once and your copilot works with messages, threads, labels, drafts and attachments 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

Gmail

Messaging & email

01 · COPILOT

Ask for it in plain language. It does the Gmail part.

Copilot rides inside the inbox. With Gmail connected it reads messages, threads, labels, drafts and attachments and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Search a mailbox by sender, subject, label or text
Read a thread in full, including attachments
Draft a reply and leave it in the thread for a human to send
Send an email from the connected account
Apply or remove a label
Forward a message with context added

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

02 · WORKFLOWS

Something happens in Gmail. A workflow starts.

Once Gmail 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 new message arrives
A message arrives carrying a chosen label

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

03 · THE AI AGENT STEP

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

What teams do with it

Two ways Gmail earns its connection.

The email nobody in support can see

A customer refers to "the email I sent on Tuesday" — Copilot finds the thread in Gmail and the agent answers it without asking them to resend.

Route the mailbox, keep the mailbox

A workflow fires on a new message to a shared address and opens a Cloodot conversation, so email joins WhatsApp and webchat in one tray without a migration.

Setup

Connect Gmail 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 Gmail in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Gmail from its card.
3
Authorize with your own Gmail account
You sign in on Gmail'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 →

Gmail questions.

How do I connect Gmail to Cloodot?

Open Settings → Apps in Cloodot, switch to Browse, and search for Gmail. Connecting it opens Gmail'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 Gmail?

Work of this kind: search a mailbox by sender, subject, label or text; read a thread in full, including attachments; draft a reply and leave it in the thread for a human to send; send an email from the connected account; apply or remove a label; forward a message with context added. The exact list depends on what your Gmail account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

Can I limit which Gmail 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 Gmail connection is a matter of leaving the writes off.

Can an event in Gmail start a Cloodot workflow?

Yes. Events like a new message arrives, a message arrives carrying a chosen label appear in the workflow editor's trigger picker once Gmail is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Gmail?

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 Gmail account that authorized it, so a messaging & email connection is only ever as broad as the account behind it.

More messaging & email