Workflow 06 / Operations

E-commerce Order Sync

Shopify orders routed to the right warehouse, the CRM and the finance ledger in seconds.

Trigger
New order in Shopify
Size
10 nodes, 6 credentials
Typical build
6 working days
Tools
n8n, Shopify, ShipStation, HubSpot, Google Sheets, Slack

Example scenario: Shopify store, about 1,600 orders a month, a US warehouse and an EU 3PL

The problem

An operations assistant copied about 1,600 orders a month between Shopify, ShipStation, the EU 3PL portal, HubSpot and a finance spreadsheet. EU orders often waited a day before anyone pushed them to the 3PL.

What the workflow does

The solution

A Shopify webhook fires on every new order. n8n maps the order, picks the fulfilment region with a Switch node and creates the shipment in ShipStation or the 3PL API. The customer is upserted to HubSpot with last-order properties, the order is added to the finance ledger and orders over $500 trigger a VIP alert in Slack.

The flow

Drawn from the real JSON

Node names, order and branches are read from the exported file at build time, so this diagram can never drift from what n8n will show you. Dashed lines are connections; amber ones leave an IF, a Switch or an error output.

Download n8n JSON
TriggerAI stepApp actionTransformBranch
10 nodes

Scroll sideways to see all branches

north-americaeuropeothertrue1. Shopify: Order CreatedShopify01Order Created2. Map OrderSet02Map Order3. Switch: RegionSwitch03Region4. ShipStation: Create OrderShipStation04Create Order5. 3PL EU: Create Shipment3PL EU05Create Shipment6. Set WarehouseSet06Set Warehouse7. HubSpot: Upsert CustomerHubSpot07Upsert Customer8. Sheets: Orders LedgerSheets08Orders Ledger9. IF: Order ≥ $500IF09Order ≥ $50010. Slack: #ops VIPSlack10#ops VIP

Node by node

#NodeTypeWhat it does
01Shopify: Order CreatedTriggerFires in real time on orders/create
02Map OrderTransformSets 10 fields: orderId, orderNumber, email, customer…
03Switch: RegionBranchRoutes to: north-america, europe, other
04ShipStation: Create OrderApp actionPOST ssapi.shipstation.com/orders/createorder
053PL EU: Create ShipmentApp actionPOST api.nl-fulfil.example/v2/shipments
06Set WarehouseTransformSets 3 fields: orderNumber, warehouse, total
07HubSpot: Upsert CustomerApp actionCreates or updates a contact
08Sheets: Orders LedgerApp actionAppends a row to the "Orders" tab
09IF: Order ≥ $500BranchTrue if total >= 500
10Slack: #ops VIPApp actionPosts a message to #ops

How a run goes

  1. Shopify trigger receives orders/create in real time.

  2. A Set node maps customer, totals and items, and computes the fulfilment region.

  3. Switch sends North American orders to ShipStation and EU orders to the EU 3PL, with billing and shipping address, line items and your warehouse ID (the order key makes retries safe).

  4. The chosen warehouse is recorded and the customer is upserted in HubSpot.

  5. Google Sheets appends the order to the finance ledger.

  6. IF the order is $500 or more, Slack alerts operations to add a handwritten note.

Tools and credentials

Credentials are referenced by name inside the JSON. Create each one in n8n under Credentials, using these names, and the nodes connect automatically.

Credential nameWhat you need
Shopify – Store AdminAdmin API access token of a custom app
ShipStation API KeyHeader name and secret value of the remote API
EU 3PL API KeyHeader name and secret value of the remote API
HubSpot – Private AppPrivate app token with contacts and deals write scopes
Google Sheets – OpsGoogle OAuth client with the Sheets API enabled
Slack – Flowforge BotBot token with the chat:write scope

Setup in about 30 minutes

  1. Import the file. In n8n open Workflows, then Import from file, and pick order-sync.json. The workflow arrives inactive.

  2. Create the 6 credentials listed above with exactly those names.

  3. Replace the placeholders with your own IDs:

    • REPLACE_WITH_SHIPSTATION_WAREHOUSE_ID in “Map Order”
    • REPLACE_WITH_ORDERS_SHEET_ID in “Sheets: Orders Ledger”
  4. Adapt it to your business.

    • Create a Shopify custom app with read access to orders and customers and paste its Admin API token into the credential.
    • Paste your ShipStation warehouse ID into the shipstationWarehouseId field of "Map Order".
    • Replace the 3PL endpoint in "3PL EU: Create Shipment" with your provider's API and map its required fields.
    • Adjust the region rule in "Map Order" to your shipping zones; anything unmatched goes to the manual-review output.
    • Change the VIP limit in "IF: Order ≥ $500" to whatever deserves a handwritten note in your shop.
  5. Connect error reporting. Import error-reporter.json once, then open this workflow’s Settings and choose it as the Error workflow. Failed runs are posted to Slack and logged, with a link to retry.

  6. Test, then activate. Run the first node with sample data, check each output in the execution view, then switch the workflow to active. Keep the test run for your records.

Example figures for the scenario above, not guarantees

What this kind of build changes

1,600orders a month synced hands-free
< 20 sfrom checkout to warehouse
-1 dayEU dispatch time
55 hops time saved monthly

Use it, or have it built for you

The JSON is free to import and adapt. If you would rather have it wired to your own stack and tested on your data, a single flow like this is a fixed-price project.