I created an agent to help me with writing and translating on my iPhone.
I followed tutorials to connect my workflow with an iOS shortcut.
I send my text from my iPhone via the shortcut. The agent processes it and sends it back to my iPhone.
THE PROBLEM:
Since it’s text in French, special characters need to be handled. The output doesn’t handle special characters, and it seems like UTF-8 isn’t being properly managed.
No issues occur with other shortcuts or workflows.
For your information: My N8N instance is hosted on a VPS server, and I’ve created tons of workflows and agents without ever encountering this issue.
Hi @gualter
Let me rephrase my problem (my screenshot isn’t the right one, so don’t take it into account):
On my N8N workflow there is no problem with special characters. The output is fine.
However, as soon as the content arrives on my iOS shortcut, special characters are not recognized.
I regularly use shortcuts (with other agents who are not N8N) and I’ve never had this problem.
Yes, you have understood both points correctly.
I get the output of n8n via a shortcut as I learned from the various tutorials.
My n8n is hosted on a classic vps server via docker.
I have several automations with outputs on various services and I never had the problem.
As I have various IOS shortcuts without this problem.
Instead of “ß” it’s showing “ß” which are both no German characters. So the speak breaks there and sounds funny. Because of that the iOS shortcut integration doesn’t seem to be useful for other languages than English, at least if they have special characters.
I have the exact same problem. Everything works fine using the shortcut with my MacBook, but when I use Siri and the shortcut with my iPhone, the shortcut execution includes some characters that are not in the n8n flow. In other words, the entire n8n flow is fine, but the iPhone does something when receiving the response that includes strange characters, and as a result, when Siri speaks it, those characters are included, and it sounds awful. As I mentioned, this doesn’t happen on the MacBook, so it must be something with the iPhone. Spanish is the language btw so must have some utf codification problem somewhere.
EDIT: Fixed with:
I have finally found the solution. I’m posting it here for those who have the same problem. The steps to configure the node are:
In your workflow, select the “Respond to Webhook” node.
In the “Response Headers” section, add two new headers: