Schedule

DJINN + Google Calendar

Schedule awareness in the daily brief: what is coming, what collides, and what needs a decision before it does.

How it connects

01

Calendar risk, not calendar display

You already have a calendar. What you do not have is something reading it against your open work and saying which commitment is about to be missed.

02

Writes wait for a person

Creating or moving an event touches other people's time, so it is proposed rather than performed.

Connector spec

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

Scopes requested

https://www.googleapis.com/auth/calendar.readonly

GET calendar/v3/calendars/${source.id}/events

Emits calendar_event · incremental on updated · cursor pagination

Declared boundary: the connecting operator only

This spec parses and validates, and it has not been run against a live Google Calendar 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 Calendar 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
  • ReferenceDaily brief configuration

Want Google Calendar wired into your own company brain?