Contact tags removed trigger

This manual will demonstrate you on how to set up a connection between the Flows feature of WP Webhooks and the Contact tags removed trigger.

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup WP Webhooks Flow

To get started, please login into your WordPress website, navigate to your WordPress dashboard > WP Webhooks > Flows and open/create a Flow of your choice. If everything is ready, please follow the steps down below:

1. Add a new trigger within the Flow, select the Autonami integration and choose the Contact tags removed trigger.

2. Setup Flows trigger

1. If you don't feel completely familar with the layout of the Flow, you can read more about the basic setup of a Flow via the following helpfile.
2. The next step is to configure the "Trigger Settings".
3. Within those "Trigger settings", you will see a list of all available customizations and filters for the Contact tags removed trigger and further information about what the setting is about.
   
4. As seen in the example screenshot above, you will see various settings available that you can use to customize this trigger. While we offer default customizations for each trigger, we do also offer specific filters for some webhook triggers. To see a full list of all individual settings for this trigger, simply scroll down on this page to the filter list.
5. After that's done, simply continue the Flow trigger and test it. If everything works fine, you will get a successful response from the webhok call and everything was set up correctly. Within this Flow, you can also use all of the sent values from the trigger call as parameters within the following actions.
6. In case of an error, please check its message for further information. We do also maintain a list of common error which you will find here.

3. Summary

If you followed all the steps above, your Flow will now send data based on the Contact tags removed trigger once its respective event was fired.
In case you want to learn more about this setup and others, please visit our documentation.

This manual will demonstrate you on how to set up a connection between the Contact tags removed trigger (to send data) and Integromat (to receive data).

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup Integromat Scenario

To get started, please make sure you are logged in into Integromat and that you have your Scenario open in which you would like to receive the webhook trigger call. If everything is ready, please follow the steps down below:

1. Add a new module within your Scenario and select the "Webhooks" app from Integromat (If you do not see the app, simply search for "Webhooks").
2. Please make sure to select the "Webhooks" app from Integromat and not the "WP Webhooks" app.

2. Setup Webhooks app

1. After you selected the app from the previous step, please follow the guide on how to Setup a basic verion of the Integromat app, and return back here once you're ready.
2. Welcome back and congratulations, you successfully set up the basic version of the Integromat app. Now it's time to connect it with WP Webhooks, specifically for this action.
3. Please copy the dynamically created URL from within the Integromat module and add it to the Contact tags removed trigger within your WordPress dashboard > Settings > WP Webhooks > Send Data > Contact tags removed > Contact tags removed trigger.
   
4. Once that's done, your module is now connected to the Contact tags removed trigger and Integromat receives the data everytime the trigger fires.
   
5. As seen in the screenshot above, you can use the settings to customize the request that is sent to Integromat, as well as you can pre-filter the request based on certain factors. To get a full list of all available filters, please scroll down to the filter list.
6. After that's done, you are readz to go ahead with your automation.
7. In case of an error, please check its message for further information. We do also maintain a list of common error which you will find here.

3. Summary

If you followed all the steps above, WP Webhooks will now send a request to your Integromat scenario every time the Contact tags removed trigger fires.
In case you want to learn more about this setup and others, please visit our documentation.

This manual will demonstrate you on how to set up a connection between the Contact tags removed trigger (to send data) and Pabbly (to receive data).

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup Pabbly Workflow

To get started, please make sure you are logged in into Pabbly and that you have your Workflow open in which you would like to receive the webhook trigger call. If everything is ready, please follow the steps down below:

1. Add the first step within your Workflow and select the "Webhooks" app from Pabbly (If you do not see the app, simply search for "Webhooks").
2. Please make sure to select the "Webhooks" app from Pabbly and not the "WP Webhooks" app.

2. Setup Webhooks app

1. After you selected the app from the previous step, please follow the guide on how to Setup a basic verion of the Pabbly Workflow, and return back here once you're ready.
2. Welcome back and congratulations, you successfully set up the basic version of the Pabbly Workflow. Now it's time to connect it with WP Webhooks, specifically for this action.
3. Please copy the dynamically created URL from within the Pabbly module and add it to the Contact tags removed trigger within your WordPress dashboard > Settings > WP Webhooks > Send Data > Contact tags removed > Contact tags removed trigger.
   
4. Once that's done, your step is now connected to the Contact tags removed trigger and Pabbly receives the data everytime the trigger fires.
   
5. As seen in the screenshot above, you can use the settings to customize the request that is sent to Pabbly, as well as you can pre-filter the request based on certain factors. To get a full list of all available filters, please scroll down to the filter list.
6. After that's done, you are ready to go ahead with your automation.
7. In case of an error, please check its message for further information. We do also maintain a list of common error which you will find here.

3. Summary

If you followed all the steps above, WP Webhooks will now send a request to your Pabbly scenario every time the Contact tags removed trigger fires.
In case you want to learn more about this setup and others, please visit our documentation.

This manual will demonstrate you on how to set up a connection between the Contact tags removed trigger (to send data) and Integrately (to receive data).

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup Integrately Automation

To get started, please make sure you are logged in into Integrately and that you have your Automation open in which you would like to receive the webhook trigger call. If everything is ready, please follow the steps down below:

1. Add the first step within your Automation and select the "Webhook/API Integration" app from Integrately (If you do not see the app, simply search for "Webhook").
2. Please make sure to select the "Webhook/API Integration" app from Integrately and not the "WP Webhooks" app.

2. Setup Webhooks app

1. After you selected the app from the previous step, please follow the guide on how to Setup a basic verion of the Integrately Automation, and return back here once you're ready.
2. Welcome back and congratulations, you successfully set up the basic version of the Integrately Automation. Now it's time to connect it with WP Webhooks, specifically for this action.
3. Please copy the dynamically created webhook URL from within the Integrately app and add it to the Contact tags removed trigger within your WordPress dashboard > Settings > WP Webhooks > Send Data > Contact tags removed > Contact tags removed trigger.
   
4. Once that's done, your step is now connected to the Contact tags removed trigger and Integrately receives the data everytime the trigger fires.
   
5. As seen in the screenshot above, you can use the settings to customize the request that is sent to Integrately, as well as you can pre-filter the request based on certain factors. To get a full list of all available filters, please scroll down to the filter list.
6. After that's done, you are ready to go ahead with your automation.
7. In case of an error, please check its message for further information. We do also maintain a list of common error which you will find here.

3. Summary

If you followed all the steps above, WP Webhooks will now send a request to your Pabbly scenario every time the Contact tags removed trigger fires.
In case you want to learn more about this setup and others, please visit our documentation.

This manual will demonstrate you on how to set up a connection between the Contact tags removed trigger (to send data) and Zapier (to receive data).

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup Zapier Zap

To get started, please make sure you are logged in into Zapier and that you have your Zap open in which you would like to receive the webhook trigger call. If everything is ready, please follow the steps down below:

1. Add the first step within your Zap and select the "Webhooks by Zapier" app from Zapier (If you do not see the app, simply search for "Webhooks").
2. Please make sure to select the "Webhooks by Zapier" and not the "WP Webhooks" app.

2. Setup Webhook by Zapier app

1. After you selected the app from the previous step, please follow the guide on how to Setup a basic verion of the Zapier Zap, and return back here once you're ready.
2. Welcome back and congratulations, you successfully set up the basic version of the Zapier Zap. Now it's time to connect it with WP Webhooks, specifically for this action.
3. Please copy the dynamically created webhook URL from within the "Webhooks by Zapier" app and add it to the Contact tags removed trigger within your WordPress dashboard > Settings > WP Webhooks > Send Data > Contact tags removed > Contact tags removed trigger.
   
4. Once that's done, your step is now connected to the Contact tags removed trigger and Zapier receives the data everytime the trigger fires.
   
5. As seen in the screenshot above, you can use the settings to customize the request that is sent to Zapier, as well as you can pre-filter the request based on certain factors. To get a full list of all available filters, please scroll down to the filter list.
6. After that's done, you are ready to go ahead with your automation.
7. In case of an error, please check its message for further information. We do also maintain a list of common error which you will find here.

3. Summary

If you followed all the steps above, WP Webhooks will now send a request to your Zapier Zap every time the Contact tags removed trigger fires.
In case you want to learn more about this setup and others, please visit our documentation.

This manual will demonstrate you on how to set up a direct connection between the Contact tags removed trigger (to send data) and your chosen service (to receive the data of this trigger).

To get started, we will walk you through each step from the beginning to the end so that you can make sure your endpoint will work as expected.

Required plugins/services

In order to use this webhook trigger, you need to make sure you installed and activated the following plugins, or have a valid account with the services:

• WP Webhooks
• Autonami

1. Setup WP Webhooks

To get started with WP Webhooks, simply download the latest version from your account dashboard and install/activate it on your WordPress website. If you want to lean more about the installation process of the plugin itself, please check out this manual.

2. Integrate the trigger with your service

In order to send data via the Contact tags removed trigger, you need to provide a webhook URL from your chosen service so that it can receive dat sent by WP Webhooks.
In case you are interested to learn more about how to set up a webhook URL with services such as Integromat, Pabbly, or Zapier, please take a look at the following help files.

1. Please head over to your WordPress dashboard > Settings > WP Webhooks > Send Data and add the webhook URL that was provided by your service to the Contact tags removed trigger by clicking the "Add Webhook URL" button.
2. To add the webhook URL, you are also promted to enter a name. This name will be used as an identifier of that specific URL. Best practice is to set it to the purpose of the webhook URL.

What we have accomplished so far: At this stage, your external service is already able to receive data from the Contact tags removed trigger whenever it fires. By default, it will send a POST request along with the Content-Type: application/json, however, you can customize that within the settings.

3. Set up Data Mapping (Optional)

While this connection can aleady transer data from the Contact tags removed trigger the webhook URL of your chosen service, your service might require a specific layout/setup of the data that is sent.
To solve that, we offer a feature called Data Mapping. This allows you to automatically alter the outgoing data from WP Webhooks to map its values to the required data structure of your service.
This feature allows you to do various mapping possibilities, create new values and manipulate existing ones. To show you this feature in a practical way, down below is a short manual on how you can set up the data mapping template:

Set up a Data Mapping template

1. Go to your WordPress dashboard > Settings > WP Webhooks > Data Mapping and add a new Data Mapping template.
2. Within it, you can add your mapping data that adjusts the data sent by WP Webhooks to the data structure required by your service.
3. Lastly, you need to connect the Data Mapping template to the webhook URL you added within the Contact tags removed trigger. To do that, please head over to your WordPress dashboard > Settings > WP Webhooks > Send Data and open the Setting of the added webhook URL. There you will find a setting called Add data mapping template - simply select your your Data Mapping template from the dropdown and save it.
4. That's it. Now all data sent from WP Webhooks will be validated and mapped by the data mapping template. To learn more about it, please check out our documentation for Data Mapping templates.

Configure the Data Mapping template (Optional)
Now it is up to you what data you want to send in wich way via the Contact tags removed trigger.
To provide you a quick example with various mapping possibilities, please take a look at the next steps.

1. Go to your WordPress dashboard > Settings > WP Webhooks > Data Mapping and open the data mapping template you created in the previous step.
2. Once you add a new row, you can add a new key at the left of it. This key will then be added to the data structure in case it does not exist yet.
3. On the right you can add keys to map the existing data based on the data that was sent by the WP Webhooks trigger. To learn more about the mapping, please check out this helpfiles.
4. To give you a better example of its possibilities, you will find a data mapping template export that you can simply copy and import it into your newly created data mapping template. This will add various data mapping entries to show you how it works.

   {"template_settings":{"wpwhpro_data_mapping_whitelist_payload":"none"},"template_data":[{"new_key":"msg","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"data_value\",\"wpwhpro_data_mapping_convert_data\":\"none\",\"wpwhpro_data_mapping_decode_data\":\"none\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"Some new message text.\"}"]},{"new_key":"sport_key","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"key_mapping\",\"wpwhpro_data_mapping_convert_data\":\"none\",\"wpwhpro_data_mapping_decode_data\":\"none\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"custom_data\"}"]},{"new_key":"test_1","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"data_value\",\"wpwhpro_data_mapping_convert_data\":\"none\",\"wpwhpro_data_mapping_decode_data\":\"none\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"Hello World\"}"]},{"new_key":"combine_both","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"data_value\",\"wpwhpro_data_mapping_convert_data\":\"none\",\"wpwhpro_data_mapping_decode_data\":\"none\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"\\\"{:test_1:}\\\" is now combined with \\\"{:sport_key:}\\\"\"}"]},{"new_key":"number","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"data_value\",\"wpwhpro_data_mapping_convert_data\":\"integer\",\"wpwhpro_data_mapping_decode_data\":\"none\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"1\"}"]},{"new_key":"json_to_array","singles":["{\"settings\":{\"wpwhpro_data_mapping_value_type\":\"data_value\",\"wpwhpro_data_mapping_convert_data\":\"none\",\"wpwhpro_data_mapping_decode_data\":\"json_decode\",\"wpwhpro_data_mapping_fallback_value\":\"\"},\"value\":\"{\\\"demo_data\\\": \\\"Demo Value\\\", \\\"more_data\\\": \\\"Another Value\\\"}\"}"]}]}

5. After the import, you can try the data mapping template with the Preview Template feature that's availablel within the Data Mapping template. Simply add a demo JSON (as provided down below) and click the "Apply for outgoing data" button. This will simulate how the response looks like when the data from the JSON below would have been sent by the Contact tags removed trigger

   {
     "success": true,
     "msg": "Some Demo Message",
     "custom_data": "Sport"
   }

6. Lastly, you only need to map the values sent by the Contact tags removed trigger to the data structure required by your service.
   If you are unsure about the format the data is sent from Contact tags removed trigger, you have various options to check it:
   • One possibility is to check the "Outgoing data" tab of a single webhook trigger within WordPress dashboard > Settings > WP Webhooks > Send Data
   • As we provide a static payload within the "Outgoing Data" tab, yours might differ, depending on custom values and other plugins. To check on those custom values, you can also use our Log feature. Once the trigger fires to the webhook URL of your service, you will see an entry within the logs, including the individual data.
   • You can also send the data to a different webhook URL such as the one generated by https://webhook.site/. Simply add the webhook URL created by webhook.site to the Contact tags removed trigger within WP Webhooks.

4. Summary

If you followed the steps above, you successfully set up your webhook connection and connected the data mapping template. This is everything you need to automatically send data from the Contact tags removed trigger to your chosen service.
In case you want to learn more about this setup and others, please visit our documentation.