Docs
/
Troubleshooting

Troubleshooting

Webflow connection issues

Common reasons a Webflow connection breaks, how the token setup avoids them, and why a published article can show page not found.

October 6, 2026

Webflow is HarperFlow's most complete integration, and most connection problems trace back to the site API token it runs on.

Common causes

  • The token was regenerated or revoked. Generating a new token in Webflow's Site settings, or revoking the old one, invalidates whatever HarperFlow was using. HarperFlow only ever holds the one token you gave it. It has no way to know a new one exists until you paste it in.
  • The token's permissions were narrowed. If the token no longer has read/write access to Sites, CMS, Assets, Pages, Custom code, and Components, calls that need those permissions start failing even though the token itself is still technically valid.
  • The site moved workspaces, or was deleted. A token is scoped to whatever it could see at the time it was generated; moving the site to a different Webflow Workspace or deleting it removes what HarperFlow was authorized to reach.

Any of these show up the same way: a reconnect banner on your dashboard, and publishing paused until it's fixed. See Reconnecting and token health for what that banner means and how to reconnect.

"This token cannot see any sites"

This specific message means the token you pasted is scoped to your whole Webflow Workspace rather than to one site. Generate a fresh token scoped to the individual site instead. See Connect your Webflow site for exactly which permissions to turn on.

Fixing it

Reconnecting is almost always faster than trying to repair the old token: generate a brand-new one with the same permissions as the original setup, and paste it into the reconnect flow on your Your Site page.

Tip: If you're not sure whether a token still works, generating a fresh one and reconnecting is the fastest way to rule it out. There's no need to diagnose the old one first.

An article says Published but its link shows "page not found"

The most common cause is a collection page that has never been designed. When HarperFlow creates a new collection for you, Webflow gives it an empty page, and Webflow shows "page not found" for every article in that collection until the page has at least one element. Publishing your site doesn't fix it on its own. HarperFlow tells you when this is the case: a banner on your dashboard's Home page, "Not visible on your site yet" next to the article on the Articles page, and one email per site.

To fix it, apply a free template with the HarperFlow Connector, or design the collection's page yourself in the Webflow Designer. Either way, publish your site afterwards. Step by step: Design your article page for a new collection. Then click Check again on the Home banner. Your articles are saved and appear as soon as the page is designed and your site is published.

If the page is already designed and the link still shows "page not found":

  • Your site hasn't been published since the page was designed. Publish your site in Webflow. Until then, the live site still has the old, empty page.
  • The article's address changed. Renaming the collection page's slug in Webflow changes every article's address. Open the article from your collection in Webflow to find its current link.

More in Troubleshooting

Browse all Troubleshooting guides