Viltrum

Documentation

Documentation

Back to website

Build

Search

Search

⌘K

⌘K

Build

Working with Nodes

Understand node types, configure settings in the side panel, and pin test data while you build.

5 min read

Every node has the same anatomy: input ports on the left, output ports on the right, and a configuration panel that opens when you select it.

Node types

  • Triggers start a workflow, for example Schedule, Webhook Trigger or an app event.

  • Actions do work in another service, such as Slack, Google Sheets or PostgreSQL.

  • Logic nodes branch, merge, filter and loop over data.

  • AI nodes run models, prompts and generators.

Configuring a node

Select a node to open its panel. Required fields are marked, and any field can switch between a fixed value and an expression. Under Node Configuration you will find node-specific settings, and under Error Handling you decide what happens if the step fails.

Pinning test data

After a test run, click Pin on a node’s output to freeze it. Downstream nodes will use the pinned data on the next run, so you can iterate quickly without calling external APIs again.

Pinned data never runs in production. It only applies when you test from the editor.

Was this page helpful?

Yes

No

Build

Search

⌘K

Build

Working with Nodes

Understand node types, configure settings in the side panel, and pin test data while you build.

5 min read

Every node has the same anatomy: input ports on the left, output ports on the right, and a configuration panel that opens when you select it.

Node types

  • Triggers start a workflow, for example Schedule, Webhook Trigger or an app event.

  • Actions do work in another service, such as Slack, Google Sheets or PostgreSQL.

  • Logic nodes branch, merge, filter and loop over data.

  • AI nodes run models, prompts and generators.

Configuring a node

Select a node to open its panel. Required fields are marked, and any field can switch between a fixed value and an expression. Under Node Configuration you will find node-specific settings, and under Error Handling you decide what happens if the step fails.

Pinning test data

After a test run, click Pin on a node’s output to freeze it. Downstream nodes will use the pinned data on the next run, so you can iterate quickly without calling external APIs again.

Pinned data never runs in production. It only applies when you test from the editor.

Was this page helpful?

Yes

No

Create a free website with Framer, the website builder loved by startups, designers and agencies.