Project node: embedded Website or Video child project

Maintain an existing Project node, understand when its child is created, connect typed inputs, use refresh/apply updates, and route its HTML, CSS, editable bundle, preview image, or pages dataset.

Where: Existing Flowgen canvas → select Project node → Edit; external MCP hosts can create type project on the open Flowgen canvas.

Before you start

This node is a legacy UI path and does not appear in the current Add menu. Use Website Editor or Video Editor for new editor-backed work unless maintaining or migrating an existing Project node.

Key ideas

The child project is created on first Edit: The card can exist before its embedded child project is ready. The first Edit action creates or opens its hidden child. Website mode is projectType simple; Video mode is projectType video. The choice locks after childProjectId exists.
Typed connections populate the child library: Images, video, audio, HTML, PDF, 3D models, HDRI, Design System, CSS, bundle, and motion can be connected through distinct typed sockets. Media is injected into the child library when the editor opens; disconnecting an already-flushed asset does not delete it from the child project.
The active page and whole project have different outputs: html_out and css_out describe the active page; bundle_out is the editable bundle; image_out is the preview screenshot; pages_out is the whole multi-page document as a dataset.
Refresh is separate from opening the editor: When a connected source changes, the node can show stale input/update state. Refresh/Apply updates can refresh an existing injected copy; inspect the source and confirmation before overwriting child content.

Steps

Select the existing Project node and review its title, Website/Video mode, creation status, preview, and visible inputs/outputs.
Choose projectType simple for a website or video for the embedded video editor before the child project is created. Once the child exists, the mode is locked.
Connect each source to the matching typed input: image_in, video_in, audio_in, html_in, pdf_in, model_in, hdri_in, design_system_in, css_in, bundle_in, or motion_in.
Choose Edit to create/open the child editor. Wait for its readiness state, review imported items in the child library, and make the page/document edits there.
Save/close through the editor surface so the node captures its editable document bundle and active-page outputs. Check the preview and status on return.
When an upstream source changes, compare the stale/update notice to the connected source. Use Refresh/Apply updates only for the intended asset; it may replace an already-flushed copy in place.
Wire html_out or css_out to a compatible downstream input for the active page; use bundle_out for another editor that accepts editable content, image_out for a visual preview, and pages_out for a multi-page/list workflow.
For external MCP, create type project only on the intended open Flowgen canvas; inspect node sockets, projectType, readiness, and open editor lifecycle before mutating the child.

Inputs and limits

image_in — Images, up to 64; video_in — Video, up to 32; audio_in — Audio, up to 32.
html_in — HTML / Interactive, up to 32; pdf_in — PDF, up to 16; model_in — 3D Model, up to 16; hdri_in — HDRI, up to 8.
design_system_in — Design System; css_in — CSS, up to 8; bundle_in — editable bundle; motion_in — motion data.
Use the current get_node_sockets result for exact handles/types rather than guessing an input.

Outputs

html_out — active page HTML; css_out — active page CSS; bundle_out — re-editable active-page bundle; image_out — preview screenshot.
pages_out — all captured pages as a typed {columns, rows} dataset; use this when downstream work needs the whole website rather than only the current page.

MCP versus Dashboard project creation

create_node creates a node inside the currently connected Flowgen graph. It does not create a standalone Dashboard project.
To create a separate Website, Video Composition, or Designer project, use Dashboard; then open/connect to the corresponding surface.
The Project node is API-compatible for existing-canvas maintenance but absent from the current visual Add menu.

Tips

Use the newer Website Editor node for a new multi-page website inside a Flowgen graph; use Video Editor for native compositor work.
Treat the child project as its own content container: disconnected flushed assets remain there until explicitly removed.
If the node says creating/error, use its Retry/ready status rather than opening a second child.

Limitations and important notes

The node’s Project/Lite UI is a legacy path and is not listed in the current Add menu.
The project type cannot be changed after child project creation.
Output data depends on a saved/captured document; creating the card alone does not create finished HTML or a rendered video.

Troubleshooting

Edit is still creating or failed.

Read the node status/error text, then use Retry if offered. Check that the project is online and that required source assets are accessible.

A changed source did not update the editor copy.

Inspect the stale-input indicator and use the node’s Refresh/Apply updates action for the intended source. A connection alone does not mean every flushed copy is a live binding.

The node has no output content.

Open and save the child editor first, then check the output handle. Use pages_out for all pages and html_out/css_out for the active page.

Related guides

Was this article helpful?