Workflows

A workflow in Frayme is a directed graph that turns events into decisions. Nodes are the building blocks; edges define the order and the conditional routing.

What lives at the top of a workflow

Each workflow declares:

Field	Purpose
`id`	Stable identifier.
`name`	Human label shown in the workflow list.
`description`	One-paragraph product summary.
`status`	`draft` · `active` · `archived`
`version`	Monotonic integer — bumped on every save.
`createdBy` / `createdAt` / `updatedAt`	Authorship + edit history.
`parameters`	Top-level tunables shared across nodes (thresholds, callback URLs, feature flags).
`nodes`	The list of nodes (see node reference).
`edges`	Directed connections — source, target, optional `sourceHandle`, optional `label`.

Node taxonomy

Flow control

input, output, split, decisionTable, assignment, condition

Computation

rule, scorecard, code, ai

Integration

dataSource, customApi

Human + outcome

manualReview, action

Variables and templating

Every node writes outputs to the run context. Downstream nodes read them via {{path.to.variable}} interpolation.

{{input.declared_country}}                ← workflow input
{{sumsub_identity.review_answer}}         ← upstream dataSource output
{{ai_risk_synthesis.risk_band}}           ← upstream AI output
{{workflow_run_id}}                       ← system-injected

Full reference in Variables & templating.

Parameters

Top-level parameters are the tunable surface — what compliance can change without touching the graph.

[
  { "name": "max_address_length", "type": "integer", "value": 100 },
  {
    "name": "false_positive_confidence_threshold",
    "type": "integer",
    "value": 85,
  },
  {
    "name": "notification_callback",
    "type": "string",
    "value": "https://api.example.com/webhook",
  },
]

Parameters are referenced like variables ({{params.max_address_length}}) and are version-controlled together with the graph.

Runs and history

Every execution writes to the workflow’s run history with per-node input, output and elapsed time. The Workflow Run Inspector replays this for any run.

Editing safely

Branch the graph

Use the Workflow Editor’s “Duplicate as draft” to fork a workflow into a draft you can edit freely.

Test with fixtures

Pin a known-good input from a recent run. Click “Test workflow” — every node executes against the fixture without writing decisions.

Promote

When the draft passes, flip status: active and the engine cuts over on the next event. The old version stays addressable via version for replay.

Get started

Core concepts

Decisions & Queue

Compliance

What lives at the top of a workflow

Node taxonomy

Flow control

Computation

Integration

Human + outcome

Variables and templating

Parameters

Runs and history

Editing safely

​What lives at the top of a workflow

​Node taxonomy

Flow control

Computation

Integration

Human + outcome

​Variables and templating

​Parameters

​Runs and history

​Editing safely

What lives at the top of a workflow

Node taxonomy

Variables and templating

Parameters

Runs and history

Editing safely