> For the complete documentation index, see [llms.txt](https://docs.hablla.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hablla.com/hablla-docs-en/hablla/marketing/batch-flow-executions.md).

# Batch Flow Executions

The **Batch Flow Execution** allows you to execute an automation flow for multiple people in bulk, making it possible to automate communications, updates, and different processes at scale.

Unlike an action limited to sending a single message, in this feature **the entire configured flow will be executed for each person defined as a target of the execution**.

This allows you to use all the versatility of Hablla's Automation Flows to build different strategies and processes.

For example, a batch execution can start a flow that sends a message to a specific audience and, according to each person's interaction, updates information, performs new actions, or transfers the support to an agent.

Other usage examples include:

* Updating People information;
* Running integrations and automations;
* Segmenting different paths according to rules defined in the flow;
* Running custom processes built through the components available in Automation Flows.

The possibilities depend directly on the **logic configured in the flow used in the execution**.

{% hint style="info" %}
The **Batch Flow Execution** is a feature recommended for users who already have knowledge about the creation and operation of **Hablla Automation Flows**.

Before running executions for large audiences, we recommend testing the flow using a reduced number of people. This way, you can validate its behavior before scaling up the execution.
{% endhint %}

## How to create a Batch Flow Execution

The configuration is done in stages, in which you can define **how the execution will happen, who will be part of it, and which flow will be used**.

{% stepper %}
{% step %}

### 1. Access Batch Flow Execution

In Hablla's top menu, access **Marketing** and select the option **Batch Flow Execution**. This page will show the executions already registered in your workspace.

To create a new one, click the <kbd>**+ New Trigger**</kbd>, located in the upper-right corner of the screen.

<figure><img src="https://1592162275-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrmxWrIrMauHcIrsuqfGq%2Fuploads%2FUtaIAczKr8LxVu4MaaeI%2F%5BDOCS%5D%20-%20Como%20Acessar%20Execu%C3%A7%C3%A3o%20de%20Fluxos%20em%20Lote.gif?alt=media&amp;token=afafb876-1b63-42f4-aaed-b8e1135b8bdb" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### 2. Trigger Information Settings

In the first step, configure the basic information of the execution.

> **Trigger Name**: Define a name that will make it easy to identify this execution later. Use a name related to the purpose or audience of the execution to make it easier to identify.

> **Sending Type**: Define **when** the execution should start. You can configure the execution to be carried out **immediately** after completing the trigger setup or define a **schedule** so that it starts on a scheduled date and time.

> **Sending Mode**: Define how the executions will be processed. You can choose between **Single Batch** or **Split**.
>
> * **Single batch:** Use this option when you want to process all executions at once.
> * **Split**: The **Split** mode allows you to divide the execution into smaller groups, distributed over time. When selecting this option, configure:
>
>   * **Interval:** quantity value **in** **minutes** between each batch;
>   * **Batch size:** number of executions that should be started at each interval.
>
>   For example, for an execution aimed at `1.000` people, you could configure:
>
>   <table><thead><tr><th width="198.17236328125">Configuration</th><th align="right">Value</th></tr></thead><tbody><tr><td><strong>Total quantity</strong></td><td align="right">1,000 people</td></tr><tr><td><strong>Batch size</strong></td><td align="right">100</td></tr><tr><td><strong>Interval</strong></td><td align="right">10 minutes</td></tr></tbody></table>
>
>   In this scenario, Hablla will process **100 executions every 10 minutes**, until the entire defined audience has been processed. Split sending can be used when you want to distribute the execution over time instead of starting the entire volume at once.

{% endstep %}

{% step %}

### 3. Define the execution targets

{% endstep %}
{% endstepper %}

**\[GIF — Configuring the information and sending mode]**

### Define the execution targets

In the next step, you will need to define **which people the flow will be executed for**.

Hablla allows you to define this audience in two ways:

| Option              | How it works                                                                                                               |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **File**            | Allows you to use a file containing the data that will be used as input for the execution.                                 |
| **Dynamic Filters** | Allows you to use the People already registered in the workspace and segment them through the filters available in Hablla. |

#### Using a file

If you choose to use a file, upload the document that contains the data that will be used in the execution.

Currently, the following formats are accepted:

* `.xlsx`
* `.xls`
* `.json`

After uploading, continue to the next step of the configuration.

**\[GIF — Uploading a file]**

#### Using Dynamic Filters

If you choose to use the **Dynamic Filters**, you will be able to segment the People registered in your workspace according to the available criteria.

As the filters are configured, Hablla will display the **number of people matching the segmentation**, allowing you to see the size of the audience that will be part of the execution.

The filters follow the same segmentation logic used in other Hablla Marketing features.

To learn about the available filters and understand how to use them, see our documentation on **Dynamic Filters by clicking here**.

**\[GIF — Creating a segmentation using Dynamic Filters]**

### Select the Flow

After defining the execution targets, select the **Automation Flow** to be used.

The selected flow will be executed for the people defined in the previous steps.

It is precisely the structure of this flow that will determine **what will happen during the batch execution**.

For example, if the flow has an action responsible for sending a message, that action will be executed while processing the people defined as targets.

If the flow has other steps, such as data updates, conditions, integrations, or transfers, these actions can also be part of the execution according to the logic built.

**\[GIF — Selecting the Automation Flow]**

### Review and finalize the execution

After completing all settings, review the defined information before continuing.

Check mainly:

* The selected audience;
* The number of people involved;
* The sending mode;
* The schedule, if one was configured;
* The selected flow;
* The actions that will be executed by this flow.

When everything is correct, click **Finish**, in the upper-right corner of the screen.

{% hint style="danger" %}
**Carefully review your configuration before confirming a Batch Flow Execution.**

The selected flow will be executed massively for the defined audience and can perform actions such as sending messages, data changes, and other processes configured in automation.

Depending on the components, channels, and services used by the flow, the execution may also **generate charges related to the use of these resources**.

Therefore, we recommend validating the flow beforehand with a reduced number of people and checking the selected audience before carrying out larger-scale executions.
{% endhint %}

### Confirm the execution

By clicking **Finish**, Hablla will display a confirmation window before recording the request.

To confirm that you are aware of the action that will be performed, you will need to type in the field provided the **confirmation word requested by the system**.

After correctly filling in the confirmation, the button responsible for completing the action will be enabled.

Click the confirmation button to register the Batch Flow Execution.

**\[GIF — Reviewing and confirming the execution]**

### All set!

After confirmation, Hablla will process the execution according to the defined settings.

If you configured an **immediate**, processing may begin after confirmation. If you used a **schedule**schedule

, the execution will follow the configured date and time. **Split**, processing will follow the previously defined interval and batch size.

From that moment on, the behavior of each execution will depend on the logic built in the **selected Automation Flow**.

It is precisely this flexibility that allows Batch Flow Execution to be used for different needs of your operation, from large-scale communications to more complete automated processes.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.hablla.com/hablla-docs-en/hablla/marketing/batch-flow-executions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
