According to the sendMail endpoint on the Microsoft 365 Mail Documentation, toRecipients
field accepts an array of collections, each looks like this:
{
"emailAddress": {
"address": "frannis@contoso.com"
}
}
So you’ll need to build the array using an aggregator, so your final structure of the array variable will look like this:
"toRecipients": [
{
"emailAddress": {
"address": "frannis1@contoso.com"
}
},
{
"emailAddress": {
"address": "frannis2@contoso.com"
}
},
{
"emailAddress": {
"address": "frannis3@contoso.com"
}
}
]
Every result (item/record) from a search/match module will output a bundle. To “combine” them into a single structure, you’ll need to use an aggregator of some sort.
Aggregators are modules that accumulate multiple bundles into one single bundle. An example of a commonly-used aggregator module is the Array aggregator module. The next popular aggregator is the Text Aggregator which is very flexible and has applies to many use-cases.
There are other types of aggregator modules, click the below links to find out more:
- Array aggregator
- Text aggregator
- Numeric aggregator
- Table aggregator
- JSON aggregator
- CSV aggregator
- Archive (ZIP) aggregator
- other app-specific aggregators
Read this
The Array Aggregator module allows you to build a complex array of collections for a later module’s field to map multiple items (collections) to it.
Here is an example of using the “Target structure type” of an Array Aggregator module:
As you can see, the “Map” toggle on fields are used when you have an array. You can easily build an array variable to map to a field, by using an Array Aggregator module and select the “Target Structure Type” as the future field you want to map the array into.