BigCommerce integration

What it does

The BigCommerce integration lets your agency run catalog, order, customer, and brand operations on behalf of your clients without leaving TaskJuice. Connect a client's BigCommerce store once and you can list and mutate products and orders, create brands and customers, and react to store events the moment they happen in the storefront, all from the same workflow that orchestrates the rest of your stack.

Connect a BigCommerce account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose BigCommerce and click Connect.
3. Enter the store hash, the alphanumeric identifier in the control-panel URL (e.g. abc123def from https://store-abc123def.mybigcommerce.com/).
4. Approve the requested API scopes (products, orders, customers, information, content, marketing) when prompted by the BigCommerce install screen.
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access, open the client's BigCommerce control panel, navigate to Settings, then API accounts, and remove the TaskJuice app. See the BigCommerce app authentication guide for the full grant flow.

Triggers

• bigcommerce/order-created fires when a new order is created in the store (BigCommerce store/order/created webhook scope). The activation payload carries the BigCommerce envelope with the order resource ID, store hash, and event timestamp.
• bigcommerce/product-updated fires when a product is updated (store/product/updated scope). Use it to react to price, inventory, status, or metadata changes.
• bigcommerce/customer-created fires when a new customer record is created (store/customer/created scope).

Every inbound POST is authenticated by recomputing HMAC-SHA256 over ${timestamp}.${body} using your app's client secret and comparing the lowercase hex digest with the value BigCommerce sends in the X-BC-Webhook-Signature header, with the matching epoch-millisecond timestamp in X-BC-Webhook-Timestamp. Activations that fail the check are rejected before they reach your workflow.

Actions

• bigcommerce/list-products, bigcommerce/get-product, bigcommerce/create-product, bigcommerce/update-product, bigcommerce/delete-product cover the product catalog through the v3 REST API.
• bigcommerce/list-categories reads the catalog category tree (v3).
• bigcommerce/create-brand adds a new brand to the catalog (v3).
• bigcommerce/list-orders, bigcommerce/update-order cover order lifecycle (v2 orders endpoints).

Known limitations

• BigCommerce rate-limits per store. When a 429 status is returned, TaskJuice surfaces it as a retryable error and respects the X-Rate-Limit-Time-Reset-Ms window so workflows can pace themselves.
• Connections are scoped to a single store hash. To work across multiple client stores, create one connection per store.
• The BigCommerce activation envelope identifies the resource by data.type and data.id only. To work with the full resource record, follow up with the corresponding bigcommerce/get-* action inside the workflow.
• Webhook events fire after store transactions commit, so an event ID may briefly 404 from the corresponding read endpoint until the upstream cache settles.