Update 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
Status status	options	Optional	Status. Options: Pending, Processing, On Hold, Completed, Cancelled, Refunded
Customer Note customer_note	string	Optional	Customer Note

Sample request

{
  "order_id": "e.g. 1001",
  "status": "{{trigger.status}}",
  "customer_note": "{{trigger.customer_note}}"
}

Returns

{
  "id": 1001,
  "status": "completed"
}

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

FAQ

Questions about Update Order.

What does the Update Order action do in WooCommerce?

Updates a WooCommerce order: status (e.g. mark as completed/refunded), shipping address, customer notes, or meta. The standard hook to push status from your fulfillment system back into Woo.

What inputs does Update 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 Update Order support batch operations?

Yes. Run Update 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