Magalu Zapier integrationAutomate Magalu with Zapier.
The Magalu Zapier integration gives you 4 triggers, 2 actions and 0 searches. Zapier can spot new orders, stock changes, price changes and new questions on your Magalu account, and it can push a new price or a new stock count for a SKU.
Verified Trustpilot reviews · AI, automation & growth agency
What the Magalu Zapier integration does for you
The integration links Magalu, a marketplace whose catalogue runs from furniture to electronics and appliances, to Zapier, the service that chains your apps so data moves without copy and paste. On Zapier, Magalu covers four signals from your account (orders, stock, prices, questions) and two ways to change a SKU: its price or its inventory.
Three results come up most. The first is an order log. New Order (Prod) picks up each new order, and a spreadsheet row records it, so everyone who handles orders works from one list.
The second is a price sheet that drives the marketplace. Someone edits a price in a spreadsheet, and Update SKU Price sends it to Magalu for that SKU. The same goes for stock with Update SKU Inventory, when your count lives somewhere else.
The third is faster answers. New Question passes each new question to your team chat, so nobody has to keep the marketplace open to notice it.
Now what Zapier does not do here. There is no search step, so a Zap cannot look up a product or an order before acting. The two actions only touch prices and stock: nothing answers a question, creates a product or changes an order from Zapier. All four triggers check on a schedule, none is instant. Comparing platforms first? See our n8n vs Zapier and Make vs Zapier comparisons.
Zapier words, in one minute
Seven terms are enough to read the rest of this page. Each one is used exactly as defined here.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that opens the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- The step that works once the Zap has started: it writes, sends or moves something in an app on your behalf.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant trigger is reported by the app itself the moment it happens.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a Magalu Zap really costs
Zapier bills the work done, not the watching. Your four Magalu triggers can check as often as your plan allows for free.
- TriggerNever billed
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
- Magalu triggers4, all polling
The trigger never costs a task, and Zapier looking for new orders or changes is free too. Each action that succeeds counts once; one that fails is not billed. Magalu is not a premium app, so it runs on the free plan: 100 tasks a month, but only two-step Zaps. A filter or a second action makes the Zap multi-step, which needs a paid plan. All four triggers poll, so the grid below decides how soon a new order or a change reaches your Zap.
Connect Magalu to Zapier in three steps
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your Magalu account linked once, then reused by every step that calls Magalu.
- 02
Pick Magalu
Type Magalu in the search box of the dialog, select it, then click Add connection. You need a Magalu account already in place before this step, since Zapier links to it.
- 03
Sign in and allow access
A new tab opens. Sign in to Magalu there and grant Zapier access to the account. Back in Zapier, the connection shows in your list, ready for triggers and actions.
Your first Zap: log each new order and tell the team
GoalEach new Magalu order adds a row to your spreadsheet, then a message tells your team that an order is waiting.
- 01
Start from Magalu
Create a Zap, choose Magalu and pick New Order (Prod) as the trigger. Select your Magalu connection when Zapier asks for it.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent orders from the connected account, so you map the next steps on a real one.
- 03
Write the row
Add your spreadsheet with its new row action. Map each column to what the trigger brought back, so every order sits in one place your team can sort.
- 04
Send the message
Add your team chat with its send message action, and write a short line using the order data, so whoever handles orders knows one is waiting.
- 05
Test, then publish
Test each step and read what came back before moving on. Then click Publish to switch the Zap on. With two actions it has three steps, so it needs a paid plan.
The Magalu triggers
4 events start a Zap when something happens in Magalu. Zapier checks for them at the interval your plan allows.
New Order (Prod)
Polling triggerIn Zapier“Triggers when a new order is created in prod.”
Each new order created in prod, as the name says, opens the Zap. It is the obvious starting point for anything that follows a sale, from a shared list to a note for the team.
Change Inventory
Polling triggerIn Zapier“Trigger when a change in stock occurs.”
When stock moves on one of your products, this trigger spots it at its next check and starts the Zap. It turns quiet stock changes into something people can see.
Change Price
Polling triggerIn Zapier“Trigger when a change in prices occurs.”
This one reacts to a price change on your products. Every new price becomes an event your Zap can record or pass on.
New Question
Polling triggerIn Zapier“Trigger when a new question is created.”
Fires on each new question created on Magalu, so a question about a product does not sit unseen while someone waits for an answer.
The Magalu actions
Magalu 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
Update SKU Price
ActionIn Zapier“Update the inventory of products”
Sets a new price on one SKU, so a decision taken elsewhere reaches the marketplace without a manual edit.
Update SKU Inventory
ActionIn Zapier“Update the inventory of products”
Writes a new stock quantity for one SKU, so the count shown on Magalu matches the one you trust.
When a Magalu Zap breaks
Zapier attaches no help article to Magalu, so the failures worth knowing come from how Zaps behave in general, and from the way the triggers and actions mirror each other.
Four situations explain most surprises. None is unique to Magalu, but each one hits a marketplace Zap in its own way. See our Zapier troubleshooting page.
Past orders never show up
A Zap only reacts to what happens after it is switched on. Orders, questions and changes from before are not picked up; moving that backlog is a separate job.Price and stock loops
Update SKU Price after Change Price, or Update SKU Inventory after Change Inventory, writes where the trigger watches. Each write starts the Zap again and drains tasks.A bulk update is held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.One order, one run
On a polling trigger, Zapier remembers what it has already seen, so the same order or change does not start the Zap a second time.
Need help automating Magalu with Zapier?
A person reads every message.



