Which events the system publishes
The reception events webhook publishes six event types: guest_registered, station_group_updated, station_group_aborted, station_training_failed, station_training_completed and guest_entered. Each one corresponds to a different moment on a guest's path through reception: from registration, through group training at a station, to entry onto the site.
The receiver does not have to handle every type. A typical workflow in an integration tool splits messages by the event type field and sends each one to a separate channel or entry template.
Which event means that a guest has registered?
The guest_registered event is sent once the guest registration is complete. It deliberately does not carry the guest's phone number, because it goes to a plant channel rather than to a system entitled to contact data. For security it is enough to know who registered the visit and when.
What do the events for a group at the registration station mean?
The station_group_updated and station_group_aborted events describe a training group at a registration station: the first reports a change in its state, the second reports that it was aborted. The station_training_completed and station_training_failed events close the training with success or failure. The guest_entered event confirms the guest's entry.
What a single event contains
Each reception event is sent as JSON. It contains the address of the server it comes from, the time of the event in ISO 8601 format in the Europe/Warsaw time zone, and a ready text that can be inserted into an entry without further processing. This way the simplest receiver needs two steps: receive the message and publish the text field.
The ready text does not replace the other fields. If security wants to filter entries by event type or count entries during a shift, the receiver should use the time and type fields rather than parse the text.
Does the event contain the guest's personal data?
The guest registration event does not contain a phone number. The scope of the remaining data is set when the receiver is configured, and minimisation is the rule: the plant channel receives only as much information as security needs to react.
In which time zone is the event time?
In the Europe/Warsaw time zone, in ISO 8601 format. A receiver in another time zone should convert the time explicitly and not assume the local time of the server.
Time limits in reception events
How and when an event is sent
The administrator sets the receiver address in the panel, in the webhook:reception_url field. An empty field means nothing is sent, so disabling the integration comes down to clearing the address.
Events are placed on a message queue and sent asynchronously as JSON with a 5-second time limit. Guest registration, scanning and training completion do not wait for the receiver's response.
Can a slow receiver slow down reception?
No. Sending takes place outside the guest service path, and a webhook error does not interrupt guest registration, scanning or training completion. The worst effect of an unavailable receiver is a missing channel entry, not a blocked reception desk.
What happens when the receiver is temporarily unavailable?
An event that could not be sent within the 5-second limit ends the attempt with an error. Because the error does not affect the business process, security should have a second source of information, for example the screen at the registration station, and the receiver should be monitored like any other plant service.
For installations where the network blocks outgoing traffic from the application server, a separate delivery mode is available, in which the receiver collects messages through a poller. We describe it in the materials on choosing direct or outbox mode.
Training groups and the failure alert
A training group at a registration station lives for 34 minutes. After that time it expires and the receiver gets the station_training_failed event. The same event reports a situation in which nobody in the group was required to complete training.
The receiver gets an alert only about a failure, with no separate notification about success. This way the security channel does not fill up with entries about things that went correctly, and the operator's attention stays on exceptions.
Can the failure alert arrive twice?
Duplicates are blocked by a SET NX marker in Redis. If sending fails, the lock is released so that the alert can go out again. This is a deliberate choice: it is better to receive a repeated alert than to receive none at all.
What the receiver looks like on the plant side
A typical receiver of reception events is a workflow in the n8n tool that publishes entries in a plant channel in Mattermost or Telegram. An entry about a group in progress is replaced by a new entry, and when a group is aborted or fails, a red entry with a sound appears.
Replacing entries has practical value: the channel shows one current state of the group rather than a series of repetitions. Security sees one line per group on the phone, and only a change of colour requires a reaction.
Do I have to use n8n?
No. The receiver can be any service that accepts JSON over HTTPS: a chat tool, a ticketing system or the integrator's own application. The n8n workflow description shows a proven pattern, not a requirement.
How do I check that the integration works?
After entering the address in the panel, register a test guest and check whether the entry appeared in the channel. The step-by-step procedure is described in the guide to configuring the reception webhook.
Video
Frequently asked questions
Does the system retry sending a reception event?
In direct mode the attempt lasts up to the 5-second limit and ends with a result. For the training failure alert, a failed send releases the duplicate lock, so the alert can go out again.
Does disabling the webhook stop guest registration?
No. An empty address field only means that nothing is sent. Registration, scanning and training continue unchanged.
Can I receive notifications about successful training?
The completion event exists, but the alert is sent only for a failure. An entry about a group in progress is replaced by a new one, so the channel does not grow.
Does the guest's phone number reach the plant channel?
No. The guest registration event deliberately does not carry a phone number.
Connect reception events to the plant channel
In a demo we will show how reception messages reach the security chat tool and what the duty officer sees. Book a meeting with the InnerWeb team.
Let's talk