Hey everyone! I've been using Copy.ai for a few months now to speed up blog and landing page content creation. It's great for generating ideas and drafts.
But I'm hitting a wall getting those drafts *into* our actual Webflow CMS efficiently. Right now, it's a lot of copy-paste and reformatting. Has anyone set up a smooth integration between Copy.ai and WordPress, Webflow, or another CMS? I'm curious about your workflow, any automation tools you used (like Zapier or Make), and if you ran into hiccups with formatting.
Would love to hear what's actually working for people in production!
Happy customers, happy life.
I feel your pain! That copy-paste shuffle from Copy.ai into Webflow's editor got old real fast for me too. I ended up using a Make (formerly Integromat) scenario that's been pretty solid for months now. It watches a specific Google Drive folder where I save my final Copy.ai drafts as plain text files.
Here's the basic flow:
1. I write in Copy.ai, do my edits, then save the final version as a `.txt` file to my "Webflow Uploads" Drive folder.
2. Make picks it up, uses a little script to clean up line breaks (Webflow's rich text field can be finicky), and posts it as a new draft item via the Webflow CMS API.
3. It even maps the filename to the title field!
The main hiccup was formatting. If you use any markdown-like symbols in Copy.ai (like asterisks for bold), you'll need a step to convert those to HTML tags. I built a simple JS code block in Make for that. It's not perfect for super complex layouts, but for standard blog posts with headers and bold text, it saves me hours.
Have you looked into whether you're using the Webflow API or their built-in Zapier integration? The API gives you more control for stuff like this.
Backup first.
That copy-paste phase is a universal pain point when you start scaling content ops. I went through a similar integration grind, but with WordPress and a different AI tool. The core issue isn't the AI platform, it's the CMS API's formatting expectations.
You can get a Make/Zapier flow working, but you'll spend more time building the "clean-up" transform module than the actual connection. Webflow's rich text editor is particularly brittle with inline HTML. If Copy.ai outputs any markdown or stray HTML tags, it'll break or look wrong. You need a strict intermediate format, like pure HTML with a very limited tag whitelist, before the API call.
Honestly, for Webflow, I found it less frustrating to use their built-in Collections CSV import. Structure your Copy.ai output into a CSV template, run a simple script to sanitize it, and do a bulk import once a week. It's a batch process, not real-time, but it avoids the constant formatting fights.
Been there, migrated that