Webflow API pasting HTML from parseJSON

Questions
,
1

:bullseye: What is your goal?

I want to use the “Make API Call” Module for Webflow to import blog posts to multiple localizations. I have a Parse JSON Module before it that splits up my original input into different items (Title, Meta Tile, Actual Blog post etc.).
For some reason the parseJSON module seems to break my Blog post into multiple lines. This then leads to a “400 Invalid Body” Error in the Webflow API.

:thinking: What is the problem & what have you tried?

I can not get the Input Blog Article into a formatting that it would be accepted by the Webflow API for the Rich Text element.

3

Hey @Philip_Stapmanns

The issue is that Parse JSON is breaking your rich text content at line breaks, but Webflow’s Rich Text API expects specific formatting. Here’s the fix:

The Problem:
Webflow Rich Text uses a structured format, not plain text with line breaks. When Parse JSON splits content by lines, it breaks the required structure.

Solution 1: Text Aggregator After Parse JSON
Add a Tools > Text Aggregator module after Parse JSON:

  • Source Module: Parse JSON
  • Text: {{content}}
  • Row separator: \n or leave empty
  • This reassembles your content into a single string

Solution 2: Proper Rich Text Format
Webflow Rich Text expects this structure:

{
  "blocks": [
    {
      "tag": "p",
      "text": "Your paragraph text here"
    },
    {
      "tag": "h2", 
      "text": "Your heading text"
    }
  ]
}

Solution 3: Replace Line Breaks
In your Webflow module, use:

{{replace(parseJSON.blogContent; newline; "<br>")}}

Or for paragraphs:

{{replace(replace(parseJSON.blogContent; newline + newline; "</p><p>"); newline; "<br>")}}

Quick Debug:
Test your Parse JSON output first by sending it to a simple webhook to see exactly how it’s structured. Then format accordingly for Webflow’s requirements.

Most likely you need Solution 1 (Text Aggregator) to reconstruct the content before sending to Webflow.

Sam @ Flow Digital
Sr Automation Specialist

4

Hi Sam,

thanks for your reply! My mistake was that I wasn’t using the built in “newline” in my search querry.
However I am still struggling with proper formatting. The automation works in about 20% of cases now. I think the other 80% are due to invalid JSONs because of not correctly escaped special characters. Is there any way in make to handle this more or less automatically?
First time working with JSON inside of make…

Thanks!