Core & Utility

The utility operators — glue verbs, format helpers, and escape hatches that don’t belong to any external service.

Flow & process control

Operator	invoke:	What it does
Flow	flow.invoke	Call another flow as a typed verb — see Composing Flows.
Shell	shell.*	Run a shell command; stdout/stderr captured to the invocation log.
No Operation	noop.*	A do-nothing step — useful as a placeholder or branch terminator.

Data shaping & build

Operator	invoke:	What it does
Combine	combine.*	Merge multiple payload sources into one structure.
Build	build.*	Run a build/packaging step (e.g. compile or bundle artifacts).
Binary Decoder	binary-decoder.*	Decode binary input into structured fields.

Secrets & credentials

Operator	invoke:	What it does
KeePass	keepass.*	Read entries from a KeePass database — an alternative credential source.

Custom script operators

When the catalog doesn’t cover a one-off integration, a flow can call a custom Python or PowerShell script as if it were an operator action. Each script lives under scripts/{name}/ with:

• its own definition file,
• a language declaration,
• an entry point.

The platform supplies a typed wrapper, captures stdout/stderr to the invocation log, and enforces the same rollback and retry semantics as a built-in operator. Use this for proprietary logic that doesn’t justify a full operator pack.

- $report:
    invoke: my-custom-script.run
    with:
      InputData: "${rows.rows}"

Script operators run with the same security posture as the rest of the platform — see the script-operator security assessment in the project docs. For anything you’ll reuse across many flows, prefer implementing a proper operator over a script.

The format converter star

Beyond operators, the platform ships a built-in converter library that reads and writes csv, json, xml, yaml, excel, word, xslt, and md-to-pdf. These power the data-shaping that operators and transformers rely on — e.g. reading an Excel file into rows or rendering a Markdown report to PDF.