Resources · Make integration

CommerceHQ Make integrationAutomate CommerceHQ with Make.

Can your CommerceHQ store run its routine chores without you? The CommerceHQ Make integration gives you 21 modules: 4 triggers, 14 actions and 3 searches. This guide is for store owners new to Make, and it walks you from the connection to a first working scenario.

Try the CommerceHQ integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CommerceHQ Make integration automate?

The CommerceHQ Make integration links your store to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something. Your store can then react on its own to new customers, paid orders and product changes, and pass that data to the other apps you use.

Orders that close themselves. Watch New Paid Orders picks up each paid order and Ship Order marks it as shipped, which suits a store where delivery is handled outside CommerceHQ.

A clean customer base. Watch New Customers hands every new buyer to the rest of your stack, while Update a Customer and Delete a Customer keep records tidy. A customer who already placed an order cannot be deleted, so plan an update instead.

A catalog that stays in sync. Watch New Products and Watch Updated Products report catalog changes, and Create a Product, Update a Product or Update a Collection push changes back from a supplier sheet.

Everything the listed modules skip can still be reached with Make an API Call, which uses the same connection. Before you commit, read our Make review and check Make pricing. CommerceHQ may also be available in n8n: the n8n vs Make comparison lays out both tools side by side.

Connect

How do you connect CommerceHQ to Make?

  1. 01

    Create a private app in CommerceHQ

    Log in to CommerceHQ, open Dashboard then Apps Store, and click Add a Private App. Give it a name you will recognize, then click Add The Private App.

  2. 02

    Save the two credentials

    CommerceHQ now shows an API Key and an API Password. Copy both into a password manager or another safe place, because Make asks for them in the next step.

  3. 03

    Add the connection in Make

    In your scenario, insert any CommerceHQ module and click Add next to the Connection field. Name the connection, type your store name in Store, paste the key and password, then click Save.

First scenario

Build your first scenario with CommerceHQ

GoalWhen a new paid order appears in CommerceHQ, Make marks that order as shipped.

  1. 01

    Start a blank scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module.

  2. 02

    Add the paid order trigger

    Search for CommerceHQ, pick Watch New Paid Orders and select your connection, or click Add to create it with the steps above.

  3. 03

    Add Ship Order

    Click the + on the right of the trigger, choose CommerceHQ again, then Ship Order. Map the order coming from the trigger so Make knows which one to close.

  4. 04

    Test with Run once

    Click Run once and open the bubbles to read the bundles, the items each module received. Use a test order: this module really marks the order as shipped.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks the store. A new scenario checks every 15 minutes by default. Then turn the scenario on.

Triggers

Which CommerceHQ triggers start a scenario?

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

CommerceHQ1Watch New Customers

Watch New Customers

Scheduled trigger

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

Hands you each customer created in your store as soon as Make spots it, so a newsletter tool, a CRM or a welcome email can take over without anyone copying data. Every customer arrives as one bundle, with the details CommerceHQ holds.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes on a new scenario.
When to use it
when a first purchase or a sign-up should add the buyer to another list right away.
Watch out
each customer found counts as an operation, so a busy launch uses more of your plan.
CommerceHQ2Watch New Paid Orders

Watch New Paid Orders

Scheduled trigger

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

Gives you every order once the payment has gone through, which makes it the safest starting point for anything that should only happen after the money is in. Unpaid carts never reach your scenario.

How it fires
scheduled, Make checks the app on the scenario's schedule rather than being alerted by CommerceHQ.
When to use it
to warn a supplier, log revenue in a sheet or close the order with Ship Order.
Watch out
on the Free plan the shortest gap between two checks is 15 minutes, so orders show up in batches.
CommerceHQ3Watch New Products

Watch New Products

Scheduled trigger

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

Tells your other tools that a product was just added to the catalog, so a marketing sheet, a feed or a team channel hears about it without a manual export. Each new product becomes one bundle you can map into the next module.

How it fires
scheduled, Make looks at the store each time the scenario runs.
When to use it
when adding a product should set off a launch checklist or a post for the team.
Watch out
it ignores edits to existing products; pick Watch Updated Products for those.
CommerceHQ4Watch Updated Products

Watch Updated Products

Scheduled trigger

In Make“Triggers when an existing product is updated.”

Catches the products someone changed in CommerceHQ, which lets a copy of your catalog elsewhere stay current instead of drifting out of date. It covers edits, not additions, so it pairs well with Watch New Products.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the products changed since the last check.
When to use it
to keep a price list, a marketplace listing or a stock sheet aligned with the store.
Watch out
if the same scenario runs Update a Product, it may pick up its own edit on the next check.
Modules

What can each CommerceHQ module do?

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

CommerceHQ1

Create a Collection

Action

In Make“Creates a new collection.”

Opens a new collection in your store from a scenario, so seasonal groupings or supplier ranges can appear without clicking through the dashboard.

When to use it
when a new brand or theme arrives in a planning sheet and should get its own shelf.
Watch out
run it once per collection name, or a repeat run may create a second one.
CommerceHQ2

Create a Customer

Action

In Make“Creates a new customer.”

Adds a customer record to CommerceHQ from data collected elsewhere, which spares you retyping names from a form or a wholesale order.

When to use it
after a trade show sign-up or a B2B request that should become a real customer in the store.
Watch out
check first with List Customers, otherwise the same person can end up with two records.
CommerceHQ3

Create a Product

Action

In Make“Creates a new product.”

Publishes a new product in the catalog from a scenario, turning a supplier row or an approved draft into a real listing without manual entry.

When to use it
when your team validates products in a spreadsheet and wants them in the store once the row is approved.
Watch out
Watch New Products will also see this product, so avoid feeding it back into the same flow.
CommerceHQ4

Delete a Collection

Action

In Make“Deletes an existing collection.”

Removes a collection you no longer need, which keeps the storefront free of empty seasonal groupings once a campaign has ended.

When to use it
when a promotion is marked as finished in your planning tool and its collection should disappear too.
Watch out
a delete cannot be undone from Make, so test it on a throwaway collection first.
CommerceHQ5

Delete a Customer

Action

In Make“Deletes an existing customer. Only customers without orders can be deleted.”

Erases a customer record from the store, useful for tidying up duplicates or test accounts created while you set things up.

When to use it
after a data cleanup flagged fake or duplicate sign-ups that never bought anything.
Watch out
CommerceHQ refuses to delete a customer who has orders, so the module fails on real buyers; update them instead.
CommerceHQ6

Delete a Product

Action

In Make“Deletes an existing product. If it has been purchased before, its data will remain untouched in orders.”

Takes a product out of the catalog for good, which helps retire discontinued items as soon as a supplier stops them.

When to use it
when an item is flagged as end of life in your supplier file.
Watch out
past orders that included the product keep their original data, so sales history stays intact, but the listing itself is gone and cannot be restored from Make.
CommerceHQ7

Get a Collection

Action

In Make“Gets information on a collection.”

Reads one collection and hands its details to the next module, so a scenario can check what a grouping contains before acting on it.

When to use it
before an update, to compare what the store holds with what your sheet says.
Watch out
it needs to know which collection to read; map it from List Collections or a previous step.
CommerceHQ8

Get a Customer

Action

In Make“Gets information on a single customer.”

Fetches the full record of a single customer, giving later modules the details they need to personalize an email or fill a CRM entry.

When to use it
right after a paid order, to pull the buyer's profile into your support or loyalty tool.
Watch out
it returns one customer only; for a batch, List Customers is the right module.
CommerceHQ9

Get a Product

Action

In Make“Gets information on a product.”

Looks up one product and returns what CommerceHQ knows about it, handy when another app only gives you a reference and you need the full picture.

When to use it
when a support ticket mentions an item and the agent should see its current store data.
Watch out
if the product was deleted in the meantime, the module will most likely error, so plan an error route.
CommerceHQ10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the CommerceHQ API with the connection you already set up, which covers everything the ready-made modules leave out.

When to use it
when you need an action no ready-made module offers, for example on orders beyond shipping.
Watch out
you write the request yourself, so keep the CommerceHQ API reference open while you build it.
CommerceHQ11

Ship Order

Action

In Make“Marks order as shipped.”

Marks an order as shipped in CommerceHQ, saving someone the routine of closing orders one by one once the parcel has left.

When to use it
when your carrier or warehouse app confirms dispatch and the store should reflect it.
Watch out
it acts on the order you map, so test on a dummy order before switching the scenario on.
CommerceHQ12

Update a Collection

Action

In Make“Updates an existing collection.”

Changes an existing collection, so its name or content can follow your merchandising plan without a trip to the dashboard.

When to use it
when a campaign is renamed or refreshed in the sheet your marketing team maintains.
Watch out
point it at the right collection; mapping the wrong one silently edits another shelf.
CommerceHQ13

Update a Customer

Action

In Make“Updates an existing customer.”

Edits a customer who already exists, keeping details in the store aligned with your CRM or support desk instead of maintaining them twice.

When to use it
when a buyer changes contact details in another tool and the store should follow.
Watch out
it is also the fallback for customers with orders, since those cannot be deleted.
CommerceHQ14

Update a Product

Action

In Make“Updates an existing product. If it has been purchased before, its data will remain untouched in orders.”

Rewrites the details of a live product, which keeps prices or descriptions in the store matched to your supplier data without manual edits.

When to use it
when a supplier file changes and the listing must follow.
Watch out
orders already placed keep the product data as it was at purchase, so only future buyers see the change.
CommerceHQ15

List Collections

Search

In Make“Gets all collections.”

Returns all your collections, one bundle each, so a scenario can loop through them to audit, export or update the whole set.

When to use it
to build an inventory of collections in a sheet before a catalog reorganization.
Watch out
every collection becomes a bundle, and each module after it runs once per bundle, which adds operations.
CommerceHQ16

List Customers

Search

In Make“Gets all customers.”

Pulls every customer in the store, one bundle per person, which is the starting point for exports, audits or a duplicate check.

When to use it
before Create a Customer, to see whether that person is already on file.
Watch out
a large customer base produces many bundles, and each module that follows counts an operation per bundle.
CommerceHQ17

List Products

Search

In Make“Gets all products.”

Gives back the whole catalog as a series of bundles, perfect for mirroring products into a sheet or checking listings against a supplier file.

When to use it
when a full sync matters more than tracking a single change.
Watch out
it returns zero, one or many products, so the modules after it may run several times in one pass.
Need help

Need help automating CommerceHQ with Make?

A person reads every message.

FAQ

CommerceHQ and Make: common questions

01Is the CommerceHQ Make integration free?
Yes, CommerceHQ is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a check every minute and runs of up to 40 minutes. Usage is counted in credits, one operation for each module run on each bundle. Your CommerceHQ subscription is a separate matter.
02What do you need to connect CommerceHQ to Make?
You need a CommerceHQ account where you can open Dashboard, then Apps Store, and create a private app. That private app gives you an API Key and an API Password. In Make, you add a connection from any CommerceHQ module and fill in a connection name, your store name and those two credentials. The store name is the first part of your shop address, so for example.commercehq.com you type example. The CommerceHQ documentation lists no other prerequisite.
03Do the CommerceHQ triggers in Make fire in real time?
No. All 4 CommerceHQ triggers are scheduled, which means Make asks the store for news on the scenario's schedule instead of being notified the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval, while paid plans can go down to one minute. If your process needs a faster reaction, shorten the schedule on a paid plan rather than expecting an instant push from CommerceHQ.
04What if a CommerceHQ module is missing in Make?
Use Make an API Call. It reaches any endpoint of the CommerceHQ API with the connection you already created, so an action outside the 21 listed modules is still possible. You build the request yourself from the CommerceHQ API reference. The Make documentation for CommerceHQ lists no numeric limit on these modules, so the practical constraints are the ones of your Make plan: interval, run length and credits. Test the call with Run once before switching the scenario on.
05Should you pick Make or n8n for CommerceHQ?
It depends on the tool your team already knows. Make gives you 21 ready CommerceHQ modules, a visual editor and a Free plan to start testing today. n8n often offers a node for the same app, so check whether it covers the orders, customers and products you care about. Neither tool is better by default: compare the modules each one provides for your exact flow, then build the smallest useful scenario in the one you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations