How do I use Workflows in Monta Hub?

Learn how to use Workflows in the new Hub to automate repeated tasks.

Updated 5 November 2026

For: Operators using Monta Hub with the Admin or Manager role.

Workflows let you automate fleet-management tasks in Hub. You build a workflow once, then Monta runs it on a manual click, a recurring schedule, a one-off scheduled time, or in response to a charge point event. Use Workflows to reboot charge points in bulk, push Open Charge Point Protocol (OCPP) configuration changes, update price groups across many charging stations at once, or export fleet data on a schedule.

What can I automate with Workflows?

Each workflow has one trigger and a sequence of action steps. The available actions cover charging-station, price-group, and reporting operations:

Reboot Charging Station: send a soft or hard reset to one or more charging stations.
Set Station Configuration: set an OCPP configuration key on selected charging stations, with the option to keep the value across reboots.
Update Price Group: change the kWh price on one or more price groups.
Set Station Price Group: assign a public or roaming price group to charging stations under a team.
Filter Charging Stations: narrow the set of charging stations that downstream steps run against.
Split Charging Stations by Property: partition the upstream charging-station selection into matched and unmatched groups based on a property comparison.
Export Data: run a saved data-export query, save the output to Recent exports, and optionally notify people when it is ready. Available on Reports workflows only.
Wait: pause a run for a set amount of time before continuing to the next step. Available in all workflow types.

Who can use Workflows?

Workflows is available to operator account members with the Admin or Manager role. Other roles do not see Workflows in the sidebar and cannot create, edit, run, or delete a workflow.

How do I open Workflows?

In the sidebar, select Workflows.

Expected result: the Workflows page opens. The header contains a toggle with two tabs: Workflows (the workflows you have saved) and Runs (every execution across all your workflows).

How do I create a workflow?

In the sidebar, select Workflows.
On the Workflows tab, select New workflow in the top right.
On the type picker screen, choose the type that matches what you want to automate, then select Next:
- Charging stations: automations that act on charging stations (reboot, configuration, price group changes).
- Price groups: automations that act on price groups.
- Reports: scheduled data exports saved to your Recent exports.
- Unconstrained: no restrictions; any combination of actions and targets. Use this for complex or multi-domain workflows.
The type is permanent, so you cannot change it after creating the workflow.
In the workflow editor, type a name in the title field at the top. The placeholder reads Untitled Workflow.
Select the trigger node, then choose the trigger type and complete its Configuration fields.
Select the + button under the trigger node, then select the action you want from the popover.
Select the new action node and complete its Target and Configuration tabs.
Add more action nodes if needed, each connected under the previous step.
Select Create Workflow in the top right.

Expected result: the workflow is saved and the editor switches to the saved view. From this point, the primary button changes to Save Changes and is only enabled when you have unsaved changes.

How do I set the trigger?

In the workflow editor, select the trigger node at the top of the canvas. The properties panel opens on the right.
Under Trigger Type, choose one option:

Manual: run this workflow yourself, whenever you need it.
Recurring: runs on a repeating schedule. Enter a cron expression and select a timezone.
Scheduled: runs once at a specific date and time. Select a date, time, and timezone.
Event: runs automatically when a charge point event occurs.

Complete the fields under Configuration. For Recurring and Scheduled triggers, the timezone defaults to your browser timezone.

Expected result: the trigger node updates to show the selected trigger type and its summary. The node shows an incomplete indicator until every required field is filled in.

Event trigger: additional configuration

When you select Event, choose the event that starts the workflow from the dropdown:

Charge point created: fires when a new charge point is added to your operator.
Charge point updated: fires when any change is made to a charge point (except energy-counter updates).
Charge point deleted: fires when a charge point is removed.
Charge point state changed: fires when a charge point or connector reports a new OCPP status or error code. Selecting this event reveals two additional required fields:
- Status: the status that fires the trigger. Choose Any status to match all statuses, or pick one: Available, Preparing, Charging, Paused (EV), Paused (EVSE), Finishing, Unavailable, Error.
- Error code: the OCPP error code that fires the trigger. Choose Any to match all error codes, or pick a specific OCPP 1.6 error code.

Optionally, add a Charge point filter (by charging station, team, site, or model) to limit which charge points fire the workflow. Only events for charge points matching the filter create a run; all others are discarded.

Disabling a workflow stops it from reacting to future events. Enabling it makes it react from that moment on, and past events are not replayed.

How do I add an action?

In the workflow editor, select the + button directly under the trigger node or under any existing action node.
In the Search actions... popover, type to filter or scroll the list.
Select the action you want.

Expected result: the action appears as a new node, connected below the previous step. Select the node to open its properties panel on the right.

How do I configure an action?

Select an action node to open its properties panel. The panel is split into two tabs:

Target: which charging stations, price groups, or team the action applies to.
Configuration: what the action does to them.

Reboot Charging Station

Target tab, Charging Station Target: filter the charging stations to target by team, site, brand, model, or specific charging stations.
Configuration tab, Hard Reset: turn on for a hard reset (immediate restart, terminates active sessions). Leave off for a soft reset (graceful restart).

Set Station Configuration

Target tab, Charging Station Target: filter the charging stations to target.
Configuration tab, Configuration Key: the OCPP key to set, for example HeartbeatInterval.
Configuration tab, Configuration Value: the value to assign, or leave empty to clear it.
Configuration tab, Persist Configuration: when on, Monta re-applies this value each time the charging station reboots, so it survives firmware updates.

Update Price Group

Target tab, Price Groups: select one or more price groups to update.
Configuration tab, New kWh Price: the new price in the price group's currency.

Set Station Price Group

Target tab, Team: select the team that owns the charging stations.
Target tab, Charging Station Target: filter which charging stations under that team to update.
Configuration tab, Public Price Group: the public price group to assign.
Configuration tab, Roaming Price Group: the roaming price group to assign.

Filter Charging Stations

Target tab, Charging Station Target: define the filter using the same team, site, brand, model, and charging-station pickers used elsewhere in Hub. Downstream steps run only against the matching charging stations.

Split Charging Stations by Property

Target tab, Charging Station Target: the upstream charging-station selection to split.
Configuration tab, Property comparison: choose a property, an operator, and a value to partition the selection. Two properties are available:
- State: for example, split into charging stations whose state equals Charging (matched) versus everything else (unmatched).
- 30-day utilisation: choose is at least, is above, is below or is at most, then enter a threshold from 0 to 100%. Utilisation is the share of the charge point's available time it spent busy over the last 30 complete days. The window ends yesterday and refreshes daily. A new condition starts at 20%.
Configuration tab, Keep switched stations: shown for 30-day utilisation only, and on by default. Once a Set Station Price Group step has changed the price group of a matched charging station, later runs skip that station. Saving the workflow with the switch off forgets these stations, so the next run checks them against the condition again.

Downstream steps can target either slice. A charging station with no data for the property goes to neither slice, so no action runs on it. This applies to State too. A charge point has no utilisation when it had no state history or no available time in the 30 days, for example a new charge point.

Export Data

Available on Reports workflows only.

Configure fields: select Configure fields in the properties panel to open the Configure export dialog with the data export query builder. Choose a dataset, columns, and any filters, then select Apply. When the workflow runs, the export is generated and saved to your Recent exports automatically.
Notify when ready: in the Configure export dialog, choose who gets a message when the file is ready: Nobody, Just me, All staff, one staff role (Admins, Managers, Bookkeepers or Supporters), or Lists (the members of the Hub lists you pick under Lists to notify). Then choose Deliver by: Hub inbox, or Hub inbox and email. The message names the export and links to Recent exports on the Data exports page. The message is in English. The file isn't attached to the email. Recipients need access to Data exports in Monta Hub to download the file. Only operator admins can save a workflow that notifies other people.
If the export fails, or isn't ready within 60 minutes, the step fails and no message is sent.

There is no Target tab for Export Data. The export runs at your operator scope, as the workflow owner.

Ready-made schedules: under Start from a template, Monthly export builds an export on the 1st of every month at 06:00, and Weekly export every Monday at 07:00. Pick the dataset and who to notify, then turn the workflow on. Templates start switched off, so nothing runs until you do. See also How do I use Data exports in Hub?

Wait

Configuration tab, Amount: enter a whole number.
Configuration tab, Unit: select Seconds, Minutes, Hours, or Days.

The maximum wait is 30 days. While waiting, the step shows as Waiting in the run timeline. When the time elapses the step completes and the run continues to the next step.

How do I switch price groups based on utilisation?

Use this to move busy charging stations to another price group, for example one with idle fees. Build the workflow once and let a schedule run it.

Create a workflow of the Charging stations type.
Select the trigger node and choose Recurring. Enter a cron expression, for example one that runs on the 1st of each month, and select a timezone.
Select the + button under the trigger node and add Filter Charging Stations. Under Charging Station Target, pick the charging stations to check.
Select the + button under the filter and add Split Charging Stations by Property. Under Charging Station Target, use the charging stations from the filter step.
On the Configuration tab, set Property comparison to 30-day utilisation, pick an operator, and enter the threshold. For example, is at least 20%.
Leave Keep switched stations on if busy charging stations must stay on the new price group when their utilisation later drops.
Select the + button under the Matched branch and add Set Station Price Group. The target is filled in with the matched charging stations.
On the Target tab, select the Team. On the Configuration tab, choose the Public Price Group to assign.
Select Create Workflow, then turn the workflow on with the Active switch.

Expected result: on each run, charging stations at or above the threshold move to the price group you chose. Charging stations below it, and those with no utilisation data, stay as they are.

How do I remove an action?

In the workflow editor, select the action node you want to remove.
In the properties panel on the right, select the Delete action (trash) icon in the top right.

Expected result: the action is removed. Any nodes connected below it stay connected to the action above.

How do I save my workflow?

Select the primary button in the top right of the editor:

On a new workflow it shows Create Workflow.
On a saved workflow it shows Save Changes and is only enabled when you have unsaved changes.

Expected result: the workflow is saved. On a new workflow the editor switches to the saved view, where the Editor and Runs tabs become available.

How do I activate or deactivate a workflow?

Open the workflow.
In the top right of the editor, find the Active / Inactive label next to a switch.
Toggle the switch on to activate the workflow. The label reads Active and the indicator turns green.
Toggle the switch off to pause the workflow. The label reads Inactive and the indicator turns grey.

Expected result: a confirmation toast appears. Inactive workflows are saved but do not run on a schedule or react to events. Their configuration and run history are kept.

How do I run a workflow manually?

Open the workflow.
In the top right of the editor, select the More actions (⋯) menu.
Select Trigger run.

Expected result: the workflow starts immediately and a confirmation toast appears. The Runs tab updates with the new run.

How do I delete a workflow?

Open the workflow.
In the top right of the editor, select the More actions (⋯) menu.
Select Delete workflow and confirm.

Expected result: the workflow and its run history are removed, and you return to the Workflows list.

How do I view run history?

Open the workflow.
Select the Runs tab at the top of the editor.

Expected result: every run for that workflow is listed. Each row shows:

Status: one of Pending, Running, Completed, Completed with errors, Failed, or Cancelled.
Start time and duration.
The error message if the run failed.

Select a run to see step-by-step results for each action in the workflow.

To see runs across all your workflows in one place, select Workflows in the sidebar, then switch the header toggle from Workflows to Runs.

Can I cancel a run?

Yes. Open a run from the Runs tab, then select Cancel run.

Cancellation takes effect at the next step boundary: the step currently executing finishes, then no further steps run. Runs that have already completed, failed, or been cancelled cannot be cancelled.

What happens during a run?

Each step runs and is retried independently. A failure in one step does not roll back earlier steps, and every step is logged on the run.
Configuration changes (Set Station Configuration, Update Price Group, Set Station Price Group) take effect as soon as the step succeeds.
Reboots are sent over OCPP. The charging station may take a few seconds to reconnect after a soft reset and longer after a hard reset.
A workflow that targets many charging stations can take time to finish. Use the Runs tab to follow progress.

FAQ

Can I undo a workflow run?

No. Runs apply changes directly to your charging stations and price groups. Before activating a Recurring or Event workflow, run it once manually with a small target set to confirm the result.

What is Continue on error?

By default, a failed step halts the run and marks it as Failed. When you turn on the Continue on error toggle in the workflow editor, a failing step no longer stops the run. Remaining steps and downstream actions still run, and the run finishes with the status Completed with errors.

Why don't I see Workflows in my Hub?

Workflows is limited to operator account members with the Admin or Manager role. Ask an admin on your operator to grant you the Admin or Manager role if you don't see it in the sidebar.

Which trigger types should I use?

Use Manual when you want full control over when the workflow runs. Use Recurring for repeating maintenance tasks (for example, a nightly OCPP configuration sweep). Use Scheduled for one-off planned changes (for example, a price update at a specific date and time). Use Event to react automatically to platform changes, for example rebooting a charge point when it enters an error state, or applying standard configuration whenever a new charge point is added.

Will a charging station switch back when its utilisation drops?

Not while Keep switched stations is on. The workflow skips a charging station it already moved. This applies only to that workflow and split step. Other workflows, charging station settings and manual edits can still change the price group.

Was this article helpful?