ProductFlowsA flow is a graph of nodes and connections that orchestrates data, logic, agents, and on-chain actions. You build it from blocks, from code, or with the agent; BluFabric runs it in order against Stellar and the XRP Ledger.Basics

Nodes — steps (read data, branch, act, notify).

Edges — wires between ports.

Library — saved flows you can reopen or reuse as subflows.

Code — a node for logic no block covers. See Code node.

PortsPorts are the connection points on a node. Types must be compatible — the editor blocks bad wires.

Trigger — starts or gates a step.

Data — carries values (addresses, amounts, reports).

Some ports accept an inline value when nothing is wired. Subflows use flexible ports so you can pass almost anything through a reusable block.How a run works

Order nodes so dependencies run first

Collect inputs from upstream wires (or inline values)

Skip a step if its trigger never fires

Run the step and pass outputs downstream

Schedules and watchers keep running until you stop them from the canvas. A deployed flow runs on the server, so it keeps going when the tab is closed.Node categories

Triggers

Manual button, schedule, account watcher, price or balance alerts.

Data

Balances, order books, paths, HTTP, constants, math.

Actions

Payments, offers, trustlines, contracts, multi-op builders.

XRPL

Balances, order books, AMM pools, candles; payments, swaps, AMM deposit and withdraw.

Skills

Research, summary, policy checks, human approval.

Logic & utility

Code, compare, switch, merge, macros, delay, error handling.

Notifications

Toast, email, webhook, browser notification, log.

Code nodeWhen a block isn't enough, write the logic. The Code node runs a JavaScript run(input, context) function over the inputs you declare and returns the outputs you declare. Each port has a type (string, number, boolean, object, array, amount, file), and values are checked against it.

Exact amounts — addAmounts, mulAmount, amountToStroops, and stroopsToAmount do 7-decimal math with no floating-point drift.

Pure compute — no network, storage, DOM, or timers. Inputs are frozen. Use an HTTP Request node upstream when you need outside data.

Limits — 32 KB of source and 1 MB of output. Runs take up to 250 ms in the browser and 2 s on the server. context.log writes to the run log.

Code nodes run in the browser and in deployed flows on the server.Live visualsAny node's output can drive a visualization. Bind a node and port to a live chart, and every run of the flow adds a sample, so the chart redraws as the data changes. This works well for oracle and price polling, pool reserves, balances, and your own Code node results.

Run the flow once, or ask the agent to “chart this output live”.

In the visualization panel, pick the node, port, and numeric field to watch.

Leave a schedule or watcher running. The chart keeps the most recent 120 samples.

The panel stores only numeric fields, never raw node outputs. Clear samples at any time to start fresh.SubflowsSave a flow with input and output nodes, then drop it into a parent flow as a single block. Useful for repeated stages.SafetyResearch is not permission. Reports do not move funds. Spending flows should use policy checks and, when needed, human approval (policyGuard, humanApproval).Agent patterns: Canvas Agent.More in the docs: BluFabric Docs · Quickstart · Canvas Agent · Agent Wallet · BFAB · Security · Zipper (Protocol 27) · Architecture