Skip to main content

DI-3: Data Integrity Checks

Summary​

DI-3 focuses on basic data quality safeguards in Make.com scenarios and n8n workflows before an automation writes into important systems. FlowBeacon uses this policy to highlight automations that may accept incomplete, malformed, or clearly risky input without enough validation.

Severity: Medium · Category: Data Integrity · Platforms: Make.com, n8n

What FlowBeacon Reviews​

  • Whether write operations appear to be preceded by validation, parsing, or guard logic.
  • Whether required data looks likely to be enforced before downstream updates happen.
  • Whether obviously bad input could move through the automation into a write path unchecked.

Why This Matters​

  • Bad data spreads quickly once it reaches customer, finance, or operational systems.
  • Preventing invalid records early is cheaper than repairing them later.
  • Clear input checks improve trust in automation outcomes.

If This Policy Is Flagged​

  1. Identify the fields and conditions that must be true before the automation writes data.
  2. Add validation or review steps for missing, malformed, or out-of-policy values.
  3. Route rejected records to a safe review path instead of forcing them downstream.
  4. Re-run the evaluation after the write path has stronger guardrails.

Why Users Care​

  • Users get cleaner records and fewer manual cleanup cycles.
  • Delivery teams reduce the risk of automation introducing hidden data issues.
  • Business owners gain more confidence in what the automation is updating.