MRPeasy

Zapier

Zapier is a powerful workflow automation system that allows integrating MRPeasy with numerous applications that are available on this platform.

MRPeasy integration with Zapier provides flexible and powerful access to Customer Orders in MRPeasy from the programs of your choice via Zapier.

By making a Zap in Zapier, it is possible to:

1. Create Customer Orders in MRPeasy.
2. Update Customer Orders in MRPeasy.
3. Search for Customer Orders in MRPeasy.
4. Catch the event when a Customer Order status changes in MRPeasy.

How to connect MRPeasy with another application using Zapier?

Creating a Zap to send a Customer Order to MRPeasy

For sending a Customer Order from an app to MRPeasy via Zapier, please create a Zap as follows:

1. Configure the trigger:
   1. Find the source app.
   2. Choose the trigger event.
   3. Select your account (if needed, sign in).
   4. Set up trigger details.
   5. Test the trigger.
2. Configure the action:
   1. Find the MRPeasy app.
   2. Choose the action "Create Customer Order".
   3. Select your account (if needed, sign in).
   4. Map the source information from the source app to the MRPeasy Customer Order data (find the data structure below).
   5. Test the action.
3. Enable the zap.

Data structure for mapping MRPeasy Customer Order data

The Customer Order data in MRPeasy consists of three structures, which all need to be mapped to the data from your source app:

1. Customer Order data.
2. Products data.
3. Shipping address data.

1. Data structure of a Customer Order in MRPeasy

2. Data structure of ordered products in MRPeasy

Important notes:

• If the product structure contains invalid information (for example the SKU does not exist in MRPeasy), only this order line is skipped.
• The Customer Order can be successfully created if it contains at least one product line.

3. Data structure of the shipping address in MRPeasy

Important notes:

• The address is not mandatory for the Customer Order. However, if it is provided and valid, it will be saved for the customer and used for this Customer Order.

Testing the Zap

After completion of the mapping, you have to test Customer Order input to be sure that the mapping is correct and the resulting Customer Order in MRPeasy contains the information that was passed from the Zap.

The response contains the following fields:

• Also, if a Customer Order is created successfully, the response contains full CO information in a structure, as defined here.

Finding a Customer Order in MRPeasy

For finding Customer Orders in MRPeasy please use the Search Customer Order action, when configuring a Zap.

The following search parameters are available:

Important notes:

• The Search Customer Order action, if successful, returns a list of CO information in a structure, as defined here.

Getting notified when a Customer Order status changes in MRPeasy

MRPeasy can notify Zapier when a Customer Order status changes in MRPeasy.

When configuring MRPeasy as a trigger, please select the event Customer Order status changed, when configuring a Zap.

Several options are available:

Important notes:

• When trigger generates an event, it returns full CO information in a structure, as defined here.