1. Home
  2. Features

Features

Sources

Notify.Events offers integration with over than 40 sources out of the box. You can find a full list of implemented sources in our "catalog".

Customization and your own sources

Any source presented in the service you can change to suit your needs (formatting, localization, its own processing logic).
Also you can create your own integration for any service which have outgoing webhook or e-mail notifications.

Recipients

Telegram Email SMS iOS Android Viber Signal Skype Browser notifications Voice call Discord Viber Custom Slack Webhook Microsoft Teams Webhook Slack Twilio (SMS) Outgoing Webhook Pushbullet Green API VK RSS Facebook Messenger Custom Line Twilio (Voice call) Zoom Webhook Pushsafer Skype Custom ClickSend (SMS) Sms.ru Google Chat Webhook Rocket.Chat Email Threema Atom Line Custom WirePusher Mattermost ClickSend (Voice call) IRC SimpleTextin Prometheus Exporter Webex Webhook Plivo Potato Chat TextLocal VK Custom Bandwidth TeleSign Firebase Cloud Messaging Jabber / XMPP Ryver DingTalk Emby Telegram Custom Gitter Flock Chatwork Vonage
1 The length of some recipient messages is limited or has a higher delivery cost.
2 Some messengers recognize and highlight links in messages, even if they do not support formatting.
3 If the recipient does not support chat actions, then depending on the source implementation, notify.events allows you to display them as direct links.
4 Some messengers do not see the difference between files and images, which means that they ignore the "Send as file" flag and display it as a picture. If the recipient does not support attachments, then depending on the source implementation, notify.events allows you to display them as direct links.
5 For some notification methods, Notify.Events charges an additional fee. You can find more information on the "pricing" page.

Messages

Messages filter

All messages in Notify.Events are assigned with a priority and level by the source.
You can use these and other properties to filter messages for each subscription.

Priority

The priority determines the importance of each message. There are 5 values in total: "Highest", "High", "Normal", "Low" and "Lowest"
This property allows you to distribute messages based on their priority and send them in a way that suits you.
For example, send "Lowest priority" messages to Telegram, and "Highest" ones - by the phone call.

Level

Defines the "type" of the message. There are 6 types in total: "Verbose", "Info", "Notice", "Warning", "Error" and "Success"
Levels allows you to know the state of the source that sent the notification and forward those notifications in an appropriate way.
For example, send a "Verbose" message with a full build log to e-mail, and an "Error" message - to Slack, to decrease your team reaction time.

Reception time

In the properties of each subscription, you can define at what time and day of the week it will receive notifications.
For example, this allows you to organize shift work (notifying employees only on their shift) or to implement various notification methods depending on the time of day:
send messages to your Viber during the day, and get any important notification by the phone call on night.