I’ve got a project where a user (we haven’t found him or her yet ) copies invisible characters into their databases. Also still no idea what this character is, but it messes up the workflow that converts json to excel. As a matter of fact, the workflow doesn’t even start (when testing), and apparently the request doesn’t even touches the Webhook node. I’m immediately getting a
Hi @dickhoning, my best guess is that your character could be something like unicode character U+2029 (a paragraph separator). This is a character requiring encoding in many applications, not just n8n or the JSON Path Finder website you are using.
So you would most likely need to apply proper encoding before sending this in a webhook as part of a JSON string, for example as suggested here on StackOverflow.
Alternatively, you could consider sending this value using a content type other than JSON. Multipart for example would worked fine when testing this just now: