CMS
DJINN + Webflow
CMS collections kept current from the systems that actually hold the truth.
How it connects
Collections from source data
Webflow collections drift the moment they are maintained by hand. Driving them from the source system is the fix.
Staged, then published
Changes land staged so a person sees them before the site does.
Connector spec
- Auth
- pat · webflow_v1
- Host
- https://api.webflow.com
GET v2/sites/${source.id}/collections
Emits cms_collection · incremental on lastUpdated
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live Webflow account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Documents
Webflow setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupAPI token and collection mapping
- RunbookSync and publish rules
Want Webflow wired into your own company brain?