All integrations

Google Docs

GOOGLE WORKSPACE · FILES & DOCS

Read and edit the documents that person can already open.

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

google_docs_createWRITE

Create a new Google Docs document.

documents
google_docs_delete_contentWRITE

Delete content from a Google Doc between start and end indexes.

documents
google_docs_getREAD

Get the content and metadata of a Google Doc.

documents.readonly
google_docs_insert_imageWRITE

Insert an image into a Google Doc at a specific position.

documents
google_docs_insert_tableWRITE

Insert a table into a Google Doc at a specific position.

documents
google_docs_insert_textWRITE

Insert text at a specific position in a Google Doc.

documents
google_docs_listREAD

List Google Docs documents.

drive.readonly
google_docs_replace_textWRITE

Find and replace text throughout a Google Doc.

documents

Put Google Docs behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.