Maintain Communication

The Communication maintainer keeps channels, bindings and rules accurate and watches the delivery log. The Daily Digest maintainer owns its Message rows and failures. Core and Tooling and Access maintainers correct the shared facts the mirrors bring in. No on-call owner or response time is set.

Daily review

After the scheduled Daily Digest run (rows appear around 12:00 UTC), open Message → Grid view and check the newest rows: the count of Sent rows with real Slack timestamps, and every Failed row. A recurring Person not found in Tooling mirror names a recipient whose Slack account is not bound in Tooling and Access. Execution history is not saved in n8n for this flow, so these rows are the only evidence of a run.

Change safely

The Daily Digest addresses this base by table and field IDs and checks the schema at the start of each run. Renaming a field is safe for an ID-based write; deleting or retyping one breaks it. Before changing Message, Channel or the Membership mirror, list the flows in Automations and confirm each one’s dependency. Keep External Message Id and Membership # stable: they are the keys flows match on.

Add select options in the Airtable UI; they cannot be created through the API. Never edit a sent Message’s Body or Status to repair history; record the correction in a new row or in the owning base.

Protect identifiers

External Identifier can hold a webhook URL or an e-mail address. Do not paste these values into documentation, tickets or screenshots. Rotate a webhook whose URL was exposed, then update the Channel row.

Refresh this documentation

Refresh these pages after a change to fields, views, mirrors, select options, a flow that reads or writes the base, or the activation of Email Logging. Re-read the live schema, the view list and the newest Message rows, and update the counts in the overview and the Daily Digest page.