Naxis Technologies Docs
Live demo

Websites

Set up Webflow

Connect Webflow to read the CMS itself rather than the rendered site — every item of every collection (blog posts, help articles, case studies, team pages) as clean structured content, drafts optional, so a help article or a case study answers from its own fields instead of page chrome. Read-only.

Before you start

  1. Generate the site token as above.
  2. Documents → Webflow, paste it as Site token.
  3. Optional, under Advanced: list Collections to sync only those, and set Drafts to decide whether unpublished items and staged edits come in.
  4. Choose access groups, Test, then Sync.

What comes in

CollectionsOptional, under Advanced — collection names exactly as Webflow shows them, one per line, to sync only those. Blank syncs every CMS collection of every site the token can see. A listed name that matches no collection is reported in the sync notes rather than failing the sync.
DraftsPublished items only (default) reads Webflow's live collection — exactly what visitors see. Include drafts and staged edits also pulls unpublished items and staged (not-yet-published) changes to published ones, tagged as drafts.

Access

Access is allow-only: every item this source brings in is visible to the groups you choose when setting it up — Webflow's API carries no per-item reader list to mirror.

Collections are capped at 3,000 items in total, read 100 at a time; Sync notes it if the cap is hit — narrow the Collections list if this persists — and items already synced beyond it stay searchable. A site the token can't list collections for is skipped with a note, not failed. Test lists the collections it can reach and names the first few; on failure it says why — a rejected token reports that Webflow rejected the credentials. To cut access, revoke the token where it was generated, under Apps & integrations → API access.

Was this page helpful?
Was this page helpful? Sign in with Google Sign in to tell us — or leave a comment.

Last updated 20 Sep 2026