What this article helps with

Use this guide if you need to know whether a field can be mapped, checked in preflight, and published with QuillDock today.

This guide is for

Anyone setting up or reviewing a QuillDock publish flow from Google Sheets or Airtable into one Wix CMS collection.

Field types QuillDock supports today

QuillDock currently supports these Wix target field types:

• Text
• Number
• Boolean
• Date and time
• URL
• Single image
• Single file
• Single reference

Current limits inside those supported types

• Single image means one usable image URL or one attachment per row
• Single file means one usable file URL or one attachment per row
• Single reference means one resolvable reference per row to an item that already exists in the referenced Wix collection
• QuillDock does not create referenced items for you

Field types and workflows QuillDock does not support yet

• Galleries or multi-asset media writes
• Multi-reference fields
• Self-reference or graph-style reference automation
• Rich content or block content
• Generic object or array payloads
• 2-way sync
• Cross-collection orchestration
• Custom transforms

What to do when a field is unsupported

1. Leave the unsupported field unmapped.
2. Continue with the supported fields you do need.
3. Run preflight again after you update the mapping.
4. Publish only from a fresh passing preflight.

What to do when a supported field is still blocked

• For image or file fields, make sure each row has only one usable asset value
• For reference fields, make sure each row has only one reference value and that the referenced Wix item already exists
• Run preflight again after you fix the source data or mapping

When to contact support

Contact support if a field looks like it belongs to the supported list above but QuillDock still keeps it blocked after you run preflight again from a fresh saved mapping.

Related guides

• Configuration / Mapping
• Preflight review
• Fix mapping issues
• Fix preflight errors and warnings