Why does the API Workflow support sending endpoint parameters as a list/array?

Why does the API Workflow support sending endpoint parameters as a list/array?

As near as I can tell, there’s nothing that can be done with this data in any of the action steps of a workflow. The most obvious scenario I can imagine would be looping through and creating a list of things, but this appears to be verboten.

Or am I missing something? How else can the data be used? The response seems to be “don’t use that, send over everything flat” in forum posts related this.

Any of the list actions should work with this - copy a list of things, delete, make changes to, or as you say schedule an API on a list. The only time I’ve ever used a list parameter though, was to schedule another API on the list. The scenario was that I had a custom state on my page which was a list of concatenated texts and I wanted to insert the components of each item in the list into two separate fields. It was only theoretical though - in response to a forum question.

It ended up looking like this (pList is a list parameter):