• user_object
  The request will send the full user object as an array. Please see https://codex.wordpress.org/Class_Reference/WP_User for more details.
• user_meta
  The user meta is also pushed to the user object. You will find it on the first layer of the object as well.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [data] => Array
        (
            [ID] => 1
            [user_login] => admin
            [user_pass] => $P$BVbptZxEcZV2yeLyYeN.O4ZeG8225d.
            [user_nicename] => admin
            [user_email] => admin@ironikus.dev
            [user_url] => 
            [user_registered] => 2018-11-06 14:19:18
            [user_activation_key] => 
            [user_status] => 0
            [display_name] => admin
        )

    [ID] => 1
    [caps] => Array
        (
            [administrator] => 1
        )

    [cap_key] => irn_capabilities
    [roles] => Array
        (
            [0] => administrator
        )

    [allcaps] => Array
        (
            [switch_themes] => 1
            [edit_themes] => 1
            [activate_plugins] => 1
            [edit_plugins] => 1
            [edit_users] => 1
            [edit_files] => 1
            [manage_options] => 1
            [moderate_comments] => 1
            [manage_categories] => 1
            [manage_links] => 1
            [upload_files] => 1
            [import] => 1
            [unfiltered_html] => 1
            [edit_posts] => 1
            [edit_others_posts] => 1
            [edit_published_posts] => 1
            [publish_posts] => 1
            [edit_pages] => 1
            [read] => 1
            [level_10] => 1
            [level_9] => 1
            [level_8] => 1
            [level_7] => 1
            [level_6] => 1
            [level_5] => 1
            [level_4] => 1
            [level_3] => 1
            [level_2] => 1
            [level_1] => 1
            [level_0] => 1
            [edit_others_pages] => 1
            [edit_published_pages] => 1
            [publish_pages] => 1
            [delete_pages] => 1
            [delete_others_pages] => 1
            [delete_published_pages] => 1
            [delete_posts] => 1
            [delete_others_posts] => 1
            [delete_published_posts] => 1
            [delete_private_posts] => 1
            [edit_private_posts] => 1
            [read_private_posts] => 1
            [delete_private_pages] => 1
            [edit_private_pages] => 1
            [read_private_pages] => 1
            [delete_users] => 1
            [create_users] => 1
            [unfiltered_upload] => 1
            [edit_dashboard] => 1
            [update_plugins] => 1
            [delete_plugins] => 1
            [install_plugins] => 1
            [update_themes] => 1
            [install_themes] => 1
            [update_core] => 1
            [list_users] => 1
            [remove_users] => 1
            [promote_users] => 1
            [edit_theme_options] => 1
            [delete_themes] => 1
            [export] => 1
            [administrator] => 1
        )

    [filter] => 
    [user_meta] => Array
        (
            [nickname] => Array
                (
                    [0] => admin
                )

            [first_name] => Array
                (
                    [0] => Jon
                )

            [last_name] => Array
                (
                    [0] => Doe
                )

            [description] => Array
                (
                    [0] => My descriptio 
                )

            [rich_editing] => Array
                (
                    [0] => true
                )

            [syntax_highlighting] => Array
                (
                    [0] => true
                )

            [comment_shortcuts] => Array
                (
                    [0] => false
                )

            [admin_color] => Array
                (
                    [0] => fresh
                )

            [use_ssl] => Array
                (
                    [0] => 0
                )

            [show_admin_bar_front] => Array
                (
                    [0] => true
                )

            [locale] => Array
                (
                    [0] => 
                )

            [irn_capabilities] => Array
                (
                    [0] => a:1:{s:13:"administrator";b:1;}
                )

            [irn_user_level] => Array
                (
                    [0] => 10
                )

            [dismissed_wp_pointers] => Array
                (
                    [0] => wp111_privacy
                )

            [show_welcome_panel] => Array
                (
                    [0] => 1
                )

            [session_tokens] => Array
                (
                    [0] => a:1:{}
                )

            [irn_dashboard_quick_press_last_post_id] => Array
                (
                    [0] => 4
                )

            [community-events-location] => Array
                (
                    [0] => a:1:{s:2:"ip";s:9:"127.0.0.0";}
                )

            [show_try_gutenberg_panel] => Array
                (
                    [0] => 0
                )

        )

)

This webhook trigger is used to send data, on the creation of a user, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Register (create_user) webhook trigger.

How to use Send Data On Register (create_user)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the user_register hook: https://developer.wordpress.org/reference/hooks/user_register/

Here is the call within our code we use to fire this trigger:

add_action( 'user_register', array( $this, 'ironikus_trigger_user_register_init' ), 10, 1 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• user_object
  The request will send the full user object as an array. Please see https://codex.wordpress.org/Class_Reference/WP_User for more details.
• user_meta
  The user meta is also pushed to the user object. You will find it on the first layer of the object as well.
• user_login
  The user login is included as well. This is the value the user used to make the login. It is also located on the first layoer of the array.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [data] => Array
        (
            [ID] => 1
            [user_login] => admin
            [user_pass] => $P$BVbptZxEcZV2yeLyYeN.O4ZeG8225d.
            [user_nicename] => admin
            [user_email] => admin@ironikus.dev
            [user_url] => 
            [user_registered] => 2018-11-06 14:19:18
            [user_activation_key] => 
            [user_status] => 0
            [display_name] => admin
        )

    [ID] => 1
    [caps] => Array
        (
            [administrator] => 1
        )

    [cap_key] => irn_capabilities
    [roles] => Array
        (
            [0] => administrator
        )

    [allcaps] => Array
        (
            [switch_themes] => 1
            [edit_themes] => 1
            [activate_plugins] => 1
            [edit_plugins] => 1
            [edit_users] => 1
            [edit_files] => 1
            [manage_options] => 1
            [moderate_comments] => 1
            [manage_categories] => 1
            [manage_links] => 1
            [upload_files] => 1
            [import] => 1
            [unfiltered_html] => 1
            [edit_posts] => 1
            [edit_others_posts] => 1
            [edit_published_posts] => 1
            [publish_posts] => 1
            [edit_pages] => 1
            [read] => 1
            [level_10] => 1
            [level_9] => 1
            [level_8] => 1
            [level_7] => 1
            [level_6] => 1
            [level_5] => 1
            [level_4] => 1
            [level_3] => 1
            [level_2] => 1
            [level_1] => 1
            [level_0] => 1
            [edit_others_pages] => 1
            [edit_published_pages] => 1
            [publish_pages] => 1
            [delete_pages] => 1
            [delete_others_pages] => 1
            [delete_published_pages] => 1
            [delete_posts] => 1
            [delete_others_posts] => 1
            [delete_published_posts] => 1
            [delete_private_posts] => 1
            [edit_private_posts] => 1
            [read_private_posts] => 1
            [delete_private_pages] => 1
            [edit_private_pages] => 1
            [read_private_pages] => 1
            [delete_users] => 1
            [create_users] => 1
            [unfiltered_upload] => 1
            [edit_dashboard] => 1
            [update_plugins] => 1
            [delete_plugins] => 1
            [install_plugins] => 1
            [update_themes] => 1
            [install_themes] => 1
            [update_core] => 1
            [list_users] => 1
            [remove_users] => 1
            [promote_users] => 1
            [edit_theme_options] => 1
            [delete_themes] => 1
            [export] => 1
            [administrator] => 1
        )

    [filter] => 
    [user_meta] => Array
        (
            [nickname] => Array
                (
                    [0] => admin
                )

            [first_name] => Array
                (
                    [0] => Jon
                )

            [last_name] => Array
                (
                    [0] => Doe
                )

            [description] => Array
                (
                    [0] => My descriptio 
                )

            [rich_editing] => Array
                (
                    [0] => true
                )

            [syntax_highlighting] => Array
                (
                    [0] => true
                )

            [comment_shortcuts] => Array
                (
                    [0] => false
                )

            [admin_color] => Array
                (
                    [0] => fresh
                )

            [use_ssl] => Array
                (
                    [0] => 0
                )

            [show_admin_bar_front] => Array
                (
                    [0] => true
                )

            [locale] => Array
                (
                    [0] => 
                )

            [irn_capabilities] => Array
                (
                    [0] => a:1:{s:13:"administrator";b:1;}
                )

            [irn_user_level] => Array
                (
                    [0] => 10
                )

            [dismissed_wp_pointers] => Array
                (
                    [0] => wp111_privacy
                )

            [show_welcome_panel] => Array
                (
                    [0] => 1
                )

            [session_tokens] => Array
                (
                    [0] => a:1:{}
                )

            [irn_dashboard_quick_press_last_post_id] => Array
                (
                    [0] => 4
                )

            [community-events-location] => Array
                (
                    [0] => a:1:{s:2:"ip";s:9:"127.0.0.0";}
                )

            [show_try_gutenberg_panel] => Array
                (
                    [0] => 0
                )

        )

    [user_login] => myLogin@test.test
)

This webhook trigger is used to send data, on login of a user, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Login (login_user) webhook trigger.

How to use Send Data On Login (login_user)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the wp_login hook: https://developer.wordpress.org/reference/hooks/wp_login/

Here is the call within our code we use to fire this trigger:

add_action( 'wp_login', array( $this, 'ironikus_trigger_user_login_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (wp_login) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• user_object
  The request will send the full user object as an array. Please see https://codex.wordpress.org/Class_Reference/WP_User for more details.
• user_meta
  The user meta is also pushed to the user object. You will find it on the first layer of the object as well.
• user_old_data
  This is the object with the previous user object as an array. You can recheck your data on it as well.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [data] => Array
        (
            [ID] => 1
            [user_login] => admin
            [user_pass] => $P$BVbptZxEcZV2yeLyYeN.O4ZeG8225d.
            [user_nicename] => admin
            [user_email] => admin@ironikus.dev
            [user_url] => 
            [user_registered] => 2018-11-06 14:19:18
            [user_activation_key] => 
            [user_status] => 0
            [display_name] => admin
        )

    [ID] => 1
    [caps] => Array
        (
            [administrator] => 1
        )

    [cap_key] => irn_capabilities
    [roles] => Array
        (
            [0] => administrator
        )

    [allcaps] => Array
        (
            [switch_themes] => 1
            [edit_themes] => 1
            [activate_plugins] => 1
            [edit_plugins] => 1
            [edit_users] => 1
            [edit_files] => 1
            [manage_options] => 1
            [moderate_comments] => 1
            [manage_categories] => 1
            [manage_links] => 1
            [upload_files] => 1
            [import] => 1
            [unfiltered_html] => 1
            [edit_posts] => 1
            [edit_others_posts] => 1
            [edit_published_posts] => 1
            [publish_posts] => 1
            [edit_pages] => 1
            [read] => 1
            [level_10] => 1
            [level_9] => 1
            [level_8] => 1
            [level_7] => 1
            [level_6] => 1
            [level_5] => 1
            [level_4] => 1
            [level_3] => 1
            [level_2] => 1
            [level_1] => 1
            [level_0] => 1
            [edit_others_pages] => 1
            [edit_published_pages] => 1
            [publish_pages] => 1
            [delete_pages] => 1
            [delete_others_pages] => 1
            [delete_published_pages] => 1
            [delete_posts] => 1
            [delete_others_posts] => 1
            [delete_published_posts] => 1
            [delete_private_posts] => 1
            [edit_private_posts] => 1
            [read_private_posts] => 1
            [delete_private_pages] => 1
            [edit_private_pages] => 1
            [read_private_pages] => 1
            [delete_users] => 1
            [create_users] => 1
            [unfiltered_upload] => 1
            [edit_dashboard] => 1
            [update_plugins] => 1
            [delete_plugins] => 1
            [install_plugins] => 1
            [update_themes] => 1
            [install_themes] => 1
            [update_core] => 1
            [list_users] => 1
            [remove_users] => 1
            [promote_users] => 1
            [edit_theme_options] => 1
            [delete_themes] => 1
            [export] => 1
            [administrator] => 1
        )

    [filter] => 
    [user_meta] => Array
        (
            [nickname] => Array
                (
                    [0] => admin
                )

            [first_name] => Array
                (
                    [0] => Jon
                )

            [last_name] => Array
                (
                    [0] => Doe
                )

            [description] => Array
                (
                    [0] => My descriptio 
                )

            [rich_editing] => Array
                (
                    [0] => true
                )

            [syntax_highlighting] => Array
                (
                    [0] => true
                )

            [comment_shortcuts] => Array
                (
                    [0] => false
                )

            [admin_color] => Array
                (
                    [0] => fresh
                )

            [use_ssl] => Array
                (
                    [0] => 0
                )

            [show_admin_bar_front] => Array
                (
                    [0] => true
                )

            [locale] => Array
                (
                    [0] => 
                )

            [irn_capabilities] => Array
                (
                    [0] => a:1:{s:13:"administrator";b:1;}
                )

            [irn_user_level] => Array
                (
                    [0] => 10
                )

            [dismissed_wp_pointers] => Array
                (
                    [0] => wp111_privacy
                )

            [show_welcome_panel] => Array
                (
                    [0] => 1
                )

            [session_tokens] => Array
                (
                    [0] => a:1:{}
                )

            [irn_dashboard_quick_press_last_post_id] => Array
                (
                    [0] => 4
                )

            [community-events-location] => Array
                (
                    [0] => a:1:{s:2:"ip";s:9:"127.0.0.0";}
                )

            [show_try_gutenberg_panel] => Array
                (
                    [0] => 0
                )

        )

    [user_old_data] => Array
        (
        )

)

This webhook trigger is used to send data, on the update of a user, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On User Update (update_user) webhook trigger.

How to use Send Data On User Update (update_user)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the profile_update hook: https://developer.wordpress.org/reference/hooks/profile_update/

Here is the call within our code we use to fire this trigger:

add_action( 'profile_update', array( $this, 'ironikus_trigger_user_update_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (profile_update) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• user_id
  The ID of the deleted user
• reassign
  ID of the user to reassign posts and links to. Default null, for no reassignment.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [user_id] => 1234
    [reassign] => 1235
)

This webhook trigger is used to send data, after deletion of a user, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On User Deletion (deleted_user) webhook trigger.

How to use Send Data On User Deletion (deleted_user)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the deleted_user hook: https://developer.wordpress.org/reference/hooks/deleted_user/

Important: If case have a multisite network set up, this webhook only fires if you delete the user from the whole network and not only from one sub site.

Here is the call within our code we use to fire this trigger:

add_action( 'deleted_user', array( $this, 'ironikus_trigger_deleted_user_init' ), 10, 3 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (deleted_user) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• post_id
  The post id of the created post.
• post
  The whole post object with all of its values
• post_meta
  An array of the whole post meta data.
• post_thumbnail
  The full featured image/thumbnail URL in the full size.
• post_permalink
  The permalink of the currently given post.
• taxonomies
  (Array) An array containing the taxonomy data of the assigned taxonomies. Custom Taxonomies are supported too.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [post_id] => 1234
    [post] => Array
        (
            [ID] => 1
            [post_author] => 1
            [post_date] => 2018-11-06 14:19:18
            [post_date_gmt] => 2018-11-06 14:19:18
            [post_content] => Welcome to WordPress. This is your first post. Edit or delete it, then start writing!
            [post_title] => Hello world!
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => hello-world
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2018-11-06 14:19:18
            [post_modified_gmt] => 2018-11-06 14:19:18
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://mydomain.dev/?p=1
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 1
            [filter] => raw
        )

    [post_meta] => Array
        (
            [key_0] => Array
                (
                    [0] => 0.00
                )

            [key_1] => Array
                (
                    [0] => 0
                )

            [key_2] => Array
                (
                    [0] => 1
                )

            [key_3] => Array
                (
                    [0] => 148724528:1
                )

            [key_4] => Array
                (
                    [0] => 10.00
                )

            [key_5] => Array
                (
                    [0] => a:0:{}
                )

        )

    [post_thumbnail] => https://mydomain.com/images/image.jpg
    [post_permalink] => https://mydomain.com/the-post/permalink
    [taxonomies] => Array
        (
            [category] => Array
                (
                    [uncategorized] => Array
                        (
                            [term_id] => 1
                            [name] => Uncategorized
                            [slug] => uncategorized
                            [term_group] => 0
                            [term_taxonomy_id] => 1
                            [taxonomy] => category
                            [description] => 
                            [parent] => 10
                            [count] => 7
                            [filter] => raw
                        )

                    [secondcat] => Array
                        (
                            [term_id] => 2
                            [name] => Second Cat
                            [slug] => secondcat
                            [term_group] => 0
                            [term_taxonomy_id] => 2
                            [taxonomy] => category
                            [description] => 
                            [parent] => 1
                            [count] => 1
                            [filter] => raw
                        )

                )

        )

)

This webhook trigger is used to send data, on the creation of a post, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On New Post (post_create) webhook trigger.

How to use Send Data On New Post (post_create)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the add_attachment hook and the wp_insert_post hook:
Add attachment: https://developer.wordpress.org/reference/hooks/add_attachment/
Insert post: https://developer.wordpress.org/reference/hooks/wp_insert_post/

This webhook fires on two different hooks since attachments (which are technically posts as well), use a custom logic.

Here are the calls within our code we use to fire this trigger:

add_action( 'add_attachment', array( $this, 'ironikus_trigger_post_create_attachment_init' ), 10, 1 );
add_action( 'wp_insert_post', array( $this, 'ironikus_trigger_post_create_init' ), 10, 3 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (wp_insert_post/add_attachment) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• post_id
  The post id of the updated post.
• post
  The whole post object with all of its values
• post_meta
  An array of the whole post meta data.
• post_thumbnail
  The full featured image/thumbnail URL in the full size.
• post_permalink
  The permalink of the currently given post.
• taxonomies
  (Array) An array containing the taxonomy data of the assigned taxonomies. Custom Taxonomies are supported too.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [post_id] => 1234
    [post] => Array
        (
            [ID] => 1
            [post_author] => 1
            [post_date] => 2018-11-06 14:19:18
            [post_date_gmt] => 2018-11-06 14:19:18
            [post_content] => Welcome to WordPress. This is your first post. Edit or delete it, then start writing!
            [post_title] => Hello world!
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => hello-world
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2018-11-06 14:19:18
            [post_modified_gmt] => 2018-11-06 14:19:18
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://mydomain.dev/?p=1
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 1
            [filter] => raw
        )

    [post_meta] => Array
        (
            [key_0] => Array
                (
                    [0] => 0.00
                )

            [key_1] => Array
                (
                    [0] => 0
                )

            [key_2] => Array
                (
                    [0] => 1
                )

            [key_3] => Array
                (
                    [0] => 148724528:1
                )

            [key_4] => Array
                (
                    [0] => 10.00
                )

            [key_5] => Array
                (
                    [0] => a:0:{}
                )

        )

    [post_thumbnail] => https://mydomain.com/images/image.jpg
    [post_permalink] => https://mydomain.com/the-post/permalink
    [taxonomies] => Array
        (
            [category] => Array
                (
                    [uncategorized] => Array
                        (
                            [term_id] => 1
                            [name] => Uncategorized
                            [slug] => uncategorized
                            [term_group] => 0
                            [term_taxonomy_id] => 1
                            [taxonomy] => category
                            [description] => 
                            [parent] => 10
                            [count] => 7
                            [filter] => raw
                        )

                    [secondcat] => Array
                        (
                            [term_id] => 2
                            [name] => Second Cat
                            [slug] => secondcat
                            [term_group] => 0
                            [term_taxonomy_id] => 2
                            [taxonomy] => category
                            [description] => 
                            [parent] => 1
                            [count] => 1
                            [filter] => raw
                        )

                )

        )

)

This webhook trigger is used to send data, on the update of a post, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Post Update (post_update) webhook trigger.

How to use Send Data On Post Update (post_update)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the attachment_updated hook and the wp_insert_post hook:
Attachment updated: https://developer.wordpress.org/reference/hooks/attachment_updated/
Update post: https://developer.wordpress.org/reference/hooks/wp_insert_post/

This webhook fires on two different hooks since attachments (which are technically posts as well), use a custom logic.
The wp_insert_post hook is fired as well for the post update - we diversify between them through the third parsed parameter called $update, which returns true or false.

Here are the calls within our code we use to fire this trigger:

add_action( 'wp_insert_post', array( $this, 'ironikus_trigger_post_update_init' ), 10, 3 );
add_action( 'attachment_updated', array( $this, 'ironikus_trigger_post_update_attachment_init' ), 10, 3 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (wp_insert_post/attachment_updated) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• post_id
  The post id of the deleted post.
• post
  Thefull post data from get_post().
• post_meta
  The full post meta of the post.
• post_thumbnail
  The full featured image/thumbnail URL in the full size.
• post_permalink
  The permalink of the currently given post.
• taxonomies
  (Array) An array containing the taxonomy data of the assigned taxonomies. Custom Taxonomies are supported too.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [post_id] => 12345
    [post] => Array
        (
            [ID] => 1
            [post_author] => 1
            [post_date] => 2018-11-06 14:19:18
            [post_date_gmt] => 2018-11-06 14:19:18
            [post_content] => Welcome to WordPress. This is your first post. Edit or delete it, then start writing!
            [post_title] => Hello world!
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => hello-world
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2018-11-06 14:19:18
            [post_modified_gmt] => 2018-11-06 14:19:18
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://mydomain.dev/?p=1
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 1
            [filter] => raw
        )

    [post_meta] => Array
        (
            [key_0] => Array
                (
                    [0] => 0.00
                )

            [key_1] => Array
                (
                    [0] => 0
                )

            [key_2] => Array
                (
                    [0] => 1
                )

            [key_3] => Array
                (
                    [0] => 148724528:1
                )

            [key_4] => Array
                (
                    [0] => 10.00
                )

            [key_5] => Array
                (
                    [0] => a:0:{}
                )

        )

    [post_thumbnail] => https://mydomain.com/images/image.jpg
    [post_permalink] => https://mydomain.com/the-post/permalink
    [taxonomies] => Array
        (
            [category] => Array
                (
                    [uncategorized] => Array
                        (
                            [term_id] => 1
                            [name] => Uncategorized
                            [slug] => uncategorized
                            [term_group] => 0
                            [term_taxonomy_id] => 1
                            [taxonomy] => category
                            [description] => 
                            [parent] => 10
                            [count] => 7
                            [filter] => raw
                        )

                    [secondcat] => Array
                        (
                            [term_id] => 2
                            [name] => Second Cat
                            [slug] => secondcat
                            [term_group] => 0
                            [term_taxonomy_id] => 2
                            [taxonomy] => category
                            [description] => 
                            [parent] => 1
                            [count] => 1
                            [filter] => raw
                        )

                )

        )

)

This webhook trigger is used to send data, on the deletion of a post, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Post Deletion (post_delete) webhook trigger.

How to use Send Data On Post Deletion (post_delete)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the delete_post hook: https://developer.wordpress.org/reference/hooks/delete_post/

Here is the call within our code we use to fire this trigger:

add_action( 'delete_post', array( $this, 'ironikus_trigger_post_delete_init' ), 10, 1 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (delete_post) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• post_id
  The post id of the trashed post.
• post
  Thefull post data from get_post().
• post_meta
  The full post meta of the post.
• post_thumbnail
  The full featured image/thumbnail URL in the full size.
• post_permalink
  The permalink of the currently given post.
• taxonomies
  (Array) An array containing the taxonomy data of the assigned taxonomies. Custom Taxonomies are supported too.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [post_id] => 12345
    [post] => Array
        (
            [ID] => 1
            [post_author] => 1
            [post_date] => 2018-11-06 14:19:18
            [post_date_gmt] => 2018-11-06 14:19:18
            [post_content] => Welcome to WordPress. This is your first post. Edit or delete it, then start writing!
            [post_title] => Hello world!
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => hello-world
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2018-11-06 14:19:18
            [post_modified_gmt] => 2018-11-06 14:19:18
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://mydomain.dev/?p=1
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 1
            [filter] => raw
        )

    [post_meta] => Array
        (
            [key_0] => Array
                (
                    [0] => 0.00
                )

            [key_1] => Array
                (
                    [0] => 0
                )

            [key_2] => Array
                (
                    [0] => 1
                )

            [key_3] => Array
                (
                    [0] => 148724528:1
                )

            [key_4] => Array
                (
                    [0] => 10.00
                )

            [key_5] => Array
                (
                    [0] => a:0:{}
                )

        )

    [post_thumbnail] => https://mydomain.com/images/image.jpg
    [post_permalink] => https://mydomain.com/the-post/permalink
    [taxonomies] => Array
        (
            [category] => Array
                (
                    [uncategorized] => Array
                        (
                            [term_id] => 1
                            [name] => Uncategorized
                            [slug] => uncategorized
                            [term_group] => 0
                            [term_taxonomy_id] => 1
                            [taxonomy] => category
                            [description] => 
                            [parent] => 10
                            [count] => 7
                            [filter] => raw
                        )

                    [secondcat] => Array
                        (
                            [term_id] => 2
                            [name] => Second Cat
                            [slug] => secondcat
                            [term_group] => 0
                            [term_taxonomy_id] => 2
                            [taxonomy] => category
                            [description] => 
                            [parent] => 1
                            [count] => 1
                            [filter] => raw
                        )

                )

        )

)

This webhook trigger is used to send data, on trashing a post, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Post Trash (post_trash) webhook trigger.

How to use Send Data On Post Trash (post_trash)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the trashed_post hook: https://developer.wordpress.org/reference/hooks/trashed_post/

Here is the call within our code we use to fire this trigger:

add_action( 'trashed_post', array( $this, 'ironikus_trigger_post_trash_init' ), 10, 1 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (trashed_post) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. Important: Please note that in case this trigger does not fire, either your post type does not support the trash status, or automatic cleaning time is reached.
2. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
3. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
4. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
5. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [0] => Your very own data construct.
)

This webhook trigger is used to send data, on a custom action, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On Custom Action (custom_action) webhook trigger.

How to use Send Data On Custom Action (custom_action)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.
6. That's it for the visual setup. Now you need to add a custom WordPress action call within your code to trigger this trigger. Down below you will find more details.

When does this trigger fire?

This trigger is registered on the wp_webhooks_send_to_webhook_filter hook, which isn't fired by default.

Here is the call within our code we use to fire this trigger:

add_filter( 'wp_webhooks_send_to_webhook_filter', array( $this, 'wp_webhooks_send_to_webhook_action_filter' ), 10, 4 );

IMPORTANT: Please note that this webhook trigger is fired immediately after the apply_filters( 'wp_webhooks_send_to_webhook_filter' ) function is called.

How to fire this trigger?

You can fire the trigger wherever you want within your PHP code. The only necessity is, that our plugin is fully initialized by WordPress (That means that our plugin has to be fully loaded before the trigger works). Here is a code example:

$custom_data = array(
	'data_1' => 'value'
);
$webhook_names = array(
	'15792546059992909'
);
$http_args = array(
	'blocking' => true //Set this to true to receive the response
);

$response = apply_filters( 'wp_webhooks_send_to_webhook_filter', array(), $custom_data, $webhook_names, $http_args );

The apply_filters() function accepts five parameters, which are explained down below:

1. 'wp_webhooks_send_to_webhook' (string)
   This is our trigger identifier so that our plugin knows when to fire the webhook. Please don't change this value.
2. array() (array)
   An array containing data we will return to the $response variable. Please note that this value will be dynamically filled with all the response data from the sent webhooks. Values you pass into this empty array will be returned as well, except they get overwritten by the dynamic values.
3. $custom_data (array)
   This variable contains an array of data you want to send over to each of the webhook URL's (payload). Depending on your Webhook URL specific settings, it will be sent in different formats (default JSON).
4. $webhook_names (array)
   This variable contains an array with Webhook URLs this trigger should fire on. To add a trigger, add the Webhook Name to the array. If you don't send over the this argument at all, all webhook URL's for this webhook trigger will be triggered.
5. $http_args (array)
   This variable contains an array with further arguments of the http request used with the wp_safe_remote_request function. Standard use-cases of it are the sslverify and the blocking keys.

Tipps

1. You can fetch the response of each of the sent webhooks requests from the $response variable. You can determine them based on the webhook name, which is used as a key.
2. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
3. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
4. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
5. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• first_name
  (String) The first name of the customer.
• last_name
  (String) The last name of the customer.
• id
  (String) The unique id of the customer. (This is not the user id)
• purchase_count
  (Integer) The number of purchases of the customer.
• purchase_value
  (Float) The value of all purchases of the customer.
• email
  (String) The main email of the customer.
• emails
  (Array) Additional emails of the customer.
• name
  (String) The full name of the customer.
• date_created
  (String) The date and time of the user creation in SQL format.
• payment_ids
  (String) A comme-separated list of payment ids.
• user_id
  (String) The user id of the customer.
• notes
  (String) Additional ntes given by the customer.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [user_id] => 1234
    [name] => John Doe
    [first_name] => John
    [last_name] => Doe
    [email] => johndoe123@test.com
    [payment_ids] => 2345
    [purchase_value] => 23.5
    [date_created] => 2020-12-01 05:32:13
    [purchase_count] => 1
    [notes] => 
)

This webhook trigger is used to send data, on creation of a customer, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD New Customer (edd_new_customer) webhook trigger.

How to use Send Data On EDD New Customer (edd_new_customer)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_customer_post_create hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_customer_post_create', array( $this, 'ironikus_trigger_edd_new_customer' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• first_name
  (String) The first name of the customer.
• last_name
  (String) The last name of the customer.
• id
  (String) The unique id of the customer. (This is not the user id)
• purchase_count
  (Integer) The number of purchases of the customer.
• purchase_value
  (Float) The value of all purchases of the customer.
• email
  (String) The main email of the customer.
• emails
  (Array) Additional emails of the customer.
• name
  (String) The full name of the customer.
• date_created
  (String) The date and time of the user creation in SQL format.
• payment_ids
  (String) A comme-separated list of payment ids.
• user_id
  (String) The user id of the customer.
• notes
  (String) Additional ntes given by the customer.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [user_id] => 1234
    [name] => John Doe
    [first_name] => John
    [last_name] => Doe
    [email] => johndoe123@test.com
    [payment_ids] => 2345
    [purchase_value] => 23.5
    [date_created] => 2020-12-01 05:32:13
    [purchase_count] => 1
    [notes] => 
)

This webhook trigger is used to send data, on update of a customer, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD Customer Update (edd_update_customer) webhook trigger.

How to use Send Data On EDD Customer Update (edd_update_customer)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_customer_post_update hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_customer_post_update', array( $this, 'wpwh_trigger_edd_update_customer' ), 10, 3 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• ID
  (Integer) The payment id.
• key
  (String) The unique payment key.
• subtotal
  (Float) The subtotal of the payment.
• tax
  (String) The tax amount of the payment.
• fees
  (Array) Additional payment fees of the payment.
• total
  (Integer) The total amount of the payment.
• gateway
  (String) The chosen payment gateway of the payment.
• email
  (String) The customer email that was used for the payment the payment.
• date
  (String) The date (in SQL format) of the payment creation.
• products
  (Array) An array of al products that are included within the payment. Please check the example below for further details.
• discount_codes
  (String) A comma separated list of applied coupon codes.
• first_name
  (String) The first name of the customer.
• last_name
  (String) The last name of the customer.
• transaction_id
  (Integer) The transaction id of the payment.
• billing_address
  (Array) The billing adress with all its values. Please check the example below for further details.
• shipping_address
  (Array) The shipping adress with all its values. Please check the example below for further details.
• metadata
  (Array) An array of all available meta fields.
• new_status
  (String) The new status of the payment.
• old_status
  (String) The prrevious status of the payment.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [ID] => 123
    [key] => c36bc5d3315cde89ce18a19bb6a1d559
    [subtotal] => 39
    [tax] => 0
    [fees] => Array
        (
        )

    [total] => 39
    [gateway] => manual
    [email] => johndoe123@test.com
    [date] => 2020-04-23 09:16:00
    [products] => Array
        (
            [0] => Array
                (
                    [Product] => Demo Download
                    [Subtotal] => 39
                    [Tax] => 0.00
                    [Discount] => 0
                    [Price] => 39
                    [PriceName] => Single Site
                    [Quantity] => 1
                )

        )

    [discount_codes] => none
    [first_name] => Jon
    [last_name] => Doe
    [transaction_id] => 123
    [billing_address] => Array
        (
            [line1] => Street 1
            [line2] => Line 2
            [city] => My Fair City
            [country] => US
            [state] => MD
            [zip] => 55555
        )

    [shipping_address] => Array
        (
            [address] => Street 1
            [Address2] => Line 2
            [city] => My Fair City
            [country] => US
            [state] => MD
            [zip] => 55555
        )

    [metadata] => Array
        (
            [_edd_payment_tax_rate] => Array
                (
                    [0] => 0
                )

            [_edd_complete_actions_run] => Array
                (
                    [0] => 8763342154
                )

        )

    [new_status] => publish
    [old_status] => pending
)

This webhook trigger is used to send data, on creation of a payment or any other payment status change, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD Payments (edd_payments) webhook trigger.

How to use Send Data On EDD Payments (edd_payments)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_update_payment_status hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_update_payment_status', array( $this, 'wpwh_trigger_edd_payments_init' ), 10, 3 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you only want to fire the webhook on specific payment statuses, you can select them within the single webhook URL settings. Simply select the payment statuses you want to fire the webhook on and all others are ignored.
2. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
3. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
4. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
5. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• file_name
  (String) The file name without the file extension.
• file
  (String) The full file URL.
• email
  (String) The email of the customer who started the download.
• product
  (String) The product name wich contains the download.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [file_name] => sample_file_name
    [file] => https://wp-webhooks.com/pro/sample/file/url/file.zip
    [email] => jane@test.com
    [product] => Sample Product
)

This webhook trigger is used to send data as soon as a file is downloaded, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD File Downloads (edd_file_downloaded) webhook trigger.

How to use Send Data On EDD File Downloads (edd_file_downloaded)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_process_verified_download hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_process_verified_download', array( $this, 'wpwh_trigger_edd_file_downloaded' ), 10, 4 );

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• id
  (String) The subscription id.
• customer_id
  (String) The id of the related customer.
• period
  (String) The subcription period.
• initial_amount
  (String) The initial price amount.
• initial_tax_rate
  (String) The initial tax rate.
• initial_tax
  (String) The initial tax amount.
• recurring_amount
  (String) The recurring price amount.
• recurring_tax_rate
  (String) The recurring tax rate.
• recurring_tax
  (String) The recurring tax amount.
• bill_times
  (String) The times the customer gets billed.
• transaction_id
  (String) The transaction id.
• parent_payment_id
  (String) The parent payment id in case the payment is recurring.
• product_id
  (String) The related product id for this subscription.
• price_id
  (String) The price id in case it is a variation.
• created
  (String) The date and time of creation (in SQL format).
• expiration
  (String) The date and time of expiration (in SQL format).
• trial_period
  (String) The trial period.
• status
  (String) The current subscription status.
• profile_id
  (String) The unique profile id.
• gateway
  (String) The chosen gateway for this subscription.
• customer
  (Array) An array with all of the customer information. Please see the example down below for further details.
• notes
  (Array) An array with all the subscription notes.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [id] => 1
    [customer_id] => 1
    [period] => year
    [initial_amount] => 9.97
    [initial_tax_rate] => 
    [initial_tax] => 
    [recurring_amount] => 9.97
    [recurring_tax_rate] => 
    [recurring_tax] => 
    [bill_times] => 2
    [transaction_id] => 
    [parent_payment_id] => 706
    [product_id] => 285
    [price_id] => 0
    [created] => 2020-04-23 16:29:36
    [expiration] => 2020-04-22 23:59:59
    [trial_period] => 
    [status] => completed
    [profile_id] => xxxxxxxx
    [gateway] => manual
    [customer] => Array
        (
            [id] => 1
            [purchase_count] => 2
            [purchase_value] => 87.97
            [email] => johndoe123@test.com
            [emails] => Array
                (
                    [0] => johndoe123more@test.com
                )

            [name] => John Doe
            [date_created] => 2019-02-26 07:32:56
            [payment_ids] => 695,706
            [user_id] => 1
        )

    [notes] => Array
        (
            [0] => April 23, 2020 16:32:05 - Status changed from completed to failing by admin
            [1] => April 23, 2020 16:30:59 - Status changed from active to completed by admin
            [2] => April 23, 2020 16:30:45 - Status changed from expired to active by admin
        )

)

This webhook trigger is used to send data, on any subscription status change, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD Subscriptions (edd_subscriptions) webhook trigger.

How to use Send Data On EDD Subscriptions (edd_subscriptions)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the following hooks of Easy Digital Downloads

• edd_subscription_post_create
• edd_subscription_post_renew
• edd_subscription_completed
• edd_subscription_expired
• edd_subscription_failing
• edd_subscription_cancelled

Here are the calls within our code we use to fire this trigger:

add_action( 'edd_subscription_post_create', array( $this, 'wpwh_trigger_edd_subscriptions_map_create' ), 10, 2 );
add_action( 'edd_subscription_post_renew', array( $this, 'wpwh_trigger_edd_subscriptions_map_renew' ), 10, 3 );
add_action( 'edd_subscription_completed', array( $this, 'wpwh_trigger_edd_subscriptions_map_completed' ), 10, 2 );
add_action( 'edd_subscription_expired', array( $this, 'wpwh_trigger_edd_subscriptions_map_expired' ), 10, 2 );
add_action( 'edd_subscription_failing', array( $this, 'wpwh_trigger_edd_subscriptions_map_failing' ), 10, 2 );
add_action( 'edd_subscription_cancelled', array( $this, 'wpwh_trigger_edd_subscriptions_map_cancelled' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you only want to fire the webhook on specific subscription statuses, you can select them within the single webhook URL settings. Simply select the subscription statuses you want to fire the webhook on and all others are ignored.
2. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
3. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
4. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
5. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• payment
  (Array) The payment data. For further details, please refer to the example down below.
• subscription
  (Array) The subscription data. For further details, please refer to the example down below.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [payment] => Array
        (
            [ID] => 123
            [key] => c36bc5d3315cde89ce18a19bb6a1d559
            [subtotal] => 39
            [tax] => 0
            [fees] => Array
                (
                )

            [total] => 39
            [gateway] => manual
            [email] => johndoe123@test.com
            [date] => 2020-04-23 09:16:00
            [products] => Array
                (
                    [0] => Array
                        (
                            [Product] => Demo Download
                            [Subtotal] => 39
                            [Tax] => 0.00
                            [Discount] => 0
                            [Price] => 39
                            [PriceName] => Single Site
                            [Quantity] => 1
                        )

                )

            [discount_codes] => none
            [first_name] => Jon
            [last_name] => Doe
            [transaction_id] => 123
            [billing_address] => Array
                (
                    [line1] => Street 1
                    [line2] => Line 2
                    [city] => My Fair City
                    [country] => US
                    [state] => MD
                    [zip] => 55555
                )

            [shipping_address] => Array
                (
                    [address] => Street 1
                    [Address2] => Line 2
                    [city] => My Fair City
                    [country] => US
                    [state] => MD
                    [zip] => 55555
                )

            [metadata] => Array
                (
                    [_edd_payment_tax_rate] => Array
                        (
                            [0] => 0
                        )

                    [_edd_complete_actions_run] => Array
                        (
                            [0] => 8763342154
                        )

                )

            [new_status] => publish
            [old_status] => pending
        )

    [subscription] => Array
        (
            [id] => 183
            [customer_id] => 36
            [period] => month
            [initial_amount] => 16.47
            [recurring_amount] => 10.98
            [bill_times] => 0
            [transaction_id] => 
            [parent_payment_id] => 845
            [product_id] => 8
            [created] => 2016-06-13 13:47:24
            [expiration] => 2016-07-13 23:59:59
            [status] => pending
            [profile_id] => ppe-4e3ca7d1c017e0ea8b24ff72d1d23022-8
            [gateway] => paypalexpress
            [customer] => Array
                (
                    [id] => 36
                    [purchase_count] => 2
                    [purchase_value] => 32.93
                    [email] => jane@test.com
                    [emails] => Array
                        (
                            [0] => jane@test.com
                        )

                    [name] => Jane Doe
                    [date_created] => 2016-06-13 13:19:50
                    [payment_ids] => 842,845,846
                    [user_id] => 1
                    [notes] => Array
                        (
                            [0] => These are notes about the customer
                        )

                )

            [user_id] => 24
        )

)

This webhook trigger is used to send data once a new subscription payment is is made, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD New Subscription Payment (edd_subscription_payment) webhook trigger.

How to use Send Data On EDD New Subscription Payment (edd_subscription_payment)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_recurring_add_subscription_payment hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_recurring_add_subscription_payment', array( $this, 'wpwh_trigger_edd_subscription_payment_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• ID
  (Integer) The license id.
• key
  (String) The license key.
• customer_email
  (String) The email of the customer.
• customer_name
  (String) The full customer name.
• product_id
  (String) The id of the product.
• product_name
  (String) The full product name.
• activation_limit
  (Integer) The activation limit.
• activation_count
  (Integer) The number of total activations.
• activated_urls
  (String) A list of activated URLs.
• expiration
  (String) The expiration date in SQL format.
• is_lifetime
  (Integer) The number 1 or 0 if it is a lifetime.
• status
  (String) The current license status.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [ID] => 1234
    [key] => 736b31fec1ecb01c28b51a577bb9c2b3
    [customer_name] => Jane Doe
    [customer_email] => jane@test.com
    [product_id] => 4321
    [product_name] => Sample Product
    [activation_limit] => 1
    [activation_count] => 1
    [activated_urls] => sample.com
    [expiration] => 2020-12-01 17:32:13
    [is_lifetime] => 0
    [status] => active
)

This webhook trigger is used to send data once a license status change, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD License Status Updates (edd_license_status) webhook trigger.

How to use Send Data On EDD License Status Updates (edd_license_status)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_sl_post_set_status hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_sl_post_set_status', array( $this, 'wpwh_trigger_edd_license_status_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you only want to fire the webhook on specific license statuses, you can select them within the single webhook URL settings. Simply select the license statuses you want to fire the webhook on and all others are ignored.
2. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
3. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
4. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
5. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• ID
  (Integer) The license id.
• key
  (String) The license key.
• customer_email
  (String) The email of the customer.
• customer_name
  (String) The full customer name.
• product_id
  (String) The id of the product.
• product_name
  (String) The full product name.
• activation_limit
  (Integer) The activation limit.
• activation_count
  (Integer) The number of total activations.
• activated_urls
  (String) A list of activated URLs.
• expiration
  (String) The expiration date in SQL format.
• is_lifetime
  (Integer) The number 1 or 0 if it is a lifetime.
• status
  (String) The current license status.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [ID] => 1234
    [key] => 736b31fec1ecb01c28b51a577bb9c2b3
    [customer_name] => Jane Doe
    [customer_email] => jane@test.com
    [product_id] => 4321
    [product_name] => Sample Product
    [activation_limit] => 1
    [activation_count] => 1
    [activated_urls] => sample.com
    [expiration] => 2020-12-01 17:32:13
    [is_lifetime] => 0
    [status] => active
)

This webhook trigger is used to send data once a license is activated, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD License Activation (edd_license_activation) webhook trigger.

How to use Send Data On EDD License Activation (edd_license_activation)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_sl_activate_license hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_sl_activate_license', array( $this, 'wpwh_trigger_edd_license_activation_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• ID
  (Integer) The license id.
• key
  (String) The license key.
• customer_email
  (String) The email of the customer.
• customer_name
  (String) The full customer name.
• product_id
  (String) The id of the product.
• product_name
  (String) The full product name.
• activation_limit
  (Integer) The activation limit.
• activation_count
  (Integer) The number of total activations.
• activated_urls
  (String) A list of activated URLs.
• expiration
  (String) The expiration date in SQL format.
• is_lifetime
  (Integer) The number 1 or 0 if it is a lifetime.
• status
  (String) The current license status.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [ID] => 1234
    [key] => 736b31fec1ecb01c28b51a577bb9c2b3
    [customer_name] => Jane Doe
    [customer_email] => jane@test.com
    [product_id] => 4321
    [product_name] => Sample Product
    [activation_limit] => 1
    [activation_count] => 1
    [activated_urls] => sample.com
    [expiration] => 2020-12-01 17:32:13
    [is_lifetime] => 0
    [status] => inactive
)

This webhook trigger is used to send data once a license is deactivated, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD License Deactivation (edd_license_deactivate) webhook trigger.

How to use Send Data On EDD License Deactivation (edd_license_deactivate)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_sl_deactivate_license hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_sl_deactivate_license', array( $this, 'wpwh_trigger_edd_license_deactivate_init' ), 10, 2 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• ID
  (Integer) The license id.
• key
  (String) The license key.
• customer_email
  (String) The email of the customer.
• customer_name
  (String) The full customer name.
• product_id
  (String) The id of the product.
• product_name
  (String) The full product name.
• activation_limit
  (Integer) The activation limit.
• activation_count
  (Integer) The number of total activations.
• activated_urls
  (String) A list of activated URLs.
• expiration
  (String) The expiration date in SQL format.
• is_lifetime
  (Integer) The number 1 or 0 if it is a lifetime.
• status
  (String) The current license status.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [ID] => 1234
    [key] => 736b31fec1ecb01c28b51a577bb9c2b3
    [customer_name] => Jane Doe
    [customer_email] => jane@test.com
    [product_id] => 4321
    [product_name] => Sample Product
    [activation_limit] => 1
    [activation_count] => 1
    [activated_urls] => sample.com
    [expiration] => 2020-12-01 17:32:13
    [is_lifetime] => 0
    [status] => inactive
)

This webhook trigger is used to send data once a license is activated, within Easy Digital Downloads, to one or multiple given webhook URL's.
This description is uniquely made for the Send Data On EDD License Creation (edd_license_creation) webhook trigger.

How to use Send Data On EDD License Creation (edd_license_creation)

1. To get started, you need to add your recieving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For a better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you are able to recieve data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the edd_sl_store_license hook of Easy Digital Downloads

Here is the call within our code we use to fire this trigger:

add_action( 'edd_sl_store_license', array( $this, 'wpwh_trigger_edd_license_creation_init' ), 10, 4 );

IMPORTANT: Please note that this webhook does not fire, by default, once the actual trigger (user_register) is fired, but as soon as the WordPress shutdown hook fires. This is important since we want to allow third-party plugins to make their relevant changes before we send over the data. To deactivate this functionality, please go to our Settings and activate the Deactivate Post Trigger Delay settings item. This results in the webhooks firing straight after the initial hook is called.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• to
  (String) A string containing one or multiple emails (as a comma-separated list) of the receivers of the email.
• subject
  (String) The subject of the email.
• message
  (String) The main mesage (body) of the email.
• headers
  (Array) Further data about the outgoing email.
• attachments
  (Array) An array of given email attachments.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [to] => test@test.demo
    [subject] => This is the subject
    [message] => This is a <strong>HTML</strong> message!
    [headers] => Array
        (
            [0] => Content-Type: text/html; charset=UTF-8
            [1] => From: Sender Name 
            [2] => Cc: Receiver Name 
            [3] => Cc: onlyemail@someemail.demo
            [4] => Bcc: bccmail@someemail.demo
            [5] => Reply-To: Reply Name 
        )

    [attachments] => Array
        (
            [0] => /Your/full/server/path/wp-content/uploads/2020/06/my-custom-file.jpg
            [1] => /Your/full/server/path/wp-content/uploads/2020/06/another-custom-file.jpg
        )

)

This webhook trigger is used to send data once an email is sent from your WordPress website via the wp_mail() function.
This description is uniquely made for the Send Data On Outgoing Email (send_email) webhook trigger.

How to use Send Data On Outgoing Email (send_email)

1. To get started, you need to add your receiving URL endpoint, that accepts webhook requests, from the third-party provider or service you want to use.
2. Once you have this URL, please place it into the Webhook URL field above.
3. For better identification of the webhook URL, we recommend to also fill the Webhook Name field. This field will be used as the slug for your webhook URL. In case you leave it empty, we will automatically generate a random number as an identifier.
4. After you added your Webhook URL, press the Add button to finish adding the entry.
5. That's it! Now you can receive data on the URL once the trigger fires.
6. Next to the Webhook URL, you will find a settings item, which you can use to customize the payload/request.

When does this trigger fire?

This trigger is registered on the wp_mail hook: https://developer.wordpress.org/reference/hooks/wp_mail/

Here is the call within our code we use to fire this trigger:

add_filter( 'wp_mail', array( $this, 'ironikus_trigger_send_email' ), 10, 1 );

IMPORTANT: Please note that this webhook fires before the email itself is sent. This is due to the fact that the wp_mail filter is fired before the actual email is send out.

Tipps

1. In case you don't need a specified webhook URL at the moment, you can simply deactivate it by clicking the Deactivate link next to the Webhook URL. This results in the specified URL not being fired once the trigger fires.
2. You can use the Send demo button to send a static request to your specified Webhook URL. Please note that the data sent within the request might differ from your live data.
3. Within the Settings link next to your Webhook URL, you can use customize the functionality of the request. It contains certain default settings like changing the request type the data is sent in, or custom settings, depending on your trigger. An explanation for each setting is right next to it. (Please don't forget to save the settings once you changed them - the button is at the end of the popup.)
4. You can also check the response you get from the demo webhook call. To check it, simply open the console of your browser and you will find an entry there, which gives you all the details about the response.

In case you would like to learn more about our plugin, please check out our documentation at:
https://ironikus.com/docs/article-categories/get-started/

• comment_id
  The comment id of the currently created comment.
• comment_data
  The full data object of the comment.
• current_post_id
  The post id of the post the comment was created on.
• current_post_data
  The full data of the current post.
• user_id
  The id of the user who posted the comment (In case it is given).
• user_data
  The full data of the user of the comment (In case a user is given).

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [comment_id] => 9
    [comment_data] => Array
        (
            [comment_ID] => 9
            [comment_post_ID] => 375
            [comment_author] => admin
            [comment_author_email] => admin@xxx.dev
            [comment_author_url] => 
            [comment_author_IP] => 127.0.0.1
            [comment_date] => 2019-08-14 14:08:53
            [comment_date_gmt] => 2019-08-14 14:08:53
            [comment_content] => My test
            [comment_karma] => 0
            [comment_approved] => 1
            [comment_agent] => Mozilla/5.0 xxx
            [comment_type] => 
            [comment_parent] => 0
            [user_id] => 1
        )

    [comment_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [current_post_id] => 375
    [current_post_data] => Array
        (
            [ID] => 375
            [post_author] => 1
            [post_date] => 2019-08-11 15:03:31
            [post_date_gmt] => 2019-08-11 15:03:31
            [post_content] => 
            [post_title] => Test Custom Comment 2
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => test-custom-comment-2
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2019-08-14 11:53:24
            [post_modified_gmt] => 2019-08-14 11:53:24
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://xxx.dev/?p=375
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 3
            [filter] => raw
        )

    [current_post_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [user_id] => 1
    [user_data] => Array
        (
            [data] => Array
                (
                    [ID] => 1
                    [user_login] => admin
                    [user_nicename] => admin
                    [user_email] => admin@xxx.dev
                    [user_url] => 
                    [user_registered] => 2017-07-27 23:58:11
                    [user_activation_key] => 
                    [user_status] => 0
                    [display_name] => admin
                    [spam] => 0
                    [deleted] => 0
                )

            [ID] => 1
            [caps] => Array
                (
                    [administrator] => 1
                )

            [cap_key] => XXX_capabilities
            [roles] => Array
                (
                    [0] => administrator
                )

            [allcaps] => Array
                (
                    [switch_themes] => 1
                    [edit_themes] => 1
                    [activate_plugins] => 1
                    [edit_plugins] => 1
                    [edit_users] => 1
                    [edit_files] => 1
                    [manage_options] => 1
                    [moderate_comments] => 1
                    [manage_categories] => 1
                    [manage_links] => 1
                    [upload_files] => 1
                    [import] => 1
                    [unfiltered_html] => 1
                    [edit_posts] => 1
                    [edit_others_posts] => 1
                    [edit_published_posts] => 1
                    [publish_posts] => 1
                    [edit_pages] => 1
                    [read] => 1
                    [level_10] => 1
                    [level_9] => 1
                    [level_8] => 1
                    [level_7] => 1
                    [level_6] => 1
                    [level_5] => 1
                    [level_4] => 1
                    [level_3] => 1
                    [level_2] => 1
                    [level_1] => 1
                    [level_0] => 1
                    [edit_others_pages] => 1
                    [edit_published_pages] => 1
                    [publish_pages] => 1
                    [delete_pages] => 1
                    [delete_others_pages] => 1
                    [delete_published_pages] => 1
                    [delete_posts] => 1
                    [delete_others_posts] => 1
                    [delete_published_posts] => 1
                    [delete_private_posts] => 1
                    [edit_private_posts] => 1
                    [read_private_posts] => 1
                    [delete_private_pages] => 1
                    [edit_private_pages] => 1
                    [read_private_pages] => 1
                    [delete_users] => 1
                    [create_users] => 1
                    [unfiltered_upload] => 1
                    [edit_dashboard] => 1
                    [update_plugins] => 1
                    [delete_plugins] => 1
                    [install_plugins] => 1
                    [update_themes] => 1
                    [install_themes] => 1
                    [update_core] => 1
                    [list_users] => 1
                    [remove_users] => 1
                    [promote_users] => 1
                    [edit_theme_options] => 1
                    [delete_themes] => 1
                    [export] => 1
                )

            [filter] => 
        )

    [user_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

)

Please copy your Webhooks Pro webhook URL into the provided input field. After that you can test your data via the Send demo button.

You will recieve a full response of the user post id, the full post object, as well as the post meta, so everything you need will be there.

You can also filter the demo request by using a custom WordPress filter.

To check the Webhooks Pro response on a demo request, just open your browser console and you will see the object.

By default, we don't send the user password within the request. To active it, please use the following WordPress filter: wpwhpro/webhooks/trigger_create_comment_restrict_user_values (More details within our docs at ironikus.com/docs

• comment_id
  The comment id of the currently updated comment.
• comment_data
  The full data object of the comment.
• current_post_id
  The post id of the post the comment was updated on.
• current_post_data
  The full data of the current post.
• user_id
  The id of the user who posted the comment (In case it is given).
• user_data
  The full data of the user of the comment (In case a user is given).

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [comment_id] => 9
    [comment_data] => Array
        (
            [comment_ID] => 9
            [comment_post_ID] => 375
            [comment_author] => admin
            [comment_author_email] => admin@xxx.dev
            [comment_author_url] => 
            [comment_author_IP] => 127.0.0.1
            [comment_date] => 2019-08-14 14:08:53
            [comment_date_gmt] => 2019-08-14 14:08:53
            [comment_content] => My test
            [comment_karma] => 0
            [comment_approved] => 1
            [comment_agent] => Mozilla/5.0 xxx
            [comment_type] => 
            [comment_parent] => 0
            [user_id] => 1
        )

    [comment_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [current_post_id] => 375
    [current_post_data] => Array
        (
            [ID] => 375
            [post_author] => 1
            [post_date] => 2019-08-11 15:03:31
            [post_date_gmt] => 2019-08-11 15:03:31
            [post_content] => 
            [post_title] => Test Custom Comment 2
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => test-custom-comment-2
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2019-08-14 11:53:24
            [post_modified_gmt] => 2019-08-14 11:53:24
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://xxx.dev/?p=375
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 3
            [filter] => raw
        )

    [current_post_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [user_id] => 1
    [user_data] => Array
        (
            [data] => Array
                (
                    [ID] => 1
                    [user_login] => admin
                    [user_nicename] => admin
                    [user_email] => admin@xxx.dev
                    [user_url] => 
                    [user_registered] => 2017-07-27 23:58:11
                    [user_activation_key] => 
                    [user_status] => 0
                    [display_name] => admin
                    [spam] => 0
                    [deleted] => 0
                )

            [ID] => 1
            [caps] => Array
                (
                    [administrator] => 1
                )

            [cap_key] => XXX_capabilities
            [roles] => Array
                (
                    [0] => administrator
                )

            [allcaps] => Array
                (
                    [switch_themes] => 1
                    [edit_themes] => 1
                    [activate_plugins] => 1
                    [edit_plugins] => 1
                    [edit_users] => 1
                    [edit_files] => 1
                    [manage_options] => 1
                    [moderate_comments] => 1
                    [manage_categories] => 1
                    [manage_links] => 1
                    [upload_files] => 1
                    [import] => 1
                    [unfiltered_html] => 1
                    [edit_posts] => 1
                    [edit_others_posts] => 1
                    [edit_published_posts] => 1
                    [publish_posts] => 1
                    [edit_pages] => 1
                    [read] => 1
                    [level_10] => 1
                    [level_9] => 1
                    [level_8] => 1
                    [level_7] => 1
                    [level_6] => 1
                    [level_5] => 1
                    [level_4] => 1
                    [level_3] => 1
                    [level_2] => 1
                    [level_1] => 1
                    [level_0] => 1
                    [edit_others_pages] => 1
                    [edit_published_pages] => 1
                    [publish_pages] => 1
                    [delete_pages] => 1
                    [delete_others_pages] => 1
                    [delete_published_pages] => 1
                    [delete_posts] => 1
                    [delete_others_posts] => 1
                    [delete_published_posts] => 1
                    [delete_private_posts] => 1
                    [edit_private_posts] => 1
                    [read_private_posts] => 1
                    [delete_private_pages] => 1
                    [edit_private_pages] => 1
                    [read_private_pages] => 1
                    [delete_users] => 1
                    [create_users] => 1
                    [unfiltered_upload] => 1
                    [edit_dashboard] => 1
                    [update_plugins] => 1
                    [delete_plugins] => 1
                    [install_plugins] => 1
                    [update_themes] => 1
                    [install_themes] => 1
                    [update_core] => 1
                    [list_users] => 1
                    [remove_users] => 1
                    [promote_users] => 1
                    [edit_theme_options] => 1
                    [delete_themes] => 1
                    [export] => 1
                )

            [filter] => 
        )

    [user_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

)

Please copy your Webhooks Pro webhook URL into the provided input field. After that you can test your data via the Send demo button.

You will recieve a full response of the user post id, the full post object, as well as the post meta, so everything you need will be there.

You can also filter the demo request by using a custom WordPress filter.

To check the Webhooks Pro response on a demo request, just open your browser console and you will see the object.

By default, we don't send the user password within the request. To active it, please use the following WordPress filter: wpwhpro/webhooks/trigger_update_comment_restrict_user_values (More details within our docs at ironikus.com/docs

• comment_id
  The comment id of the currently trashed comment.
• comment_data
  The full data object of the comment.
• current_post_id
  The post id of the post the comment was trashd on.
• current_post_data
  The full data of the current post.
• user_id
  The id of the user who posted the comment (In case it is given).
• user_data
  The full data of the user of the comment (In case a user is given).

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [comment_id] => 9
    [comment_data] => Array
        (
            [comment_ID] => 9
            [comment_post_ID] => 375
            [comment_author] => admin
            [comment_author_email] => admin@xxx.dev
            [comment_author_url] => 
            [comment_author_IP] => 127.0.0.1
            [comment_date] => 2019-08-14 14:08:53
            [comment_date_gmt] => 2019-08-14 14:08:53
            [comment_content] => My test
            [comment_karma] => 0
            [comment_approved] => 1
            [comment_agent] => Mozilla/5.0 xxx
            [comment_type] => 
            [comment_parent] => 0
            [user_id] => 1
        )

    [comment_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [current_post_id] => 375
    [current_post_data] => Array
        (
            [ID] => 375
            [post_author] => 1
            [post_date] => 2019-08-11 15:03:31
            [post_date_gmt] => 2019-08-11 15:03:31
            [post_content] => 
            [post_title] => Test Custom Comment 2
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => test-custom-comment-2
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2019-08-14 11:53:24
            [post_modified_gmt] => 2019-08-14 11:53:24
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://xxx.dev/?p=375
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 3
            [filter] => raw
        )

    [current_post_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [user_id] => 1
    [user_data] => Array
        (
            [data] => Array
                (
                    [ID] => 1
                    [user_login] => admin
                    [user_nicename] => admin
                    [user_email] => admin@xxx.dev
                    [user_url] => 
                    [user_registered] => 2017-07-27 23:58:11
                    [user_activation_key] => 
                    [user_status] => 0
                    [display_name] => admin
                    [spam] => 0
                    [deleted] => 0
                )

            [ID] => 1
            [caps] => Array
                (
                    [administrator] => 1
                )

            [cap_key] => XXX_capabilities
            [roles] => Array
                (
                    [0] => administrator
                )

            [allcaps] => Array
                (
                    [switch_themes] => 1
                    [edit_themes] => 1
                    [activate_plugins] => 1
                    [edit_plugins] => 1
                    [edit_users] => 1
                    [edit_files] => 1
                    [manage_options] => 1
                    [moderate_comments] => 1
                    [manage_categories] => 1
                    [manage_links] => 1
                    [upload_files] => 1
                    [import] => 1
                    [unfiltered_html] => 1
                    [edit_posts] => 1
                    [edit_others_posts] => 1
                    [edit_published_posts] => 1
                    [publish_posts] => 1
                    [edit_pages] => 1
                    [read] => 1
                    [level_10] => 1
                    [level_9] => 1
                    [level_8] => 1
                    [level_7] => 1
                    [level_6] => 1
                    [level_5] => 1
                    [level_4] => 1
                    [level_3] => 1
                    [level_2] => 1
                    [level_1] => 1
                    [level_0] => 1
                    [edit_others_pages] => 1
                    [edit_published_pages] => 1
                    [publish_pages] => 1
                    [delete_pages] => 1
                    [delete_others_pages] => 1
                    [delete_published_pages] => 1
                    [delete_posts] => 1
                    [delete_others_posts] => 1
                    [delete_published_posts] => 1
                    [delete_private_posts] => 1
                    [edit_private_posts] => 1
                    [read_private_posts] => 1
                    [delete_private_pages] => 1
                    [edit_private_pages] => 1
                    [read_private_pages] => 1
                    [delete_users] => 1
                    [create_users] => 1
                    [unfiltered_upload] => 1
                    [edit_dashboard] => 1
                    [update_plugins] => 1
                    [delete_plugins] => 1
                    [install_plugins] => 1
                    [update_themes] => 1
                    [install_themes] => 1
                    [update_core] => 1
                    [list_users] => 1
                    [remove_users] => 1
                    [promote_users] => 1
                    [edit_theme_options] => 1
                    [delete_themes] => 1
                    [export] => 1
                )

            [filter] => 
        )

    [user_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

)

Please copy your Webhooks Pro webhook URL into the provided input field. After that you can test your data via the Send demo button.

You will recieve a full response of the user post id, the full post object, as well as the post meta, so everything you need will be there.

You can also filter the demo request by using a custom WordPress filter.

To check the Webhooks Pro response on a demo request, just open your browser console and you will see the object.

By default, we don't send the user password within the request. To active it, please use the following WordPress filter: wpwhpro/webhooks/trigger_trash_comment_restrict_user_values (More details within our docs at ironikus.com/docs

• comment_id
  The comment id of the currently deleted comment.
• comment_data
  The full data object of the comment.
• current_post_id
  The post id of the post the comment was deleted on.
• current_post_data
  The full data of the current post.
• user_id
  The id of the user who posted the comment (In case it is given).
• user_data
  The full data of the user of the comment (In case a user is given).

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [comment_id] => 9
    [comment_data] => Array
        (
            [comment_ID] => 9
            [comment_post_ID] => 375
            [comment_author] => admin
            [comment_author_email] => admin@xxx.dev
            [comment_author_url] => 
            [comment_author_IP] => 127.0.0.1
            [comment_date] => 2019-08-14 14:08:53
            [comment_date_gmt] => 2019-08-14 14:08:53
            [comment_content] => My test
            [comment_karma] => 0
            [comment_approved] => 1
            [comment_agent] => Mozilla/5.0 xxx
            [comment_type] => 
            [comment_parent] => 0
            [user_id] => 1
        )

    [comment_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [current_post_id] => 375
    [current_post_data] => Array
        (
            [ID] => 375
            [post_author] => 1
            [post_date] => 2019-08-11 15:03:31
            [post_date_gmt] => 2019-08-11 15:03:31
            [post_content] => 
            [post_title] => Test Custom Comment 2
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => test-custom-comment-2
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2019-08-14 11:53:24
            [post_modified_gmt] => 2019-08-14 11:53:24
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://xxx.dev/?p=375
            [menu_order] => 0
            [post_type] => post
            [post_mime_type] => 
            [comment_count] => 3
            [filter] => raw
        )

    [current_post_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

    [user_id] => 1
    [user_data] => Array
        (
            [data] => Array
                (
                    [ID] => 1
                    [user_login] => admin
                    [user_nicename] => admin
                    [user_email] => admin@xxx.dev
                    [user_url] => 
                    [user_registered] => 2017-07-27 23:58:11
                    [user_activation_key] => 
                    [user_status] => 0
                    [display_name] => admin
                    [spam] => 0
                    [deleted] => 0
                )

            [ID] => 1
            [caps] => Array
                (
                    [administrator] => 1
                )

            [cap_key] => XXX_capabilities
            [roles] => Array
                (
                    [0] => administrator
                )

            [allcaps] => Array
                (
                    [switch_themes] => 1
                    [edit_themes] => 1
                    [activate_plugins] => 1
                    [edit_plugins] => 1
                    [edit_users] => 1
                    [edit_files] => 1
                    [manage_options] => 1
                    [moderate_comments] => 1
                    [manage_categories] => 1
                    [manage_links] => 1
                    [upload_files] => 1
                    [import] => 1
                    [unfiltered_html] => 1
                    [edit_posts] => 1
                    [edit_others_posts] => 1
                    [edit_published_posts] => 1
                    [publish_posts] => 1
                    [edit_pages] => 1
                    [read] => 1
                    [level_10] => 1
                    [level_9] => 1
                    [level_8] => 1
                    [level_7] => 1
                    [level_6] => 1
                    [level_5] => 1
                    [level_4] => 1
                    [level_3] => 1
                    [level_2] => 1
                    [level_1] => 1
                    [level_0] => 1
                    [edit_others_pages] => 1
                    [edit_published_pages] => 1
                    [publish_pages] => 1
                    [delete_pages] => 1
                    [delete_others_pages] => 1
                    [delete_published_pages] => 1
                    [delete_posts] => 1
                    [delete_others_posts] => 1
                    [delete_published_posts] => 1
                    [delete_private_posts] => 1
                    [edit_private_posts] => 1
                    [read_private_posts] => 1
                    [delete_private_pages] => 1
                    [edit_private_pages] => 1
                    [read_private_pages] => 1
                    [delete_users] => 1
                    [create_users] => 1
                    [unfiltered_upload] => 1
                    [edit_dashboard] => 1
                    [update_plugins] => 1
                    [delete_plugins] => 1
                    [install_plugins] => 1
                    [update_themes] => 1
                    [install_themes] => 1
                    [update_core] => 1
                    [list_users] => 1
                    [remove_users] => 1
                    [promote_users] => 1
                    [edit_theme_options] => 1
                    [delete_themes] => 1
                    [export] => 1
                )

            [filter] => 
        )

    [user_data_meta] => Array
        (
            [demo_key_1] => Array
                (
                    [0] => 375
                )

            [demo_key_2] => Array
                (
                    [0] => test
                )

        )

)

Please copy your Webhooks Pro webhook URL into the provided input field. After that you can test your data via the Send demo button.

You will recieve a full response of the user post id, the full post object, as well as the post meta, so everything you need will be there.

You can also filter the demo request by using a custom WordPress filter.

To check the Webhooks Pro response on a demo request, just open your browser console and you will see the object.

By default, we don't send the user password within the request. To active it, please use the following WordPress filter: wpwhpro/webhooks/trigger_delete_comment_restrict_user_values (More details within our docs at ironikus.com/docs

• form_id
  The id of the form that the data comes from.
• form_data
  The post data of the form itself.
• form_data_meta
  The meta data of the form itself.
• form_submit_data
  The data which was submitted by the form. For more details, check the return code area.

Here is an example of all the available default fields that are sent after the trigger is fired. The fields may vary based on custom extensions or third party plugins.

Array
(
    [form_id] => 1
    [form_data] => Array
        (
            [ID] => 1
            [post_author] => 1
            [post_date] => 2018-11-06 14:19:18
            [post_date_gmt] => 2018-11-06 14:19:18
            [post_content] => THE FORM CONTENT
            [post_title] => My form
            [post_excerpt] => 
            [post_status] => publish
            [comment_status] => open
            [ping_status] => open
            [post_password] => 
            [post_name] => my-form
            [to_ping] => 
            [pinged] => 
            [post_modified] => 2018-11-06 14:19:18
            [post_modified_gmt] => 2018-11-06 14:19:18
            [post_content_filtered] => 
            [post_parent] => 0
            [guid] => https://mydomain.dev/?p=1
            [menu_order] => 0
            [post_type] => wpcf7_contact_form
            [post_mime_type] => 
            [comment_count] => 1
            [filter] => raw
        )

    [form_data_meta] => Array
        (
            [my_first_meta_key] => MY second meta key value
            [my_second_meta_key] => MY second meta key value
        )

    [form_submit_data] => Array
        (
            [your-name] => xxxxxx
            [your-email] => xxxxxx
            [your-message] => xxxxxx
        )

    [special_mail_tags] => Array
        (
            [custom_key] => 123
            [another_key] => Hello there
        )

)

Please copy your webhook URL into the provided input field. After that you can test your data via the Send demo button.

You will recieve a full response of the user form data, the form post meta, as well as of the sumitted form data.

You can also filter contact forms to specify where exactly you want to run the trigger on.

To check the Webhooks response on a demo request, just open your browser console and you will see the object.

You can also rename certain webhook keys by defining an additional attribute within the Contact Form template. Here is an example:

[text your-email wpwhkey:new_key]

The above example changes the key within the payload from "your-email" to "new_key". To define it, simply set the argument "wpwhkey" and separate the new key using a double point (:)."