Dataflow

The wippy/dataflow module provides a workflow orchestration engine based on directed acyclic graphs (DAGs). Workflows are composed of nodes — functions, agents, cycles, and parallel processors — connected by typed data routes. The orchestrator manages execution, state persistence, and recovery.

Setup

Add the module to your project:

wippy add wippy/dataflow
wippy install

Declare the dependency:

version: "1.0"
namespace: app

entries:
  - name: dep.dataflow
    kind: ns.dependency
    component: wippy/dataflow
    version: "*"

The dataflow module depends on wippy/agent, wippy/llm, and wippy/session — these are resolved automatically when you run wippy install. Workflow persistence uses the target_db dependency parameter (default app:db) and runs migrations via wippy/migration.

The module publishes an env.variable entry userspace.dataflow.env:web_host_origin (default https://front.wippy.ai) that downstream flows can read for building public URLs. Override it through the env router or a requirement.

Flow Builder

The flow builder provides a fluent interface for composing workflows. Import it into your entry:

imports:
  flow: userspace.dataflow.flow:flow
local flow = require("flow")

Core API

flow.create()
    :with_title(title)
    :with_metadata(metadata)
    :with_input(data)
    :with_data(data)
    :[operation](config)
    :as(name)
    :to(target, input_key, transform)
    :error_to(target, input_key, transform)
    :when(condition)
    :run()   -- synchronous
    :start() -- asynchronous

flow.template()
    :[operations]...

Linear Pipeline

Nodes chain automatically when no explicit routing is defined. Output of each node flows to the next:

local result, err = flow.create()
    :with_input({ text = "Hello world" })
    :func("app:tokenize"):to("translate", "text")
    :func("app:translate", { args = { target_lang = "fr" } }):as("translate")
    :func("app:format_output")
    :run()

Named Routing

Use :as() to name nodes and :to() to route data between them. Only use :as() when the node needs to be referenced:

local result, err = flow.create()
    :with_input(task)
        :to("router")

    :func("app:router"):as("router")
        :to("context", "routing")
        :to("dev", "routing")

    :agent("app:context_agent"):as("context")
        :to("dev", "gathered_context")

    :agent("app:dev_agent"):as("dev")
        :to("@success")

    :run()

The second parameter to :to() is the discriminator — the input key at the receiving node. When a node receives multiple inputs, they are collected as a table keyed by discriminator.

Workflow Input and Static Data

:with_input() is the single primary input to the workflow. :with_data() creates independent static data sources:

flow.create()
    :with_input(task)
        :to("router")

    :with_data(config):as("cfg")
        :to("dev", "config")
        :to("logger", "config")

    :with_data(branch):as("branch_data")
        :to("checker", "branch")

    :func("app:router"):as("router")
        :to("dev", "task")

    :func("app:dev"):as("dev")
        :to("@success")
        :error_to("@fail")

    :func("app:logger"):as("logger"):to("@success")
    :func("app:checker"):as("checker"):to("@success")

    :run()

Use :with_input() for external data entering the workflow. Use :with_data() for config, constants, and reference data shared across multiple nodes. Static data uses reference optimization — the first route creates actual data, subsequent routes create lightweight references.

Conditional Routing

Use :when() after :to() to add conditions. Conditions evaluate against the node's output using expr syntax:

flow.create()
    :with_input(data)
    :func("app:classify"):as("classify")
        :to("handler_a"):when("output.category == 'a'")
        :to("handler_b"):when("output.category == 'b'")
        :to("fallback")
    :func("app:handler_a"):as("handler_a"):to("@success")
    :func("app:handler_b"):as("handler_b"):to("@success")
    :func("app:fallback"):as("fallback"):to("@success")
    :run()

Conditions can combine with inline transforms for more complex routing:

:func("app:decompose"):as("decompose")
    :to("@success", nil, "{passed: true, feedback: nil}"):when("len(output.items) == 0")
    :to("processor", "items", "output.items")

Conditional expressions support: comparisons (output.score > 0.8), logical operators (output.valid && output.count > 5), array functions (len(output.items) > 0, any(output.errors, {.critical})), string operations (output.status contains 'success'), and optional chaining (output.data?.nested?.value).

Workflow Terminals

Route to @success or @fail to terminate the workflow explicitly. In nested contexts (cycles, parallel), terminals create node outputs instead of workflow outputs:

:func("app:final_step"):to("@success")
:func("app:handler"):error_to("@fail")

Error Routing

Use :error_to() to route node errors to a handler. Errors can be routed as normal inputs to recovery nodes:

:agent("app:gpt_planner", { model = "gpt-5" }):as("gpt_planner")
    :to("consolidator", "gpt_plan")
    :error_to("consolidator", "gpt_plan")

:agent("app:claude_planner", { model = "claude-4-5-sonnet" }):as("claude_planner")
    :to("consolidator", "claude_plan")
    :error_to("consolidator", "claude_plan")

:agent("app:consolidator", {
    inputs = { required = { "gpt_plan", "claude_plan" } }
}):as("consolidator")

This pattern runs both planners in parallel — if one fails, its error becomes the input for the consolidator, which proceeds with whatever results are available.

Input Merging

How nodes receive inputs depends on discriminators and whether args is configured.

Without args — single default input:

:func("source"):to("target")
-- target receives: raw content (unwrapped)

Without args — single named input:

:func("source"):to("target", "task")
-- target receives: { task = content }

Without args — multiple inputs:

:func("source1"):to("target", "data")
:func("source2"):to("target", "config")
-- target receives: { data = content1, config = content2 }

With args — inputs merge into base:

:func("app:api_client", {
    args = { base_url = "https://api.com", timeout = 5000 }
})
-- with :to("api_client", "body") from upstream
-- api_client receives: { base_url = "https://api.com", timeout = 5000, body = content }
Nodes with args cannot receive inputs with the "default" discriminator. Use named discriminators with :to(target, "input_key") instead.

Input Transforms

Transform data before it reaches a node:

-- String transform: single expression
:func("app:step", { input_transform = "input.nested.field" })

-- Table transform: named expressions
:func("app:step", {
    input_transform = {
        task = "inputs.task",
        config = "inputs.settings",
        priority = "inputs.analysis.score > 0.8 ? 'high' : 'normal'"
    }
})

Node input transforms use input (the sole incoming value, or the default input when there are several) and inputs (incoming values by discriminator). Inline route transforms use output (the sending node's result).

Inline Route Transforms

The third parameter to :to() is an inline transform expression:

:func("source"):as("source")
    :to("target", nil, "output.data")
    :to("other", nil, "{passed: true, value: output.x}")
    :to("list", nil, "map(output.items, {.id})")

Node Types

Function Node

Executes a registered function.lua entry:

:func("app:my_function", {
    args = { key = "value" },
    inputs = { required = { "task", "config" } },
    context = { session_id = "abc" },
    input_transform = { task = "inputs.prompt" },
    metadata = { title = "Process Data" }
})
Option Type Description
args table Base arguments merged with node inputs
inputs table Input requirements: { required = {...}, optional = {...} }
context table Execution context passed to function
input_transform string/table Expression to transform inputs
metadata table Node metadata (e.g., { title = "..." })
start_to_close_timeout number/string Per-attempt timeout: milliseconds or a duration string
schedule_to_close_timeout number/string Overall attempt/retry window, retained across restarts
retry_policy table Retry settings; omitted by default for a single attempt

An empty retry_policy allows three attempts, starting with a one-second backoff and multiplier 2. The policy accepts initial_interval, backoff_coefficient, maximum_interval, maximum_attempts and non_retryable_error_types. Unlimited attempts (maximum_attempts = 0) require a positive schedule_to_close_timeout. Cancellation and explicitly non-retryable errors stop retries. Successful calls are not retried for later routing or control failures. Retry-enabled calls receive attempt and a stable idempotency_key in their execution context; a crash after reserving an attempt consumes it. Other node types reject these retry and timeout options.

If the function returns { _control = { commands = [...] } }, the orchestrator spawns a child workflow. This is how nested flows work.

Agent Node

Executes an agent with tool calling and optional structured exit:

:agent("app:content_writer", {
    model = "gpt-5",
    inputs = { required = { "context", "content_plan", "analysis" } },
    arena = {
        prompt = "Write content based on the provided context.",
        max_iterations = 12,
        tool_calling = "any",
        exit_schema = {
            type = "object",
            properties = {
                content = { type = "string" },
                title = { type = "string" }
            },
            required = { "content", "title" }
        }
    },
    show_tool_calls = true,
    metadata = { title = "Content Writer" }
})
Option Type Description
model string Override model
arena.prompt string Additional system prompt; also used as the first user message when conversation input is empty
arena.max_iterations number Max reasoning loops (default: 32)
arena.min_iterations number Min iterations before exit (default: 1)
arena.max_unproductive_steps number Consecutive turns with no call or answer before failure (default: 3)
arena.tool_calling string "auto", "any" (requires exit_schema), "none" (rejects exit_schema)
arena.tools array Tool registry IDs
arena.exit_schema table JSON schema for structured exit
arena.exit_func_id string Function to validate exit output
arena.context table Additional context
active_traits array Active trait overlay, persisted across recovery
active_tools array Active tool overlay, persisted across recovery
inputs table Input requirements
show_tool_calls boolean Include tool calls in output
input_transform string/table Transform inputs
metadata table Node metadata

Dynamic agent selection: Pass an empty string as agent ID and resolve it via input_transform:

:agent("", {
    inputs = { required = { "spec", "task" } },
    input_transform = {
        agent_id = "inputs.spec.agent_id",
        task = "inputs.task"
    },
    arena = {
        prompt = "Process according to spec",
        max_iterations = 25
    }
})

Exit validation: When exit_func_id is set, the function validates the agent's exit output. On validation failure, the agent receives the error as observation and continues (up to max_iterations).

Tool Execution and Recovery

Calls from one model response execute in parallel. The host uses the tool caller's result listener to commit each ordinary tool result as it finishes; recovery runs only calls without committed results. All calls replay together before their results. A completed external effect whose result did not commit can run again, so tools with external writes need idempotency.

Agent and model inputs choose the selection only until the first commit, which stores it in node configuration. _control.config switches commit with their results. Recovery reloads that selection, including trait/tool overlays, before another lifecycle hook, checkpoint or model step. A successful fallback route also persists across iterations and recovery; an agent or model switch clears it.

Stable Conversation

The node folds its conversation inputs into one first user message and stores it once as agent.input. Later inputs and restarts cannot change that message. With no conversation input, a nonblank arena.prompt supplies the first user message on every driver. With neither, the node sends no user message; a positional note can supply content, and without one the node fails before dispatch.

For agent_options.turn_context, the host renders one time note before the first request and stores it as a positional system agent.memory row with key turn_context. It follows the stored input through every iteration, restart and checkpoint. It is not included in the summary.

Recall notes from context_notes become agent.memory rows with metadata.llm_meta.preserve_position and memory_ids, before the action row. Lifecycle messages from activate and before_step must be developer or system. They are stored where sent, with metadata.role, metadata.lifecycle_phase and positional metadata. Other roles fail the node. Restart activation appends a new note; it does not rebuild the earlier one.

Action rows keep thinking_blocks, content_positions when present, and prefix_fingerprint under metadata.llm_meta. Each step sets drop_stale_thinking = true. Checkpoint cuts remove complete earlier rounds, so surviving actions use the default fingerprint comparison; the node supplies no thinking_is_current predicate.

Agent Checkpoints

Checkpoint options merge trait defaults, explicit agent_options.checkpoint, then raw node config.checkpoint. Maps merge recursively and lists replace, including empty lists. enabled = false disables checkpointing; nonpositive thresholds disable automatic scheduling. No checkpoint configuration means no implicit checkpointing. With the fluent builder, configure defaults on the agent or a compaction trait: :agent() does not forward a checkpoint option in this release. Raw node commands can set config.checkpoint directly.

Scheduling compares the latest action's tokens.context_tokens with token_threshold using strict >. It counts the full prompt, including cached input, rather than cumulative usage or only uncached prompt_tokens. A memory.compact = true behavior proposal requests a checkpoint without waiting for the threshold, but cannot override an explicit disable or missing provider.

Checkpoints run after tool results settle and before the next model request. No cut is made while the newest action has an unanswered call on a continuing node. A requested checkpoint waits for that round to close; compaction on a finish round commits with completion. A successful summary replaces all rows through the newest-row cut, calls and results together. Future requests contain the stored input, time note, summary marker and rows after the cut.

Each new summary receives the previous summary plus the rows after its cut, so earlier state rolls forward. The stored input, time note and checkpoint-skip audit rows are excluded. The host passes history rows with data_id, type, content, content_type and metadata, plus dataflow_id, node_id, scenario_id, iteration, prompt_tokens, context_tokens, history_count, checkpoint_before_data_id and effective options to a function fallback. Checkpoint bindings also receive host/agent refs and a since_checkpoint run-context selector. Bindings run before the function fallback; a strict binding failure prevents fallback.

The default summarizer uses model = "class:fast", temperature = 0.2 and max_row_chars = 2000. The per-row clamp does not apply to the earlier summary; the host sets no additional input-size limit. max_memory_chars defaults to 8192 characters and caps stored summary text without splitting a character. Absent max_tokens, the output budget is the smallest of twice that character cap, one eighth of the resolved model's context window, and 16000 tokens. Explicit or derived output budgets are capped at the model's output limit. The prompt asks for at most min(max_memory_chars, floor(max_tokens * 3 / 4)) characters. On a class route, sizing uses only the first model's limits.

Blank summaries and summaries stopped at max_tokens fail without moving the cut. Longer completed summaries are cut at max_memory_chars and marked checkpoint_memory_truncated. Non-strict failures leave an audit observation and are retried when new rows arrive, not repeatedly for the same rows within one process. Host strict = true fails the node; when the node is already completing, a failed requested checkpoint is recorded as a skip instead.

Recovery Limits

  • Recovery does not make external writes exactly once. Lifecycle hooks and durable behavior controls may replay and need stable IDs for idempotency.
  • After recovery of a partially completed tool round, after_execute wrappers see only calls recovery ran. If all results committed but the round's closing commit did not, wrappers run for the whole round. Stored scalar and failure results can lose their original Lua shape (for example, SQLite reads true back as 1).
  • A checkpoint guards the newest open round; older unanswered calls are summarized with their rounds. Bounded get_prompt views can separate calls from results and must not be sent directly to a provider.
  • Older stored runs can restart their cache once on upgrade. A resumed run past its first iteration gets no new time note. Old history with text between a call and its result is not repaired at render time and can fail at the provider.
  • One tool call can return only one _control.delegate, with input_data. Multiple delegates for one call fail the node; an empty list keeps the ordinary result.
  • Checkpoints compact conversation; they do not provide durable memory storage or a hard spending limit. A large summarizer input can still exceed its model.

Agent/trait/tool changes and checkpoints deliberately edit the prefix. Memory clear/delete controls remove only rows added by memory directives; deleting a different existing row fails. A crash before a step commits loses that step and its notes, and recovery repeats from the last committed history.

Cycle Node

Iterates a function or template repeatedly with persistent state:

:cycle({
    func_id = "app:content_cycle",
    max_iterations = 3,
    continue_condition = "not result.approved",
    initial_state = {
        task = task,
        entry_id = entry_id,
        content_prompt = prompt,
        min_score = 8.0,
        feedback_history = {}
    }
})

The cycle function receives on each iteration:

{
    input = <workflow_input>,  -- only on the first iteration (iteration == 1); nil thereafter
    state = <accumulated_state>,
    last_result = <previous_iteration_output>,
    iteration = <current_iteration_number>
}

input carries the workflow input only on the first iteration and is nil thereafter; persist anything needed across iterations into state.

The function controls continuation:

function my_cycle(cycle_context)
    -- stop if approved
    if cycle_context.last_result and cycle_context.last_result.approved then
        return {
            state = cycle_context.state,
            result = cycle_context.last_result,
            continue = false
        }
    end

    -- spawn child workflow for this iteration
    -- task is read from state since cycle_context.input is nil after iteration 1
    local next_iteration, err = flow.create()
        :with_input({ task = cycle_context.state.task })
        :agent("app:worker")
        :agent("app:qa")
        :run()
    if err then return nil, err end
    next_iteration.state = cycle_context.state
    return next_iteration
end

For the child workflow above, continue_condition checks the collected result after the children finish. An explicit continue returned by the function or child result takes precedence. Exceeding max_iterations while continuation is still requested fails the cycle.

Option Type Description
func_id string Iteration function (mutually exclusive with template)
template FlowBuilder Template for each iteration (mutually exclusive with func_id)
max_iterations number Maximum iterations
initial_state table Starting state
continue_condition string Expression: continue while true

Template-based cycle:

:cycle({
    template = flow.template()
        :agent("app:worker")
        :func("app:validator"),
    max_iterations = 5
})

Parallel Node

Map-reduce pattern over arrays:

:parallel({
    inputs = { required = { "specs", "task" } },
    source_array_key = "specs",
    iteration_input_key = "spec",
    passthrough_keys = { "task" },
    batch_size = 10,
    on_error = "continue",
    filter = "successes",
    unwrap = true,
    template = flow.template()
        :agent("app:processor", {
            inputs = { required = { "spec", "task" } },
            input_transform = {
                agent_id = "inputs.spec.agent_id",
                task = "inputs.task"
            },
            arena = {
                prompt = "Process according to spec",
                max_iterations = 25
            }
        })
        :to("@success"),
    metadata = { title = "Process Specs" }
})
Option Type Description
source_array_key string Input key containing the array (required)
template FlowBuilder Template for each item (required, must route to @success)
iteration_input_key string Input key for current item (default: "default")
batch_size number Items per parallel batch (default: 1 = sequential)
scheduling string "batch" (default) or "rolling"; rolling fills free slots and requires on_error = "continue"
on_error string "continue" (default) or "fail_fast"; "collect_errors" is a compatibility alias for "continue"
filter string "all" (default), "successes", "failures"
unwrap boolean Return raw results instead of wrapped metadata (default: false)
passthrough_keys array Input keys forwarded to every iteration

Passthrough keys provide shared context (config, task description) to every iteration without duplicating data in the source array:

:with_data(file_list):as("files"):to("processor", "files")
:with_data("secret"):as("api_key"):to("processor", "api_key")

:parallel({
    inputs = { required = { "files", "api_key" } },
    source_array_key = "files",
    iteration_input_key = "filename",
    passthrough_keys = { "api_key" },
    template = flow.template()
        :func("app:upload", {
            inputs = { required = { "filename", "api_key" } }
        })
        :to("@success")
}):as("processor")

Signal Node

Pauses execution until an external signal arrives. Use for human approvals, external events, or staged workflows:

:signal({
    signal_id = "approval",
    inputs = { required = { "draft" } },
    metadata = { title = "Wait for approval" }
})
Option Type Description
signal_id string Signal name matched against client:signal(). If empty or omitted, a UUID v7 is generated at runtime
inputs table Input requirements
input_transform string/table Transform inputs before the node receives them
metadata table Node metadata

Send the signal from outside the workflow using the client API (see client:signal() below).

Behavior

The node yields with wait_for_signal = true and persists that yield in the workflow state. The orchestrator resumes the node when a matching NODE_SIGNAL commit arrives.

  • The signal is satisfied by any non-nil payload. false, 0, "", and {} all satisfy the yield; only nil keeps it pending.
  • A signal yield blocks COMPLETE_WORKFLOW but does not block other pending nodes — parallel branches continue to execute while one branch waits.
  • Signals can be pre-queued before :start(): if a matching NODE_SIGNAL commit arrives before the signal node reaches the yield, it is delivered the moment the yield is tracked.
  • Only one signal satisfies each yield. If a second signal with the same signal_id arrives before the yield is satisfied, it overwrites the first.
  • When multiple signal yields share the same signal_id, the first matching yield receives the data.
  • Raw NODE_SIGNAL data matches by payload.key, falling back to payload.discriminator.
  • Delivered signal data is passed to the node's output as the signal payload.

Durability and recovery

The signal yield is part of the workflow state, persisted through the same outbox mechanism as every other command. If the orchestrator process is killed while waiting:

  • The pending yield is restored on restart.
  • Signals delivered during the outage are queued and applied when the state reloads.
  • Compound pipelines (func → signal → signal → func) recover step-by-step — each signal can be delivered across a separate restart.

Orphaned signal yields (yields whose parent process exited without completion) are cleaned up by the workflow state's process exit handler.

Pipeline patterns

Signal nodes participate in any topology:

-- Human-in-the-loop approval between two functions
flow.create()
    :func("app:draft")
    :signal({ signal_id = "approve_draft" })
    :func("app:publish")
    :run()

-- Two parallel approvals that must both arrive before release
flow.create()
    :with_input({ doc = "release-notes" })
        :as("trigger")
        :to("legal", "doc")
        :to("finance", "doc")

    :signal({ signal_id = "legal_ok", inputs = { required = { "doc" } } })
        :as("legal")
        :to("gate", "legal")

    :signal({ signal_id = "finance_ok", inputs = { required = { "doc" } } })
        :as("finance")
        :to("gate", "finance")

    :join({ inputs = { required = { "legal", "finance" } } })
        :as("gate")
        :to("release")

    :func("app:release"):as("release"):to("@success")
    :run()

Signal data is exposed as the node output, so downstream nodes receive whatever was passed to client:signal().

Join Node

Collects multiple inputs before proceeding:

:join({
    inputs = { required = { "source1", "source2" } },
    output_mode = "object",
    ignored_keys = { "triggered" }
})
Option Type Description
output_mode string "object" (default) or "array" (arrival order)
ignored_keys array Input keys excluded from output
inputs table Input requirements

Templates

Templates define reusable sub-workflows. Use flow.template() to create, :use() to inline:

local preprocessor = flow.template()
    :func("app:clean")
    :func("app:tokenize")

flow.create()
    :with_input(data)
    :use(preprocessor)
    :func("app:process")
    :run()

Templates inline their operations into the parent flow at compile time.

Nested Workflows

Functions used in cycles and parallel nodes can spawn child workflows by returning flow.create():run():

function my_processor(input)
    return flow.create()
        :with_input(input)
        :func("app:step_a")
        :func("app:step_b")
        :run()
end

When :run() executes inside an existing dataflow context, it returns { _control = { commands = [...] } } instead of executing directly. The orchestrator handles the child workflow through the yield mechanism.

Functions that participate in dataflow composition must return flow.create():run(). Functions returning anything else cannot spawn child workflows.

Synchronous vs Asynchronous

:run() blocks until the workflow completes and returns output:

local result, err = flow.create()
    :with_input({ text = "hello" })
    :func("app:process")
    :run()

:start() returns immediately with a workflow ID:

local dataflow_id, err = flow.create()
    :with_input({ text = "hello" })
    :func("app:process")
    :start()

:start() cannot be used in nested contexts.

Client API

For programmatic workflow management:

imports:
  client: userspace.dataflow:client
local client = require("client")

local c, err = client.new()
Method Description
client.new() Create client (requires security actor)
:create_workflow(commands, options?) Create workflow, returns dataflow_id
:execute(dataflow_id, options?) Run synchronously, returns result
:start(dataflow_id, options?) Run asynchronously, returns dataflow_id
:output(dataflow_id) Fetch workflow outputs
:get_status(dataflow_id) Get current status
:cancel(dataflow_id, timeout?) Gracefully cancel (default: 30s)
:terminate(dataflow_id) Force terminate
:signal(dataflow_id, signal_id, data?) Deliver an external signal to a waiting signal node

Workflow Status

Status Description
template Node is a template instance
pending Waiting for inputs
ready Inputs collected, ready to execute
running Actively executing
waiting Persisted wait; execution can resume after a signal, timer or recovery
paused Yielded, waiting for child workflow
completed Finished successfully
failed Failed
cancelled User cancelled
skipped Conditional branch not taken
terminated Force terminated

Metadata

flow.create()
    :with_title("Document Processing Pipeline")
    :with_metadata({ source = "api", priority = "high" })
    :func("app:process", { metadata = { title = "Process Document" } })
    :run()

Title defaults to "Flow Builder Workflow" if not provided.

Validation Rules

The compiler validates workflows at compile time:

  • All :as(name) names must be unique
  • All :to() and :error_to() targets must reference existing names (except @success, @fail)
  • Graph must be acyclic
  • All nodes must have incoming routes (from another node, workflow input, or static data)
  • :cycle() requires func_id or template (not both)
  • :parallel() requires source_array_key and template
  • At least one path must lead to @success or have auto-output
  • :when() only follows :to() or :error_to() from nodes (not static data)
  • Nodes with args cannot receive inputs with "default" discriminator

Expression Reference

Expressions use the expr module syntax, available in :when() conditions and input_transform values.

Operators: +, -, *, /, %, **, ==, !=, <, <=, >, >=, &&, ||, !, contains, startsWith, endsWith

Array functions: all(), any(), none(), one(), filter(), map(), count(), len(), first(), last()

Math functions: max(), min(), abs(), ceil(), floor(), round(), sqrt(), pow()

String functions: len(), upper(), lower(), trim(), split(), join()

Type functions: type(), int(), float(), string()

Literals: numbers, strings, booleans (true/false), null (nil), arrays ([1, 2, 3]), objects ({key: value})

Ternary: output.age >= 18 ? output.verified : false

Optional chaining: output.data?.nested?.value

Error Handling

Both :run() and :start() follow standard Lua error conventions:

  • Success: data, nil (run) or dataflow_id, nil (start)
  • Failure: nil, error_message

Error categories: compilation errors, client errors, workflow creation errors, execution errors, and workflow failures.

The lower-level client:execute() returns its result alongside a WorkflowFailed error on workflow failure. Optional error_details identify failing nodes; native node errors retain kind, message, retryability and details in cause. Routed errors retain node_error alongside any transformed error.

See Also