WooCommerce to Zapier Not Triggering? Check These 5 Things

You placed an order, but the Zap didn't run and Zapier says it received nothing. To troubleshoot this issue, there are five main checks to perform.

First, verify which setup you have for sending WooCommerce data to Zapier. There are two options: the official Zapier Integration for WooCommerce extension (a paid extension) or a self-created webhook under WooCommerce settings. Both methods use WooCommerce's built-in webhook system, but the official extension creates and deletes webhooks based on Zap usage. The self-created method requires manual management.

Next, check if the webhook is still active. Open WooCommerce settings and look at the Advanced > Webhooks section. Disabled webhooks are automatically deactivated after five consecutive failed deliveries. If a webhook is disabled, any events that happened while it was off will not be resent. To reactivate a webhook, edit it and switch it back to Active. Keep in mind that WooCommerce does not notify you when it disables a webhook, and pending actions can pile up if the cron isn't running.

The second check is to ensure the background queue (Action Scheduler or WP-Cron) is running. WooCommerce schedules a background action called woocommerce_deliver_webhook_async, which sends data to Zapier after the customer's checkout is loaded. Pending woocommerce_deliver_webhook_async actions indicate that data is ready to be sent but hasn't been yet.

You can manually run these actions or check for any failures in the Scheduled Actions section. If pending actions keep accumulating, your cron isn't running, so check the WP-Cron settings or a real server cron job. Additionally, if Zapier shows "rest_api_unavailable," this may be due to WooCommerce's ALTERNATE_WP_CRON feature, which requires removal from wp-config.php.

The third check is to determine if you're testing with a fresh, live event. Some users have reported receiving no data when testing a Catch Raw Hook in Zapier. This is because WordPress sends a webhook only once, when the event occurs, and does not resend old events. If you're experiencing issues, try using a fresh, live event to see if the problem persists.

Finally, ensure the webhook and Zap settings are correctly configured. The official extension documentation states that WooCommerce disables webhooks on its own after repeated consecutive failures, while the self-created webhook requires manual management. Additionally, if the Zap is turned off or cloned to staging, the corresponding WooCommerce webhook will be removed, causing the issue. Regularly check the webhook status, queue, and Zap settings to ensure everything is functioning correctly.