Pick a ready-made graph, reuse a saved flow, and keep the product terminology clear: flows are connected nodes; canvases are saved boards.
Where: Flowgen → Flows / Blueprints / canvas switcher
Key ideas
- Blueprints: Curated connected graphs span Builders, Research, Marketing & UGC, Product, Video & Motion, Web & Brand, Audio, and Imaging.
- Flows store: Reusable flow assets and Marketplace node groups insert as editable starting graphs rather than opaque one-click jobs.
- Naming: A flow is the connected node graph. A canvas is one saved board in the project; a project can contain several canvases.
Steps
- Open Blueprints or Flows and filter to the outcome you need.
- Read the description/how-to and insert the graph.
- Replace its briefs, references, records, and models for the current job.
- Save/rename the current canvas or create another canvas when you need a separate board.
- For website content, search the blueprint gallery for Pages from Content or Posts from Rows and inspect the connected graph before running it.
- For Posts from Rows, open the Website Editor, create or select the destination post type, then drag the mapper output to that post type’s newly available input socket.
Blueprint categories
- Builders.
- Research.
- Marketing & UGC.
- Product.
- Video & Motion.
- Web & Brand.
- Audio.
- Imaging.
Insert, then own the graph
Blueprints and Marketplace flows insert editable nodes and connections. Replace sample briefs, references, Brain records, models, and destinations; inspect cost/approvals before a full run.
Canvas management
Use multiple canvases when boards represent genuinely separate workflows or experiments. Rename them by outcome. Use a group/subflow when the work belongs in one larger connected process.
Website Editor outside-in blueprints
- Pages from Content wires an Items/List table into Website Editor.pages_in. Rows can provide Name/Title/Page plus Content/Markdown for design-system-aware conversion or Html for verbatim markup.
- Posts from Rows uses a Field Mapper to shape rows, then applies the mapped dataset to one post type. Create/select that real post type in the Website Editor first; its post_in_<collectionId> socket appears from the document schema and must be connected explicitly.
- The blueprints apply the whole table once. They are not loops and should not be wrapped in a Group Repeater or List Iterator.
- Stable source keys let reruns address the same destination records; review apply results and conflicts rather than assuming every row was accepted.