RAiN — Rivium AI Network
Back to Help

Google Docs

Read, write, and manage collaborative documents.

What it does

Reads and writes Google Documents. Where an agent's output should end up as a document somebody opens and edits rather than an email they skim.

What you need

An account with Google Docs that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Google Docs's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.

Connecting it

Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.

  1. Open the project and stay on the Visual Editor tab.
  2. Open the Tools & Integrations rail on the right.
  3. Find Google Docs and press Connect.
  4. Authorise in the window that opens, then come back. The rail will show it as connected.

The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.

To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Google Docs's own security settings, which works even if you never open RAiN again.

What an agent can do with it

34 actions are available once connected, 7 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Google Docs is never offered them.

Action What it does
google_docs_copy_document Copy Google Document
google_docs_create_document_markdown Create Document Markdown
google_docs_create_tab Create Document Tab
google_docs_create_footer Create Footer
google_docs_create_footnote Create Footnote
google_docs_create_header Create Header
google_docs_create_named_range Create Named Range
google_docs_create_paragraph_bullets Create Paragraph Bullets
google_docs_create_and_populate_table Create and Populate Table in Google Doc
google_docs_delete_content_range Delete Content Range in Document ⚠️ deletes things
google_docs_delete_footer Delete Footer ⚠️ deletes things
google_docs_delete_header Delete Header ⚠️ deletes things
google_docs_delete_named_range Delete Named Range ⚠️ deletes things
google_docs_delete_paragraph_bullets Delete Paragraph Bullets
… and 20 more, all listed in the rail

Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.

A worked example

A consultancy's agent drafts a weekly client report into a Google Doc, and the account manager edits it before sending. The draft is ready before anybody sits down.

When it goes wrong

Formatting comes out flat. These actions write text and structure, not design. Put the styling in a template document and have the agent fill it.

See also