Start free
ActionBigCommerceUpdated June 2026

How do I fetch a BigCommerce order?

Short answer: Drop the "BigCommerce → Get Order" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this actionAll 10 BigCommerce actions
Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Order ID
order_id
stringRequiredThe Order ID assigned by Bigcommerce. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.
Sample request
{
  "order_id": "{{trigger.order_id}}"
}
Returns
{
  "id": 100,
  "status": "Awaiting Fulfillment",
  "customer_id": 42,
  "total_inc_tax": "29.99",
  "billing_address": {
    "email": "buyer@x.com"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Order.

Any of these apps can fire this action as part of a workflow.

Gmail → BigCommerce
1 Gmail triggers
Slack → BigCommerce
13 Slack triggers
Google Sheets → BigCommerce
2 Google Sheets triggers
HubSpot → BigCommerce
18 HubSpot triggers
FAQ

Questions about Get Order.

What does the Get Order action do in BigCommerce?
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.
What inputs does Get Order require?
Required: Order ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if BigCommerce returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Order support batch operations?
Yes. Run Get Order inside a Loop node to process arrays. Tiny Command handles BigCommerce's rate limits automatically so you don't have to throttle manually.
More actions

Other BigCommerce actions.

Action
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.
Action
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.
Action
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.
Action
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.
Action
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.
Action
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.

Send get order from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.

Try for freeRequest a demo