Steps on a canvas. Started by whatever happens.
A flow is a canvas of steps inside a project. A Call step is any request, gRPC method, MCP tool, broker message or device tag the project holds; If, For each, Join and Wait until shape the run. It starts from a form, from a message on Kafka or MQTT, from a tank level past a line, or from an Echo endpoint acting as a webhook.
The steps
A step for every call. Wires for everything else.
A Call step is any request, gRPC method, MCP tool, broker message or device tag the project holds. If, For each, Join and Wait until shape the run around them: several wires from one port run at the same time, and a fail port handles a failure where it is wired. A field reaches an earlier step's answer by name — {{login.body.token}}, {{$item}} — and expressions are interpreted, never executed.
While it runs, every step says what it is doing on the canvas: its status, its words, its milliseconds. Beside it, a tank past its line: a login, six pumps started four at once, and a wait until the level comes down.
A message, a reading, a webhook.
A flow listens on a messenger's topic with wildcards and a filter expression, runs N at once, and its outcome settles the message it started from.
From a broker — and the run settles the message.
MQTT, Kafka, RabbitMQ, NATS, Redis, STOMP, AMQP 1.0, FIX and HL7. On failure, reject or requeue. A RabbitMQ reply-to is answered. An HL7 message gets its AA, AE or AR from the flow — AE after 25 seconds without an answer.
From a device, when a reading crosses a line.
A Modbus, OPC UA, HART or DDS tag: each change past the deadband is a message, and msg.value > 80 starts a run.
From a request, as a local webhook.
An Echo endpoint answered by a flow: the caller waits — up to ten minutes — and gets what the flow ends with. A local webhook with no server.
A flow that listens cannot run away.
What holds a listening flow back, and what bounds every run, however it started.
See it run. Keep what it did. Publish none of it.
Live status, words and milliseconds per step, on the canvas, as it happens. When it ends, the run keeps each step's outputs, the log and the values set. Beside it, the run drawn above, as its record reads once it ended.
Themis lists your flows and runs one when asked, reading its summary with credentials scrubbed.
Themis AI