ShipHero Login + Case/Base SKU Storage

An inactive, experimental precursor to the API-based SKU pulls. It logs into the ShipHero web app (not the public API) by simulating the full browser OAuth login, then scrapes Case SKUs and their Base SKU components from the internal dashboard and stores them in Supabase.

At a glance

• Status: Inactive
• Trigger: Manual ("When clicking 'Test workflow'"). No production trigger.
• Runs on: Hand-run tests only.
• Talks to: ShipHero (internal web dashboard endpoints via scraped session cookies); Supabase (Case SKUs, Base SKUs).

How it works

1. A multi-step manual login sequence (Open First Page, Auth Scopes, Login ID, extract hidden state via regex, Verify, Password, Submit, Resume, Do Login) accumulates cookies across redirects via Cookie Array code nodes.
2. Get Case SKUs1 calls the internal dashboard/products/v2/getProducts DataTables endpoint (filtered to is_product_case=1); Parse Result parses the JSON.
3. A counter loop over case SKUs looks each up in the Supabase Case SKUs table and fetches its components via getProductCaseComponents.
4. Components are parsed, base SKUs are extracted from HTML anchors via regex, then each is looked up in the Supabase Base SKUs table.

Notes

• Inactive, manual-only experimental precursor to the API-based SKU pulls.
• Contains hardcoded plaintext credentials and hardcoded customer_id / warehouse_id.
• Fragile, since it depends on ShipHero's HTML markup.

Related

• Pull Brand SKUs
• SKU Information Handler
• ShipHero Login → Auth Cookies
• Settings feature · Inventory feature
• Data Flows