Get Order: WooCommerce action

Inputs

The fields this action accepts.

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

Field	Type	Required	Description
Order ID order_id	string	Required	Order ID. Example: 1001

Sample request

{
  "order_id": "e.g. 1001"
}

Returns

{
  "id": 1001,
  "total": "59.98",
  "status": "processing",
  "billing": {
    "email": "customer@example.com"
  },
  "line_items": [
    {
      "name": "T-Shirt",
      "total": "59.98",
      "quantity": 2
    }
  ]
}

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

FAQ

Questions about Get Order.

What does the Get Order action do in WooCommerce?

Returns a single WooCommerce order by ID with line items, totals, customer, addresses, and order notes. The standard read action after a trigger fires with an ID.

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 WooCommerce 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 WooCommerce's rate limits automatically so you don't have to throttle manually.

More actions