Skip to main content

Connector Action

Connector action merges multiple branches and proceeds when any one of them is completed.

Updated yesterday

The Connector action in Yeeflow’s workflow is a logic control action used to merge multiple parallel execution paths into a single flow.

When there are multiple tasks or branches running in parallel (e.g., AI processing, approvals, or other operations), the Connector action can be used to unify them.


How It Works

  • As soon as any incoming line reaches the Connector action, it is considered passed.

  • It does not wait for all paths to complete.

  • Ideal for scenarios where any one of the parallel branches is sufficient to proceed.

Tips:

When any incoming line reaches this action, it is considered passed.


Difference Between Connector and Inclusive Gateway

Comparison

Connector Action

Inclusive Gateway Action

Type

Merge action

Branch/Merge action

Incoming behavior

Passes when any line arrives

Waits for all incoming lines

Waits for all?

❌ No

✅ Yes

Typical use case

Continue when any condition is met

Continue only when all parallel tasks are completed


When to Use

Use the Connector Action When:

  • You have multiple AI assistant actions (e.g., classification, summarization, etc.) and want to proceed once any one completes.

  • You are handling conditional branches and only need one path to meet the criteria.

  • You have parallel approvals where any one approval is enough to proceed.

Use the Inclusive Gateway Action When:

  • You must wait for all branches (e.g., all approvers) to complete before moving forward.

  • You are aggregating data from multiple sources and want to process only after all tasks are done.


How to Use the Connector Action in a Workflow

  1. In the workflow designer, open the Logic and Flow section in the left panel.

  2. Drag and drop the Connector action into the workflow canvas.

  3. Connect multiple parallel branches to the Connector action.

  4. From the Connector action, continue the flow to the next step (e.g., send email, end action, etc.).

  5. In the right-hand configuration panel:

    • Action name: Assign a clear and descriptive name to the action.

    • Description: (Optional) Add notes to explain the logic or use case.

Example: As shown in the image, three AI assistant actions are merged by a Connector action. Once either path completes, the workflow proceeds to the send email action.

Did this answer your question?