Filters help you decide when to send a trigger and what information to include. When working with Flows, you can also use Flow conditionals to make the trigger even more specific.
All of the filters are available for both Webhooks and Flows Automations.
Set user id
Set the numeric ID of a user that has permission to view the Woocommerce REST API. By default we try to locate the ID of the first admin user.
Set API version
Select the Woocommerce API version you want to use for this request. By default, we use wp_api_v2
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
User must be logged in
Check this button if you want to fire this webhook only when the user is logged in ( is_user_logged_in() function is used ).
User must be logged out
Check this button if you want to fire this webhook only when the user is logged out ( ! is_user_logged_in() function is used ).
Trigger from backend only
Check this button if you want to fire this trigger only from the backend. Every post submitted through the frontend is ignored ( is_admin() function is used ).
Trigger from frontend only
Check this button if you want to fire this trigger only from the frontent. Every post submitted through the backend is ignored ( ! is_admin() function is used ).
Flows or Webhooks?
While automating, it is crucial that you understand the difference between our Flows feature and Webhooks as it affects the way you work with our product. Below you will find further details of the core differences.
Can receive data from an external URL/API/Webhook to run multiple actions within our plugin (E.g., When a flow was executed, create a user, then the data to Zapier, take the response, and send an email).
Offers bidirectional connections (Can send AND receive data)