Automations

Nothing in Systems Central runs automatically except Airtable syncs. Every link, status and date described in these pages is set by a person or an agent session.

Automation	State	Effect
Automation 1	Undeployed	None. When a Feedback row is created, it would send the creator’s name to an n8n test webhook
Syncs in (Membership, Organization, Tool, Tags)	Configured in Airtable	Refresh the four mirrors from Core and Tooling and Access
Sync out (CRM Feedback)	Configured in Airtable	Shows Feedback rows with System Key = CRM in CRM - Pedro

Automation 1

Trigger: a record is created in Feedback. Action: a script reads System Key, Created By, Lifecycle Status and Description from the new row, then posts only the creator’s name to a test webhook on the group’s n8n. It is undeployed, so it does not run. Its configuration is valid. No known workflow consumes it. It does not link System from System Key, although the System field description says an automation does. Treat it as an unfinished placeholder. The webhook address is not reproduced here.

n8n

No known n8n workflow reads or writes this base; check n8n before relying on that. The System row Cal.com Booking Intake registers an n8n workflow, but that workflow writes Core and CRM, not Systems Central. See Cal.com Booking Intake.

What does not happen automatically

• System is not linked from System Key on new feedback.
• No notification is sent when Notify Reporter is ticked or Response changes.
• Work Item Status, Done On and Waiting On are not checked or updated.
• Record Types are not detected when a table is created in another base.
• System Rules are not evaluated; Enforced By records where enforcement happens elsewhere.

Syncs

Sync settings, such as refresh interval, field mapping and retention of source deletions, are not exposed by the API; confirm them in each sync’s settings in Airtable. The CRM copy of Feedback is set up as two-way. See Architecture.