Files

DJINN + Google Drive

The file layer behind document search — finding the thing nobody can remember the name of.

How it connects

01

Search that knows the company

Drive search matches filenames. This matches what you were actually trying to find, using the same memory that answers everything else.

02

Scoped, not wholesale

Access is scoped to the folders that matter rather than an entire corporate drive.

Connector spec

Auth
oauth2 · google_v2
Host
https://drive.google.com

Scopes requested

https://www.googleapis.com/auth/drive.readonlyhttps://www.googleapis.com/auth/documents.readonly

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 Drive 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 Drive 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.

  • SetupScope configuration and re-auth
  • PolicyFolder scoping policy

Want Google Drive wired into your own company brain?