Resources · Zapier integration

MRPeasy Zapier integrationAutomate MRPeasy with Zapier.

The MRPeasy Zapier integration gives you 2 triggers, 2 actions and 1 search. A customer order changing status can start a Zap at once, other apps can create or update orders in MRPeasy, and a search finds an existing order. Here is what it does, costs and breaks.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MRPeasy Zapier integration actually does

MRPeasy runs material and production planning online, for small manufacturing companies of 10 to 200 employees. Connected to Zapier, it shares customer orders with the rest of your tools: orders taken elsewhere land in MRPeasy, and what happens to an order in MRPeasy can be passed on to another app.

Three results you can build. Status news where your team reads it: Customer Order Status Changed starts a Zap the moment an order moves, and a message can go to your team chat. Orders entered once: Create Customer Order opens the order in MRPeasy from another app, with a customer name, a SKU and a quantity. Orders kept in step: Search Customer Order finds the order, then Update Customer Order changes it by its number.

The most useful thing on this page: of the two triggers, Customer Order Status Changed is the only instant one. It reacts at once even on the free plan, while Get Sites waits for the interval of your plan.

What Zapier does not do here. Nothing deletes an order, and outside customer orders the only thing within reach is the list of sites. Get Sites is described only as fetching a list of sites, so check at the test what it returns. To weigh Zapier against other tools, see our n8n vs Zapier comparison or our Zapier review.

Vocabulary

Zapier words in one minute

Eight words the Zapier editor uses everywhere, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts a Zap, like a customer order changing status in MRPeasy. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like creating an order.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer; an instant one is reported by the app the moment it happens. MRPeasy has one of each.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What MRPeasy on Zapier really costs

Zapier bills completed actions, not events. The trigger never costs a task, and checking for new items is free however often it happens.

  • Free plan100 tasks a month, unlimited two-step Zaps
  • MRPeasy on freeYes, not reserved for paid plans
  • Instant triggerCustomer Order Status Changed, any plan
  • Search, filter or second actionPaid plan required

Each action that succeeds counts once; one that fails is not counted. MRPeasy is not reserved for paid plans, so it runs on the free plan: 100 tasks a month and unlimited Zaps of two steps each. A filter, Search Customer Order or a second action makes the Zap multi-step, which needs a paid plan. The grid below only concerns Get Sites, the polling trigger; Customer Order Status Changed is instant and ignores it.

Connect

Connect your MRPeasy account

  1. 01

    Open Apps and add a connection

    Go to the Apps page of your Zapier account and click + Add connection. You need an MRPeasy account, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick MRPeasy

    Type MRPeasy in the search box of the dialog, select it and click Add connection. A new tab opens on the MRPeasy sign-in screen, where the next step happens.

  3. 03

    Sign in and grant access

    Log in to MRPeasy in that tab, then grant Zapier access to the account. Every MRPeasy step in your Zaps reuses this connection afterwards, so you only do it once.

First Zap

Your first Zap: tell the team when an order reaches a given status

GoalWhen a customer order changes status in MRPeasy and the new status is the one you picked, post a message in your team chat.

  1. 01

    Set the trigger

    Create a Zap, choose MRPeasy as the trigger app and Customer Order Status Changed as the event, then pick the MRPeasy connection made earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map fields on a real order rather than an empty one.

  3. 03

    Add the filter

    Click the plus icon, choose Filter and set the field to look at, the rule and the value. A filter makes the Zap multi-step, so this step needs a paid plan.

  4. 04

    Add the chat action

    Add your team chat app and its send-message action, connect the account, then put the order details from the trigger into the message. Test it and read what was posted.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only status changes made after this point reach the chat; earlier ones are not replayed.

Triggers

MRPeasy triggers

2 events start a Zap when something happens in MRPeasy, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Customer Order Status Changed

Instant trigger

In Zapier“Triggers when the status of a customer order changes.”

Starts a Zap whenever a customer order in MRPeasy moves from one status to another, and hands that order to the next step so the change can be announced or recorded elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team chat, a shared sheet or a customer message should follow the life of each order without anyone checking MRPeasy.
Watch out
every status change fires it, so add a filter if only one status matters, and remember the filter needs a paid plan.
2

Get Sites

Polling trigger

In Zapier“Fetches a list of sites.”

Its official description says it fetches a list of sites from MRPeasy. Zapier passes what it finds to the following steps.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
only once a test has shown you what it returns and that this suits your Zap.
Watch out
the description says nothing about which event counts as new, so run the trigger test and read what comes back before building on it.
Actions

MRPeasy actions

MRPeasy gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Customer Order

Action

In Zapier“Create a customer order”

Opens a new customer order in MRPeasy from data that arrived in another app, so orders taken outside MRPeasy do not have to be typed in again.

When to use it
orders come in through your online shop or a form and should exist in MRPeasy too.
Watch out
Customer name, SKU and Quantity are required. If you do not import customers into MRPeasy, the field help suggests a generic name such as E-shop buyer.
2

Update Customer Order

Action

In Zapier“Update a customer order”

Changes an existing customer order in MRPeasy, picked by its customer order number, the unique code that identifies it.

When to use it
something about the order changed in another tool and MRPeasy has to reflect it.
Watch out
the order number is required, so if the earlier steps do not carry it, put Search Customer Order in front to find it.
Searches

MRPeasy search

1 search step looks for data that already exists in MRPeasy, so a later step can use it.

A search step finds an existing record and passes it on. In the editor it sits at the bottom of the Action event list, under the SEARCH heading, and it makes the Zap multi-step. Three settings decide what happens when the result is not one clean match.

1

Search Customer Order

Search

In Zapier“Find a customer order”

Finds a customer order that already exists in MRPeasy and hands it to the steps that follow, so a later step can use its details.

When to use it
just before Update Customer Order, when the trigger of your Zap does not carry the order number.
Watch out
whether it wants an exact value or something close is decided by MRPeasy, so test it with a real order first.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into a find-or-create. MRPeasy has no such variant, so you will not see it on this search.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When the MRPeasy Zap breaks

Zapier lists no limit and no error specific to MRPeasy. What can go wrong comes from how every Zap works.

Four cases to know before you publish. If a Zap behaves oddly, our Zapier troubleshooting guide is the next stop.

  • Past orders never show up

    A Zap only reacts to what happens after it is switched on. Orders and status changes from before are not picked up; moving that history is a separate job.

  • A Zap that keeps setting 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 fast.

  • A bulk import is held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back.

  • The same site twice? No

    On a polling trigger such as Get Sites, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help

Need help automating MRPeasy with Zapier?

A person reads every message.

FAQ

MRPeasy Zapier integration: questions people ask

01Is the MRPeasy Zapier integration free?
Yes, for two-step Zaps. MRPeasy is not reserved for paid plans, so it works on the free Zapier plan, which gives 100 tasks a month and an unlimited number of Zaps, each made of one trigger and one action. Posting a chat message on every order status change fits in that. Keeping only one status with a filter, or chaining Search Customer Order and Update Customer Order, makes the Zap multi-step, and that needs a paid plan.
02How many tasks does an MRPeasy Zap use?
One task per successful action, and nothing for the trigger. A status change reaching Zapier costs nothing, and neither does Zapier checking Get Sites, however often. A Zap that posts one message per status change uses one task each time it posts. In a Zap with two actions, each successful one counts on its own. An action that fails is not counted. On the free plan, compare your number of status changes with the 100 tasks of the month.
03Does MRPeasy trigger Zaps in real time?
One of its triggers does. Customer Order Status Changed is instant: MRPeasy tells Zapier the moment it happens, so the Zap starts right away on any plan, free included, and the editor shows a lightning bolt on such a Zap. Get Sites is a polling trigger: Zapier checks at regular intervals, every 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team and Enterprise. Paid plans can also change that interval.
04What do you need to connect MRPeasy to Zapier?
An MRPeasy account, plus read or write access on anything you do not own yourself and want the Zap to touch. You connect it once from the Apps page of your Zapier account: click + Add connection, pick MRPeasy, sign in in the tab that opens and grant Zapier access. Every MRPeasy step in your Zaps then reuses that connection. Test each step once afterwards to see what it can really read.
05What does Create Customer Order need from the other app?
Three required values: a customer name, a SKU and a quantity, every time. The SKU is the part number in MRPeasy, so the code your source app sends has to match it. When customers are not imported into MRPeasy, the field help suggests a generic name such as E-shop buyer. Run the action test with a real order from your source app and read what came back. An action that fails is not counted against your plan.
06What if the MRPeasy operation you need is not there?
Then Zapier does not offer it today. The MRPeasy page on Zapier shows the current list of triggers, actions and searches, and that is where to look before planning a Zap. Right now the integration revolves around customer orders: create, update, find, and hear when their status changes, plus the list of sites. If what you need sits elsewhere in MRPeasy, this integration does not cover it on Zapier. Build around what exists rather than around a step that is not offered.
07Zapier, Make or n8n for MRPeasy?
Choose on criteria, not on a ranking. Coverage comes first: on Zapier, MRPeasy offers two triggers, two actions and one search, so check what the other tool offers for MRPeasy before comparing anything else. Then speed: the status trigger is instant on Zapier, even on the free plan. Then cost shape: syncing an order by number with a search plus an update is a multi-step Zap, so it needs a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations