Workflow lets you automate fleet operations by connecting a trigger, decision or processing steps, and actions into a visual flow. A workflow can react to vehicle telemetry or run on a schedule, evaluate conditions, generate reports, send notifications, call external systems, register events, and perform other supported actions without building the complete process manually each time.
Last updated August 20, 2026
Workflow is the automation workspace in Open VTS.
It allows you to define a process once and let Open VTS follow that process whenever the required event occurs.

Instead of repeatedly checking vehicle data and performing the same action manually, you can build a visual flow that tells Open VTS:
When this happens → check or process this → then do this.
For example:
Incoming Vehicle Data → IF a condition is true → Send Notification
or:
Schedule → Generate Report → Send Email
A workflow is built by placing individual nodes on a visual canvas and connecting them in the order they should run.

A good workflow starts before you open the editor.
You should first understand what should start the workflow, what information it needs, and what should happen at the end.
Start with one clear question:
What do I want Open VTS to do automatically?
For example:
Having one clear outcome makes the workflow easier to build, test, and maintain.
Every published workflow requires one enabled trigger.
The current Workflow builder provides two primary trigger types:
Use Incoming Data when the workflow should react to vehicle telemetry.
This is appropriate for workflows based on information such as:
You can select the vehicles that the workflow should monitor.
Only vehicles that are authorized and available to your User account can be selected.
Use Schedule when the workflow should run at a particular time or interval rather than waiting for vehicle data.
For example:
A timezone is also configured so the schedule runs according to the intended operating time.
Important: A workflow must have exactly one enabled trigger before it can be published.
A workflow can only act on information that is actually available.
For an Incoming Data workflow, make sure the required vehicles are assigned to your User account and that they are sending the telemetry needed by the workflow.
For example, if your condition depends on a sensor value, that value must be available in the incoming vehicle data.
Incoming Data workflows can work with information such as the current vehicle data, previous data, vehicle information, IMEI, and other available normalized telemetry fields.
Using real test data before publishing helps confirm that the field you want to use actually exists.
Some workflow actions depend on another Open VTS service being configured.
You only need the integrations required by the nodes you plan to use.
| Workflow Action | What May Be Required |
|---|---|
| Send Email | Email/SMTP configuration |
| Send Notification | Firebase/FCM configuration for Web or Mobile Push |
| Send WhatsApp | Configured WhatsApp integration |
| HTTP Request | Reachable HTTPS API |
| Code | Workflow isolated code runner enabled on the server |
| Generate Report | Required vehicles and report data |
| Send Device Command | Supported and authorized vehicle/device |
| Register Event | Current authorized vehicle context |
If a required service is not configured, the workflow may fail validation, publishing, or execution for that action.
The Workflow canvas is designed for a larger workspace.
When the editor window is narrower than approximately 900 px, Open VTS changes the canvas to read-only mode.
You can still inspect the workflow and execution information, but editing nodes and connections requires a wider desktop-sized window.
A workflow becomes much easier to understand when you think of it as three layers.
The trigger answers:
When should this workflow start?
Examples:
Every workflow begins here.
These nodes decide what should happen to the data before an action is performed.
Available logic nodes include:
For example:
Incoming Data → IF temperature is above a threshold
The IF node can send the workflow down different paths depending on whether the condition is True or False.
An action answers:
What should Open VTS do?
Current action nodes include:
A workflow may contain more than one action when required.
Most workflows can be understood using this simple structure:
For example:
Incoming Data↓IF a condition matches↓Send Notification
A more advanced workflow could be:
Incoming Data↓IF condition↓Register Event↓Wait↓Send Notification
Or a scheduled workflow:
Schedule↓Generate Report↓Send Email
You can build only the steps that your process actually requires.
From the User Home page, open Workflow.
The Workflow page contains three sections:
Shows workflows created under your User account.
Provides predefined starting structures that can help you build common workflows faster.
Shows workflow runs and lets you inspect what happened during previous executions.
Select Create workflow.

The Create workflow window asks for:

Give the workflow a name that describes what it does.
Good names are specific and easy to recognize.
For example:
Daily Fleet Report
or:
Vehicle Temperature Alert
Use Description to explain the purpose of the workflow.
This becomes especially useful when several workflows exist.
You can:
A template gives you an existing node structure that you can modify instead of starting from an empty canvas.
Select Create and edit to open the Workflow editor.
Creating a workflow only creates a draft. It does not make the workflow active.
Every workflow needs a starting point.
From the node panel, add either:

Use this when the workflow should respond to vehicle telemetry.
Configure which authorized vehicles the workflow should monitor.
Incoming Data can also be configured to focus on particular changed fields or usable GPS data when required.
Use this when the workflow should run according to time.
Configure the schedule rule and timezone.
[Add Screenshot: Workflow editor showing the node palette, canvas, and a trigger node]
Use the node panel to add the next steps.
You can search the node list or select the node you need.
For example, to create a simple condition-based alert:
For a scheduled report:
Do not add nodes simply because they are available. Every node should have a clear purpose in the workflow.

Connect the output of one node to the input of the next node.
The connection determines the order in which the workflow runs.
For example:
Incoming Data → IF → Send Notification
An IF node provides separate paths such as:
Connect the action to the path where you want it to run.
A published workflow cannot contain enabled nodes that are disconnected from the trigger.
Select a node to configure it.
Each node has settings appropriate to its function.
For example:
Choose the vehicles and data scope.
Choose:
Choose when the workflow should run and which timezone should be used.
Configure the notification destination, title, message, and severity.
Choose the report type, vehicles, time period, and required report-specific filters.
The Workflow editor also supports using information produced by earlier nodes in later nodes.
This means later steps can use the actual data that caused the workflow to run instead of requiring every value to be entered manually.
Testing is one of the most important parts of building a workflow.
For an Incoming Data workflow, use the available test-listening functionality to capture a real sample from an authorized vehicle.
This lets you see the structure of the incoming information before mapping it into an IF, Code, HTTP Request, notification, or another node.
Using an actual sample helps prevent incorrect field paths and assumptions about the data.
Use Test before publishing.
Testing allows you to check the workflow path and inspect how nodes behave without immediately relying on the workflow in normal operation.
Test mode is designed to suppress external delivery while you verify the workflow.
You can also execute supported individual steps while configuring them.
A useful testing sequence is:
Do not publish simply because the workflow looks correct visually.
Verify the data path first.
Select Validate when the workflow structure is ready.
Validation checks whether the workflow meets the rules required for publishing.
Open VTS verifies items including:
Any blocking validation errors must be corrected before the workflow can be published.
When validation succeeds, select Publish.

The Publish checklist provides a final review of the workflow.
Publishing creates a server version of the workflow and makes the valid workflow Active.
A published workflow can then respond to its configured trigger while the Workflow runtime is available on the Open VTS deployment.
Once active, qualifying telemetry from the selected vehicles can start the workflow.
Once active, the scheduler starts the workflow according to the configured schedule.
Publishing should therefore be treated as the point where your automation moves from design into operational use.
Open the Executions section to review previous workflow runs.
Execution history helps you understand:
Use execution history when troubleshooting a workflow instead of changing nodes without first checking what actually happened.
A workflow can be managed from the Workflows list.
Depending on its current state, available actions include:
Use Pause when you want to temporarily stop an active workflow without deleting it.
Use Activate to resume a previously published workflow.
A workflow must have a published version before it can be activated.
Use Duplicate when you want to create a new workflow based on an existing one.
This can be useful when the logic is similar but the vehicles, conditions, or actions are different.
Use Archive for workflows you no longer want in normal active use but do not want to delete.
Use Delete only when the workflow should be permanently removed.
Suppose you want Open VTS to notify you when a particular telemetry condition occurs.
The workflow could be:
Select the vehicles that should be monitored.
↓
Choose the telemetry field and define the condition.
↓
Create the message that should be sent when the condition is true.
Then:
This same pattern can be expanded gradually when your process requires additional logic or actions.
For your first workflows, keep them simple.
A strong first workflow usually has:
1 Trigger → 1 Condition → 1 Action
Once that works correctly, add more steps only when they solve a real requirement.
This makes the workflow easier to:
The goal of Workflow is not to build the largest possible automation.
The goal is to make a repeatable fleet process clear, dependable, and automatic.
A User can only build workflow operations around resources authorized for that User account.
For vehicle-based workflows, selectable vehicles must be active, available to the User, and not blocked by their licence state.
Creating a workflow does not activate it. The workflow must first be configured, tested, validated, and published.
A valid published workflow requires exactly one enabled Incoming Data or Schedule trigger and at least one reachable action.
External actions may require their corresponding Open VTS integration to be configured before they can work.
The Code node cannot be published unless the isolated Workflow code runner is enabled on the Open VTS server.
Publishing creates an immutable workflow version. Later edits are made to the workflow draft and require publishing again when you want the new version to become operational.
Use Executions to understand workflow behaviour and failures rather than relying only on the visual canvas.
The Workflow editor requires a desktop-sized window for safe editing. On smaller windows, the canvas becomes read-only.