Skip to content

Plugin Compatibility

With thousands of WooCommerce extensions, addons and plugins available for WooCommerce, it can be difficult to know if they are compatible with WooCommerce Zapier.

Below is a list of WooCommerce Extensions that we have tested with WooCommerce Zapier.


If a plugin that you are using isn’t listed below, it doesn’t necessarily mean it is or isn’t compatible. You can always purchase the WooCommerce Zapier extension and use the 30-day money back guarantee to try it for yourself.

Supported Plugins

The following WooCommerce extensions are actively supported by WooCommerce Zapier:

WooCommerce Bookings

Compatibility with the WooCommerce Bookings plugin was added in version 2.2 of WooCommerce Zapier. You must be running at WooCommerce Bookings version 1.15.35 or later.

If you have WooCommerce Bookings installed, you can use Bookings data in your Zaps (Triggers only).

More on how to use Bookings in WooCommerce Zapier.

WooCommerce Subscriptions

Compatibility with the WooCommerce Subscriptions plugin was added in version 1.6 of WooCommerce Zapier. You must be running at WooCommerce Subscriptions version 2.4.3 or later.

If you have WooCommerce Subscriptions installed, you can use Subscriptions data in your Zaps (Triggers and Actions).

More on how to use Subscriptions in WooCommerce Zapier.

Checkout Field Editor

Compatibility with the WooCommerce Checkout Field Editor plugin was added in version 1.1 of WooCommerce Zapier.

Any additional checkout fields added to your store by the WooCommerce Checkout Field Editor plugin will be sent to Zapier , allowing you to use your custom checkout fields in your Zaps that use any Order trigger events.

You may also wish to view the Checkout Field Editor documentation.

Compatible Plugins

Below is a list of WooCommerce extensions that are compatible with WooCommerce Zapier.

Sequential Order Numbers Pro

WooCommerce Zapier is compatible with the WooCommerce Sequential Order Numbers Pro plugin since version 1.1.

If using the WooCommerce Sequential Order Numbers Pro plugin, we recommend using the number data field (not the id data field) in your Zap Triggers. See the Order Data Fields documentation for full details on the number field.

You may also wish to view the Sequential Order Numbers Pro documentation.

WooCommerce Order Status Manager

Custom order statuses are supported, including ones created with the Order Status Manager extension.

We’d recommend using the Order status changed trigger rule, which triggers every time an order changes status (including changing to or from a custom order status).

WooCommerce Pre-Orders

Compatibility with the WooCommerce Pre-Orders plugin is included.

You typically need to use the Order status changed trigger rule, which will fire whenever an order changes status.

You can use this together with a filter to act only when an order changes status to pre-ordered:

Pre-Order Filter Example

See the documentation on filters for more information.

You may also wish to view the WooCommerce Pre-Orders documentation.

Groups for WooCommerce

Whilst we haven’t extensively tested these plugins together, we do know of users that are using them successfully.

If you are encountering memory exhausted errors when using WooCommerce Zapier and Groups for WooCommerce, please update it to version 1.7.3 which includes a fix that prevents an infinite recursion bug in WooCommerce core.

You may also wish to view the Groups for WooCommerce documentation.

WooCommerce Gravity Forms Add-Ons

WooCommerce Zapier includes support for the Gravity Forms Add-Ons extension.

The Gravity Forms Add-Ons data is sent to Zapier as part of the line_items meta_data field, allowing it to be used in Zap filters.


Please keep in mind that the Zapier Zap editor won’t be aware of your additional Gravity Forms product fields up until an order is placed on your WooCommerce store for that product. After that, you can open the Zap Editor and you should see your Gravity Forms fields along with the standard fields.

URL Coupons

WooCommerce Zapier lets you create new Coupons in Zaps (using the Create Coupon action).

If you are using the URL Coupons Extension, you can automatically configure the URL Coupons settings (such as Unique URL and Page Redirect) for the coupon when it is created via a Zap:

The Resulting Coupon in WooCommerce

To achieve this, in your Zap’s Create Coupon action, use the Meta Data List field to add a new the _wc_url_coupons_unique_url metadata record. You would typically set the value of this field to the Slug output from the suggested Code by Zapier step:

Set Coupon Unique URL Meta Data


Please be sure to read the URL Coupons documentation which describes important things to consider when setting Coupon URLs.

If you would also like to set the Page Redirect attribute for the coupon, you can do so by adding two additional meta data records to your create coupon action:

  • _wc_url_coupons_redirect_page_type set to page.
  • _wc_url_coupons_redirect_page set to the page ID of your choice.

Set Coupon Page Redirect Page ID Metadata

The end result is a newly created coupon in WooCommerce with all three URL coupon settings automatically configured:

New Coupon with URL Coupon Settings Configured

Uncanny Toolkit for LearnDash

Communication with an application-specific password1 not affected by this plugin, but the Front End Login feature causes issues when authenticating with the normal WordPress account password.

When using WordPress older than 5.6, please deactivate this feature.

Security Plugins

To avoid interfering with security plugins in general, please ensure that you are using WordPress Application Passwords1 to connect your store.

Use Application Passwords

To set up an Application Password, go to WordPress DashboardSide MenuUsersProfile screen and press the “Add New Application Password” button. Please see here for details.


When using Jetpack with WordPress 5.6 or later, the majority of the Jetpack plugin features are compatible with WooCommerce Zapier, however, there are several areas where you need to be aware of to make the two plugins work together.

If you are using the Jetpack Protect feature, you need to authenticate WooCommerce Zapier using an application-specific password1. Otherwise, please consult the Jetpack Protect documentation for assistance.

If you are using the Secure Sign On feature, use a WordPress Application Password1 feature when authenticating. Please see here for details on how to successfully authenticate.

Wordfence Security

For maximum compatibility with the Wordfence plugin, please ensure you’re using WordPress 5.6 or later.

In order to successfully authenticate with two-factor authentication enabled, you need to use a WordPress Application Password1 feature.

Please ensure that the WordPress DashboardSide MenuWordfenceAll OptionsDisable WordPress application passwords checkbox is not ticked (i.e., application passwords need to be enabled and not disabled).

Alternatively, you need to disable two-factor authentication for the user that connects to Zapier. Please ensure that that account has a very complex password to help improve security as much as possible.

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

Moreover, you will likely need to whitelist the WooCommerce Zapier REST API endpoints. You can find the list of the plugin endpoints inside our Developer Documentation.


To see if Wordfence is interfering with the communication, please go to WordPress DashboardSide MenuWordfenceToolsLive Traffic and review the live traffic logs to identify the specific reason for the failure.

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

iThemes Security

iThemes Security does not interfere with WooCommerce Zapier if you are using a WordPress Application Password1.

Alternatively, with older WordPress versions, iThemes Security has its own application-specific passwords solution, so when authenticating, please ensure that you use that application-specific password rather than your account password.

WP Rocket

This plugin has a feature that forces trailing slash for any URLs, which not compatible with the authentication mechanism in WooCommerce Zapier.

To avoid problem with it, please remove trailing slash functionality or disable it for the Integration endpoints. Refer to the WP Rocket Documentation to how to do it.

JWT Auth

The JWT Auth plugin forces its authentication method to all REST API requests (including WooCommerce Zapier). This interferes with the WooCommerce Zapier’s Actions functionality. It also prevents Trigger sample data from working.

The solution is to add WooCommerce Zapier’s endpoints to the JWT Auth plugin’s whitelist so that JWT authentication is not applied to WooCommerce Zapier’s endpoints.

Whitelist Example

add_filter( 'jwt_auth_whitelist', function ( $endpoints ) {
    return array(
} );

Other Security Plugins

The following plugins can cause authentication errors when connecting with WordPress account password:

Partially Compatible Plugins

Below is a list of plugins that are partially compatible with WooCommerce Zapier.

WooCommerce Product Add-Ons

WooCommerce Zapier includes support for the Product Add-Ons extension.

The Product Add-Ons data is sent to Zapier as part of the line_items and meta_data fields, allowing them to be used in Zap filters.

We don’t recommend using the Product Add-Ons data in Zap templates, unless all of your products have the same add-on fields available. This is because a Zap requires a predictable set of data fields coming through for each and every order line item.


The Product Add-Ons extension stores addon price information in the meta key field, which can result in a different key value from order to order, making the key name unpredictable and difficult to use in Zap actions.

Fancy Product Designer

Some WooCommerce Zapier users have reported success when using the Fancy Product Designer plugin, whereas others have encountered issues.

The Fancy Product Designer data is sent to Zapier as part of the line_itemsmeta_data fields, allowing them to be used in Zaps.


This plugin is prone to store vast amounts of information, which can lead to the data exceeding the current limitation of Zapier platform (6MB) for Order or Product triggers. When this happens, you may be unable to create a Zap, or the corresponding task will fail.

One possible solution for preventing this to happen that filtering out the outgoing data in WooCommerce, as described in the Modifying or Extending Data and Fields chapter.

WooCommerce Composite Products

The WooCommerce Composite Products extension can cause WooCommerce Zapier Create Product actions to fail with an Configuration" (composite_scenarios__configuration) is missing. error message.

To resolve this, please update Composite Products to version 8.1.1 (or newer).

Heads Up

It is not possible to create Composite Products via a Create Product action.

Incompatible Plugins

Below is a list of plugins that are not currently compatible with WooCommerce Zapier.


The WP-SpamShield plugin is known to cause issues when authenticating.

Having this plugin active may cause you to receive either of the following error messages:

Sorry, this user does not have the correct permissions.
ERROR: Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again.

Please deactivate the plugin and try again.

WP Content Copy Protection & No Right Click

This plugin is known to cause issues when authenticating.

Please deactivate the plugin and try again.

WooCommerce Real-time Notifications for new orders

This plugin is known to cause issues when authenticating, with the following error message:

Sorry, you cannot list resources.

Please deactivate the plugin and try again.

  1. WordPress 5.6 or later is required to use the Application Passwords feature. 

Last update: 2021-07-01
Back to top