Build a workflow
Chat & Visual Builder
Two ways to author one canonical workflow, with proposals you can inspect before applying.
On this page
One workflow, two interfaces
Chat interprets intent into a proposal. The visual builder exposes supported nodes and their configuration. Both author the canonical Semantic Workflow IR. Moving a card on the canvas changes presentation, not financial semantics.
Inspect and apply the proposed edit before it enters your workflow. The conversational Copilot can ask for missing facts, revise a proposal and describe visible workflow state; ambiguous references require clarification.
Keep the proposal explicit
- State the action, network, asset and amount.
- Answer clarification questions rather than relying on inferred financial values.
- Read the resulting proposal and select Apply proposal.
- Simulate and review the resulting workflow revision.
Composition has boundaries
A list of steps is approved once and executed in order: each step gets its own fresh simulation, Review and wallet signature, and starts only after the previous step reconciled on chain. A step that cannot run (a disabled flow, a network or asset FloFi does not support) stops the workflow before anything new is submitted, and steps already reconciled stay done. The existing Base Sepolia supply → borrow → swap lending composition has a dedicated implementation. Where a deployment does not run workflows, a list is refused with WORKFLOW_RUNS_NOT_ENABLED.
Continue with Simulation and Wallet Authorization for the execution boundary.
These guides summarize the repository’s current contracts. Detailed evidence and engineering history stay in their original records.
docs/STATUS.md docs/builds/BUILD-COPILOT-002-REPORT.md docs/contracts/INVALIDATION_V1.md