Skip to content


Troubleshooting Tips

Initial Setup

If you have issues during initial setup a Zap in Zapier, please refer to the Authentication Errors chapter below, or Zapier’s Troubleshooting documentation.

Once You’re Up and Running

Once your initial setup and configuration is completed and your WooCommerce Zapier integrations are running, most of the time if a problem occurs, it will be shown in your Task History screen.

If you experience stopped or halted tasks, please view the task details to decide whether what to do next. For further information, see the Task History chapter.

If it is an error, you can usually find the related information in the your WordPress Dashboard’s Task History screen. From there you can navigate to the actual Resource and inspect its WooCommerce Zapier History box, or you can review the Logs in your WordPress dashboard.

Issues with Zaps

If you are having other problems with a Zap that you have created, we recommend contacting Zapier Support. They are usually the best people to help you with any issues that you have within the Zapier dashboard, Zap configuration and/or behaviour.

General WooCommerce Issues

If you encounter errors or issues in WooCommerce, first visit the WooCommerce Status Screen to identify and troubleshoot errors, or look at the Logs.

If you need further support, please don’t hesitate to Contact Us and send a support request.

Enabling Detailed Logging

To help troubleshoot and identify the exact cause of an issue, our support team may ask you to do the following:

  1. Please go to your WordPress DashboardSide MenuWooCommerceSettings screen → Zapier tab, and then tick the Enable Detailed Logging checkbox and Save changes.

This allows our support team to see detailed information about your store, and will usually help us resolve an issue. interface

Below are some common errors and issues that can occur when you are using the Zap Editor interface.

Authentication Dialogue

When you create your first WooCommerce Zap, you will be asked to choose your WooCommerce account.

The authentication process involves the service connecting to your WooCommerce store using your WordPress username and password.

Please ensure you complete the authentication dialogue window correctly:

  • In the Website URL field, enter the URL to your WooCommerce store’s homepage. Be sure the URL starts with https:// and do not include the trailing slash.
    For example: or
  • In the WordPress Administrator Username field, enter your admin username or email address that you use when logging into the WordPress dashboard.
  • In the WordPress Administrator Password field, enter your WordPress password.

Example Authentication dialog

Authentication Errors

If you encounter an error whilst authenticating, please make a note of the red error message that you see in the Zapier Authentication popup window, and click on the error message below for next steps.

The username and/or password you supplied is incorrect.
This user does not have the correct permissions.
  1. Your WordPress username and password was accepted when authenticating, however your user account does not have the necessary permissions. Specifically, you do not have permission to read WooCommerce webhooks.

    • Refer to WooCommerce’s documentation on Roles and Capabilities.
      • Check for conflicting plugins.
      • If using WordPress multisite, review this FAQ.
      • If you are using any plugins or code that customises user role permissions, ensure that your role can manage WooCommerce webhooks, and has the following capabilities: manage_woocommerce, promote_users, edit_users.
  2. Your website has a security solution or firewall that is blocking authentication attempts. For example, Cloudflare’s Web Application Firewall.

Sorry, you cannot list resources.

WooCommerce accepted your username and password, however there is an issue authenticating with the WooCommerce REST API.

The WooCommerce Zapier plugin is missing or WordPress pretty permalinks may not be configured correctly. 404 File Not Found.

A HTTP 404 (File Not Found) error was encountered when authenticating.

Authentication response starts with a BOM character.

At least one file in your WordPress website has a special byte-order mark (BOM) character character in it. This causes every request to your website to contain a mostly invisible BOM character at the beginning of every response.

This invalid character doesn’t usually cause an issue for web browsers, however, it does cause an issue for apps (such as WooCommerce Zapier) that use the WooCommerce REST API for communicating with your website.

In our experience, the most likely cause is that the offending character is at the very beginning (or end) of your wp-config.php file. Or possibly it is at the very beginning and end of a plugin or theme file that you have installed.

This BOM character article has some suggestions on which text editors you can use to help you find this character. It may also be necessary to temporarily switch to a default WordPress theme and deactivate all plugins (except WooCommerce and WooCommerce Zapier), and then reactivate them one-by-one to determine which one is causing the problem.

These general WordPress/WooCommerce configuration issues need to be solved for WooCommerce Zapier (and other REST API based integrations) to work correctly.

You can test your site with the W3C Internationalization Checker.

Could not interpret the authentication response.

Your WooCommerce store did not respond with valid JSON when authenticating.

Authentication response is missing required information.

Your WooCommerce store isn’t responding as with a valid authentication message.

HTTPS (secure) connection required.
  • Make sure you’re communicating to your WooCommerce store via HTTPS, and the URL you enter starts with https://.
  • If your WooCommerce store does not support HTTPS, please contact your website host or web developer.
Sorry, SSL is not configured correctly.
Unexpected redirect attempt. (30x Errors)

A HTTP redirect was encountered when authenticating.

Error variations:

  • 300 Multiple Choices. Check your Website URL and try again.
  • 301 Moved Permanently. Check your Website URL and try again
  • 302 Found. Check your Website URL and try again.
  • 303 See Other. Check your Website URL and try again.
  • 304 Not Modified. Check your Website URL and try again.
  • 305 Use Proxy. Check your Website URL and try again.
  • 307 Temporary Redirect. Check your Website URL and try again.
  • 308 Permanent Redirect. Check your Website URL and try again.


  • Ensure the Website URL that you entered is correct. It must be the full canonical URL of your WordPress/WooCommerce website’s home (front) page, excluding a trailing slash.
  • Ensure that you don’t have any plugins or custom code that is enforcing a trailing slash on your website URLs.
  • Check for conflicting plugins.
  • Disable any third-party plugins.
Communication error. 400 Bad Request.

If the above suggestions do not resolve your issue, please contact support for further assistance.

If Your Username and Password Are Correct, but You Still Can’t Authenticate

Security Plugins

If you continue to encounter an authentication error, and you are sure your username and password is correct, then it is likely you have a security-related plugin or service on your website that is preventing Zapier from authenticating with your WooCommerce store.

For example, the following security plugins are known to cause issues when authenticating. Please click on one for further details.

Jetpack: Secure Sign On

If you are using Jetpack’s Secure Sign On feature, you will likely be logging in to your website’s dashboard using your email address and password.

In order to successfully authenticate Zapier with your WooCommerce store, you need to use different login credentials:

  1. Log into your WordPress website’s Dashboard (wp-admin).
  2. Go to WordPress DashboardSide MenuUsers -> Profile, which lets you edit your WordPress account.
  3. Make a note of your Username, as you need to use this username when authenticating later.
  4. In the New Password section, generate a new password. Make a note of your new password then click Update Profile to set your new password.
  5. Return to and authenticate again, but instead of using your credentials you will use:
    • Your username from step 3 above.
    • Your password from step 4 above.

Congratulations, you have successfully authenticated your WooCommerce store with Zapier.

You will continue to log into your WordPress Dashboard (wp-admin) using your email address and password, but whenever you authenticate your WooCommerce store with Zapier you will use your WordPress username/password from the above steps.

Jetpack: Protect

If you are using the Jetpack Protect feature, please consult the Jetpack Protect documentation for assistance.

Wordfence Security: Brute Force Protection

You may experience difficulties authenticating if you are using Wordfence’s Brute Force Protection.

If you are unable to authenticate, please go to WordPress DashboardSide MenuWordfenceToolsLive Traffic and review the live traffic logs to identify the specific reason for the failure.

Tip: For busy stores, you may need to use the Show Advanced Filters -> User Agent = Zapier option in order to only see Zapier authentication logs.

Cloudflare: Web Application Firewall (WAF)

If you are using Cloudflare’s Web Application Firewall feature, you will likely need to whitelist the WooCommerce Zapier REST API endpoints.

Please see the WAF documentation and the WooCommerce Zapier developer documentation.

Other security plugins that we have seen cause authentication issues are:

If you are still unable to authenticate, please try temporarily disabling the security plugin(s), then authenticating, and then re-enabling the security feature(s) once you have successfully authenticated.

Two Factor Authentication

If you are using Two Factor Authentication (2FA) when logging in to WordPress, please consult the security plugin’s documentation on how to generate an application-specific password, and use that when authenticating WooCommerce with Zapier:

iThemes Security: Two Factor Authentication

iThemes Security supports using application specific passwords, so when authenticating, please ensure that you use an application specific password rather than your usual password.

Wordfence Security: Two Factor Authentication

Wordfence Security’s Two Factor Authentication feature does not currently support application specific passwords.

In order to successfully authenticate, it is necessary to disable two factor authentication for the user account that you are authenticating WooCommerce Zapier with. Please ensure that the account has a very complex password to help improve security as much as possible.

IP Address Whitelisting

It isn’t usually feasible or practical to whitelist Zapier’s IP addresses, because they use Amazon AWS, which means the authentication attempts come from IP addresses are regularly changing.

Conflicting Plugins

Tip: Check for Conflicting Plugins

Please review the list of conflicting plugins to ensure one of those isn’t causing your authentication issues.

Using Detailed Logging to Determine the Reason for an Authentication Failure

If you still are unable to identify the cause of your authentication issues, please try the following:

  1. Ensure that you have the latest version of WooCommerce Zapier installed.
    You will need to be running version 2.0.2 or newer to complete the following steps.
  2. Enable detailed logging by going to your WordPress DashboardSide MenuWooCommerceSettings screen → Zapier tab, and then tick the Enable Detailed Logging checkbox and Save changes.
  3. Return the to Zap Editor on, and try and re-authenticate.
  4. The authentication attempt will likely fail again, however this time a detailed reason why it failed will be recorded in your WooCommerce logs.
  5. Go to your WordPress DashboardSide MenuWooCommerceStatus screen → Logs tab and select the newest log whose name starts with woocommerce-zapier. Press the View button.
  6. The log should contain an Authentication attempt failed or Authentication validation failed message, along with a detailed reason that should help you determine the problem.

If you are able to solve the issue, that’s great!

If you’re not able to solve the issue yourself, please contact support and be sure to include the red error message from step 3 and the logged error message from step 6.


Please be sure to disable detailed logging once you have successfully authenticated.

Task History

You can see previously sent information to Zapier in the Task History page.

If the task encounters a problem, will be stopped. Zapier can distinguish between different types of problems, and stops affected task(s) automatically.

If the problem prevents not just that specific task, but any later task as well, then the task will be stopped and marked as “Errored.” If repeated errors occur then the corresponding Zap is also disabled.

Alongside the above error, Zapier can stop and mark a task as “Halted” if the problem will not affect future tasks from completing successfully.

Please consult the Troubleshoot Zaps documentation for more troubleshooting tips.


If you need, you can resubmit halted or errored tasks in this page.

You can find more information in the Task History Help page in Zapier.

Errored Tasks

Tasks errors can occur for a wide variety of reasons, but you can always see the exact reason when you open your task history and look the error message. Here is an example of a task error:

Example Errored Task

The most common errors related to the WooCommerce Zapier plugin:

Error message(s) Possible Solution(s)
Coupons are not enabled. Please make sure the feature or plugin is configured correctly on … Please enable Coupons in the WooCommerce Settings by following those instructions.
Subscriptions are not enabled. Please make sure the feature or plugin is configured correctly on … If you want to use the Subscription Resource, install and activate the WooCommerce Subscriptions plugin.
  • Create Resource response parse failed.
  • Update Resource response parse failed.
  • Search Resource response parse failed.
  • List Resource response parse failed.
Your WooCommerce store’s WooCommerce REST API isn’t responding with valid JSON, so your task has been halted.

Once the issue has been resolved, replay your halted task(s).

Halted Tasks

Most of the time when a Zapier task is halted, is the expected behaviour. For example if you use a filter and the incoming data not matches what you filter for.

Another common reasons why a task is halted is that WooCommerce could not perform the specific task on the Resource. Every halted task has a detailed reason that you can refer in the task details page.

For example for the latter, the task will be halted if you trying to create a new coupon with a coupon code that already exists:

Example Halted Task

Example Reason in Halted Task Detail


There are many possible reasons why a Zapier task can’t be completed. The WooCommerce Zapier plugin handles these cases for you to prevent introducing a problem in WooCommerce and always provide a detailed explanation in the task details page.

Zapier Service Outages

From time to-time, the service may have an outage or period of downtime. This can cause delays or occasionally skipped or errored tasks. Please be patient, up until the issue is resolved by Zapier and do not attempt to resubmit data.

If all Zapier services are working normal, you can start collecting information on what data missing.

To identify which data that you need to resubmit, first look the Zapier’s Task History page, and search for any errors. You can replay a task from this page.

If you still have missing data, because of they not arrived to Zapier at all, you can resend them with specific triggers. For further reference see Manually Sending Data chapter.


For the current Zapier service status information, please visit the Zapier Status page.

WooCommerce Store

If you are having any problems in your WooCommerce store, first please ensure that you have updated to the latest version of the WooCommerce Zapier plugin.

Unable to Update the WooCommerce Zapier Plugin

If you are having problems updating the WooCommerce Zapier plugin to the latest version:

  1. Go to your WordPress DashboardSide Subscriptions screen and verify that your account is connected and WooCommerce Zapier license is active.
  2. On your WordPress DashboardSide Subscriptions screen, click the Update button to force a refresh of your account data from
  3. Go to your WordPress DashboardSide MenuUpdates screen, and click the Check Again button to force WordPress to check for updates again.
  4. The WooCommerce Zapier plugin update should now show on the Updates screen. Select it and click Update Plugins to install the update.
  5. If you still encounter problems, disconnect and reconnect your account connection. To do this, go back to your WordPress DashboardSide Subscriptions screen and hover over the Connected to option and click Disconnect. Click Connect and follow the prompts, then retry steps 2-4 above.
  6. If you still encounter problems, please submit a ticket here and choose the Help with my account option so that the support team can assist.

No Data is Being Sent to Zapier

Action Scheduler

WooCommerce Zapier uses Action Scheduler (which is integrated in WooCommerce core) to send data for Triggers.

This means that data is not sent immediately to Zapier. Instead the data is queued to be sent asynchronously in the background.

This helps ensure that your customers don’t experience a slow checkout process, and it also allows the extension to retry sending the data if there is an error communicating with Zapier.

A typical delay is between ten seconds and one minute, but in staging/testing/development environment or sites with extremely low traffic can be much longer.


Updating your WooCommerce to version 4.0 (or newer) will improve queue processing times and reduce delays in data delivery from WooCommerce to Zapier.

The scheduled actions queue is a WooCommerce core feature that needs to be working correctly in order for WooCommerce Zapier to send data to Zapier.

To check for Failed tasks, go to your WordPress DashboardSide MenuWooCommerceStatus screen → Scheduled Actions tab, then click on the Failed filter (if it doesn’t exist, you don’t have failed tasks). There you can search for your Resource by id to confirm if the Resource was sent to Zapier or not in the first place. If you have failed tasks, please copy the log column and include it when you Contact Us and send a support request. Unfortunately, there is no option to resend a failed task. Please see the Manually Sending Data chapter to if you want to resend previously failed data.

On the same screen you can check the Pending tasks by clicking on the Pending filter. Look for tasks with a hook name of woocommerce_deliver_webhook_async. If you have one or more of these with a Pending status, it means that queued trigger data hasn’t been sent yet.

You can manually run Pending tasks from that screen, but if tasks remain Pending then you will need to identify why the Action Scheduler queue isn’t being processed automatically. See the WordPress Cron chapter below for some ideas on how to troubleshoot the issue.

If the problem persists, go to your logs screen and look for any errors in the recent Zapier log. For further information see the Logs chapter.

WordPress Cron

Sometimes your scheduled actions are stays pending for a long time. In this case, you may have a problem with the WP-Cron system.

The Action Scheduler extension uses WordPress’s built-in Cron for scheduling. This means it will only work correctly if your WordPress WP-Cron is working correctly.

The WP Crontrol plugin can help pinpoint cron issues. It tests the WP-Cron spawner on your site and reports the error message if it fails.

Alternatively, you can try to enable Alternative Cron.

If your WordPress installation’s cron system isn’t working correctly, this plugin will not work correctly either.

You can follow these instructions to disable WordPress’ in-built cron and replace it with a dedicated cron job. We suggest running the real cron job every 5 minutes or so (rather than every half hour like the article suggests).

If your data is being sent to Zapier erratically, or if your data is being sent slowly rather than straight away, you have a few options:

  1. Please create a free Pingdom or UptimeRobot account and point it to your store’s front page. This will ensure WP-Cron fires regularly (from every 30 seconds using PingMate to every 5 minutes using UptimeRobot). This is the simplest solution.
  2. Create a manual cron job by following the WP Daily tutorial instructions or this WP Tuts+ tutorial. Please set it to trigger every 10 seconds. This is a more reliable and flexible solution but also more challenging to implement.

For further information, please see this article for some ideas on how to troubleshoot the issue.

Resource Sent with Wrong Status

WooCommerce Zapier uses Action Scheduler (which is integrated in WooCommerce core) to send data for Triggers.

This means that data is not sent immediately to Zapier. Instead the data is queued to be sent asynchronously in the background.

This helps ensure that your customers don’t experience a slow checkout process, and it also allows the extension to retry sending the data if there is an error communicating with Zapier.

A typical delay is between ten seconds and one minute, but in staging/testing/development environment or sites with extremely low traffic can be much longer.

If a Resource status changing during scheduling and actually sending to Zapier, WooCommerce will send the Resource with the new status information to Zapier. Furthermore if you are using the Order status changed or the Subscription status changed triggers, in this case Zapier will receive the same data multiple times.


There is an automatic de-duplication implemented in the Zapier platform, to prevent fire multiple tasks. Please Contact Us if you experiencing the above problem.

“Order Paid” Triggering Twice

There was a bug in previous WooCommerce versions, if you use the PayPal payment processor, the orders are completed twice. This bug was fixed in WooCommerce version 3.8. Please update your WooCommerce to version 3.8.0 or newer.


If you want to validate this WooCommerce bug impacts you, look the affected orders, and in the sidebar look at the bottom of any order notes, you can see the WooCommerce status change is triggered twice. In both cases from “pending payment” to “completed”. Once for IPN, once for PDT.

Manually Sending Data

You can send data manually to Zapier for specific Trigger Rules, but not for all:

Trigger Name Manual Sending Support
Coupon created No
Coupon deleted No
Coupon restored No
Coupon updated Yes
Customer created No
Customer deleted No
Customer updated Yes
Order created No
Order deleted No
Order paid No
Order restored No
Order status changed Yes
Order updated Yes
Product created No
Product deleted No
Product restored No
Product updated Yes
Subscription created No
Subscription deleted No
Subscription renewal failed No
Subscription renewed No
Subscription status changed Yes
Subscription switched No
Subscription updated Yes

For Order status changed and Subscription status changed trigger rules, all you have to do to change the Order or Subscription status in the WooCommerce admin area. If you want to preserve the current status of, we recommend the following process: Disable the corresponding Zap, change the status of the affected items, enable the Zap and change the status back to the current state.


Don’t forget to disable automatic emails in WooCommerce (Side Menu → WooCommerce → Settings screen → Email tab) before you start switching Order or Subscription statuses to avoid alerting customers. Also, keep in mind, customers will not receive emails for their new orders while automatic mails disabled. Try to do in a low sales volume time or put your store in maintenance mode (for example installing a plugin for that).

For all five updated Triggers, all you have to do to edit/change the specific resource.

If you want to keep your WooCommerce store’s data in sync with another system, for triggers that don’t support manually sending data, you will need to enter them in the target system manually.

Troubleshooting REST API Issues

The REST API is how Zapier communicates with your WooCommerce store to send and receive data, so your WooCommerce store’s REST API must be operational and working correctly.

We have listed some of the most common error messages that you may encounter when using WooCommerce Zapier with a WooCommerce store with REST API configuration issues:

  • Authentication response is missing required information.
  • Create Resource response parse failed
  • Update Resource response parse failed
  • Search Resource response parse failed
  • List Resource response parse failed
  • Webhook Subscribe response parse failed.
  • Webhook Unsubscribe response parse failed.
  • Trigger Rule response parse failed.
  • Input Fields response parse failed.

WooCommerce REST API

If your WooCommerce REST API not working correctly, please consult the Getting started with the REST API guide for details on how to verify that your REST API is working correctly.


In order to connect Zapier, you don’t need to install an extra REST Auth plugin, manage REST API keys or Webhooks in your store. The integration automatically handles those for you.

Coming Soon or Maintenance Mode

The most common cause is a simple one: your WooCommerce store isn’t publicly accessible because you have a “Coming Soon” or “Maintenance Mode” plugin active. Please try deactivating it, and ensure that people can view/visit your website without needing to log in to WordPress.

Invalid or Untrusted SSL Certificates

Your website must also have a valid and trusted SSL certificate installed Zapier to communicate with your WooCommerce store.

If you encounter an error message such as certificate verify failed, it usually means that the Zapier service isn’t able to successfully connect to your WooCommerce store because it uses an SSL certificate that was issued from a Certificate Authority that Zapier doesn’t trust.

Please consult this Zapier guide and this Zapier guide for further instructions, and if the problem persists please contact Zapier support for assistance.

Debug Output

WordPress or PHP debug output can render REST API responses invalid, so make sure the WP_DEBUG_DISPLAY constant is set to false in your site’s wp-config.php file:

define( 'WP_DEBUG_DISPLAY', false );
Please see here for more details.

SSL Check Failing

In order for the WooCommerce REST API authentication process to work correctly, your website must be configured to use SSL correctly.

If your status screen shows SSL as red (No), then you will be unable to authenticate your WooCommerce store with Zapier:

SSL Check Failing Example

Often this issue results in one of the following error messages when you authenticate your WooCommerce store with Zapier:

  • Sorry, SSL is not configured correctly.
  • Sorry, you cannot list resources.

Also, if you review your WooCommerce Zapier logs, you will likely see the following error message:

CRITICAL: WooCommerce REST API Basic Authentication was not performed during ping because is_ssl() returned false.

To resolve this issue, you will need to contact your web host and let them know that WordPress core’s is_ssl() function is returning false during WooCommerce REST API requests, and ask them to resolve this for you. Often it is an indication that your website’s SSL/HTTPS configuration isn’t correct.

WooCommerce REST API Authentication

If you are still receiving the Sorry, you cannot list resources. error message after trying the above steps, then this usually means that WooCommerce’s REST API is unable to authenticate using a standard consumer key and secret, which means that WooCommerce Zapier is unable to work as expected.

In order for WooCommerce Zapier to operate correctly, your website must have a working WooCommerce REST API. This is listed in our System Requirements.

You can check whether your WooCommerce REST API authentication mechanism is working by following this documentation which explains how to create a consumer key and secret, and then test if your REST API is working by querying the endpoint to confirm that it returns an HTTP 200 OK response, and not an HTTP 401 Unauthorized response.

If the response is 401, then please review our list of known incompatible and conflicting plugins.

If you are still receiving a 401 response, please use a separate staging/test environment to temporarily switch to a default WordPress theme and deactivate all plugins (except WooCommerce), and then try authenticating to your test environment. If it works, then you can reactivate your plugins one-by-one to determine which one is causing the authentication problem.

If authentication still isn’t working with only the WooCommerce plugin active, then this indicates that WooCommerce core’s built in REST API authentication isn’t working as it should. Please log into your account and submit a support request to the WooCommerce core support team so that they can investigate and identify why WooCommerce core’s REST API query parameter authentication mechanism isn’t working as expected.

Other Resources to Assist With REST API Issues

Here are some other great resources that may also be helpful:

Last update: December 28, 2020