Magento 2 n8n integrationAutomate Magento 2 with n8n.
Your store data stops living only inside the admin panel. The Magento 2 n8n integration exposes 15 operations across 4 resources: customers, invoices, orders and products. The node has no trigger of its own, so another node starts the workflow and hands it the data.
Verified Trustpilot reviews · AI, automation & growth agency
What does the Magento 2 n8n integration actually do?
The Magento 2 node lets an n8n workflow read and write your store through the Magento API, the programming interface your store already exposes, using the access token you would otherwise use by hand. It groups 15 operations into 4 resources: Customer, Invoice, Order and Product. A single workflow can fetch an order, raise an invoice against it, mark it shipped, and keep the product catalog in step with another system.
Start with the orders, because that is where the typing hurts most. A Schedule Trigger fires every morning, order.getAll pulls the recent orders, and invoice.create raises an invoice for each Order ID it finds. When the warehouse confirms, order.ship closes the loop on the same order. The finance sheet in Google Sheets gets a row per run, and nobody retypes an order number.
Second pattern: a customer list that follows the buyer. customer.getAll reads the store's accounts with Return All switched on, and each record can be pushed into HubSpot or Pipedrive. It works in the other direction too: customer.create writes a buyer into Magento from a form, and customer.update fixes a misspelled last name without anyone opening the admin.
Third pattern: one catalog, two storefronts. product.getAll lists what the store sells, product.update pushes a new Price or Status onto a SKU, and product.create adds the reference that so far only exists in a spreadsheet. Teams running Magento next to WooCommerce lean on this to keep one source of truth instead of two.
The node speaks to the Customer, Invoice, Order and Product resources listed below. For any other Magento endpoint, the HTTP Request node calls the API directly and reuses the very same credential through predefined authentication, so nothing needs re-authorizing. One thing to plan for before you build: this node ships without a trigger, so a Schedule Trigger (a clock that fires at a fixed interval) or a Webhook node (a URL another service calls when something happens on its side) starts the workflow and feeds Magento its input.
Still weighing platforms? The n8n review digs into hosting and the cost model, and the n8n training walks through building workflows like these from an empty canvas.
How do you connect Magento 2 to n8n?
- 01
Allow standalone bearer tokens
In the Magento admin, open
Stores > Configuration > Services > OAuth > Consumer Settingsand set Allow OAuth Access Tokens to be used as standalone Bearer tokens to Yes. The same switch flips from the command line withbin/magento config:set oauth/consumer/enable_integration_as_bearer 1. The n8n credential needs this step until it moves to OAuth. - 02
Create the integration and copy the token
Still in the admin, head to
System > Extensions > Integrationsand add a new integration. On its API tab, pick the Magento resources n8n is allowed to reach and nothing beyond them. Back on the Integrations list, hit Activate, then Allow: Magento displays the access token, and that screen is your one chance to copy it. - 03
Fill in the credential inside n8n
In n8n, open the Credentials menu and create a Magento 2 credential. It asks for two things: a Host, the address of your store, and the Access Token you just copied. A credential is stored once and then picked from a dropdown by every node that needs it, so the second workflow never asks you to paste that token again.
What the Magento 2 node does, operation by operation
The Magento 2 node exposes 15 operations across 4 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
| Resource | Create | Get | Get Many | Update | Delete | Cancel | Ship |
|---|---|---|---|---|---|---|---|
| Customer | ✓ | ✓ | ✓ | ✓ | ✓ | ||
| Invoice | ✓ | ||||||
| Order | ✓ | ✓ | ✓ | ✓ | |||
| Product | ✓ | ✓ | ✓ | ✓ | ✓ |
Customer
5 operationsCreate a customer
customer.createWhat you see in n8n
Notes & use cases
Registers a new customer account in the store and hands the created record to the next node.
Key parameters
- Email: the address the account is keyed on, in the
name@email.comshape, often{{ $json.field }}from the form or CRM node before it. - First Name and Last Name: both required, so a single full-name input has to be split upstream.
- Additional Fields: 18 optional entries, among them Group Name or ID, Is Subscribed and Addresses.
Delete a customer
customer.deleteWhat you see in n8n
Notes & use cases
Removes one customer account from Magento, one record per execution.
Key parameters
- Customer ID: the store's internal identifier for the account, not the email address; a name typed here will not resolve.
Get a customer
customer.getWhat you see in n8n
Notes & use cases
Reads a single customer account and passes the record along for the rest of the workflow to use.
Key parameters
- Customer ID: the account to read; if your workflow only knows an email address, resolve it first with the get-many operation.
Get many customers
customer.getAllWhat you see in n8n
Notes & use cases
Lists customer accounts in bulk, one output item per account.
Key parameters
- Return All: on, n8n walks every page of the customer list; off, Limit caps how many accounts come back in a run.
- Filter:
nonetakes everyone,manualbuilds conditions in the interface,jsonreads them from Filters (JSON). - Must Match:
allFiltersdemands every condition,anyFilteris satisfied by one.
Update a customer
customer.updateWhat you see in n8n
Notes & use cases
Modifies an existing customer account with the values you hand it.
Key parameters
- Customer ID: names the account to modify, and comes from the same place as it does for the read operation.
- Email, First Name, Last Name: the identity fields offered directly on the operation, alongside Website Name or ID.
- Update Fields: 18 more entries, including Date of Birth, Gender and Default Shipping Address ID.
Invoice
1 operationCreate an invoice
invoice.createWhat you see in n8n
Notes & use cases
Turns an existing order into an invoice inside Magento.
Key parameters
- Order ID: identifies the order being invoiced, usually carried over from an earlier order step as
{{ $json.field }}. It is the only field the operation asks for, which keeps the node easy to drop at the end of an existing branch.
Order
4 operationsCancel an order
order.cancelWhat you see in n8n
Notes & use cases
Cancels the order you point it at, straight from a workflow.
Key parameters
- Order ID: the single required field, so the cancellation applies to exactly one order per item that reaches the node.
Get an order
order.getWhat you see in n8n
Notes & use cases
Fetches a single order with its details so the next nodes have something to work from.
Key parameters
- Order ID: required, and this is the Magento identifier rather than any reference your own tools print on a document.
Get many orders
order.getAllWhat you see in n8n
Notes & use cases
Returns orders as a list, ready to loop over item by item.
Key parameters
- Return All: left off, Limit decides how many orders n8n brings back per execution.
- Filters: each condition pairs a Field, a Condition Type such as
gteqorlike, and a Value. - Sort: an entry under Options where the sorting rule is added.
Ship an order
order.shipWhat you see in n8n
Notes & use cases
Marks the order as shipped on the Magento side.
Key parameters
- Order ID: the order to ship; feed it one item per order if a run handles several at once.
Product
5 operationsCreate a product
product.createWhat you see in n8n
Notes & use cases
Adds a new product to the catalog.
Key parameters
- SKU: the stock-keeping unit, the product's unique reference in the store.
- Name: the second required field, the product name itself.
- Attribute Set Name or ID and Price: offered next to the required pair, the attribute set picked from the list or given as an ID through an expression.
- Additional Fields: 7 entries, among them Status (
1Enabled,2Disabled), Visibility and Weight (LBS).
Delete a product
product.deleteWhat you see in n8n
Notes & use cases
Deletes a product from the catalog, addressed by its reference rather than an internal number.
Key parameters
- SKU: the stock-keeping unit of the product to remove, which makes this operation easy to drive from a plain list of references.
Get a product
product.getWhat you see in n8n
Notes & use cases
Pulls one product record out of the catalog.
Key parameters
- SKU: the reference to look up, typically read from the item flowing in, as in
{{ $json.field }}. Unlike the customer operations, this one runs on the SKU you already use, not an ID you would have to look up first, so a reference list is enough to drive it.
Get many products
product.getAllWhat you see in n8n
Notes & use cases
Walks the catalog and returns products as separate items.
Key parameters
- Return All: switched on, n8n keeps requesting pages until the catalog is exhausted, which is what a full export needs.
- Filter on
manual: Filters holds the conditions and Must Match says whether all of them or just one has to be true. - Value: with
inornin, it accepts a comma-separated list.
Update a product
product.updateWhat you see in n8n
Notes & use cases
Changes a product already in the catalog, found by its reference.
Key parameters
- SKU: the only required field here, which means the reference has to be right before anything else matters.
- Update Fields: 7 entries covering Price, Name, Status, Visibility, Type Name or ID, Weight (LBS) and Attribute Set Name or ID.
Need help automating Magento 2 with n8n?
A person reads every message.
