Files & knowledge · wired today
Google Docs, wired into your agent workforce
Documents and wikis are the long-term memory agents reason over. The Google Docs connector is one of 205 executable connectors and gives agents 1 read-only tool, with the credential held in the vault and every call receipted.
Connecting Google Docs takes one credential
You provide service account json from your Google Docs account; Quox sends it as a Google service account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Google Docs's own API documentation ↗ covers creating and scoping the credential.
What agents can run against Google Docs
get_documentGet a Google Docs document's ID and title by document ID (metadata only, not the document text)
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
How proven is this?
This connector was blind shape-proven against the real Google Docs API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Google Docs integration FAQ
What can Quox agents do with Google Docs?
Agents can run 1 read-only tool against Google Docs: get document. Every call is receipted in the evidence trail.
What does the Google Docs integration need?
You provide service account json from your Google Docs account; Quox sends it as a Google service account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Google Docs credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Google Docs connector?
This connector was blind shape-proven against the real Google Docs API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.