Pricing
Apps
Log in
Start trial

Merge

Wait for two or more incoming branches to arrive, then continue the workflow as one path.

1 actionPolling

AI-assisted documentation1 min read

This documentation is compiled from our integration source code, internal specs for Merge, its official API documentation and anonymized requests logs we collect from our support team[2].

Open Merge on WEXTL →

The list below is a reference of every Merge node module the integration supports. You will be able to pick any of them on the workflow canvas while building automations.

Each Merge node module below opens to reveal its input parameters, outputs, and connection requirements.

MergeAction

Merge has no settings; it waits for its incoming branches and continues as one path.

Look for Merge templates in the WEXTL template library.

Browse templates →
  1. Continue[2]In an error-handler branch, swallow the error and resume the workflow on the success path.
  2. ConditionBranch the workflow on a boolean rule — route matching data down the true path and everything else down the fallback (else) route.
  3. Human in the LoopPause the run for a person to review, approve, or reject before the workflow proceeds.
  4. IgnoreIn an error-handler branch, discard the failed item and stop this path without failing the run.
  5. FunctionCall a built-in or your own custom function as a single workflow step, with typed inputs and a result output.
More apps in Built-in category →
  1. WEXTL® Merge Source Code connector implementation.
  2. Our users use cases and automations.
  3. Official API Documentation for Merge.
  4. WEXTL® visual workflow builder data.

Last updated: Jul 18, 2026 19:12

How we write our apps documentation

How we compile these docs — sources, AI's role, and how we verify.