What does a rule consist of?
An if-this-then-that rule consists of three elements arranged from icons: an event, a filter and an action. The event can be a permit status, an alarm, no movement, SOS or a schedule. The action can be an e-mail, a push, a team notification or a webhook.
The filter narrows the event, for example to one hall or one group of people. Thanks to it the rule does not react to every event in the plant, only to those that matter for a given team.
- event: permit status, alarm, no movement, SOS, schedule
- filter: narrowing to an area or group
- action: e-mail, push, team notification, webhook
Step 1: choose the no-movement event
Add the event icon and choose the no-movement alarm. The event appears when the system detects that a person working alone has not moved for longer than the configuration allows. The rule runs automatically when it occurs.
Before saving, check that the time is set in the no-movement configuration, because the rule reacts to the event and does not define the threshold.
Number of options in each element of a rule
Step 2: add a filter
Add the filter icon and narrow the rule to the area the team is responsible for. Two halls with separate teams should have two rules, so that each team gets only its own alarms.
An overly broad filter is the most common cause of notification fatigue. Start with a narrow scope and widen it after a week of work.
Step 3: add the team notification
Choose the team notification action. The plant's team channel in the messenger is switched on with one setting containing the messenger's webhook address. Once enabled, alarms and events appear in the channel the team already has open.
Send a test event and check that the message reached the right channel.
Step 4: add a webhook to an external system
The second action is a webhook, which passes the event to an external system, for example a ticketing tool or a dispatch system. A rule can have several actions at once, so the team and the external system receive the same event at the same time.
If the client's network blocks outgoing traffic from the application host, alarm webhooks are stored permanently in a queue, and an external poller collects them through an incoming channel. The event is not lost, it waits to be collected.
Step 5: save, test and describe the rule
Save the rule with a clear name that states the event, the area and the addressee. After a month the plant has a dozen rules, and without names nobody knows which one does what.
Run a test in the presence of the team: trigger a test event, check the team channel and the receipt of the webhook. Record the result as proof of the implementation.
Video
Frequently asked questions
Does building a rule require a developer?
No. Rules are built from icons in the administrator panel.
Can a rule trigger several actions at once?
Yes. One event can trigger a team notification and a webhook at the same time.
What happens to a webhook when the network blocks outgoing traffic?
The webhook is stored permanently in a queue, and an external poller collects it through an incoming channel.
Does the team notification need a separate integration?
One setting with the channel's webhook address in the messenger is enough.
Want to build a rule for your team?
Book a demo. We will show how to assemble a rule from icons and send a notification to the team channel on test data.
Let's talk