Teams and webhooks
Slack reaches people one by one. Microsoft Teams and a generic webhook work differently: they receive everything Delegaris announces as a stream of posts, to a channel or to another system.
What is sent:
| Event | What it covers |
|---|---|
keep_on | Keep-on reminders and ends |
approval | Approval requests and decisions |
access_request | Requests for access, and their answers |
alert | Alerts: AWS credentials failing, timed stops not finishing, backups failing |
summary | The weekly summary, on Mondays. It is only produced when Slack is connected and a Weekly summary channel is set |
test | Test messages |
Both are set under Settings > Notifications, in the Microsoft Teams and webhooks section. Either, both or neither can be used, alongside Slack or without it.
Microsoft Teams
Teams receives posts through a Workflows webhook.
- In Teams, on the channel, open Workflows and choose Post to a channel when a webhook request is received.
- Follow the steps and copy the address it gives you.
- In Delegaris, paste it into Microsoft Teams under Settings > Notifications.
- Press Test beside it. A test message arrives in the channel, and Delegaris shows "Teams: Sent." or why not.
- Press Save changes.
Posts arrive as Adaptive Cards. Office 365 connector addresses still work for as long as Microsoft keeps them.
Teams posts carry a link to the right page in Delegaris instead of buttons. Buttons in Teams need a registered bot, which a channel webhook is not. Approvals are decided on the Approvals page.
Generic webhook
Any HTTPS address can receive the events as JSON: a ticketing system, a chat bot, a log collector.
- Enter the address in Webhook.
- Optionally enter a Webhook secret, so the receiver can check posts really came from Delegaris.
- Press Test beside the address. Delegaris sends a
testevent and shows "Webhook: Sent." or why not. - Press Save changes.
The secret is never shown again. To keep it, leave the box empty when saving; to replace it, type a new one.