Webflow

Connecting a site

Authentication uses a Webflow Site access token (Site settings → Apps and integrations → API access in Webflow) — Webflow OAuth apps are not supported in this release.

Generate the token with assets:read, assets:write, cms:read, and cms:write scopes; a token without these scopes will fail verification with a permission error.

After connecting, select which Webflow site the connection targets from the sites your token can access — a connection targets exactly one site at a time.

New connections start pending and must pass a verification check (a valid token and confirmed access to the selected site) before they can publish.

Mapping CMS fields

Before publishing, an owner or admin must map an existing Webflow collection: choose the collection, discover its live field schema, and assign one Image field (required) plus optional PlainText/RichText fields for alt text, title, caption, and description.

Img Pilot never creates a collection or a field — mapping only binds a publish job to fields that already exist in your Webflow site.

If a mapped field is later renamed or removed in Webflow, the mapping is marked stale and must be re-mapped before new jobs can use it; jobs already queued against the old mapping fail safely instead of writing to the wrong field.

What publishing does

Publishing searches for and selects an EXISTING CMS collection item in your Webflow site, uploads the image's active derivative (or the original, if no derivative is selected) as a new Webflow asset, and updates only the mapped fields on that item — it never creates a collection or a CMS item.

Every publish is verified by re-reading the asset and the CMS item back from Webflow after the update; partial failures (e.g. the asset uploaded but the CMS update failed) are reported separately from full failures.

Assets are never re-uploaded once a remote asset id exists — retries resume from the CMS update/verification step.

Images over Webflow's 4 MB asset limit are rejected before any upload is attempted.

What publishing does not do

Img Pilot never creates, edits, or deletes Webflow collections, CMS items outside the one you selected, or Designer/layout elements — only the mapped fields on the CMS item you chose are touched.

Updating a CMS item's fields does not publish your live Webflow site — Webflow may require a separate, explicit site publish (from within Webflow) before the change is visible on your public domain. Img Pilot never triggers a site-wide publish.

Nothing is ever deleted remotely on your Webflow site by this integration; disconnecting a connection only stops future publishing and destroys the locally stored access token — assets and CMS field values already published to Webflow remain untouched.

The Site access token is encrypted at rest and is never returned by any API response or shown again in the dashboard after it is saved.

Limits and retries

Connection counts, monthly publish volume, and bulk publish batch size are limited by plan.

Failures such as authentication or permission errors are not retried automatically; rate limits and transient network or availability errors are retried with a bounded attempt count before a job is marked failed.