Stijn AI
Automation

Workflow Runner

Chains the other agents together and decides what runs next.

Workflow Runner is the orchestrator. You describe a process in plain language, it decides which agents to call in what order, passes data between them, handles failures and returns one consolidated result with a full audit trail.

Describe the process, not the graph

You write what should happen: "when an invoice arrives, extract the fields, check the supplier against our records, and if the total is over five thousand, route it to finance with a summary." The runner works out which agents that needs and in what order.

Branching on real results

Decisions are made against what the previous step actually returned, including confidence scores. A workflow can route low-confidence extractions to a human step while auto-approving the rest, without you writing that logic.

Every step is billed and logged

A workflow run costs the runner fee plus the cost of each agent it invoked. The audit trail shows every step, its inputs, outputs, duration and cost, so an unexpectedly expensive workflow is always explainable rather than mysterious.

Failure handling

Steps retry with backoff. If a step fails permanently, the workflow either halts or takes the fallback branch you defined, and the partial result plus the failure reason are returned. It never pretends a workflow succeeded when part of it did not.

What it can do

  • Plan a multi-agent sequence from a description
  • Branch on previous step output and confidence
  • Pass and reshape data between agents
  • Retry transient failures with backoff
  • Halt or fall back on permanent failure
  • Return a per-step audit trail with costs
  • Insert human approval steps
  • Run steps in parallel where order does not matter

Inputs and outputs

It takes

  • Process description
  • Trigger payload
  • Approval rules (optional)

It returns

{ "result": ... "steps[]": ... "total_cost": ... "duration_ms": ... "failures[]": ... "awaiting_approval": ... }

Fit

Good for

  • Multi-stage document processing
  • Lead handling end to end
  • Anything currently glued together by scripts
  • Processes needing human checkpoints

Not for

  • Sub-second latency requirements
  • Processes needing transactional rollback
  • Replacing a real workflow engine at scale