- Home
- Resources
- Integrations
- Magento 2.X
Magento 2.X Zapier integrationAutomate Magento 2.X with Zapier.
The Magento 2.X Zapier integration gives you 6 triggers, 2 actions and 0 searches. Every trigger checks your store on a timer and the app is premium, so here is what a run costs, how to connect the store and which Zaps break first.
Premium app Zapier reserves this app to its paid plans.
Verified Trustpilot reviews · AI, automation & growth agency
What the Magento 2.X Zapier integration actually does
The Magento 2.X Zapier integration lets Zapier watch your store and react to it. It spots six kinds of new records (products, customers, orders, invoices, credit memos, shipments) and writes two things back: a new customer account, or a comment on an existing order. Everything else happens in the other tools you plug in.
Three results you can get out of it. An order log that lives outside the store: New Order hands each fresh order, line items included, to a spreadsheet so the numbers sit where your team already reads them. A refund heads-up: New Sales Order Credit Memo posts a note to your team chat whenever Zapier finds a credit memo, so nobody discovers a refund by surprise. An order history that tells the full story: Create Sales Order Comment writes on the order what happened somewhere else, right where support looks first.
Now the limits. There is no search step for Magento 2.X, so a Zap cannot look up an order or a customer that already exists. No action edits an order, changes a status or creates a product: the two actions only add a customer or a comment. And no trigger is instant, so every event waits for Zapier's next check of the store.
If those gaps weigh on your plans, see our n8n vs Zapier and Make vs Zapier comparisons.
Zapier words in one minute
Seven words come back on every line of this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts the Zap, like a new order in your store. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts these, nothing else.
- Polling vs instant
- A polling trigger is checked on a timer for items Zapier has not seen yet. An instant one is reported by the app the moment it happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already in an app, so the next steps can use what it found. Magento 2.X has none.
What a Magento 2.X Zap really costs
Short version: the trigger is free, each action that works counts once, and this app needs a paid plan.
- Free plan100 tasks a month, unlimited Zaps, checks every 15 minutes, no premium app
- This appPremium: paid plan or free trial
- BilledEach successful action; the trigger and the checks cost nothing
Watching the store costs nothing, however often Zapier looks. A task is counted only when an action goes through, and a failed action is not billed. A Zap with three actions uses three times what a one-action Zap uses. Magento 2.X is a premium app: Zapier keeps it for paid plans and the free trial. The free plan also stops at two steps, so adding a filter, a search or a second action makes a multi-step Zap, which needs a paid plan anyway.
Connect your Magento 2.X store to Zapier
- 01
Open your apps
In your Zapier account, go to the Apps page and click + Add connection. A connection is your store account linked once, then reused by every step that touches Magento 2.X.
- 02
Pick Magento 2.X
Type the app name in the dialog, select Magento 2.X, then click Add connection. A new tab opens on the store side. You need an existing account on that store before going further.
- 03
Sign in and allow access
Sign in to Magento 2.X in that tab and grant Zapier access. If the Zap should touch records you do not own, your account needs read or write rights on them first.
Your first Magento 2.X Zap, step by step
GoalEvery new order that passes your condition lands as a row in your spreadsheet, line items included, without anyone copying it by hand.
- 01
Create the Zap
Start a new Zap and pick Magento 2.X as the app that starts it, with New Order as the event. Choose the connection you set up above.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent orders of your store, so you map fields on a real order rather than an empty template.
- 03
Add a filter
From the + in the editor, add Filter and fill its three boxes: the field to look at, the rule, and the value to compare with. A text rule only works on text.
- 04
Add and test the row
Add your spreadsheet tool and its new row action, map the order fields into the matching columns, then run the step once and check the row before going further.
- 05
Publish
Click Publish to switch the Zap on. From then on, Zapier checks the store at your plan's interval and adds each new order it finds.
Magento 2.X triggers
6 events start a Zap when something happens in Magento 2.X. Zapier checks for them at the interval your plan allows.
New Product
Polling triggerIn Zapier“Triggers when a new product is created.”
Starts the Zap when a product appears in your catalog, and hands its details to the next steps. Useful to announce or log additions without opening the admin.
New Customer
Polling triggerIn Zapier“Triggers when a new customer is created.”
Picks up each customer account freshly created in the store and passes its details along, ready to be copied into whatever tool keeps your contacts.
New Order
Polling triggerIn Zapier“Triggers when a new order is created (with line item support).”
Fires on every new order and carries the line items with it, so a later step can see what was bought, not only the total.
New Sales Order Credit Memo
Polling triggerIn Zapier“Triggers when a new sales order creditmemo is created.”
Reacts when a credit memo is issued on an order, which in Magento 2.X is how a refund shows up. The memo details travel to the next steps.
New Sales Order Invoice
Polling triggerIn Zapier“Triggers when a new sales order invoice is created (with line item support).”
Each invoice your store creates for an order sets this one off, line items included, so the next step can rebuild the billed detail elsewhere.
New Sales Order Shipment
Polling triggerIn Zapier“Triggers when a new sales order is created (with line item support).”
Every shipment created in the store is caught here, with its line items, so customers or colleagues can hear about it from the tool they actually use.
Magento 2.X actions
Magento 2.X gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Customer
ActionIn Zapier“Create a new customer”
Opens a customer account in your store from data that came in elsewhere. Email, first name, last name and password are all required.
Create Sales Order Comment
ActionIn Zapier“Create a new sales order comment”
Adds a comment to an existing order, so its history in the admin shows what happened in other tools. It needs the Order ID to know where to write.
When a Magento 2.X Zap breaks
Most failures here are not bugs. They come from how polling works and from the two actions writing back into the store.
Zapier remembers what it already saw on each trigger, so the same order never starts the Zap twice. The cases below are what usually goes wrong instead. Zapier links one help article to this app, How to get started with Magento 2.X on Zapier, and you can also see our Zapier troubleshooting page.
Old records never show up
A Zap only reacts to what happens after you switch it on. Orders, customers or invoices created earlier stay where they are; moving that backlog is a separate job.The customer loop
A Zap that starts on New Customer and runs Create Customer on the same store sets itself off again and again, and burns through your tasks fast.A bulk import gets held back
After a mass import or a migration, a trigger can suddenly return a huge batch of records. Zapier's flood protection may hold that batch back.Shipments without tracking codes
By default a shipment triggers as soon as Zapier finds it. Set Delay to capture tracking data to True so the store has about 10 minutes to attach tracking.
Need help automating Magento 2.X with Zapier?
A person reads every message.



