InnerWeb
Skip to main content

Reception notifications in the plant messenger

The security manager of a food plant wants to know who has registered and who has entered the site, without sitting at the reception screen. A reception events webhook sends this information to a channel in the plant messenger, and a guest's phone number is deliberately not part of it. We describe the scenario from the event to the entry in the channel.

6
reception event types
Source: karta
5 s
webhook delivery timeout
Source: karta
34 min
lifetime of a training group
Source: karta

The need: information about guests where security already looks

A food plant with raised hygiene and safety requirements usually has one entry point for guests and several recipients of the information: security, the visit host and the shift manager. Each of them already uses the plant messenger, so a separate screen or mailbox is one more place to watch.

The scenario assumes that the InnerWeb guest registration system is the source of events and a channel in the messenger is the recipient. As a result the security manager sees the course of each visit in one thread, without logging in to the panel and without phone calls from reception.

How an event reaches the channel

The reception events webhook publishes six event types: guest registration, an update of a group at the registration station, a group being interrupted, a failed training, a passed training and a guest entering the site. The recipient address is set in the panel in one field; when the field is empty, nothing is sent.

Events go onto a message queue and are sent asynchronously as JSON with a 5-second timeout. As a result, a webhook error does not interrupt a guest registration, a scan or a passed training. Reception keeps working normally, even when the messenger has an outage.

What a single event contains

Each event carries the server address, the time of the event in ISO 8601 format in the Europe/Warsaw time zone, and a ready-to-display text. The recipient does not have to assemble a message from fields; it only has to publish the ready text.

Why there is no guest phone number

The guest registration event deliberately does not carry a phone number, because it goes to a client channel that many people read. This is an example of data minimisation: the channel gets the information needed to react, not the contact details, which stay in the registration system.

Reception webhook parameters

Reception webhook parametersBar chart: 6 event types, a 5-second delivery timeout and a 34-minute group lifetime.010203040valueEvent types: 6 value6 valueEvent typesDelivery timeout (s): 5 value5 valueDelivery timeout (s)Group lifetime (min): 34 value34 valueGroup lifetime (min)
Source: Description of the Reception Events Webhook feature (product documentation)

The recipient: an n8n workflow and the plant channel

The recipient of the events is an n8n workflow, which publishes entries to the plant channel in the messenger, either Mattermost or Telegram, depending on the plant's choice. An entry about a group in progress is replaced by a new entry, so the channel does not fill up with repeated updates of the same visit.

When a group is interrupted or a training is failed, the workflow publishes a new red entry with a sound alert. This pattern makes sense in terms of organisation: ordinary events are quiet and sort themselves out, while a deviation from the norm draws attention.

Two pitfalls worth knowing before the start

The first pitfall concerns training. A training group at the registration station lives for 34 minutes, and the event for a failed training reports that the group expired or that no training was required for that person. The recipient gets an alert only for a failure, with no separate notification of success. A security manager who expects confirmation of every passed training has to take this into account when reading the channel: the lack of an alert is not proof of a passed training, the training report is the source for that.

The second pitfall is duplicates. The alert for a failed training is protected by a marker in Redis that blocks repeats. When sending fails, the lock is released so the alert can go out again. In practice, after a messenger outage the same alert may therefore appear once more, which is the intended behaviour.

Conclusions for the security manager

The scenario gives the security manager one source of information about visits, without pulling guests' contact data into the channel. The condition is that the recipient in the channel is configured correctly and that the team knows the rule that alerts are sent only for failures.

Before going live, run a test registration and check that the six event types produce the expected entries in the channel: this is how evidence of receipt on the plant side is created.

Video

Frequently asked questions

Will a messenger outage block a guest's registration?

No. Events go through the queue asynchronously with a 5-second timeout, and a webhook error does not interrupt registration, a scan or a passed training.

Will a guest's phone number appear in the channel?

No. The registration event deliberately does not include it, because it goes to a client channel that many people read.

Will I get a notification for every passed training?

The recipient gets an alert only for a failure, with no separate notification of success. Confirmations of passed trainings are in the training reports.

Reception notifications in your channel

Book a call and see how guest registration events reach your plant's messenger.

Let's talk