Automations
See what runs, what is disabled and which records each flow writes.
The CRM has one working Airtable automation, which re-links mirrored Messages, plus two empty placeholders. Two n8n workflows write the CRM: Cal.com Booking Intake and Email Capture (through Communication — Record Email); a third, CRM — Resolve Context, only reads it. The Relationship and Participation automations were deleted with their tables on 2026-11-04. The source Campaign UUID assignment belongs to Core.
| Automation | State | Effect |
|---|---|---|
| Message — link Interaction, Sender and Receivers | Deployed 2026-11-06 (Airtable) | When a row is created in Message (mirror), fill the local links the sync cannot: Interaction by Thread Id, Sender° and Receivers° by coreId against People. Fills only empty links; writes nothing else |
| Cal.com Booking Intake | Active in n8n | Capture, reschedule or cancel a booking; write Core Person when missing, create or advance a CRM Deal, write the Interaction |
| Email Capture | Active in n8n since 2026-11-06 | For each seller e-mail copied to non-reply@, resolve the Person and open Deal, then write one Interaction of Type Email per thread (through Communication — Record Email) |
| CRM — Resolve Context | Active in n8n (sub-workflow) | Reads People, Deal and Memberships; writes nothing |
| Automation 1, Automation 2 | Undeployed | Empty placeholders; safe to delete |
How the Message link automation runs
Communication is the source of Message. The CRM table Message (mirror) is a sync of the view Sync - CRM, so a new Message appears in the CRM minutes after the n8n flow writes it, when Airtable refreshes the sync. That refresh creates the mirror row, and the creation fires the automation once for that row. The script reads the row’s Thread Id, Sender (coreid) and Receivers (coreid), looks up the Interaction with the same Thread Id and the People with the same coreId, and writes the three local links. If an Interaction is not there yet, the link stays empty and nothing re-runs; re-run it by hand or with the backfill script. Each row costs one automation run.
What does not happen automatically
A Message that arrives after its Interaction was deleted stays unlinked. A manual Interaction does not copy next contact/action anywhere. A won Deal does not create a contract. Cal.com does not set Campaign° on the Deal or attribute old contacts/deals. The Campaign mirror synchronizes source data; it does not run a sales sequence. The CRM has no workflow that evaluates or delivers KPIs.
Verification boundary
This page covers the CRM base and the CRM folder in n8n; integrations elsewhere are not listed here. To confirm capture is running, check the n8n execution log and look for new or advanced Deal and new Interaction rows after recent bookings or seller e-mails; the automation run history of the Message link automation shows one run per mirrored Message. Keep workflow definitions and webhook secrets out of public pages.