Sync multi-location inventory to Medusa from any WMS or ERP
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 10 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Medusa (community).
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Validate Stock Feed (Code): runs custom JavaScript code
- Fetch Inventory Item by SKU (Medusa): work with inventory item
- If: checks a condition and branches into true / false
- Set Inventory Level (Medusa): set level (inventory item)
- Log Missing SKU (Edit Fields (Set)): sets 5 fields: status, sku, stock_location_id…
- Log Synced SKU (Edit Fields (Set)): sets 5 fields: status, sku, inventory_item_id…
- Merge: merges the data from its input branches
- Prepare Sync Report (Code): runs custom JavaScript code
- Send Sync Report (Respond to Webhook): sends the response back to the webhook caller
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @blackswampai/n8n-nodes-medusa is verified or supports 3.0 (used in Fetch Inventory Item by SKU, Set Inventory Level).
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - Medusa
@blackswampai/n8n-nodes-medusa.medusa - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Respond to Webhook
n8n-nodes-base.respondToWebhook
From the author
Quick Overview This workflow receives a stock feed via webhook, validates and expands SKU rows, then syncs per-location inventory levels to Medusa by matching inventory items by SKU and returning a JSON report of synced and missing items. How it works 1.…