Hey Lukas, thanks for sharing-
I’m in the middle of upgrading Sygnal’s templatting and data-binding libs so your use case caught my interest.
In general, Webflow’s hosting solution avoids building pages dynamically as much as possible, because that massively increases the server costs and complicates CDN deployment. Even simple dynamics like randomizing a collection list only refreshes every 12 hours.
But you can accomplish this kind of template + content meld effectively on either side of the page build.
CLIENT-SIDE
You can deliver the page with your { variable }
template, retrieve your data and then process the template using client-side js. Handlebars or mustache are good for template processing, and give you a nice bridge between JS objects and HTML.
My agency has our own custom solution for this because we commonly need to integrate a range of different datasources- CMS data, plus external data. However it’s client side which means we don’t integrate with secure APIs from the client. Instead we push that data into the CMS or another DB securely and access it from there.
Is your API request to a public, unsecured API? If so, you could use that same approach here.
SERVER-SIDE
Have a server-side process that composes your rich text content, and then syncs it to Webflow through the API. For a lot of teams, AirTable is the go-to here since it has an easy interface and scripting support. For the sync, powerimporter pro or whalesync are popular, or you could build something custom particularly if it’s a one way AirTable → Webflow CMS sync.
This gets you 90% of the way there, however if your API data needs to be more real-time, you may still need to handle that piece client-side.
HYBRID
Obviously you can mix these approaches to suit your use case, but one good direction you might look is Wized + Xano. Together they are the closest thing you’d get to Bubble-like nocode functionality on a pixel-perfect Webflow hosted site.