Trigger Rules
A Trigger Rule defines an event (or multiple events) that will cause WooCommerce data to be sent to a Zapier Zap.
Tip
To see what has changed in Trigger Rules since the previous 1.x version, please see the Changes in Triggers chapter in the Migration Guide.
Orders¶
Warning
Available for both Order and Line Item in an Order triggers. See here for details on which trigger to use.
The following trigger rules are available to trigger your Zaps when order data in your WooCommerce store is added, changed or deleted.
Order created¶
Triggers when an order is created.
Note
The Order created trigger rule will trigger for every order received (both paid and unpaid).
If you would like to trigger your Zap only when you receive a paid order, then consider using the Order paid trigger rule instead.
Order deleted¶
Triggers when an order is deleted (trashed).
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Order paid¶
Triggers when an order is paid for. Occurs for real-time payment gateways (such as Stripe, PayPal, or most other credit card gateways).
Tip for offline/deferred payment methods
The Order paid trigger rule will not typically fire for offline/deferred payment methods such as Direct Bank Transfer (BACS), Check/Cheque or Cash on Delivery (COD).
If you are using an offline/deferred payment method, you have several choices:
- Use the Order created trigger rule, which will trigger for both paid and unpaid orders.
- Use the Order status changed trigger rule with a Filter if you wish to trigger your Zap when you receive a payment for an order. You could filter on
status = processingorstatus = completed. Your Zap will then trigger when you change an order’s status toprocessingorcompletedrespectively.
Order restored¶
Triggers when an already trashed order is restored from the trash.
Order status changed¶
Triggers every time an order changes status including when an order is first created.
Consider using with a Filter if you are interested in specific status changes only.
Note
For more information on WooCommerce Order Statuses and transitions, view the WooCommerce Order Status documentation.
Order updated¶
Triggers when an order is updated/edited/changed/modified, including when an order is refunded.
Products¶
The following trigger rules are available to trigger your Zaps when product data in your WooCommerce store is added, changed or deleted.
Tip
See the Product Types chapter for a full list of supported WooCommerce product types and functionalities.
Product created¶
Triggers when a product is created.
Triggers for every individual product variation in a variable product, and the parent product as well.
Product deleted¶
Triggers when a product is deleted (trashed).
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Product restored¶
Triggers when an already trashed product is restored from the trash.
Product updated¶
Triggers when a product is updated/edited/changed/modified.
Triggers for every individual product variation in a variable product, and the parent product as well.
Customers¶
The following trigger rules are available to trigger your Zaps when customer data in your WooCommerce store is added, changed or deleted.
What is a Customer?
A Customer in WooCommerce is someone with a user account to log in to your store. People purchasing as a guest (without logging into an account) are not considered customers.
Customer created¶
Triggers when:
- a customer registers (creates an account) in your WooCommerce store.
- a WordPress user account (with any role) is created.
Tip
For this to trigger, your WooCommerce store would normally be configured to allow customers to create an account.
Note
This trigger rule does not trigger when someone purchases as a guest without registering for an account. Please use one of the Order trigger rules if you would like guest purchases to be sent to Zapier.
Customer deleted¶
Triggers when a customer is deleted.
Note
There is no trash functionality for customers (users) in WordPress.
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Customer updated¶
Triggers when a customer (or any WordPress user) is updated/edited/changed/modified.
Coupons¶
Only available if the Coupon functionality is enabled in your WooCommerce store. (Enabled by default).
If your WooCommerce store has coupons enabled, the following trigger rules are available to trigger your Zaps when coupon data in your WooCommerce store is added, changed or deleted.
Coupon created¶
Triggers when a coupon is created.
Coupon deleted¶
Triggers when a coupon is deleted (trashed).
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Coupon restored¶
Triggers when an already trashed coupon is restored from the trash.
Coupon updated¶
Triggers when a coupon is updated/edited/changed/modified.
Bookings ¶
Only available if the WooCommerce Bookings plugin is installed.
If your WooCommerce store has WooCommerce Bookings installed, the following trigger rules are available to trigger your Zaps when booking data in your WooCommerce store is added, changed or deleted.
Booking cancelled¶
Triggers when a booking is canceled. Either by the customer, an administrator or automatically if the order is not finished.
Booking created¶
Triggers when a booking is first created.
Note
The Booking created trigger rule will trigger when a customer adds a bookable product to their cart. Before they proceed to the checkout to complete and pay for their order.
If you would like to trigger your Zap only when you receive a paid booking, then consider using the Booking ordered trigger rule instead.
Booking deleted¶
Triggers when a booking is deleted (trashed).
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Booking ordered¶
Triggers when an order is placed containing a booking, which is the same time that the Order created trigger rule.
Booking restored¶
Triggers when an already trashed booking is restored from the trash.
Booking status changed¶
Triggers every time a booking changes status including when a booking is first created.
Consider using with a Filter if you are interested in specific status changes only.
Tip
For more information on the WooCommerce Bookings statuses, please see the Bookings Documentation.
Booking updated¶
Triggers when a booking is updated/edited/changed/modified, including any status change.
Subscriptions¶
Only available if the WooCommerce Subscriptions plugin is installed.
If your WooCommerce store has WooCommerce Subscriptions installed, the following trigger rules are available to trigger your Zaps when subscription data in your WooCommerce store is added, changed or deleted.
Subscription created¶
Triggers when a subscription is created.
Triggers for both paid and unpaid subscriptions
The Subscription created trigger rule will trigger for every new subscription (both paid and unpaid).
See the tip below if you would like to perform a Zap for successful (paid) subscriptions only.
How to trigger for paid subscriptions only
If you would like to trigger your Zap only when a paid subscription is created, you can use the following Zap setup:
- Zap Step 1: Use the Subscription status changed trigger rule.
- Zap Step 2: Add a Filter step for
status=active. - Zap Step 3: Add a Formatter by Zapier step, with the Compare Dates Transform:
- Start Date: Subscription Start Date
- End Date Value: Subscription Date Paid
- Zap Step 4: Add a Filter step for 3. Output Days (Number) Less than
2. - Zap Step 5: Your desired action.
The above setup should ensure that the Zap only triggers when a subscription is first paid for. It shouldn’t trigger for subsequent subscription renewals (which also change a subscription’s status to Active).
This setup works because the date_paid subscription field changes to a new date every time the subscription renews, so steps 3 and 4 in the above Zap setup should ensure that the Zap only continues for the initial payment (when the Subscription first changes status to active).
Subscription deleted¶
Triggers when a subscription is deleted (trashed).
Important
When using this trigger rule, only the ID of the deleted Resource is sent to Zapier. No other data fields are sent.
This is due to limitations in how WooCommerce handles deleted events.
Subscription renewal failed¶
Triggers when a subscription has just had a renewal payment fail.
Note
This is not triggered for failed payments on the initial order or a switch order. It is only triggered for failed payments on renewal orders.
Subscription renewed¶
Triggers when a subscription renewal payment completes successfully. It is triggered for both automatic and manual renewal payments.
Important
This is not triggered for payments on the initial order or a switch order. It is only triggered for successful payments on renewal orders.
Subscription status changed¶
Triggers every time a subscription changes status including when a subscription is first created.
A subscriptions status can be changed by store owners, subscribers or automatic schedule events, like expiration. This trigger rule will always be triggered on status changes, regardless of what initiated the status change.
Consider using with a Filter if you are interested in specific status changes only.
Tip
For more information on the WooCommerce Subscriptions statuses and status transitions, please see the Subscription Status Guide documentation.
Subscription switched¶
Triggers when a user upgrades or downgrades their subscription from the My Account page.
Note
Triggered when the switch order status changes to processing or completed and runs after all the switching and updating has happened.
Subscription updated¶
Triggers when a subscription is updated/edited/changed/modified/renewed/failed, including any status change.