Automations

The base has no Airtable automations, deployed or not. Every automatic effect comes from n8n workflows that read the base through the Airtable API, or from Airtable syncs. No known workflow writes to this base.

n8n workflows that read this base

Workflow	State	Reads from Tooling	Effect
Slack — Workspace Token Cache	Active	Bot Tool Accounts: workspace id, account id, Access Token	Refreshes every five minutes and keeps one bot credential per Slack workspace in an n8n Data Table. See Workspace cache.
Communication — Daily Digest	Active	Slack Tool Accounts, Identity Binding, Person (mirror), table metadata	Resolves each recipient’s Slack account and workspace, then asks the cache for that workspace’s bot. See Daily digest.
Communication — Reading Reply	Active	Nothing directly	Reads bot credentials from the cache.
Email Logging	Inactive since 2026-10-17	Tool Account by Login Alias, Bound Membership ID	Would resolve a mailbox to its membership before writing Communication and CRM records.
Cal.com Booking Intake	Active	Nothing directly	Reads CRM Lead Source, whose account lookups come from the CRM Tool Account mirror. See Cal.com booking.

Syncs are listed in Architecture and ownership.

What does not happen automatically

• Accounts are not created, deactivated or updated from the tools. Source Lifecycle Label changes only when someone edits it.
• No binding is opened or closed when a person joins or leaves; close it with Valid Through.
• Grant expiries do not revoke anything, and nothing checks seats against Seat Count.
• Tokens are not rotated. The cache refreshes from the base; it does not perform OAuth rotation.

Verification boundary

The Airtable automation list is as of 2026-10-28. Workflow states and read paths are as of 2026-10-21. Before relying on them, confirm in n8n that each workflow is still in the state shown, check its execution history, and search other n8n folders for further readers of this base.