Notifications and channels
Send ticket notifications to Microsoft Teams, Slack, a Telegram group or a signed webhook, and check who is on call in each group.
On this page
Settings → Notifications has two tabs:
Channels: the team channels where ticket notifications go out, for the whole company or for one resolver group.
On-call: who is on shift right now in each group.
Team channels add to personal notifications. Each person also chooses their own channels (email, browser push, Telegram) in My notifications, from their profile. See Set up your notifications.
Before you start
For the Channels tab you need Administer in the Desks, groups, rules, categories, services and organization module (for example, the Administrator role). Without that level you see Managing channels requires the “Manage” level in Settings.
The On-call tab is visible with View in that module.
Have the tool's connection details ready: the webhook URL, or the bot token and the channel or chat.
Create a channel
Go to Settings → Notifications, Channels tab.
Click New channel.
In Type, choose Microsoft Teams, Slack, Telegram (group) or Signed webhook.
If you chose Slack, in Slack: how it connects choose:
Incoming Webhook (simplest), or
Bot with token and channel (posts the resolution in the same thread).
Click Next.
Enter the Name, for example "IT desk on Teams".
Fill in the details for the type:
Microsoft Teams: Teams webhook URL (Workflows).
Slack with Incoming Webhook: Incoming Webhook URL, which starts with
https://hooks.slack.com/.Slack with bot: Bot token (xoxb-…) and Channel (#support or C0123…).
Telegram (group): Bot token (from @BotFather) and Group chat (id, e.g. -100123…).
Signed webhook: Receiver URL (HTTPS), which will receive the signed notifications.
In Group, choose a resolver group to receive only its notifications, or All groups.
In From, choose which notifications go out on the channel:
Warnings and breaches, or
Breached and critical only.
Select Also notify when resolved if you want the closing notification.
Leave Active selected.
Click Create.
You see Channel created. URLs must start with https://.
For a Signed webhook, Elion ITSM shows you the Webhook secret only once. Copy it into the receiver so it can verify each notification's signature. You cannot see it again afterwards.
Secrets (URL and token) are stored encrypted and are never shown again.
Test a channel
On the channel's row, click Test. You see Test sent: check the channel in a few seconds and, shortly after, the Status column updates.
The channel list
Column | What it shows |
|---|---|
Channel | Name and type ("· bot" if it is Slack with a bot). |
Destination | The destination server. |
Group | The resolver group, or All. |
From | Warnings or Breached, and "+ resolved" if it also notifies the closing. |
Status | working, failing (with the last error), untested or off, and when the last send was. |
Edit, pause or delete a channel
Click Edit. Secret fields appear empty: leave them that way to keep them unchanged. Clear Active to pause the channel.
For a webhook, when editing you can select Generate a new signing secret (the previous one stops working). The new secret is shown only once.
To delete it, click the trash icon and confirm with Delete. It stops receiving notifications immediately.
Notifications for tickets in a private desk do not go out on All groups channels: only on the channels of the ticket's group.
On-call tab
It shows each resolver group with its Desk, its On-call (active or no on-call) and who is On shift now, with the cover tag when it applies. A group without on-call says Notifies the whole group; one with on-call but nobody on shift says Nobody (check the shift). Times are shown in the company's time zone.
If you have Administer in the module, click On call on the row to change the rotation or add a cover. See On-call and covers.