Resources · Make integration

PrestaShop Make integrationAutomate PrestaShop with Make.

What if new orders, customers and stock levels in your shop fed your other tools on their own? The PrestaShop Make integration gives you 32 modules: 5 triggers, 18 actions and 9 searches. This guide connects your store, then walks you through a first working scenario.

Try the PrestaShop integration on Make See the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PrestaShop Make integration do for your shop?

The PrestaShop Make integration links your store's back office to Make, a no-code tool where you build a scenario (the automation itself, a chain of steps). Each step is a module: it watches orders or customers, reads a product, or writes a change back to the store, without a line of code.

Orders that reach the right people. A typical setup for an online shop: Watch Orders spots each new or edited order, List Order Rows pulls out the items bought, and the next module sends them to the tool your warehouse or accounting team already reads.

A stock level you can trust. Watch Products catches every product created or edited, Get a Product's Stock reads the quantity, and Update a Product's Stock writes a corrected figure back when another system holds the real count.

Customer records kept tidy. Watch Customers fires on new sign-ups and profile edits, List Customer Groups shows which groups exist, and Update a Customer fixes the record in place.

Know the limits before you start. All five PrestaShop triggers are scheduled: Make checks the store on a clock, so nothing arrives the instant it happens. The module list has no Delete module, and anything missing goes through Make an API Call. Make also flags its PrestaShop documentation as AI-generated, so double-check important details with PrestaShop. When a run fails, Make troubleshooting covers the usual causes.

Comparing tools? The n8n vs Make guide lays out the criteria side by side, and Make training takes you further once this first scenario runs.

Connect

How do you connect PrestaShop to Make?

01
Generate an API key in PrestaShop
In your PrestaShop back office, open Advanced Parameters, then the Web service page. Click Add new webservice key, then Generate, and copy the key shown in the input field. You need an active store for this.
02
Add a PrestaShop module in Make
Log in to Make, add any PrestaShop module to your scenario and click Create a connection. A connection is your store linked to Make once, then reused by every PrestaShop module you add later.
03
Paste the key and save
Give the connection a name in Connection name if you run several stores (the field is optional). Enter the credentials you copied from PrestaShop, or follow the on-screen instructions, and save. Make can now read your store.

First scenario

Your first scenario: send order rows onward

GoalWhen an order is created or updated in PrestaShop, Make lists the rows of that order so the next module can use each item.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big +. Search for PrestaShop and pick Watch Orders as the first module.
02
Connect your store
Click Create a connection and paste the API key from your back office. Once linked, Make can list the objects it reads in your store, so there is nothing to type by heart.
03
Add List Order Rows
Click the + on the right of Watch Orders and choose List Order Rows. Map the order ID from the first module: each row then travels as its own bundle, one item per product line.
04
Test with Run once
Edit or place a test order in the shop, then click Run once. Open the bubbles above each module to read the bundles they received and check the rows match the order.
05
Schedule and switch on
Open the clock on Watch Orders. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Adjust it, then switch the scenario on.

Triggers

What starts a PrestaShop scenario

5 modules start a scenario when something happens in PrestaShop. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PrestaShop as soon as it happens.

PrestaShop1Watch Carts

Watch Carts

Scheduled trigger

In Make“Triggers when a cart is created or updated.”

This trigger hands your scenario every cart that shoppers create or change in the store, so you can react to baskets before they turn into orders.

How it fires

scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and picks up what changed since the last check.

When to use it

when your team wants to follow what customers put in their basket, for example to log carts in a sheet shared with marketing.

Watch out

an edited cart comes through again, since the trigger covers creation and updates. Plan a check so the same cart is not handled twice.

PrestaShop2Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when a customer is created or updated.”

Each new account and each edited customer profile lands in your scenario as a bundle, ready to be copied into your CRM or mailing tool.

How it fires

scheduled. Make polls PrestaShop on the scenario's schedule instead of hearing from the store instantly.

When to use it

a new buyer registers and your sales or support team needs the contact in their own tool without copying it by hand.

Watch out

a simple profile edit also triggers a run. If you only want brand-new customers, add a filter after the trigger, or you will create duplicates downstream.

PrestaShop3Watch Manufacturers

Watch Manufacturers

Scheduled trigger

In Make“Triggers when a manufacturer is created or updated.”

Here the scenario starts whenever a brand record is added or edited in your catalog, which keeps supplier lists elsewhere in step with the shop.

How it fires

scheduled. Make checks the app on the scenario's schedule; nothing is pushed by PrestaShop.

When to use it

your purchasing team keeps a supplier sheet and wants each new brand from the back office to appear there too.

Watch out

manufacturer changes are rare, so a tight schedule mostly burns checks on empty runs. The Free plan will not go under 15 minutes anyway.

PrestaShop4Watch Orders

Watch Orders

Scheduled trigger

In Make“Triggers when an order is created or updated.”

Most PrestaShop scenarios start here: every order placed or modified in the shop becomes a bundle your next modules can read and pass on.

How it fires

scheduled. Make queries the store on the scenario's schedule, every 15 minutes on a new scenario, down to 1 minute on paid plans.

When to use it

a sale should alert the warehouse, feed an accounting sheet or start a follow-up email in another app.

Watch out

every update counts, so a status change will likely bring the same order through the scenario again. Add a filter on what you actually care about before any action that sends a message.

PrestaShop5Watch Products

Watch Products

Scheduled trigger

In Make“Triggers when a product is created or updated.”

Use this trigger to catch each product that appears in the catalog or gets edited, and push the change to wherever else your product data lives.

How it fires

scheduled. Make checks the app on the scenario's schedule and collects the products changed since its previous look.

When to use it

a marketplace feed, a price sheet or a team channel needs to know when the catalog moves.

Watch out

a bulk edit in the back office sends many bundles at once, and each module run on each bundle is an operation Make counts on your plan.

Modules

What Make can do in your PrestaShop store

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

PrestaShop1

Create a Cart

Action

In Make“Creates a new cart.”

Opens a fresh cart in the store from data your scenario already holds, so a basket can exist in PrestaShop without anyone clicking through the front office.

When to use it

a quote accepted in another tool should become a real cart the customer can finish.

Watch out

a cart is not an order. Pair it with Create an Order if the sale must be recorded.

PrestaShop2

Create a Customer

Action

In Make“Creates a new customer.”

Adds a new customer account to your shop, filled from a form, a CRM or any earlier module, and saves the retyping.

When to use it

a B2B client signs in another tool and needs a PrestaShop account before the first order.

Watch out

run List Customers first to check the person is not already there, or you will end up with two accounts for one buyer.

PrestaShop3

Create an Order

Action

In Make“Creates a new order.”

Records a new order in PrestaShop from outside the storefront, which keeps sales made elsewhere in the same back office as the rest.

When to use it

orders taken by phone, at a trade fair or in another sales channel should sit next to online ones.

Watch out

test it with Run once on a dummy order first, since the list of modules has no Delete to undo a mistake.

PrestaShop4

Create a Product

Action

In Make“Creates a new product.”

Puts a new product in your catalog from a supplier file, a sheet or another app, instead of entering it by hand in the back office.

When to use it

your team prepares new references in a shared sheet and wants them published in the store from there.

Watch out

the scenario creates one product per bundle it receives. Run it once on a single row before you feed it a full list.

PrestaShop5

Get a Cart

Action

In Make“Retrieves the details of a customer cart by its ID.”

Fetches everything about one cart when you already know its ID, so the next module can read what the shopper had selected.

When to use it

another module handed you a cart ID and you need the detail before sending a reminder.

Watch out

without an ID this module has nothing to look up. When you only have criteria, use List Carts instead.

PrestaShop6

Get a Customer

Action

In Make“Retrieves the details of a customer by its ID.”

Returns the full record of a single customer from their ID, which gives later modules the details they need to personalise a message or update another tool.

When to use it

a trigger or search gave you a customer ID and you want the rest of the profile.

Watch out

it reads one customer only. To browse by criteria, List Customers is the right choice.

PrestaShop7

Get a Language

Action

In Make“Retrieves the details of a specified language by its ID.”

Tells your scenario which language sits behind a language ID in your store, handy when a shop runs in several languages.

When to use it

an order or customer comes with a language ID and you want to route it to the team that speaks that language.

Watch out

the module needs the ID to start from; it does not list every language of the store for you.

PrestaShop8

Get a Manufacturer

Action

In Make“Retrieves the details of a manufacturer by its ID.”

Reads one brand record by its ID and passes its details downstream, so a product or order can be matched to the right supplier.

When to use it

you want the manufacturer behind a product before notifying the buyer who handles that brand.

Watch out

it needs the brand's ID to start from. If you only know the name, List Manufacturers finds the ID first.

PrestaShop9

Get an Address

Action

In Make“Retrieves the details of an address by its ID.”

Pulls a single address from the store by its ID and makes it available to the next module, typically a shipping or invoicing tool.

When to use it

a new order should create a shipment elsewhere and the carrier needs the full address.

Watch out

a customer can have several addresses. Make sure the ID you map is the one you want, not just the first one found.

PrestaShop10

Get an Order

Action

In Make“Retrieves the details of an order by its ID.”

Loads one order in full from its ID, a useful step when a previous module only gave you the reference and you need the rest.

When to use it

a support ticket mentions an order ID and your scenario should attach the order details to it.

Watch out

items bought are not listed one by one here; add List Order Rows when you need each product line.

PrestaShop11

Get a Product

Action

In Make“Retrieves the details of a product by its ID.”

Gives your scenario the complete sheet of one product, looked up by ID, so later steps can reuse its details.

When to use it

an order row points to a product and you want its full details for an invoice or a feed.

Watch out

stock is read by a separate module. Use Get a Product's Stock for the quantity.

PrestaShop12

Get a Product's Stock

Action

In Make“Retrieves stock quantity of a product by the product ID.”

Reads how many units of a product are on hand, from the product ID, and lets the scenario decide what to do with that number.

When to use it

after each order, check the remaining quantity and alert purchasing when it gets low.

Watch out

it only reads. Nothing changes in the store until you add Update a Product's Stock.

PrestaShop13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the PrestaShop API from your scenario, using the connection you already set up, for everything the listed modules do not cover.

When to use it

you need an action missing from this page, such as removing a record, if the PrestaShop API allows it, since the list has no Delete module.

Watch out

you write the request yourself, so keep the PrestaShop API documentation open and test with Run once before going live.

PrestaShop14

Update a Cart

Action

In Make“Updates an existing cart by its ID.”

Changes an existing cart, found by its ID, so the basket in PrestaShop reflects what was agreed elsewhere.

When to use it

a sales rep adjusts a quote in another tool and the customer's cart should follow before checkout.

Watch out

Watch Carts also fires on updates. If both sit in one scenario, you can create a loop, so filter carefully.

PrestaShop15

Update a Customer

Action

In Make“Updates an existing customer by its ID.”

Edits a customer already in the store, located by ID, which keeps profiles aligned with the CRM your team works in every day.

When to use it

someone changes their details in your CRM and the PrestaShop account should match.

Watch out

an update wakes Watch Customers too. Avoid pairing both in the same scenario without a filter, or records bounce back and forth.

PrestaShop16

Update an Order

Action

In Make“Updates an existing order by its ID.”

Writes changes onto an existing order by its ID, so a status or detail handled in another system shows up in your back office.

When to use it

the warehouse marks a parcel as shipped in its own tool and the order in PrestaShop should move too.

Watch out

Watch Orders sees that edit as a new event. Keep the two in separate scenarios, or filter, to avoid endless runs.

PrestaShop17

Update a Product

Action

In Make“Updates an existing product by its ID.”

Modifies a catalog product from its ID, letting a sheet or supplier feed keep the store's product pages correct.

When to use it

prices or descriptions are maintained outside PrestaShop and must reach the shop after each change.

Watch out

run it once on a single product and check the page before mapping a full catalog; there is no undo button.

PrestaShop18

Update a Product's Stock

Action

In Make“Updates stock quantity of a product by the product ID.”

Sets the quantity available for a product, found by product ID, so the shop stops selling what the warehouse no longer has.

When to use it

your inventory tool or supplier holds the real count and the store must follow it.

Watch out

read the current figure with Get a Product's Stock and test with Run once, since a wrong mapping changes what customers can buy.

PrestaShop19

List Addresses

In Make“Retrieves a list of addresses and filters by criteria.”

Searches the store's addresses with the criteria you set and returns each match as its own bundle, one address per item.

When to use it

you want every address tied to a customer, for instance to check them before a delivery campaign.

Watch out

a search can return zero, one or many bundles, and every following module then runs once per address.

PrestaShop20

List Carts

In Make“Retrieves a list of customer carts and filters by criteria.”

Pulls a batch of customer carts filtered by your criteria, which lets you review baskets without waiting for the trigger.

When to use it

you are building a one-off report on open carts, or catching up on carts from before the scenario existed.

Watch out

each cart becomes a bundle, and each module after it counts one operation per cart.

PrestaShop21

List Customer Groups

In Make“Retrieves a list of customer groups and filters by criteria.”

Shows the customer groups defined in your shop, one bundle per group, so the scenario knows which segments exist.

When to use it

before you place a customer in a group from another tool, you need the list to pick the right one.

Watch out

it lists groups, not the customers inside them. Use List Customers for the people.

PrestaShop22

List Customers

In Make“Retrieves a list of customers and filters by criteria.”

Finds customers that match your criteria and sends each one down the scenario as a separate bundle.

When to use it

check whether the person already has an account before Create a Customer, or export a segment to a newsletter tool.

Watch out

an empty result is normal when nobody matches. Plan what the next module should do in that case.

PrestaShop23

List Images

In Make“Retrieves a list of images of a specific entity.”

Collects the images attached to a given entity, a product for instance, and outputs one bundle per image.

When to use it

a marketplace feed or a catalog sheet needs every picture of each product you sell.

Watch out

the module works on one specific entity at a time, so map its ID from an earlier step.

PrestaShop24

List Manufacturers

In Make“Retrieves a list of manufacturers and filters by criteria.”

Returns the brands registered in your catalog that fit your criteria, each as its own bundle for the next step.

When to use it

you want to rebuild a full supplier list in a sheet, or find the ID of a brand by name.

Watch out

for a single known brand, Get a Manufacturer is lighter than a search.

PrestaShop25

List Order Rows

In Make“Retrieves a list of rows of an order by the order ID.”

Breaks an order into its lines, from the order ID, and passes each product line on as a separate bundle.

When to use it

right after Watch Orders, when the warehouse or accounting needs one entry per item sold.

Watch out

an order with many lines means many bundles, and the modules after this one run once per line.

PrestaShop26

List Orders

In Make“Retrieves a list of orders and filters by criteria.”

Retrieves orders that match your filters, one bundle per order, which is useful when you need past sales rather than new ones.

When to use it

you set up a scenario after launch and want to bring older orders into a report or another app.

Watch out

a wide filter returns a lot of orders, and each one costs operations in every module that follows.

PrestaShop27

List Products

In Make“Retrieves a list of products and filters by criteria.”

Searches the catalog with your criteria and delivers the matching products one bundle at a time.

When to use it

you want to push a whole category to a price sheet, or check products before a bulk Update a Product.

Watch out

test the filter with Run once and read the bundle count before connecting any update module behind it.

Need help

Need help automating PrestaShop with Make?

A person reads every message.

FAQ

PrestaShop and Make: common questions

01Is the PrestaShop Make integration free?

Yes, PrestaShop is a standard app in Make, so it works from the Free plan. That plan has 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) go down to a 1 minute interval, remove the cap on active scenarios and count usage in credits per month. Your PrestaShop store itself is a separate subscription with PrestaShop.

02What do you need to connect PrestaShop to Make?

An active PrestaShop store and an API key generated in its back office. Go to Advanced Parameters, open the Web service page, click Add new webservice key, then Generate, and copy the key from the input field. In Make, add a PrestaShop module, click Create a connection, name it if you like and paste the credentials. The connection is then reused by every PrestaShop module in your scenarios, so this setup only happens once per store.

03Do PrestaShop triggers in Make fire instantly?

No. All five PrestaShop triggers are scheduled: Make checks the store on the scenario's schedule and picks up carts, customers, manufacturers, orders or products created or updated since the last check. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. There is no instant trigger for PrestaShop in Make, so plan for that delay when a customer message depends on it.

04What if a PrestaShop module is missing in Make?

It depends on what you need, but the Make an API Call module covers most gaps. It calls any endpoint of the PrestaShop API with the connection you already have, which helps for actions outside the 32 listed modules, such as deleting a record, since the list has no Delete module. You write the request yourself, so test it with Run once. Make also warns that its PrestaShop documentation is AI-generated: check important details with PrestaShop before relying on them.

05Make or n8n for PrestaShop automation?

It depends on the tool your team already runs. On the Make side, PrestaShop brings 32 modules, including 5 scheduled triggers and a Make an API Call module for the rest, and it is available on every plan, Free included. An n8n node often exists for the same app, so compare what each one offers for your store before choosing. The n8n vs Make comparison on this site sets out the criteria side by side, without declaring a winner.

Generate an API key in PrestaShop

Add a PrestaShop module in Make

Paste the key and save

Create the scenario

Connect your store

Add List Order Rows

Test with Run once

Schedule and switch on

Need help automating PrestaShop with Make?