Notification channels
A notification channel is a saved connection to a mail server, an SMS provider or a webhook endpoint. Workflows use channels to tell people about alerts: the Send Email and Send SMS steps send through a channel you pick. See Steps.
You manage channels in Settings, Notifications. You need the admin role.
Add a channel
- Open Settings and pick Notifications.
- Click Add Channel.
- Enter a Channel Name, for example
Security team email, and an optional description. - Pick the Type and fill in its settings (see below).
- Leave Enabled on, then click Create Channel.
Email (SMTP)
| Field | What to enter |
|---|---|
| SMTP Host | Your mail server, for example smtp.example.com. |
| Port | Usually 587 (STARTTLS) or 465 (TLS). |
| From Email | The sender address, for example alerts@example.com. |
| SMTP Username and SMTP Password | Optional. The account Argus signs in to the mail server with. |
SMS
Fill in either a Twilio account or your own SMS gateway, not both:
- Twilio Account SID, Twilio Auth Token and From Number.
- Or a Gateway URL. Argus sends each message to it as an HTTP
POSTwith a JSON body offrom,toandmessage.
Webhook
Enter the Webhook URL. A test send posts a small JSON test message to it. To send alerts to a webhook from a workflow, use the Send Webhook step, which takes its own URL and payload. See Steps.
Send a test message
Each channel card has a Send test button. For email and SMS channels, open Recipient email or Recipient phone first and enter where the test should go. The card then shows whether the message was delivered. A disabled channel can't send tests.
Test sends are recorded in the audit log.
Use a channel in a workflow
- Open Workflows and edit the workflow.
- Add a Send Email or Send SMS step.
- Pick the Email Channel or SMS Channel.
- Enter the Recipients: email addresses or phone numbers, separated by commas.
- If you like, write your own subject and body or message. They can use the placeholders
{{camera_name}},{{ts}},{{severity}},{{caption}}and{{event_id}}. See Payload templates. - Click Save Workflow.
If a step's channel is disabled or deleted, the step fails and the run shows as partial or failed in Runs History. The workflow editor warns you when a step points at a channel that no longer exists.
Account emails
Argus also sends one kind of email that isn't about alerts: password reset links, when someone clicks Forgot password? on the sign-in page.
- Open Settings and pick Notifications.
- In the Account Emails card, pick an email channel in Send with.
If you pick none, Argus uses the SMTP relay set in .env (SMTP_*), if there is one. With neither, password reset by email is off, and users who forget their password are asked to contact an administrator. The card tells you what is missing. See Set up password reset email.
Change, turn off or delete a channel
On the channel card:
- Click Edit to change the settings, then Update Channel. Passwords and tokens are shown masked. Leave the masked value unchanged to keep the stored one.
- Use the switch to turn the channel on or off. Workflows can't send through a channel that is off.
- Click Delete to remove it. A channel that a workflow still uses can't be deleted. Change or remove those workflow steps first.
Security notes
- Passwords and tokens are stored in the site database. They are masked in the dashboard, the API and the audit log.
- Mail servers, SMS gateways and webhook addresses can be on your local network, but not on the site's own loopback address, link-local addresses or cloud metadata addresses. To use a mail relay on the host's loopback address, your administrator sets
SMTP_ALLOW_LOCAL=true. To allow other internal targets, they list them inARGUS_EGRESS_ALLOWLIST. See Install.