Publishing to Webflow

What it does

Nexus publishes articles into the client's Webflow blog collection, as drafts by default, with every field filled: title, slug, body, images, meta, excerpt, author, category, reading time and schema.

Set it up

1. ✋ The client's Webflow site admin generates a Site API token: Webflow → the site → Settings → Apps & integrations → API access → Generate API token, with CMS and Assets read + write and Sites read. It needs a paid site plan.
2. "Connect Webflow with this token: [token]." Nexus checks it and sets the blog collection when there's only one.
3. Several collections: tell Nexus which one is the blog.
4. "Check the Webflow collection fields." Nexus maps each field; ask about any it couldn't map.

Don't paste the token in a shared channel: it's a write credential.

Use it

• "Publish [title] to Webflow as a draft." Then check the draft in Webflow and publish it there, or ask Nexus to go live.
• Fix a published piece: "Update [title] on Webflow." It updates the same item.

Troubleshooting

• A field is empty in Webflow. Its collection field isn't mapped. Run the field check again.
• Category didn't set. The value didn't match a category in Webflow. Nexus lists the options.

Prompts

• "Connect Webflow with this token: [token]."
• "Check the Webflow collection fields."
• "Publish [title] to Webflow as a draft."
• "Update [title] on Webflow."

Machine twins: /help/cms-webflow.json · /help/cms-webflow.md · /help.json · /llms.txt

Reviewed 2026-10-14. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.