Skip to content
Ahura OS
Get $10 free
All services
Act

Ahura Workflows

Reliable multi-step work.

Describe a sequence of steps once in plain JSON or YAML and let the platform run it: branching, parallel steps, retries, timeouts, and pauses for human approval.

What it does

  • Declarative definitions

    Write the steps, not the plumbing.

  • Retries and timeouts

    Hard limits stop runaway loops and runaway spend.

  • Human in the loop

    Pause a run until a person or another agent signs off.

  • Full history

    Every run records each step, its input and output, so it can be audited and replayed.

An agent calls it like this

{ "tool": "workflow.run", "name": "weekly-report", "input": { "week": 41 } }

Interactive simulation

Try Ahura Workflows

Press Run to send the call. The dashboard shows what it would use in a partition. Simulated: nothing is actually executed.

ahura mcp · ptn_demo_7f3a

# Start a multi-step run.

→ POST /mcp

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "workflow.run",
    "arguments": {
      "name": "weekly-report",
      "input": {
        "week": 41
      }
    }
  }
}

# See every step recorded.

→ POST /mcp

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "workflow.history",
    "arguments": {
      "run": "wr_aa17"
    }
  }
}

Ready. Press Run.

ptn_demo_7f3a

Partition · N. Virginia · created just now

Simulated
Activeus-eastRetention hold
Run time
0.0s
0 calls
Size
2.3MB
0.00 ACU used

Services in this partition

  • Workflows

    0 calls · 0.00 ACU

Spend by service

Ledger

  • No usage yet.

Why it matters

Where Ahura Workflows beats hand-built orchestration.

A multi-step agent job is easy to write once and hard to make reliable: retries, timeouts, approvals and restarts all need code.

Scripts, queues and cron

  • Write retry, timeout and error handling into every script.
  • Run a scheduler and a queue, and keep them alive.
  • Lose your place when a job dies halfway.
  • Hope a loop does not burn budget while nobody is watching.

Ahura Workflows

  • Declare the steps. Retries, timeouts and branching are properties.
  • Triggers and schedules are built in.
  • Every step is recorded, so a run resumes or replays from any point.
  • Each run has a credit envelope and capped retries, so runaway spend stops itself.
  • Reliability

    Retries with backoff and hard time limits on every step.

  • Control

    Pause for approval from a person or another agent.

  • Audit

    Full step history with inputs, outputs and cost.

  • Spend

    Per-run credit limits and automatic trigger throttling.

Workflows run inside one partition. Very large fan-outs and visual editing are not included.

In depth

What Ahura Workflows can do.

  • Any tool is a step

    Chain Memory, Store, AI, QC, VM or any other tool into a workflow with a short JSON or YAML document.

  • Parallel by default

    Steps with no dependency on each other run side by side. You only declare what must wait.

  • Conditions and branches

    Skip steps, choose between paths, or jump to a handler when something fails.

  • Fan out over lists

    Run the same steps over each item in a list, with a concurrency limit you control.

  • Waits and approvals

    Pause for a timer, until a time, or until a person or another agent approves.

  • Nested workflows

    Call one workflow from another to build bigger processes from reusable parts.

  • Retries and timeouts

    Retry with backoff on the errors you choose. Every step and every workflow has a hard time limit.

  • Sync or async

    Short workflows return their result in the same call. Long ones return a run ID and can run for up to 7 days.

  • Triggers

    Start a workflow from an event on a stream, or on a schedule.

  • Full history and replay

    Every step’s input, output, cost and timing is recorded. Replay a run, or restart from any step using the recorded earlier results.

Every call, listed

13 tools your agent can call. Each one is a standard MCP tool with a typed schema and a price shown in tools/list.

Run

workflow.run
Run a document or a named definition, with an optional spending envelope.
workflow.validate
Check a document and estimate its cost.
workflow.get
Status, output, cost and waiting approvals.
workflow.cancel
Stop a run and refund what was not spent.

Definitions

workflow.define
Save a named, versioned workflow.
workflow.definitions.list / get / delete
Manage saved workflows.

History

workflow.history
Every step with inputs, outputs and cost.
workflow.list
Runs by status, name or time.
workflow.replay
Re-run from any step using recorded results.

Approvals

workflow.approvals
Workflows waiting for sign-off.
workflow.signal
Approve, reject or answer a waiting step.

Triggers

workflow.trigger.create
Start a workflow from an event or a schedule.
workflow.triggers.list / delete / enable
Manage triggers.

Safeguards against runaway spend: every run has a credit envelope, retries are capped, timeouts are mandatory, and a trigger that fires too fast is switched off automatically. If a run runs out of credits, it stops cleanly with a payment request, and you can top up and resume from that step.

Industries using Ahura Workflows