Compatibility

WooCommerce Feature Compatibility¶

WooCommerce core contains some optional features that may affect the behaviour of Zapier Integration for WooCommerce.

Below is a list of these features and their compatibility with Zapier Integration for WooCommerce.

Cart and Checkout Blocks¶

v2.10

Zapier Integration for WooCommerce supports the Cart & Checkout Blocks feature.

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

Please consult the Cart & Checkout Blocks documentation for further information.

Coming Soon Mode¶

Zapier Integration for WooCommerce is fully compatible with the WooCommerce Coming Soon Mode, which was introduced in WooCommerce version 9.1. This feature allows stores to control the visibility of their site and store while it is under construction. Zapier Integration for WooCommerce can seamlessly handle this mode without any issues.

For more information on Coming Soon Mode, please see the Coming Soon Mode documentation.

Coupons¶

Zapier Integration for WooCommerce is fully compatible with WooCommerce’s Coupon functionality, allowing you to send and receive coupon data through Zaps. However, to ensure proper functionality, the coupon feature must be enabled in WooCommerce for this to work.

To enable coupons in WooCommerce:

1. Go to WooCommerce → Settings → General.
2. Scroll down to the Enable Coupons section.
3. Tick the box next to Enable the use of coupon codes.
4. Save changes.

For more information on using coupon triggers and actions, please see the Coupon Data Fields documentation.

High-Performance Order Storage (HPOS)¶

v2.7

Zapier Integration for WooCommerce includes support for WooCommerce’s High-Performance Order Storage (HPOS) feature.

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.

Order Attribution¶

v2.10

WooCommerce 8.5 introduced an Order Attribution Tracking feature to help store owners understand where their orders are coming from.

This data is included in the Order data sent to Zapier. Please see Order Data Fields documentation for more information.

Stock Management¶

The default stock management feature for your store can be enabled or disabled in WooCommerce → Settings → Products → Inventory → Manage stock checkbox. (Enabled by default).

Stock management feature must be enabled for your product(s) as well for the following trigger rules to work:

• Product stock low
• Product stock status changed

To enable stock management for your products:

• For regular products, go to Product Data → Inventory → Stock management → then ticking the Track stock quantity for this product and saving the product.
• For individual variations, edit the product in WooCommerce, then go to Product Data → Variations, then edit each variation and tick the Manage stock? checkbox and save each variation.

Tax¶

Zapier Integration for WooCommerce works whether WooCommerce’s Tax functionality is enabled or disabled.

The tax feature can be enabled and disabled in WooCommerce → Settings → General → Enable tax rates and calculations checkbox (enabled by default).

Once taxes are enabled, Zapier Integration for WooCommerce can send and receive tax-related data in your Zaps. This includes:

• Order tax data: You can send tax data with order-related Zaps. Please see Order Data Fields for details.
• Product tax settings: You can trigger actions or automate workflows based on specific product tax classes. Please see Product Data Fields for details.

WooCommerce Extension 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 Zapier Integration for WooCommerce.

Below is a list of WooCommerce Extensions and plugins that are supported, compatible, or partially compatible with Zapier Integration for WooCommerce.

Also, security plugins that may interfere with Zapier Integration for WooCommerce are listed separately.

Supported Plugins¶

The following WooCommerce extensions are actively supported by Zapier Integration for WooCommerce.

WooCommerce Bookings¶

v2.2 WooCommerce Bookings

Compatibility with the WooCommerce Bookings plugin was added in version 2.2 of Zapier Integration for WooCommerce. You must be running at WooCommerce Bookings version 2.0.0 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 Zapier Integration for WooCommerce.

WooCommerce Memberships¶

v2.10 WooCommerce Memberships

Compatibility with the WooCommerce Memberships plugin was added in version 2.10 of Zapier Integration for WooCommerce. You must be running WooCommerce Memberships version 1.26.0 or later.

If you have WooCommerce Memberships installed, you can use Membership data in your Zaps, including Membership Plan and User Membership.

WooCommerce Subscriptions¶

WooCommerce Subscriptions

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

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

More on how to use Subscriptions in Zapier Integration for WooCommerce.

Checkout Field Editor¶

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

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 known to be compatible with Zapier Integration for WooCommerce.

Sequential Order Numbers Pro¶

Zapier Integration for WooCommerce 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 who are using them successfully.

If you are encountering memory exhausted errors when using Zapier Integration for WooCommerce 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¶

Zapier Integration for WooCommerce 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 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¶

Zapier Integration for WooCommerce 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:

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.

The 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 is 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.

Asset CleanUp: Page Speed Booster¶

Zapier Integration for WooCommerce does not interfere with the Asset CleanUp: Page Speed Booster CSS/JavaScript minifying and combining functionality. However, the Pro version includes an option to turn off plugins on the front-end.

Borlabs Cache¶

The Borlabs Cache plugin helps with caching and optimisation, but it can interfere with the Zapier Integration for WooCommerce authentication endpoint. You can still use it safely if you disable caching for this specific endpoint.

Security Plugins¶

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

If you have a plugin installed that prevents the connection between Zapier.com and your site, please try temporarily disabling the security plugin(s), authenticating, and then re-enabling the security feature(s) once you have successfully authenticated.

Jetpack¶

When using Jetpack, the majority of the Jetpack plugin features are compatible with Zapier Integration for WooCommerce. However, there are several areas 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 Zapier Integration for WooCommerce 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¶

v2.3

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

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

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

Moreover, you may need to whitelist the Zapier Integration for WooCommerce 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 Dashboard → Side Menu → Wordfence → Tools → Live 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 to only see Zapier authentication logs.

Solid Security¶

Solid Security (formerly iThemes Security) does not interfere with Zapier Integration for WooCommerce if you are using a WordPress Application Password.

Alternatively, with older WordPress versions, Solid Security has its own application-specific password 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 is not compatible with the authentication mechanism in Zapier Integration for WooCommerce.

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

JWT Auth¶

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

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

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

Two-Factor Authentication¶

Your WordPress dashboard

The Zapier Integration for WooCommerce plugin is generally compatible with most security plugins that enforce two-factor authentication (2FA), provided that you are using the WordPress Application Password feature. Please use an application-specific password if you encounter a problem.

Alternatively, consult the security plugin’s documentation as they may have their own application-specific password feature, and use that when authenticating WooCommerce with Zapier.

Please see the Security Plugins chapter for a list of known compatibility statuses.

Other Security Plugins¶

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

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

Hosting Providers¶

Some hosting providers have specific configurations or security settings that can interfere with Zapier Integration for WooCommerce.

Cloudflare Web Application Firewall (WAF)¶

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

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

WordPress.com Secure Sign On¶

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

To successfully authenticate Zapier with your WooCommerce store, you need to use an Application Password:

1. Log into WordPress.com.
2. Switch to your site in the side menu.
3. Go to the Side Menu → Jetpack → Dashboard, and click the Settings button in the top right corner.
4. Inspect the status of the Allow users to log in to this site using WordPress.com accounts toggle.
5. If the toggle is
   1. Off: you can navigate WordPress Dashboard → Side Menu → Users → Profile page.
   2. On: you need to manually type https://<YOUR SITE NAME>/wp-admin/profile.php URL in your browser. Use your site URL, not wordpress.com to access your WordPress profile page.
6. Note your Username, as you need to use this username when authenticating later.
7. Create an Application Password as described here.
8. Return to Zapier.com and authenticate again, but instead of using your wordpress.com credentials, you will use:
   • Your username from step 6 above.
   • Your password from step 7 above.

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

WP Engine¶

If your website is hosted with WP Engine, you may encounter issues with the Zapier Integration for WooCommerce authentication process.

You must ensure that WP Engine’s Redirect Bots feature is disabled so the Zapier Integration for WooCommerce authentication process works correctly.

Partially Compatible Plugins¶

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

WooCommerce Product Add-Ons¶

Zapier Integration for WooCommerce 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 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 Zapier Integration for WooCommerce 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, 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 Zapier Integration for WooCommerce 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 Zapier Integration for WooCommerce Create Product actions to fail with the following error message:

Configuration (composite_scenarios__configuration) is missing.

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

Incompatible Plugins¶

Your WordPress dashboard

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

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.