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.

Note

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.

Security Plugins

Looking for security related plugin compatibility? See details in Troubleshooting on how to successfully authenticate.

Compatible Plugins¶

Below is a list of WooCommerce extensions that are compatible with 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).

You may also wish to view the WooCommerce Subscriptions documentation.

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.

Sequential Order Numbers Pro¶

Compatibility with the WooCommerce Sequential Order Numbers Pro plugin was added in version 1.1 of the Zapier Integration plugin.

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:

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

Note

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:

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:

Important

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 end result is a newly created coupon in WooCommerce with all three URL coupon settings automatically configured:

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.

Warning

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

Warning

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.

Incompatible Plugins¶

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

WooCommerce Bookings¶

At this stage the WooCommerce Zapier extension does not support Booking information.

If you would like to see this featured added, we suggest following these instructions on how to request a new feature.

WP Rocket | Enforce Trailing Slash on URLs¶

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

We suggest disabling this plugin.

Conflicting Plugins¶

Below is a list of plugins that our users have reported having conflicts or issues with when using them with WooCommerce Zapier.

If you are using one of these plugins and can’t authenticate, then please deactivate the plugin and try again.

Jetpack¶

If you are using the WordPress.com Secure Sign On feature, please see here for details on how to successfully authenticate.

Uncanny LearnDash Toolkit¶

The Front End Login feature in this plugin causes issues when authenticating.

Please deactivate this feature (or the entire 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.

WP Content Copy Protection & No Right Click (premium)¶

This plugin is known to cause issues when authenticating.

Please deactivate the plugin and try again.

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.

Last update: December 9, 2020