- Integrations
- /
- WooCommerce
- /
- Actions
- /
- Get Customer
ActionWooCommerceUpdated May 2026
How do I fetch a WooCommerce customer by ID?
Short answer: Drop the "WooCommerce → Get Customer" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Customer ID customer_id | string | Required | Customer ID. Example: 25 |
Sample request
{"customer_id": "e.g. 25"}
Returns
{"id": 25,"role": "customer","email": "customer@example.com","billing": {"city": "Anytown","email": "customer@example.com","phone": "555-1234","state": "CA","postcode": "90210","address_1": "123 Main St","last_name": "Doe","first_name": "John"},"shipping": {"address_1": "123 Main St","last_name": "Doe","first_name": "John"},"last_name": "Doe","first_name": "John","total_spent": "149.97","orders_count": 3}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Customer.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Customer.
What does the Get Customer action do in WooCommerce?
Returns a single WooCommerce customer by ID with their addresses, role, and order summary. Used to enrich trigger payloads or to render customer-detail UI.
What inputs does Get Customer require?
Required: Customer 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 Customer support batch operations?
Yes. Run Get Customer 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
Other WooCommerce actions.
Action
Create Coupon
Creates a new coupon in WooCommerce with code, type (percent/fixed_cart/fixed_product), amount, usage limits, and product/category restrictions. Used to generate personalized discounts from a CRM or campaign tool.
ActionCreate Customer
Creates a new customer record in WooCommerce with email, name, billing/shipping addresses, and optional metadata. Used when a customer is provisioned upstream (e.g. by your CRM) and needs to exist in Woo.
ActionCreate Order
Creates a new WooCommerce order with line items, customer, addresses, status, and payment method. Used for back-office orders, draft orders to share with a customer, or migration imports.
ActionCreate Product
Creates a new WooCommerce product with name, type (simple/variable/grouped), prices, SKU, stock, images, and category. Used to mirror catalog from a PIM or another store.
ActionDelete Product
Deletes a WooCommerce product. By default moves to trash; pass force=true to permanently delete. Use the soft-delete path so you can recover from accidents.
ActionGet Order
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.
Send get customer from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.