Short answer: Drop the "WooCommerce → List Customers" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Per Page per_page | string | Optional | Per Page. e.g. "10" |
Page page | string | Optional | Page. e.g. "1" |
Email email | string | Optional | Filter by email address |
Role role | options | Optional | Role. Options: All, Customer, Subscriber, Administrator |
Order By orderby | options | Optional | Order By. Options: Date, ID, Name |
{"per_page": "10","page": "1","email": "customer@example.com","role": "{{trigger.role}}","orderby": "{{trigger.orderby}}"}
[{"id": 25,"role": "customer","email": "customer@example.com","billing": {"email": "customer@example.com","phone": "555-1234"},"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.