I’m attempting to create a custom action that sends a POST request to Shortcut API. The request succeeds when I test it in Postman or other testing tools; however, when I try to test the request in Intercom’s Custom Action building tool, Intercom arbitrarily inserts escape characters into the JSON in the Request Body, which causes the Shortcut API to return a code 400 Bad Request. Here’s a comparison of the Intercom and Postman consoles (Intercom on the left, Postman on the right). Notice that Intercom has added escape characters to the body. I’ve already confirmed that the error is caused by Intercom inserting those escape characters. Is there any way to force Intercom to send the request as-is? It makes no sense that it would alter a Request Body...those should ALWAYS be sent as-is. Here’s a zoom recording showing the issue, if that helps: https://us02web.zoom.us/rec/share/C1W_oCh039rZ4cvJOi639opBCb2-kocdh16CjsHyILJrqE-gUKno1holp0EI_4rk.7_lD0QAgj0pYeCkQ?startTime=1697468415000

Resolved!Even though the request was automatically using Content-Type: application/json (I kept an eye on that in the console), it looks like I needed to actually specify that in the Headers in the Custom Action builder.Good to keep in mind if you are running into similar issues. Be sure to specifyContent-Type: application/json in the headers!@Eden and Kyle!

Thanks for giving that a try @Doug Taylor. I’ve escalated this as a conversation with the Support team for a support engineer to investigate further with you. They will reach out to you in the conversation as soon as possible!👍

Custom Action is automatically inserting escape characters into request body and causing request to fail

Custom Action is automatically inserting escape characters into request body and causing request to fail | Community

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded