Choose which step to execute next based on a condition

The **branch on expression** action allows you to create logical branches within your integration based on comparisons of config variables, results from previous steps, or static values.

The full list of comparison functions you can use is available on our [Building Integrations](building-integrations.mdx#branch-on-expression-operators) article.

<Screenshot filename="shared/branch-on-expression.png" />

Multiple expressions can be grouped together with **And** or **Or** clauses, which execute like programming **and** and **or** clauses.
Take, for example, this programming expression:

```
if ((foo > 500 and bar <= 20) or ("b" in ["a","b","c"]))
```

The same logic can be represented with a group of conditionals:

<Screenshot filename="shared/branch-on-expression-logic.png" maxWidth="500px" />


Choose which step to execute next based on a value.

The **branch on value** action allows you to branch into one of many paths of an integration based on an input and branch mapping.
Think of it like a [switch/case](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch) or **if/elseif/else** statement.

For example, if you received a webhook request that includes an `order-create`, `order-update` or `order-delete` event, you could structure your branches like this:

<Screenshot filename="shared/branch-on-value.png" />

This setup would be equivalent to some pseudocode reading:

```
if event == "order-create":
  acme.createOrder()
else if event == "order-update":
  acme.updateOrder()
else if event == "order-delete":
  acme.deleteOrder()
else:
  throw Error("Invalid Payload")
```

An "else" branch is generated in the case that the input value does not match any of the values in your branch value mapping.
In the example above, if the notification payload didn't include a known event type, you can log an error and quit.


Given a collection of step results, returns the results of whichever step was executed and returned a result.

Regardless of which branch is followed, branches always converge to a single point.
Once a branch has executed, the integration will continue with the next step listed below the branch convergence.

This presents a problem: how do steps below the convergence reference steps in branches that may or may not have executed (depending on which branch was followed)?
In your integration you may want to say "if branch _foo_ was executed, get the results from _step A_, and if branch _bar_ was executed, get the results instead from _step B_."
Prismatic provides this action to handle that scenario.

Imagine that you have two branches - one for incoming invoices, and one for outgoing invoices, with different logic contained in each.
Regardless of which branch was executed, you'd like to insert the resulting data into an ERP.
You can leverage this action to say "get me the incoming or outgoing invoice - whichever one was executed."

This action iterates over the list of step results that you specify, and returns the first one that has a non-null value (which indicates that it ran).

<Screenshot filename="shared/select-executed-step-result.png" />

Within the component configuration drawer, select the step(s) whose results you would like, and this step will yield the result of whichever one was executed.


Choose which step to execute next based on a condition or value

The **branch** component allows you to add branching logic to your integration.
Think of **branches** like if/then or [switch/case](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/switch) programming statements.
Your integration can follow one branch or another depending on the values of some config variables or results from previous steps.


Action Name	Action Description
Branch on Expression	Choose which step to execute next based on a condition
Branch on Value	Choose which step to execute next based on a value.
Select Executed Step Result	Given a collection of step results, returns the results of whichever step was executed and returned a result.

Branch Component

Integrate with customers’ other SaaS apps, fast

About the Branch Component

Actions

Ready to get started?