Communication
Channels, notification rules and the delivery log that n8n flows read and write.
Communication - Pedro is the base the n8n flows read and write when they talk to people. It registers where messages can go (Channel), which subject each channel serves (Channel Binding), which event sends what to whom (Notification Rule) and every delivery attempt (Message). People, organizations and memberships come from Core; tools and tool workspaces come from Tooling and Access.
Communication records deliveries. It does not record sales conversations, KPI answers or follow-up work: the CRM keeps one Interaction per conversation, KPIs & OKRs keeps the Observation, and each base keeps its own follow-up.
Start here
| Your task | Page |
|---|---|
| Register a channel, bind it to a subject or describe a rule | Register channels and rules |
| Check what was sent, to whom, and what failed | Review deliveries |
| See which flows write here | Automations |
| Understand ownership and mirrors | Architecture and ownership |
| Find a table or view | Entities · Data views |
Choose the right surface
Open Data in Communication - Pedro and work in the table’s Grid view. Every table has exactly one view, a Grid view without filters. There are no intakes or check views yet; Airtable Interfaces are outside the operating model.
What is verified
The reference covers 13 tables (4 native, 9 mirrors), 215 fields and 13 Data views as of 2026-10-28. The base has no Airtable automations. One n8n flow writes here today: the KPIs & OKRs Daily Digest, which logs every Slack direct message it sends or fails to send. It has sent for real since 2026-10-26. Email Logging is built but inactive.
Today the base holds two named channels, no channel bindings, one notification rule and the Daily Digest delivery history. See known gaps before relying on bindings, rules or the message log for anything beyond Daily Digest delivery.