Resources · Zapier integration

BigCommerce Zapier integrationAutomate BigCommerce with Zapier.

The BigCommerce Zapier integration gives you 11 triggers, 5 actions and 3 searches. Every trigger is instant, so your store reports orders, carts and customers to Zapier as they happen. The catch: BigCommerce is a premium app, so it needs a paid plan.

Premium app Zapier reserves this app to its paid plans.

See the 19 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the BigCommerce Zapier integration actually does

It lets your BigCommerce store start automations on its own. A new order, a cart left behind, a customer who edits an address: each of these events can kick off a Zap, and the Zap can then write back into BigCommerce, create a customer, add a product, publish a blog post or look something up in your catalog.

Three results people build first. A blog that keeps up with the catalog: Product Created feeds Create Blog Post, so a launch gets its announcement without anyone opening the editor. A customer list without doubles: when buyers reach you through another tool, Search Customer with the find-or-create box ticked returns the existing account or creates it, instead of adding the same person twice. Dropped carts someone actually sees: Abandoned Cart hands each left-behind cart to the tool your team already reads, where a person decides what happens next.

Now the limits, because they shape what you can build. Zapier can create in BigCommerce, but it cannot edit an order, change a product or delete anything with a ready-made action. The only way past that is API Request (Beta), which is a raw call to the store and expects you to know what you are asking for. There is also no action that emails a shopper: the abandoned cart trigger tells you a cart was dropped, and sending the reminder is the job of another tool.

If you are weighing platforms, the same store is covered on our BigCommerce Make integration page, and Make vs Zapier sets the two side by side.

Vocabulary

Zapier words, in plain English

Eight terms come back on every line of this page. Read them once and the rest is easy.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts your Zap. Once the Zap is on, Zapier sits and waits for it, for example an order created in BigCommerce.
Action
What the Zap does after it starts: the step that creates, writes or sends something for you, like a new customer record.
Task
What Zapier bills you for: one action your Zap finished successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment it happens. All BigCommerce triggers are instant.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it quietly otherwise.
Search step
A step that looks up something already in an app, such as an existing customer, so the following steps can use what it found.
Connection
Your BigCommerce account linked to Zapier once, then reused by every Zap and every step that talks to the store.
Cost

What a BigCommerce Zap really costs

Two things decide the bill: the plan you are on, and how many actions succeed. The trigger is not one of them.

  • Premium appYes, paid plan or free trial required
  • TriggerNever costs a task
  • Each successful action1 task
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps, no premium apps

BigCommerce is a premium app, which Zapier keeps for paid plans and the free trial. So the free plan (100 tasks a month, two-step Zaps only) is not an option here. On a paid plan, the trigger costs nothing, and checking for new data costs nothing either. Each action that works counts as one task, and a three-action Zap burns three times what a one-action Zap does. An action that fails is not counted. Add a filter or a search and the Zap becomes multi-step, which paid plans allow.

Connect

Connect your BigCommerce store to Zapier

  1. 01

    Open Apps and add a connection

    In your Zapier account, go to the Apps page and click + Add connection. Before you start, make sure you can sign in to the BigCommerce store yourself, with enough rights on whatever the Zap will create.

  2. 02

    Pick BigCommerce

    In the dialog, type BigCommerce, select it, then click Add connection. A new browser tab opens on the BigCommerce side, where the actual sign-in happens.

  3. 03

    Sign in and grant access

    Log in to your store in that tab and allow Zapier to reach the account. From then on, every Zap and every step that uses BigCommerce picks this connection, so you do it once per store.

First Zap

Your first Zap: announce every new product on your blog

GoalEach product you add to the catalog gets a blog post, but only the ones that match your rule.

  1. 01

    Build: pick the trigger

    Create a Zap, choose BigCommerce as the app and Product Created as the event, then select your connection. The lightning bolt next to it confirms the trigger is instant.

  2. 02

    Test the trigger

    Click test. Zapier pulls the three most recent products from your store, so you can pick a real one and map its values in the next steps.

  3. 03

    Add a filter

    Use the plus icon, choose Filter, then in Configure & test set the field, the rule and the value. Pick a text rule for text, a number rule for numbers.

  4. 04

    Add the blog action

    Add BigCommerce again, choose Create Blog Post, and map the product values from the trigger into the post. Test this step and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. Products added from now on are handled, one blog post each; the ones already in the catalog are not.

Triggers

BigCommerce triggers: 11 events, all instant

11 events start a Zap when something happens in BigCommerce, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Abandoned Cart

Instant trigger

In Zapier“Triggers when a cart is abandoned.”

Starts a Zap when a shopper leaves a cart without checking out. You get the cart as a starting point for a recovery workflow, which another tool will have to send.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a fashion shop that wants its customer service team to see dropped carts in their own queue, with a filter keeping only the ones that match its rule.
Watch out
BigCommerce has no action that emails the shopper, so plan the reminder step in a different app.
2

Cart Created

Instant trigger

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

Fires as soon as a cart exists in your store, before any order or payment. It catches intent very early, which also means it fires much more often than an order trigger.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a store testing a new landing page that wants to count how many visitors actually add something to their cart.
Watch out
every cart counts, including the ones that never turn into a sale, so the tasks add up fast on any action that follows.
3

Customer Created

Instant trigger

In Zapier“Triggers when an new customer is created.”

Picks up each new customer account the moment it is registered. It is one of the triggers Zapier highlights for this app, and the natural start of any onboarding flow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a shop that wants each new account passed to the tool where it welcomes new buyers, as soon as the account exists.
Watch out
if the Zap creates customers in the same store it watches, it will set itself off again and again.
4

Customer Address Created

Instant trigger

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

Reacts when a customer saves a new address in their account. That is useful because buyers often add a second shipping address long after signing up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a subscription box business that ships to offices and homes and wants each new address visible to the person planning deliveries.
Watch out
Zapier's own description for this trigger repeats the customer wording, so test it on a real address before relying on it.
5

Order Created

Instant trigger

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

Starts the Zap whenever an order lands in your store. It is the trigger Zapier puts forward first for BigCommerce, and the backbone of most sales workflows you will think of.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a print shop that wants each new order to reach the person who prepares the files, without anyone watching the dashboard.
Watch out
an order placed before the Zap was published is never picked up, so do not expect a backfill.
6

Product Created

Instant trigger

In Zapier“Triggers when an new product is created.”

Fires when you add a product to your catalog. It turns a catalog update into a signal, which is exactly what you need for announcements and for copying products elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a craft brand that publishes a short blog post for every new piece with Create Blog Post, filtered so only finished listings go out.
Watch out
importing a whole catalog at once can trigger Zapier's flood protection, which holds the batch back.
7

Shipment Created

Instant trigger

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

Covers each shipment you create against an order. It is the moment a parcel becomes real, so it suits anything that should happen once goods leave the warehouse.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an electronics retailer whose support team wants a trace of every shipment the day it is created, to answer where-is-my-order questions faster.
Watch out
the trigger follows the creation of a shipment, not its delivery to the buyer.
8

Customer Updated

Instant trigger

In Zapier“Triggers when a customer is updated.”

Fires whenever a customer record changes, whatever the change. Whatever was edited on the account in BigCommerce, the Zap starts each time.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a merchant who keeps a copy of customer details in another tool and wants each correction made in BigCommerce to reach it.
Watch out
a Zap that writes customer data back into the store it watches sets itself off again, so keep its actions away from BigCommerce customers.
9

Customer Address Updated

Instant trigger

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

Runs when an existing customer address is edited. It catches the quiet changes, a new street number or a moved office, that otherwise surface only when a parcel comes back.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a furniture store that delivers with its own vans and wants the route planner to see corrected addresses straight away.
Watch out
a customer who adds a new address rather than editing one fires Customer Address Created instead.
10

Order Updated

Instant trigger

In Zapier“Triggers when an order is updated.”

Reacts to any change on an existing order, not just a status move. Zapier highlights it for this app, and it is the broadest way to follow an order after checkout.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an operations lead who wants every edit on high-value orders logged, with a filter keeping only the ones that match your rule.
Watch out
it fires on every edit, so a busy store can spend a lot of tasks; add a filter to keep only the orders you care about.
11

Order Status Updated

Instant trigger

In Zapier“Triggers when an order status have changed.”

Fires only when the status of an order changes. That makes it narrower than Order Updated, and usually the better choice when your workflow follows the order through its stages.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a store that wants a step to run each time an order moves to a specific status, using a filter on the new status.
Watch out
set the filter on the exact status your next step depends on, as it reads the status reached in this change.
Actions

BigCommerce actions: what Zapier can create

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

1

Create Blog Post

Action

In Zapier“Create a blog post”

Publishes a post on the blog built into your BigCommerce store, filled with whatever earlier steps passed along.

When to use it
turning each new product into a short announcement for shoppers who follow the store blog.
Watch out
review the first posts by hand, because the Zap writes exactly what you mapped, typos included.
2

Create Customer

Action

In Zapier“Create a customer”

Adds a customer account to your store from data another step provides. First Name and Last Name are required, and options cover a forced password reset and the review or abandoned cart email consent.

When to use it
copying buyers from a pop-up shop register into BigCommerce so they can log in online.
Watch out
pair it with Search Customer first, or you will create duplicates.
3

Create Customer Address

Action

In Zapier“Create a customer's address”

Saves an address on an existing customer, which keeps the account ready for the next checkout instead of asking the buyer to type it again.

When to use it
a B2B shop that receives delivery sites by another channel and wants them stored on the right account.
Watch out
the customer must exist first, so a search step usually comes before it.
4

Create a Product

Action

In Zapier“Create a product”

Adds a product to your catalog. The custom fields are mandatory here, and each one wants its names and values separated by commas.

When to use it
adding products listed in another tool to the catalog without retyping them.
Watch out
check how your custom fields are written before mapping them, because both lists must arrive comma-separated.
5

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to BigCommerce using your existing connection. HTTP Method, URL and Stop on error are required, and the URL must point to a domain tied to the app.

When to use it
reaching a part of BigCommerce that none of the four ready-made actions covers.
Watch out
it is in beta and needs some comfort with the BigCommerce API; set Stop on error to Yes if a failure should halt the Zap.
Searches

BigCommerce searches and their find-or-create versions

3 search steps look for data that already exists in BigCommerce, so a later step can use it.

A search step looks inside your store before the next step acts. In the action list, searches sit at the bottom under SEARCH, and some fields offer + Add search step to insert one for you. Each app decides whether its search wants an exact match.

1

Search Customer

SearchFind or create

In Zapier“Search for a registered customer”

Looks for a registered customer in your store and hands the match to the next step. The editor also lists Find or Create Customer, which is this same search with the creation box ticked.

When to use it
checking whether a wholesale buyer already exists before adding them.
Watch out
the search alone creates nothing; only the ticked box makes it add a missing customer.
2

Search Customer Address

SearchFind or create

In Zapier“Search for a customer's address”

Finds an address already saved on a customer. Its twin, Find or Create Customer's Address, adds the address when the search comes back empty.

When to use it
avoiding a second copy of the same delivery site when addresses arrive from another channel.
Watch out
leave the no-result setting on its default if a missing address should stop the Zap.
3

Search Product

SearchFind or create

In Zapier“Search for a product in the catalog”

Searches your catalog for a product so later steps can use its details. Find or Create Product is the same search, set to create the product when nothing matches.

When to use it
making sure a product sent from another tool is not added to the catalog twice.
Watch out
with several matches, the default keeps only the first one, so pick the setting that fits.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that needed it. Switch it on and the Zap goes on without a result.
  2. Create X if it doesn't exist yet?
    Tick it and the search becomes a find-or-create: it drops the setting above and asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on.
When it breaks

When a BigCommerce Zap breaks

Instant triggers remove one classic headache, the wait between checks. The breakages that remain come from data, rights and loops.

Zapier links two help articles to this app, one on common problems with BigCommerce and one on getting started. Below are the cases worth knowing before you build. For a Zap already in trouble, our Zapier troubleshooting page walks through the method.

  • Nothing from before the Zap

    A Zap only reacts to orders, carts and customers that appear after you publish it. Your existing history is never picked up, and moving it is a separate job.

  • The Zap that triggers itself

    Customer Created plus Create Customer on the same store is a loop: each new customer starts the Zap again and burns through your tasks quickly.

  • Bulk imports held back

    A catalog import or a migration can return a huge batch at once. Zapier's flood protection may hold it back rather than run every item.

  • Custom fields without commas

    Create a Product requires Custom Fields Name and Value, separated by commas. A value mapped without them will not land where you expect.

  • API Request pointed elsewhere

    API Request (Beta) only accepts URLs on domains associated with BigCommerce. Any other address is out of reach, so check the URL before you blame the connection.

  • Free plan, premium app

    BigCommerce is a premium app, reserved for paid plans and the free trial. A Zap built on the free plan alone cannot use it, whatever the number of steps.
Need help

Need help automating BigCommerce with Zapier?

A person reads every message.

FAQ

BigCommerce Zapier integration: your questions

01Is the BigCommerce Zapier integration free?
No. BigCommerce is a premium app on Zapier, and premium apps are kept for paid plans and the free trial. The free plan, with its 100 tasks a month and two-step Zaps, does not include premium apps. Once you are on a paid plan, the cost of a BigCommerce Zap comes down to the number of actions that succeed. The trigger itself and the checks for new data are never billed, so a quiet store costs very little.
02How many tasks does a BigCommerce Zap use?
One task per action that completes successfully. A Zap that turns each new product into a blog post uses one task per product. If you add a second action, each product now costs two tasks. The trigger costs nothing, and an action that fails is not counted. Watch the busy triggers: Cart Created and Order Updated can fire far more often than you think, and every run that reaches an action spends from your monthly count. A filter placed right after the trigger is the simplest way to keep that under control.
03Are BigCommerce triggers real time?
Yes, all 11 of them are instant. BigCommerce tells Zapier about each event as it happens, so the Zap starts straight away. The plan interval grid, 15 minutes on Free down to 1 minute on Team and Enterprise, applies only to polling triggers, and this app has none. In the editor, an instant trigger shows a lightning bolt. That type is set by the app and cannot be changed from Zapier, so there is nothing to tune on your side for speed.
04What does it take to connect BigCommerce to Zapier?
A paid Zapier plan or a trial, since BigCommerce is a premium app, and a login on the store with rights on what the Zap will create. Then the steps are short: open the Apps page, click + Add connection, pick BigCommerce, click Add connection, sign in on the tab that opens and grant access. The connection is saved once and reused by every Zap that touches the store. Once it is connected, testing a trigger brings back the three most recent items from the store, which is a quick way to check the link works.
05Why does a BigCommerce product Zap fail on custom fields?
Because Create a Product treats Custom Fields Name and Custom Fields Value as required, and both expect their entries separated by commas. If the previous step sends one long value, or an empty one, the product is not created as planned. Test the action on a real product, read what came back, then adjust the mapping. Remember that a failed action is not counted as a task, so testing a few times does not eat into your plan.
06What if the BigCommerce action you need does not exist?
Use API Request (Beta). It sends a raw request to BigCommerce with the connection you already set up, which covers the parts of BigCommerce that the four ready-made actions leave out. It asks for an HTTP method, a URL on a domain tied to the app, and a Stop on error choice. It is a beta and expects some knowledge of the BigCommerce API, so it is worth testing on a copy of real data first.
07Zapier, Make or n8n for BigCommerce?
Choose by criterion rather than by reputation. On Zapier, the facts for this app are clear: 11 instant triggers, 5 actions, 3 searches, a paid plan because BigCommerce is a premium app, and one task per successful action. So the questions to ask each platform are the same: does it react to the store events you need, which actions can it write back, how does it count a run, and who on your team will maintain the workflow. Line those answers up for your own volume of orders and carts before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations