Resources (Data Types)
Resources (or Data Types) are the building blocks of the WooCommerce Zapier integration. Every resource can be sent from your store to Zapier, and most of them can be received too. The list includes the most useful set of built-in and other plugin provided types.
WooCommerce Zapier uses WooCommerce’s REST API. This means that data field names, descriptions and values can vary from one WooCommerce store to another.
Your store’s data, fields and trigger rules may be different to this documentation due any of the following:
- Your installed (active) WordPress plugins and WooCommerce extensions.
- Your WooCommerce and WordPress versions and the used locale/language.
- Any custom code that overrides or changes how the WooCommerce/WordPress REST API operates.
Field definitions in this documentation are generated with WordPress v5.3 and WooCommerce v3.9 with
Orders are an essential part in the eCommerce process. They represent an “order event” followed by its various stages, such as payment, fulfillment, or shipping.
For triggers, the Order resource is accessible in two separate ways in Zapier Integration:
- The Order trigger creates a separate Zapier Task for every order in your store.
- The Line Item in an Order trigger is a great way to send every order line item (product) data independently to Zapier, because it creates a separate Zapier Task for every single line item (product) ordered in your store.
See the key differences in this Frequently Asked Questions chapter.
You can choose between the two types of behaviour in your Zap when you are configuring the trigger step. Both triggers support the same set of Trigger Rules, but produce a slightly different data fields (see below).
- Order Trigger Rules
- Order Actions
- Order Data Fields (triggers and actions)
- “Line Item in an Order” Data Fields (triggers only)
You can send Products data to Zapier, or you can create or update it from external source.
WooCommerce comes with multiple types of products out of the box. The Zapier Integration supports most of them, however not all WooCommerce Zapier features are available for every WooCommerce product type. Please consult the following tables for details.
Extensions can extend available data and introduce other product types. Please see the Plugin Compatibility chapter for details.
Integration Functionality by Product Type:¶
|Product type||Triggers||Actions and Searches||Order Context1|
Data Availability by Product Type:¶
N/A: Functionality or data is not provided by WooCommerce.
Limited: Partially supported. For details, please see the limitations below.
Product Data in Order Context¶
While every order contains one or more product as a line item, not all product data included by default. Please compare Order Data Fields or Line Item in an Order Data Fields with Product Data Fields for availability. If you need additional product data fields, consider adding a Find step to your Zap.
In WooCommerce, a product with variable attributes is constructed as multiple interconnected products. The parent product that connects everything and holds shared information, which you can edit in the WooCommerce dashboard, has a variable product type. For each individual variation, a separate product is created and stored as a product variation. This latter product holds selected attributes for the variable product. For example, an individual product variation has price, SKU or stock level information for a particular attribute.
In the Zapier interface, you can see IDs of linked variations in the
variations field for a variable product. On the other hand, the variable product ID is visible in the
parent_id field for a product variation.
You can’t edit a variation name directly in the WooCommerce dashboard. Instead, the name is automatically constructed with the used product attributes and the selected values.
Sending or Receiving a Variable Product¶
Triggers are supported for variable products as well as their individual product variations. They do not behave differently from any other supported product type.
Actions, on the other hand, do not support individual variations. Only the (parent) variable product is supported. I.e., you can create, update and search for a variable product, but you can’t for its individual product variations.
Variable Products as Order Line Item¶
In Order Triggers, when a line item represents a variable product, WooCommerce combines fields data from the parent and the selected variation. While the
product_id and some other fields source are the variable product, most of the information is selected from the used product variation. For example, the actual used product ID is visible in the
For Order Actions or Searches, you can add a variable product to an order as long you know the ID or SKU of a variation and the product already exists in your WooCommerce store.
Notable Order Field Sources:¶
|line_items → product_id||Variable product|
|line_items → variation_id||Product variation|
|line_items → name||Product variation|
|line_items → price||Product variation|
|line_items → sku||Product variation|
|line_items → tax_class||Variable product|
If you want to use Zapier to create an order in WooCommerce for a variable product, consider using the individual variation’s SKU rather than variation ID.
The Customer resource represent a buyer who registers to your site. If you are relying on this resource, you can enforce registration by disabling Guest Checkout.
WooCommerce store customers alongside with the WorPress users. If you customise WorPress Roles and Capabilities feature, make sure to not rename the Customer role, it may interfering with the plugin functionality.
Coupon functionality is built in in WooCommerce. They are a great way to offer discounts and rewards to your customers, and can help promote sales across your shop. The integration can create or update a coupon, or send coupon details when its changed.
Enabled by default, but can be disabled
This resource is only available in WooCommerce Zapier if your store has coupons functionality enabled. If you want to use this resource, go to the WordPress Dashboard → Side Menu → WooCommerce → Settings screen, and make sure the Enable coupons is enabled.
Please see the Product chapter for information about the Bookable product.
Please see the announcement post for some examples of how you could use WooCommerce Booking data in your Zaps.
You may choose Booking in the Zapier.com interface without installing the WooCommerce Bookings plugin, however the functionality will not work without WooCommerce Bookings, which is sold separately by WooCommerce.
The minimum required WooCommerce Bookings version is 1.15.35.
Please ensure you are using WooCommerce Zapier plugin to 2.2.0 or later.
Please see the Products chapter for Simple subscription and Variable subscription informations. Availability of data fields and behaviour for the “Variable subscription” product are similar to the WooCommerce built-in variable products. For details, please see the Variable Products chapter.
You may choose Subscription in the Zapier.com interface without installing the WooCommerce Subscriptions plugin, however the functionality will not work without WooCommerce Subscriptions, which is sold separately by WooCommerce.
The minimum required WooCommerce Subscriptions version is 3.0.0.