New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

Rules card or flow? Choosing where your automation logic lives

The Rules card and flows both act on live data, but they suit different jobs and different people. Here is how I decide where a piece of automation logic belongs.

Automation rules vs flows in Hermetry comes down to who has to understand the logic. Put “when this happens at this place, do that” logic in the Rules card, where the people who run the place can read it and pause it. Use a flow when the work is on the data itself or on another system.

Hermetry 2.0, released on 26 August 2026, shipped rules and flows that act on live data, next to alarms with five severities, acknowledgement and notifications. When the answer to “what should happen?” is “open an alarm”, the docs page on choosing the right tool starts with an alarm rule instead. The Rules card and flows get mixed up, because both act on the same live data.

What is the difference between the Rules card and a flow?

A Rules-card rule is written in sentences and belongs to one place, an asset or a device. A flow is a chain of blocks on a canvas and belongs to the whole organisation.

Rules cardFlow
Written asSentences: When, Only if, ThenBlocks on a canvas
Set perPlace (asset or device)Organisation
Typical jobCommands, settings, notifications, alarms, waitsTransforming, enriching or routing data, calling outside systems
Stopped by Manual modeYesNo

When should automation logic live in the Rules card?

Put it in the Rules card when the people who run the place need to understand it and take it over by hand. The docs’ example for the Rules card reads like an instruction you would give a colleague: “turn the fan on when the room is above 28 °C for five minutes during working hours”.

Test now runs a rule against the values stored now and sends nothing, then says whether the rule would run and what it would do. The Auto / Manual switch lets someone take a place over during maintenance: its rules do nothing, and alarms keep working. I like that the logic sits where the people it affects can read it and pause it.

When do you need a flow instead of a rule?

You need a flow when the work is about the data itself or about other systems. Flows transform, enrich and route messages, compute derived values and call outside systems.

A flow is also the place for logic that the Rules card cannot express in its When, Only if and Then sentences. If the job is getting device data to another system, my post on webhook vs WebSocket vs polling helps you choose how that system should hear about it.

I keep a simple test: if I can say the logic out loud as one sentence about one place, it goes in the Rules card. If the sentence needs the words “every message” or “the other system”, it is a flow.

Does Manual mode stop flows?

No. In Manual and Auto modes, Manual applies to the Rules card only: while a place is in Manual its rules do nothing and no rule sends its devices commands, but flows keep running and alarms keep working.

This decides where equipment logic belongs. If operators expect the automation of a pump or a fan to pause when they switch its place to Manual, that logic has to be a Rules-card rule. A flow keeps running while the place is in Manual, so the switch does not pause it.

Frequently asked questions

How do I check a rule before it acts on real equipment?

Use Test now in the rule editor. It runs the rule against the values stored now and sends nothing. The result shows whether each trigger holds, whether the rule would run, and which actions it would take, so you can fix a wrong limit before the rule moves anything.

Can a Rules-card rule send a command to a device?

Yes. The Then part of a rule runs its actions in order, and they can send commands, change settings, notify people, raise alarms or wait. While the rule’s place is in Manual, no rule sends commands to its devices, so rules do not move equipment while people work on it.

Where should I start if I am not sure which one fits?

I start in the Rules card. A rule is quicker to read, Test now shows what it would do before it acts, and the people who run the place can pause it. When the logic stops fitting into When, Only if and Then sentences, or it has to talk to another system, I build it as a flow instead.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.