Control Flow
Merge and Match Nodes Reference
Technical reference for `merge` and `matchFiles`, including synchronization modes, timeout handling, and filename pairing rules.
Updated 2 min read
Overview
These nodes coordinate multiple incoming streams:
mergesynchronizes or forwards branches.matchFilespairs files from multiple lists before later processing.
Configuration / Settings
| Node | Setting | Details |
|---|---|---|
merge | inputCount, mode, timeout, onTimeout, onUpstreamFail | waitAll is the synchronization mode. first is a race. any is pass-through. |
matchFiles | inputCount, strategy, sourceInput, regexGroup, ignoreExtension, normalizeSeparators, caseSensitive, allowReuse, regexPattern, regexFlags | Supports sequential pairing or name-based matching with optional normalization. |
Inputs Expected
mergeaccepts any payload type.matchFilesexpects two or more non-empty arrays of file-like objects.
Variables Exported / Outputs
| Node | Output shape | Notes |
|---|---|---|
merge | passthrough input | The executor is intentionally simple because the engine performs the real synchronization work. |
matchFiles | any[][] | Each inner array is a matched file tuple ordered by input stream. |
Common Use Cases
- Wait for a spreadsheet branch and a file branch before generating final output.
- Pair original PDFs with signed copies or sidecar metadata files by filename.
- Race two alternative upstream branches and keep whichever arrives first.
Edge Cases
mergetimeout handling only applies inwaitAllmode.matchFilesdrops incomplete pairs instead of emitting partial matches.- Regex matching compares the selected capture group across inputs.
allowReusedetermines whether one candidate file can satisfy multiple base items.