Resources · Make integration

BigCommerce Make integrationAutomate BigCommerce with Make.

What if every order, cart and customer change in your store could start a task on its own? The BigCommerce Make integration gives you 24 modules, 11 of them instant triggers. This guide is for store owners who are new to Make: connect your store, then build a first scenario.

Try the BigCommerce integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BigCommerce Make integration automate?

The BigCommerce Make integration links your store to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. BigCommerce tells Make when a cart, customer, order, product or shipment changes, and Make can create, update, look up or delete customers and products in return.

Follow up on carts that were left behind. Watch Abandoned Cart starts a scenario the moment a shopper walks away from a cart, so you can pass that cart to your email or messaging tool while the purchase is still fresh.

Keep the catalog in step with your source of truth. If products live in a spreadsheet or supplier file, Create a Product and Update a Product write them into the store, and Search Products checks what already exists before anything is added twice.

Tell the right people when an order moves. Watch Updated Order Status fires when an order changes status, which is the cleanest signal for warehouse, support or finance to act on.

The listed modules do not create or edit orders, carts or shipments; they only watch them. For those, Make an API Call reaches the rest of the BigCommerce API with the same connection. If you are also weighing n8n, read our n8n vs Make page, and if a run fails, Make troubleshooting walks through the usual causes. To go further on your own, Make training covers the editor step by step.

Connect

How do you connect BigCommerce to Make?

  1. 01

    Create API credentials in your store

    In the BigCommerce control panel, open Settings, then API Accounts, and click Create API Account. Choose the OAuth option and paste the callback URI https://www.integromat.com/oauth/cb/bigcommerce. Keep the Client ID and Client secret shown on screen.

  2. 02

    Copy your Store Hash

    Look at the address bar of your browser while you are in the store control panel. The Store Hash is part of that URL. Copy it next to the Client ID and Client secret: Make asks for all three.

  3. 03

    Add the connection in Make

    In your scenario, add a BigCommerce module and click Create a connection. You can give it a name in Connection name, then paste the credentials or follow the on-screen instructions. The connection is saved once and reused by every BigCommerce module.

First scenario

Build your first scenario with BigCommerce

GoalWhen a new contact lands in another app, Make creates the matching customer in BigCommerce.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. Pick the app that holds your new contacts, such as a form or a sheet, and connect it as its own module asks.

  2. 02

    Add Create a Customer

    Click the + on the right of that first module, search for BigCommerce and choose Create a Customer. Click Create a connection and paste the credentials from your store.

  3. 03

    Map the contact data

    Fill the fields Make shows for the new customer by clicking into each one and picking the matching value from the first module. Each contact that flows through is a bundle, one item passed from module to module.

  4. 04

    Test with Run once

    Click Run once, then add a test contact in the source app. Open the bubbles above each module to read the bundles, and check in BigCommerce that the customer now exists.

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module with Scheduling. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Switch the scenario on and it keeps working without you.

Triggers

BigCommerce triggers: what starts a scenario

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

BigCommerce1Watch Abandoned Cart

Watch Abandoned Cart

Instant trigger

In Make“Triggers when a cart is abandoned.”

Gets you a second chance at a sale: the scenario starts with the cart a shopper left behind, ready to hand to a reminder or a sales follow-up.

How it fires
instant. BigCommerce calls Make through a webhook as soon as the cart is abandoned, and the scenario processes that cart as one bundle.
When to use it
you want to reach shoppers who got close to checkout and stopped, through a tool you already use for email or messages.
Watch out
the BigCommerce module only reports the cart. Sending the reminder is the job of the next module, from another app.
BigCommerce2Watch New Cart

Watch New Cart

Instant trigger

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

Lets you see demand forming before any order exists, because the scenario receives each cart the moment a shopper starts one in your store.

How it fires
instant. The store alerts Make by webhook as soon as a cart is created, with no polling interval to wait for.
When to use it
you want a log of carts in a sheet, or you track which products get added first during a launch.
Watch out
carts are far more frequent than orders, and each run spends operations, the unit Make counts on your plan. Pick Watch Abandoned Cart if only lost carts matter.
BigCommerce3Watch New Customer

Watch New Customer

Instant trigger

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

Puts every new account holder into the rest of your stack without retyping: the scenario receives the customer record right after it is created in BigCommerce.

How it fires
instant. BigCommerce sends a webhook to Make the moment the customer is created.
When to use it
you add new customers to your CRM or newsletter tool, or you post a welcome message to a sales channel.
Watch out
if a scenario of yours also uses Create a Customer, every customer it adds fires this trigger too. Keep those two in separate scenarios with a clear role each, so you know which run did what.
BigCommerce4Watch New Customer Address

Watch New Customer Address

Instant trigger

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

Gives you each new shipping or billing address as soon as a customer saves it, so delivery and invoicing tools start from the same data as the store.

How it fires
instant. BigCommerce notifies Make by webhook when the address is created.
When to use it
your carrier software or accounting tool keeps its own address book and you are tired of copying addresses by hand.
Watch out
this trigger is about new addresses only. An address that a customer edits later arrives through Watch Updated Customer Address, so add both when your address book must stay complete.
BigCommerce5Watch New Order

Watch New Order

Instant trigger

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

Turns each purchase into an action somewhere else: the scenario starts with the new order as soon as it is placed on the storefront.

How it fires
instant. BigCommerce calls Make through a webhook right after the order is created from the storefront.
When to use it
a new order should add a row to your sales sheet, ping the team channel or open a task for fulfillment.
Watch out
the official description speaks of orders created from the storefront. If your team also keys orders in by other routes, test with Run once before counting on this trigger for them.
BigCommerce6Watch New Product

Watch New Product

Instant trigger

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

Spreads each new catalog item to your other channels without anyone copying it: the product reaches the scenario right after it is created.

How it fires
instant. BigCommerce pushes a webhook to Make as soon as the product exists in the store.
When to use it
a new product should be announced to the team, added to a price list or prepared for a social post in another tool.
Watch out
a scenario that runs Create a Product also sets this trigger off. When one scenario feeds the catalog and another listens to it, name them clearly to follow what started each run.
BigCommerce7Watch New Shipment

Watch New Shipment

Instant trigger

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

Keeps customers and support informed the moment a parcel leaves, because the scenario receives each shipment as soon as it is created in the store.

How it fires
instant. BigCommerce calls Make by webhook when the shipment is created.
When to use it
you send your own shipping message from an email tool, or support needs a line in a shared sheet for every parcel sent.
Watch out
there is no module to create or edit a shipment from Make. This trigger only reads shipments; changing one goes through the store or through Make an API Call.
BigCommerce8Watch Updated Customer

Watch Updated Customer

Instant trigger

In Make“Triggers when a customer is updated.”

Keeps your other tools in sync whenever a customer record changes in BigCommerce, so nobody works from an old email or name.

How it fires
instant. BigCommerce notifies Make by webhook as soon as the customer is updated.
When to use it
your CRM or mailing list must mirror the store after a customer edits their account or your team corrects it.
Watch out
do not follow this trigger with Update a Customer on the same record. The update made by the scenario can fire the trigger again, and the scenario ends up feeding itself.
BigCommerce9Watch Updated Customer Address

Watch Updated Customer Address

Instant trigger

In Make“Triggers when a customer address is updated.”

Catches every address change right away, which saves a parcel from going to a place the customer already left.

How it fires
instant. The store alerts Make through a webhook as soon as an existing address is updated.
When to use it
your carrier or invoicing tool holds a copy of each address and must follow the customer's edits.
Watch out
it only sees edits to addresses that already existed. Pair it with Watch New Customer Address in a second scenario if the copy of your address book must also receive new entries.
BigCommerce10Watch Updated Order

Watch Updated Order

Instant trigger

In Make“Triggers when an order is updated.”

Passes on any change to an order, which is what you need when another system keeps its own copy of your orders and must stay accurate.

How it fires
instant. BigCommerce sends a webhook to Make each time an order is updated.
When to use it
an order sheet or accounting tool needs the latest version of each order, whatever part of it changed.
Watch out
this trigger reacts to every kind of update, so it runs more often than you may expect. If only the status matters to you, Watch Updated Order Status is the tighter choice.
BigCommerce11Watch Updated Order Status

Watch Updated Order Status

Instant trigger

In Make“Triggers when the order status has changed.”

Starts work at each step of an order's life, since the scenario runs only when the status of an order changes.

How it fires
instant. BigCommerce calls Make by webhook as soon as the order status has changed.
When to use it
the warehouse should hear about orders ready to pack, or finance about refunds, without watching the dashboard.
Watch out
every status change starts a run, including the ones nobody needs to hear about, and each run spends operations. Check with Run once which statuses your store actually sends before wiring the next modules.
Modules

BigCommerce modules: what Make can do in your store

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

BigCommerce1

Create a Blog Post

Action

In Make“Creates a new blog post.”

Publishes content to your store blog from another tool, so writers never need access to the BigCommerce control panel.

When to use it
articles are drafted and approved in a document or a sheet, and the approved ones should land on the store blog without copy and paste.
Watch out
no module updates or deletes a post afterwards. Test with Run once on a sample before you switch the scenario on.
BigCommerce2

Create a Customer

Action

In Make“Creates a new customer.”

Adds a customer account to your store from data that starts somewhere else, like a trade show list or a B2B signup form.

When to use it
a new contact should be able to log in and order without your team creating the account by hand.
Watch out
place Search Customers before it when the same person may already exist, or the scenario may try to add them a second time.
BigCommerce3

Create a Customer Address

Action

In Make“Creates a new address for the selected customer.”

Attaches an extra address to a customer who already exists, so repeat buyers find their delivery details ready at checkout.

When to use it
a B2B client sends you a new site or branch address, and it should appear on their account in the store.
Watch out
the address needs a customer to belong to. Get that customer first, from a trigger or from Search Customers.
BigCommerce4

Create a Product

Action

In Make“Creates a new product.”

Adds items to your catalog from a spreadsheet, a supplier feed or a product tool, without filling the product form in the control panel.

When to use it
a new range is ready in a shared sheet and each row should become a product in BigCommerce.
Watch out
run Search Products first on the same reference, so a second run of the scenario does not add duplicates.
BigCommerce5

Delete a Customer

Action

In Make“Deletes the selected customer.”

Removes a customer account from the store as part of a scenario, which is useful when erasure requests arrive through another tool.

When to use it
a customer asks to close their account through your support tool, and the store should follow once the request is approved.
Watch out
there is no undo. Test on a dummy customer with Run once and feed this module one exact customer, never a broad search.
BigCommerce6

Delete a Product

Action

In Make“Deletes the selected product.”

Takes a product out of your catalog automatically, for example when a supplier drops an item or a product line ends.

When to use it
your supplier list marks a reference as discontinued and the store should stop showing it.
Watch out
a deleted product cannot be brought back from Make. If you may sell it again, Update a Product is the safer path.
BigCommerce7

Get a Product

Action

In Make“Returns information about the selected product.”

Fetches the full record of one product you already know, so later modules can use its details in a message, a sheet or a document.

When to use it
a trigger hands you a product and you need its complete information before the next step.
Watch out
it works on one product you select. When you do not know which one yet, Search Products is the module that finds it.
BigCommerce8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the BigCommerce API to your scenario, using the connection you already set up, so you are not limited to the listed modules.

When to use it
you need to create or change orders, carts or shipments, which no listed module does.
Watch out
this module expects you to know the endpoint to call. Read the BigCommerce API documentation for the request before you build it.
BigCommerce9

Update a Customer

Action

In Make“Updates the selected customer.”

Changes a customer record in the store from outside, so one correction made in your CRM reaches BigCommerce too.

When to use it
your CRM is the reference for customer details and the store must follow each change.
Watch out
keep it out of scenarios started by Watch Updated Customer on the same record, or each update can start a new run.
BigCommerce10

Update a Product

Action

In Make“Updates the selected product.”

Edits an existing product from your working file, which keeps descriptions and other details aligned without a trip to the control panel.

When to use it
your product sheet is the master copy and a changed row should reach the matching product in the store.
Watch out
the module needs the product to update. Find it with Search Products first when your sheet does not hold the BigCommerce product.
BigCommerce11

Search Customer Address

Search

In Make“Searches for specific customer addresses, or lists them all.”

Finds the addresses saved in the store, or lists them all, so a scenario can check what already exists before adding anything.

When to use it
before Create a Customer Address, to avoid saving the same address twice on an account.
Watch out
a search returns zero, one or several bundles, and each one runs the modules that follow. Plan for the empty case too.
BigCommerce12

Search Customers

Search

In Make“Searches for specific customers or lists them all.”

Looks up customers in your store, or lists all of them, which is how a scenario learns whether someone is already a client.

When to use it
a contact arrives from a form and you want to update the existing account instead of creating a duplicate.
Watch out
listing every customer produces one bundle per customer, and each one counts as operations further down the scenario.
BigCommerce13

Search Products

Search

In Make“Searches for specific products or lists them all.”

Finds products in your catalog, or lists the whole catalog, so later modules can work on the right items.

When to use it
you check whether a reference exists before Create a Product, or you export the catalog to a sheet for a review.
Watch out
no result means no bundle, and the modules after it do not run. Test with Run once on a reference you know.
Need help

Need help automating BigCommerce with Make?

A person reads every message.

FAQ

BigCommerce and Make: common questions

01Is the BigCommerce Make integration free?
Yes. BigCommerce is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your BigCommerce store subscription is separate and is not covered here.
02What do you need to connect BigCommerce to Make?
You need an active BigCommerce store account and API credentials created in its control panel. Under Settings and then API Accounts, create an API account with the OAuth option and the callback URI Make gives in its documentation. Copy the Client ID, the Client secret and the Store Hash, which appears in the store URL. In Make, add a BigCommerce module, click Create a connection and paste them. For a trigger, click Create a webhook first.
03Do BigCommerce triggers in Make react instantly?
Yes. All 11 BigCommerce triggers in Make are instant. The store calls Make through a webhook as soon as the event happens, whether that is a new order, an abandoned cart, an updated customer or a shipment. You do not wait for a polling interval, and a scenario with an instant trigger runs when data arrives. The schedule of the scenario, every 15 minutes by default, matters for scenarios that start with a scheduled module instead.
04What if the BigCommerce module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the BigCommerce API with the connection you already have, which covers what the listed modules leave out, such as creating or editing orders, carts and shipments. You will need the BigCommerce API documentation to write the request. The Make documentation for this app lists no specific limit, and it notes that its content is AI-generated from BigCommerce sources, so verify important details with BigCommerce.
05Should you use Make or n8n for BigCommerce?
It depends on your criteria, not on a winner. On Make, BigCommerce offers 24 modules, including 11 instant triggers and a Make an API Call module for the rest of the API, and it is available from the Free plan. The same app often has an n8n node as well. Compare the two tools on the modules you need, the way you prefer to build and how each counts usage, then test your first scenario on the one that fits.
Same platform

Other docs you might need on this stack.

Browse all integrations