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.

Order¶

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)

Product¶

You can send Products data to Zapier, or you can create or update it from external source.

• Product Trigger Rules
• Product Actions
• Product Data Fields

Product Types¶

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.

Integration Functionality by Product Type:¶

Data Availability by Product Type:¶

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.

Variable Products¶

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.

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.

The Update Product Stock Quantity action is an exception. It can update an individual product variation’s stock quantity too.

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 line_items → 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 line_items → variation_id.

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:¶

Customer¶

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.

• Customer Trigger Rules
• Customer Actions
• Customer Data Fields

Coupon¶

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.

• Coupon Trigger Rules
• Coupon Actions
• Coupon Data Fields

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.

Booking ¶

The Booking resource represents a booked timeslot, as described in the WooCommerce Bookings plugin. See the Bookings documentation for more details.

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.

• Booking Trigger Rules
• Booking Actions are not supported
• Booking Data Fields

Subscription¶

The Subscription resource represents a recurring payment as described in the WooCommerce Subscriptions plugin. See the Subscriptions documentation for more details.

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.

• Subscription Trigger Rules
• Subscription Actions
• Subscription Data Fields