Creating an automation

Who can do it: Service provider
Where: Wialon Platform Studio

Automations are the presets where you define the rules and actions that are automatically triggered based on specific conditions.

1. In Wialon Platform Studio, navigate to the Customers section.

2. Select a customer from the list to open their details.

3. Go to the Automations tab.

4. Click Add to open the dropdown menu.

5. Select Add automation.

   

6. In the New automation form, enter a descriptive name for the automation.

7. Set the toggle to Enabled to activate the automation immediately, or Disabled to keep it inactive.

8. Select the Automation type from the dropdown list. The available parameters will change based on your selection.

9. After configuring all necessary parameters for the selected automation type, click Save.

All automation types require a set of unique condition parameters.

Triggers when a device fails to send data to the server for a specified duration. To configure the automation:

1. In the Name field, enter a descriptive name.
2. For the Type, select Connection loss.
3. In the Minimum duration of alarm state field, enter the minimum duration (in seconds).
4. (Optional): Turn on the Geofences toggle and select specific geofences and geofence groups.
5. (Optional): Toggle the Trigger outside geofences option to trigger the automation only when connection loss occurs outside the selected geofences.
6. (Optional): For the Time limitation setting, configure specific days of the week and time ranges.
7. (Optional): In the Maximum triggers per day field, enter the daily limit.
8. In the Devices to monitor section, select specific devices and labels.

The most flexible automation type. You can create complex, multi-layered conditions based on available telemetry data. Configure the following parameters for a Logical expression automation:

1. In the Name field, enter a descriptive name (for example, Engine malfunction).
2. For the Type, select Logical expression.
3. Fill the Expression to trigger alarm: create a logical expression using the section on the right. This section helps you find the necessary parameters and logical operators to join them into an expression. Learn more about the logical expression format.
4. In the Minimum duration of alarm state, enter the minimum duration (in seconds).
5. (Optional): Turn on the Geofences toggle and select specific geofences and geofence groups.
6. (Optional): Toggle the Trigger outside geofences option to trigger the automation only when connection loss occurs outside the selected geofences.
7. (Optional): For the Time limitation setting, configure specific days of the week and time ranges.
8. (Optional): In the Maximum triggers per day field, enter the daily limit.
9. Ensure the Enabled toggle is active.
10. In the Devices to monitor section, select specific devices and labels.

See the examples of setting up automation workflows on the pages:

• Notifying about various device events
• Notifying the user when a device loses connection

A time-based trigger that activates on a recurring schedule. Configure the following parameters for a Schedule automation:

1. In the Expression field, enter a cron expression. Use the Syntax reference on the right to create an expression manually. To use the scheduling examples:

   • Find the necessary period in the Scheduling example description.
   • Click on the example to copy it to clipboard.
   • Paste the example to the Expression field on the left.

2. Ensure the Enabled toggle is active.

Triggers based on the maintenance schedule of a device, used for sending service reminders. Configure the following parameters for a Service due info automation:

1. In the Name field, enter a descriptive name.
2. For the Type, select Service due info.
3. In the Service plans field, select the relevant service plans.
4. Choose one or more conditions:
   • Days left or overdue
   • Mileage left or overdue
   • Engine hours left or overdue
5. Ensure the Enabled toggle is active.
6. In the Devices to monitor section, select specific devices.

Triggers when a new service is created in the Maintenance module. The automation is useful for creating notification chains.

Select the devices to which this automation applies.

Triggers when a new inspection is assigned to a driver or device.

Select the devices to which this automation applies.

Triggers when an assigned inspection passes its deadline without being completed.

Select the devices to which this automation applies.

Triggers when a completed inspection is reviewed and rejected by a manager.

Select the devices to which this automation applies.

Triggers upon completion of a checklist if one or more checklist items were marked as failed.

Select the devices to which this automation applies.

See details on the Configuring automatic task creation for a failed checklist page.

The Expression to trigger alarm field in the Logical expression automation requires a mathematical or logical expression that uses telemetry parameters. Browse the right part of the window to find the necessary parameters and operators. Learn more about logical expressions in the flespi documentation.

For example, if your device’s GPS reports a speed greater than 10 km/h and its ignition status is off, the logical expression is: position.speed > 10 && ignition == false

You can combine multiple conditions using logical operators:

• + (sum): Adds values.
• - (difference): Subtracts values.
• * (multiply): Multiplies values.
• / (divide): Divides values.

• && (logical AND): Both conditions must be true.
• || (logical OR): At least one condition must be true.
• ! (NOT): Negates the condition.

• == (equal): Checks if two values are the same.
• != (not equal): Checks if two values are different (inverse of ==).

• > (greater than)
• < (less than)
• >= (greater than or equals)
• <= (less than or equals)
• () (parentheses) define the order of logical operations

• engine.oil_pressure < 10 (if oil pressure drops below 10 units)
• engine.temperature > 100 && vehicle.speed > 0 (if engine overheats while moving)
• battery.voltage < 11.5 || engine.blocked.status == true (if battery low or engine is blocked)

See more examples of setting up automation workflows on the pages:

• Notifying about various device events
• Notifying the user when a device loses connection