Connect Woocommerce to FluentCRM
All triggers and actions
Get started
Requirements
For this connection to work, please make sure the following plugins/services are in place:
Documentation
To make your start as smooth as possible, we prepared various helpfiles for you that assure an easy start using WP Webhooks.
Scenarios
What's the integration?
Woocommerce
WooCommerce is an open-source e-commerce plugin for WordPress. It is designed for small to large-sized online merchants using WordPress. While WooCommerce webhooks are, by default, limited, WP Webhooks aims to fill that gap.
FluentCRM
FluentCRM is a WordPress plugin that allows users to create and manage email marketing campaigns on their WordPress websites. It includes customizable opt-in forms, automation workflows, and integration with popular email marketing services. FluentCRM is designed to be user-friendly and easy to set up, making it a good choice for small businesses and bloggers who want to grow their email lists and communicate with their customers and subscribers.
Contact added to list
This webhook fires as soon as a contact is added to a list within FluentCRM.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected lists
Select only the lists you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on users only
Check this if you only want to fire this trigger when a WordPress user is connected to the contact email.
Add contact to list
Add a contact to one or multiple lists within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set the email of the contact/user you want to add the lists to.
- user_id
In case you did not set the email, you can also assign the user via a given user id.
- lists
Add the lists you want to add the user to. This argument accepts a comma-separated string, as well as a JSON construct.
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Contact added to tag
This webhook fires as soon as a contact is added to a tag within FluentCRM.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected tags
Select only the tags you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on users only
Check this if you only want to fire this trigger when a WordPress user is connected to the contact email.
Add contact to tag
Add a contact to one or multiple tags within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set the email of the contact/user you want to add the tags to.
- user_id
In case you did not set the email, you can also assign the user via a given user id.
- tags
Add the tags you want to add the user to. This argument accepts a comma-separated string, as well as a JSON construct.
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Order created
This webhook fires as soon as an order was created within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
Add coupon emails
Add one or multiple emails to a coupon within Woocommerce.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- coupon_id
Set this argument to the id of the coupon.
- emails
Add the emails you want to add to the user. This argument accepts a comma-separated string, as well as a JSON construct.
- replace
Set this to yes to replace the existing emails. If set to no, the emails are appended to the existing ones. Default: no
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Contact deleted
This webhook fires as soon as a contact was deleted within FluentCRM.
Add coupon user IDs
Add one or multiple emails via user IDs to a coupon within Woocommerce.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- coupon_id
Set this argument to the id of the coupon.
- user_ids
Add the user_ids you want to add to the user. This argument accepts a comma-separated string, as well as a JSON construct.
- replace
Set this to yes to replace the existing user_ids. If set to no, the user_ids are appended to the existing ones. Default: no
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Contact removed from list
This webhook fires as soon as a contact was removed from a list within FluentCRM.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected lists
Select only the lists you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on users only
Check this if you only want to fire this trigger when a WordPress user is connected to the contact email.
Create Woocommerce order
Create a Woocommerce order on your website using webhooks.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- billing_address
The billing address of the order. Please see the description for more information.
- shipping_address
The shipping address of the order. Please see the description for more information.
- shipping_lines
This argument allows you to add certain shipping lines to your order. Please see the description for further details.
- add_products
The slist with the product ids and the quantity. More information within the description.
- calculate_totals
Set it to "yes" in case you want to calculate the order total. Default "no".
- payment_complete
Set it to "yes" in case you want to set the payment to complete. You can also set a transation id instead of "yes".
- legacy_set_total
Set the legacy total amount and type. More information within the description.
- order_meta
You can also set custom order meta. This meta will be saved as custom values within the post meta table. More information within the description.
- order_status
The order status you want to use for the order. Please check the description for more information.
- customer_id
The id or the email of the customer for the order.
- customer_note
Some text that will be displayed as the customer note.
- order_parent
The id of a parent order.
- created_via
In identifier where the order was created from. E.g. "wp-webhooks".
- cart_hash
A cart hash value.
- order_id
A custom order id (Please note that this value may NOT be the order id of the order you currently create).
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Contact removed from tag
This webhook fires as soon as a contact was removed from a tag within FluentCRM.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected tags
Select only the tags you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on users only
Check this if you only want to fire this trigger when a WordPress user is connected to the contact email.
Create contact
Create a contact within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set this field to the email of the person you want to create as a contact.
- name_prefix
A prefix for the contact name.
- first_name
The first name of the contact.
- last_name
The last name of the contact.
- full_name
A separate field for the full user name.
- address_line_1
The first address line.
- address_line_2
The second address line.
- city
The city name.
- state
The country state.
- postal_code
The postal code.
- country
The country code.
- ip
The contact IP address.
- phone
The phone number for the contact.
- source
Where the subscriber was acquired from. Standard values are: wp_users or web
- date_of_birth
The birthday of the contact.
- status
The status of the contact.
- tags
A comma-separated list or JSON construct of the tags you want to assign to the contact.
- lists
A comma-separated list or JSON construct of the lists you want to assign to the contact.
- timezone
The timezone of the contact. E.g.: UTC
- custom_values
A JSON construct containing further meta values for the contact.
- send_pending_mail
Set this to "yes" to send a pending email to the contact in case the status is set to pending. Default: no
- do_action
Advanced: Register a custom action after WP Webhooks fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Contact status updated
This webhook fires as soon as a contact status gets updated within FluentCRM.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
- Trigger on users only
Check this if you only want to fire this trigger when a WordPress user is connected to the contact email.
Create coupon
Create a coupon within Woocommerce.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- coupon_code
The code that your customers can use during checkout.
- type
The coupon type.
- amount
The discount amount of the coupon code, based on the selected type.
- individual_use
Set this to yes if the coupon cannot be used in conjunction with other coupons. Default: no
- product_ids
Add IDs of products in case you want to apply the coupon code only to specific products. This argument accepts a comma-separated string, as well as a JSON construct.
- exclude_product_ids
Add IDs of products that you want to exclude from the coupon code. This argument accepts a comma-separated string, as well as a JSON construct.
- usage_limit
Set a number if you want to limit the coupon to be used a limited amount of times only. Default: 0 (unlimited)
- usage_limit_per_user
Set a number to define whether a user can use the coupon code multiple times. Default: 0 (unlimited)
- limit_usage_to_x_items
Define a maximum number of products this coupon can be applied to for each cart. Default: 0 (unlimited)
- usage_count
A number that shows how often the code has been already used.
- expiry_date
A date when the coupon code expires. Leave empty to never expire it.
- enable_free_shipping
Set this to yes to enable free shipping. Default: no
- product_category_ids
Add the category IDs you want to add to the coupon. This argument accepts a comma-separated string, as well as a JSON construct.
- exclude_product_category_ids
Add the category IDs you want to exclude to the coupon. This argument accepts a comma-separated string, as well as a JSON construct.
- exclude_sale_items
Set this to yes to prevent the coupon being applied to items on sale. Default: no
- minimum_amount
Set a minimum amount that need to be reached before the coupon can be applied.
- maximum_amount
Set a maximum amount of which the coupon can be applied to.
- coupon_emails
Add one or multiple emails to the coupon. Only the users with those emails can redeem the code. This argument accepts a comma-separated string, as well as a JSON construct.
- description
Add a coupon author. This field accepts a user id.
- replace
Set this to yes to replace the existing user_ids. If set to no, the user_ids are appended to the existing ones. Default: no
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Coupon created
This webhook fires as soon as a coupon was created within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Get contact
Retrieve a contact within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- contact_value
Set this field to either the contact email or contact id.
- value_type
If you want to fetch the contact by a given user id, set this field do user_id. Default: default
- do_action
Advanced: Register a custom action after WP Webhooks fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Coupon deleted
This webhook fires as soon as a coupon was deleted within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Remove lists from contact
Remove one or multiple lists from a contact within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set the email of the contact/user you want to remove the lists from.
- user_id
In case you did not set the email, you can also assign the user via a given user id.
- lists
Add the lists you want to remove from the user. This argument accepts a comma-separated string, as well as a JSON construct.
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Coupon restored
This webhook fires as soon as a coupon was restored within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Remove tags from contact
Remove one or multiple tags from a contact within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set the email of the contact/user you want to remove the tags from.
- user_id
In case you did not set the email, you can also assign the user via a given user id.
- tags
Add the tags you want to remove from the user. This argument accepts a comma-separated string, as well as a JSON construct.
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Coupon updated
This webhook fires as soon as a coupon was updated within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Update contact
Update or create a contact within FluentCRM.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- email
Set this field to the email (or the user id) of the contact you want to update.
- name_prefix
A prefix for the contact name.
- first_name
The first name of the contact.
- last_name
The last name of the contact.
- full_name
A separate field for the full user name.
- address_line_1
The first address line.
- address_line_2
The second address line.
- city
The city name.
- state
The country state.
- postal_code
The postal code.
- country
The country code.
- ip
The contact IP address.
- phone
The phone number for the contact.
- source
Where the subscriber was acquired from. Standard values are: wp_users or web
- date_of_birth
The birthday of the contact.
- status
The status of the contact.
- tags
A comma-separated list or JSON construct of the tags you want to assign to the contact.
- lists
A comma-separated list or JSON construct of the lists you want to assign to the contact.
- timezone
The timezone of the contact. E.g.: UTC
- custom_values
A JSON construct containing further meta values for the contact.
- remove_tags
A comma-separated list or JSON construct of the tags you want to remove from the contact.
- remove_lists
A comma-separated list or JSON construct of the lists you want to remove from the contact.
- create_if_none
Set this argument to yes to create the contact in case it does not exist yet. Default: no
- send_pending_mail
Set this to "yes" to send a pending email to the contact in case the status is set to pending. Default: no
- do_action
Advanced: Register a custom action after WP Webhooks fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Customer created
This webhook fires as soon as a customer was created within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Woocommerce API call
The full power of the woocommerce API, packed within a webhook.
Arguments
Down below you will find a list of all available arguments you can use for this specific endpoint. Each of those arguments can be set within the webhook request.
- consumer_key
Your API consumer key. Please see the description for more information.
- consumer_secret
Your API consumer secret. Please see the description for more information.
- api_base
The action you want to use. E.g. products/1234 - Please see the description for more information.
- api_method
The method of the api call. E.g. get - Please see the description for more information.
- api_data
Additional data you want to send to the api call. Please see the description for more information.
- api_options
Extra arguments. Please see the description for more information.
- do_action
Advanced: Register a custom action after Webhooks Pro fires this webhook. More infos are in the description.
- wpwh_call_action
(String) Register a custom WordPress hook callback. The value will be called as followed: do_action( $yourdefinedaction, $action_return_data, $request_data )
Customer deleted
This webhook fires as soon as a customer was deleted within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Customer updated
This webhook fires as soon as a customer was updated within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Order deleted
This webhook fires as soon as an order was deleted within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Order restored
This webhook fires as soon as an order was restored within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
Order updated
This webhook fires as soon as an order was updated within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
- Trigger on selected statuses
Select only the statuses you want to fire the trigger on. You can also choose multiple ones. If none is selected, all are triggered.
Product added to cart
This webhook fires as soon as a product was added to the cart within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected products
Select only the products you want to fire the trigger on. If none is selected, all are triggered.
Product created
This webhook fires as soon as a product was created within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Product deleted
This webhook fires as soon as a product was deleted within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Product restored
This webhook fires as soon as a product was restored within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Product review approved
This webhook fires as soon as a product has been approved within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected products
Select only the products you want to fire the trigger on. If none is selected, all are triggered.
Product updated
This webhook fires as soon as a product was updated within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- 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 secret
Set a custom secret that gets validated by Woocommerce, just as you know it from the default Woocommerce webhooks.
Product viewed
This webhook fires as soon as a product was viewed within Woocommerce.
Customizations
Down below you will find a list of possible customizations you have available within our plugin. You can use them to fire the trigger only on certain criterias.
- Trigger on selected products
Select only the products you want to fire the trigger on. If none is selected, all are triggered.
User password updated
This webhook fires after a user password is updated within a WooCommerce account page.