See the supported connectors for Application Integration.

Edge and edge conditions

Edge

An edge is a connection between any two elements in an integration. The connection denotes the direction of the control flow from one element(task or trigger) to another. The connection can be between a trigger and a task or between a task and another task. By using an edge along with fork and join, you can implement complex branching and conditions in your integration. For more information, see Forks and joins.

For example, if there is an edge from a Send Email task to a Call Integration task, it means that after the Send Email task is run, the next task to run is the Call Integration task. An edge also supports conditional checks. Before the control passes to the next task, you can check for a condition in the edge and based on the result, decide to run the task or not. For more information about the supported conditional checks, see Edge conditions.

image showing highlighted edge image showing highlighted edge

Edge conditions

Edge conditions let you specify the conditions that must be met for control of an integration to pass to the task connected by the edge. The task is run only if the specified conditions are met. Edge conditions are useful in cases where there are multiple incoming edges to a task, where each edge checks for specific conditions before the task.

Specify edge conditions using the following steps:

  1. In the Google Cloud console, go to the Application Integration page.

    Go to Application Integration

  2. In the navigation menu, click Integrations.

    The Integrations page appears listing all the integrations available in the Google Cloud project.

  3. Select an existing integration or click Create integration to create a new one.

    If you are creating a new integration:

    1. Enter a name and description in the Create Integration pane.
    2. Select a region for the integration.
    3. Select a service account for the integration. You can change or update the service account details of an integration any time from the Integration summary pane in the integration toolbar.
    4. Click Create. The newly created integration opens in the integration editor.

  4. In the integration editor navigation bar, click Tasks to view the list of available tasks and connectors.
  5. Select an existing integration or create a new one.
  6. In the integration editor, click on the edge to open the Edge configuration pane.
  7. Configure the edge:
image showing highlighted edge condition image showing highlighted edge condition

Supported operators

The following table describes the supported operators available for use in edge conditions.

Operator Description Example
= Checks for equality between two values $var$ = "value"
!= Checks for inequality between two values $var$ != "value"
< Checks if a value is less than another value 5 < 10
<= Checks if a value is less than or equal to another value $var$ <= 5
> Checks if a value is greater than another value 1 > 0
>= Checks if a value is greater than or equal to another value $var$ >= 0
: Checks if a string contains a substring within it, or checks if a list contains a specific primitive value.

$longString$ : "substring"

$list of values$ : "value"
AND Checks two expressions and returns true if both the expressions evaluate to true. $a$ > $b$ AND $b$ < $c$
OR Checks two expressions and returns true if any one of the expressions evaluates to true. $a$ > $b$ OR $b$ < $c$
NOT Negation operator. Flips the result of an expression. NOT($var$ = "value")

Supported functions

The following table describes supported functions available for use in edge conditions.

Function Description
exists(VARIABLE) Checks if a given variable exists
does_not_exist(VARIABLE) Checks if a given variable does not exist
is_empty(VARIABLE) Checks if a given variable is a list AND is empty. Supports array variable type except JSON array.
is_not_empty(VARIABLE) Checks if a given variable is a list AND is not empty. Supports array variable type except JSON array.

Quotas and limits

For information about quotas and limits, see Quotas and limits.

What's next