/help/create-a-reusable-node

Loading…

Help center

All topics & search Table of contents Getting startedWhat GraphVM is, the console and dashboard, search, and building your first graph.Graph editorThe editor views, drawing and wiring nodes, the inspector, graph info pages, and checks.Nodes & catalogBrowsing node types, scopes, the connection taxonomy, and reusable nodes.Running & debuggingRun configuration, breakpoints, run pages, logs and output, and controlling live runs.AI generationDescribing a workflow in prose and refining the graph the builder produces.Credentials & modelsAPI keys for integrations, secret references, and LLM access and budgets.Workspace & adminWorkspace defaults, users and teams, billing, security, your profile, and the audit log.ReferenceKeyboard shortcuts, glossary, and pointers to the API documentation.

Reachable from Help → Help center, or press ⌘K and search.

Help center/Nodes & catalog

Create a reusable node

Save a configured piece of work as its own catalog entry instead of copying it between graphs.

In the app

New node
My nodes

Open the scope you want the node to live in and use its New node action (/nodes/{scope}/new).
Name and classify the node — its category and connection classification are what make it findable in the catalog and legal to wire.
Fill in the fields other graphs should be able to set, and leave secrets as run-only references rather than baked-in values.
Save, then find it in the catalog and drag it into a graph to check it wires and runs as expected.

TipPut it in your own scope first. Move it to shared once it has run inside a real graph — a shared node's rough edges become everyone's rough edges.

Related

Browse the node catalogNodes & catalogFind a node type by category, subcategory, owner, or date, and read what it needs before you place it.
Scopes: my, shared, and publicNodes & catalogEvery graph and node lives in a scope, and the scope is part of its URL.
Reference secrets instead of inlining themCredentials & modelsenv: and ${ENV:VAR} references resolve at run time, so no key is ever written into a graph or preset.

More in Nodes & catalog · Search all help