Resources · Make integration

Maropost Commerce Cloud Make integrationAutomate Maropost Commerce Cloud with Make.

Your store already records every order, payment and customer; Make can act on each one for you. The Maropost Commerce Cloud Make integration offers 24 modules, including 8 triggers. This guide walks store operators through the connection, a first scenario and every module.

Try the Maropost Commerce Cloud integration on Make See the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Maropost Commerce Cloud Make integration do?

The Maropost Commerce Cloud Make integration links your store (the platform your control panel calls Neto by Maropost) to Make, a no-code automation tool. You build a scenario, meaning a chain of blocks called modules, and Make watches your orders, customers, products and content pages, then creates, updates or looks up records without anyone copying data by hand.

Paid orders that feed the rest of your stack. Watch Paid Orders picks up each order once payment lands, and the next module can pass it to your accounting tool, a chat channel or a spreadsheet. Pair it with Search Payments when you need the payment details next to the order.

Customer records that stay in sync. Watch New Customers and Watch Updated Customers spot changes in the store, while Create a Customer and Update a Customer push changes back from a CRM or a signup form, so both sides describe the same person.

A catalog and content you manage from elsewhere. Create a Product, Update a Product and Create a Content Page let a supplier sheet or an editorial tool write straight into the store. Returns get their own pair too: Create an RMA and Search RMAs.

One thing to know up front: the 8 triggers are all scheduled, none of them is instant, so Make checks the store at intervals rather than being pinged. The documentation is flagged as AI-generated, so confirm anything critical with Maropost directly. If you are still choosing a tool, read Make review and n8n vs Make; for help building, see Make agency.

Connect

How do you connect Maropost Commerce Cloud to Make?

01
Copy your API key from the store
In the Neto control panel, open Settings and tools, click All settings and tools, then API. The key shown on screen is what Make needs, so copy it now. You need an active Neto by Maropost account for this.
02
Add a module and start the connection
In your Make scenario, add any Maropost Commerce Cloud module and click Create a connection. A connection is your store account linked to Make once, then reused by every Maropost module in your scenarios.
03
Name it and paste the key
The Connection name field is optional but useful if you run several stores; a clear label saves guessing later. Paste the API key you copied, or follow the on-screen instructions, and save. Make can now read your store.

First scenario

Your first scenario with Maropost Commerce Cloud

GoalWhen an order is paid in Maropost Commerce Cloud, Make updates the matching customer record in the store.

01
Create the scenario
From the Scenarios page, create a new scenario and click the big + to add your first module. Search for Maropost Commerce Cloud and pick Watch Paid Orders.
02
Link your store
Click Create a connection, paste your API key and save. Once the connection exists, Make can list what it reads from your store while you fill in the trigger.
03
Add the customer update
Click the + on the right of the trigger and choose Update a Customer. Map the customer from the paid order into the module, so each order updates the right person.
04
Test with Run once
Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one paid order. Check that the right customer changed before going further.
05
Schedule and switch on
Open the clock on the first module to set the schedule: every 15 minutes by default, and never faster on the Free plan. Then switch the scenario on and let it run.

Triggers

What starts a Maropost Commerce Cloud scenario

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

Maropost Commerce Cloud1Watch Completed Orders

Watch Completed Orders

Scheduled trigger

In Make“Triggers when an order is completed.”

This trigger hands your scenario every order that reaches the completed stage, so post-sale work starts from a finished order rather than a fresh one.

How it fires

scheduled, Make checks the store on the scenario's schedule and collects the orders completed since its last look.

When to use it

send a thank-you message, request a review or push final figures to a report once the order is fully wrapped up.

Watch out

a completed order is further along than a paid one; if you need to react at payment, pick Watch Paid Orders instead.

Maropost Commerce Cloud2Watch New Content Pages

Watch New Content Pages

Scheduled trigger

In Make“Triggers when a new content page is created.”

Each content page someone creates in the store arrives in your scenario as a bundle, which lets your team announce or archive new pages without checking the admin.

How it fires

scheduled, Make polls the store at the interval set on the scenario and picks up pages created since the previous run.

When to use it

post a note to your marketing channel when an editor publishes a new landing or blog page, so nobody misses it.

Watch out

edits to existing pages do not fire it; only creations count.

Maropost Commerce Cloud3Watch New Customers

Watch New Customers

Scheduled trigger

In Make“Triggers when a new customer is created.”

Here your scenario receives every customer account newly created in the store, ready to be copied into a CRM, a mailing list or a welcome flow.

How it fires

scheduled, Make asks the store for new customers each time the scenario's schedule comes round, not the moment they sign up.

When to use it

add first-time buyers to your email tool with a welcome sequence, or open a record for them in your support desk.

Watch out

changes to existing customers are handled by Watch Updated Customers, so use both if your CRM must mirror every edit.

Maropost Commerce Cloud4Watch New Orders

Watch New Orders

Scheduled trigger

In Make“Triggers when a new order is created.”

You get each order created in the store, whatever its payment status, which makes it the earliest point to react to a sale.

How it fires

scheduled, Make checks for newly created orders on the scenario's schedule and passes along each one it finds.

When to use it

alert the warehouse team in chat, or log every incoming order in a sheet that sales can scan at a glance.

Watch out

a new order may still be unpaid; if the next step should only happen after payment, start from Watch Paid Orders.

Maropost Commerce Cloud5Watch Paid Orders

Watch Paid Orders

Scheduled trigger

In Make“Triggers when an order is paid.”

This one waits for money: your scenario only receives orders once they are paid, which keeps unpaid baskets out of your accounting and fulfillment steps.

How it fires

scheduled, Make looks at the store on the scenario's schedule and returns the orders paid since its last check.

When to use it

create the invoice in your accounting tool, or ping the packing team, only when the payment is confirmed.

Watch out

this trigger hands you the order; add Search Payments after it when you also need the payment record.

Maropost Commerce Cloud6Watch Updated Customers

Watch Updated Customers

Scheduled trigger

In Make“Triggers when a customer is updated.”

Whenever a customer record changes in the store, this trigger brings the new version into your scenario, so other tools stop working from an old address or name.

How it fires

scheduled, Make queries the store at the scenario's interval and gathers customers edited since the previous run.

When to use it

keep your CRM contact in step when a buyer changes their details at checkout or in their account.

Watch out

if the next module writes back into the store with Update a Customer, that edit can fire this trigger again, so avoid round trips.

Maropost Commerce Cloud7Watch Updated Orders

Watch Updated Orders

Scheduled trigger

In Make“Triggers when an order is updated.”

Any change made to an existing order lands in your scenario, which is handy for following an order through its life instead of only at creation.

How it fires

scheduled, Make checks the store on the scenario's schedule and collects orders modified since it last looked.

When to use it

update a shipping tracker or tell customer service when an order is edited after it was placed.

Watch out

writing to the same order with Update an Order in this scenario counts as a change too, and can start the loop again.

Maropost Commerce Cloud8Watch Updated Products

Watch Updated Products

Scheduled trigger

In Make“Triggers when a product is updated.”

Edits to your catalog flow straight into the scenario, so a price or description change in the store can reach every channel that lists the product.

How it fires

scheduled, Make polls the store at the scenario's interval and returns products changed since the previous check.

When to use it

refresh a marketplace listing, a product sheet shared with resellers or an internal catalog when merchandisers edit a product.

Watch out

new products are not covered by a dedicated trigger here; Search Products can list them when needed.

Modules

What Maropost Commerce Cloud can do in Make

Maropost Commerce Cloud gives you 16 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Maropost Commerce Cloud1

Create a Content Page

Action

In Make“Creates a new content page.”

Adds a new content page to your store from data held elsewhere, so an editorial tool or a spreadsheet can publish pages without anyone opening the admin.

When to use it

when an article is approved in your editorial calendar and should become a store page.

Watch out

each run creates a page; check with Search Content Pages first if the same item might arrive twice.

Maropost Commerce Cloud2

Create a Customer

Action

In Make“Creates a new customer.”

Opens a customer account in the store from details captured by another app, which spares your team from retyping names and addresses.

When to use it

a B2B lead signs a contract in your CRM and needs a store account before placing orders.

Watch out

run Search Customers first, otherwise a returning buyer can end up with a duplicate record.

Maropost Commerce Cloud3

Create an RMA

Action

In Make“Creates a new RMA.”

Records a return request, the RMA or return merchandise authorization, in the store, so returns logged in a form or a helpdesk reach the place your warehouse checks.

When to use it

a support agent approves a return in the ticketing tool and the store must know about it.

Watch out

link it to the right order; Search Orders helps you find it first.

Maropost Commerce Cloud4

Create a Payment

Action

In Make“Creates a new payment.”

Logs a payment in the store when the money was collected outside it, which keeps order balances accurate for your finance team.

When to use it

a bank transfer or an invoice paid through another tool must be marked against the store order.

Watch out

a payment created twice distorts your figures; check Search Payments before adding one from a source that can repeat.

Maropost Commerce Cloud5

Create a Product

Action

In Make“Creates a new product.”

Puts a new product into your catalog straight from a supplier sheet or a product database, so launches no longer depend on manual data entry.

When to use it

a new row appears in the purchasing spreadsheet and the item should be ready to sell.

Watch out

this module only creates; for an item that may already exist, look it up with Search Products and use Update a Product instead.

Maropost Commerce Cloud6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the store's API with the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it

you need an object or an action that no module on this page handles, and the API documentation describes it.

Watch out

you write the request yourself, so keep the vendor's API reference open and test with Run once.

Maropost Commerce Cloud7

Update a Content Page

Action

In Make“Updates the information of a specified content page.”

Changes an existing content page with new information, letting you maintain store copy from the tool where your team actually writes.

When to use it

a revised text is validated in your document workflow and the live page must reflect it.

Watch out

the module needs to know which page to change; find it with Search Content Pages or map it from Watch New Content Pages.

Maropost Commerce Cloud8

Update a Customer

Action

In Make“Updates the information of a specified customer.”

Rewrites the details of a specified customer, so the store holds the same information as your CRM or support desk.

When to use it

an account manager corrects a company name or contact in the CRM and the store should follow.

Watch out

in a scenario that starts with Watch Updated Customers, this edit can trigger the scenario again; add a filter to avoid a loop.

Maropost Commerce Cloud9

Update an Order

Action

In Make“Updates the information of a specified order.”

Edits a specified order with information coming from another system, typically your shipping or warehouse tool, so the store always shows where the order stands.

When to use it

the carrier platform confirms dispatch and the order in the store should carry that update.

Watch out

paired with Watch Updated Orders, the change you write counts as an update and can restart the scenario.

Maropost Commerce Cloud10

Update a Product

Action

In Make“Updates the information of a specified product.”

Refreshes a product that already exists in your catalog, which lets stock or price data from a supplier file land in the store without manual edits.

When to use it

your supplier sends a new price list and the matching products must change.

Watch out

identify the product first with Search Products; a wrong match overwrites the wrong item.

Maropost Commerce Cloud11

Search Content Pages

In Make“Returns an information about content pages.”

Looks up content pages in the store and returns what it finds, which gives later modules the page they need to update or report on.

When to use it

before Update a Content Page, or to build a list of pages for a content audit shared with the team.

Watch out

a search can return zero, one or many pages, and every following module runs once for each.

Maropost Commerce Cloud12

Search Customers

In Make“Returns an information about customers.”

Finds customers in the store and hands their records to the next step, the usual way to check whether a buyer exists before creating one.

When to use it

a lead arrives from a form and you want to avoid a duplicate account with Create a Customer.

Watch out

no match means no bundle, so later modules do not run; plan a route for that case.

Maropost Commerce Cloud13

Search Orders

In Make“Returns an information about orders.”

Retrieves orders from the store so a scenario can work on past sales, not only those picked up by a trigger.

When to use it

a customer writes to support and you want their orders attached to the ticket automatically.

Watch out

several orders can match, each becoming a separate bundle that consumes operations, the unit Make counts on your plan.

Maropost Commerce Cloud14

Search Payments

In Make“Returns an information about payments.”

Pulls payment records from the store, so your finance steps can see how an order was paid without opening the admin.

When to use it

right after Watch Paid Orders, when your accounting tool needs payment details to reconcile the sale.

Watch out

a search can return several payments, each as its own bundle, and every following module runs once per bundle.

Maropost Commerce Cloud15

Search Products

In Make“Returns the information about products.”

Returns products from your catalog, which is how a scenario checks that an item exists or gathers product data for another channel.

When to use it

before Update a Product, or to feed a price comparison sheet your buyers keep.

Watch out

a broad search on a large catalog sends many bundles down the scenario, so narrow it where you can.

Maropost Commerce Cloud16

Search RMAs

In Make“Returns an information about RMAs.”

Lists return authorizations recorded in the store, so your team can track returns from a report or a helpdesk instead of the admin.

When to use it

a support agent needs the status of a customer's return, or you compile returns for a quality review.

Watch out

an empty result stops the rest of the scenario for that run, which is normal but can look like a failure.

Need help

Need help automating Maropost Commerce Cloud with Make?

A person reads every message.

FAQ

Maropost Commerce Cloud and Make: common questions

01Is the Maropost Commerce Cloud Make integration free?

Yes, on the Make side. Maropost Commerce Cloud is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits each month. You still need your own Maropost store subscription, which Make does not cover. Every plan also includes more than 3000 standard apps, so the rest of your stack is usually covered too.

02What is needed to connect Maropost Commerce Cloud to Make?

You need an active Neto by Maropost account and its API key. In the Neto control panel, open Settings and tools, then All settings and tools, then API, and copy the key displayed. In Make, add a Maropost Commerce Cloud module, click Create a connection, optionally name it, and paste the key. The connection is then reused by every Maropost module in your scenarios, so this setup happens once. If the key changes later, update the connection once and every module keeps working.

03Do Maropost Commerce Cloud triggers in Make fire instantly?

No. All 8 triggers are scheduled: Make checks the store on the scenario's schedule and collects what changed since its last visit. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. Whatever happens between two checks is picked up at the next run, so plan steps that tolerate that gap. The clock badge on each trigger in the editor is the visual reminder that it runs on a schedule.

04What if a Maropost Commerce Cloud module is missing in Make?

Use Make an API Call. It reaches any endpoint of the store's API with the connection you already have, so actions the 24 listed modules do not cover remain possible. You write the request yourself, following the vendor's API reference. Note that Make's documentation for this app is marked as AI-generated and may contain mistakes, so verify important details with Maropost before relying on them. Test each custom request with Run once before switching the scenario on.

05Make or n8n for Maropost Commerce Cloud?

It depends on the tool your team already knows. This page covers what Make offers for this store: 24 modules, 8 scheduled triggers and Make an API Call for the rest. The same app often has an n8n node too. Compare both on what matters to you, such as the modules available for your use case and how your team prefers to build, and test your first workflow in the tool you keep. A useful check is to build the same small flow in both and keep the one your team maintains most easily.

Copy your API key from the store

Add a module and start the connection

Name it and paste the key

Create the scenario

Link your store

Add the customer update

Test with Run once

Schedule and switch on

Need help automating Maropost Commerce Cloud with Make?