# Automation Flow - Subdividing Departments and Setting Up Send Cadence #### Prerequisite: Have a segment containing the Leads that will receive the messages. ## Creating segments For example purposes, 3 empty segments were created, but it could be any desired quantity, depending on the total number of Leads. Assuming the total Leads is 300, each segment should contain 100 of them.

## Creating Flow to distribute the Leads A Flow was created and configured to run for all Leads present in the segment '🏠 Main Segment'.

### Using the Alternator block The alternator block was used inside the Builder. This block alternates between the different paths on each execution, ensuring the Flow goes through all Leads and distributes them, one at a time, among the segments sequentially. In the 'Modify lead segments' action, each block is configured to add its respective segment (Group 1, Group 2, Group 3...).

## Creating Flow to send messages After the Flow runs and distributes all Leads into the smaller segments, a new Automation Flow was created to send messages to each group on different days. The logic is simple: all Leads are checked according to the segment they belong to. If they are in the first group, the message is sent; otherwise, a 1-day Wait block is executed. After that period, the process checks if the Lead is in the second group, and so on, successively.

--- # Agent Instructions: 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.sprinthub.com/en/topics/relate/automation-flows/actions/automation-flow-splitting-departments-and-configuring-trigger-cadence.md?ask= ``` 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.