Connecting Nodes

Nodes are connected using edges (lines) that define the flow of data through your workflow.

Creating Connections

Drag to Connect

1. Hover over a node's output handle (right side, circular indicator)
2. Click and drag to create a connection line
3. Drop on another node's input handle (left side)
4. Release to complete the connection

Connection Rules

• Connections flow left-to-right (output → input)
• A node can have multiple outgoing connections
• A node can have multiple incoming connections
• You cannot create circular connections (loops)

Removing Connections

Select and Delete

1. Click on a connection line to select it (it will highlight)
2. Press Delete or Backspace to remove it

Disconnect from Handle

1. Click on a connection's endpoint
2. Drag it away from the handle
3. Release in empty space to delete

Data Flow

When nodes are connected, data flows from the output of one node to the input of the next.

Example Flow

[Trigger: "generate a cat meme"]
    ↓
[Briefputer: generate_brief]
    ↓ (outputs: brief, angle, tone)
[PFPputer: generate_pfp]
    ↓ (outputs: imageUrl)
[Output]

Accessing Upstream Data

In a Resource or Transform node, you can access data from any connected upstream node:

1. Open the node configuration (double-click)
2. Look for Linked Inputs section
3. Select which upstream output to use for each input

Best Practices

Keep Workflows Linear When Possible

Simple left-to-right flows are easier to understand and debug.

Good:  [A] → [B] → [C] → [Output]

Avoid: [A] → [B] ↘
              [C] → [Output]
       [A] → [D] ↗

Use Transforms for Data Shaping

If a resource expects data in a different format than what's provided, add a Transform node between them.

[API Response] → [Transform: extract field] → [Next Resource]

Name Your Nodes

Double-click a node and update its label to describe what it does. This makes complex workflows easier to read.

Parallel Execution

Nodes with independent inputs can execute in parallel:

[Trigger] → [Resource A] ↘
                         → [Output]
[Trigger] → [Resource B] ↗

Both Resource A and Resource B will start executing simultaneously, and Output will wait for both to complete.