Docs
DJINN + Google Docs
Documents as grounded source material — answers cite the doc rather than paraphrasing from memory.
How it connects
Cited, not recalled
An answer from a document names the document. That is what makes it checkable, and checkable is the difference between useful and dangerous.
Drafting into your format
Output lands in the structure your team already uses instead of a wall of chat text.
Connector spec
- Auth
- oauth2 · google_v2
- Host
- https://docs.google.com
Scopes requested
GET drive/v3/files/${source.id}/export
Emits doc · incremental on modifiedTime
Declared boundary: per record via drive/v3/files/${source.id}/permissions
This spec parses and validates, and it has not been run against a live Google Docs account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Google Docs setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupOAuth setup and scopes
- ReferenceDocument grounding and citation
Want Google Docs wired into your own company brain?