Text aggregator warning: Last in route

How To
,
1

Hey guys,

I was wondering why text aggregators can’t or shouldn’t be last in route. In the scenario I keep getting warnings about that.

We are building a small scenario that handles form submissions and the notifications afterwards. In the form I am getting 4 arrays that contain values of a checkbox group. What I needed was to create a single variable that stores all values of all checkboxes so I can work with it.

For example I wanted to have:

Goal1, Goal2, Goal3 instead of:

goals [
 1: Goal1
 2: Goal2
 3: Goal3
]

To achieve this I used iterators and text aggregators which are looping through the arrays and then adding all values in a single string separated by a comma.

This is my scenario:

Bildschirmfoto 2024-03-03 um 13.59.56
Bildschirmfoto 2024-03-03 um 13.59.562002×1652 214 KB

My questions are:
Why can a text aggregator not be last in route?
What should I do instead or how can I improve my scenario?

3

I am unsure of the specific reason behind Make’s warning, but in my experience, text aggregators and transformers are tools used for data manipulation. Since the purpose of these tools is to modify data, it’s generally expected that the data will be transformed for a specific use case, such as feeding it into another application. So it’s not expected to be the last module of a scenario.

4 Likes
4

Can you try putting a Set Variable after each Text Aggregator?
Then, before Email an Team, insert a Get [Multiple] Variable?
The way it is now there’s no way for your Email modules to access whatever the Text Aggregators have created.

3 Likes