E-commerce integration
BigCommerce integration for AI workflows.
Requires a BigCommerce store-level API account. Act on new orders and move orders through your fulfillment statuses.
In short
Fluxo Flow connects to BigCommerce with an API key or credentials you provide; workflows can get an order, find orders and update order status and more, and start from new order and order status changed. The integration is live.
Live means tested end to end against real accounts. Found a problem? Tell us.
What you can do
Actions and triggers for BigCommerce.
Actions
Get an order
Reads an order with its billing address, totals and status.
Find orders
Finds orders by customer email, status or creation date (newest first).
Update order status
Moves an order to another status (e.g. Shipped, Completed). BigCommerce may email the customer, depending on your store's order notification settings.
Get an order's products
Lists the line items (products, SKUs, quantities, prices) of an order.
Find products
Searches the catalog by keyword (name, description, SKU or brand) or exact SKU.
Find a customer
Finds a customer by email.
Triggers
New order (checked on your plan's schedule interval)
Starts a run for each new order.
Order status changed (checked on your plan's schedule interval)
Starts a run when an order moves to another status (checks orders modified since the last poll).
How to connect
Connect BigCommerce in a minute.
Connects with an API key or credentials, tested before they're saved and encrypted at rest.
- In your BigCommerce control panel, open Settings → Store-level API accounts → Create API account.
- Give it the scopes Orders: modify, Products: read-only, Customers: read-only and Information & settings: read-only, then save and copy the access token and API path.
- Open Settings → Integrations here, click Connect on BigCommerce and paste the API path and access token.
Permissions & limits
What it can access, and how fast it runs.
Permissions requested
Orders: get, find, change status, triggers
Orders: modify (store_v2_orders)
Find products
Products: read-only (store_v2_products_read_only)
Find a customer
Customers: read-only (store_v2_customers_read_only)
Connection check (store name)
Information & settings: read-only (store_v2_information_read_only)
Limits and timing
- Polling triggers are checked on your plan's schedule interval: Basic every 15 minutes, Pro every 5 minutes, Business every 2 minutes, Elite every minute.
- BigCommerce triggers check at most every 5 minutes, whatever your plan, to respect BigCommerce's limits.
- If BigCommerce says to slow down (HTTP 429 or 503), requests wait as told and retry a limited number of times.
FAQ
BigCommerce questions, answered.
Does changing an order status email my customer?
That depends on your store's order notification settings in BigCommerce; Fluxo only changes the status.
Are new orders instant?
No, Fluxo checks for new and changed orders every few minutes.
If an order changes status twice between checks, do I get two runs?
No — one run with the latest status. And if an order goes back to a status it already had, that change isn't reported again.
Is the BigCommerce integration ready to use?
Yes. BigCommerce is live: connect it in Settings → Integrations on any plan, including Free (on Free you can build with it and Dry Run; running it live needs a paid plan).
Can I call BigCommerce endpoints the integration doesn't cover?
Yes, if BigCommerce has an API: save a key in the encrypted credential vault and call it with an HTTP Request step.
Can I test a workflow without touching my real data?
Yes. Dry Run walks through every step with simulated app calls, so nothing is sent until you run it for real or activate its trigger.
Connect BigCommerce to your first workflow.
Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.
Free to explore · No credit card · 30-day money-back guarantee on paid plans