Medusa Product Upsert Webhook Workflow (n8n) via Admin API

Upsert Medusa products automatically from your PIM—using an n8n webhook

This Medusa Product Upsert Webhook Workflow (n8n) via Admin API receives product-launch webhooks from a PIM, then creates or updates products in Medusa by handle, assigns them to the right category and collection, and publishes to the correct sales channel. It finishes by returning a clear JSON response describing what happened.

What this workflow does

• Receives a POST webhook request with product details, pricing, and destination merchandising IDs.
• Validates and normalizes required fields—including handle, SKU, currency, amount, category_id, collection_id, and sales_channel_id.
• Searches Medusa by product handle to determine whether the product already exists.
• Upserts the product: updates core fields if found, or creates a new Medusa product with an initial priced variant if not.
• Links merchandising destinations by adding the product to the specified Medusa product category and product collection.
• Publishes to a sales channel so the product becomes available in the intended Medusa sales channel.
• Returns a JSON response indicating whether the product was created or updated, including product and destination IDs.

Use cases

• When a catalog team launches a product in a PIM, automatically push it into Medusa and make it sellable in the correct sales channel.
• Use handle-based upserts to keep Medusa synchronized when product attributes or pricing change.
• Rapid onboarding of new products: category/collection/sales-channel placement happens automatically via IDs sent from your source system.

Technical details

• Install the community node package @blackswampai/n8n-nodes-medusa.
• Create a Medusa Admin API credential in n8n.
• Webhook endpoint receives the payload from your PIM.
• Uses n8n nodes: if, set, code, merge, webhook, and sticky note.

Copy the workflow webhook URL from n8n and configure it in your PIM’s outbound webhook settings.