Blueprint
Invoke a published Blueprint as a collapsed subworkflow. Its inputs become node ports on the left, its outputs become ports on the right. At execution time, the Blueprint runs as a child execution and pipes its results back into this graph.
Blueprint
Badge: Blueprint
Node type: blueprint:invoke
Category: process
Description
Invoke a published Blueprint as a collapsed subworkflow. Its inputs become node ports on the left, its outputs become ports on the right. At execution time, the Blueprint runs as a child execution and pipes its results back into this graph.
Pricing
- Cost: this node itself costs no credits
Canvas ports
These appear as port handles on the left side of the node.
No input ports.
Sidebar config
These render as form fields in the right-side config panel when the node is selected.
No sidebar config fields.
Outputs
No outputs.
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.
Auto-generated from the Wireflow node registry.