Publish articles straight to Webflow.
Citapult creates a published item in your blog collection for each article, uploads the images to the site's assets and updates that same item when you change the article later.
Updated
What you need
- A Webflow site with a CMS collection for the articles that has a rich text field.
- No required fields in that collection beyond the ones Citapult fills. The table below lists them.
- Access to the site's Site settings to create an API token.
Set it up
1. Create an API token
In Webflow, open the site's Site settings, then Apps & integrations → API access, and generate a token. It needs read and write access to CMS and Assets and read access to Sites. A token belongs to exactly one site.
2. Add the integration
In Citapult, open Settings → Integrations, pick Webflow under “Type” and paste the token into “API token”. Under “Collection”, enter the collection's name, like “Blog Posts”. You can leave it empty if only one collection has a rich text field or only one is named like Blog, Posts or Articles. When you click “Add”, Citapult checks the token and matches the fields. The collection stays fixed after that.
3. Insert the SEO fields
Citapult fills fields like “Meta Title” and “Summary”, but Webflow only uses them as the SEO title and meta description once you insert them: in the Designer, open the collection page's settings and add the fields under SEO settings. You do this once per collection.
4. Publish an article
Open a finished article and click “Publish”. The item goes live right away, without publishing the whole site again. Below the button you see whether Webflow took it.
5. Optional: publish automatically
Turn on “Publish automatically” under Integrations. Articles marked “Needs review” then go out to all integrations on their scheduled day without a click. You set the time in the calendar under “Schedule”.
Which fields Citapult fills
Citapult recognizes fields by type and name. If several image fields or several text fields match, it fills all of them. JSON-LD isn't sent.
| Citapult | Webflow field |
|---|---|
| Title | Name |
| Slug | Slug |
| Article text | The rich text field, preferring one with Body or Inhalt in its slug or name, then Content or Text |
| Featured image | Image fields, except ones like Author, Avatar, Portrait or Logo |
| Meta description | Text fields like Summary, Excerpt, Description, Teaser or Intro |
| Meta title | Text fields like Meta Title or SEO Title |
| Images in the text | The site's assets. Images you added yourself from another address stay linked there. |
When you change an article
Edit a published article and its status goes back to “Needs review”. “Update” sends the new version to the same item.
- A live item is updated live. If you turned it into a draft or archived it in Webflow, it stays that way.
- If you deleted it, Citapult creates it again.
- A featured image, meta description or meta title you set only in Webflow stays. If you remove one in Citapult that Citapult sent before, Update clears it in Webflow too.
Good to know about Webflow
- Citapult writes to the site's primary locale. If you use Webflow Localization, articles in other languages land there too.
- YouTube videos become Webflow's own video block.
- Webflow empties code blocks in a rich text field, so Citapult sends them as a paragraph of code with line breaks.
- Webflow doesn't accept images over 4 MB.
- If you change the collection's fields in Webflow, click “Test” next to the integration. That matches the fields again.
Removing the integration
The items stay in Webflow. If you add the integration again later, Citapult won't recognize them: sending again fails on the slug that's already taken until you delete the old items in Webflow or change their slug.
Errors and questions
“Checking with Webflow failed (HTTP 401 …)” or HTTP 403
HTTP 403Webflow rejected the token, or it lacks permissions. Create a new one with read and write access to CMS and Assets and read access to Sites.
“Name the collection the articles go into: …”
Several collections have a rich text field, posts and authors for example. Enter one of the names listed under “Collection”.
“Webflow has no collection ‘…’ with a rich text field.”
No collection with that name or slug has a rich text field. Enter the name exactly as in Webflow, like “Blog Posts”, or leave the field empty.
“… has required fields Citapult can't fill: …”
Those fields are required in Webflow, but Citapult has nothing for them, a category or an author reference for example. Make them optional in the collection settings, then click “Add” or “Test”.
“Use the API token of a single site …”
The token reaches several sites or none at all, for example because it's a workspace token. Create it in the Site settings of that one site.
“The token belongs to the site …”
While editing, you pasted the token of another site. An integration stays with its site; for another one, add a new integration.
An error with HTTP 400 when publishing
HTTP 400 when publishingUsually a field changed in Webflow: it was renamed, deleted or made required. Click “Test” next to the integration so Citapult matches the fields again, then publish once more.
“Webflow already has an item with the slug …”
The collection already has an item with this slug that Citapult didn't create. Delete it or change its slug there. As long as no integration has the article or is creating it, you can change its slug in Citapult instead.
Google doesn't show the meta title from Citapult
Webflow uses whatever the collection page's SEO settings say as the SEO title. Insert the “Meta Title” field and the summary there, as in step 3.