Reference Fields (Single Reference)

What is a reference field?

A reference field creates a relationship between two collections. Instead of duplicating data, you point to an item in another collection. When that item updates, every reference to it updates automatically.

How it works

A single reference field on Collection A points to one item in Collection B. For example:

• A Blog Post references one Author (team member).
• A Product references one Category.
• A Case Study references one Client.

In the CMS editor, the reference field appears as a dropdown showing all items from the referenced collection.

When to use single reference

Use a single reference when:

• Each item relates to exactly one item in the other collection.
• The related item has its own identity — it could appear in multiple places.
• You want to avoid duplicating data (e.g., author name and photo on every blog post).

Do NOT use a reference when:

• The data only belongs to one parent (use regular fields instead).
• You need to relate to multiple items (use multi-reference instead).
• The related data is a simple label (use a select field instead).

Reference vs. select

Reference	Select
Points to	A full collection item	A label/string
Data	Name, photo, bio, etc.	Just the label
Own page	Can have its own page	Cannot
Maintenance	Update once, reflects everywhere	Update everywhere manually

Use a reference when the related item is a real entity (a person, an organization, a product). Use a select when it is just a category label.

Setting up references

1. Create the referenced collection first — you cannot reference a collection that does not exist yet. Build the Author collection before adding an Author reference to Blog Posts.
2. Choose a good primary field — the referenced collection's primary field is what appears in the dropdown. "John Smith" is useful. "Author #47" is not.
3. Consider the display — what data will you pull from the reference? If you only need the name, a reference might be overkill. If you need name, photo, and bio, a reference is the right choice.

Common patterns

• Blog Posts → Author (team member)
• Products → Category
• Events → Location
• Case Studies → Client
• Courses → Department
• Employees → Department

Tips

1. Name your reference field clearly — "Author" is better than "Team Member Reference". The field name should describe the relationship, not the collection.
2. Make references optional when appropriate — not every blog post needs an author. Make the field optional so it does not block content creation.
3. Limit the dropdown — if the referenced collection has hundreds of items, the dropdown becomes unwieldy. Consider adding search or filtering.

Platform-specific behavior

Airtable linked records

Airtable's linked record fields are bidirectional by default. When you create a linked record from Table A to Table B, Airtable automatically creates a corresponding field in Table B pointing back to Table A. This means both sides of the relationship are always visible and navigable.

Webflow references

Webflow reference fields are one-way only. Adding a reference from Blog Posts to Authors does NOT automatically create a back-reference in the Authors collection. If you want bidirectional navigation (showing an author's posts on their profile page), you need to explicitly create a second reference field — or use a nested collection list on the template page.

This directional difference is one of the most common sources of confusion when syncing between Airtable and Webflow. Trellis asks you whether to create references in both directions during the build step.

Reference field limits in Webflow

Webflow allows a maximum of 5 multi-reference fields per collection. Single reference fields do not count against this limit — you can have as many single references as you need (within the 60-field total). This makes single references the better choice whenever an item only relates to one item in the other collection.

Nested collection lists

In Webflow, you can display referenced content inside a collection list using nested collection lists. For example, on a Blog Post page, you can show the author's name and photo by adding a nested list bound to the Author reference field. Key constraints:

• Nesting depth is limited to 5 levels in Webflow.
• Each nested list adds a database query, which can impact page load time.
• Nested lists display the referenced item's fields, not the parent's fields — you cannot mix fields from both collections in the same list context.

Sync considerations

When syncing references between platforms, the referenced items must exist in the destination before the referencing items. For example, if Blog Posts reference Authors, the Authors collection must be fully synced before Blog Posts. Trellis handles this dependency ordering automatically during the build step by analyzing reference chains and deploying collections in the correct order.