store/get-customer reads one customer: their order count and lifetime spend.
Name, email, username and addresses are withheld unless include_personal_data is set.
At a glance
| Ability | store/get-customer |
| Toolset | WooCommerce — toolset/woocommerce |
| Group | WooCommerce › Customers |
| Requires | WooCommerce, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
“How much has this customer spent” and “who is this customer” are different questions, and the first one is asked far more often. Keeping them separate means the common question can be answered without the personal data leaving the site.
Password hashes, session tokens and payment provider customer references are never returned, with or without the flag. Those are not personal data to be disclosed carefully — they are credentials, and a payment provider customer reference in particular is a key that can be used to charge somebody.
The spend figure counts completed and processing orders, in line with the rest of the suite. Pending and failed orders are not money.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | Customer user ID. |
include_personal_data | boolean | No — defaults to false | Include name, email, username and addresses. |
What comes back
| Name | Type | What it is |
|---|---|---|
customer | object | Order count and total spend, plus identifying fields only when asked for. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
How much has customer 318 spent with us?
It resolves to one call:
{
"ability": "store/get-customer",
"parameters": {
"id": 318
}
}Worth knowing
- Personal fields are off by default.
- Password hashes, session tokens and payment provider references are never returned under any flag.
- Spend counts completed and processing orders only.
Related abilities
- Update Customer — correct their details
- List Customers — the aggregate view
- Export Customers — a formal release of records
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category