Configure alerting and notifications

Mode: the create and edit controls described on this page are shown in Expert mode (sidebar footer toggle Mode: Basic / Expert). In Basic mode the page shows only Refresh.

Overview

Configure the alerting items that control when notifications are sent and which accounts send them. Use Alert Profiles to define alert rules, Alert Triggers to define delivery methods, Notification Accounts to configure mail or Twilio sending accounts, and Credential Profiles when a workflow needs stored credentials.

This guide spans two areas of the platform: Steps 1 and 2 are in the Alerting module, Steps 3 and 4 are under Configuration.

Before you begin

• At least one module with alerting is licensed.
• Have the mail server or Twilio account details ready if you plan to add notification accounts.
• Have the required domain, username, and password ready if you plan to add a Run-As profile.

Steps

Step 1

Open Alert Profiles. Click All, Monitoring, Testing, or Uptime to filter profiles by scope. Click Create Profile when you need to add a profile. Expect a profiles table with columns for name, scope, data type, severity, trigger, status, last triggered, count, and actions. See Alerting: Profiles for the full controls reference.

Step 2

Open Alert Triggers. Click Create Trigger when you need to add an Email, Webhook, SMS, or WhatsApp trigger. Expect a triggers table with columns for name, type, status, last used, created by, and actions. See Alerting: Triggers for the full controls reference.

Step 3

Open Notification Accounts under Configuration. Use the Mail Accounts tab to click Add Mail Account and enter the SMTP account details. Use the Twilio Accounts tab when you need SMS or WhatsApp delivery. Test the account before using it in alerting. See Configuration: Notification Accounts for the full controls reference.

Step 4

Open Credential Profiles under Configuration. The page lists credential profiles by type (Windows Run-As, Basic, SQL Login, API Key, Bearer, Service Principal, Azure Function Key, Custom Headers, OAuth2, Platform Tokens) with the columns Name, Identity, Secret, Tags and Actions. Click New Windows Run-As to add a Windows account for impersonation, then fill the profile name, domain, username and password. Use the Edit and Delete row actions to maintain existing profiles. See Configuration: Credential Profiles for the full controls reference.

Verify the result

Alert profiles, alert triggers, notification accounts, and any required Run-As profiles are visible in their tables and are ready to be selected by alerting workflows.

Troubleshooting

• If no alert profiles or triggers are listed, create the required profile or trigger before assigning it to an alerting workflow.
• If email notifications fail, check the mail account SMTP host, port, username, password, and sender address, then run the mail test again.
• If SMS or WhatsApp notifications fail, check the Twilio Account SID, Auth Token, sender number, and recipient format.
• If a Run-As profile cannot be used, confirm the stored username, domain or workgroup, and password are current.

Related articles

• Set up monitoring checks
• Review uptime incidents and alerts
• Alerting: Profiles
• Alerting: Triggers
• Configuration: Notification Accounts
• Configuration: Credential Profiles