WooCommerce integration

What it does

The WooCommerce integration runs ecommerce automations for any client whose WooCommerce store you manage. Connect a store once, then route new orders into fulfillment, update order status when a shipment leaves, keep prices and stock in sync, onboard customers, mint coupons, issue refunds, and pull sales reports. Sixteen store events start workflows the moment they happen.

Connect a WooCommerce store

1. In the store's WordPress admin, open WooCommerce -> Settings -> Advanced -> REST API and click Add key. Give it a description such as "TaskJuice", pick a user who is a Shop Manager or Administrator, set Permissions to Read/Write, and click Generate API key.
2. In TaskJuice, add a WooCommerce connection from any WooCommerce node.
3. Enter the store URL including https:// and without a trailing slash, for example https://shop.example.com. The store must be served over HTTPS.
4. Paste the Consumer key (starts with ck_) and the Consumer secret (starts with cs_). WooCommerce shows the secret only once, so copy it before you leave the page.
5. If you plan to use triggers, fill in Webhook secret too (see below). Actions work without it.

You can revoke or rotate the key from the same REST API page at any time.

Set up triggers

WooCommerce webhooks are created in the store admin, one per event. For each trigger you use:

1. Add the trigger to a workflow and copy the incoming webhook URL it shows.
2. In WordPress, open WooCommerce -> Settings -> Advanced -> Webhooks and click Add webhook.
3. Set Status to Active, pick the matching Topic (for example Order created), and paste the URL into Delivery URL.
4. Type a Secret. Use the same secret on every webhook you point at TaskJuice, and paste it into the connection's Webhook secret field. TaskJuice checks every delivery's X-WC-Webhook-Signature against it and refuses any delivery that does not match.
5. Click Save webhook.

When you save an active webhook, WooCommerce sends an unsigned test ping. TaskJuice cannot verify it and refuses it, so WordPress may show "Delivery URL returned response code: 401". That message is expected. The webhook is saved, and real signed deliveries go through.

Triggers

• Order Created, Order Updated, Order Deleted, Order Restored. Order Updated also fires on status changes and refunds.
• Product Created, Product Updated, Product Published, Product Deleted, Product Restored.
• Customer Created, Customer Updated, Customer Deleted.
• Coupon Created, Coupon Updated, Coupon Deleted, Coupon Restored.

Deleted triggers carry only the record id, because that is all WooCommerce sends for a deletion. Use a Get action downstream if you need more.

Actions

• Products: list, get, create, update, delete, and batch create/update/delete.
• Product variations: list, get, create, update, and delete.
• Product categories, tags, and attributes: list, create, update, and delete. Categories and attributes also have get, and attributes have a batch action.
• Attribute terms: list, get, create, update, delete, and batch.
• Product reviews: list, create, update, and delete.
• Orders: list (filter by status, customer, date, or search text), get, create, update (including status), delete, and batch.
• Order notes: list, get, create, and delete.
• Refunds: list store-wide, plus list, get, create, and delete on an order. Creating a refund can return money through the payment gateway.
• Customers: list (filter by email or search text), get, create, update, delete, and batch.
• Coupons: list (filter by code), get, create, update, delete, and batch.
• Reports: sales, top sellers, and order totals.
• Payment gateways: list.

To find a record, use the matching List action with a filter: SKU or search text for products, email for customers, code for coupons, search text for orders. Pickers let you choose products, variations, categories, tags, attributes, terms, orders, customers, and coupons by name instead of pasting IDs.

Known limitations

• Triggers need one webhook per topic, created by hand in the store admin. TaskJuice does not register them for you yet.
• Every webhook pointed at TaskJuice must use the same secret, the one saved on the connection.
• WooCommerce does not retry failed deliveries, and it disables a webhook after repeated failures. Re-enable it from the Webhooks page if a trigger goes quiet.
• List actions return at most 100 records per page.
• HTTP Basic authentication only works over HTTPS.
• What the key can do is limited to the WordPress user it was generated for. Coupons, refunds, and reports need a Shop Manager or Administrator.
• Subscriptions, Memberships, and Bookings are paid extensions and are not covered.