Automating Company Vehicle Fleet Tracking with n8n

A van taken off the road on a Monday morning because its roadworthiness inspection expired over the weekend, a fleet insurance policy cancelled without clear notice because no one saw the renewal deadline coming, a manufacturer service that would have prevented a costly breakdown if it had been scheduled three weeks earlier: in a small or mid-sized business running five, ten, or twenty vehicles, these incidents are almost never caused by poor maintenance — they come from a date that lived in one person's head, or in a spreadsheet opened once a quarter. This guide builds an n8n workflow that centralizes every vehicle's deadlines, automatically computes the next critical dates, and alerts the right person before it's too late.

What to track, vehicle by vehicle

A company fleet actually accumulates three distinct families of deadlines that are rarely in sync with each other:

• The roadworthiness inspection, mandatory for any category M1 (car) or N1 (light commercial, gross weight ≤ 3.5 tonnes) vehicle: a first inspection within the six months before its fourth registration anniversary, then every two years after a pass. Since January 1, 2026, the inspection also checks whether any serious manufacturer recall ("stop drive") is still unresolved — an affected vehicle can be classified as a critical failure on the spot, which grounds it immediately.
• The supplementary pollution check, specific to diesel light commercial vehicles from their fourth anniversary: annual, so on a different cycle from the main roadworthiness test — the deadline most often forgotten on a van-heavy fleet.
• Fleet insurance and manufacturer servicing, whose dates follow no common regulation and vary from one vehicle to the next depending on the contract signed and the maintenance log.

Without a centralized registry, these three clocks run independently for every vehicle — and that's exactly what a workflow needs to unify.

Workflow architecture

Vehicle table (Airtable / Google Sheets / n8n Data Table)
  → plate number, category (car/van), fuel type, registration date,
    date of last roadworthiness inspection, insurance deadline, mileage, assigned driver

Schedule Trigger (daily, early morning)
  → Read the vehicle table
  → Code node: compute the next deadline per vehicle
      (inspection = last inspection + 2 years, or registration date + 4 years if no inspection on file;
       diesel van pollution check = last inspection + 1 year from year 4 onward;
       insurance and servicing = read directly from the table)
  → Filter (deadline ≤ D+60)
  → Switch (D-60 heads-up / D-30 reminder / D-7 urgent)
  → Slack or email to the assigned driver, copying the fleet manager
  → Update a "last alert sent" field (anti-duplicate)

Schedule Trigger (weekly, Monday morning)
  → Aggregate every upcoming deadline
  → HTTP Request → Gotenberg (summary PDF report)
  → Send to the fleet manager

Step 1 — One table, one source of truth per vehicle

Everything relies on a single registry that replaces paper maintenance logs and reminders scattered across several calendars. Google Sheets works well for up to about ten vehicles; beyond that, Airtable or an n8n Data Table provide views filtered by category or driver, useful as soon as a vehicle regularly changes hands. Each row carries the plate number, vehicle category, fuel type, registration date, date of the last roadworthiness inspection, insurance contract deadline, and mileage recorded at the last service.

Step 2 — Compute deadlines, never rely on manual re-entry

A Code node applies the periodicity rules to every row instead of depending on a manually entered expiry date, which always ends up going stale. The roadworthiness deadline is recomputed from the actual last inspection (last inspection + two years); if no inspection is on file yet, the workflow falls back to the first-inspection-at-four-years rule from the registration date. The diesel van pollution check follows its own annual cycle, computed independently. Insurance and servicing have no general rule — their dates come directly from fields entered when the policy was signed or the last garage visit took place.

Step 3 — Alert with the right intensity, to the right person

A deadline sixty days out deserves a simple heads-up; at seven days, it warrants an alert that can't get lost in a noisy Slack channel. A Switch node routes each deadline to the right level: a grouped notice to the fleet manager at D-60, an individual reminder to the assigned driver at D-30, a doubled alert (driver and fleet manager, by Slack and email) at D-7. The principle is the same as the one detailed in our guide on tracking contract deadlines, applied here to a physical asset instead of a document: what matters is the distance to the deadline, not the nature of what's expiring.

Step 4 — A weekly report instead of scattered alerts

On top of the individual alerts, a second weekly trigger aggregates every deadline due within the next sixty days into a single PDF report, generated via Gotenberg exactly as for an invoice or a quote. This document, sent every Monday to the fleet manager, provides an overview for planning garage slots and negotiating insurance renewals well in advance instead of scrambling in the final week.

Step 5 — Never alert twice for the same deadline

A "last alert sent" field, updated after every notification, stops the workflow from resending the same message on every daily run as long as the deadline hasn't moved to a new tier. It's the same tracking logic described in our guide on n8n error handling: without a state marker, a recurring job always ends up generating noise that people learn to ignore, which defeats the entire point of the alert.

A study by Blows, Ameratunga and colleagues (2003, Does periodic vehicle inspection reduce car crash injury? Evidence from the Auckland Car Crash Injury Study, Australian and New Zealand Journal of Public Health — see the study) compared crashed vehicles to control vehicles on Auckland roads: cars without a valid inspection certificate showed a significantly higher risk of being involved in an injury crash, after adjusting for driver age and profile. An automatic reminder that keeps an inspection from lapsing unnoticed is therefore more than an administrative detail.

Pitfalls to avoid

• Confusing the inspection date with the expiry date. The date to watch is when the certificate expires, not when the last inspection took place — a common mix-up that makes the workflow miss the deadline by several weeks if the calculation starts from the wrong reference point.
• Forgetting the diesel van pollution check. It follows its own annual cycle, independent of the main roadworthiness test from year four onward: a workflow that computes only one deadline per diesel van systematically misses a second one.
• Alerting only the fleet manager. The assigned driver is often the only one who actually knows where the vehicle is and when it's free for a garage appointment; leaving them out of the alert almost always delays booking.

An analysis by Das, Dutta and Geedipally (2019, Applying Bayesian data mining to measure the effect of vehicular defects on crash severity, Journal of Transportation Safety & Security — see the study), based on seven years of crash data from Louisiana, found that worn tires and defective brakes are over-represented among the defects associated with the most severe crashes — two of the exact checks performed during a roadworthiness inspection, which reinforces the case for never letting it lapse over a simple administrative oversight.

Going further

This workflow reuses building blocks already documented separately on this blog — scheduling via Schedule Trigger, PDF report generation, Slack alerts, and delivery tracking — assembled here around a single vehicle registry. A small business can start with just the roadworthiness-inspection piece, which covers most of the regulatory risk, then add insurance and servicing once the registry is in place. For the tracking and audit-trail side, the Compliance & Audit Pack (€149) provides a ready-to-reuse Supabase logging base for this exact use case, and the Complete FlowKit Bundle (€269) pairs it with the Inbox AI and RAG Assistant packs for anyone who also wants to make garage and insurer correspondence searchable in plain language.