Integrations · Docs & knowledge

Google Drive in the conversation.

The file store the rest of the Google workspace hangs off. Connect it once and your copilot works with files, folders, permissions and shared links 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 Drive
Docs & knowledge
01 · COPILOT

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

Copilot rides inside the inbox. With Google Drive connected it reads files, folders, permissions and shared links and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

  • Search Drive for a file by name or content
  • Read a file’s text content
  • Create a folder or upload a generated file
  • Share a file and produce a link
  • List what is in a folder

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

02 · WORKFLOWS

Something happens in Google Drive. A workflow starts.

Once Google Drive 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 file is added to a folder

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

03 · THE AI AGENT STEP

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

What teams do with it

Two ways Google Drive earns its connection.

01

Send the right PDF

A customer asks for the warranty terms — Copilot finds the current PDF in Drive and the agent attaches it without hunting through folders.

02

Every escalation keeps its evidence

A workflow files the transcript and the attachments into a Drive folder per case, so the record exists after the conversation closes.

Setup

Connect Google Drive 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 Drive in Browse

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

  3. 3

    Authorize with your own Google Drive account

    You sign in on Google Drive'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 Drive questions.

How do I connect Google Drive to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Google Drive. Connecting it opens Google Drive'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 Drive?
Work of this kind: search drive for a file by name or content; read a file’s text content; create a folder or upload a generated file; share a file and produce a link; list what is in a folder. The exact list depends on what your Google Drive account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Google Drive 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 Drive connection is a matter of leaving the writes off.
Can an event in Google Drive start a Cloodot workflow?
Yes. Events like a file is added to a folder appear in the workflow editor's trigger picker once Google Drive is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Google Drive?
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 Drive account that authorized it, so a docs & knowledge 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.