n8n Workflow: Verify Destination Record Count (Guardrails)

Verify destination data is really there—before you call it a success

This credential-free n8n workflow checks whether a destination system contains at least a minimum number of records. It generates a clear verification “receipt” when the guardrail passes, or stops the run with an actionable error when the record count is too low—so you don’t ship broken automation results.

What this workflow does

• Manually starts to test the verification logic on demand (useful for validation and pre-flight checks).
• Uses a sample destination_count value to simulate the record count read-back from your destination system.
• Builds an outcome contract that includes: workflow name, outcome name, minimum expected count, observed count, and a timestamp.
• Compares observed vs. expected minimum to determine whether the verification criteria are met.
• If the minimum is met, outputs a simple receipt summarizing “observed vs required” counts.
• If the minimum is not met, stops the workflow and raises an actionable error message describing the failed outcome and the counts.

Use cases

• Data pipeline guardrails: Ensure a destination (database/export/search index) has enough records before downstream steps report success.
• Release validation: Run the workflow with passing and failing counts to confirm both branches behave correctly.
• SaaS operations checks: Prevent “silent failures” where upstream runs complete but the destination received too little data.

Technical details

• Nodes used: manual trigger, if, set, sticky note, stop, and error.
• Credential-free: no credential handling is required in the workflow itself.
• Setup step: replace the simulated destination read-back with your real read/query and map the resulting count into destination_count.
• Configuration: set workflow_name, outcome_name, and expected_minimum to match the business outcome you want to verify.