Skip to main content

WooCommerce orders

WooCommerce Review Request Automation Setup

WooCommerce can already send a webhook whenever an order changes. From Pro, StoryProof gives every automation an inbound URL to receive one, and its ready-made purchase flow turns a new order into a review request a week later. No extra WordPress plugin is involved.

  • The webhook screen under WooCommerce Advanced settings
  • Order topic choice, and why updates fire more than once
  • Delivery logs on both ends for when nothing arrives

Store checklist

One WooCommerce webhook, one StoryProof automation

WooCommerce items follow WooCommerce’s webhook documentation. Do the StoryProof group first so you have a URL to paste.

StoryProof side
WooCommerce side
Confirm

Ticks are local to your browser and nothing is uploaded.

The problem, solved

Why store owners give up on review emails

  • Problem 1

    Another plugin is the last thing we need

    Every plugin adds updates, conflicts and load to a WordPress store.

  • Problem 2

    Buyers are asked before delivery

    An email on the day of the order asks about a parcel that is still in a warehouse.

  • Problem 3

    Order updates fire again and again

    Processing, completed, refunded: an update topic calls the URL for each one.

  • Problem 4

    The webhook switched itself off

    WooCommerce disables a webhook after more than five failed deliveries in a row.

  • Problem 5

    Good reviews never reach the store

    Reviews collected by email often sit in an inbox.

Direct webhook or through Zapier

WooCommerce fields from its webhook documentation; Zapier and Make settings from their help, read 2026-11-18.
QuestionWooCommerce webhook directZapier or Make in between
Extra costNone beyond StoryProofA Zapier plan with webhooks, or a Make account
Custom headersNot offered on the webhook screenYes, set in the POST step
Choosing fieldsWooCommerce sends the whole orderYou map only email and name
Filtering to completed ordersNot on the webhook itselfA filter step before the POST

In StoryProof

Build it in five steps

Step 1 of 5

Create the automation

Use the purchase template or an inbound webhook trigger, a wait and a review request.

Before you start

Read before switching it on

  • Not product reviews

    Replies arrive in StoryProof as testimonials. They are not WooCommerce product reviews and do not appear under products unless you embed a widget.

  • The token may force a detour

    WooCommerce cannot add custom headers. If the automation needs the token in a header, route through Zapier or Make.

  • Whole orders are sent

    A direct webhook sends the full order to StoryProof. Use the Zapier route if you want to send only email and name.

  • Check field names on your store

    This page does not list payload fields. Your sample order shows them.

  • Docs as of today

    WooCommerce, Zapier and Make steps follow their documentation as of 2026-11-18 and were not clicked through on a live store.

FAQ

Questions people ask

Short answers to what usually comes up next.

Which order topic should I choose?

A creation topic gives one call per order and fits the ready-made purchase flow. An update topic lets you react to completion but calls on every change.

What is the ping when I first save?

WooCommerce sends a ping to the delivery URL the first time a webhook is saved as Active. Check the automation log to see how it was handled.

Why did my webhook become Disabled?

WooCommerce disables a webhook after more than five consecutive failed deliveries. Fix the cause, then set it back to Active.

Is there anything to install on the WordPress side?

Not for collection. The widget that shows testimonials on product pages is a separate embed.

Still have a question? Ask the StoryProof team or book a demo.

Ask every WooCommerce buyer, without a plugin

Create the automation, paste its URL into a WooCommerce webhook, and let orders do the rest.

Sources

  1. Webhooks, WooCommerce Documentation. Checked 2026-11-18.
  2. Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.
  3. HTTP app, Make. Checked 2026-11-18.

Last updated 2026-11-18.