autoranko

Native connector

Publish to a Webflow CMS collection

Autoranko creates items in a Webflow CMS collection through the Data API v2: the title, a slug and the article HTML in your rich-text field, staged as a draft or published to your live site.

  • About 10 minutes to connect (estimate)
  • Last verified November 8, 2026

How it connects

Webflow stores blog posts as items in a CMS collection, and every site designs its collection differently. So Autoranko needs three things from you: an API token for the site, the ID of the collection that holds your posts, and the slug of the rich-text field that receives the article body. The item name becomes the title, and Autoranko generates a URL slug from it.

When you publish live, the item is created and published to your site in one step; when you choose a draft, it’s created in the CMS without being published. Updates edit the same item and publish it again, and unpublishing takes it off the live site without deleting it from the CMS.

Set up Webflow

  1. 1

    Generate a site API token

    In Webflow, open Site settings → Apps & integrations → API access and generate a token with read and write access to the CMS. Tokens belong to one site, so create one for each site you connect.

  2. 2

    Find the collection ID

    In the Webflow Designer, open the CMS collection that holds your blog posts. The collection ID is shown in its settings panel; copy it.

  3. 3

    Note the field slugs

    Note the slug of the rich-text field for the article body (post-body in Webflow’s blog template) and, if you want featured images, the slug of the image field.

  4. 4

    Connect in Autoranko

    Add a non-WordPress site in Dashboard → Integrations, choose Webflow, and enter the token, the collection ID and the field slugs. Saving runs a connection test against the collection.

  5. 5

    Publish live or as a draft

    Approve an article and publish it. Live items appear on your site at the URL your collection template defines; drafts wait in the Webflow CMS until you publish them.

What gets published

Exactly what Autoranko sends and controls on this platform, as of the last verification date.

Capabilities of the Webflow integration
CapabilityWebflow
TitleSupported
Article body (HTML)Supported1
Meta descriptionNot supported2
Featured imagePartly3
Images in the articleSupported4
Publish as a draftSupported
Update a published articleSupported5
UnpublishSupported
Tags or categoriesNot supported6
JSON-LD structured dataNot supported7
SupportedPartlyNot supported
  1. 1.Sent to the rich-text field you name (post-body by default).
  2. 2.Collections have no standard SEO field; bind your template’s description to a field yourself.
  3. 3.Set only when you name the collection’s image field in the connector.
  4. 4.Images inside the article body may be served from autoranko.com/media when the platform can’t store them; they’re deleted 30 days after you remove the site.
  5. 5.The item is edited, then published again.
  6. 6.Reference fields such as categories and authors need IDs from your collections and aren’t filled in.
  7. 7.No JSON-LD is added; the article keeps its visible FAQ section.

Limits and honest caveats

Webflow collections have no standard SEO-description field, so Autoranko doesn’t send one: bind your collection template’s meta description to a field you fill in yourself. Reference fields such as categories and authors need item IDs from your own collections and aren’t filled in.

Featured images are set only when you name the image field. Images inside the article body are served from autoranko.com/media. Webflow doesn’t return the public URL of a new item, so the dashboard may show the item without its link. No structured data is added: the visible FAQ stays in the body.

Troubleshooting

The messages below are exactly what Autoranko shows in the dashboard or returns from the API, with what they mean and how to fix them.

Webflow returned 401: …
The token is invalid, revoked or belongs to another site. Generate a new token for this site and save it again.
Webflow returned 404: …
Webflow couldn’t find the collection. Check the collection ID, and that it belongs to the same site as the token.
Webflow returned 400: …
Webflow rejected the item. Usually the body field slug doesn’t match a rich-text field, a required field in your collection is empty, or the slug is already taken. Webflow’s message after the colon names the field.
Webflow accepted the request but returned no item id.
Webflow answered without an item ID, so Autoranko can’t confirm the publish. Check the collection in Webflow; if the item is missing, publish again.

Questions

Do I need a paid Webflow plan?+
You need a site plan that includes the CMS and API access. Check Webflow’s current plans for their CMS item and API limits.
Can I use my own collection fields?+
Yes. You choose which rich-text field receives the body and which image field receives the featured image. Other required fields in your collection need default values, or Webflow rejects the item.
Does publishing republish my whole site?+
No. Autoranko publishes the single item through the CMS API; the rest of your site isn’t touched.

Connect your site in minutes

Start on the free plan — no card — and publish your first article to your own platform.