Connect Webflow to cmo.so

Every Webflow site structures its CMS differently, so the collection has to be mapped once. We do that with you; after that it runs like any other connection.

Your part takes about 15 minutes: create a Site API token with CMS and Assets access, then bind one Collection page in the Designer and publish. In between, we connect the token and create a Resources collection, or map your existing one. From then on, articles wait in Posts → Ready for your OK like on any other platform, and each approved one becomes a published item with its own page on your site.

Yes. Instead of creating a Resources collection, we map your collection's fields (name, slug, excerpt, body and image) once.

For example, if your CMS already has a Blog Posts collection, we map its fields and your existing template page shows Maggie's articles in the same design. Maggie only fills the fields; your Collection page decides how each article looks. Featured pictures are uploaded to your Webflow assets and then added to the item. Note that if you delete an item, Webflow keeps its slug reserved.

Webflow can only publish collection items once a Collection page exists for that collection and the site has been published. Bind the page's title, picture and body to the collection's fields in the Designer and publish once.

In the Designer's Pages panel, open the collection's Template page under CMS collection pages. Bind a heading to Name, an image to Featured image and a Rich Text block to Body. Duplicating your existing blog post page is a quick alternative. Then press Publish, tick your domain and press Publish to selected domains. You only do this once; after that, each approved article is published as its own page.

Never paste it into a chat. Contact us from the Contact page or ask Maggie to talk to a person, and we'll arrange a secure way to receive it.

Webflow shows the token only once, so keep it somewhere safe before pressing Hide token forever. Give it CMS and Assets read and write access and leave the rest as No access. Webflow tokens expire after 365 days without use. If that happens, we'll ask you for a new one in the same safe way.

New connections start at one article a day. You choose Posts per day in Publishing settings, up to your plan's limit: 1 before a plan, then 2 (Air), 12 (Pro), 24 (Max), 48 (Ultra) or 96 (Elite).

Each delivered article uses one post from your monthly allowance, and the app shows what's left. Turn Publishing off and written articles simply wait in order.

Yes. Open it in Posts → Ready: switch between Preview and Edit, change any words and Save. Rewrite asks Maggie for a new version with your note, Fix Markdown tidies the formatting, and Publish now sends it straight away on connections that support it.

Ideas for future articles sit in Posts → Ideas, where you can add your own, reorder the plan or delete any you don't want.

If you want her to. In Publishing settings, Refresh older articles can be Off, When I ask or Automatic. Automatic uses a share of each day's posts (10 to 50%) for rewrites of articles older than 30, 60, 90 or 180 days.

Rewrites keep the same address, so links and search history stay; the Rewrite queue in Me shows what's suggested and what has been rewritten, and Search Console data steers which articles need it most.

When it's on, the content guard reads each post before it goes out and checks it against your industry's rules (financial, medical, insurance, legal or education) and any rule you write yourself, such as never naming a competitor.

A post that may break a rule is held, as a draft on your website or in Review for social, with the reason and a suggested rewrite, even if posts normally go out on their own. You can see what it held and why in Publishing settings.

Yes, and that's how it starts. New posts wait in the app (Posts → Ready for articles, Social → Review for social posts) until you approve them. You can edit any post, ask Maggie to change it in your own words, or delete it.

When you trust the results, switch the channel to go out on its own; the content guard keeps checking each post first and holds anything it isn't sure about. You can switch back, or pause, at any time.

Your brand profile and the first drafts are ready within minutes of entering your website, and the first posts can go out the same day once you approve them.

Search traffic builds over weeks to months as Google and AI assistants find and trust your pages; social reach grows with regular posting. Connect Search Console to see which posts bring clicks, and Maggie uses it to choose what to improve.

Verifying proves the website is yours. It unlocks your 30 free posts and, for some connections, publishing itself. You can verify with a work email at your domain, a DNS TXT record (one tap if your domain is on Cloudflare), the WordPress plugin, or by asking us to check by hand, usually within one working day.

Free email addresses such as Gmail or Outlook can't be used for the email check.

Yes. Everything on this page works in the cmo.so app on iPhone and on the web at app.cmo.so: connecting, approving, editing and pausing.

You can also ask Maggie from ChatGPT or Claude through the cmo.so connector, for example to see what's waiting for you or to change a post, and she shows a card before she changes anything.