BigCommerce
BigCommerce product and order operations
BigCommerce is the enterprise-focused alternative to Shopify, often chosen by larger brands that want more control over their templating, headless setups, or B2B-specific features. Ten actions cover the operational core: Create Product, Get Product, List Products, Create Customer, Search Customers, Get Order, List Orders, List Categories, plus the related read endpoints. No triggers today (BigCommerce's webhook system is set up per-store and per-event; native triggers ship in the next release). The integration uses a BigCommerce store API token (generated from your store's API accounts settings). Common patterns: a Stripe Subscription Created creates the matching BigCommerce customer with the subscription tier as a custom field, a Klaviyo segment recalculation triggers a List Orders query for cohort analysis, or a Slack slash command runs Search Customers to look up details mid-conversation. For triggers today, set up BigCommerce's native webhooks (Settings → API → Webhooks) pointing at a Tiny Command HTTP webhook trigger.
Do anything BigCommerce can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Customer | Creates a new customer in BigCommerce with email (dedupe key), name, addresses, customer group. Useful for "B2B account provisioning from CRM → BigCommerce" workflows where pre-creating customers gates self-serve checkout. |
| Create Product | Creates a new product with name, SKU, price, description, categories, weight, dimensions. For high-volume catalog management, prefer the batch endpoint via HTTP action. Optional variants array for products with size/colour options. |
| Get Order | Returns the order by ID with customer, line items, totals, status, shipping/billing addresses. The standard lookup for workflows that received an order ID via webhook and need richer detail before fulfilment. |
| Get Product | Returns a product by ID with all configured fields, current inventory, categories, custom attributes. Useful for "sync product changes to external CDN" or "validate product exists before linking from another tool" workflows. |
| List Categories | Returns the category tree — each category's name, parent, child count, visibility. Useful for resolving category IDs in product-create workflows or for "audit which categories have stale activity" maintenance. |
| List Orders | Paginated orders with filters by status, customer, date range, total. The base query for "this morning, list yesterday's orders" daily-summary digests and for backfill workflows that catch orders missed during webhook downtime. |
| List Products | Paginated products with filters by category, brand, visibility, recently-modified time. For full-catalog syncs to a search index or external storefront, use the recently-modified filter to incrementally pull only changed products. |
| Search Customers | Lookup by partial name, email, company, or customer group. The standard "find before update" pattern for upsert workflows that don't want to create duplicates. |
| Update Order Status | Transitions an order to a new status (e.g., Pending → Shipped, Shipped → Completed). Useful for "external fulfilment provider confirmed shipment → update BigCommerce status" workflows. |
| Update Product | Partial update on a product — change price, inventory, description, categories. For bulk catalog updates, prefer the batch endpoint via HTTP action. Useful for "ERP price update → push to storefront" sync workflows. |
Pre-built BigCommerce workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect BigCommerce once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every BigCommerce field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the BigCommerce integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect BigCommerce to Tiny Command?
What BigCommerce triggers does Tiny Command support?
What BigCommerce actions can I run from a workflow?
Is the BigCommerce integration real-time?
Do I need to write code to use BigCommerce with Tiny Command?
How much does the BigCommerce integration cost?
More e-commerce apps people connect.
Same category as BigCommerce, ordered by how often teams pair them. Hover the carousel to pause.
Do more with BigCommerce.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
