Events & data⚓︎
INVERS connects to your automation tool in three ways. Choose based on what you want to automate and which tool you’re using.
| Method | How it works | Best for |
|---|---|---|
| Event stream (RabbitMQ) | INVERS pushes events to your tool the moment they occur | Reactive workflows with n8n — high reliability and volume |
| Webhooks | INVERS forwards selected events to a URL your tool provides | Reactive workflows with Make, Zapier, or Power Automate |
| INVERS REST APIs | Your tool asks INVERS for data or triggers a vehicle action on demand | Scheduled checks, triggered lookups, vehicle actions |
Event stream (RabbitMQ)⚓︎
INVERS sends events to your tool the moment they happen — no polling, no delay. n8n connects to this stream natively via RabbitMQ (a message broker that holds events until your tool reads and acknowledges them).
Use this when:
- You need to react immediately when something happens on a vehicle
- You want the most reliable delivery method
VehicleChange⚓︎
Published when something changes on a vehicle. Each event includes a reasons field that tells you what changed. Common values:
| Reason | What it means |
|---|---|
RENTAL_STATUS_CHANGED |
A rental has started or ended — check vehicle.rental_status.value for IN_RENTAL or NOT_IN_RENTAL |
LIFE_STATUS_CHANGED |
The vehicle has come online or gone offline |
MASTER_DATA_CHANGED |
Vehicle master data (name, license plate, etc.) has been updated |
VehicleChange generates high event volume
A single active vehicle can generate hundreds of VehicleChange events per day. This volume can cause processing delays or missed events in your automation tool. For trip-based triggers, use Trip (v2). For smoke sensor events, use SmokeDetection. To retrieve current vehicle data at a specific moment, use the INVERS REST APIs.
→ See the Events reference for the full list of reasons and the data each event contains.
Trip (v2)⚓︎
Published when a trip starts or ends. Use this when you want to react to completed trips or monitor vehicle usage.
| Event type | What it means |
|---|---|
TripStarted |
A trip has started — contains the vehicle ID and trip start position |
TripEnded |
A trip has ended — contains the vehicle ID, start and end positions, and timestamps |
→ See the Events reference for full field details.
SmokeDetection⚓︎
Published when a vehicle’s smoke sensor reports a detection event.
| Event type | What it means |
|---|---|
SmokeDataReady |
Smoke detection data is available — contains the vehicle ID, timestamp, and detection details |
→ See the Events reference for full field details.
Webhooks⚓︎
INVERS can forward selected events to a URL your automation tool provides. This lets tools like Make, Zapier, and Power Automate trigger workflows based on vehicle events.
Interested in webhooks?
Contact your INVERS representative (your Technical Account Manager or Customer Success Manager), or use the contact form if you don’t have a dedicated contact.
INVERS REST APIs⚓︎
The most common use in automation workflows is requesting current vehicle data from INVERS — on demand, after an event, or as part of a scheduled check.
Use this when:
- You need current vehicle data at a specific moment — for example, to check whether an EV is charging after a rental ends
- You’re building a scheduled check across your fleet
- You need to trigger a vehicle action (lock, unlock) as part of a workflow
Your tool sends a request to the INVERS REST APIs and receives the data or confirmation immediately. See Authentication in the INVERS Developer Docs for how to authenticate these calls.
→ See the API reference and Authentication for full details.