A user seeks to access translated product titles within Shopify Flow, initially attempting to use GraphQL queries and the translations field from the “Get product data” action. Despite trying various approaches with Liquid variables, the translations field remains inaccessible and returns validation errors.
Root Cause:
Shopify staff confirmed this is a known limitation—Flow cannot currently access fields requiring arguments (like translations and metafields). The product team is aware but prioritizing metafields and API version updates first, with no concrete timeline for native translation support.
Current Workaround:
Use the “Send HTTP request” action to directly call the Shopify Admin GraphQL API:
Generate an API access token
Query translations via GraphQL (example queries provided)
Parse the JSON response using “Run code” action to extract translated values
Community members have successfully implemented this workaround, sharing code snippets for querying product translations by locale. The discussion remains open as users await a more integrated solution within Flow’s native interface.
Summarized with AI on October 27.
AI used: claude-sonnet-4-5-20250929.
I would like to know if it is possible to get the translated product title somehow in Flow.
I have used Get product data and for each I would like to do query to get the translated product title but I’m not sure if that is possible. Is there any other way?
Thanks in advance!
This is the query I have used to get the translated product title. (Cleared the id and locale.)
Unfortunately still it says: “‘translations’ is invalid. Replace this variable.”
For some reason it doesn’t have access to the translations, am I right? Any ideas?
I changed your “getProductForEachItem.translations” to this: “getProductDataForeachitem.translations” because it said it was invalid and should replace the variable.
We looked into it and found a problem with those fields and how Flow is able to access them. It’s on the product team’s radar to look at so stay tuned!
We have a feature in the works to be able to access fields that require arguments (like translations and metafields), but are focused on metafields currently. We can’t offer a timeline at the moment for when translations will be available.
Cheers @paul_n , yeah I know you in April '24 couldn’t offer a timeline for when translations will be available, do you have anything more concrete at this time?
Being able to work with translations in Flow would def be a game changer for us dealing with multiple languages.
There is a workaround in that you can now use Send HTTP request to directly call the API and get the translations. You’ll need to generate an API key to make the call. Which API depends on which translations.
Regarding an easier to use option, we are still working to get Flow on the latest API version, which needs to finish before we take us this work. It is going faster, but I don’t have an ETA on when this will be done.
Thanks @paul_n for the suggested workaround. I can see that as a viable temporary solution to ease som of the automation work for translation - while waiting for a more handy solution via Flow. I’ll make some tests.
Any more info on this? I am running into the same problem now.
For the workaround how is that supposed to work? It seems like the REST api can’t access the translation data and the graphQL api can’t be used in Flow, so I would need to have another server running somewhere just to proxy the request to access the product translations?
and most probably afterwards you will need to add a run custom code action to parse the response so you are able to get the content for me I only wanted to get the translation digest