How to pass array to a form input in Workflow from httprequest action and form as action?

[vdivakar (Vaibhav Divakar)]

Hi Developers,
We have workflow in which there is HTTPRequest step and after which we are putting a form for user.

We want to pass the array data from this httprequest step to the form step as an form input.

I am having hard time passing the array in the form,

Any insights on how to do it are appreciating.

My Form :

What I am trying to do in Workflow

The array that I want to pass is at path $.hTTPRequest.body.attributes.divisions

The error that I am getting is NOT making any sense to me:

Any insights are appreciated.

[schattopadhy (SHANTANU CHATTOPADHYAY)]

@vdivakar
try something like shown below the example fetches list of accounts a users owns so a array input has been used

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Hi @vdivakar
Can you show how the HTTP response looks like?

[vdivakar (Vaibhav Divakar)]

[
    {
        "authoritative": true,
        "systemAccount": false,
        "uncorrelated": false,
        "features": "DISCOVER_SCHEMA, DIRECT_PERMISSIONS, NO_RANDOM_ACCESS",
        "cloudLifecycleState": null,
        "identityState": "ACTIVE",
        "connectionType": "file",
        "uuid": null,
        "nativeIdentity": "location1",
        "description": null,
        "disabled": false,
        "locked": false,
        "type": null,
        "isMachine": false,
        "recommendation": null,
        "manuallyCorrelated": false,
        "hasEntitlements": true,
        "sourceId": "7f0fb36914944637b2a335691febbe69",
        "sourceName": "Location and Division Mapping Test",
        "identityId": "ec783e1705ca4d04abcb4c6e021e9262",
        "identity": {
            "type": "IDENTITY",
            "id": "ec783e1705ca4d04abcb4c6e021e9262",
            "name": "location1"
        },
        "sourceOwner": {
            "type": "IDENTITY",
            "id": "d8b3c1e1ec984ede8d12a75905aa019e",
            "name": "Vaibhav Divakar"
        },
        "attributes": {
            "location": "location1",
            "divisions": [
                "div1",
                "div2"
            ],
            "idNowDescription": "3ac84a606318ab4b8c16d3f8157f6ebe9da4ee81e775b471f1e9b78bdcdf3278"
        },
        "origin": "AGGREGATED",
        "ownerIdentity": null,
        "ownerGroup": null,
        "id": "d3c9e30d6ea442b3b3773d48eea63815",
        "name": "location1",
        "created": "2026-01-29T11:20:13.770Z",
        "modified": "2026-01-29T13:49:49.102Z"
    }
]

@sidharth_tarlapally, this is my http response,
I want to pass [“div1”, “div2“]

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

try :
divison1
$hTTPRequest.body[*].attributes

Array Label
$.divisions

Array Value
$.divisions

[vdivakar (Vaibhav Divakar)]

@sidharth_tarlapally, it still gives me this error
I tried both with $hTTPRequest.body[*].attributes and $hTTPRequest.body[0].attributes

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Can you show the latest configuration?

[vdivakar (Vaibhav Divakar)]

Actually now I am seeing that with the $hTTPRequest.body[*].attributes, the test workflow does not give any error , but it is getting stuck at loading the form.
When I enabled workflow and tried, it is loading the form, but the values div1 and div2 are NOT coming up in the form in the dropdown field

[lampard08 (Chelsea Blue)]

try :
divison1
$hTTPRequest.body[*]

Array Label
$.attributes.divisions

Array Value
$.attributes.divisions

[sidharth_tarlapally (TARLAPALLY SIDHARTH)]

Please share the workflow execution and definition (mask sensitive data)

[vdivakar (Vaibhav Divakar)]

@sidharth_tarlapally , Shared in private chat..!!

[vguleria (Vikas Guleria)]

Hi @vdivakar

Can you please try like this

division1 → $.hTTPRequest.body[*].attributes ( if the result you are not getting as list , then you can use .hTTPRequest.body.attributes)

Array Value–> $.divisions
Array Label –> $.divisions

Please let me know if this works.

Thank You.
Regards
Vikas.

[rpriya (Priya Rudra)]

Hi @vdivakar,

Did you find a solution to this?

Per my understanding- Form Inputs expect a list of objects to be passed in. From this list, the individual objects are displayed as selectable options in the dropdown field of the form.

If instead a list of primitive elements, such as strings, is passed in, the entire list is treated as a single option and displayed as one entry in the dropdown, rather than as separate selectable values.

For example, if the data is provided as "divisions": ["div1", "div2"], this is a list of strings. However, if the structure of the data is a list of objects—where each object contains a single division value—then that list of objects can be passed to the form input. This would allow the dropdown to correctly display each division value as a separate selectable option.

Adding to this, it seems your use case is to display the current divisions associated with an account directly in the form. I’m not entirely sure what your current design looks like for the source from which you’re trying to fetch the account’s division values.

That said, there is a potential workaround that could be helpful here. You could mark the divisions as an entitlement attribute, which would allow each division value to be represented as a separate entitlement object assigned to the account. With this approach, you could then leverage the Account Entitlement API to retrieve a list of objects (as explained above) and display the division values, meeting your use case more effectively

[vdivakar (Vaibhav Divakar)]

@rpriya , great insights,
I will see if I can mark the column as entitlement..!!
Thank you..!!

[chakribravo10 (chakri bravo)]

you need to feed the variable something like this $.httpRequest.body[*].attributes.JSON(). i had somewhat similar requirment where i had to display governance groups and it worked for me i was display those as dropdown for non admin to select