Circuitry Logo
Circuitry
Open Editor

Node Reference

Build powerful automation workflows by connecting specialized nodes. Each node type serves a specific purpose and can be combined to create complex automation flows.

Quick Navigation

<div class="overflow-x-auto pb-2"> <div class="inline-flex gap-4 min-w-max">

Core Nodes: Start • Agent • Code • Sticky Notes
Control Flow: Condition • Loop • Fork • Join
Triggers: Trigger • Webhook Response
Actions: Action • Plugin • Response

</div> </div>

Core Nodes

Essential building blocks for every workflow

Start Node

The entry point for every workflow. Provides initial data to downstream nodes.

Configuration:

  • Input Data: JSON data to pass to the workflow
  • Trigger Type: Manual, Scheduled, or Webhook

Output: The configured input data

Trigger Node

Initiates workflows based on external events.

Configuration:

  • Event Type: Webhook, Schedule, Email, etc.
  • Conditions: Filters for when to trigger

Processing Nodes

Agent Node

Processes data using AI language models.

Configuration:

  • Model: Select from GPT-5, GPT-4, Claude, or custom models
  • Prompt: Instructions for the AI model
  • Temperature: Controls creativity (0-2)
  • Max Tokens: Maximum response length
  • System Message: Optional context for the model

Input: Data from previous node Output: AI-generated response

Sticky Notes

Non-executing documentation nodes for annotating workflows.

Features:

  • Rich text editing with formatting (bold, italic, lists)
  • 8 color options for visual organization
  • Resizable and collapsible
  • Dual editing modes (inline and side panel)
  • Real-time content synchronization

Use Cases:

  • Document workflow logic and decisions
  • Add team collaboration notes
  • Create section headers and labels
  • Track TODOs and known issues

→ Complete Sticky Notes Guide

Action Node

Performs specific operations like HTTP requests or data transformations.

Common Actions:

  • HTTP Request
  • Parse JSON
  • Transform Data
  • Send Email
  • Database Query

Configuration: Varies by action type

Code Node

Execute custom JavaScript code for advanced data processing.

Configuration:

  • Code: JavaScript code to execute
  • Timeout: Maximum execution time

Input: Data from previous node as input variable Output: Whatever the code returns

Example:

// Transform and enrich data
return {
  ...input,
  processed: true,
  timestamp: new Date().toISOString()
}

Control Flow Nodes

Condition Node

Branches workflow execution based on conditions.

Configuration:

  • Condition Type: Contains, Equals, Greater Than, etc.
  • Field: JSON path to check
  • Value: Expected value

Outputs:

  • True Branch: Executed when condition is met
  • False Branch: Executed when condition is not met

Loop Node

Iterates over arrays or repeats operations.

Configuration:

  • Loop Type: For Each, While, Fixed Count
  • Array Path: JSON path to array (for For Each)
  • Max Iterations: Safety limit

Input: Array or data to iterate over Output: Accumulated results from all iterations

Parallel Processing Nodes

Fork Node

Splits execution into multiple parallel branches.

Configuration:

  • Branch Count: Number of parallel paths (2-10)
  • Data Distribution: How to split input data

Input: Data to distribute across branches Outputs: Multiple output ports for parallel execution

Join Node

Merges results from parallel branches.

Configuration:

  • Merge Strategy:
    • Array: Combine into array
    • Object: Merge as object properties
    • Custom: JavaScript function for merging

Inputs: Multiple input ports from Fork branches Output: Merged data

Working with Nodes

Adding Nodes

  1. Drag from the sidebar onto the canvas
  2. Or right-click canvas and select "Add Node"
  3. Use keyboard shortcuts (see Shortcuts)

Connecting Nodes

  1. Click and drag from an output port
  2. Drop on an input port of another node
  3. Connections show data flow direction

Configuring Nodes

  1. Click on a node to select it
  2. Use the right panel to configure settings
  3. Test configurations with sample data

Node States

During execution, nodes display their current state:

  • Idle: Gray - Not yet executed
  • Running: Blue with spinner - Currently processing
  • Success: Green - Completed successfully
  • Error: Red - Execution failed
  • Skipped: Gray striped - Skipped due to conditions

Best Practices

  1. Name your nodes descriptively for clarity
  2. Test incrementally as you build
  3. Use conditions to handle edge cases
  4. Leverage parallel processing for performance
  5. Add error handling with condition nodes
  6. Document complex logic in node descriptions

Advanced Features

Dynamic Configuration

Use {{variable}} syntax to reference data from previous nodes:

{{input.userName}}
{{previousNode.output.result}}

Custom Scripts

Some nodes support custom JavaScript:

// Transform data in Action node
return {
  ...input,
  timestamp: new Date().toISOString(),
  processed: true
}

Examples

Simple AI Processing

Start → Agent (GPT-5) → Action (Save Result)

Conditional Branching

Start → Condition → [True] → Agent A
                 → [False] → Agent B

Parallel Processing

Start → Fork → [Branch 1] → Agent → Join → Action
            → [Branch 2] → Action ↗
            → [Branch 3] → Loop ↗

Related Topics