National Commerce Docs
n8n flows

Missing Shipment Data Pull 2.0 (Reconciliation)

A disabled reconciliation copy of the 2.0 flow that backfills missing ShipHero shipment data into Supabase for every active brand.

A one-off reconciliation copy of the 2.0 pull, left disabled. It backfills missing ShipHero shipment data into Supabase for all active brands, reconciling orders, packages, line items, Product SKUs, customers, stores, and brand links.

At a glance

  • Status: Inactive, a reconciliation copy kept disabled.
  • Trigger: A self-restarting webhook, a daily schedule (~03:00), and a manual Test trigger.
  • Runs on: Every active brand, one brand/date at a time.
  • Talks to: ShipHero GraphQL, Supabase, and internal n8n webhooks (SKU lookup, self-restart, voided-label cleanup).

How it works

  1. It loads all active brands and iterates one brand/date at a time; a merge node normalizes the cursor, date, and brand inputs from the webhook or schedule.
  2. It calls ShipHero GraphQL for one day of shipments, paginating by end-cursor, and re-invokes its own webhook to restart after about 150 run-index iterations or to advance one day.
  3. It looks up each shipment/package by Tracking_ID and creates it if missing (box dims, weight, label cost, warehouse link).
  4. It resolves the order, creates Orders records, and links order to shipment, brand, and store.
  5. It finds or creates Shipment Line Items, links them to packages and to Product SKUs (resolved via an internal webhook), dedupes, and marks them valid.
  6. It creates customer records, increments brand onboarding progress, and calls the voided-labels webhook to prune voided shipments, with rate-limit handling.

Notes

  • Nearly identical to the backup flow (~130 nodes) but disabled. It uses recursive webhook self-calls for pagination and day-advancement to survive long runs.

On this page