@User15717589852053945299 (Customer)​ --

Few questions:

1. Does the payload always have multiple entries like this one?
2. Are you wanting to Assign "each" user (two visible in your example)?

This one is relatively easy if you are wanting to perform an action against EACH of the users listed in your example. You just need to break down in current input into something that can be passed to a helper flow that finishes the job.

See example:

However, if you are wanting this to be some object/list that contains all of the users in the input as a final output this is quite a bit more complicated.

Does the payload always have multiple entries like this one?

No. But I do have a separate workflow for a single assignee. Is it possible to merge that to this workflow?

Are you wanting to Assign "each" user (two visible in your example)?

Yes

@User15717589852053945299 (Customer)​  - Shouldn't matter if there is 1 or more. The key thing here is what you plan to do with the data. If the data (email) is going to be leveraged as a target for taking an action on each email address then the above should consistently work.

The point of the "length" & "slice" cards in the provided screenshot is to always skip the place 0 which is going to be nothing (since a split was done on the first character) and ensuring the remaining places are captured. Since the example would only technically have places 0,1,2 using the length value of 3 just means it will be one longer than the actual remaining list length so that last place since it doesn't exist will not be used for the new list creation resulting in a list of 2. In a scenario where it is just one the length/slice would be: drop 0, grab place 1 & 2 but 2 will be empty resulting in a new list of 1.