Skip to content
Nexus

Flows and governed actions

Deterministic steps, governed actions, one runtime.

A Flow owns the business sequence from capture to handoff. Actions cross a typed boundary, and one configured Agent can take a step inside the same runtime that runs the Flow.

Create an account

Runs today

  1. Deterministic steps

    Capture structured input, branch on conditions, send purpose-written messages, and hand off, in an order you authored.

  2. Governed actions

    Actions cross a typed boundary with declared inputs, outputs, and receipts, so a Flow acts only in the ways you defined.

  3. One Agent step

    A configured Agent can take one step inside a Flow, on the same runtime as the Flow itself.

  4. Publication and versioning

    Draft, publish, and version a Flow so customers see only what you released.

The Telecom story walks two customer tasks through capture, governed actions, and handoff.