Message Merger application icon — a white wrench outline on an orange rounded square Product Wialon trusted partner

Data the tracker never sent, inside the unit anyway.

A Wialon unit binds to exactly one tracking device, so everything else a customer owns — cold-chain probes, weighbridges, ERP job events, a driver app, a third-party API — has no way in. Message Merger takes a webhook from any of them, maps its fields onto Wialon message parameters and writes them into the unit that keeps its real tracker.

Book a free call Product site merger.theassettrack.com
Message Merger's admin: three webhook senders, each with the Wialon unit it writes to and the parameter names it may set, then one sender's mapping — JSON paths turned into cargo_temp, door_open, probe and load_kg — and the queue counting what has been buffered, imported and retried

What it fixes

  • A unit has room for exactly one device

    Everything Wialon knows about a vehicle arrives through that device's protocol. A probe, a weighbridge or an ERP event has no protocol slot to arrive in, so it cannot become a sensor, a report column or an alert.

  • The usual answer is a second platform

    Merge the streams in flespi and feed Wialon one combined virtual device. It works — and it is another vendor, another bill and another system to operate for the sake of one number.

What it does

  • An endpoint per sender

    Each system posts to its own hook with its own field mapping, so adding a sender changes nothing for the ones already running.

  • Fields become parameters

    A body of {"celsius": -18.4} arrives on the unit as the parameter the mapping names, beside everything the tracker sent.

  • Sensors read it like any other value

    A Wialon sensor bound to the parameter renders it in Wialon's own formatting — which is what a report prints and a notification tests.

  • The tracker stays exactly where it is

    Nothing about the unit's device changes. The imported messages sit alongside the tracker's own, on the same unit.

  • Buffered per unit, imported in order

    One import at a time across the account, a buffer per unit, and a dead letter for anything Wialon refuses, with the reason it gave.

  • Batched, because only batching works

    Of the two ways into Wialon, the real-time one requires the unit's device type to be Wialon IPS. The HTTP import accepts any unit, so that is the path this takes.

How to open it

This one is not self-serve yet. We stand the endpoint up against your account, configure the first sender with you, and hand over the admin app that shows what is configured and what the queue is doing.

  • Option A: Ask for an endpoint

    1. 1. Tell us the unit and the system that has the data.
    2. 2. We map its fields onto Wialon parameters and arm the hook against your account.
    3. 3. Your system posts to the hook; the values show up on the unit, and a sensor reads them back.

FAQ

Why not send it over Wialon IPS?

Because IPS only accepts messages for a unit whose device type is Wialon IPS. A unit that already has a real tracker is not that, and changing its device type would cost the tracker. The HTTP import path accepts any unit, so that is the one used.

Does the imported value merge with the tracker's message?

No. It lands as a message of its own at its own timestamp, beside the tracker's. A sensor bound to the parameter reads messages that carry that parameter and no position, which is worth knowing when a report expects coordinates on every row.

Can a reading be back-dated?

It can carry its own timestamp, but not a future one: Wialon silently rewrites anything ahead of the clock to the time it arrived, so nothing can be post-dated into the account.

How quickly does a value appear?

Seconds, not milliseconds. The webhook is acknowledged immediately, the import is batched behind it, and acceptance by Wialon is not the same as the message being visible — which is why the admin app shows the queue rather than claiming success.

Is this instead of flespi?

For this one job, yes: it puts the extra data on the unit without a second platform in the path. Where a customer already runs flespi, or needs real-time streaming rather than batches, flespi remains the better answer — and we build on it too.

What state is it in?

Preview. The chain has run end to end on a live account: a webhook became a message, and a Wialon sensor bound to its parameter read it back as -18.40 °C in Wialon's own formatting. We are taking early users one at a time rather than listing it as finished.

Related

Guide · Integration

Webhook Data into a Wialon Unit

A Wialon unit takes one tracker. Message Merger writes probe, weighbridge or ERP readings into that same unit as parameters sensors and reports can read.

Read more

Let's connect

  • “Our client needed a data pipeline. It came back working, plus a few Wialon fixes we had not asked for. That client trusts us more now.”
    Faiz K. Customer Manager · Trakpro Limited
Book a call