Ops data
DJINN + Google Sheets
The spreadsheet that is quietly running an operation, read and reported on like a real data source.
How it connects
Where the real process lives
Most companies run something important out of a sheet. Treating it as a data source beats pretending it will be migrated.
Read freely, write carefully
Reads are automatic. Writing into a sheet people depend on waits for a person.
Connector spec
- Auth
- oauth2 · google_v2
- Host
- https://sheets.google.com
Scopes requested
GET drive/v3/files/${source.id}/export
Emits sheet · 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 Sheets 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 Sheets 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.
- SetupSheet access and range scoping
- PolicyWrite boundaries
Want Google Sheets wired into your own company brain?