n8n Workflow: Scale Calibration Outcomes Router (Webhook + OpenAI)

Automatically route scale calibration results with NIST 44 tolerance logic + OpenAI classification

This n8n workflow receives scale calibration outcomes through a Webhook, calculates NIST Handbook 44-style tolerance deviations per device, uses OpenAI to classify each result (compliant, out-of-tolerance fail, or condemned), and then routes submissions to the right destination—Google Drive, Gmail, HTTP state registry endpoints, and Google Sheets—with a consolidated audit log per visit.

What this workflow does

• Receives calibration data via POST Webhook including a visit ID, technician details, and an array of device calibration readings.
• Splits the payload per device and computes deviation percent, a tolerance band by device class, and a numeric status hint.
• Validates required fields; malformed readings are appended to an “Invalid Submissions” tab in Google Sheets.
• Classifies each valid device outcome with OpenAI to select one of: compliant, out_of_tolerance_fail, or condemned.
• Compliant routing: stores the certificate file in Google Drive and sends a certification update to the state registry via HTTP.
• Out-of-tolerance routing: sends an urgent Gmail alert to the owner and opens a compliance case in Google Sheets.
• Condemned routing: submits a decommission notice to the state registry via HTTP, logs the decommission record in Google Sheets, then merges all outcomes.
• Consolidated audit log: appends one audit-log row per visit in Google Sheets.

Use cases

• Calibration labs automating end-to-end reporting after technician field visits.
• SaaS operators standardizing compliance workflows that must follow tolerance rules and recordkeeping.
• Automation engineers building reliable routing for certification, compliance cases, and decommission actions.

Technical details

• n8n workflow components: if, set, code, gmail, merge, switch
• Integrations: Webhook, Google Sheets, Google Drive, Gmail, OpenAI, and HTTP state registry endpoints (including an HTTP header configuration step).