Workflows

A workflow runs several steps in order. Steps (nodes) can be agents, built-in function nodes such as a database query, a file download or one of your functions, routers that choose the next step, iterators that repeat a step, and nested sub-workflows. A workflow is written in YAML, saved in an app, versioned, and run from the console or the API.

Anatomy

metadata:
  name: ticket-intake
  version: 1.0.0
  description: Classifies a support ticket and routes it

arium:
  agents:                       # agent nodes
    - name: triage
      role: Support triage assistant
      job: Classify the ticket.
      model: { provider: rootflo, model_id: <llm-config-id> }
      parser:
        name: triage
        fields:
          - name: category
            type: enum
            description: What the ticket is about
            values: [billing, bug, other]

  function_nodes:               # deterministic steps
    - name: open_billing_case
      function_name: trigger_message_processor
      input_filter: [triage]
      prefilled_params: { message_processor_id: <function-id> }
    - name: open_bug_report
      function_name: trigger_message_processor
      input_filter: [triage]
      prefilled_params: { message_processor_id: <function-id> }

  routers:                      # choose the next node
    - name: by_category
      type: field_match
      field: category
      routes: { billing: open_billing_case, bug: open_bug_report }
      default: open_bug_report

  workflow:                     # the graph
    start: triage
    edges:
      - from: triage
        to: [open_billing_case, open_bug_report]
        router: by_category
    end: [open_billing_case, open_bug_report]

Section	Holds
`metadata`	Name, version and description, for humans
`arium.agents`	Agent nodes, defined inline or referenced
`arium.function_nodes`	Built-in function nodes: queries, file downloads, configuration reads, your functions, and more
`arium.routers`	Routers that pick the next node
`arium.iterators`	ForEach nodes that repeat a sub-workflow per item
`arium.ariums`	Sub-workflows, nested in this workflow
`arium.workflow`	The graph: `start`, `edges` (each `from` one node `to` a list of nodes, optionally through a `router`) and `end`

Every declared node must be connected by an edge. A node that nothing leads to and that leads nowhere is rejected as an orphan.

Inline and referenced agents

You can define an agent inline, as above, with the same keys as a standalone agent plus input_filter.

Referencing saved agents

You can also reuse an agent saved in the app by writing only its namespace/name:

arium:
  agents:
    - name: support/support-triage      # a saved agent
  workflow:
    start: support/support-triage
    edges:
      - from: support/support-triage
        to: [route_ticket]
    end: [route_ticket]

Edges, start and end use the full reference (support/support-triage). Add @<version> to pin a version (support/support-triage@3); without it the agent’s current version is used.
The agent’s output is stored under the name in the agent’s own YAML (agent.name, here support-triage). Downstream nodes select it with input_filter: [support-triage], not with the reference. See Passing data between nodes.

Referencing is useful when one agent serves several workflows, or when the agent is maintained separately. Inline agents keep the whole workflow in one file.

Creating a workflow

Console
API

Go to Workflows → Create Workflow, enter a Workflow ID and a Namespace, paste the YAML and click Create Workflow. The YAML is checked when you save: invalid structure, orphan nodes or unknown references are rejected, for now with a generic error message (#450).

curl -X POST "$APP/floware/v1/workflow-management/workflows/ticket-intake?namespace=support" \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: text/plain' \
  --data-binary @ticket-intake.yaml

The response contains the workflow’s id.

Running a workflow

In the console, open the workflow. Its YAML is on the left and a chat panel on the right: type the input in Ask anything, add variables with + → Add variables, attach images or documents with +, and send. Turn on JSON output to pretty-print the result.

From the API:

curl -X POST "$APP/floware/v2/workflows/<workflow-id>/inference" \
  -H "Authorization: Bearer $TOKEN" -H 'Content-Type: application/json' \
  -d '{
    "inputs": [{ "role": "user", "content": "My invoice was charged twice" }],
    "variables": { "customer_id": "C-1001" },
    "output_json_enabled": true
  }'

Field	Meaning
`inputs`	The input messages, as for agents. When the first node is a function, send JSON text, for example `"{}"`
`variables`	Values every node can read (`<name>` placeholders in agents, and function inputs)
`output_json_enabled`	Default `false` for workflows: `result` is a string holding the last node’s output. Set `true` to receive it parsed as JSON

Add ?version=<n> to run a specific version instead of the current one, which is useful for trying a new version before making it current. Long workflows can also run in the background; see Running workflows.

Other routes

Action	Request
List	`GET /floware/v1/workflow-management/workflows`
Get one, with its YAML	`GET /floware/v1/workflow-management/workflows/<id>` (optionally `?version=`)
Update	`PUT /floware/v1/workflow-management/workflows/<id>`; see Versions
Delete	`DELETE /floware/v1/workflow-management/workflows/<id>`

Rules worth knowing

One node at a time

Workflows run sequentially; how memory and the output work.

Data between nodes

input_filter, node_outputs and variables.

Sub-workflows

Keep each agent’s context small.

Troubleshooting

Validation errors, orphan nodes, variables and other common surprises.

Getting started

Models and agents

Functions

Data, files and configuration

Run and integrate

Guides

Patterns and troubleshooting

Operations

Workflows

Anatomy

Inline and referenced agents

Referencing saved agents

Creating a workflow

Running a workflow

Other routes

Rules worth knowing

One node at a time

Data between nodes

Sub-workflows

Troubleshooting

​Anatomy

​Inline and referenced agents

​Referencing saved agents

​Creating a workflow

​Running a workflow

​Other routes

​Rules worth knowing

One node at a time

Data between nodes

Sub-workflows

Troubleshooting

Anatomy

Inline and referenced agents

Referencing saved agents

Creating a workflow

Running a workflow

Other routes

Rules worth knowing