> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/connectors/helpers/multi-case-helper.md).

# Multi Case Helper

<figure><img src="/files/hmdK1j9pp00CPvPJzYow" alt="" width="215"><figcaption></figcaption></figure>

## Overview

With the Multi Case Helper, you can route the Flow path based on the specific value of some field, variable, etc.

## Actions

The **Multi Case Helper** has only one default action - **Select case decision**.

The label of the corresponding arrow needs to match the test case value so that its Flow path is taken. You can add as many arrows as you like.

## Example

Let's imagine a Flow that takes data from a form and based on a select field in the form should either create a payment in Stripe, create a new deal in a CRM such as HubSpot, or create a new ticket in a system such as Zendesk.

The Multi Case Helper in that case takes the field as the test case value:&#x20;

<figure><img src="/files/KRmAUHarXW1E0QQln4Lp" alt="" width="563"><figcaption></figcaption></figure>

Based on that value of `{{ inquiry_type }}` it will follow one of the three arrows to the next step of the Flow:

![Flow paths after Multi Case Helper](/files/e0nOaPTqVPPzjQQIrlf3)

## Defaulting to a Case

Q: Is there a **standard (default)** action possible with the Multi Case Helper?

A: It is possible to add in the Multi Case Helper e.g.:

```django
{% if reference == ‘value1‘ or reference == ‘value2‘ or .. %}
{{ reference }}
{% else %}
default
{% endif %}
```

Then three arrows need to be created with the following names:

* value1
* value2
* default

Thus, the flow route defaults to `default` whenever none of the other arrows match.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.locoia.com/connectors/helpers/multi-case-helper.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
