Connecting telematics
An organization admin connects your telematics account once, and Quanty then reads your vehicles' positions, plates and driver names on a schedule. This page walks through the providers, the connection wizard and everything you can do with a connection afterwards. For a telematics Quanty does not read itself, see Your own system (API).
Before you start
- Telematics is part of the TMS add-on. Without it the page says "Telematics is part of the TMS add-on" and "Contact Quanty to switch the TMS add-on on for your organization."
- Only organization admins connect or change telematics accounts. Everyone else sees the page with "Only organization admins can connect or change telematics accounts."
- Have the access details your provider gave you for its API at hand (the table below).
- An organization can have up to 10 telematics connections.
Open Telematics
Open Integrations and the card Telematics (GPS) under Fleet & telematics: "Your trucks live on a map, and a Vehicles table that keeps itself current." It says Connect before the first connection, Connected · 2 with Manage afterwards, and Needs attention when a connection fails. You also get there from Connect telematics on the fleet map, the vehicle board in Tracking and the vehicles list of the TMS.
The page has two parts:
- Connected accounts: "Each account is read on its own schedule." With no account yet: "No telematics account connected yet" and Connect telematics. Once there is one, Open fleet map and Connect telematics sit at the top.
- Providers: "The telematics services Quanty can read from." Each tile says "Vehicle positions, plates and driver names, read on a schedule." with Connect (or Connect another, and "Connected: 1"), and Provider documentation where the provider publishes it.
Providers
| Provider | What you enter |
|---|---|
| Eurowag | API token |
| Inelo GBOX | API user, API password, and Client ID, only when the login sees several clients (optional; a number, found by itself otherwise) |
| Webfleet | Account name, API user, API user password, WEBFLEET.connect API key |
| Samsara | API token, Region: us or eu (optional; European accounts use eu, anything else is read as us) |
| Frotcom | API user, Password |
| Your own system (API) | Nothing: your system sends the positions (see Your own system (API)) |
| Provider | What Quanty reads |
|---|---|
| Eurowag | Positions, the route, drivers, the odometer and fuel |
| Inelo GBOX | Positions, the route, drivers, drivers' working times, the odometer, fuel and the ETA of the truck's own computer |
| Webfleet | Positions, the route, drivers, the odometer and fuel |
| Samsara | Positions, the route, the odometer and vehicle readings |
| Frotcom | Positions, the route, drivers and the odometer |
Ask your provider for a login meant for an API (a separate API user is best). For Webfleet that is a user with WEBFLEET.connect access. In GBOX the API user cannot contain a colon.
Cartrack and Geotab are Planned: "Not available yet. Tell us you use it and we will prioritise it." Their Tell us you need this opens Ask for Cartrack: "We will send a request to Quanty support saying your organization needs Cartrack. We will reply through your support requests." Add Anything we should know (optional) ("For example: how many vehicles, which data you need", up to 1 000 characters) and click Send request. Anyone in the organization can ask.
Eurowag: where the token comes from
Quanty does not issue the token. The wizard's Access step says it:
- "Eurowag issues the API token. Ask your Eurowag account manager or Eurowag support for API access to your telematics data and a token for it."
- "Tokens can expire or be revoked. If the connection stops working, ask Eurowag for a new token and paste it in Rotate token."
- "Quanty reads vehicle positions, plates and driver names."
- "Quanty never writes to Eurowag: nothing you do here changes your Eurowag account."
Connect a provider
Connect telematics (or Connect on a tile) opens the wizard. From a tile it starts on Access with that provider chosen. Everything typed is cleared when you close it.
- Provider: "Which telematics service do your vehicles report to?" Pick one and click Next.
- Access: "The access details Eurowag gave you for its API." Fill in the fields; an empty required field says "Required". Under them: "Quanty stores it encrypted and only uses it to read your vehicles. It cannot be shown again, not even to admins."
- Destination: "Besides the fleet map, where should the positions go?" (below).
- Schedule: how often Quanty asks the provider, a name, and Test and save (below).
Destination
| Choice | What it does |
|---|---|
| Write positions into a table | Pick a Table of a TMS project ("Choose a table"); Vehicles tables are listed first. Every sync updates one row per vehicle. You need the right to change that table. |
| Create a Vehicles table for me | A new Vehicles table in your TMS project, "filled on the first sync". Offered when a TMS project has no Vehicles table yet. |
| No table, map only | "The vehicles are shown on the fleet map only. You can choose a table later." |
Quanty picks the first TMS project's Vehicles table for you when there is one. Without any table in a TMS project, Write positions into a table is greyed out ("There is no table in a TMS project to write to yet."), and without a TMS project at all, map only says "Your organization has no TMS project yet, so positions are shown on the fleet map only. You can choose a table later." Where the positions go also decides who sees them (see Who can see positions), and what is written into the table is on Positions and the fleet map.
Schedule, name and test
- Read positions every: 5 min (the default), 10 min, 15 min, 30 min or 60 min. "The fleet map refreshes on its own; this is how often Quanty asks the provider." The interval cannot be changed later in the app; to change it, delete the connection and connect again.
- Name (optional): for example "Eurowag, tractors". Without one the connection is named after the provider.
- Test and save: "Quanty first tests the access details with the provider, and saves the connection only when they work." While it runs: "Testing...".
If the test fails, the wizard explains it (for example The access details were rejected) with the provider's own sentence underneath, and says "Nothing was saved. Go back to fix the access details, or try again." Test again retries.
When it works: "Eurowag connected" and "41 vehicles found. They appear on the fleet map after the first sync." The first sync runs within about a minute.
The connection row
Each connection shows its name (with the provider under it when you renamed it) and a state:
| State | Meaning |
|---|---|
| Connected | Quanty reads on schedule. |
| Needs attention | Reading fails (amber, with what went wrong under the row). |
| Paused | An admin paused it; nothing is read. |
| Fact | Example |
|---|---|
| Last sync | "4 minutes ago", or "Not yet". |
| Next sync | "in 1 minute", "Due now", "Paused", "Not scheduled", or Paused until the plan is active ("Scheduled sync is paused until this organization has an active plan. Positions already read stay on the map."). |
| Vehicles | "41 · every 5 min". |
| Writes to | The table (a link), or Map only. |
| Token | "ends in ••••3F9A" for token providers (Eurowag, Samsara), otherwise Stored. |
| Position history | "Kept for 90 days": "Position history is kept for 90 days, then deleted." |
What you can do with a connection
| Action | Who | What it does |
|---|---|---|
| Sync now | Admins | Reads at once: "Sync started" or "Sync finished". |
| Sync history | Everyone | The syncs of the last 30 days (below). |
| Test connection (in More actions) | Admins | "The connection works" and "41 vehicles found.", or "The connection does not work". Saves nothing. |
| Pause / Resume | Admins | Stops and restarts reading. |
| Rotate token | Admins | Replaces the token or password (below). |
| Change destination | Admins | "Where the positions are written on every sync. Rows already written stay where they are." Choose a table or No table, map only; a change syncs at once. |
| Rename | Admins | Rename connection, Name, Save. |
| Delete | Admins | Asks "Delete Eurowag?" (below). |
Rotate token
Tokens and logins can expire or be revoked on the provider's side; there is no warning ahead, only the next sync failing with The access details were rejected. Then Rotate token shows right on the row.
- Click Rotate token: "Paste the new token from Eurowag. Quanty tests it with the provider first, and replaces the old one only when the new one works."
- Paste the new token or password (only the secret fields are asked: the Eurowag token, the GBOX password, the Webfleet password and API key, the Samsara token, the Frotcom password).
- Click Replace and test. On success: "Token checked and replaced", the state returns to Connected and a sync starts. If the provider refuses the new one, the old one stays.
A user name, account name, client ID or region cannot be changed this way; for that, delete the connection and connect again.
Delete
"Quanty stops reading positions from this account and its vehicles leave the fleet map. Rows already written to the table are kept." Deleting also removes the connection's position history at once, and the TMS vehicles it fed are no longer linked to telematics.
Sync history
Sync history lists each sync as Running, Done or Failed (Started by hand when someone clicked Sync now), with "41 vehicles read", "3 rows added", "2 rows linked" and "120 cells updated". Before the first one: "No syncs yet. The first one runs a few minutes after connecting." Syncs are kept for 30 days.
When something goes wrong
The row turns Needs attention at once when the provider refuses the access details, and then tries again every 6 hours. Other failures turn it after three failed syncs in a row; Quanty keeps retrying, waiting longer each time (at most an hour), and a good sync clears the error. Being asked to slow down never turns a connection to Needs attention.
| What you see | What to do |
|---|---|
| The access details were rejected | "The provider refused the token or the login. Check them with your telematics provider and enter the new ones in Rotate token." |
| The provider asked us to slow down | "Too many requests in a short time. Quanty waits and tries again; a longer sync interval avoids it." |
| The provider could not be reached | "Its service did not answer. Quanty tries again at the next sync; nothing to do unless it keeps happening." |
| The provider reported an error | Quanty tries again; contact support if it keeps happening. |
| The provider sent an answer Quanty could not read | "This usually means the provider changed its service." |
| Access details are missing | "This connection is missing something it needs: a token, a password or a choice the provider asks for. The detail below says which." |
| The table is gone | "The table positions were written to was deleted or moved. Choose another one in Change destination." |
| Too many connections | "An organization can have up to 10 telematics connections. Delete one you no longer use." |
When Quanty has switched syncs off for everyone, the page says "Telematics syncs are switched off on Quanty right now, so positions are not updated. The accounts and their settings are kept."
Quanty only reads
Quanty never writes to your telematics account: nothing you do in Quanty changes what your provider stores.
Related pages
- Telematics (GPS): the overview.
- Your own system (API): sending positions from your own system.
- Positions and the fleet map: the map, the route, the Vehicles table and the history.
- Telematics in the TMS: linking the fleet, ETAs, kilometres and working times.