A Guide To Webflow CMS Errors

Watch the original video

A Webflow validation failure means the submitted data does not match what the integration expects. The February 2021 video covers four useful causes. Start with the failed step's input and exact error.

1. The CMS structure changed

Compare the failed input with the collection's current fields. Check required fields, renamed fields, deleted fields, and option values. Refresh the collection selection in Zapier, then remap affected fields. Test one record before replaying the failed queue.

2. A referenced item does not exist

A reference field needs an item ID from the correct collection. An Airtable record ID or category name does not replace a Webflow item ID. Find the referenced item first. If it is missing, stop the run and resolve the mapping. Do not create another category automatically unless that is an intended part of your workflow.

3. The field type is wrong

Check the Webflow CMS API documentation against the collection schema. Text, numbers, images, options, and references need different values.

For a hypothetical collection with a numeric price field, compare these fragments:

{"fieldData":{"name":"Test listing","slug":"test-listing","price":"ten"}}

{"fieldData":{"name":"Test listing","slug":"test-listing","price":10}}

The second fragment supplies a number. It still needs the remaining required fields from your collection. For complete create/update handling, see the Airtable-to-Webflow workflow.

4. The action and publishing state differ

The original video discusses publishing only the .webflow.io domain. Current actions distinguish staged items from live items, so inspect the action you actually use. A successful draft update does not prove the public page changed. Confirm the connected site, collection, item, and intended publish destination. Zapier's current Webflow guide lists its supported actions.

Retry one item

Keep the failed input for comparison. Correct one cause, then retry only that item. Read its returned ID and inspect its stored fields. If creation succeeded before a later step failed, reuse that ID during recovery. Otherwise, a replay can create duplicates.

Original chapters

• 00:00 Intro
• 01:28 You changed your CMS structure in Webflow
• 02:12 Your referenced CMS Item ID doesn't exist
• 04:37 You are sending an incorrect field type to Webflow
• 05:54 You only published your .webflow.io domain