Hi @deltacx,
Happy to help with this! The most likely reason Zapier showed no data is a timing issue. When you click “Test” in Zapier on a Catch Hook zap, Zapier opens a short listening window waiting for a new incoming request. If your order was placed before you set Zapier to listen, that payload has already been sent and Zapier missed it. WooCommerce webhooks fire once at the moment the order is created and don’t resend historical events.
To get it working, here’s what to do:
- Go to WooCommerce → Settings → Advanced → Webhooks, click on your webhook, and scroll down to the Recent deliveries section. This shows a log of every delivery attempt, the HTTP response code WooCommerce received back, and the full payload sent. If it shows a 200 response, the webhook fired successfully and the issue is purely on the Zapier side. If it shows a failure code or nothing at all, the webhook isn’t firing correctly.
- On the same page, make sure the webhook status is set to Active and that the delivery URL matches exactly what Zapier provided in the Catch Hook trigger.
- In Zapier, go to your zap, click on the Catch Hook trigger step, and click “Test trigger”. Then go back to WooCommerce and place a test order (you can use a free/zero-dollar product). The webhook will fire on the new order and Zapier should catch it this time.
- To check your webhook logs, go to WooCommerce → Status → Logs. Since you might have many log files, use the dropdown to filter by source – look for webhooks-delivery to see specifically your webhook activity. You can also use the search box to find relevant entries.
Once you have a live payload captured, you’ll be able to map the order data fields to the rest of your zap.
I hope that helps. Let us know if you need anything else.
Thanks. This is getting muddier!
I found webhooks-delivery under logs. I went into today’s log since I had one order earlier today.
The log shows no information relevant to the order. Just that an order was created at a date and time.
I’m trying to get the email, name, what they bought, etc. so I can send them an email. How do I get that information pushed to Zapier?
Thanks.
OK now people are spamming me telling me to hire them to fix this for me.
No. No thank you. And No.
I will spend my day moving my shop to Gumroad. Thanks.
Hi @deltacx,
I can see how this is getting confusing, especially when you’re expecting order details like customer info and products but only seeing minimal entries in the logs. Let’s walk through this together and get you to the point where Zapier receives the full payload.
What you’re seeing in the WooCommerce logs is expected behavior. The webhooks-delivery logs don’t display the full structured order data in a friendly format, they mainly confirm that a webhook event was triggered and whether delivery succeeded. The actual payload with customer email, name, and items is sent to your endpoint, in this case Zapier, but not fully expanded in those logs.
To get the data you need into Zapier, here are the key things to check:
- Confirm webhook topic and status: Make sure your webhook is set to:
– Topic: Order created
– Status: Active
– API version: Use the latest available (this ensures richer payload structure)
- Capture a fresh payload in Zapier: Zapier only catches live events. So:
– Click Test Trigger in your Catch Hook step
– Then place a new test order in WooCommerce
This is critical, older orders won’t resend
- Ensure you are using the correct Zapier trigger: Using Catch Raw Hook is good if you want full data, but it will return raw JSON. After Zapier successfully catches it, you should see fields like:
– billing.email
– billing.first_name
– line_items
– total
If you’re not seeing these, it usually means Zapier hasn’t actually received a proper payload yet
- Check webhook delivery status: Go to: WooCommerce → Settings → Advanced → Webhooks → Your webhook → Recent deliveries
– If you see 200 response → WooCommerce sent the data successfully, focus on Zapier
– If you see errors → there may be an issue with the delivery URL
- Optional deeper inspection: If you want to inspect the raw payload outside Zapier, you can temporarily use a request bin tool like: https://webhook.site
Paste that URL into your webhook, place an order, and you’ll see the full JSON WooCommerce sends
You can also review this guide for more details on how WooCommerce webhooks work:
https://woocommerce.com/document/webhooks/
Once Zapier successfully captures one live order, you’ll be able to map all the fields you need for your email automation.
Let me know what you see after triggering a fresh order while Zapier is listening, happy to help you interpret the payload if needed.
Thank but I just moved my entire shop to Gumroad. I’m done with WooCommerce. Oh and the Gumroad zap I built? Worked the first time.
Exported my customers. Will let all of them know we moved… and why.
Ciao ciao!
Oh, let me mark this as resolved.
Hi @deltacx,
I can absolutely understand how frustrating this whole experience must have felt, especially with things not behaving as expected and then getting unsolicited messages asking you to hire people, that can really take away from trying to focus on solving the issue.
From what you described earlier, your setup was very close, and there is a strong chance the issue may have been on the Zapier side, particularly around how the trigger was listening for a live event. Since WooCommerce webhooks only fire once per event, if Zapier was not actively listening at that exact moment, it would not capture the payload, which often leads to the “no data” situation you ran into.
That said, it makes complete sense that you chose to move forward with a solution that worked immediately for your needs.
If you ever decide to give WooCommerce another try in the future, you are always welcome to reach out here, we will be glad to walk through things with you and help get everything working smoothly without the noise you experienced this time.
Wishing you continued success with your new setup.
