Integrations / Webflow
Webflow
Webflow visual CMS and website platform for managing sites, CMS collections and items, pages, forms, webhooks, and assets.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- assets:readOAuth 2.0
- cms:readOAuth 2.0
- cms:writeOAuth 2.0
- forms:readOAuth 2.0
- pages:readOAuth 2.0
- sites:readOAuth 2.0
- sites:writeOAuth 2.0
- ecommerce:readOAuth 2.0
- ecommerce:writeOAuth 2.0
- page:readOAuth 2.0
- page:writeOAuth 2.0
- assets:writeOAuth 2.0
- comments:readOAuth 2.0
- components:readOAuth 2.0
- components:writeOAuth 2.0
- forms:writeOAuth 2.0
- site_activity:readOAuth 2.0
- site_config:readOAuth 2.0
- site_config:writeOAuth 2.0
In Telara
Connect in Telara
OAuth 2.0 authorization-code connection for a Webflow App. The authorizing user selects the sites or workspace the app may access. Register every requested scope in Webflow App Development before enabling this method; an authorization URL cannot request a scope that is absent from the app configuration.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Webflow API v2 token — a Site API Token or Workspace API Token generated under Site Settings > Apps & Integrations > API access, or a manually issued OAuth2 access token (both are sent as a Bearer token; confirmed against Webflow's own OpenAPI spec, which accepts either security scheme on every operation). Most Webflow tokens are scoped to a single site or a small set of sites — optionally store site_id with the credential so it auto-fills on every call instead of the model having to supply it; call list_sites first to discover the value if it isn't already known.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API key
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Site | Partial — not every record the vendor holds is synced |
| Collection | Partial — not every record the vendor holds is synced |
| Pages | Partial — not every record the vendor holds is synced |
| Collection item | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Site | Up to 1 day | Removed records disappear on the next full sync |
| Collection | Up to 1 day | Removed records disappear on the next full sync |
| Pages | Up to 1 day | Removed records disappear on the next full sync |
| Collection item | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Site, Collection, Pages, Collection item.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty

