# How to use a Righthand with Webflow

Use Righthand to audit one Webflow CMS collection before publication.

By Righthand Team · 2026-10-11

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-webflow

## Quick answer

Use Righthand to audit one Webflow CMS collection before publication. Prepare field-level exceptions instead of treating complete text as proof an item is live.

Start with a reviewable deliverable, keeping Webflow as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

Webflow documents collections, CMS items, and publishing operations. See the [official Webflow reference](https://developers.webflow.com/data/docs/working-with-the-cms). Provider capabilities and Righthand's available tools are separate checks.

Use the owner's named site and CMS collection, excluding unpublished collections and unrelated workspace sites from the review. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: site ID, collection, item ID, slug, locale, draft status, title, referenced author. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Draft and live states need separate review. Publishing or deleting referenced items belongs to the site owner.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the website editor |

## Illustrative first-run brief

> Use the owner-provided Webflow snapshot or approved read-only view. Compare ten CMS items against the editorial checklist. Flag required fields, duplicate proposed slugs, and unresolved references without publishing. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the website editor to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

An article with full text but a missing author reference stays an exception. An approved draft remains awaiting publication verification.

Compare an exception with its editor view and check the public URL separately. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Item A | Approved copy, image supplied | Ready for editor review |
| Item B | Reference image missing | Hold publishing recommendation |
| Item C | Same slug as another item | Resolve identity conflict |

## Common failure and recovery

Staged content can differ from the live item. Identify the input state before correcting anything; do not replace a newer draft with stale live content.

When a slug conflicts, preserve both item IDs and ask the site editor which record is authoritative before preparing any publishing checklist.

## FAQ

### What should the reviewer verify first?

Compare an item ID, slug, referenced images, and source content with the supplied publish state. A CMS entry alone is not public-page evidence.

### How should a repeat run be scoped?

Record the site, collection, item IDs, and cutoff on each release review. Recheck publication separately after any authorized change; do not recycle an earlier preview result.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.