Email Meeting Sync
Gmail and Circleback retain their intended cadences, but both adapters are paused until their exact credentials and source receipts pass readiness.
Email and meeting syncs collect private, account/provider-scoped evidence
first. Both are proposal-only adapters under source.absorb; they cannot write
wiki owners directly. Source: automations/email-sync.md;
automations/meeting-sync.md
Jobs
| Job | Command or contract | Cadence | State keys |
|---|---|---|---|
email-sync |
Paused V2; exact Gmail read-only scope | Intended every 4 hours after activation | Per-account integration clocks plus proven global syncs.email |
meeting-sync |
Paused V2; Circleback token and revision fixture | Intended daily after activation | Provider receipt plus proven syncs.meetings |
Promotion Criteria
Promote when the source changes durable context: a real person relationship, company/project status, decision, follow-up that affects future work, or reusable communication pattern. Keep routine email, signatures, and low-signal meeting chatter in raw/output.
Failure Handling
Missing scopes, expired tokens, absent Circleback credentials, partial account
or transcript windows, and collection failures hold syncs.*. A blocked
definition is setup state, not a completed scheduled check.
Timeline
-
2026-08-12 | Migrated both legacy jobs to paused V2 proposal-only source adapters, separated account/provider identity, and removed direct entity propagation. Source:
automations/email-sync.md;automations/meeting-sync.md; connector contract tests -
2026-07-01 | Separated Gmail four-hour collection from daily meeting sync and clarified collection vs promotion state writes. Source: User request, 2026-07-01
-
2026-06-30 | Moved Gmail into the every-four-hours communications loop while keeping Circleback on daily meeting transcript sync. Source: User request, 2026-06-30;
automations/email-sync.md -
2026-05-31 | Email/meeting sync from integration recipes. Source: public wiki expansion, 2026-05-31