We are not a telematics provider, but we have known the field for a long time: it is a strong platform, and we have not met deeper reports anywhere in telematics. FlowTrux simply complements it: connects Wialon to everything that lives around it, so the jobs that cost providers and fleets hours and people get done more flexibly and for less. What follows is not slides — it is real workflows from one fleet.
Where Wialon ends — and everything else begins
Wialon is telematics automation: trackers, sensors, reports, notifications, geofences, schedules. On its own turf it does almost everything. But around it, a provider or a fleet has another dozen systems: the ERP and master data — clients, contracts, vehicles, drivers, fuel cards, orders — the billing that sends invoices, the task tracker for the technicians, the spreadsheets where the important stuff somehow always ends up, the email and messengers where decisions get made. Every time a task crosses the line between Wialon and any of those, a person is needed: export, merge, copy over, write it up, remember to send it.
The cost of that manual bridging is made of small things that appear on no invoice: the dispatcher's hour on the morning summary, the technician's trip to “offline” units half of which are simply parked at the depot, the manager's evening building a client report from three exports. Add the mistakes that come with numbers copied by hand, reactions half a day later than they could be, and the report a client never received because there was no time. Small things one by one; together, a visible line of expense and missed opportunity.
FlowTrux sits exactly on that line — a gateway between Wialon and everything around it. A workflow reads from Wialon, picks up what it needs from the ERP, the vehicle and driver master data, a spreadsheet or a fuel-card statement, does the math, and an agent puts the result into words. Then the result goes where it is needed: a messenger (Telegram, WhatsApp — whichever your people use), email, a PDF, a task for the technician in the tracker, a record in the ERP, or a live page on a link the client opens without logging in. Prettier, yes — but mainly cheaper: what used to take hours is set up once in minutes, and then it just runs.
How it connects
Wialon is a built-in integration: paste a token in Settings, assign it to a workspace. From then on, workflow steps and the assistant can read everything the token has access to — units and groups, any report template with its options and filters, live sensor values, messages, events, drivers, geofences, routes. Your Wialon data stays as it is.
Two things matter for a provider. One workspace per client: each fleet in its own workspace with its own token; the client's staff see only their workspace and run only what they are allowed to. And honest answers: names instead of ids, units and time zones instead of raw numbers, and a report that does not support your filter says so before the workflow runs instead of quietly returning a wrong table.
Seven workflows from one fleet
1. Your own Dashboard — in the morning, in the chat, on a link
Wialon has a Dashboard app: the fleet's summary figures on one screen. Handy — as long as you are inside Wialon. Our version starts from the same place but lives where people read it. At 07:00 the workflow reads yesterday from Wialon — units with current positions, the group's trips, the day's statistics, eco-driving, every unit's sensors — merges it into one structure and hands it to an AI agent, which writes a dashboard: KPI cards, status and eco-driving charts, a units table, trips, fuel and sensors. It goes out as an A4 PDF to the dispatchers' chat (Telegram here; any other messenger works the same way) and as a page that always shows the latest run.
Wialon can build each of these tables, and Dashboard shows them to whoever opens Wialon. What it will not do is put five of them on one page in your layout, write “two units did not report overnight, the Scania drained 40 litres at 23:40” above them, send it to the chat at seven, and give the owner a link to open on a phone without logging in.
2. Vehicle trips on a link
The most common client request: yesterday's trips without logging in. A trips report for the client's group, a clean table with totals, routes on a map, on a link they bookmark. The page shows the last successful run, so a failed report never shows a client a half-empty page.
3. Your own Sensolator
Anyone on Wialon knows the Sensolator app: the whole fleet on one screen, in real time. A good idea — and exactly the one we asked the assistant to reproduce, our way. The workflow walks the units and reads what matters for each: status and speed now, the driver, mileage and trips for the week, the eco score, the age of the last message and the last position — and publishes a page: fleet totals on top, a units table, and a card per unit with its own map. Three things differ from the ready-made app: the page was built in one conversation and changes with the next sentence; it opens on a link, without a Wialon login; and it comes with an alert to a messenger — only when something is wrong, instead of a screen someone has to keep watching.
4. Tracker or vehicle?
A unit goes silent: parked with the ignition off, a dead tracker, or a cut power line? The status icon says “no data” for all three. Device Healthy Checkcombines the age of the last message, the ignition sensor and a depot geofence, and sends one grouped message — these are probably parked, these need a look at the device — instead of twenty “unit offline” notifications.
5. Geofences — who was where
Control Geofencesreads visits for the period and compares them with the plan: a unit in a zone it should not be in, or leaving the depot outside working hours, is reported with time, duration and the driver assigned at that moment. A step reads a unit's drivers and geofences directly, so nobody joins three reports in a spreadsheet.
6. Eco Driving as a weekly note
Wialon's Eco Driving app and the report of the same name score harsh braking, acceleration, cornering and speeding per driver — they score well, but the output is a forty-row table and it is rarely read. We take exactly those scores and turn the week into a short note: the three best and the three worst indicators, and what changed since last week. The workflow computes the numbers; the agent only writes the words, so the text never gets the arithmetic wrong. The note goes to the manager's messenger on Monday morning — and gets read, because it is short and arrives by itself.
7. A route on a map
Two workflows draw a unit's route for a period — from raw messages point by point, or from the trips report trip by trip with stops — and publish a page with an interactive map: zoom, markers, a popup with speed and time. The map library ships with FlowTrux, so the public page loads nothing from outside.
The Vehicle trips page above is one of them.
How these get built
None of this was drawn by hand. You open the assistant, describe the job the way you would brief a colleague, and it proposes the steps as cards you apply. Three things make it reliable with Wialon rather than a presentation trick: the assistant asks Wialon while it builds (which groups exist, what a report returns, whether an id is a unit or a resource) and checks every Wialon step before adding it; it tries a calculation on your last run's real data before proposing it; and numbers are computed in a step, words are written by the agent.
What FlowTrux adds to Wialon
| Wialon gives you | FlowTrux adds |
|---|---|
| Deep reports, one at a time | Several reports and live values combined into one result |
| Tables and a few standard charts inside Wialon | Any report table turned into a chart, a KPI card or a map with one sentence to the assistant; your own layout — dashboard, note, map — published on a link |
| A notification per event | One grouped, explained message — wherever it is needed: messengers (Telegram, WhatsApp), email, files (PDF, spreadsheets), any third-party system with an API — ERP, task tracker, billing |
| Fleet data only | Fleet data joined with the rest of the business: master data and orders from the ERP, spreadsheets, tasks in the tracker, documents in a knowledge base |
| A login per user | A link per client; one workspace per fleet for a provider |
| Numbers | Numbers plus the two sentences a manager actually reads |
And not only the fleet. The same workspaces that run Telematics & IoTcover support and sales in the same organization: a request from the website or a messenger is read by an agent, lands in the ERP and with the right manager, and the client gets a reply; customer issues are routed to the technicians' task tracker; HR screens candidates from their applications; weekly reporting is assembled from spreadsheets and the ERP and reaches management by itself. Any repeating process in the company is built the same way — a trigger, a few steps, an agent where judgment is needed, a result delivered where people already look — and built in a conversation with the assistant, not by developers.
If you run more than one fleet
This is most useful to telematics providers and integrators: dozens of client fleets in Wialon, each asking for something beyond the standard reports. That is the work FlowTrux is shaped around: one organization — yours; every client is a separate workspace with its own Wialon token, its own recipients and its own workflows; set it up for one client, save it as a template, roll it out to the next in minutes.
How you sell it is your call. You can hand the client a finished thing: invite their staff into their workspace with rights to view and run, and they live with it from there. Or keep it on your side and sell it as a service — “morning summary, alerts and dashboard” as a line on your invoice, with FlowTrux as the tool behind the curtain. Both work today, nothing to build.
Try it on one of your clients.Connect their Wialon token, pick a fleet template, and ask the assistant for tomorrow morning's summary — by the evening you will have a first workflow to show them.