Slack and Microsoft Teams notifications

HyoNova can post the notifications you choose to a Slack channel or a Microsoft Teams channel: "Chosen notifications are also sent here. Notifications inside HyoNova are not affected." It is one-way. HyoNova posts to the channel; it does not read anything from Slack or Teams.

How it works#

A notification channel in HyoNova is one webhook address that you create in Slack or Teams. The address decides where messages go; HyoNova posts wherever it points. You choose which events are sent, and HyoNova keeps a log of every message and whether the provider accepted it.

Company work never waits for Slack or Teams. A task is assigned whether or not the channel answers; the message is sent afterwards, and retried if needed.

Add a channel#

Create the webhook in Slack or Teams. See the two sections below.
Open the card. In HyoNova, go to Company administration › Integrations, open Slack or Microsoft Teams, and choose Add channel.
Name it. Name in HyoNova is how the channel is listed. Channel (for your reference) is a note for you, for example the Slack channel's name; it does not decide where messages go.
Paste the Webhook address. "This address is a secret. It is stored encrypted and is never shown again."
Choose What to send, the Detail, the Language and At most per hour.
Save, then choose Send test. A new channel reads Send a test to start. It begins sending only after the provider accepted a test message.

Create the webhook in Slack#

HyoNova shows these steps on the card: create an app at Slack's app page, open Incoming Webhooks, switch it on, choose Add New Webhook to Workspace, choose the channel, and copy the webhook URL.

HyoNova accepts only a Slack incoming webhook address, which starts with https://hooks.slack.com/services/.

Create the workflow in Microsoft Teams#

In Teams, open the channel, then ⋯ › Workflows, and choose the template Send webhook alerts to a channel, whose trigger is When a Teams webhook request is received. Save it and copy the link.

HyoNova accepts the address of such a workflow. Addresses of the older Office 365 connectors are refused, because Microsoft is retiring them.
"A Teams workflow belongs to the person who created it. Add a co-owner in Power Automate so it keeps working if they leave."

What you can send#

Under What to send, tick the events for this channel. With nothing ticked, the channel receives only test messages.

Group	Events
Tasks	A task is assigned, A task becomes overdue, A task is completed
Projects	A milestone is completed, A project is completed
Meetings	A meeting is scheduled, A meeting is moved, A meeting is cancelled
Bookings	A booking is made, A booking is moved, A booking is cancelled
Support	A high-priority ticket arrives, A ticket passes its response time
Approvals	An approval is requested

Different channels can receive different events — for example bookings to a sales channel and overdue tasks to a team channel.

What leaves HyoNova#

A message says what happened and, when allowed, names the record.

Detail	What a message contains
Titles when allowed	The event and the name of the task, project, meeting or booking type — unless the record is confidential
Never a title	The event only, never a name

Whatever you choose:

Confidential records never send their title.
A message never contains a visitor's or a customer's name, an email address, or the text of a message or ticket.
A booking message names the booking type, never the visitor. Meetings that HyoNova creates for a booking are not announced separately.

Remember that everyone in the Slack or Teams channel can read what is posted there, including people who are not members of your HyoNova company.

Test, pause and remove#

Action	What it does
Send test	Posts one test message now and shows the result
Pause, Resume	Stops and restarts sending. Notifications that fall due while a channel is paused are skipped, not sent later
Remove channel	"HyoNova forgets the address and stops sending. Nothing changes in Slack or Teams."

To change the address, edit the channel and paste a new one; leave the field empty to keep the stored address. To stop HyoNova at the source, delete the webhook or the workflow in Slack or Teams.

Results of a test:

Result	Meaning
The provider accepted the test message. Check the channel.	Slack or Teams took the message
The provider refused the message (with a code)	The address is wrong, or the webhook or workflow was removed or disabled
The provider could not be reached (with a code)	A network problem between HyoNova and the provider
The provider is limiting requests right now. Try again in a minute.	Too many messages in a short time
This address cannot be used (with a code)	The address is not a Slack incoming webhook or a Teams workflow address

"“Accepted” means the provider took the message. HyoNova cannot know who read it."

Channel states#

State	Meaning
Send a test to start	The channel is saved but has not passed a test yet
Sending	Chosen events are being sent
Paused	Paused by your company
Stopped after repeated refusals	"This channel stopped itself. Fix the webhook if needed, then send a test to start it again."
Paused by HyoNova	HyoNova paused this service for everyone for now. Your settings are kept

The delivery log and retries#

Each channel lists its Recent messages with a status, the number of Attempts and, for a message that will be tried again, the Next attempt.

Status	Meaning
Waiting	Queued to be sent
Sending	Being sent now
Accepted	The provider took the message
Failed	The provider refused it or could not be reached, and the attempts are used up
Blocked	The address could not be used
Skipped	Not sent: the channel was paused, or the hourly maximum was reached

How retries work:

A message that could not be delivered is tried again after 30 seconds, 2 minutes, 10 minutes, 1 hour and 3 hours — six attempts in all. If the provider asks HyoNova to wait, HyoNova waits that long.
After five messages in a row end in a refusal, the channel stops itself and reads Stopped after repeated refusals. Send a test to start it again.
At most per hour is a ceiling for one channel (60 unless you change it). Above it, messages are skipped instead of flooding the channel.
Send again re-sends a failed message by hand.
The same event is never posted twice to the same channel.

Security#

The webhook address is treated as a password: it is stored encrypted in a secret store, never shown again, and never written to logs. HyoNova shows only that an address is stored.
HyoNova sends only to Slack's and Microsoft's webhook hosts, over HTTPS, and does not follow redirects.
Anyone who has the webhook address can post to your channel. If it leaks, delete the webhook in Slack or the workflow in Teams, create a new one and paste the new address.

Limits#

Your plan can limit the number of notification channels. When a limit applies, the card shows how much is used.

What this does not do#

It does not read messages, channels or members from Slack or Teams.
It does not send direct messages to people, only to the channel a webhook points at.
It does not let people act on HyoNova from Slack or Teams.
It does not replace notifications inside HyoNova; those keep working as before.

Status#

Feature	Status	Notes
Slack notifications	Beta	Send the notifications you choose to Slack channels through incoming webhooks, with a test message, a pause and a delivery log.
Microsoft Teams notifications	Beta	Send the notifications you choose to Teams channels through a Workflows webhook, with a test message, a pause and a delivery log.
Integration Hub	Beta	One page in Company administration for the tools your company connects, each card showing what is really connected.