All Collections
Analyze & Report - Analytics, Dashboards, and Reports
Reports
Set up Alerts with a Generic Webhook Integration
Set up Alerts with a Generic Webhook Integration

Automate your Alerts through a Generic Webhook Integration.

Whitney W. avatar
Written by Whitney W.
Updated over a week ago

Introducing another delivery method to receive your Meltwater Alerts - a Generic Webhook!

This article will help guide you through:

What is a Generic Webhook?

Nearly all organizations use some form of a collaboration tool to conduct business. Meltwater has supported direct integrations with Slack, Microsoft Teams, and DingTalk. But what if you don’t use one of these messaging services? Are you able to receive alerts as well? Yes! Meltwater has taken the next step in our integration plans - a Generic Webhook.

A webhook in web development is a method of augmenting or altering the behavior of a web page or web application with custom callbacks. To simplify, it’s how one app can send an automated message to another app. In this instance, it allows Meltwater to send Smart Alerts to other apps. Using an automation platform such as Zapier, Make, or IFTT (If This Then That), you can connect to Discord, Google Chat, and many more! Using the generic webhook, also allows you to have the ability to receive alerts directly to an API (configuration required).

Generic Webhook Value

By enabling this integration right from within Meltwater, you can now receive automated, AI-powered alerts sent directly to your preferred channels. Having a centralized channel with all Alerts flowing in will allow your team to better collaborate and act on business-critical news, market shifts/trends, and competitive intelligence.

Since there is no limit on either the number of connections or connections per channel, you are able to customize your integrations directly into the channels you are already working in.

How does it work?

Please note: Webhooks are not created in Meltwater. Webhooks are created by you, within the specific platforms of choice. You can then add that Generic Webhook from the Third party integrations page via the Account section in Meltwater.

Below is an example of using the Third Party Integration Platform with Zapier.

Step 1: Create the Webhook on Zapier

  1. Within Zapier click on Create Zap

2. Next, click on Webhooks by Zapier

3. Next, Select Catch Hook under Event and Click Continue

4. Next, Click Continue (Pick off a Child Key is not required)

5. Copy the webhook URL

Now that the Webhook URL has been created you will need to create the integration of the Webhook within Meltwater by following the steps below.

Step 2: Create integration of Webhook in Meltwater

  1. Click on Third Party Integrations under Account within your Meltwater platform. Once on the page, Click on Connect under Generic Webhook

2. Add a name for the Webhook and the Webhook URL from Zapier and click on Add

3. The Webhook will now appear as shown below

Step 3: Create Alert Subscription

  1. Under Content within your Meltwater platform, click on Alerts. Then Click on Create Alert on the top right corner

2. Select the Alert Type you would like to create and click next

3. Add the searches and recipients you would like to receive the alerts for. Under Delivery Method, select Generic Webhook

4. Add the Name created during the setup that should receive the alerts and click Save

Step 4: Test the Webhook

  1. Zapier requires to Test the webhook using the Test Trigger functionality on their platform. Once the alert set up receives an alert, select Test Trigger on the Zapier site to ensure it is working.

2. Once the test trigger is completed, you can connect to any delivery channel within the third-party integration platform.

Notes:

  • When setting up a generic webhook, it is highly recommended to speak your organizations IT team for the setup as it requires technical steps.

  • There is no limit on the amount of integrations therefore you can connect to multiple channels.

  • For Zapier specifically: you can connect multiple connections under the same webhook, but it functions as a funnel - so any alert you connect to that webhook will go to both apps - they cannot be unique. If you want Alert A to go to Google Meet and Alert B to go to Trello - they have to be different webhooks within Zapier.

💡 Tip

Need more help? Feel free to reach out to us via Live Chat or check out our Customer Community.

Find answers and get help from Meltwater Support and Community Experts.


Did this answer your question?