Parse a clean JSON string returned from a Text Parser Replace module into a JSON Parse module so I can iterate over an array and send each item as a separate Notion block.
What is the problem & what have you tried?
The Text Parser Replace module outputs clean valid JSON confirmed in the output bubble. The JSON Parse module set to {{7.result}} returns BundleValidationError — Missing value of required parameter json on every run. I also tried {{trim(7.result)}} and using parseJSON() function directly in an Iterator array field. All return the same error. The JSON string looks exactly like this:
{“title”: “Sample Analysis Title”, “bullets”: [“insight one”, “insight two”, “insight three”]}
Error messages or input/output bundles
BundleValidationError — Validation failed for 1 parameter — Missing value of required parameter ‘json’
This usually means the Parse JSON module is getting nothing at all from 7.result at runtime, even if the bubble shows text. In your example, the JSON also uses curly quotes, which is not valid JSON. It has to be plain double quotes. So the issue is either 7.result is empty when mapped into the json field, or the string is not real JSON because of the quote characters.
Ethan Marcellus- Automation Expert at Tuesday Wizard | Top Make Solution Partner | Make Community Contributor
Your JSON itself looks valid. The error suggests Parse JSON is not actually receiving a value in its json field. In Make, this usually happens when the mapped token is empty/null at runtime even if the output bubble looks correct. Try storing {{7.result}} in a Set variable first, then map that variable into JSON > Parse JSON. Also ensure the Text Parser output contains only raw JSON with no extra text/line breaks. If needed, use parseJSON({{7.result}}) directly in the next step instead of the Parse JSON module.
Thanks everyone for jumping in on this. Wanted to close the loop on what we found.
Ethan, you nailed it — the curly quotes were the root cause. The Text Parser Replace module was outputting curly apostrophes and curly double quotes that look fine in the output bubble but break JSON Parse completely. We added additional Text Parser Replace modules upstream to strip out curly quotes, curly apostrophes, em-dashes, and asterisks before the JSON ever reached the Parse module. Once the string was clean straight-quote JSON, the BundleValidationError disappeared.
Devtrest, your suggestion to store the result in a Set Variable first was also helpful as a diagnostic step — it confirmed the value was actually passing through, which helped us isolate the character encoding as the real issue rather than a mapping problem.
Stoyan, appreciate you offering to dig in as well.
For anyone finding this thread later — if you’re getting BundleValidationError on JSON Parse even though your output bubble looks valid, check your quote characters first. Curly quotes will kill it every time.