n8n Workflow: Verify Shipment Docs in OneDrive vs SharePoint

Verify shipment document packs in OneDrive against SharePoint instructions—automatically

This n8n workflow checks each shipment’s OneDrive document pack (including bill of lading, phytosanitary, and origin certificates) against the required shipping instructions stored in a SharePoint “Shipments” list. It verifies presence using fixed rules, extracts specified field values from documents with Anthropic (Messages API), and flags discrepancies for a named approver—then triggers Outlook chasing for missing originals.

What this workflow does

• Runs on schedule and on file creation: it executes every morning and also re-checks a specific shipment when a new file is created in a OneDrive shipment subfolder.
• Matches OneDrive shipments to SharePoint data: lists shipment folders in OneDrive, matches each folder to a row in the SharePoint “Shipments” list, and loads the required document requirement rows from the SharePoint “Document requirements” list.
• Validates draft/original presence and overdue originals: scans OneDrive drafts/ and originals/ subfolders, classifies documents by filename, checks required drafts/originals, and determines whether originals are overdue for chasing.
• Extracts and compares field values: for required draft documents with fields to verify, the workflow downloads the file and sends it to Anthropic (Messages API) to extract the specified fields, then compares extracted values against the SharePoint instruction fields using fixed rules and tolerances.
• Creates a per-shipment work status: calculates a status and next step (e.g., ready for approval, discrepancy, awaiting originals, or complete) and writes results back to the SharePoint “Shipments” list.
• Logs and pursues originals: appends status-change and chase events to a SharePoint “Document log” list and emails the document control desk and/or the counterpar via Outlook.

Use cases

• Automate document control for sea freight shipments by ensuring OneDrive packs match SharePoint requirements.
• Detect discrepancies early by extracting key fields from draft documents and comparing to shipment instructions.
• Reduce manual follow-ups by tracking overdue originals and initiating Outlook email chasing.

Technical details

• Workflow category: n8n automation workflow
• Core integrations: OneDrive, SharePoint lists (“Shipments”, “Document requirements”, “Document log”), Anthropic (Messages API), Outlook
• n8n nodes used (per design): if, set, code, form, sticky note, form trigger