Channel Configuration
Channels store the delivery details for notifications. A channel defines where the message is sent and what delivery method is used.
Channel types :-
| Type | What it does |
|---|---|
| Sends notification emails using a configured email sending service | |
| SMS | Sends text message alerts using an SMS provider |
| Webhook | Sends notification data to an external URL for integrations |
What channel configuration includes
Email channels
Email channels typically include:
- Sender email address (the "From" address)
- Email provider or delivery method (SMTP, SendGrid, or another mail provider)
- SMTP host and port
- Authentication credentials (username/password or API key)
- Encryption settings (TLS/SSL)
This configuration tells Hunto how to deliver email notifications.
SMS channels
SMS channels typically include:
- SMS provider name
- API key or authentication tokens
- Sender ID or phone number used for outgoing SMS
- Regional or routing settings if required by the SMS provider
This configuration tells Hunto how to send text message alerts.
Webhook channels
Webhook channels typically include:
- Webhook URL where Hunto should send the notification payload
- Authentication headers or secret if the endpoint requires them
- Payload type or format information
- Provider-specific settings if needed by the target system
This configuration tells Hunto how to deliver alerts to another system, such as Slack, Teams, JIRA, or a custom application.
How channels work with notification rules
Each notification rule points to one channel configuration. That means the rule decides what to send and who should receive it, while the channel decides where and how the message is delivered.
For example:
- A detection alert rule may use an email channel to send a message to security analysts.
- A status update rule may use a webhook channel to post to an external incident management system.
The Channels tab is where you review and manage the delivery methods separately from the rules themselves.