A complete map of the Flowgen workspace, including the canvas, left rail, Add catalog, node cards, right properties panel, Make and Agent modes, project controls, and embedded editors.
Where: Open a Flowgen project from the dashboard.
Key ideas
- Canvas is the workspace: A canvas contains connected nodes, groups, lists, areas, routes, comments, and run state. A flow is the connected node graph on that canvas.
- Cards and node graph are two views: Card mode reduces wiring chrome for outcome-first work; Node graph shows handles and connections. The project preference changes presentation, not the saved nodes.
- Make and Agent are complementary: Make is the compact command/composer path. Agent exposes planning, conversation context, and assisted construction. The MCP host can instead call the same tools directly without starting the in-app assistant.
- Editors are deliberate surfaces: Eligible nodes open f0 document editors; Designer nodes open Designer. Opening a surface does not flatten the project into an image or detach it from Flowgen.
Steps
- Orient yourself on the canvas: use zoom/fit controls, the minimap when present, and selection to reveal node-specific actions.
- Open the left rail. Use Add to search the complete node catalog; use Assets for project media and the other tabs for their labeled project resources.
- Add a node from the catalog or ask Make/Agent to assemble a small branch. Read the proposed nodes and connections before running paid work.
- Select a node to open the right properties panel. Configure every required input, model, output setting, run behavior, and node-specific option shown on the card or sidebar.
- Connect compatible handles in Node graph view. In Card mode, use the card’s guided inputs and outcome controls without assuming that hidden wires disappeared.
- Use groups, areas, lists, batches, routes, and approval pauses to structure a larger workflow; use comments for collaboration rather than encoding notes into prompts.
- Run one node, a selection, group, batch, list iteration, or the full flow according to the scope you intend. Watch status and inspect the selected result/version.
- Open an eligible embedded editor or Designer surface for direct work, save/close it, then rerun any downstream nodes that now contain stale inputs.
- Use Project settings for Cards/Node graph and Open settings on selection. Use Save status, JSON export, Marketplace/flows, or app publishing according to the intended reuse path.
Left side
- Add/search node catalog
- Project Assets
- Canvas-oriented tabs and shortcuts
- Collapse/expand rail controls
Center and bottom
- Pan/zoom canvas
- Nodes, handles, frames, groups, areas, lists and comments
- Make composer and Agent conversation/mode controls
- Selection and run feedback
Cards and right side
- Card inputs and quick actions
- Properties sidebar with complete node options
- History/version selection
- Expanded inspectors and specialized editors
Top/project controls
- Project identity and save state
- Flows/blueprints and sharing paths
- Project settings
- Run controls and collaboration presence when available
Tips
- Build and test one branch before selecting Run flow.
- Keep automatic settings-on-selection off when the sidebar interrupts spatial canvas work; turn it on during property-heavy setup.
Limitations and important notes
- The Flowgen canvas itself is not the f0 document editor.
- Cards view can hide connection detail; switch to Node graph when diagnosing propagation.
- A completed upstream edit does not automatically prove every downstream result is current.
Troubleshooting
A control described for a node is missing.
Select the node and check both its card and right properties panel. Some controls appear only after an input or mode makes them relevant.
An editor opens blank or refuses the node.
Only nodes that report an editor surface can open one. Use the node reference and its current editor indicator rather than guessing from the name.