RSS to Webflow CMS: Import Feed Items Into a Collection

Updated: 2026-09-28

Short answer: create a Site API token in Webflow with the cms:read, cms:write and sites:read scopes and paste it into PostRSS under Accounts → Add new Webflow CMS account. Open Targets → Add feed, choose Webflow CMS in Target settings, pick the site and the collection, and map which collection fields receive the body, the image and the summary. Then add your feed under Add source (Type = RSS feed, Link = your feed address). Each new item becomes a CMS item, published live or saved as a draft. Webflow CMS is included from the Professional plan.

Webflow is a design tool with a CMS attached, and the CMS is where the friction usually shows up. The site looks exactly as intended; getting content into it means someone opening the Designer or the Editor and filling in fields by hand. For a marketing site updated occasionally that is fine. For anything fed from elsewhere — a blog on another platform, a product feed, a partner's articles — it becomes the bottleneck.

Field mapping is the part worth getting right

Unlike a social network, a CMS collection has a shape you defined. A Blog Posts collection might have Name, Slug, Post Body, Main Image, Summary, Author and half a dozen switches. A feed item has a title, some HTML, an image and a date. Connecting the two means deciding which feed value goes into which field, which you do once in Target settings: the body, the image and the summary each get a destination.

Spending two minutes on that mapping is the difference between items that render correctly and items that appear in the collection with an empty layout. It is also worth checking the collection for required fields before you start. A required field that nothing maps to will stop items being created, and the symptom looks like a broken connection rather than a schema problem.

Setting it up, step by step

1. In Webflow, create a Site API token with the cms:read, cms:write and sites:read scopes. Anything narrower will fail when PostRSS tries to create an item.
2. In PostRSS, open Accounts and choose Add new Webflow CMS account. Paste the token. It is scoped to the site it was created for, so a token for the wrong site will not see your collection.
3. Open Targets and click Add feed. One feed going to one destination is one Target.
4. In Target settings, choose Webflow CMS and the account you just connected. Pick the site and the collection, map the fields, and choose whether items are published live or saved as drafts.
5. Click Add source. Set Type to RSS feed and paste your feed address into Link. Save.
6. Check the first item that arrives. PostRSS checks the feed every 5 minutes (every minute on Enterprise plans), so the wait is short.

Live or draft

Webflow distinguishes between a CMS item that exists and one that is published to the live site. PostRSS lets you choose: items can go live as they arrive, or land as drafts for someone to check and publish.

Drafts are the safer default while the mapping is new, particularly because Webflow layouts are unforgiving — a body field carrying HTML your rich-text element does not expect will look wrong on a designed page in a way it never would on a blog. Review two or three, adjust the mapping, then switch to live if you want it unattended.

What this is good for

• A Webflow marketing site with the blog elsewhere. Common when the blog runs on WordPress or Ghost for editorial reasons but the design lives in Webflow.
• Product or listing feeds. Anything that produces a structured feed — jobs, properties, events — can populate a collection instead of being retyped.
• Multi-site publishing. One source feed can fill collections on several Webflow sites, each with its own Target and mapping.
• Syndicated or partner content. With drafts on, the collection becomes an inbox an editor works through.

How this compares to the alternatives

• Webflow's CSV import. Good for a one-off migration, useless as a pipeline: you run it by hand, and it is finished.
• A Zapier or Make scenario. Workable, and it puts the field mapping, the image handling, the de-duplication and the per-run cost on you.
• A script against the Webflow API. Total control, plus token rotation, retries and the day an endpoint changes.
• Doing it by hand. Genuinely the right answer for four posts a year, and the reason most Webflow blogs are three months out of date.

What it does not do

PostRSS publishes items that appear in the feed after the Target starts running. Connecting an established feed does not import its back catalogue, which is deliberate — the alternative is a destination flooded with years of archive on day one.

It does not design your collection, create fields, or publish the site itself beyond the item-level live setting. The template is yours; PostRSS fills it.

Which plan includes it

Webflow CMS is included from the Professional plan. Each destination you connect counts as one Target, and your plan sets how many Targets and how many posts a month you get. An annual subscription is cheaper than paying monthly. The current limits for every tier are on the pricing page, and the full list of 66 networks is on the supported networks page. The Webflow CMS page has the short version.

Troubleshooting

• The token is rejected. Check the scopes. cms:read, cms:write and sites:read are all required, and a token missing any of them fails at item creation.
• Items are not created at all. Look for a required field in the collection that nothing is mapped to. Webflow refuses the item, and the failure looks like a connection problem.
• Items appear but render badly. The body field is probably receiving HTML the rich-text element does not expect. Re-check the mapping and the source feed's content.
• The image is missing. The feed item has none, or it is not mapped to the image field.
• The wrong site or collection. A Site API token only sees the site it was created for; generate one on the correct site.

Getting the source feed right first

More Webflow imports go wrong at the source than at the mapping. Three checks before you connect anything:

• Full content, not summaries. If your feed ships excerpts, the body field receives excerpts. Nothing downstream can restore text the feed never sent.
• An image in the item. The picture has to be in the feed — in the item content or as an enclosure — not merely on the page the item links to. Many WordPress themes show a featured image without putting it in the feed.
• A usable summary. If your collection has a summary or excerpt field, check the feed actually carries a description. Where it does not, either map the field to something else or leave it unmapped rather than letting it block creation.

A note on slugs and duplicates

Webflow generates a slug for each item from the name. Two feed items with the same title — a weekly "Release notes" post, for example — produce two items whose slugs collide, and Webflow resolves that by appending a suffix rather than by failing. It is not a problem, but it is worth knowing before you conclude something has gone wrong, and it is a small argument for titles that carry a date or a version number.

De-duplication on the feed side is handled for you: PostRSS tracks which items it has already sent, so a feed that rebuilds itself or reorders entries does not produce repeats in your collection.

Frequently Asked Questions

Which Webflow token scopes are required?

A Site API token with cms:read, cms:write and sites:read. A token missing any of the three will connect but fail when it tries to create an item.

Can I choose which collection fields receive the feed content?

Yes, and you should. The mapping is set once per Target and decides which fields get the body, the image and the summary. Check the collection for required fields first — one with nothing mapped to it will block item creation.

Do items go live immediately?

Only if you choose that. The Target setting lets each new item publish live or land as a draft for someone to review, which is the safer option while the mapping is new.

Can one feed fill collections on more than one Webflow site?

Yes. Each site-and-collection pair is a separate Target with its own token and mapping, and the same feed can be a source on all of them.

Is this the same as Webflow’s CSV import?

No. CSV import is a one-off migration you run by hand. This is a pipeline: new feed items become collection items as they appear, without anyone opening Webflow.

Will my existing articles be imported when I connect a feed?

No. PostRSS creates items for feed entries that appear after the Target starts running, so connecting an established feed does not backfill your archive into the collection.

The bottom line

Webflow CMS is the destination where the setup rewards a couple of minutes of care: get the token scopes and the field mapping right, start with drafts, and a collection that used to be filled by hand fills itself. It is included from the Professional plan.