Governed ability
List WooCommerce customers
aafm/wc-list-customers Read only
Lists WooCommerce customers with their id, email, name, username, order count, and total spent. Customer email is returned in full under the Integrations security disclaimer. Requires the manage-WooCommerce capability.
How it is governed
The same model as every ability in the plugin, stated for this one.
- Off until you enable it
Like every ability, List WooCommerce customers ships switched off. You turn it on one at a time, and an update never widens access on its own.
- Reads only
It reads data and returns it to your client. Nothing on your site is created, changed, or removed.
- Capability gated
A connection only sees List WooCommerce customers if the user you connected can run it, and the plugin checks that capability again before it executes.
- Every call audited
The call is written to the log in your own database, denials included, with the argument keys but never the values.
See it in action
An illustrative run. Your real calls and data stay on your own site.
Try it with a prompt
Example requests you could paste to your agent.
List the store customers with their names, order counts, and total spent.
Show me all WooCommerce customers along with their email addresses.
Who are our customers, and how much has each one spent?
These are illustrative example prompts. The agent runs them as the user you connected, checked against that user's capabilities and written to your audit log.
Frequently asked
Short answers for List WooCommerce customers.
Does this return customer email addresses?
Yes. Customer email is returned in full under the Integrations security disclaimer, which is why the ability can reach personal data and stays off until an administrator enables it.
How is access controlled?
The caller must hold the manage WooCommerce capability, and every call is written to the audit log by ability name and argument keys, never the returned values.
Governed by default, from the first call.
List WooCommerce customers is off until you enable it, scoped to the user you connect, and logged like everything else. Turn on only what you need.
Every ability off until you enable it, capability-gated on every call.