---
title: "Introduction to Data Workflow Gateways Operators"
slug: "introduction-to-data-workflow-gateways-operators"
updated: 2025-09-26T04:35:29Z
published: 2025-09-26T04:35:29Z
canonical: "docs.unqork.io/introduction-to-data-workflow-gateways-operators"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction to Data Workflow Gateways Operators

The [**Gateways operators**](/v1/docs/gateways-operators) let you introduce decision logic, control Data Workflow pathways, and merge and split branches different Data Workflow paths.

## What You'll Learn

In this article, you'll get an overview of the various [Data Workflow](/v1/docs/introduction-to-data-workflow) Gateways operators.

## Gateways Operators

Below is a list of the Data Workflow Gateways operators with descriptions of how to use them.

| Operator | Description |
| --- | --- |
| [Branch Merge](/v1/docs/branch-merge-operator) | Merges two pathways created by the Branch Split operator. This operator has two inputs, but it only receives the input passed by the Branch Split operator. The pathway not taken by Branch Split is blocked. > [!WARNING] > You must use the [Branch Merge](/v1/docs/branch-merge-operator) operator with the [Branch Split](/v1/docs/branch-split-operator) operator. |
| [Branch Split](/v1/docs/branch-split-operator) | Splits a single input into two pathways based on the conditional event entered in the **Condition** field. When the **Condition** is `True`, the upper output port passes the data. When `False`, the lower output port passes the data. > [!WARNING] > You must use the [Branch Split](/v1/docs/branch-split-operator) operator with the [Branch Merge](/v1/docs/branch-merge-operator) operator. |
| [Decision](/v1/docs/decision-operator) | Chooses one of two paths for your data to pass based on the conditional event entered in the **Condition** field. If your data meets the criteria, it follows the upper output port. If your data does not meet the criteria, it follows the lower output port. The Condition statement must use <, >, =, >=, or <=. You can use A as an alias for the data coming into the input port. You can use _arg to reference values coming into the top argument port. For example, A > _arg. You can also use OR statements. For example, OR(A="a",A="b",A="c"). > [!NOTE] > The **Input List** setting is optional. If you using this setting, the selected component must be the component connected to the input port. |
| [Gate](/v1/docs/gate-operator) | You can use this operator to pass or block data to another operator based on a specified criteria. When the **Condition** is **True**, the data passes to the next operator. When the condition is **False**, the operator blocks the data and stops the Data Workflow. > [!TIP] > You can reference `_arg` in the **Condition** field to allow or block data from the input connected to the top argument port. |
| [Input Switch](/v1/docs/input-switch-operator) | Switches between two inputs based on a specified criteria. You'll connect two different inputs to the operator and enter your criteria in the **Condition** field. If the result of your condition is **True**, data from the upper input port passes. If **False**, data from the lower input port passes. > [!TIP] > You can use `_arg` in the **Condition** field to reference the input connected to the top argument port. For example, `_arg='false'` or `_arg=0`. |

## Resources

- [Introduction to Data Workflow](/v1/docs/introduction-to-data-workflow)
- [Data Workflow Component](/v1/docs/data-workflow-component)
- [Introduction to Data Workflow I/O Operators](/v1/docs/iooperators)
- [Introduction to Data Workflow Table Operators](/v1/docs/table-operators)
- [Introduction to Data Workflow Array Operators](/v1/docs/array-operators)
- [Introduction to Data Workflow Object Operators](/v1/docs/object-operators)
- [Introduction to Data Workflow Value/String Operators](/v1/docs/valuestring-operators)