Open website, video, or Designer editing surfaces from Flowgen nodes while keeping the editor artifact connected to its source inputs and downstream outputs. The exact editor and MCP lifecycle depend on the node type.
Where: Flowgen → left rail → Add → Website (Agentic Web / Website Studio) or Video (Video Composition / Video Timeline)
Key ideas
- Shared editor engine: Section, Project, Lite, Document, and Video Composition surfaces open the same f0 editor in a same-origin iframe.
- Graph inputs: Connected HTML, bundle, design system, media, 3D, and per-page section inputs are injected into the embedded document.
- Graph outputs: Save captures editable scene documents plus HTML/CSS, page previews, thumbnails, or rendered video outputs.
Steps
- Create the appropriate editor-backed node.
- Wire generated sections/assets/design system into its typed inputs.
- Run or open the node to launch the embedded f0 editor.
- Edit and click Done/Save so the refreshed outputs propagate downstream.
Match the node to the editing surface
- Unified Section is the current website section/composition node; do not use retired HTML Section or HTML Join/Combine for new work.
- Website Editor nodes assemble visual multi-page websites; Video Editor nodes host the native compositor/timeline.
- Designer is its own document surface and tool API, not the generic f0 iframe/document surface.
- The native Video Editor uses the compositor’s dedicated same-window lifecycle; its MCP readiness is distinct from the embedded f0 document bridge.
Direct canvas editing is surface-specific
- Designer documents use a contextual floating Easy Edit bar for the selected element; the Designer global top bar remains for pages, modes, device/aspect, and project actions.
- The native Website Add menu includes text presets, basic layout shapes, and media; its selection controls and history belong to the original Website document.
- For the full Designer control and Website Add/media workflows, use the linked Easy Edit guides rather than assuming the two editors share identical controls.
MCP uses native source tools, not UI gestures
Discover the exact tool declarations from the original node/editor surface, read its current document and revision, then invoke only supported source operations. UI-only gestures such as local file picking, clipboard insertion, Asset Manager selection, and contextual insertion targeting are not external MCP commands. The Website add-element API also does not carry every visual Add preset’s complete style payload; apply supported style edits separately.
Opening and returning
- Select the node and choose Open editor/Open video editor or the corresponding card/sidebar action.
- Use Detach editor when available to work in a floating window; Full screen editor returns to the expanded editor.
- Close or finish the editor using its own save/resolve controls. Recheck the node’s preview and outputs after returning to Flowgen.
Project promotion
Some editor-backed nodes expose Make this a project. Use that when the document needs a separate dashboard identity and direct project lifecycle; keep it node-backed when it should remain a connected stage in a flow.
Tips
- Before an MCP edit, identify the exact surface and verify its readiness/document identity; do not route Designer or Video Editor calls through the f0 document bridge.
Limitations and important notes
- Only one embedded editor overlay/document automation surface can be open at a time.
- Website Document Editor uses pages; video mode uses a continuous timeline and scenes even though a compatibility socket may still contain page_in_home in its id.
Troubleshooting
The embedded editor changed but Flowgen outputs did not refresh
Use Done/Save—or flowgen_close_node_editor through MCP—and wait for the node to capture the updated document.