Resources · Make integration

Adobe Commerce Make integrationAutomate Adobe Commerce with Make.

What could your store run on its own once orders, customers and products talk to Make? The Adobe Commerce Make integration offers 25 modules, including 4 triggers. This page is for store operators new to Make: you link your account, then build a first scenario that invoices new orders.

Try the Adobe Commerce integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Adobe Commerce Make integration do?

The Adobe Commerce Make integration lets Make read and change your store without code. You build a scenario, the automation Make runs for you, out of modules: bricks that watch for new orders, customers, products or credit memos, then create, update, invoice, ship or look up records in the store.

Orders that invoice themselves. Watch orders spots each new order, Invoice an order bills it, and Ship an order records the shipment once the parcel leaves. Your back office stops copying order numbers by hand.

A catalog fed from elsewhere. A supplier sheet or another tool can drive Create a product and Update a product, both keyed on the product SKU. Find Products checks first whether the item already exists, so you avoid duplicates.

Refunds your finance team hears about. Watch Credit Memos picks up each new credit memo and passes it to your accounting tool or a team channel. The same logic works for Watch customers when a new account should land in your CRM.

Two things to know before you start. The 4 triggers are all scheduled: Make checks the store on the scenario's schedule, there is no instant trigger here. And Make flags its own documentation for this app as AI-generated from Adobe's docs, so check important details on the Adobe side. When a listed module falls short, Make an API Call reaches any endpoint of the store's API with the same connection.

Adobe Commerce often has an n8n node too; n8n vs Make puts both tools side by side. To go further, Make training walks through scenario building, and Make troubleshooting helps when a run fails.

Connect

How do you connect Adobe Commerce to Make?

  1. 01

    Add a module and open the connection

    In your scenario, add any Adobe Commerce module and click Create a connection. A connection is your store account linked to Make once, then reused by every Adobe Commerce module.

  2. 02

    Generate an access token in the store

    In the Adobe Commerce admin, open System > Extensions > Integrations, click Add New Integration, fill Name and Your Password, pick resources in the API tab, then Save.

  3. 03

    Activate it and paste the token

    Click Activate next to the new integration, then Allow, and copy the API token shown. Back in Make, name the connection in Connection name if you like and paste the credentials.

First scenario

Your first scenario: invoice every new order

GoalWhen a new order is created in Adobe Commerce, Make creates its invoice.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Search for Adobe Commerce and choose Watch orders as the first module.

  2. 02

    Link your store

    Click Create a connection and paste the access token from your Adobe Commerce admin. Then fill the fields of Watch orders; Make lists what it can read once the connection works.

  3. 03

    Add the invoice step

    Click the + to the right of Watch orders and add Invoice an order. Map the order coming from the trigger, so each bundle (one order passing between modules) gets its own invoice.

  4. 04

    Test with Run once

    Place a test order, then click Run once. Read the bundles each module received, then confirm the invoice appears on the order in your admin.

  5. 05

    Schedule and switch on

    Click the clock on Watch orders to set the schedule. A new scenario checks every 15 minutes by default, and the Free plan cannot go faster. Then turn the scenario on.

Triggers

What can start an Adobe Commerce scenario?

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

Adobe Commerce1Watch Credit Memos

Watch Credit Memos

Scheduled trigger

In Make“Triggers when a new credit memo is created.”

Watch Credit Memos starts your scenario whenever a new credit memo is created in the store, so every refund reaches the people who need to see it. Each memo arrives as one bundle you can pass to a spreadsheet, an accounting tool or a message.

How it fires
scheduled. Make checks the store on the scenario's schedule and collects the memos created since the last check.
When to use it
your finance team wants a line in its ledger each time a customer is refunded.
Watch out
each memo it returns uses an operation, one run of one module that Make counts on your plan.
Adobe Commerce2Watch customers

Watch customers

Scheduled trigger

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

Every new customer account created in Adobe Commerce becomes a starting point with Watch customers. You get the new account as a bundle and can send it to a CRM, a mailing list or a welcome sequence without exporting anything.

How it fires
scheduled. Make polls the store on the scenario's schedule, the clock badge on the module.
When to use it
new sign-ups should appear in your sales or email tool without anyone exporting a CSV.
Watch out
its description covers new customers only; to act on a change to an existing account, pair Find Customers with your own logic.
Adobe Commerce3Watch orders

Watch orders

Scheduled trigger

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

This is the trigger most store automations begin with: each new order becomes a bundle Make can invoice, ship, copy to a sheet or announce to your team. It is the clearest way to see the integration work on real data.

How it fires
scheduled. Make checks the store on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
you want Invoice an order or Ship an order to follow each sale without anyone opening the admin.
Watch out
it reacts to new orders; to follow where an order stands later, call Get order status in a separate step.
Adobe Commerce4Watch products

Watch products

Scheduled trigger

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

Watch products tells you when a new product lands in the catalog, and hands its details to the next module. Useful to push a fresh item to a marketplace feed, a product sheet or a channel where merchandisers review launches.

How it fires
scheduled. Make looks at the catalog on the scenario's schedule and returns the products created since the previous run.
When to use it
several people add products and someone needs to check each new listing.
Watch out
an edit to an existing product does not count as new; rely on Get a product when you need the current version.
Modules

What else can Make do in Adobe Commerce?

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

Adobe Commerce1

Add a Cart Item

Action

In Make“Adds an item to a cart.”

Puts a product into an existing cart, the way a shopper would, so you can prepare a basket on a customer's behalf. The cart then holds the item until the customer checks out.

When to use it
a sales rep builds a reorder from a form and wants it ready in the customer's cart.
Watch out
the cart must exist first; run Create a Cart or Get a Cart earlier in the scenario.
Adobe Commerce2

Create a Cart

Action

In Make“Creates an empty cart and quote for a specified customer if customer does not have a cart yet.”

Opens an empty cart and quote for a given customer, which gives the following modules a basket to fill. It is the first brick of any assisted ordering flow.

When to use it
a phone or chat request should turn into a cart the customer finds when logging in.
Watch out
it only creates a cart if the customer does not already have one; otherwise use Get a Cart to work on the existing basket.
Adobe Commerce3

Create a Credit Memo

Action

In Make“Creates a new credit memo.”

Records a new credit memo in the store, so a refund decided somewhere else ends up in Adobe Commerce with the rest of the order history. Your books and your store stay in line.

When to use it
returns are approved in a helpdesk or a form, and the refund must be logged in the store afterwards.
Watch out
a credit memo is a financial record; test it with Run once on a test order before switching on.
Adobe Commerce4

Create a customer

Action

In Make“Creates a new customer.”

Adds a new customer account to the store from data held in another tool. Leads or wholesale clients can get an account without anyone typing their details into the admin.

When to use it
a B2B application form is approved and the buyer needs an account ready to order.
Watch out
run Find Customers first to check whether the person already has an account, otherwise you may create duplicates.
Adobe Commerce5

Create a product

Action

In Make“Creates a new product.”

Publishes a new product in the catalog from a sheet, a PIM or a supplier feed. The product appears in the store with the data you mapped from the previous module.

When to use it
your team prepares new references in a spreadsheet and wants them created in the store row by row.
Watch out
products are identified by SKU in this app; check with Find Products or Get a product that the SKU is free.
Adobe Commerce6

Delete a customer

Action

In Make“Deletes a customer by customer id.”

Removes a customer account, found by its customer ID, from the store. It keeps your customer base tidy when an account must disappear after a request handled elsewhere.

When to use it
a data deletion request is validated in your support tool and the store account has to go too.
Watch out
a deletion cannot be undone from Make; put a filter or an approval step before this module.
Adobe Commerce7

Delete a product

Action

In Make“Deletes a product by product SKU.”

Takes a product out of the catalog for good, using its SKU. Handy to clean up references a supplier has discontinued, instead of hunting them one by one in the admin.

When to use it
a supplier list marks items as withdrawn and your catalog must follow.
Watch out
nothing brings the product back once deleted; double check the SKU with Get a product first.
Adobe Commerce8

Edit a Cart Item

Action

In Make“Edits an existing cart item.”

Changes a product already sitting in a cart, so the basket matches what the customer finally wants. The rest of the cart stays as it was.

When to use it
a customer changes their mind by email and the rep updates the cart from the scenario.
Watch out
it edits an existing item only; to add a new product to the cart, use Add a Cart Item.
Adobe Commerce9

Get a Cart

Action

In Make“Gets info for the cart for a specified customer.”

Reads the cart of a given customer and returns its contents as a bundle. You see what the customer has selected and can decide what to do next in the scenario.

When to use it
before adding or editing items, to know what the basket already holds.
Watch out
it works per customer; if the customer has no cart yet, create one with Create a Cart.
Adobe Commerce10

Get a customer

Action

In Make“Gets a customer detail by customer id.”

Fetches the full record of one customer from its customer ID. The next modules can then use the name, email or other details without you opening the admin.

When to use it
an order or credit memo gives you a customer ID and you need the person's details for a message.
Watch out
it needs the ID; with only an email or a name, use Find Customers instead.
Adobe Commerce11

Get an order

Action

In Make“Gets an order by order id.”

Pulls one order by its order ID with everything the store knows about it. It is the step that turns a bare ID into data you can put in a sheet, a message or an invoice tool.

When to use it
a support ticket mentions an order ID and your scenario needs the order's content.
Watch out
one ID, one order; to list several orders by criteria, Find Orders is the right module.
Adobe Commerce12

Get a product

Action

In Make“Gets an info about product by product SKU.”

Reads the current information of a product from its SKU. You get a reliable picture of the item before updating it, deleting it or copying it to another channel.

When to use it
a price or stock update arrives by SKU and you want to compare it with the store first.
Watch out
it searches by exact SKU; with a partial name or a set of criteria, go through Find Products.
Adobe Commerce13

Get order status

Action

In Make“Checks the status of an order”

Checks where an order stands and returns its status. Your scenario can then branch: notify the customer, alert the warehouse, or simply wait.

When to use it
a customer asks about delivery in a form or chat, and you want the answer pulled from the store automatically.
Watch out
it reads the status at the moment the module runs; it does not start a scenario when the status changes.
Adobe Commerce14

Invoice an order

Action

In Make“Creates a new invoice for an order”

Creates the invoice for an order, which saves your back office from billing sales one at a time. Paired with Watch orders, it is the core of the first scenario on this page.

When to use it
every confirmed order should be invoiced as soon as Make sees it.
Watch out
an invoice is a financial document; run a test order with Run once before activating the scenario.
Adobe Commerce15

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Adobe Commerce API with the connection you already set up. It covers what the listed modules leave out, without a second login.

When to use it
you need an operation of the store that has no dedicated module in the list.
Watch out
you write the request yourself, so keep the Adobe Commerce API reference open and test with Run once.
Adobe Commerce16

Ship an order

Action

In Make“Creates new Shipment for given Order.”

Creates a new shipment for a given order, the step that tells the store the parcel has left. Your order history reflects reality without warehouse staff touching the admin.

When to use it
your logistics tool or a warehouse form confirms dispatch and the store must record it.
Watch out
map the right order ID from the previous module; a shipment recorded on the wrong order confuses customers.
Adobe Commerce17

Update a customer

Action

In Make“Updates a customer by customer id.”

Changes an existing customer record, found by its customer ID, with data coming from another tool. Corrections made in your CRM reach the store.

When to use it
your sales team edits contacts in a CRM and the store account must follow.
Watch out
it needs the customer ID; retrieve it with Find Customers when your other tool only knows the email.
Adobe Commerce18

Update a product

Action

In Make“Updates a product by product SKU.”

Modifies a product already in the catalog, targeted by its SKU. Changes coming from a sheet or supplier file land in the store without manual edits.

When to use it
a supplier sends revised prices and you want the catalog aligned.
Watch out
the SKU must match exactly; a typo means the product is not found, so check it with Get a product.
Adobe Commerce19

Find Customers

Search

In Make“Retrieves a list of customers based on search criteria.”

Searches the customer base with criteria and returns every match. Unlike Get a customer, you do not need the ID in advance, which makes it the usual first step before an update.

When to use it
you only have an email from a form and must find the matching account.
Watch out
a search can return zero, one or many bundles; add a filter so later modules act on the right one.
Adobe Commerce20

Find Orders

Search

In Make“Retrieves a list of orders based on search criteria.”

Returns the orders matching your search criteria, as many bundles as there are results. It is how you pull a batch of orders into a report or a follow-up flow.

When to use it
you want every order matching a condition copied to a sheet for review.
Watch out
each returned order flows through the next modules and uses operations; narrow the criteria to avoid surprises on your plan.
Adobe Commerce21

Find Products

Search

In Make“Retrieves a list of products based on search criteria.”

Looks through the catalog with criteria and lists the products that match. Perfect to check whether an item exists before creating it, or to gather products for a price change.

When to use it
a supplier sheet arrives and you must know which rows are new and which are updates.
Watch out
no result means zero bundles, so the following modules do not run; plan a branch for new products.
Need help

Need help automating Adobe Commerce with Make?

A person reads every message.

FAQ

Questions about Adobe Commerce and Make

01Is the Adobe Commerce Make integration free?
Yes, on the Make side. Adobe Commerce is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. Your Adobe Commerce subscription is a separate matter handled by Adobe.
02What does connecting Adobe Commerce to Make require?
You need an active account on the store with API credentials, meaning an access token. You create it in the admin under System, Extensions, Integrations: add a new integration, give it a name, confirm with your admin password, choose the resources in the API tab, save, then activate and allow it. Copy the token shown, click Create a connection in Make and paste it. Naming the connection is optional. Every Adobe Commerce module in your scenarios then reuses that single connection.
03Do Adobe Commerce triggers in Make fire instantly?
No. The 4 Adobe Commerce triggers (credit memos, customers, orders, products) are scheduled: Make checks the store on the scenario's schedule and picks up what was created since the last check. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan. Paid plans can go down to 1 minute. There is no instant, webhook based trigger for this app. Each check that returns items uses operations on your plan.
04What if a needed Adobe Commerce module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Adobe Commerce API with the connection you already have, so an operation without a dedicated module is still possible. You write the request yourself, so keep Adobe's API reference at hand. Make also flags its documentation for this app as AI-generated from Adobe's docs, so confirm important details with Adobe before relying on them. Test every custom request with Run once before switching the scenario on.
05Is Make or n8n better suited to Adobe Commerce?
It depends on the tool your team already works in. In Make, Adobe Commerce comes with 25 modules, 4 of them scheduled triggers, plus Make an API Call for the rest, and it works from the Free plan. The same app often has an n8n node as well, so check that it covers the records you need. Choose on the modules available and the platform you know, not on a ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations