q5nrb (q5nrb) asked a question.
Hi,
I have an object looking which contains multiple users' information. I would like to send each user complete information down to a helper flow, and struggle to send the right information downstream. The object looks like this:
{
"users": [
{
"id": "f5[CUT]1c4",
"user_name": "De[CUT]mo",
"first_name": "De[CUT]",
"last_name": "[CUT]mo",
"membership_status": "active",
"email": "de[CUT]mo@n[CUT]o",
"membership_created_on": "2022-01-13T15:36:33.847",
"membership_id": "15[CUT]04"
},
{
"id": "a4[CUT]b2",
"user_name": "Do[CUT]nt",
"first_name": "Do[CUT]",
"last_name": "[CUT]nt",
"membership_status": "active",
"email": "do[CUT]@n[CUT]o",
"membership_created_on": "2022-01-13T08:53:53.137",
"membership_id": "77[CUT]7e"
},
{
"id": "b6[CUT]37",
"user_name": "Ma[CUT]dt",
"first_name": "Ma[CUT]",
"last_name": "[CUT]dt",
"membership_status": "closed",
"email": "ma[CUT]@n[CUT]o",
"membership_created_on": "2021-11-01T08:17:50.577",
"membership_id": "8f[CUT]99"
}
]
}
And I would like to send each user downstream like this:
{
"id": "b6[CUT]37",
"user_name": "Ma[CUT]dt",
"first_name": "Ma[CUT]",
"last_name": "[CUT]dt",
"membership_status": "closed",
"email": "ma[CUT]@n[CUT]o",
"membership_created_on": "2021-11-01T08:17:50.577",
"membership_id": "8f[CUT]99"
}
Any advice?
Bonus question, the object may contain thousands of users. I can control the size of returned users, and I guess maximum about 9 000 users. Is there a practical limit I should be aware of - it might push into the yellow zone, but what is considered "Large data processing within a single execution" (ref: Large data processing within a single execution)
Thanks,
Mads
Sometimes I miss an edit button...
ref: https://help.okta.com/wf/en-us/Content/Topics/Workflows/workflows-system-limits.htm
Haha, I found it! Object Get card to a list, then the List For Each card 🥳
Glad you were able to solve it.
You had also mentioned a user amount (around 10k). With the "For Each" you do have a concurrency (it defaults to 1 as in your screenshot). The concurrency dictates how many Helper flows are spun up at a time for processing the list. While it will speed up the flow it also could potentially cause rate limit problems depending on the endpoint(s) you are communicating with.