Resources · Make integration

PlentyMarkets Make integrationAutomate PlentyMarkets with Make.

Can Make handle your PlentyMarkets orders, items and support tickets without code? The PlentyMarkets Make integration gives you 21 modules: 16 actions and 5 searches. This page shows online sellers how to link the account, build a first scenario and pick the right module.

Try the PlentyMarkets integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the PlentyMarkets Make integration let you automate?

The PlentyMarkets Make integration links your PlentyMarkets shop back end to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick that creates, reads, updates or searches something. Your orders, items, contacts, tickets and tag relationships become data other apps can use, and the reverse is true too.

Support tickets that open themselves. A customer writes through a form in another tool, Search Contacts finds the matching buyer in PlentyMarkets, and Create a Ticket logs the request with the right person attached. Nobody retypes an email address.

Orders fed from outside the shop. When a sale closes somewhere else, such as a spreadsheet or a sales app, Create a Contact and Create an Order put it into PlentyMarkets so stock and fulfilment stay in one place.

Catalog lookups for other teams. Search Items and Get an Item pull product data out of PlentyMarkets and hand it to a sheet, a chat message or an Airtable Make integration base.

What Make does not do here: PlentyMarkets has no trigger module, so nothing starts on its own when an order lands. A scenario begins on a schedule you set in Make or on another app's event. The official Make documentation for this app also warns that it was generated with AI and may contain mistakes, so check anything critical against PlentyMarkets itself. For the wider picture, read our Make review and the n8n vs Make comparison, and look at Make pricing before you go past the Free plan.

Connect

How do you connect PlentyMarkets to Make?

  1. 01

    Create a back end user in PlentyMarkets

    In PlentyMarkets, open Setup > Settings > API > Data and copy the REST-API HTTP Endpoint. Then go to Setup > Settings > User > Accounts, click New, fill in the user details, choose Back end as user access and click Save.

  2. 02

    Add a PlentyMarkets module in Make

    In your Make scenario, add any PlentyMarkets module and click Create a connection. A connection is your PlentyMarkets account linked to Make once, then reused by every PlentyMarkets module you add later. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Enter the endpoint you copied, plus the username and password of the user you just created, or follow the instructions Make shows on screen. Once the connection is saved, Make can list the PlentyMarkets data it is allowed to read.

First scenario

Build your first PlentyMarkets scenario

GoalWhen a customer sends a request through another app, Make finds the buyer in PlentyMarkets and opens a ticket for them.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the trigger of the app where customer requests arrive, such as your form tool, and connect it.

  2. 02

    Add Search Contacts

    Click the + on the right of the first module, search for PlentyMarkets and choose Search Contacts. Click Create a connection and link your account as shown above.

  3. 03

    Map the customer details

    Fill the search criteria with data from the form, for example the contact details the customer typed. Each item that flows between modules is called a bundle, and here the bundle is one contact.

  4. 04

    Open the ticket

    Add Create a Ticket after the search. Map the contact it found and the message from the form, so the request lands in PlentyMarkets with the buyer already attached.

  5. 05

    Test with Run once

    Send a test request through your form, then click Run once. Open the bubble on each module to read the bundles it received and check that the ticket appears in PlentyMarkets.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default) and switch the scenario on. Every module run counts as one operation on your Make plan.

Modules

What can each PlentyMarkets module do in Make?

PlentyMarkets gives you 21 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PlentyMarkets1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a new customer record to PlentyMarkets, so a buyer met outside your shop exists in the back end before any order or ticket points to them.

When to use it
a lead from a sales app or a spreadsheet becomes a real customer and needs a record.
Watch out
run Search Contacts first, or the same person can end up recorded twice.
PlentyMarkets2

Create an Item

Action

In Make“Creates a new item.”

Puts a new product into your PlentyMarkets catalog straight from another source, which saves typing when product data already lives in a sheet or a supplier file.

When to use it
a new product row is approved in your planning sheet and should become an item in the shop system.
Watch out
check with Search Items that the product is not already there before creating it.
PlentyMarkets3

Create an Order

Action

In Make“Creates a new order.”

Records a sale in PlentyMarkets even when it happened somewhere else, so fulfilment and stock follow the same process as your shop orders.

When to use it
a deal closes in a sales app or a marketplace your shop system does not read, and the warehouse needs to see it.
Watch out
make sure the buyer exists first, with Search Contacts or Create a Contact earlier in the scenario.
PlentyMarkets4

Create a Tag Relationship

Action

In Make“Creates a new tag relationship.”

Attaches a tag to a record in PlentyMarkets, which lets you mark things automatically instead of clicking through the back end one by one.

When to use it
an event in another tool, such as a complaint or a priority flag, should show up as a tag your team can filter on.
Watch out
run Search Tag Relationships first if the scenario may pass the same record twice, so the link is not created again.
PlentyMarkets5

Create a Ticket

Action

In Make“Creates a new ticket.”

Opens a support ticket in PlentyMarkets from any source you connect, so customer requests stop living in scattered inboxes.

When to use it
a form, a chat or an email parser receives a request that the service team handles in PlentyMarkets.
Watch out
map the contact from a previous search, otherwise the ticket has nobody to answer.
PlentyMarkets6

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a customer record from PlentyMarkets, which is how you honor a deletion request coming from another system without doing it by hand.

When to use it
a customer asks to be forgotten in your CRM and the shop back end must follow.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy contact before switching the scenario on.
PlentyMarkets7

Delete an Item

Action

In Make“Deletes an item.”

Takes a product out of your PlentyMarkets catalog for good, keeping the item list in line with the source where products are managed.

When to use it
a product is marked as discontinued in your product sheet and should disappear from the shop system as well.
Watch out
nothing brings the item back from Make; add a filter so only the rows you really mean reach this module.
PlentyMarkets8

Delete an Order

Action

In Make“Deletes an order.”

Erases an order from PlentyMarkets, useful to clean out test orders or duplicates created by another scenario.

When to use it
a test run left dummy orders behind and you want the order list clean again.
Watch out
this is permanent, so for a real customer order, correcting it with Update an Order is usually the safer move.
PlentyMarkets9

Get a Contact

Action

In Make“Gets a contact.”

Fetches the full record of one customer you already know, so later modules can reuse what PlentyMarkets stores about that customer.

When to use it
an earlier module handed you a specific contact and you need its details to write an email or fill a ticket.
Watch out
it reads one known contact; to find someone by criteria, start with Search Contacts.
PlentyMarkets10

Get an Item

Action

In Make“Gets an item.”

Reads a single product from the catalog, handy when another app only knows which item it is and needs the rest of the product data.

When to use it
an order line or a support ticket points to a product and you want its details in a message or a sheet.
Watch out
map the item from a previous module; if you only have a name or a criterion, Search Items is the right entry point.
PlentyMarkets11

Get an Order

Action

In Make“Gets an order.”

Pulls one order out of PlentyMarkets with its details, so you can pass them to accounting, a chat channel or a customer message.

When to use it
a ticket or an email mentions an order and the scenario must look it up before replying.
Watch out
Make needs to know which order you want, so map it from an earlier module rather than typing it by hand.
PlentyMarkets12

Get a Ticket

Action

In Make“Gets a ticket.”

Returns the content of one support ticket, which lets other tools display or react to a request the team already logged.

When to use it
you want to post a ticket's details in a team chat or copy them into a reporting sheet.
Watch out
it reads a single known ticket; to go through several at once, use Search Tickets instead.
PlentyMarkets13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the PlentyMarkets API with the connection you already set up, covering whatever the other modules leave out.

When to use it
you need a PlentyMarkets object or action that none of the 21 modules names, and a developer or the API docs can tell you which call to make.
Watch out
you write the request yourself, so check the PlentyMarkets API documentation and test with Run once.
PlentyMarkets14

Update a Contact

Action

In Make“Updates a contact.”

Changes an existing customer record, so a new address or email captured elsewhere reaches PlentyMarkets without anyone editing it by hand.

When to use it
a customer updates their details in your CRM or newsletter tool and the shop back end should match.
Watch out
find the right contact first with Search Contacts, then map it here, to avoid overwriting someone else.
PlentyMarkets15

Update an Order

Action

In Make“Updates an order.”

Edits an order already in PlentyMarkets, which keeps its information current when news about it arrives from a carrier, a payment tool or your team.

When to use it
another app learns something about an order, such as a payment or a shipping event, and PlentyMarkets must reflect it.
Watch out
if the same scenario also searches orders, make sure an updated order does not get picked up and changed again on the next run.
PlentyMarkets16

Update a Ticket

Action

In Make“Updates a ticket.”

Modifies a support ticket in PlentyMarkets, so progress made in another tool is visible to the team working in the back end.

When to use it
a reply or a status change happens in your helpdesk or chat, and the PlentyMarkets ticket should show it.
Watch out
map the ticket from Search Tickets or Get a Ticket, so the change lands on the right request.
PlentyMarkets17

Search Contacts

Search

In Make“Searches contacts by given criteria.”

Looks through your PlentyMarkets customers with the criteria you set and hands back every match, one bundle per contact.

When to use it
before creating or updating anyone, to check whether the person already exists.
Watch out
the search can return zero, one or many contacts; each one runs the next modules separately and uses operations, so tighten your criteria or add a filter.
PlentyMarkets18

Search Items

Search

In Make“Searches items by given criteria.”

Finds products in the PlentyMarkets catalog that match your criteria, giving you a clean list to send to a sheet or another app.

When to use it
a colleague needs product data outside the shop system, or you want to check an item exists before creating it.
Watch out
a broad search can return many items and each result costs operations downstream, so keep the criteria narrow.
PlentyMarkets19

Search Orders

Search

In Make“Searches orders by given criteria.”

Pulls the orders that fit your criteria out of PlentyMarkets, which is the usual way to start a scheduled scenario on this app since it has no trigger.

When to use it
you want a scenario that picks up the orders matching your criteria and sends them to accounting or a reporting sheet.
Watch out
if nothing in your criteria or a filter excludes orders you already handled, the same orders come back on every run.
PlentyMarkets20

Search Tag Relationships

Search

In Make“Searches tag relationships by given criteria.”

Lists which records carry which tags in PlentyMarkets, turning your tagging into something other tools can read and act on.

When to use it
your team tags records by hand and you want those tagged records exported or sent to someone.
Watch out
each relationship found becomes its own bundle, so add an aggregator if you want one summary instead of many messages.
PlentyMarkets21

Search Tickets

Search

In Make“Searches tickets by given criteria.”

Collects the support tickets that match your criteria, so open requests can be reviewed or forwarded outside PlentyMarkets.

When to use it
you want a team chat to receive the tickets that still need an answer, or a sheet to list them.
Watch out
the module returns every match, so set criteria that exclude tickets you already handled, or they will be sent again.
Need help

Need help automating PlentyMarkets with Make?

A person reads every message.

FAQ

PlentyMarkets and Make: common questions

01Is the PlentyMarkets Make integration free?
Yes, PlentyMarkets is a standard app in Make, so you can use it on the Free plan. That plan has real limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, allow unlimited active scenarios and count usage in credits, which are operations. Your PlentyMarkets subscription is separate and is handled with PlentyMarkets.
02What do you need to connect PlentyMarkets to Make?
You need an active PlentyMarkets account and access to its back end settings. In Setup, copy the REST-API HTTP Endpoint shown under API data, then create a user under User accounts with Back end access and note its username and password. In Make, add a PlentyMarkets module, click Create a connection and enter those details or follow the on-screen instructions. The Make documentation also mentions OAuth 2.0 and a Bearer token, so follow whatever the connection window asks for.
03Does PlentyMarkets trigger Make scenarios in real time?
No. PlentyMarkets has no trigger module in Make, scheduled or instant, so nothing starts automatically when an order or ticket appears. You have two ways around it. Start the scenario on a schedule, set on the first module and every 15 minutes by default, then use Search Orders or Search Tickets to fetch what is new. Or start it from another app's trigger, a form or a sales tool for instance, and let PlentyMarkets modules do the work after it. On the Free plan a schedule cannot run more often than every 15 minutes.
04What if the PlentyMarkets module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the PlentyMarkets API with the connection you already have, so you are not limited to the 16 actions and 5 searches in the list. You write the request yourself, which means reading the PlentyMarkets API documentation first and testing with Run once. Also keep in mind that Make flags its own documentation for this app as AI-generated and possibly wrong in places, so confirm important details with PlentyMarkets before relying on them.
05Should you use Make or n8n with PlentyMarkets?
It depends on the tool your team already runs. Make offers 21 PlentyMarkets modules plus a universal API call, a visual editor and the Free plan to start. Many apps also have an n8n node, so check whether one exists for PlentyMarkets and what it covers before you decide. Compare the two on the modules you actually need, how each tool starts a scenario and which one your team is comfortable maintaining. Neither choice is wrong if it covers your orders, contacts and tickets.
Same platform

Other docs you might need on this stack.

Browse all integrations