Recipes are built by connecting nodes on a canvas. Each node has typed input and output ports that you wire together to form a processing pipeline. This guide covers the node types available in the palette and the workflows they support.
Input nodes provide data to your recipe. They appear in the Input section of the node palette.
Add file - Upload any file as an asset. This is typically the starting point for image-based workflows.
Connect read - Defines an input port for automation recipes. Used when a recipe is triggered programmatically rather than run manually.
Corner set - Define parameter corners for sweep runs. Outputs both the active corner and the full set of corners.
Extract image - Takes a file (PDF, SVG, 3D model) and extracts a raster image from it. Useful for pulling reference drawings out of documents before sending them to a process node.
Import - Import EDA libraries and schematics directly. Outputs a library, schematic, and preview image.
Prompt - A text field where you describe what you want to create. Most process nodes accept a prompt input for context.
Mechanical nodes run remotely and handle CAD tasks. They appear in the Mechanical section of the palette.
Interpret drawing - Analyzes an engineering drawing and extracts structured dimensions and parameters. Outputs a parameter set that can feed into a Model node for more precise geometry.
Model - Creates 3D CAD models from drawings and prompts. Accepts separate image inputs for part and enclosure references.
Other Mechanical nodes (Drawing, Assembly, Sketch) are planned but not yet enabled.
EDA nodes run remotely and handle electronic design tasks. They appear in the EDA section of the palette.
Library - Creates component library symbols and footprints from reference images and prompts. Accepts separate image inputs for symbol and footprint references.
Other EDA nodes (Schematic, PCB, CAM, Wire diagram, SPICE) are planned but not yet enabled.
Output nodes are the terminal step of a recipe. They appear in the Output section of the palette.
Connect write - Defines an output port for automation recipes. Paired with Connect read to form the boundary of a headless pipeline.
Embeddable - Publishes the output artifact so it can be embedded or shared externally.
Live design - Sends the result to your local Neurocad installation for viewing and further editing.
Run recipe - Executes the entire recipe as a job. Also used to publish the recipe as an embeddable link.
Other output nodes (Remote journaled, Stored macromodel) are planned but not yet enabled.
When you create a new recipe you can start from a preset template. These wire up common workflows so you can get started quickly.
EDA presets
Extract footprint - File > Extract image > Library (footprint mode) > Live design
Extract symbol - File > Extract image > Library (symbol mode) > Live design
Mechanical presets
CAD part from drawing - File > Extract image > Model (part mode) > Live design
CAD enclosure from drawing - File > Extract image > Model (enclosure mode) > Live design
CAD part from interpreted drawing - File > Extract image > Interpret drawing > Model > Live design. The interpret step extracts dimensions from the drawing and passes them as parameters to the model node.
Automation presets
Automation: Library symbol - Connect read > Library > Connect write
Automation: CAD part - Connect read > Model > Connect write
Automation presets use Connect read/write instead of file inputs and live design outputs. They are designed for triggered or headless execution. The typical workflow is to prototype with a standard preset first, then adapt for automation once the flow works.
Blank recipe
Blank recipe - An empty canvas. Build your recipe from scratch.
Nodes communicate through typed ports. The main port types are:
Text - Prompt and description strings
Image - Raster images extracted from documents or uploaded directly
Data - Structured data like parameter sets and sweep results
EDA - EDA artifacts (libraries, schematics, netlists)
Mechanical - CAD artifacts (3D models, drawings, assemblies)
Generic - Accepts any type. Used by output nodes so they can receive artifacts from either domain.
The canvas enforces type compatibility when you draw connections. Generic inputs accept any output type, but typed inputs only connect to matching outputs.
Last updated March 26, 2026