Slack

This guide presents the connector configuration for the Slack destination type.

Prerequisites

Some destination types, such as Slack, require you to configure an outbound integration before a notification request can reach the designated connector. Make sure to configure the integration before setting up the connector configuration.

Configuration

Field	Description
Connector name	Select a name that will allow you to easily recognize the connector configuration.
Description	[Optional] Provide a description for the connector.
Integration name	Select an integration from the dropdown menu.
Channel	[Optional] Defines the connector channel to which the notification is sent.
Fallback & test channel	Serves as the default channel If the notification cannot be delivered to the specified Channel.

Templating for dynamic routing

The Channel field supports Tera templating, enabling dynamic routing by inserting variables into the notification configuration. This allows notifications to be sent to different channels within Slack based on alert attributes.

Here are some customization examples:

Example 1: Using alert priority

{{alertDef.priority}}-interface

This configuration dynamically inserts the priority of an alert into the channel name.
The {{alertDef.priority}} placeholder retrieves the priority level from the alert definition (alertDef).
The notification is sent to a channel with the format: priority-interface (e.g., high-interface, medium-interface).

Example 2: Routing based on the first group’s team ID

{{alert.groups[0].keyValues.teamId}}-interface

This configuration dynamically routes notifications based on the team ID found in the first alert group.
The placeholder {{alert.groups[0].keyValues.teamId}} retrieves the teamId value from the first group in the alert.
The resulting notification channel follows the format: teamId-interface (e.g., engineering-interface, security-interface).

Example 3: Using team name when a naming standard exists

[{{...teamName | lower | replace(from=' ', '')}}-interface]

This ensures the team name is formatted correctly by:

Converting it to lowercase (lower).
Replacing spaces with an empty string (replace(from=' ', '')).

The resulting notification channel follows the format: teamname-interface (e.g., devops-interface).

Example 4: Using team name when no naming standard exists

{% set first_group = alert.groups | first %}
{% if first_group is object %}
    {% set team_name = first_group.keyValues | get(key='Team', default='-') %}
{% else %}
    {% set team_name = "-" %}
{% endif %}
{% if team_name == "Supply" %}
    supply-alerts
{% elif team_name == "Billing" %}
    billing-alerts
{% else %}
    techsupport_alerts
{% endif %}

This script determines the notification channel based on the team name in the alert metadata.

If a recognized team name is found, the alert is sent to a predefined channel:

"Supply" → supply-alerts
"Billing" → billing-alerts

If no matching team name exists, the alert defaults to techsupport_alerts.

Generic HTTPS

Next Schema Structures