A flow graph is built from steps: each step does one job, and connections carry its result into the next. The steps you can add fall into a few families — sources that bring data in, transforms that reshape it, commands that change something in Pyron or an outside system, and control steps that shape the path through the flow. To drop a step onto the canvas, wire it up and fill in its settings, see adding and configuring steps; for the editor itself, see building an automation. In the editor you can search the steps by name or by what they do, so the names below are a guide to each step's job rather than an exact label.
Sources
Source steps bring data into the flow. Every automation starts from a trigger; a source step then fetches the data the rest of the steps work on — entries and other things held in Pyron, or a reply from an outside system.
Transforms
Transform steps take data and reshape it without changing anything that is stored. They filter, sort, group, combine and rework the fields of a list so it is ready for the next step — a report, a chart, or a decision.
Filter and order
Group and summarise
Combine lists
Shape fields, text and dates
Commands
Command steps change something — an entry, a directory item, a report, an email, or a message to another system. Unlike source and transform steps, a command has a real effect each time it runs, so it is checked against the permissions the automation runs with.
Entries
Lifecycles
Directory, categories and tabs
Reports, messages and other flows
Control
Control steps decide the shape of the run itself — how many times a group of steps repeats, which branch the flow takes, and what happens when something fails.
Two related steps live in other families. To pick a value based on a condition without changing which steps run, use the choose-a-value step under Transforms. To hand work to another automation, use the run-another-flow and start-another-flow steps under Commands.
AI and code
Two steps hand a job to something outside the fixed catalogue — an AI agent, or code you write yourself — and one works out a value from an expression when no ready-made step fits. In the editor the AI and code steps sit among the command steps, and the expression step sits behind an advanced section; they are grouped here by what they share.
The AI agent step uses the AI provider your organisation has set up — see choosing an AI provider and the AI assistant. The Run code step needs the run-code permission before it will run, which administrators grant through roles and permissions.