Workflows

The way your team runs a day, now runs itself.

Every plant has a rhythm. Monday triage. Tuesday PMs. End-of-month compliance. AssetOS Workflows turn those rhythms into work that kicks off on its own — with the same humans approving the same things, just without the reminding.

Try the builder ↓Browse 24 starter workflows

24starter workflows, ready to run

No-codevisual trigger → action builder

Any eventschedule, status change, or threshold

app.assetos.io / workflows / boiler-room-weekly-pm

Boiler room — weekly PM

WF-0042 · last run Mon 06:00 BST

LIVE

Trigger

Every Monday at 06:00schedule

↗ ran 06:00:02

Condition

If asset group = Boiler Roomand last_PM > 7 days

matched 11

Action

Create WOs from checklist PM-BR-WEEK · assign to on-shift tech

created 11

Action

Post summary to Slack #maint-uk

sent

[06:00:02]✓ run complete· 11 WOs created, 1 Slack notification · 1.4s

Three scenarios · three ready-to-run workflows

Not demoware. These are workflows you can turn on today.

Each example ships ready to run with AssetOS. Tap a tab to see the trigger, conditions, and actions — and the kind of work it takes off your plate.

workflow · WF-0019 · runs Mon 07:15

Every Monday, the week triages itself before anyone gets in.

Instead of an ops manager spending the first hours of every Monday going through weekend tickets, hunting down which ones are urgent, and forwarding the compliance-adjacent ones on, this workflow does the triage on its own — so the team walks in to a dashboard that's already sorted.

Mon 07:15

runs before the shift starts

Auto-route

WOs sorted by priority + owner

Auto-tag

compliance items flagged

app.assetos.io / workflows / monday-triage

Monday morning triage

WF-0019 · 14 runs · 99.2% success

SCHEDULED

Trigger

Every Monday 07:15schedule

cron

For each WO opened since Friday 17:00

Priority = P1/P2branch

12 matched

if yes

Action

Auto-assign to on-shift supervisor

12/12

For each WO tagged compliance

Route to Greg (H&S)

2 matched

Action

Post weekend summary to Slack #westford-ops

sent 07:15:04

[Mon 07:15:04]✓ complete· 12 routed, 2 escalated, 1 Slack · 2.1s

Try it · no signup

Build your own right here.

This is a mock of the real builder. Click nodes from the palette on the left to drop them onto the canvas. Press Run to simulate what a real workflow run looks like.

Paletteclick to add

Triggers

Schedule

cron · one-off · recurring

Record event

WO / asset / cert · create, update, status

Sensor / webhook

IoT reading, integration event

Conditions

Filter / branch

by asset, site, priority, tag

Wait / delay

pause before next step

Human approval

PO, change, attestation

Actions

Create / update WO

from template · assign · schedule

Notify

Slack · Teams · email · SMS

Raise PO / assign part

preferred vendor · auto-draft

API / webhook

Any system with an HTTP endpoint

My workflow0 nodes

Empty canvas

Pick a trigger from the left, then add conditions and actions to build a workflow.

← start with a trigger

Library · 24 starters

You don't start from zero. Pick a template, edit the names.

Every workflow below ships in the product. Clone it, change the asset group or the Slack channel, and you're running in 90 seconds.

Weekly PM batch

Generate WOs from a PM template every Monday at 06:00, assign to on-shift tech.

WF-STARTER-011,240 installs

P1 escalation (8-min)

When a P1 WO isn't acknowledged in 8 minutes, SMS + call the shift manager.

WF-STARTER-02880 installs

Cert renewal · 30d

Raise a WO, draft a PO, and notify the cert owner 30 days before expiry.

WF-STARTER-031,020 installs

PO approval routing

Route POs > £500 to ops director; > £5k to CFO. Approve/reject in Slack.

WF-STARTER-04640 installs

Sensor-triggered WO

When a vibration sensor exceeds threshold, open a diagnostic WO with the last 24h trend attached.

WF-STARTER-05310 installs

Weekend summary digest

Every Monday 07:15, post a triaged summary of weekend tickets to #ops.

WF-STARTER-06720 installs

Stale WO reminder

Ping the assignee after 3 days of no update, CC supervisor after 5.

WF-STARTER-07590 installs

Audit-trail freeze

When a WO is marked complete, snapshot all evidence fields as immutable. CFR-ready.

WF-STARTER-08410 installs

Under the hood

Four building blocks. Infinite combinations.

Every workflow — no matter how complex — is a chain of four things. We kept it simple on purpose.

Triggers

What starts the run — time, event, sensor reading, or a webhook from anywhere.

Schedule (cron, recurring)
WO / asset / cert event
Sensor threshold
Inbound webhook

Conditions

Branch on real data — asset, site, priority. Wait for humans or for time.

Filter / branch
Delay / wait-until
Human approval
Field comparison

Actions

The useful stuff — create WOs, update assets, raise POs, notify humans, call APIs.

Create / update WO
Raise PO / assign parts
Notify Slack / email / SMS
Custom API call

Integrations

40+ native connectors plus Zapier/Make. Your tools stay your tools.

Slack · Teams · Twilio
SAP · NetSuite · Xero
ServiceNow · Jira
Webhooks · OAuth APIs

assetos cli — get started

visitor@assetos.io:~$ assetos start-trial

Bring the Monday morning workflow to your team.

Pick any starter from the library, connect it to your data, and watch your first run go off tomorrow at 06:00. No implementation team required.

Start a free trial →Talk to a maintenance engineer

# No credit card · 30 days free · Cancel in 2 clicks

visitor@assetos.io:~$

From the blog