WooCommerce

E-commerce Consumer key and secret

Read and update WooCommerce orders, products and customers from any Windmill script, flow or app.

Set up in 3 steps

Get your credential

In WordPress, open WooCommerce then Settings, Advanced, REST API, and create a key with the permissions your scripts need. Copy both halves — they are shown only once.

Add the resource in Windmill

Open Resources, add a resource of type woocommerce, and fill it in.

Run your first script

Fork any script below and read before writing anything.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Resource type

woocommerce — the shape of the credential every script on this page expects.

View raw schema →

Field	Type	Required	What it is
url	string	Yes	Your Store URL
consumerKey	string	Yes	The consumer key for WooCommerce API authentication
consumerSecret	string	Yes	The consumer secret for WooCommerce API authentication
version	string	No	The version of the WooCommerce API, default is v3
queryStringAuth	boolean	No	When true and using under HTTPS, forces Basic Authentication as query string, default is false

Questions

What is queryStringAuth for?

WooCommerce normally authenticates over HTTPS with Basic auth. Some servers strip that header — turning this on sends the key and secret as query parameters instead.

Calls fail on a plain-HTTP store

Without HTTPS, WooCommerce falls back to OAuth 1.0a signing, which these scripts do not do. Serve the store over HTTPS.

Is my credential stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

Set up in 3 steps

Get your credential

Add the resource in Windmill

Run your first script

Scripts

Get Customer

Create Order

Search Customers

Update Order Status

Create Product

Update Product

Get Order

Create Customer

Resource type

Questions