← Real Cases
REAL CASEcase-n8n-boundary
n8n — orchestrate without owning business truth
A reusable boundary between the application/API and the orchestrator.
Context
DCP automations connect channels, APIs, ERP systems and agents through n8n.
Problem
Business rules could easily be reconstructed inside workflows, creating two competing sources of truth.
Evidence
- Rewi/MicroPOS integrations.
- Commercial bots.
- APIs exposing authoritative values.
Decision
The application/API owns business truth; n8n coordinates steps, events and systems.
What changed
The application owns truth / orchestrator owns coordination boundary became reusable reference knowledge.
What we learned
- n8n does not replace backend or ERP.
- Persist first, automate after.
- Workflows consume authoritative values.
How to reuse it
- Bots.
- SaaS integrations.
- Internal automations.
What NOT to generalize
- Every process must use n8n.
- n8n is the only valid orchestrator.