Connect Webflow to the Spectersync webapp

You want to edit your Webflow CMS the way it should be editable — open the whole archive at once, run an AI recipe across every blog post or case study, review the changes as a diff, and publish back to the live site. Before any of that happens, you connect Webflow to Spectersync in the browser. This guide walks the exact OAuth flow, what happens at each step, and what to do when you have more than one Webflow site. Webflow support is in beta — solid for editorial CMS work, with a few edges noted below. Subscribe now and your workspace opens with 500 free credits.

What “connecting” actually means on Webflow

Webflow OAuth is account-level, not site-level. You authorize Spectersync once against your Webflow account, and during that approval screen you pick which sites Spectersync is allowed to read and write. There’s no site handle to type and no Designer secret to paste. The whole flow runs through Webflow’s hosted approval screen.

When you connect, Webflow hands Spectersync an access token scoped to sites:read cms:read cms:write — exactly the surface needed to read your CMS and publish edits back. Everything else (the Designer, components, interactions, custom code, forms, Memberships, Webflow Ecommerce) stays invisible to the app. The full breakdown is in the What Spectersync sees section at the bottom of this guide.

The connection flow, step by step

1. Start the flow

In the Spectersync workspace, choose Webflow and click Connect Webflow site. This starts a server-side OAuth flow that mints a short-lived state token and redirects you to Webflow’s authorization screen. No tokens travel through your browser URL.

2. Approve Spectersync in Webflow

You’ll land on Webflow’s standard authorization screen. This is Webflow’s own page, not ours. You’ll see:

• The app name (Spectersync) and developer
• The exact scopes being requested: sites:read, cms:read, and cms:write
• A list of your Webflow sites and a way to pick which ones Spectersync can access

Pick the sites you actually want to sync — you can always add more later by re-running the flow. Hit Authorize app. Webflow mints the access token and redirects you back.

3. Pick collections to sync

Once the handshake completes, Spectersync lists the sites you authorized and the CMS collections inside each one. Pick which collections to sync — typically the editorial ones (Blog posts, Case studies, Guides, Authors) rather than every utility collection. Each collection item opens as clean, editable content: the item name, slug, draft / published / archived state, rich-text body, reference fields, image fields by URL, and the per-collection SEO fields the collection exposes. From here you can edit a single item by hand or run a recipe across the collection, review the diff, and publish back.

Reauthorizing (when the handshake breaks)

If the connection ever ends up in a weird state — token revoked, scopes changed, a site moved between Workspaces — the fix is the same: revoke and reauthorize.

1. In your Webflow dashboard, go to Workspace → Apps & integrations → Authorized apps, find Spectersync, and click Revoke. That immediately invalidates the access token on Webflow’s side.
2. In your Spectersync workspace, remove the connection from the connected-sites list.
3. Run the flow again.

This is also what to do if you ever suspect a token has been exposed. Webflow’s tokens are long-lived and non-expiring — revoke and reauthorize is the rotation.

If the handshake fails partway through (the browser stalls on the redirect, or you see an error after approving in Webflow), the connection-failed troubleshooting guide walks the common causes.

Connecting multiple sites and Workspaces

A single Webflow account can own a flagship site, a marketing micro-site, and a help center — and Spectersync handles all three from one connection. During the approval screen, just authorize every site you want to sync.

For sites that live in different Workspaces, you’ll need to run the OAuth flow once per Workspace, since Webflow’s authorization screen is Workspace-scoped. Each Workspace becomes its own connection in your workspace, with its own access token.

What you’ve actually given Spectersync

It’s worth being explicit, because Webflow’s approval screen flashes past quickly. You’ve given Spectersync:

• Read access to the list of sites in your Workspace (sites:read)
• Read and write access to the CMS — collections and items — on the sites you authorized (cms:read, cms:write)

You have not given Spectersync access to the Designer, page structure, components, interactions, custom code, forms, Memberships, Webflow Ecommerce orders / products / inventory, or any other surface of Webflow. That’s not policy on our side — it’s enforced by Webflow, because those scopes were never requested.

Once you’re connected, the rest of the workflow on Webflow — bulk SEO sweeps, meta description passes, CTA inserts across every blog post — runs the same way it does on any connected CMS.

Prefer the desktop edition?

If you’d rather run the engine locally — your CMS items as plain .md files on your Mac, edited with Obsidian, Claude Code, or your own scripts, the OAuth token stored in the macOS Keychain and nothing routed through our servers — that’s the desktop and open-source edition. The hosted webapp is the fastest way in. Subscribe now →