/ SONDA · AUTOMATE

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.

13 STEP KINDS TRIGGERS FROM 9 BROKERS AND 4 DEVICE KINDS RUNS STAY ON THIS COMPUTER

The steps

DoCall — any request, gRPC, MCP tool, Kafka, RabbitMQ, MQTT, NATS, AMQP, Redis, FIX, HL7, STOMP, Modbus, OPC UA, HART, DDS. Flow — another flow with its inputs. Script in JavaScript. Set. Note.
ShapeIf, with a yes and a no. For each over a list, a number or words, one at a time or N at once. Join — all, any one, or N of the wires. Wait. Wait until — a call repeated until a condition holds or a timeout.
JudgeCheck — assertions with pass and fail. Show — a table drawn on the canvas as the flow runs. End — success or failure, with a message.
DataReached by name: {{login.body.token}}, {{$input.id}}, {{$item}}. Expressions are interpreted, never executed.
/ THE CANVAS, AS IT RUNS

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.

/ TRIGGERS

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.

Messaging

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.

Industrial

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.

Echo

/ GUARDS AND LIMITS

A flow that listens cannot run away.

What holds a listening flow back, and what bounds every run, however it started.

QueueA queue of 500, then messages are dropped and counted.
BreakerMore than 30 runs in 10 seconds switches the flow off.
ChangesA flow that makes changes listens only with May send changes ticked.
Its own topicA flow that publishes to its own topic will not listen on it.
Per computerListening is a switch on this computer, never on another member's, and never for an app runner.
Stop on errorOn by default — or let the rest of the run go on.
In flightEight calls in flight across branches, by default. A time limit for the whole run.
InputsTyped as text, number, boolean or JSON, with required, default and a note, and a form to run from.
/ THE RUNS

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
# run · Tank 3 high · started by Tank3.Level = 86.4 (msg.value > 80) # kept on this computer · never published to the team login Call ok 84 ms every pump For each done 6 of 6 · 4 at once start pump Call ok × 6 41 ms each all running? If yes 1 ms level < 60 Wait until done try 9 · 44 s end End success "tank 3 drained" values set login.body.token •••••••• # credentials hidden log 08:14:02.117 started · Tank3.Level 86.4 08:14:02.201 login · 200 · 84 ms 08:14:02.244 start pump · p1 p2 p3 p4 at once 08:14:46.390 level 58.7 · success
The canvasUndo and redo, copy, cut, paste, duplicate, Shift-drag to select, Fit, a minimap, zoom with the wheel.
UpstreamUpstream outputs listed with their keys, click to copy.
KeptRuns kept per flow — twenty by default — on this computer only, never published to the team.
One pageA run saved as one HTML page, credentials hidden.
/ LOCKFLARE SONDA

Flows, in the free edition.

Flows, listed →