- A Discord server and channel (within the server) that you want messages to arrive in.
- Admin or super-admin user role within Hudu.
At any time, you can come back to the Hudu admin area → Alerts → edit the 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 Discord.
- Provide payload delivery information in the WebHook payload field (must be valid JSON format).
- Save the alert by clicking Create Alert.
Obtaining the Discord WebHook URL
- Navigate to your Discord server, and into the channel that you'd like messages to be sent to.
- Click on your Discord server name → Server Settings.
- Click Integrations → Create WebHook.
- Edit the newly created WebHook.
- Save your settings.
- Copy the newly generated WebHook URL into Hudu WebHook alert settings exactly.
WebHook Payloads
In order to have a message generated in your Discord, you will need to deliver a payload. A payload is a piece of essential information in a data block that you send to or receive from the server when making API requests. The payload must be sent or received in JSON format.
Supported variables and example payloads
Expand an alert type to see its supported variables and an example Discord payload.
$WEBSITE_NAME, $WEBSITE_HUDU_URL, and $EXPIRATIONS_HUDU_URL are no longer listed on the alert form. Existing alerts that use them still work: Hudu treats $WEBSITE_NAME as $RECORD_NAME, and $WEBSITE_HUDU_URL and $EXPIRATIONS_HUDU_URL as $HUDU_URL. Use the current variable names for new alerts.
Supported variables
- $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
Example payload
{"content": "Expiration alert: $COMPANY_NAME - $RECORD_NAME. View: $HUDU_URL."}Supported variables
- $EXPIRATIONS_COUNT = Number of expirations
- $HUDU_URL = Link to the relevant expirations in Hudu
- $TRIGGER_DAYS = Number of days set as trigger time
Example payload
{"content": "There are *$EXPIRATIONS_COUNT* expirations expiring within *$TRIGGER_DAYS* days. View: $HUDU_URL."}Supported variables
- $RECORD_NAME = Name of website
- $HUDU_URL = Link to the relevant URL in Hudu
Example payload
{"content": "*$RECORD_NAME* appears to be down. View: $HUDU_URL"}Supported variables
- $RECORD_NAME = Name of password
- $HUDU_URL = Link to the relevant URL in Hudu
Example payload
{"content": "The shared password *$RECORD_NAME* was just viewed. View: $HUDU_URL"}Supported variables
- $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)
Example payload
{"content": "*$RECORD_NAME* [$RECORD_TYPE] has been *$ACTIONd*. View: $HUDU_URL"}Testing WebHooks
- Navigate to 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
The guides below will serve to assist with setting up WebHook notifications to alternative common providers.