@nicolas_dap Nested fields would indeed be very very helpful and open up a greater range of services that could send data to an API workflow, but they create an associated need around looping, or doing some kind of workflow action for each nested item. That can probably be solved from a design standpoint – it’s similar to “schedule an API on a list” – but we can be sure there will be performance limitations.
And then there’s the problem of multiple layers within a nested list, which would get a little confusing in terms of workflows, which have a bias towards linear flows with an “only when …” statement to handle conditional tests.
The query string parameters are a big move forward though, and open the doors for some integrations that were previously impossible or required Frankenstein solutions.