RAiN — Rivium AI Network
Back to Help

Google Drive

Cloud file storage and search.

What it does

Finds, reads, uploads and organises files in Drive. The filing cabinet: use it when work produces documents that have to live somewhere the client already looks.

What you need

An account with Google Drive that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Google Drive'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 Drive 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 Drive's own security settings, which works even if you never open RAiN again.

What an agent can do with it

57 actions are available once connected, 6 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 Drive is never offered them.

Action What it does
google_drive_create_comment Create Comment
google_drive_create_file Create File or Folder
google_drive_create_permission Create Permission
google_drive_create_permissions_batch Create Permissions Batch
google_drive_create_reply Create Reply
google_drive_create_drive Create Shared Drive
google_drive_create_shortcut_to_file Create Shortcut to File/Folder
google_drive_create_folder Create a folder
google_drive_delete_comment Delete Comment ⚠️ deletes things
google_drive_delete_permission Delete Permission ⚠️ deletes things
google_drive_delete_reply Delete Reply ⚠️ deletes things
google_drive_delete_drive Delete Shared Drive ⚠️ deletes things
google_drive_download_file Download a file from Google Drive
google_drive_download_file_operation Download file via operation
… and 43 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 property firm's agent files each signed tenancy agreement into the right client folder and renames it to a consistent pattern, so a search actually finds things a year later.

When it goes wrong

A file uploads but nobody can see it. Drive permissions are inherited from the folder. Upload into a shared folder rather than the connected account's own space.

See also