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, or 3 minutes by hand.
#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.
GrowGanic finds the collection for you. A Webflow token names an account, 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. Instead we read the sites your grant covers and every collection's real field schema, and score each one against what an article actually needs. If exactly one collection can receive an article, it is chosen silently. If several can, you are asked once. If none can, nothing is connected and you are told which fields are missing.
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.
- Publishing rights on that site. A token generated by a collaborator without CMS access can read the collection and then fail on the first article.
#Connect
In one click
- Click Connect Webflow. Webflow opens its own permission screen listing your sites.
- Click Authorize app on that screen. We find your blog collection on our own and ask only when more than one 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.
Or connect by hand
- Open Webflow Site settings (gear icon, top-left), then Apps and Integrations, then API access.
- Click Generate API token. Under Sites enable Read, under CMS enable both Read and Write, and under Assets enable Write so your hero images are hosted on your own site. Click Generate, then copy the token.
- Paste the token below without a
Bearerprefix. We add it automatically. - Leave the Collection ID field alone. After you paste the token we list every collection on your site; click the one articles should go to and we save its ID for you.
What you paste
| Field | Required | Where to find it |
|---|---|---|
| Site URL | Yes | Your published site address, for example yoursite.webflow.io or your custom domain. |
| API token | Yes | Webflow Site settings, then Apps and Integrations, then API access, then Generate API token. |
| Collection ID | Yes | Filled in for you by the picker under the token field. Webflow never displays this value in the Designer, so the picker is how it gets filled. |
If it will not connect
- Webflow Designer does not display Collection IDs anywhere, so the picker above is the way to fill the field. You can still paste a 24-character ID by hand.
- Your Blog Collection needs fields named exactly name, slug, and a Rich Text field called post-body (or body, content, or rich-text). Without those, articles cannot publish.
#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 the collection picker finds your site. Without it a token refuses the very first call, before you 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 on your page is served from your own domain rather than from ours. |
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 your domain. 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.
A grant you approved in one click is deleted from our database at that moment, because Webflow refusing its own token is Webflow telling us the grant is over, and getting it back is one click on Connect. A site API token you pasted is kept instead, because a refused call does not prove a pasted token is gone and clicking Test is how a connection repairs itself with nothing re-entered. Disconnect if you want a pasted token removed.
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 |
|---|---|---|
| Webflow token is missing scopes. | The token was generated without one of the four permissions. Sites read is the one most often missed, because the first call the picker makes is the one that needs it. | Regenerate the token with Sites read, CMS read and write, and Assets write all enabled, then paste it again. |
| Wrong Webflow API token. | Webflow refused the token outright. Usually a partial paste, or a token from a different site. | Generate a fresh token on the site your articles belong to and paste the whole value. Leave off any Bearer prefix; we add it. |
| That token reaches no Webflow sites. | Site API tokens are scoped to the site they were generated on, and this one covers none we can publish to. | Open the settings of the site your articles belong to and generate the token there. |
| 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 clear the Collection ID field and pick the collection again. |
| Webflow collection not found. | The collection was deleted or re-created, which gives it a new id. | Clear the Collection ID field, click Find my collections and pick it again. |
| The article is live but the hero image is not in my assets. | The token is missing Assets write, so the upload was refused and the image fell back to a remote reference. | Regenerate the token with Assets write enabled and reconnect. The next article uploads its hero normally. |
Still stuck? Email [email protected] and tell us the sentence you are seeing. Or read the other destinations.