Alerts

    The Hudu admin area is accessible ONLY to admins and super admin users within your organization.

Alerts keep your team aware of upcoming expirations, website outages, and changes to your documentation. Each alert can be scoped to specific companies and sent by email, webhook, or both.

Alerts can be configured for:

  • Single expiration: sends a separate alert for each expiration of a certain type within a set number of trigger days.
  • Expiration list: sends a single alert listing all expirations within a set number of trigger days.
  • Website down: sends an alert when a website appears down.
  • One-time shared password reveal: sends an alert when a one-time shared password has been revealed.
  • Record created/updated/deleted: sends an alert when a company, password, article, website, or asset record is created, updated, or deleted.

    Expiration alerts require at least one expiration within a client space. Visit Expirations for additional information.

Guides

Creating an alert

  • Navigate to the Hudu admin area >> Alerts.
  • Click ((+ New Alert)).
  • Enter a Name for the alert.
  • Choose an option from Alert type, then complete the settings for that type (see Alert types below).
  • Select the company or companies the alert applies to. This field is required. Use Select All to apply the alert to every company.
  • Enter the email address to receive the alert in Send alert to.
  • Optionally, under Configure Webhook, enter a Webhook URL and a Webhook payload. The payload must be valid JSON.
    • The Hudu Webhook Variables available for the selected alert type are listed below the payload field.
  • Click Create Alert to save.

    To change an alert later, return to the Hudu admin area >> Alerts and edit it from the list.

Alert types

Single expiration

Sends a separate alert for each expiration of a certain type within a set number of trigger days.

  • Select the number of trigger days (how many days before the expiration you want to be notified).
  • Stop alerts after reaching trigger: stops alerts from sending after the trigger day is reached.
  • Include expiring records in museum: includes expirations for archived records.
  • Choose an option from Expiration type:
    • All expirations
    • Domain expirations only
    • SSL certificate expirations only
    • Warranty expirations only
    • Article expirations only
    • Asset expirations only: select one or more asset expiration types. This field is required. The options come from date fields in your asset layouts that have been added to expirations, and only types used by the selected companies appear.
Expiration list

Sends a single alert listing all expirations within a set number of trigger days.

  • Select the number of trigger days (how many days before the expiration you want to be notified).
  • Stop alerts after reaching trigger: stops alerts from sending after the trigger day is reached.
  • Include expiring records in museum: includes expirations for archived records.
  • Choose an option from Expiration type:
    • All expirations
    • Domain expirations only
    • SSL certificate expirations only
    • Warranty expirations only
    • Article expirations only
    • Asset expirations only: select one or more asset expiration types. This field is required. The options come from date fields in your asset layouts that have been added to expirations, and only types used by the selected companies appear.
Website down

Sends an alert when a website appears down.

  • No additional settings are required beyond the company, email, and optional webhook.
One-time shared password reveal

Sends an alert when a one-time shared password has been revealed.

  • No additional settings are required beyond the company, email, and optional webhook.
Record created/updated/deleted

Sends an alert when a record is created, updated, or deleted.

  • Select the record type.
    • If the record type is Assets only, select one or more asset layouts in the Asset type field to limit the alert to those layouts. At least one asset layout is required.
  • Select the action to alert on: created, updated, or deleted.

Webhook alerts

Webhook alerts send alert data to external applications. Payloads can include Hudu variables, such as the record name, company, and $USER (who triggered the alert, or the scheduled job for automated alerts). The variables available for each alert type are listed on the alert form below the payload field.

Guides for common webhook providers:

slacklogo.png

Slack

teamslogo.png

Microsoft Teams

discordlogo.png

Discord

zapierlogo.png

Zapier

genericwebhook.png

Generic provider

    Visit Understanding WebHooks for additional information on payloads and the variables available for each alert type.

FAQ

Can an alert apply to every company?

Yes. The company field is required on every alert, but you can use Select All to include every company.

Why don't I see a specific asset expiration type in the list?

The list only shows asset expiration types used by the companies selected on the alert. These types come from date fields in your asset layouts that have been added to expirations. If a selected company has no assets using that field, the type won't appear.

What happened to my existing asset expiration alerts after updating?

Existing single expiration and expiration list alerts set to asset expirations have all asset expiration types selected, so they continue to work as before. Edit the alert to narrow it to specific types.

Does the Alerts list show alerts that have been sent?

No. The Alerts list in the Hudu admin area shows the alerts you've configured, not a history of alerts that have been sent.

Was this article helpful?
2 out of 2 found this helpful