All integrations
BigCommerce logo

BigCommerce

E-Commerce

Run a BigCommerce store from a workflow: search and edit the catalogue, manage categories and read product variants, place and progress orders, and manage customer accounts and their saved addresses. Connects with a store-level API account, so there is no OAuth app to register.

20 actions

Actions

Steps your workflow can run in BigCommerce.

List productsSearch the store's catalogue. Filter by name, SKU, keyword, type, condition, availability, brand, category, visibility, whether stock is low or gone, and when a product last changed. Returns each product with its prices, stock, categories and identifiers. With no filters at all this is the whole catalogue.
Get productRead one product by its ID: name, description, SKU, every price, stock, dimensions, categories, brand, search identifiers and review totals - plus its images, variants, custom fields and options if you ask for them.
Create productAdd a product to the catalogue: name, type and price, plus SKU, description, stock tracking and level, categories, brand, sale and retail prices, dimensions, barcodes and page metadata. The name and the SKU both have to be unique across the store.
Update productChange an existing product. Only the fields you fill in are sent, so everything you leave blank keeps its current value - which makes this safe for changing one thing, such as a price or a stock level, without restating the rest of the product.
Delete productRemove a product from the catalogue, along with its variants, images and options. BigCommerce has no trash and no restore, so this cannot be undone - hide a product instead by turning off 'Visible in the storefront' with 'Update product'. Orders that already include the product keep their own copy of it.
List product variantsThe variants of one product - the individual combinations of its options that a shopper actually buys. Each has its own SKU, price, weight, image and stock level. A product whose stock is tracked on its variants keeps the real numbers here rather than on the product.
List categoriesThe categories the catalogue is filed under, each with its ID, tree, parent, name, description, visibility and web address. Use it to turn a category name into the numeric ID the product actions file a product under, or to find the tree a new category should go into.
Create categoryAdd a category to the catalogue. Give it a parent to nest it under an existing category, or a tree to put it at the top level - 'List categories' reports both for every category the store already has. Names are capped at 50 characters and categories can be nested eight deep.
Update categoryChange an existing category - its name, description, visibility, position among its siblings, parent or web address. Only the fields you fill in are sent, so everything you leave blank keeps its current value.
Delete categoryRemove one or more categories from the catalogue. Products filed under a deleted category are not deleted with it - they are left uncategorised. This cannot be undone, and at least one ID has to be named: BigCommerce takes these as a filter, so an empty one would not mean 'nothing'.
List customersSearch the store's customers by email, name, company, phone, customer group, ID or when they registered. Returns each customer with their name, email, company, phone, group and notes - and their saved addresses, store credit and attributes if you ask for them.
Create customerAdd a customer account to the store, optionally with a saved address. The email address is their sign-in and has to be unique across the store. A saved address needs a street, a city and a two-letter country code together, or none of them at all.
Update customerChange an existing customer's details. Only the fields you fill in are sent, so everything you leave blank keeps its current value. Saved addresses cannot be changed here - BigCommerce does not accept them on this endpoint, so this action does not pretend to offer them.
Delete customerRemove one or more customer accounts and their saved addresses. Orders they placed stay in the store. This cannot be undone, and at least one ID has to be named: BigCommerce takes these as a filter and answers a filterless delete with a success that changed nothing.
List ordersSearch the store's orders by customer, email, status, payment method, total, channel and when they were placed or last changed. Returns each order with its status, every total, currency, payment method and billing address. What an order is actually for comes from 'List order products' - the 'products' field on an order is a link, not the lines.
Get orderRead one order by its number: its status, every subtotal, tax, shipping and handling figure, the currency it was placed in, the payment method and status, the billing address, and the notes the buyer and staff left. Amounts come back as strings, which is how BigCommerce sends them.
Create orderPlace an order in the store for one catalogue product or one custom item, with a billing address and an optional status. Leave the customer blank for a guest order, which is what a checkout by someone without an account produces. The postcode is the only part of the address BigCommerce insists on.
Update orderChange an order - most often to move it to its next status, such as marking an awaiting-fulfilment order shipped. Only the fields you fill in are sent, which matters here: a BigCommerce order update that restates the line items clears every discount and promotion applied to them, so this action never touches them.
List order productsWhat an order is for: every line on it, with the product it points at, its name and SKU, the quantity, the price with and without tax, any discount applied, and how much of it has been shipped or refunded. This is the only way to read an order's lines - the 'products' field on the order itself is a link to this.
Get store informationThe store's own settings: its name, domain, status, country and timezone, the currency and how amounts are formatted, the weight and dimension units the catalogue is measured in, the plan it is on, and its default channel. Two of these decide how the other actions behave - 'is_price_entered_with_tax' says whether a price you send includes tax, and 'default_channel_id' is the channel an order lands on.

Connect in a few clicks

Authenticate once and every action and trigger for the app is ready to drop into a workflow. No glue code, no maintenance.

Automate across your stack

Chain apps together with triggers, actions, and logic that move data between your tools automatically, so work happens without you.

Secure by default

Credentials are encrypted and scoped per workspace. Connect the tools your team already trusts with confidence.

Automate BigCommerce with Lodol.

Connect BigCommerce and build your first workflow in minutes. No credit card required.

Free plan available · No credit card required