WooCommerce
Manage products, orders and customers on a WooCommerce store.
About
WooCommerce ships in the w6w first-party pack. It declares 13 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.woocommerce- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments
Overview
WooCommerce turns a WordPress site into a store, and this app manages the products, orders and customers behind it. Create, read, update, delete and list products and orders, and create, read and list customers — the core catalog and fulfillment data a workflow needs to act on.
Since every WooCommerce store lives on its own WordPress domain rather than one shared host, each connection carries its own store URL, so the same actions work against any self-hosted install. Deleting a product or order defaults to permanent removal, with the option to move it to trash instead when that’s the safer choice.
A fit for syncing orders into a fulfillment or accounting system, updating stock or pricing from another source, or creating a customer record the moment someone signs up elsewhere — the everyday store operations a workflow can handle instead of a person in the WordPress admin.
Build with WooCommerce
Three routes to the same 13 actions. The Workflow tab is generated from WooCommerce's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Order
order-delete Delete an order. Defaults to a permanent delete (`force`); unset to move to trash.
Delete Product
product-delete Delete a product. Defaults to a permanent delete (`force`); unset to move to trash.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying WooCommerce's real ids.
{
"manifestVersion": "2",
"name": "woocommerce-example",
"steps": [
{
"id": "customer-create",
"uses": {
"app": "io.w6w.woocommerce",
"action": "customer-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"email": "<email>"
}
}
]
}Here are some of the things you can do
-
Create Customer
performcustomer-create -
Get Customer
readcustomer-get -
List Customers
readcustomer-get-many -
Create Order
performorder-create -
Get Order
readorder-get
+8 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for WooCommerce, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to WooCommerce. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "order-create",
payload: {
// status: "<value>",
// currency: "<value>",
// customerId: "<value>",
// customerNote: "<value>",
// paymentMethod: "<value>",
// paymentMethodTitle: "<value>",
// setPaid: "<value>",
// billing: "<value>",
// shipping: "<value>",
// lineItems: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action order-create --payload '{}'Give an AI agent WooCommerce — without giving it WooCommerce's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.woocommerce#customer-create",
"input": {
"email": "<email>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's WooCommerce connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
WooCommerce's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. WooCommerce itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
WooCommerce declares its own checks, so its health is a property of the app rather than something the host guesses at.
WooCommerce platform status
API quota headroom
Store reachable
Unauthenticated `GET /wp-json/` against this connection's store — proves the host resolves AND that the WordPress REST API WooCommerce rides on is enabled.