<script type="application/ld+json">{"@context":"https://schema.org","@type":"TechArticle","headline":"Webflow connection issues","description":"Common reasons a Webflow connection breaks, and how the token setup avoids them.","dateModified":"2026-07-12","inLanguage":"en","author":{"@type":"Organization","name":"HarperFlow"},"publisher":{"@type":"Organization","name":"HarperFlow","url":"https://www.harperflow.io","logo":{"@type":"ImageObject","url":"https://www.harperflow.io/favicon.png"}},"mainEntityOfPage":"https://www.harperflow.io/docs/webflow-connection-issues"}</script>
Troubleshooting
Common reasons a Webflow connection breaks, and how the token setup avoids them.
Webflow is HarperFlow's most complete integration, and most connection problems trace back to the site API token it runs on.
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 the 14-day timeline behind it.
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.
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.