Custom Action not sending payload in req.body


I am attempting to build an integration service with a custom action that is resolved by a cloud hosted endpoint. Unfortunately, I am unable to retrieve the “payload” object in the request body, as it is outlined in the Custom Action documentation. Here is my current implementation:



And here is the result:

What am I missing?

Hello there @JeffHalbert,

I am not sure I understand where you are getting that. If you are talking about the run URL from your custom action, that should give you a payload like this one from req.body.payload:

  "payload": { //input fields are based on the input fields configuration of your action
     "inputFields": { //fields structure depends on the type of the specific field
        "boardId": 12345678,
        "itemId": 12345678,
        "columnId": 'text_1',
        "targetColumnId": 'text_2',
        "transformationType": { 
             "title": 'to lower case', 
             "value": 'TO_LOWER_CASE' 
      "recipeId": 123456, //unique ID of the recipe for your app. if multiple accounts are using the same recipe, the same recipe ID will be sent
      "integrationId": 123456 //unique ID of the integration recipe added to your board

And you should get a token from req.headers.authorization that will look something like:

eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhY2NvdW50SWQiOjk3MTEwNTcsInVzZXJJZCI6MjM5NTA2MDAsImF1ZCI6Imh0dHBzOi8vasohisabhiuafsibjiuafsiguafs80yasfy89asf8y9g9usaf98hfs7s9af97asgf78asgf79sfgUiLCJpYXQiOjE2Nzk0MDUwMjZ9.ouG8fHZkO5qpSumOsODiuX2PA-hRUiqaLySTPXEmBkI (this is not a real token, just in case)


I’m expecting the request.body to look like the example provided, but it looks like Monday is not sending one at all. When I attempt to deconstruct the request.body into the payload constant, it throws an error because the payload property does not exist. Actually, the request.body does not exist. When I console log the request.body, it returns undefined.

I’m wondering if there is something I’ve done incorrectly in my implementation to have caused this. The session and shortLivedToken are coming through successfully.

Hello again @JeffHalbert,

Can you please send us an email to and share a screen recording showing your entire app’s configuration page, including the whole configuration for your custom action, showing your code and showing us how you are triggering the action and the payload you get to your run URL? Please console.log the entire req so we can take a look into what you are receiving and please do not omit any of this information.

Looking forward to hearing from you!


Thank you @Matias.Monday,

As suggested, I have sent a recording to showing the full application, code, and console.log of the entire request. Thank you for your quick response.

Hello @JeffHalbert,

Thank you for sending the information! We will take it from there :slightly_smiling_face: