CMS integrations

Webflow

GrowGanic writes each finished article into a CMS collection on your own Webflow site, hero image and all.

A primary destination. Your article lives here and the canonical URL points at it, so this is the site Google credits. About 1 minute, in one click.

#What connecting does

Once Webflow is connected, every article GrowGanic finishes is created as an item in one collection on your site and published live. Nothing waits for your approval, and nothing needs copying across.

Your site comes from Webflow, never from a form. A Webflow grant names an account, not a site and not a collection, and the Webflow Designer does not display a Collection ID anywhere, so asking you to paste one was never a step anybody could complete. The moment you approve, we read the sites your grant covers and every collection's real field schema, and score each one against what an article actually needs. You are never asked to type a web address.

Installing from the Webflow Marketplace shows you that list and you pick the site. Your GrowGanic project is created from whatever you pick, named after the site, so there is nothing to set up first. Connecting from inside GrowGanic, where a project already exists, skips the question when exactly one collection qualifies, asks once when several do, and connects nothing at all when none can receive an article, telling you which fields are missing instead.

Webflow is the one destination GrowGanic connects through the provider's own authorization screen and nothing else. There is no API token to generate and nothing to paste, because Webflow asks every Marketplace app to use their authorization flow exclusively, and the reason is a good one: a token you paste is a secret you have to carry, while a grant you approve is one you can withdraw from your own dashboard.

Articles publish under your byline on your domain, which is the point: the ranking credit belongs to your site, not to ours.

#Before you start

A Webflow site with a CMS collection your articles belong in. It needs a name field, a slug field and a rich text body field. The default Blog Posts collection from Webflow's own blog template already qualifies.
Permission to authorize an app on that site. Webflow shows you which sites the grant will cover on its own screen, and a collaborator without CMS access cannot approve it.

#Connect

In one click

From the Webflow Marketplace, click Install. From inside GrowGanic, open Integrations and click Connect Webflow. Either way, the next thing you see is Webflow's own permission screen.
Click Authorize app and choose the sites the grant should cover. Nothing is typed and no token is ever generated.
Pick the site your articles belong to. GrowGanic lists the sites your authorization covers, reads each collection's real fields, and connects the one that can receive an article. Installing from the Marketplace always shows you that list and creates your GrowGanic project from the site you pick; connecting from inside GrowGanic, where a project already exists, skips the question when exactly one collection qualifies.

That is it. You land back in GrowGanic connected, with your blog collection already chosen, and articles publish to Webflow on their own from then on.

#Permissions we ask for

Every permission below is used by a call GrowGanic actually makes. We ask for nothing we do not use.

Permission	Used for	Why
sites:read	Listing the sites your grant covers	It is how we find your site. Without it the very first call is refused, before we see a single collection.
cms:read	Reading a collection's real field schema, and reading items back	So we only ever write field slugs your collection actually defines, and can confirm what landed.
cms:write	Creating, updating, publishing and deleting the article items	This is the publishing itself.
assets:write	Uploading the article's hero image to your site's asset library	So the image belongs to your site rather than to ours: it lives in your own asset library, on Webflow's CDN, and it keeps working if you ever stop using GrowGanic.

GrowGanic does not read your existing assets: it uploads the hero it generated for the article it is publishing, and nothing else. Webflow's app settings have no write-only option for assets, so the app is configured as read and write, but the permission you are actually asked to approve is write alone. It also asks for no access to your pages, forms, custom code, ecommerce data, site users or workspace.

#What we write

Field	What goes in it
name	The article title.
slug	The article slug, or one derived from the title.
post-body	The article body as rich text. Also accepted: body, content, rich-text, article-body, main-content, post-content.
post-summary	The excerpt. Also accepted: summary, excerpt, description, subtitle, preview.
seo-title	The meta title. Also accepted: meta-title, search-title.
meta-description	The meta description. Also accepted: seo-description, search-description.
main-image	The hero image. Also accepted: thumbnail-image, featured-image, image, hero-image, cover-image, post-image.

Fields your setup does not have are skipped rather than guessed at, and the article publishes with the ones it does have.

The hero image

The hero is uploaded into your own site's asset library and the CMS item references it by asset id, so the image your visitors load is served from Webflow's CDN as part of your own site, not hotlinked from a GrowGanic server. It stays yours and keeps working if you stop using GrowGanic. This is the only thing the assets permission is used for.

Editing an article does not upload the image again. Before an update, GrowGanic reads the item and reuses the asset already attached when it is provably the same picture, so a refreshed article does not leave a second copy of the same image in your library.

Deleting an article removes the CMS item, not the asset. Its hero stays in your asset library, the same way an image stays in a WordPress media library after the post is gone. Remove it in Webflow if you want it gone.

If the upload ever fails, the article still publishes with the image referenced from our CDN. A hero image never holds an article back.

#Publishing behaviour

A new article is created as a CMS item and then promoted live. If the promotion fails, the item still exists as a draft in your collection and GrowGanic retries rather than creating a second copy.

Editing an article in GrowGanic updates the same item. It never creates a duplicate.

Deleting an article removes the live copy first and then the staged copy. Webflow keeps two copies of every item, the staged one the Designer edits and the live one your published site serves, and deleting only the staged copy would leave the page live on your own domain forever.

You can set articles to arrive as drafts instead of publishing live, from Settings in GrowGanic. Drafts are created with isDraft set and are never promoted.

If you rename a field in the Designer mid-flight, GrowGanic re-reads the schema once and retries, rather than failing the article over a rename.

If this destination is ever unreachable, the article is not held. It publishes to your GrowGanic blog and moves here on its own once the connection is healthy again. GrowGanic never holds a finished article back waiting for you.

#Disconnect

Disconnecting stops publishing to Webflow. Articles already on your site stay published and stay yours; nothing is removed from your collection.

You can also remove GrowGanic from Webflow's side. Webflow sends no notification when you do, so we find out on the next call: it is refused, the connection is switched off, and you get an email saying it needs reconnecting. Nothing keeps calling Webflow with a token it has already refused.

The grant is deleted from our database the moment Webflow refuses it, without exception. Webflow refusing its own token is Webflow telling us the grant is over, there is no second kind of Webflow credential we could be holding, and getting the connection back is one click on Connect Webflow.

Open Integrations in GrowGanic, find this destination and click Disconnect. The stored credential is deleted from our database in the same step, not marked inactive. Articles already published stay exactly where they are, and they are yours.

#Troubleshooting

What you see	Why	Fix
The Webflow authorization is missing a permission.	One of the four permissions was not approved on Webflow's screen, or the app was authorized for a set of sites that does not include the one your articles belong to.	Click Connect Webflow again and approve Sites read, CMS read and write, and Assets write, with the right site selected.
Webflow no longer accepts this connection.	The grant was removed on Webflow's side. Webflow sends no notification when that happens, so a refused call is how we find out.	Click Connect Webflow. Nothing has to be re-entered.
The Webflow account you approved reaches no site we can publish to.	The authorization covered sites that do not include the one your articles belong to.	Connect again and select that site on Webflow's screen.
None of your Webflow collections can receive an article yet.	No collection on the site has the three fields an article needs.	In the Designer, open the collection articles should go to and add a name field, a slug field and a rich text body field, then connect again.
Your Webflow collection is missing required fields.	The collection connected fine and has since lost a field, or the wrong collection was picked.	Add fields with the exact slugs named in the message, all lowercase with hyphens, or click Connect Webflow again and pick the collection again.
Webflow collection no longer exists.	The collection was deleted or re-created, which gives it a new id.	Click Connect Webflow again and pick the collection your articles should go to.
The article is live but the hero image is not in my assets.	Assets write was not approved, so the upload was refused and the image fell back to a remote reference.	Click Connect Webflow again and approve Assets write. The next article uploads its hero normally.

Still stuck? Email hey@growganic.io and tell us the sentence you are seeing. Or read the other destinations.