Hello ! I have setup a webhook : its purpose is to receive datas from an external CRM that send datas to our app. Everything working great, until we figured out some datas doesn’t come in the app, when they have non ASCII characters in it (they send a json). Just blank datas, nothing when whith non ASCII characters in values fields.
So I’ve created a test webhook, with a header “Content-Type:application/json” and sent some datas with and without non ASCII char (like é or è that are often used in french) and the data comes right in both case.
Does someone knows about some headers or any other parameters they should send for this to work ?
Did you use Bubble auto-detect payload when first receiving the webhook? (you can use detect header too). Because if Bubble parse the JSON payload sent, normally this is because the application/json header was there.
The issue for me seem to be more related to JSON encoding from the CRM. Did you try to send the CRM webhook to requestbin and check how this is received? (you should also have access to raw payload in requestbin)
requestbin is a tool to debug webhook/ API requests. This will give you a lot of informations about the call received (parsed and raw data, all headers…)
When you created your Backend WF in Bubble, did you use Detect data?
Ok. It may be better to use their sending and activate detect header if needed. You will see the content-type header they useand if Bubble can parse the payload.
After, you can send a request with ascii characters to requestbin from their sending and you can inspect to see if there’s a JSON encoding error
