Ops · n8n

Route Failed Quality Inspections for Rework or Rejection

Keep quality tight by routing each failed inspection to rework or rejection based on the defect, and tracking the outcome.

difficulty Intermediatesetup 35 minresult Failed inspections are handled consistently and tracked, protecting product quality and reducing escapes.
  1. 1

    Capture Inspections

    Add a Google Sheets Trigger on the inspection results form.

  2. 2

    Classify the Failure

    Add a Code node deciding rework versus rejection by defect type.

  3. 3

    Route the Item

    Add a Slack node sending each failure to the responsible team.

  4. 4

    Track the Outcome

    Add an Airtable node recording the disposition for quality reporting.

  5. 5

    Activate and Test

    Activate the workflow with a failed test inspection. Confirm routing works.

Frequently asked questions

Can I spot defect trends?

Aggregate failures by type and line to find recurring quality issues worth fixing at the source.

What about borderline cases?

Route ambiguous results to a supervisor rather than auto-deciding rework or rejection.

About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.