WebHooks are automated messages sent from apps when something happens. They have a message—or payload— and are sent to a unique URL; named WebHook URL. This article will serve to assist with sending WebHook notifications to Zapier, to trigger alerts to other providers.
Before setting up the integration with Zapier, please read over our Alerts article to learn basic concepts and useful tips.
In order to set up WebHook notifications to Zapier, you will need:
- A Zapier premium account.
- Admin or super-admin user role within Hudu.
At any time, you can come back to the Hudu admin area → Alerts → edit specific alert to make changes to the alert.
Enabling Alerts
- Navigate to your Hudu admin area → Alerts.
- Click + New Alert.
- Give your alert a name.
- Select the expiration type from the choices and complete the required fields (see Alerts for more information).
- Click Configure WebHook and obtain the required WebHook URL from Zapier.
- Provide payload delivery information in the WebHook payload field (must be valid JSON format).
- Save the alert by clicking Create Alert.
Obtaining the Zapier WebHook URL
- Log in to your Zapier account and click ((+ Create Zap)).
- Find or search for WebHooks by Zapier.
- Select Catch Hook from the dropdown list for the Event field.
- Click continue.
- Under Test Trigger, copy the newly generated WebHook URL into Hudu WebHook alert settings exactly.
- Provide WebHook payloads to create a Zapier request.
- Save the alert in Hudu.
Testing WebHooks
- Navigate to your Hudu admin area → Alerts and find your created alert from the list.
- Click on Test WebHook.
We are only testing your connection and payload, not your variables; sample variables will be filled in.
- Once a WebHook alert to Zapier has been tested on the Hudu side; by clicking ((Test Trigger)) in Zapier, it will pull up your WebHook request (if it was successful).
Zapier Actions
Once a WebHook Zap has been successfully sent and tested within Zapier, you'll need to assign an action to the Zap. For additional information, please visit the link here.
Sending Hudu Radar alerts to Zapier
Hudu Radar alerts send a preconfigured payload that cannot be customized, and most providers, including Slack, Microsoft Teams, and Discord, will reject it if it's sent to them directly. Zapier can receive the Radar payload and reformat it into a message your destination service accepts.
- Create a Catch Hook Zap and copy the WebHook URL, as described above.
- In the Hudu admin area >> Alerts, create or edit a Radar alert and enter the Zapier URL in Webhook URL. The Radar payload is preconfigured, so there's no payload to enter.
- In your Zap's action step, map the preconfigured Radar payload fields listed below into the message for your destination service.
Hudu webhook variables, such as $HUDU_URL, are not supported for Radar alerts. Radar alerts always send the preconfigured fields below.
Preconfigured Radar payload fields
Radar device offline
- event_type = Radar alert type
- deployment_name = Deployment name
- company_name = Company name
- occurred_at = When the alert fired (UTC)
- device.id = Device ID
- device.name = Device name
- device.ip_address = Device IP
- device.device_type = Device type
- device.is_up = Up status
- device.last_agent_check_in_time = Last agent check-in (if present)
- device.network_cidr_address = Network CIDR
- device.hudu_asset_url = Linked Hudu asset URL (if present)
Radar new device
- event_type = Radar alert type
- deployment_name = Deployment name
- company_name = Company name
- occurred_at = When the alert fired (UTC)
- device.id = Device ID
- device.name = Device name
- device.ip_address = Device IP
- device.device_type = Device type
- device.is_up = Up status
- device.last_agent_check_in_time = Last agent check-in (if present)
- device.network_cidr_address = Network CIDR
- device.hudu_asset_url = Linked Hudu asset URL (if present)
Radar agent check-in
- event_type = Radar alert type
- deployment_name = Deployment name
- company_name = Company name
- occurred_at = When the alert fired (UTC)
- device.id = Device ID
- device.name = Device name
- device.ip_address = Device IP
- device.device_type = Device type
- device.is_up = Up status
- device.last_agent_check_in_time = Last agent check-in (if present)
- device.network_cidr_address = Network CIDR
- device.hudu_asset_url = Linked Hudu asset URL (if present)
Radar scan overdue
- event_type = Radar alert type
- deployment_name = Deployment name
- company_name = Company name
- occurred_at = When the alert fired (UTC)
- scan.id = Scan ID
- scan.status = Scan status
- scan.started_at = When the scan started
- scan.ended_at = When the scan ended (if present)
- scan.network_cidr_address = Network CIDR (if present)
Radar scan failed
- event_type = Radar alert type
- deployment_name = Deployment name
- company_name = Company name
- occurred_at = When the alert fired (UTC)
- scan.id = Scan ID
- scan.status = Scan status
- scan.started_at = When the scan started
- scan.ended_at = When the scan ended (if present)
- scan.network_cidr_address = Network CIDR (if present)
Visit Hudu Radar Alerts for additional information on Radar alert types and settings.
Alternative Guides
The guides below will serve to assist with setting up WebHook notifications to alternative common providers.