HTTP Request JSON Body seems to be getting formatted to remove brackets

Hello, I’ve run into an odd situation.

I need to pass a specific JSON structure to create a termination ticket, but Workflows seems to remove the brackets at the beginning and end when it is sent.

I found this quote but I’m not sure that it should be applying to a free form body field, nonetheless it is. Goofy thing too is that in the test workflow output it seems fine but then in the execution workflow export they are gone.

I need to pass this structure to my ITSM to create the termination ticket:

[
    {
        "tickettype_id": "76",
        "details":"Automated ticket creation by SailPoint Identity Security Cloud for ",
        "customfields": [
            {
                "id": "259",
                "value": "2024-12-30T00:00:00.000Z"
            },
            {
                "id": "240",
                "value": {
                    "name": "First Last"
                }
            }
        ]
    }
]

Is there a way to prevent workflows from removing those?

Thank you!

Hi @jewalker ,

{
        "tickettype_id": "76",
        "details":"Automated ticket creation by SailPoint Identity Security Cloud for ",
        "customfields": [
            {
                "id": "259",
                "value": "2024-12-30T00:00:00.000Z"
            },
            {
                "id": "240",
                "value": {
                    "name": "First Last"
                }
            }
        ]
    }

Just provide the above JSON in the body field.

Thanks!! ~ Gokul

I have tried that as well. The target system gives me the same error. The issue is that what you provided is what workflows end up sending instead of leaving the brackets and the beginning and end.

I have managed to work around this by creating the json body within a define variable operator and then passing that to the json body within the http request.