{"product_id":"n8n-workflow-verify-destination-record-count-guardrails","title":"n8n Workflow: Verify Destination Record Count (Guardrails)","description":"\u003ch3\u003eVerify destination data is really there—before you call it a success\u003c\/h3\u003e\n\u003cp\u003eThis 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.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eManually starts\u003c\/strong\u003e to test the verification logic on demand (useful for validation and pre-flight checks).\u003c\/li\u003e\n  \u003cli\u003eUses a sample \u003ccode\u003edestination_count\u003c\/code\u003e value to simulate the record count read-back from your destination system.\u003c\/li\u003e\n  \u003cli\u003eBuilds an \u003cstrong\u003eoutcome contract\u003c\/strong\u003e that includes: workflow name, outcome name, minimum expected count, observed count, and a timestamp.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCompares observed vs. expected minimum\u003c\/strong\u003e to determine whether the verification criteria are met.\u003c\/li\u003e\n  \u003cli\u003eIf the minimum is met, outputs a \u003cstrong\u003esimple receipt\u003c\/strong\u003e summarizing “observed vs required” counts.\u003c\/li\u003e\n  \u003cli\u003eIf the minimum is not met, \u003cstrong\u003estops the workflow\u003c\/strong\u003e and raises an \u003cstrong\u003eactionable error message\u003c\/strong\u003e describing the failed outcome and the counts.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eData pipeline guardrails:\u003c\/strong\u003e Ensure a destination (database\/export\/search index) has enough records before downstream steps report success.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRelease validation:\u003c\/strong\u003e Run the workflow with passing and failing counts to confirm both branches behave correctly.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSaaS operations checks:\u003c\/strong\u003e Prevent “silent failures” where upstream runs complete but the destination received too little data.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eNodes used:\u003c\/strong\u003e manual trigger, \u003ccode\u003eif\u003c\/code\u003e, \u003ccode\u003eset\u003c\/code\u003e, sticky note, \u003ccode\u003estop\u003c\/code\u003e, and \u003ccode\u003eerror\u003c\/code\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCredential-free:\u003c\/strong\u003e no credential handling is required in the workflow itself.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSetup step:\u003c\/strong\u003e replace the simulated destination read-back with your real read\/query and map the resulting count into \u003ccode\u003edestination_count\u003c\/code\u003e.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eConfiguration:\u003c\/strong\u003e set \u003ccode\u003eworkflow_name\u003c\/code\u003e, \u003ccode\u003eoutcome_name\u003c\/code\u003e, and \u003ccode\u003eexpected_minimum\u003c\/code\u003e to match the business outcome you want to verify.\u003c\/li\u003e\n\u003c\/ul\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45923064479923,"sku":"N8N-18883","price":41.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/920KBvpxS3tf0TOmA9O62_vH9sQDzH.png?v=1788167570","url":"https:\/\/buyflowscripts.com\/products\/n8n-workflow-verify-destination-record-count-guardrails","provider":"N8N Commerce","version":"1.0","type":"link"}