Compatibility

With thousands of WooCommerce extensions, addons and plugins available for WooCommerce, and a similar amount of integrations for Zapier, it can be challenging to know if they are compatible with WooCommerce Zapier.

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

High-Performance Order Storage (HPOS) ¶

WooCommerce Zapier version 2.7 and later includes support for WooCommerce’s High-Performance Order Storage (HPOS) feature. If you are using WooCommerce Zapier version 2.6 or earlier, you must update to version 2.7 or later before enabling HPOS in WooCommerce. After doing so, your WooCommerce Zaps should continue to work with or without enabling HPOS.

For the best possible HPOS experience, please ensure you are using the latest versions of your WooCommerce plugin and extensions before enabling HPOS in WooCommerce.

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.55 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.

Woo Subscriptions¶

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

If you have Woo 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 created with the Order Status Manager extension are supported in the Order data Status field when using Order triggers and actions

However, a dedicated Trigger Rule for Order status changed to … is not available for created custom order statuses.

If you would like to trigger a Zap when an order changes to a custom status, we’d recommend using the Order status changed (any status) 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 (any status) 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:

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.

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:

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:

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.

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

Uncanny Toolkit for LearnDash¶

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

Please deactivate this feature if you are not authenticated with a WordPress Application password.

Security Plugins¶

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

Jetpack¶

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 Brute Force Attack Protection (formerly Protect) feature, you need to authenticate WooCommerce Zapier using an application-specific password. Otherwise, please consult the Jetpack Protect documentation for assistance.

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

Wordfence Security ¶

Wordfence Security is a very popular security plugin that is commonly used with WooCommerce Zapier.

In order to successfully authenticate with two-factor authentication enabled, you need to use a WordPress Application Password (not your regular WordPress password) when authenticating.

Please also ensure that the WordPress Dashboard → Side Menu → Wordfence → All Options → Disable WordPress application passwords checkbox is not ticked (i.e., application passwords need to be enabled and not disabled).

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

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

iThemes Security¶

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

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.

add_filter( 'jwt_auth_whitelist', function ( $endpoints ) {
    return array(
        '/wc-zapier-auth/*',
        '/wp-json/wc-zapier/*',
    );
} );

Other Security Plugins¶

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

• Limit Login Attempts Reloaded
• SiteGuard WP Plugin
• IP Geo Block
• WPS Hide Login

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.

WooCommerce Deposits¶

The WooCommerce Deposits extension can cause problems when retrieving sample order data from WooCommerce when using the Zapier.com Zap editor.

This is because WooCommerce Deposits creates future-dated orders that have a status of scheduled-payment, so when WooCommerce Zapier loads the most recent orders to display as sample data, the future-dated scheduled-payment orders are listed first.

This makes it difficult to display useful orders in the Zap editor when setting up your Zap.

The workaround is to temporarily trash these Scheduled Payment orders, then set up your Zap, and then restore the orders:

1. Go to the WordPress Dashboard → Side Menu → WooCommerce → Orders screen, then filter by Scheduled.
2. Select all the Scheduled orders, then Bulk actions → Move to Trash.
3. Return to the Zapier.com Zap Editor, then in your Trigger step, click Test Trigger, then click the Dropdown list and click the Load More button to retrieve your most recent order data from your store. This sample data should now contain recent valid orders (rather than future-dated scheduled payment orders).
4. Select a recent order from the dropdown, then complete the setup of your Zap and turn it on.
5. Return to WordPress Dashboard → Side Menu → WooCommerce → Orders, filter by Trashed.
6. Select all trashed orders, then Bulk actions → Restore to reinstate the Scheduled Payment orders.

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_items → meta_data fields, allowing them to be used in Zaps.

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).

Incompatible Plugins¶

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

WP-SpamShield¶

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.

Partially Compatible Integrations¶

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

Gmail¶

Google is restricting the Gmail Integrations usage. Only the approved apps can receive information. Unfortunately, the WooCOmmerce Zapier is not on the list. If you have a consumer Gmail account and configure Gmail as a trigger and WooCommerce as an action, you will see the following error:

Sending data from WooCommerce to Gmail is not restricted.