Integrations · Docs & knowledge

Google Docs in the conversation.

The document editor most teams draft policies, scripts and playbooks in. Connect it once and your copilot works with documents, their text and their comments 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 Docs

Docs & knowledge

01 · COPILOT

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

Copilot rides inside the inbox. With Google Docs connected it reads documents, their text and their comments and acts on them from the same panel as the conversation — no second tab, no copying an order number across.

Find a document by title
Read a document as plain text
Create a document from generated content
Append or insert text into a document

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

02 · WORKFLOWS

Something happens in Google Docs. A workflow starts.

Once Google Docs 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 document is created in a watched folder

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

03 · THE AI AGENT STEP

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

What teams do with it

Two ways Google Docs earns its connection.

Answers grounded in the real doc

Copilot reads the escalation playbook straight out of Docs, so a new agent gets the current version rather than the one they were onboarded on.

The weekly write-up, drafted

A workflow assembles the week’s escalations into a Google Doc your lead can edit, instead of a message nobody can revise.

Setup

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

How do I connect Google Docs to Cloodot?

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

Work of this kind: find a document by title; read a document as plain text; create a document from generated content; append or insert text into a document. The exact list depends on what your Google Docs account is allowed to do — Settings → Apps shows every tool the connection actually exposes.

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

Can an event in Google Docs start a Cloodot workflow?

Yes. Events like a document is created in a watched folder appear in the workflow editor's trigger picker once Google Docs is connected, and the event's own fields become variables the rest of the workflow can read.

Who in my team can connect Google Docs?

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

More docs & knowledge