Nodes

Understand nodes, the building blocks of Draft & Goal workflows: inputs and outputs, node types like LLM and Web Scraper, configuration, and variables.

What is a node?

A node is a single step in your workflow that performs a specific action. Think of nodes as individual LEGO pieces that you connect together to build something powerful.

Each node:

  • Takes inputs (data to process)
  • Performs an action (scrape, transform, analyze, etc.)
  • Produces outputs (results to pass to the next node)
Tip

To choose which family of node to open in the library (Inputs, AI, Integrations, Tools), see Introduction to Nodes. This page covers ports, configuration, and variables.

Workflow canvas in Build mode with connected input, integration, code, and LLM nodes

Anatomy of a node

Connection points

Every node has connection points:

  • Input points (left side): Where data enters the node
  • Output points (right side): Where results leave the node for the next step
LLM node on the canvas with input port on the left and output port on the right

Node types by function

TypeWhat it doesExamples
InputAccepts user inputShort Text, Paragraph, URL
AIUses AI modelsLLM, AI Agent
IntegrationsFetches dataWeb Scraper, Google Sheets
ToolsModifies dataFind & Replace, Merge With Template, Loop, Conditional

Configuring nodes

Click on any node to open its configuration panel on the node.

LLM node settings panel with model, temperature, and prompt fields

Required fields

Fields marked with a red asterisk (*) are required. The node won’t run without them. For example, the URL node requires a target address:

URL *: https://example.com

Using variables

Instead of hardcoding values, use variables to pass data from other nodes:

URL: {{url}}

The {{text}} syntax means “use the output value from the node named text”.

LLM prompt editor referencing upstream node outputs with variable syntax
Info

Learn more about variables in the Variables guide.

Working with inputs

Static values

Enter values directly in the configuration. On an LLM node, for example:

Temperature: 0.7
Max Tokens: 1000

Dynamic values from other nodes

Reference outputs from previous nodes:

Content: {{WebScraper}}
Web Scraper node connected upstream to supply page content to a downstream step

Combining static and dynamic

You can mix both in text fields — for example in an LLM prompt that reads a Short Text value:

Summarize this article about {{topic}}:

Understanding outputs

Every node produces an output that can be used by subsequent nodes. After a run, click a node to inspect its result in the output panel.

LLM node output panel showing formatted markdown text
Node output panel showing structured JSON from a completed step

Output structure

Most nodes output a JSON object with specific fields. A Web Scraper response might look like this:

{
  "status": "success",
  "data": "The scraped content...",
  "metadata": {
    "url": "https://example.com",
    "timestamp": "2024-01-15T10:30:00Z"
  }
}

Node categories

AI Nodes

Leverage powerful AI models for text generation, analysis, and more.

AI Agent node on the canvas with tool and output ports

Data Source Nodes

Connect to external data sources.

Google Sheets Reader node on the workflow canvas

Tools Nodes

Transform and manipulate data.

Find and Replace node on the workflow canvas

Control Flow Nodes

Control how your workflow executes.

Loop node on the workflow canvas with list input and iteration output ports

Best practices

Keep nodes focused

Each node should do one thing well. If a node is doing too much, split it into multiple nodes.

Web Scraper → Extract text → LLM → Summarize → Google Sheets → Save results

One mega-node that scrapes, 
summarizes, AND saves

Name your nodes

Give nodes descriptive names by clicking on their title:

  • ❌ LLM_0
  • ✅ Summarize Article (on an LLM node)

Test incrementally

After adding each node, run your workflow to verify it works before adding more.

Troubleshooting

Node shows an error

  1. Check that all required fields are filled
  2. Verify variable references are correct
  3. Ensure previous nodes completed successfully

Output is unexpected

  1. Click on the node to see its output preview (see Build & Run mode for canvas testing)
  2. Check the logs for detailed execution info
  3. Verify your variable paths are correct — see the Variables guide and tools like JSON Path Extractor when you need a nested field

Next steps