A workflow is an automation definition consisting of a trigger and a directed acyclic graph (DAG) of action nodes. Workflows progress through a controlled lifecycle:

Each workflow contains:

• Definition: JSON graph of nodes (trigger + actions + control flow)
• UIMetadata: Canvas layout for the visual editor
• Configuration: Max runs, cooldown period, CU budget

A run is a single execution of a workflow. Runs capture:

• A snapshot of the workflow definition at execution time
• ExecutionState: A map of node progress and results
• TriggerSource: The event that initiated the run

A node is a single step in a workflow. Nodes are connected in a directed graph with sequential and branching execution.

Node Types:

• Trigger: The entry point; defines what starts the workflow
• Action: Executes an operation (built-in, dynamic, or logic)
• Control Flow: if/else, for-each, filter, pluck, wait

Node Structure:

• Children: Nodes that execute after this node completes
• LoopBody: For for-each nodes, the subgraph that runs per item
• Connector: Optional reference to stored credentials
• Props: Configuration parameters for the action

The event source that starts a workflow. B3OS supports 7 trigger categories:

See Triggers for the full reference.

An operation performed by a node. 280+ action types across 21 providers:

• Built-in: Execute within the workflow engine (delay, filter, log, storage, code-transform, db-query)
• Dynamic: Execute via the b3os-actions service (blockchain transactions, DeFi, APIs, messaging)
• Logic: Control flow actions (if, for-each, filter, pluck, wait)

See Actions Overview for details.

A template string that references data from other nodes. Expressions are resolved at runtime before a node executes, with type preservation (numbers stay numbers, not strings).

text
{{trigger.result.amount}}
{{node-abc.result.balance}}
{{$storage.lastPrice}}
{{$org.stores.myStore.key}}

See Expressions for the full syntax.

A team workspace that owns workflows, wallets, connectors, and compute units. All resources are scoped to an organization with full data isolation between tenants.

Organizations support:

• Member management with Owner and Developer roles (21 permissions)
• Shared storage: Key-value stores accessible across workflows
• D1 Database: Dedicated SQLite database per org for structured data
• API keys: Up to 50 scoped keys with SHA-256 hashing and usage tracking

Each workflow run consumes compute units. CU allocation depends on your plan:

• Built-in actions consume minimal CU
• Dynamic actions and AI interactions consume more based on complexity
• Redis-first metering provides sub-millisecond cost accounting

See Pricing for full details.

Reusable encrypted credentials that actions reference at runtime. Connectors keep sensitive data out of workflow definitions:

• Encrypted at rest with AES-256-GCM (authenticated encryption)
• Decrypted only in-memory during action execution
• Never exposed in API responses or run logs
• Organization-scoped, available to all workflows within the org

B3OS includes an AI agent with 17+ specialized tools for natural language workflow generation. The agent can:

• Search the action catalog and resolve full I/O schemas
• Query live token prices, wallet balances, and DeFi positions
• Generate production-ready workflow JSON with schema validation and auto-repair
• Apply incremental JSON patches for modifications (not full regeneration)
• Access organization knowledge via pgvector semantic search

The agent uses a multi-model strategy (GPT via OpenRouter, Claude Haiku for memory, Nvidia Nemotron for cost optimization) with persistent chat memory for long sessions.