InnerWeb
Skip to main content

Webhook integration cost versus manual retyping of reception events

Manually retyping reception events into a messenger costs a typical plant several dozen hours of work a month, and every delay means security learns about an event too late. Below we break the cost into its factors, show a sample calculation with explicit assumptions, and point out which parts of a webhook integration are one-off costs and which are recurring.

29.3 h
a month spent on manual retyping, sample scenario
Source: sample calculation
28.3 h
monthly saving after the webhook is deployed
Source: sample calculation
5 s
timeout for sending an event
Source: feature card

Where the cost of manual retyping comes from

Manual retyping of reception events is work that does not show up in the budget. A security or reception employee reads the event from the system screen and types it into a messenger channel so that the dispatcher, the health and safety team or the guest's host knows about it. Each such entry takes tens of seconds, and over a month it adds up to dozens of hours.

The second component of the cost is delay. A manual entry is made when someone has a free moment, so information that a training group has failed, for example, reaches the person who could react with a delay. We do not price this component without knowing the plant's process, so the sample calculation leaves it out and counts only working time.

Which events are most often retyped

The reception event webhook covers six event types: guest registration, changes and interruptions of a group at a station, failed and passed training, and guest entry. In practice, the events that are retyped by hand are the ones that require a human reaction: an interrupted group, a failed training and a guest entering a restricted zone.

What a webhook integration costs

A webhook integration has a one-off cost and a recurring cost. The one-off cost covers setting the recipient address in the webhook:reception_url field, building the recipient workflow in the integration tool and testing it on a test guest. The recurring cost is maintaining the recipient: monitoring the service, updates and occasional changes to the entry template.

Events are sent asynchronously as JSON with a 5-second timeout, and a webhook error does not interrupt guest registration. This matters for the calculation: a recipient failure does not generate a reception downtime cost, only a temporary return to manual notification.

Indicative ranges

Setting up a recipient of reception events in a plant messenger usually takes a few working days of the integrator's or IT team's time. These are indicative ranges from 2025-2026 deployments; pricing is individual. Maintenance comes down to a few hours a month, which is what we assume in the calculation below.

What does not need to be bought

The recipient can be a workflow in n8n that publishes entries to a channel in a messenger such as Mattermost or Telegram. An entry about a group in progress is replaced by a new one, and an interruption or a failed training produces a red entry with a sound alert. A separate application for security is not needed.

Hours of work a month spent on reception events

Hours of work a month spent on reception eventsComparison: 29.3 hours a month with manual retyping against about 1 hour of supervision with a webhook.0102030hManual retyping: Work time: 29.3 h29.3 hManual retypingWebhook: Work time: 1 h1 hWebhook
Source: Sample calculation based on the assumptions in the Sample calculation section

Sample calculation: hours per month

The sample calculation for a medium-sized plant assumes 22 working days a month, an average of 40 reception events a day that need an entry in the messenger, and 2 minutes per manual entry including switching between screens. This gives 1760 minutes, or about 29.3 hours a month.

After the webhook is deployed, retyping disappears. About 1 hour a month remains for supervising the recipient and checking that entries arrive. The saving is therefore about 28.3 hours a month. At an assumed rate of PLN 80 per hour of work, this amounts to about PLN 2260 a month, or about PLN 27,100 a year.

If the assumption is 20 events a day, the saving falls by half, and at 80 events a day it doubles. The result is therefore proportional to the number of events and to the time of a single entry, and these are two values that any plant can measure in a week.

How to measure your own values before deciding

The most reliable method is a week of observation: security records how many entries it retyped into the messenger and how much time that took. The result is multiplied by the number of working weeks in a year. A calculation based on your own figures is convincing for management, while the sample calculation serves only as an order of magnitude.

The calculation should also include an item we do not price: the risk of a lost entry. Manual retyping always carries a human error risk, while the webhook passes the timestamp in ISO 8601 format and the ready text unchanged.

  • Number of reception events a day that currently reach the messenger by hand.
  • Average time of one entry in seconds, measured with a stopwatch over a week.
  • Number of people who retype events, and their shifts.
  • Hourly rate set by the finance department, without additional overheads.

Limits of the calculation

The calculation counts working time, not the value of a faster reaction. If the plant has a process in which an entry about an interrupted group triggers an important action, the value of faster information is higher than the saving in hours.

The calculation also does not include the time the team will spend configuring the recipient for the first time. For consistency we treat it as a one-off cost, and we note that the payback already comes within the first months at the volumes described.

Example calculation

Sample calculation: manual retyping versus webhook

Assumptions
ParameterValue
Working days22 days/month
Events requiring an entry40 events/day
Time of one manual entry2 min
Supervision of the recipient after deployment1 h/month
Sample rate80 PLN/h

Result: Manually about 29.3 h/month, after deployment about 1 h/month; saving about 28.3 h/month, or about PLN 2260/month.

Note: Sample calculation. Your plant's values will differ; the result is proportional to the number of events and the time of a single entry.

Video

Frequently asked questions

Does the webhook replace all of security's work?

No. It replaces retyping information into the messenger. Reacting to an event, for example contacting the guest's host, still belongs to a person.

How long does it take to set up the recipient?

Usually a few working days of the integrator's or IT team's time, including a test on a test guest. These are indicative ranges from 2025-2026 deployments; pricing is individual.

What happens if the recipient stops working?

Reception keeps working, because a webhook error does not interrupt guest registration or passing a training. Entries in the channel will reappear once the recipient is repaired.

Let us calculate it with your plant's figures

Together we will measure the number of events and the time spent retyping them, and then show you the reception event recipient in the messenger. Book a conversation with InnerWeb.

Let's talk