Email Meeting Sync
Gmail runs on the four-hour communication loop; Circleback meeting sync runs daily when credentials are configured.
Email and meeting syncs collect raw evidence first. Durable wiki promotion happens only for project decisions, person/company context, action items, career signals, or repeated workflows. Source: automations/email-sync.md; automations/meeting-sync.md
Jobs
| Job | Command or contract | Cadence | State keys |
|---|---|---|---|
email-sync |
automations/email-sync.md, Gmail scripts |
Every 4 hours | automations.email-sync, syncs.email |
meeting-sync |
automations/meeting-sync.md, Circleback scripts |
Daily | automations.meeting-sync, 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 OAuth, expired tokens, absent Circleback credentials, or collection failures should leave syncs.* stale. Write blocker output and update only the automation run state when the scheduled check actually happened.
Timeline
- 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