Connect your BigCommerce store to Syncaut to automate product management, order processing, customer operations, inventory updates, and more — all from within your workflows.
Before adding a BigCommerce node to your workflow, you need two things from your BigCommerce store:
An API Access Token
Your Store Hash
Both are found inside your BigCommerce control panel. Keep these safe — treat them like passwords.
Log in to your BigCommerce control panel
Go to Settings → API → API Accounts → Create API Account
Choose V2/V3 API Token
Give it a name (e.g. "Syncaut")
Under OAuth Scopes, enable the following based on what you need:
Orders — Read-Only (or Modify if updating/deleting orders)
Products — Read-Only (or Modify if creating/updating/deleting products)
Customers — Read-Only (or Modify if creating/updating/deleting customers)
Content — Read-Only
Information & Settings — Read-Only
⚠️ Important: If a scope is missing, any action that requires it will fail with a
403 Forbiddenerror. Always double-check your scopes match the actions you plan to use in your workflow.
Click Save — BigCommerce will show your Access Token once only. Copy it immediately as it will not be shown again.
Your store hash is the unique identifier in your API path. You can find it in two places:
On the API credentials page after creating your account — the path shown looks like /stores/abc123xyz/v2/
In your browser URL when inside the control panel: https://store-abc123xyz.mybigcommerce.com
The store hash is the alphanumeric string — for example abc123xyz.
In Syncaut, open your Workspace → Credentials
Click Add Credential
Select BigCommerce as the type
Paste your API Access Token as the credential value
Give it a recognisable name (e.g. "Client Store — BigCommerce")
Save
Your token is encrypted at rest and never exposed after saving.
When adding a BigCommerce node to your workflow, you go through three steps:
Step name — a variable name used to reference this node's output in later steps (e.g. getOrders). Must start with a letter or underscore, no spaces.
Credential — select the BigCommerce credential you added above
Store hash — enter your store hash (e.g. abc123xyz)
⚠️ Make sure the store hash matches the store the credential belongs to. A mismatched store hash will cause a
403 Forbiddenerror even if the token itself is valid.
Choose what you want this node to do. Actions are grouped by resource — Products, Orders, Customers, Categories, and Inventory.
Depending on the action, you will see either filters (for list actions like Get all orders) or a parameter form (for single-record actions like Get order).
Get all products Fetches a paginated list of products from your catalog. Available filters: Per page (max 250), Page, Search keyword, Visibility (Any / Visible / Hidden / Pre-order)
Get product Fetches a single product by ID. Requires productId.
Create product Creates a new product. Requires name and price. Optional: type (physical or digital), weight, description.
Update product Updates an existing product. Requires productId. Optional: price, inventory_level.
Delete product Permanently deletes a product. Requires productId.
Get all orders Fetches a paginated list of orders. You can filter by order status. Available statuses:
0 — Incomplete
1 — Pending
2 — Shipped
3 — Partially Shipped
4 — Refunded
5 — Cancelled
6 — Declined
7 — Awaiting Payment
8 — Awaiting Pickup
9 — Awaiting Shipment
10 — Completed
11 — Awaiting Fulfillment
12 — Manual Verification Required
13 — Disputed
14 — Partially Refunded
Get order Fetches a single order by ID. Requires orderId.
Update order Updates an order. Most commonly used to change order status. Requires orderId. Optional: status_id (use the status IDs listed above).
Delete order Deletes an order. Requires orderId.
Get all customers Fetches a paginated list of customers. Filter by keyword or customer group ID.
Get customer Fetches a single customer by ID. Requires customerId.
Create customer Creates a new customer. Requires first_name, last_name, email.
Update customer Updates a customer. Requires customerId. Optional: first_name, and other profile fields.
Delete customer Deletes a customer. Requires customerId.
Get all categories Fetches all categories from your catalog. No parameters required.
Create category Creates a new category. Requires name. Optional: parent_id — use 0 for a top-level category.
Get inventory Fetches a product including its variant inventory levels. Requires productId.
Update inventory Updates the inventory level of a product. Requires productId and inventory_level. Optional: inventory_warning_level.
You can reference outputs from previous workflow steps inside any parameter field using Handlebars syntax:
{{stepName.data}}
For example, if a previous step named getOrder fetched an order, reference its ID in a later step as:
{{getOrder.data.id}}
Use the variable picker (+ variable) next to each field to insert common variables without typing them manually.
Every BigCommerce node stores its result under the step name you provide. The output structure is:
{
"data": {},
"action": "get_orders",
"storeHash": "abc123xyz"
}
Reference the response data in later steps as {{stepName.data}}. For example, if your step name is fetchOrders:
{{fetchOrders.data}}
403 Forbidden Your API token is missing the required scope for the action. Go to BigCommerce → Settings → API → API Accounts, edit your account, and enable the missing scope. Also verify your store hash belongs to the same store as the token.
Credential not found The credential attached to the node was deleted from your workspace. Re-add it under Workspace → Credentials and update the node.
Invalid Access Token The token is malformed or has been invalidated. BigCommerce tokens do not expire on their own but are invalidated when you regenerate or delete the API account. Create a new API account and save the new token as a credential.
orderId / productId / customerId is required The ID field is empty. Provide the ID directly or reference it from a previous step using {{stepName.data.id}}.
Store not found / 404 Your store hash is incorrect. Double-check it on your BigCommerce API credentials page.
Navigate