Build with Blueprint.
Invoke a published Blueprint as a collapsed subworkflow.
Best for
Invoke a published Blueprint as a collapsed subworkflow. Use the playground to set up a single step, then open a workflow when you want to connect more tools.
Inputs explained
NEVER emit this node yourself, in buildWorkflow or addNode. Its ports and its config.blueprintId are computed per instance by the server, and one you create arrives with zero handles, can be wired to nothing, and fails at run time on a missing config.blueprintId. There is exactly ONE exception and it is not an emit: the attachContextBlueprint tool, which mints and persists a CONTEXT blueprint node server-side (zero ports by design, never runs, never bills). For a RUNNABLE blueprint there is no tool at all. tell the user to open it on /blueprints and press "Add to workflow", which is the only caller of POST /api/workflows/[id]/add-blueprint.
Tips before you run
Start with the default settings and change one input at a time. Keep the result you like on your board so the next step can use it.
If you add a reference file, use a link the workflow can read. Check the inputs and credit estimate on the board before starting a run.
Working with this model
Ports are per instance, not fixed
The tables above are empty because the registry entry is a shell. A real Blueprint node gets its ports when you add it: every input node in the Blueprint becomes a port on the left, every leaf output becomes a port on the right. Two nodes pointing at different Blueprints have completely different shapes, so there is no fixed port list to document here. Open the node on the canvas to see its actual ports.
Add it from the Blueprint's page
Press Add to workflow on a Blueprint's page. That route is the only thing that computes the ports and the blueprint id together. A node built by hand arrives with zero handles, can be wired to nothing, and fails at run time.
Credits
The node itself is free. The Blueprint's constituent nodes bill individually against the parent run's user as the child execution runs, so the cost is whatever the inside of that Blueprint costs. There is no separate child run to open: the internals do not get their own execution record yet, so per-step timings and results for them are not shown.
Common questions
How do I use Blueprint on Wireflow?
Set the inputs above and choose Open in a workflow. Sign in to save your board, then check its credit estimate before you run.
Can I use Blueprint through an API?
Yes. Save a workflow with this model, then call the Wireflow run API with its workflow ID. The API tab has examples you can copy.
What changes the credit price?
The price shown uses the model defaults. Your inputs and model settings can change the total. The workflow shows an estimate before you run.
Can I connect this to another model?
Yes. Open it in a workflow and connect its output to another node with a matching input type.