Specter for Webflow Beta

Edit your whole Webflow CMS with AI, in your browser.

Connect your Webflow site in the browser and the CMS collections you choose open as clean, structured content — blog posts, case studies, any collection item. Run AI recipes across the whole archive, review each change as a diff, and Specter publishes back through the Webflow Data API. CMS collections only — never the Designer, your site structure, or your e-commerce.

Any Webflow plan with the CMS · nothing to install · browsing & diffs are free · workspaces open with 500 free credits.

Also for: Ghost →  ·  WordPress →  ·  Shopify →

Why Webflow operators reach for Specter

The Webflow Editor opens one CMS item at a time

Webflow's CMS is built for craft — a designer builds the template once, and the Editor lets a writer fill in one item at a time. That's fine for a launch and painful at scale. The Webflow AI Assist is fine for a paragraph, useless across a hundred posts. The Data API is honest and rate-limited. Specter takes a different angle. Connect your site in the browser and your CMS items open as clean content. Run AI recipes across the whole archive, review every change as a diff, and publish back through the Webflow Data API.

What you can do

The workflow layer between Webflow and AI

Specter isn't an AI and it isn't a CMS. It's the workflow and control layer: connect your live Webflow CMS in the browser, run AI recipes across the whole archive, and review every change before it ships — so the model can finally reach your content, all of it, at once.

Full-archive context for AI

Connect your Webflow site and every item in the collections you choose lands in one workspace as clean, structured content. AI recipes run with the whole archive as context — accurate internal links, consistent tone, no blind one-item rewrites.

Bulk SEO across every collection item

Run an AI recipe across hundreds of CMS items — rewrite SEO titles, regenerate meta descriptions, swap CTAs, refresh stale copy. Review the pass as a diff, approve what is right, and publish back over the Webflow Data API.

Everything in one workspace

Webflow sits side by side with Ghost, WordPress, and Shopify. Run the same recipe across more than one platform, review each, and publish back — from one place.

Recipes, not one item at a time

AI runs as recipes across your connected content, not pasted item-by-item into a chat window. The whole collection is the context — and you review every change as a diff before publishing.

Two-way sync

Edit in your workspace and the change publishes back. Edit in the Webflow Editor and Specter pulls it in. Each CMS item round-trips with its frontmatter: slug, name, published state, reference fields, rich-text body, and the SEO fields the collection exposes.

Dry-run diff before you publish

Every run shows up as a diff first — which Webflow items would be created, updated, or flagged as conflicts. Browsing and reviewing diffs are free, and every publish keeps a snapshot for rollback.

OAuth, scoped to the CMS only

Specter requests sites:read cms:read cms:write. Your Designer, components, interactions, and e-commerce are not in the scope. Revoke from your Webflow dashboard any time.

Credits, not lock-in

Connecting Webflow, browsing items, and reviewing diffs are free. Only AI runs spend credits, and every workspace opens with 500 free. Your content stays yours.

How it works on Webflow

Three steps. No drama.

01

Step

Authorize Specter in Webflow

Click Connect Webflow site, sign in to Webflow, and approve the install. Webflow shows you exactly what Specter will access — your CMS, scoped to the sites you authorize, nothing else.

02

Step

Your collections open in the workspace

Specter finishes the OAuth handshake and pulls the collections you authorize into the workspace as clean, structured content.

03

Step

Pick collections, run a recipe, review, publish

Choose which collections to sync (one site can have many — pick the ones with editorial content). Edit by hand or run an AI recipe across the archive, review every change as a diff, and Specter publishes back. Every publish keeps a snapshot for rollback.

What round-trips today

The Webflow capability map

Specter syncs the editorial text content of your Webflow CMS collections. The Designer, site structure, components, interactions, and Webflow Ecommerce are deliberately out of scope.

Pushes and pulls today

CMS collection items, name, slug, draft / published / archived state, rich-text body (markdown ↔ Webflow rich text), plain-text fields, number and date fields, reference and multi-reference fields by item id, image fields by URL, and the SEO fields each collection exposes (meta title, meta description, OG image, canonical).

Specter never touches

The Designer, page structure, components, interactions, custom code, site SEO outside CMS items, forms, Memberships, Webflow Ecommerce orders / products / inventory, redirects, hosting settings. CMS collections only — period. See the full capability matrix →.

Credits, not lock-in

Browsing is free. Only AI runs spend credits.

Connecting Webflow, reviewing diffs, and publishing edits cost nothing. Only AI recipe runs spend credits, and every workspace opens with 500 free.

Prefer your own machine?
Desktop
  • Run the engine locally, your items as plain .md files on disk
  • Open-source and self-hostable
  • Nothing routed through our servers
  • Desktop Core is $99/year; engine is free on GitHub
Desktop & open-source edition →

FAQ

Webflow questions, answered

Which Webflow plans does Specter work with?
Any Webflow plan that exposes the CMS — Basic doesn’t include the CMS, so you’ll need CMS, Business, or Enterprise (Site plans) or a Workspace plan that publishes to a CMS-enabled site. Specter authenticates via standard Webflow OAuth, so if you can install a Webflow App on the site, you can install Specter.
Why is this called "beta"?
The OAuth handshake, the pull, and the push for the most common CMS field types (plain text, rich text, slug, switch, number, date, image URL, reference) are all working. We’re still expanding fidelity for the less common field types and edge cases — see the capability matrix for the current state. The beta label comes off when those last edges round-trip cleanly.
Can Specter edit my Designer pages or components?
No. Specter syncs the Webflow CMS — the items inside your collections. Designer pages, component instances, interactions, and custom code are not in scope and not visible to Specter. The Designer remains the Designer’s job.
Does Specter see my e-commerce orders or customers?
No. The OAuth scope Specter requests is sites:read cms:read cms:write. Webflow Ecommerce — products, variants, orders, customers, inventory — is not in the scope and not visible to Specter. You can verify the exact scopes during install — Webflow lists them on the approval screen.
Can I revoke Specter’s access?
Any time. Specter holds a CMS-scoped OAuth token, and you can revoke it from your Webflow dashboard (Workspace → Apps & integrations → Authorized apps → Specter → Revoke) whenever you like. The moment you do, the connection stops.
What about Webflow’s rich-text editor and embedded components?
Specter converts the rich-text body between Webflow’s rich-text format and standard markdown in both directions, preserving headings, lists, code blocks, links, images (by URL), and inline formatting. Embedded components and custom HTML blocks inside rich text round-trip as opaque blocks you can keep, edit around, or rewrite — Specter won’t silently break them.
Does it work across multiple Webflow sites?
Yes. One Webflow account can authorize Specter for multiple sites — pick which sites and which collections per site to sync. Each gets its own connection and its own sync folder.
Does Specter publish to staging or to the live site?
Specter writes to the Webflow CMS, which is the same surface the Webflow Editor writes to. Your existing publish workflow (staging URL → publish to your live domain) keeps working — Specter doesn’t bypass it.

Bring AI to your whole Webflow CMS

Connect in the browser and start with 500 free credits. Prefer files on your own disk? There’s a desktop and open-source edition too.