Skip to main content

​
Connecting Nodes

Connections define how data flows between nodes. You create connections by dragging from an output handle to an input handle.

​
Handle types

Handles are color-coded by data type:

​
Creating connections

  1. Hover over an output handle (right side of a node) — it highlights when ready
  2. Click and drag to an input handle (left side of another node)
  3. Release to create the connection
Rules:
  • You can only connect handles of the same data type (e.g., image → image)
  • Output handles can have multiple connections (fan out to several nodes)
  • Input handles accept only one connection — dragging a new connection replaces the existing one
  • Invalid connections (mismatched types) are rejected automatically

​
Connection validation

Hyperclip validates connections in real-time. The connection line turns green when hovering over a valid target handle, and red when the types don’t match.

​
Arrays vs. single items

Some outputs produce arrays instead of a single item — Clip Finder emits Video[] (a list of clips), Parse Scenes emits Text[] (a list of scene descriptions), Collect always emits an array of whatever it gathered. Array handles render with a dashed line style; single-item handles render solid. The validator pairs them strictly:
  • Video[] → Video[] ✅ — to Video Editor: Video Array, Approve & Export, or Split: Array In
  • Video → Video ✅ — normal single connection
  • Video[] → Video ❌ — needs a Split node in between to fan out one item at a time
  • Video → Video[] ❌ — single items can’t fill an array slot; wrap in a Collect inside a Split loop instead

​
Standard clipping flow uses Split → Collect

The standard shape for a multi-clip output is:
Each clip runs through Auto Captions and Video Editor individually, so you can shape per-clip captions/edits. Both nodes detect when they’re inside a Split loop and surface shortcut buttons:
  • Auto Captions → Apply to All Remaining Clips — finishes the current iteration with the chosen style and applies it to every later iteration without opening the design UI again.
  • Video Editor → Skip Editing for All — finishes the current iteration with no edits and skips the editor for every later iteration.
So you can either go through every clip individually, or set the style/skip once and let the rest auto-complete. Split → … → Collect is also the right shape when each item needs its own independent generation pass — image-per-scene, per-clip music, etc. Approve & Export accepts a Video[] directly (e.g., from Collect) and renders one MP4 per clip with a ZIP download.

​
Special cases

Some nodes have dynamic handles:
  • Mixed Media Analysis — Accepts dynamic image and video inputs in addition to its base text input
  • Video Editor — Accepts multiple video inputs for combining clips
  • Image Generation — Can accept an optional image input for reference-based generation

​
Removing connections

Click on a connection line to select it, then press Delete to remove it.