Skip to content

Connecting Nodes

Connections define the flow of your workflow - they tell CiraIQ which node to execute next.

The simplest workflow is a straight line:

Trigger
Action
Action
1

Locate Output Handle

Find the small circle on the right edge of the first node

2

Click and Drag

Click the output handle and drag towards the next node

3

Release on Target

Drop the connection on the input handle of the target node

Creating connection animation Creating Connection - Show step-by-step connection process

One node leads to the next in order:

[Start] → [Step 1] → [Step 2] → [Step 3] → [End]

When to use: Simple, linear workflows

Workflow splits based on conditions:

[Trigger] → [Condition]
├─ True → [Action A]
└─ False → [Action B]

When to use: Different outcomes based on data

When nodes are connected, data flows through them:

Google Sheets

Outputs: Row data

→ (Data flows) →

Email

Uses: Row data in message

💡 Understanding Data Flow:
Each node can access data from all previous nodes in the workflow. This is how you can use form data in emails, API responses in messages, etc.
  • Trigger → Action
  • Action → Action
  • Action → Logic → Action
  • Logic → Multiple branches
  • Action → Trigger (workflows must start with triggers)
  • Node → itself (creates infinite loop)
  • Multiple triggers in one workflow (use separate workflows)
⚠️ Avoid Loops:
Don't create circular connections (A → B → A). This causes infinite loops and will fail.

Method 1: Click the line and press Manage Method 2: Right-click the line and select “Delete”

Deleting connection context menu Deleting Connection - Show context menu

  1. Delete the old connection
  2. Create a new connection to different node

Some builders allow dragging the connection endpoint to a different node.

Connections provide visual feedback:

  • Solid Line - Valid, active connection
  • Dashed Line - Conditional branch
  • Red Line - Configuration error
  • Animated - Data flowing during execution
✅ Connection Tips:
- Keep connections short and direct - Avoid crossing lines when possible - Use clear node placement (left to right) - Test each connection before adding more

One trigger, multiple actions:

[Trigger]
├─ [Email]
├─ [Slack]
└─ [Database]

All actions run in parallel.

Each action waits for the previous:

[Trigger] → [Fetch] → [Transform] → [Send]

Can’t create connection?

  • Check if target node accepts inputs
  • Ensure source node has output
  • Try zooming in for better precision

Connection disappears?

  • Check if nodes are compatible
  • Look for error messages
  • Verify both nodes are saved