Webflow Integration: Publish Content Agent Articles to a CMS Collection

Once connected, the ReddGrow content agent publishes articles and FAQ blocks into a Webflow CMS collection, typically a Blog Posts collection, creating, updating, and retracting items as needed. Because Webflow's API doesn't return live page URLs, you also tell ReddGrow the URL path the collection is published under.

Requirements

• A Webflow site on a plan with CMS enabled (Starter, Basic, CMS, or Business)
• Site Administrator access (only site administrators can see the API access section)
• An existing CMS collection to publish into

Webflow enforces API rate limits of 60 requests/minute on Starter and Basic plans, or 120 requests/minute on CMS and Business plans.

Get your credentials

1. Open your site in Webflow and go to Site settings
2. Select Apps & integrations in the left sidebar
3. Scroll down to the API access section. This only appears for site administrators
4. Click Generate API token and give it a name, e.g. ReddGrow
5. Grant the token CMS read and write scope, and also Sites: publish if you want new items to go live immediately instead of landing as CMS drafts
6. Click Generate, then copy the token immediately. It's shown once

Webflow allows a maximum of 5 tokens per site, and tokens expire automatically after 365 days of inactivity.

Collection ID: open the target collection in the Webflow Designer, open its settings, and copy the collection ID shown there.

Connect in ReddGrow

1. Go to Settings → Integrations
2. Under Website publishing, find the Webflow card and click Connect
3. Fill in the form:
   • Site URL: your site's full https:// address
   • Site token: the API token you generated above
   • Collection ID: the ID of the CMS collection to publish into
   • Path prefix (optional): the URL folder the collection is published under, e.g. /blog. Webflow's API doesn't return live URLs, so ReddGrow uses this to build page links.
4. Click Connect Webflow

If another platform is already connected, ReddGrow warns you that connecting Webflow will replace it. Only one website can be connected at a time.

Troubleshooting

I don't see an API access section under Apps & integrations

Only site Administrators can see and generate API tokens. Ask a site administrator to either generate the token for you or grant you administrator access.

Connecting fails with a 401 or 403 error

The token is either missing the CMS read/write scope, or it expired after 365 days of inactivity. Generate a new token with the correct scopes and reconnect.

Published articles don't show up as live on the site

The token needs the Sites: publish scope to push CMS items live automatically. Without it, items save as CMS drafts and need a manual publish inside Webflow. Regenerate the token with that scope added.

Connections start failing with rate-limit (429) errors

Starter and Basic plans cap out at 60 requests/minute, CMS and Business at 120. This is rare in normal use but can happen during a burst of edits. Wait a minute and retry. The content agent doesn't need to be told to retry manually, it will pick back up.

Articles are landing in the wrong place, or path prefix looks wrong

Double-check the Collection ID against the Designer and confirm the Path prefix matches that collection's actual live URL folder. A mismatch here only affects the links ReddGrow shows you, not what Webflow stores, but it's worth fixing so links are accurate.

---

Related: see the ReddGrow App guide for how campaigns, drafts, and the platform's automation pipeline fit together.