MarketProvider Zapier integrationAutomate MarketProvider with Zapier.
MarketProvider Zapier integration: 2 triggers, 1 action, 0 searches. MarketProvider can start a Zap when a product is added to your catalog or changed in it, and Zapier can fetch a product from the PIM on demand, so your product data reaches the tools that need it.
Verified Trustpilot reviews · AI, automation & growth agency
What the MarketProvider Zapier integration does for you
The MarketProvider Zapier integration lets your product catalog speak to your other tools. MarketProvider is a PIM, the one place that holds your product information, where it gets cleaned up, filled out and sent on to each of your channels. Zapier watches it for new and changed products, and can also fetch one product when another tool asks.
A product list your team can read. New Products starts the Zap whenever a product appears in MarketProvider, and the next step writes it as a row in a shared spreadsheet. Your colleagues follow the catalog without opening the PIM.
Changes that reach the right person. Updated Products fires when a product is modified. Pair it with a filter and a team chat message, and only the changes you care about make noise.
A product on demand. Get Product pulls one product from the PIM inside a Zap that started somewhere else, so a later step can use its data. Run the test first: the editor shows which identifier it expects.
What Zapier does not do here. Both triggers are polling ones: there is no instant trigger, so nothing fires faster than your plan's interval. There is no action that creates or edits a product in MarketProvider, and no search step. Data flows out of the PIM, not into it. To weigh Zapier against other tools, see our n8n vs Zapier comparison.
Zapier words, in plain English
Eight terms come back on this page. Here they are once, in ordinary words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, here a new or updated product in MarketProvider. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or fetches something for you.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
- Instant trigger
- A trigger the app reports itself the moment the event happens. MarketProvider has none on Zapier.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it 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 MarketProvider Zap really costs
Zapier bills in tasks, and MarketProvider is not a premium app: it works from the free plan.
- Free plan100 tasks a month, unlimited Zaps, two steps each
- Premium appNo, MarketProvider works on the free plan
- Trigger type2 polling triggers, no instant one
The trigger never costs a task, and Zapier checking MarketProvider for new or updated products costs nothing either, however often it looks. Each action that succeeds counts as one task, Get Product included; one that fails is not counted. A few apps and actions take more than one task. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps each: a filter or a second action needs a paid plan. Both MarketProvider triggers follow the grid below.
Connect MarketProvider to Zapier in 3 steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. A connection is your MarketProvider account linked once, then reused by every step that uses it.
- 02
Pick MarketProvider
Type MarketProvider in the search box of the dialog, select it, then click Add connection. A new tab then opens, so you can sign in to your own MarketProvider account.
- 03
Sign in and grant access
Sign in to MarketProvider in that tab and grant Zapier access to the account. You need a MarketProvider account, plus read or write access to anything you do not own yourself and want the Zap to touch.
Your first Zap: filtered product changes in your team chat
GoalEach product updated in MarketProvider that passes your filter posts a message in your team chat, so the people who sell it hear about the change.
- 01
Build: pick the trigger
Start a new Zap, choose MarketProvider, then Updated Products. The trigger always comes first: a Zap is one trigger followed by its actions.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you build the next steps on real products rather than on empty boxes.
- 03
Add the filter
From the plus icon, add a Filter and set its three boxes: the field to look at, the rule, and the value. A text rule only works on text, a number rule only on numbers.
- 04
Add the chat message
Pick your team chat and its send-message action, then write the message with the product fields the test brought back. Test it and read the message it posted.
- 05
Publish
When each step returns what you expect, click Publish. The filter makes this a multi-step Zap, so it needs a paid plan, which also shortens the polling interval.
The 2 MarketProvider triggers
2 events start a Zap when something happens in MarketProvider. Zapier checks for them at the interval your plan allows.
New Products
Polling triggerIn Zapier“Triggers when there's a new products.”
Starts the Zap when a product is added to your MarketProvider catalog, so the newcomer can be copied, announced or sent on to another channel.
Updated Products
Polling triggerIn Zapier“Triggers when there's a updated products.”
Picks up products that change in MarketProvider, so the people and tools downstream of the PIM are not left with an outdated version.
The MarketProvider action
MarketProvider gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Get Product
ActionIn Zapier“Get product from PIM”
Fetches one product from the MarketProvider PIM in the middle of a Zap, so the steps after it can use that product's data.
When a MarketProvider Zap breaks
Zapier attaches no help article to MarketProvider, and no limit specific to the app is documented. What breaks is what breaks on any Zap.
Four cases are worth knowing before you publish. For deeper digging, see our Zapier troubleshooting guide.
The existing catalog stays out
A Zap only reacts to what happens after it is switched on. Products that existed before never start it; moving that backlog is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your task count. Keep the trigger and the write in different places.A bulk import held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those products back instead of running them all.No double runs
Both triggers are polling ones, and Zapier keeps track of the items it has already seen, so the same product does not start the Zap twice.
Need help automating MarketProvider with Zapier?
A person reads every message.
