Let Flowgen search Blueprints, Marketplace groups, shared projects, apps, and your own eligible flows for a proven graph shape, then insert and adapt it instead of rebuilding blindly.
Where: Flowgen Agent or MCP → search_reference_flows / insert_reference_flow
Key ideas
- Searchable corpus: Flow structure, wiring, titles, descriptions, tags, and safe prompt ingredients are indexed. Generated media URLs and large outputs are excluded from the retrieval document.
- Entitlements still apply: A gated Marketplace listing can be discovered by metadata, but its graph is not exposed without the user’s entitlement. Insertion uses the authorized retrieval path.
- Adaptation over cloning: A retrieved graph is an editable starting point. Replace its brief, Brain context, models, destinations, and legacy nodes for the current request before running.
Steps
- Describe the desired outcome, inputs, and important constraints in the Flowgen Agent or an MCP host.
- Search reference flows and review each match’s title, source, graph shape, ingredients, and legacy warning.
- Choose a match only when its workflow shape fits; otherwise refine the query or build directly.
- Insert the authorized reference flow, then inspect every node, connection, model, prompt, Brain item, and destination.
- Adapt and test a small representative path before approving a full or expensive run.
Reference sources
- Built-in Blueprints.
- Published Marketplace node groups.
- Published Flowgen apps.
- Public shared projects and individual flows.
- The signed-in user’s own eligible project flows.
Legacy references
Older personal or shared flows can be the best evidence of intent while containing retired node types. A legacy hit is a shape reference only: rebuild the affected step with its current replacement rather than inserting it unchanged.
Limitations and important notes
- A search result is not proof that every referenced model, connection, or asset is available to the current workspace.
- Retrieval does not run the inserted graph automatically.