A narrow, honest automation engine — not a fake AI agent.
A Workflow is a short sequence of steps you run manually against your own Nodes: inspect a capability fact, test an Integration, check a condition, record a notification, or wait. It's proud of what it is — a deterministic, inspectable operator tool — and doesn't claim to be an autonomous agent, a scheduler, or an n8n replacement.
The Step Library
Step Library — the 5 real step kinds
A sequence in order
Runs manually, on your own Nodes, one step at a time — a deterministic, inspectable operator tool, not a background scheduler or an autonomous agent.
Five step kinds, one honestly not executable
Inspect Node reads a capability fact off one of your Nodes. Invoke Integration tests the connection to a published Integration. Condition checks a capability fact against a value you choose. Notify records a simulated message — no real notification channel exists yet, and the step says so. Wait pauses for a number of minutes but isn't itself executable; it's a placeholder step kind, not a scheduler.
Manual, deterministic, inspectable
A Workflow runs when you run it — there's no background cron, no autonomous trigger deciding when to act on your Nodes. Every step's outcome is visible before you move to the next one. That's a narrower tool than a full automation platform on purpose: every action is something you chose to run, against Nodes you actually have, with a result you can see.
What it isn't
This is not an AI agent making decisions on your behalf, not a scheduled background job runner, and not an n8n-style general automation replacement. It's an operator tool for a narrow, real job: sequencing checks and Integration calls against your own Network, manually, one run at a time.
Capabilities
What this is backed by: lib/workflows/step-kind-catalog.ts's STEP_KIND_CATALOG — the single source both the builder and this page read from.
Related Platform features