Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/696925ea-1264-800c-8cec-22fafd520907
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==== π How to Fix / Workaround ==== ===== β 1. Force UTF-8 parsing ===== In your HTTP Request node: # Set Response Format β String # Add header: </code>`<code> Accept-Charset: utf-8 <syntaxhighlight>3. If you have control over headers, also add: </syntaxhighlight> Content-Type: application/json; charset=utf-8 <syntaxhighlight> This explicitly tells n8n to parse the response as UTF-8. ===== β 2. Try reading raw binary and converting manually ===== Instead of interpreting it as JSON/text immediately, you can do: # In HTTP Request node: - Response Format β Buffer/Binary # Pass buffer into a Function Node: </syntaxhighlight>js const buf = items[0].binary.data; // adjust if different key const str = buf.toString('utf8'); // enforce UTF-8 return [{ json: JSON.parse(str) }]; </code>`` This ensures the text is decoded as UTF-8 manually. ===== β 3. Check Shopify API pagination ===== If youβre requesting fewer products via pagination (e.g., cursors), the API might return slightly different content or headers. Make sure both requests use the same Accept headers as in the working larger request. ===== π Extra Tips ===== βοΈ Use the latest Shopify GraphQL / REST endpoints β older ones can sometimes omit proper charset headers. βοΈ If possible, test the same requests using curl and inspect the raw headers β this will confirm whether the charset header is missing. βοΈ Always set your HTTP Request node to explicitly expect UTF-8 when dealing with Unicode text.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)