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 any generic provider.
Before setting up WebHooks, please read over our Alerts article to learn basic concepts and useful tips.
You can use any generic provider to send WebHooks, if:
- The provider supports WebHooks.
- The provider supports requests with the Content-Type set to application/json
- The provider allows JSON payloads.
At any time, you can come back to the Hudu admin area >> Alerts >> edit specific alert to make changes to the alert.
Guides
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 your provider.
- Provide payload delivery information in the WebHook payload field (must be valid JSON format).
- Please see one of our alternative guides linked below for specific payload examples.
- Save the alert by clicking ((Create Alert)).
Hudu webhook variables you can use in payloads
When configuring a Hudu Alert that sends to a webhook, you can include dynamic values in your JSON payload using Hudu variables (tokens that start with $). Hudu replaces these tokens with real alert data when the webhook is delivered.
Supported variables
Single Expiration
- $HUDU_URL = Link to the relevant expiration in Hudu
- $TRIGGER_DAYS = Number of days set as trigger time
- $RECORD_NAME = Name of expiring record
- $COMPANY_NAME = Name of expiring record's company
- $EXPIRATION_TYPE = Type of expiration (e.g., domain, ssl_certificate, warranty)
- $EXPIRATION_DATE = The expiration date
- $COMPANY_ID = Company ID
- $RECORD_ID = Record ID
Expiration List
- $EXPIRATIONS_COUNT = Number of expirations
- $EXPIRATIONS_HUDU_URL = Link to the relevant expirations in Hudu
- $TRIGGER_DAYS = Number of days set as trigger time
Website monitoring
- $WEBSITE_NAME = Name of website
- $WEBSITE_HUDU_URL = Link to the relevant URL in Hudu
One-Time Shared Password Reveal
- $RECORD_NAME = Name of password
- $HUDU_URL = Link to the relevant URL in Hudu
Record created / updated / deleted
- $RECORD_NAME = Name of record
- $RECORD_TYPE = Type of record
- $HUDU_URL = Link to the relevant URL in Hudu
- $ACTION = Name of action that occurred (create, update, delete)
- $RECORD_ID = ID of record
- $COMPANY_NAME = Record's Company Name (if present)
- $COMPANY_ID = Record's Company ID (if present)
- $HUDU_COMPANY_URL = Record's Company URL (if present)
- $ASSET_LAYOUT_ID = Record's Asset Layout ID (if present)
Password Created / Updated
- $RECORD_NAME = Name of password
- $HUDU_URL = Link to the relevant URL in Hudu
- $ACTION = Name of action that occurred (create or update)
Example JSON payload (generic webhook receiver)
{
"message": "Hudu alert: $RECORD_NAME ($RECORD_TYPE) was $ACTIONd. Link: $HUDU_URL"
}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.
Alternative Guides