Four WooCommerce triggers start a run from what happens in your store:

  • WooCommerce · New order — When an order is placed in the store.
  • WooCommerce · Order updated — When an order changes — its status, its items.
  • WooCommerce · New customer — When a customer account is created.
  • WooCommerce · Product updated — When a product is changed.

All four are instant triggers. Publishing makes the webhook in WooCommerce for you, and nothing needs pasting — see How instant triggers work.

Who can do this

Workspace Admins and Editors, on every plan — WooCommerce is not a premium connection. Viewers see the trigger and its status but cannot change it.

Before you start

A WooCommerce connection with a Read/Write key — see Connect WooCommerce. A Read key cannot make webhooks.

Steps

  1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.

  2. Under WooCommerce, select the event — New order, say. It reads WooCommerce · instant. Or type WooCommerce in Search triggers.

  3. In Connection, choose your WooCommerce connection — for example Northwind shop. These triggers have no other settings.

  4. The panel reads Publishing sets this up in WooCommerce, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.

  5. Add the steps, then Publish. Bizomate makes a webhook named Bizomate in your store, for that event. It shows in WordPress under WooCommerce › Settings › Advanced › Webhooks.

    The panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

  1. Make the event happen in the store — place a test order, change an order's status, add a customer or change a product.
  2. When it arrives, the panel reads Listening — instant — Last event 10:45 · New order · #1001 · pending.
  3. On Output, select Use the last event, then Test run.

What the trigger gives

New order and Order updated — the order:

Field What it is
id WooCommerce's id for the order — what Update an order's status and Add an order note take.
number The order number customers see.
status pending, processing, completed and so on.
total, currency The total and its currency — 1499.00, INR.
email, phone, customerName From the billing details — rohan@consulace.com, Rohan Mehta.
paymentMethod The payment method's name.
createdAt When it was placed, in UTC.
lineItems A list, each with name, quantity, total and sku.

New customer: id, email, firstName, lastName, phone, username.

Product updated: id, name, sku, status, price, regularPrice, salePrice, stockQuantity, stockStatus, permalink.

Use them in later steps as {{ trigger.number }}, {{ trigger.email }} and so on.

What happens next

  • Each event starts one run of the live version, in Production, named after it — New order · #1001 · pending, Order updated · #1001 · completed, New customer · rohan@consulace.com, Product updated · Consulace onboarding pack.
  • Every publish sets the webhook up again: Bizomate deletes its old webhook in WooCommerce and makes a new one, with a new secret. A webhook deleted or switched off in WooCommerce comes back the next time you publish.
  • Changing to another trigger and publishing, or deleting the workflow, deletes the webhook in WooCommerce.

How Bizomate knows an event is WooCommerce's

When it makes the webhook, Bizomate gives it a secret of its own making, which WooCommerce uses to sign every event. Bizomate checks each event's signature, and answers one that does not match with 401 — The signature does not match. — and starts nothing. The test call WooCommerce sends when a webhook is made is answered, and starts nothing.

Good to know

  • Events can take a little while. WooCommerce sends webhooks from its own background jobs, which on a quiet site run when someone next visits it. A few seconds is usual; longer is not a fault.
  • Order updated fires for every change to an order, its status included — a new note, a refund, a change of address. Check status with an If step to act on one status only.
  • A new order can also send Order updated as WooCommerce finishes it. Use one of them, not both, for the same job.
  • WooCommerce switches off a webhook after five failed deliveries in a row. Publishing again makes a new one.
  • Each workflow has its own webhook, all named Bizomate. Leave them be in WooCommerce.

If something goes wrong

What you see Why What to do
Not listening — WooCommerce would not take Bizomate's address: WooCommerce refused: Sorry, you are not allowed to create resources. Check the connection's details on Connections. Fix it, then publish again. The key is Read only, or its user cannot manage WooCommerce. Make a Read/Write key for an Administrator or Shop manager, select Reconnect, then publish again.
Not listening — WooCommerce would not take Bizomate's address: WooCommerce refused: Consumer key is invalid. … The key was revoked. Select Reconnect with a new key, then publish again.
Not listening — WooCommerce would not take Bizomate's address: Could not reach WooCommerce: … Fix it, then publish again. The site could not be reached. Check the site is up, then publish again.
Waiting for the first event stays Nothing has happened yet, WooCommerce's background jobs have not run, or the webhook was switched off in WooCommerce. Visit the site to wake its jobs. Check the Bizomate webhook under WooCommerce › Settings › Advanced › Webhooks is Active; if not, publish again.
A run did not start for an event the panel shows The workflow is switched off, or its workspace is archived. Switch it on — see Switch a workflow on or off.