# Automations

Which flows read or write Communication, and which are inactive.

The base has no Airtable automations. Every write comes from n8n. Confirm a flow's current state and version in n8n before relying on the table below; the Message rows in the base show what the Daily Digest actually did.

| Flow | State | Role in Communication |
| --- | --- | --- |
| [Daily Digest](/automations/daily-digest) | Active; real sends since 2026-10-26 | Reads metadata and the Membership mirror; writes one Message per digest attempt |
| [Email Capture](/automations/email-capture) | Active since 2026-11-06 | Reads the non-reply@ mailbox; calls Record Email for every e-mail of a known Person |
| [Communication — Record Email](/automations/communication-record-email) | Active (sub-workflow) | Writes one Message per e-mail (Sender (Person), Receivers (Person), Account, Participants (Account), Body, Thread Id, Direction, Context) and the CRM Interaction; deduplicates by External Message Id |
| [Legacy — Email Logging](/automations/email-logging) | Inactive, superseded | Replaced by Email Capture on 2026-11-06 |
| Reading Reply | Active | No Communication read or write verified; updates the Slack message and writes Observations in KPIs & OKRs |
| Workspace Token Cache | Active | None; serves Slack bot tokens to the two KPI flows |
| Cal.com Booking Intake | Active | None; registered here as the Webhook channel `cal-com-bookings → n8n → CRM` |

Each flow's complete behavior is documented in Automations: [Daily Digest](/automations/daily-digest), [Reading Reply](/automations/reading-reply), [Slack — Workspace Token Cache](/automations/workspace-token-cache), [Email Capture](/automations/email-capture), [Communication — Record Email](/automations/communication-record-email) and [Cal.com Booking Intake](/automations/calcom-booking-intake). This page keeps only what each one does to Communication.

## What does not happen automatically

No flow reads Channel Binding or Notification Rule to decide what to send. No flow queues a Message and sends it later; rows are written after the attempt. No flow retries a Failed row. No flow retries a No match e-mail after the Person is created; it has to be re-labeled in Gmail. Messages reach the CRM through the view Sync - CRM and the CRM automation "Message — link Interaction, Sender and Receivers", which re-links Interaction, Sender° and Receivers° from Thread Id and coreId; that automation lives in the CRM, not here.

## Verification boundary

Since 2026-11-06 the Daily Digest saves its executions in n8n; for earlier runs the Message table is the only record. Email Capture and its sub-workflows save executions too.