Inspiring

Solved

Data mapper in HTTP Actions for multipart endpoints

Forum|Forum|6 months ago
February 27, 2026
8 replies
276 views

In my application, all request bodies need to be form data with data as the key and the json body as the value. I am able to handle this in http actions with raw json body by having it be something like data={<insert body here>} and having the header of Content-Type=application/x-www-form-urlencoded

I want to use the new data mapper functionality in http actions so it will handle escaping and such for me, however I cannot seem to find a way to get it to work with this setup. I have attempted numerous times with variations of data: <json to mapper syntax> , but the app always returns with a missing data element error. Is there any way to handle this currently?

Best answer by Kevin Mok

Hey @andrewwhitley we are putting in a change to support this explicitly when you use set the headers. It will allow you to do this:

data: payload

and it should send it as

data={}

I’ll update when the change is deployed

rgeroulo

Community Manager

@andrewwhitley can you try $STRINGIFY() on your value? Something like this:

data: $STRINGIFY(<json to mapper syntax>)

Kevin Mok

Community Manager

Can you also share what you are doing? It’s hard for me to visualize it right now.

A

andrewwhitleyAuthor

Inspiring

@rgeroulo - I have tried things like the following as well and am still getting the no data error from the application:
data:
'$STRINGIFY_JSON({})'

@Kevin Mok - In my action, my raw json body that is accepted by the application is the following:
data={
<json>
}
The app needs the data key for it to be accepted.
When I try to convert this to the data mapper, even when I have data as the first top most element, the application always says that it is missing the data object. From testing in the logs, it looks like the problem is that the request body needs to be a string that the app is then parsing and the data mapper is mapping it to an object. If there is another Content-Type I can use for this to be accepted as valid form-data of data={<json>}
When looking at how it works in postman/curl the body is included with this syntax:
--form 'data="{}"'

varockiasamy

Employee

@andrewwhitley Can you try passing it in the query params section with the Key as data and the Value as the json object?

Kevin Mok

Community Manager

@andrewwhitley - I think this would send the whole payload as a string

Can you try something such as this:

EVAL():
    expression: data.$STRINGIFY_JSON()
    args:
        data:
            data:
                xyz: "'test'"

A

andrewwhitleyAuthor

Inspiring

Thank you both for the ideas. I tried them both and unfortunately neither of them was successful in that the application returned with a “No Data found” error. I will continue using raw json for this connection.

Kevin MokAnswer

Community Manager

Hey @andrewwhitley we are putting in a change to support this explicitly when you use set the headers. It will allow you to do this:

data: payload

and it should send it as

data={}

I’ll update when the change is deployed

Kevin Mok

Community Manager

Hey @andrewwhitley - this should work now!

Sign up

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.

Login or create an account

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.