Tip

This feature might be limited based on your subscription level. Please check your subscription for more details.

Alerts

With alerts you can get notified, when a vehicle enters or leaves a geo-zone. For example: “Tell the dispatchers when a city van arrives at a customer warehouse.”

An alert can show a notification in the system, on your mobile app, send an email, or send the data to another system via a webhook.

Click Alerts in the top menu to see your alerts.

Your alert list

The list shows each alert’s name, whether it fires on entering or leaving, its severity, and whether it sends emails and notifications. Click an alert to change it. Click the bin to delete it.

The alert list with four alerts

Create an alert

Click + above the alert list. You fill in the page from left to right.

1. Name and settings

  • Name – for example “Arrived at customer”.

  • Severity – Info, Success, Warning or Critical. It sets the icon and color of the notification.

  • Cooldown period (minutes) – stops repeated alerts while a vehicle drives along the edge of a zone. Enter 0 to get an alert every time.

  • Time zone – the time zone of the times in the messages.

The empty Create alert page with Name, Severity, Cooldown and Time zone

2. Vehicles – which vehicles to watch

Tick vehicles or whole groups. Click Watch all vehicles instead to watch every vehicle, including vehicles that you add later.

The City delivery group ticked in the Vehicles column

3. Geo-zones – where the alert applies

Tick geo-zones or whole groups. Click Apply to any geo-zone instead to use every geo-zone, including geo-zones that you draw later.

The Customers / Kaunas group ticked in the Geo-zones column

4. Actions – when the alert fires and what happens

  1. Under Trigger, choose when the alert fires: when vehicles Enter, Leave, or Enter & Leave.

  2. Click Add action and choose what happens:

    • In-app notification – a notification under the bell for the employees you choose

    • Email – an email to the employees you choose

    • Webhook – sends the alert data to another system (see below)

    The Add action menu with In-app notification, Email and Webhook
  3. Write the message and tick who gets it. Click the { } button in the message to insert details such as the vehicle name.

    The Notify in app action with the message and the list of employees

5. Check and save

The bar at the bottom says in plain words what the alert does, for example: “Alerts will be sent via notifications (all employees) when any vehicle in 1 groups enters any geo-zone in 1 groups”. If it is right, click Save.

When the alert fires, the employees in its Email action get an email like this:

The alert email: Sprinter 01 entered Mega retail park, with the time and the alert Arrived at customer

Details you can put in a message

Placeholder

What it becomes

${vehicle.name}

The vehicle’s name

${vehicle.group}

The vehicle’s group

${vehicle.notes1}

The vehicle’s notes

${tracker.imei}

The tracker’s IMEI

${geoZone.name}

The geo-zone’s name

${geoZone.group}

The geo-zone’s group

${alert.name}

The alert’s name

${alert.event}

Whether the vehicle entered or left

${alert.time}

When it happened

${alert.timeZone}

The alert’s time zone

Send alerts to another system (webhook)

A webhook sends the alert to your own software, for example a dispatch system, as soon as it fires.

Note

Webhooks are available on higher plans.

  1. In Actions, click Add action and choose Webhook.

  2. In Webhook URL, enter the address that your IT team gives you.

  3. Optional: click Add metadata to send extra values with every alert, for example the depot or route.

  4. Click Send test to send an example and check that your system receives it.

  5. Click Save.

A webhook action with a URL and two metadata values

Fliteca sends a POST request with this JSON body:

{
  "idempotencyKey": "3f6b2a0e-7c1d-4a8e-9b2f-1c5d7e9a0b34",
  "alertId": "a1d4c2b0-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "alertName": "Arrived at customer",
  "alertSeverity": "info",
  "vehicleId": "7e2c9b1a-3d4f-4e5a-8b6c-9d0e1f2a3b4c",
  "vehicleName": "Sprinter 01",
  "geoZoneId": "c0b1a2d3-e4f5-4a6b-8c7d-9e0f1a2b3c4d",
  "geoZoneName": "Amberfield Foods",
  "isEntrance": true,
  "timeStamp": "2026-11-01T09:42:17Z",
  "longitude": 23.979735,
  "latitude": 54.916214,
  "metadata": {
    "depot": "Kaunas",
    "route": "City delivery"
  }
}
  • isEntrance is true when the vehicle enters the geo-zone and false when it leaves.

  • idempotencyKey is unique per alert event - retried publishing of an alert event retains the same idempotencyKey value. Use it to skip duplicates.

  • You can use the placeholders from the table above in the URL and in metadata values.

To see every webhook that Fliteca sent, and to resend failed ones, see Webhooks.