BDS0.1

About automations

Which workflows live here and how each page matches the version running in n8n.

Reviewed 2026-11-06Markdown

A workflow that reads or writes more than one system is documented here, once, instead of in each system it touches. So is a helper workflow that only one system feeds but other workflows call, such as the Slack token cache. The system pages link here and keep only what that system needs to know: which of its records the workflow creates or changes.

An automation that works inside a single base, such as an Airtable automation that fills a UUID, stays in that system’s Automations page.

What a workflow page holds

Each page opens with the workflow’s identity as saved in n8n: platform, workflow ID, status, version, last save, node count and the systems it reads or writes. The body then covers:

  • what triggers it and how the request is checked;
  • each path, step by step, with the node names used in n8n;
  • every field it writes, per table and per node;
  • every node and every connection of that version;
  • settings, error handling, known gaps and how to recover a partial write.

How a page stays exact

A page describes one saved version of the workflow. The version ID in its header is the n8n version ID. When someone saves the workflow in n8n, the version changes, and the page is out of date until it is reviewed against the new version. The review compares node by node and connection by connection, and the page is published only when every node and every connection of the new version is in its tables.

Secrets and callable addresses never appear on these pages: not the webhook path, not signing secrets, not API keys.

Workflows

Workflow Platform Systems Status
Cal.com Booking Intake n8n CRM, Core Active
Communication — Daily Digest n8n KPIs & OKRs, Communication, Tooling and Access Active
Communication — Reading Reply n8n KPIs & OKRs, Tooling and Access Active
Slack — Workspace Token Cache n8n Tooling and Access (helper) Active
Email Capture n8n Communication, CRM, Tooling and Access Active (since 2026-11-06)
CRM — Resolve Context n8n CRM, Tooling and Access (sub-workflow) Inactive (created 2026-11-06)
Communication — Record Email n8n Communication, CRM (sub-workflow) Inactive (created 2026-11-06)
Email Capture — Health Check n8n Communication, Tooling and Access Inactive (created 2026-11-06)
Legacy — Email Logging n8n Communication, CRM, Tooling and Access Inactive, superseded