DJINN + Gmail
DJINN reads threads to answer questions with real context. Sending stays behind a person, deliberately.
How it connects
Read to ground the answer
Mail is context, not a task queue. A question about a client is answered against the actual thread rather than someone's recollection of it.
Drafting is not sending
DJINN writes the reply. A person reads it and presses send. Sending is an outbound action and the tool layer enforces the gate.
Connector spec
- Auth
- oauth2 · google_v2
- Host
- https://gmail.com
Scopes requested
GET users/me/messages
Emits email · incremental on internalDate · cursor pagination
Declared boundary: the connecting operator only
This spec parses and validates, and it has not been run against a live Gmail 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
Gmail 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
- PolicyWhy sending stays human-approved
Want Gmail wired into your own company brain?