How it works
Hours of setup.
Gone in 60 seconds.
Describe what you need. Trellis builds your content structure across all your connected platforms, manages fields as your site evolves, and optionally syncs everything. Here's exactly what happens under the hood.
The model
Architect. Manage. Sync.
Every Trellis workflow maps to one of three operations. Use them independently or chain them together. The architect alone saves hours.
Operation 01
Propose & Build
You describe the content model you need. Trellis translates that into a production-ready Webflow CMS schema and builds it directly in your site.
Input: plain language or structured brief
Tell Trellis what content you need: "A blog with authors, categories, and related posts" or "A product catalog with variants, pricing tiers, and documentation links." You can be as terse or as specific as you want. Trellis handles the structural interpretation.
Output: a complete CMS schema
Trellis generates a full collection structure — every field name, field type, help text, validation rule, and reference relationship. This isn't a wireframe. It's a buildable specification. You review it, adjust anything you want, then approve.
Execution: direct Webflow API writes
On approval, Trellis creates the collections and fields in your Webflow site via the CMS API. Fields are created in the correct order — references last, so dependencies resolve cleanly. No manual clicking. No missed field types.
Result: production-ready collections
Open your Webflow Designer. The collections are there, correctly structured, correctly named, ready for content entry or CMS-bound components. The schema matches what Trellis proposed — no drift, no silent defaults.
Operation 02
Audit
Already have collections? Trellis reads your existing CMS schema and tells you exactly what's wrong with it — and what 'wrong' means in context.
Input: your existing Webflow site
Authorize Trellis to read your Webflow site. It pulls every collection, every field, every reference. Read-only by default — Trellis does not modify anything during an audit unless you explicitly ask it to.
Process: structural analysis against best practices
Trellis checks field naming conventions, type appropriateness (is that really a plain text field, or should it be rich text?), missing help text, orphaned references, unused collections, slug conflicts, and image field configurations. Every check maps to a specific Webflow behavior.
Output: a prioritized issue list
You get a structured report: critical issues first, warnings second, suggestions third. Each issue includes what's wrong, why it matters, and the specific fix. Not vague advice — exact field-level changes.
Action: fix manually or let Trellis apply
Review the report and choose which fixes to apply. Trellis can execute approved changes directly, or you can export the report and handle it yourself. Either way, the diagnosis is precise. Read more about CMS best practices in our collection setup guide.
Definitions
What “correct CMS structure” means
Trellis isn't opinionated for the sake of it. Every structural recommendation maps to a specific Webflow behavior, API constraint, or downstream consequence.
These aren't arbitrary preferences. Each rule exists because violating it causes a specific, observable problem in Webflow — either in the Designer, the published site, or the API. See our full guide to CMS collection setup for the complete rationale.
Operation 03
Sync to Airtable
Trellis maps your Webflow CMS collections to Airtable bases — field by field, type by type. No CSV exports. No Zapier chains. Direct, structural sync.
Link Webflow collection to Airtable base
Select a Webflow collection and an Airtable base. Trellis reads both schemas and generates a field mapping proposal. It handles the type translation — Webflow "Option" becomes Airtable "Single Select," Webflow "Multi-Reference" becomes Airtable "Linked Record," and so on.
Automatic field-level type coercion
Every Webflow field type has an Airtable equivalent (or a close-enough equivalent with documented caveats). Trellis generates the mapping, flags fields that require lossy conversion, and lets you adjust before syncing. No silent data loss.
Bidirectional data flow with conflict rules
Records sync between Webflow and Airtable based on the rules you set: Webflow as source of truth, Airtable as source of truth, or last-write-wins. Trellis tracks sync state per record and per field, so partial updates don't clobber unrelated changes.
Airtable becomes your editorial interface
Your content team works in Airtable — filtering, sorting, bulk-editing with familiar spreadsheet mechanics. Changes flow back to Webflow CMS automatically. Editors never need to open the Webflow Designer for content updates.
How the sync actually works
Initial sync: Trellis reads every item in the Webflow collection and creates corresponding records in Airtable (or vice versa, depending on direction). Each record gets a sync ID — an internal identifier that ties the Webflow item to the Airtable record regardless of name changes.
Ongoing sync: On each sync cycle, Trellis compares field-level timestamps. If a field was modified in Airtable since the last sync, it writes to Webflow. If modified in Webflow, it writes to Airtable. If modified in both, it follows your conflict resolution rule.
What doesn't sync: Webflow CMS items in draft or archived state are excluded by default (configurable). Computed fields in Airtable (formulas, rollups, lookups) are read-only — Trellis will never attempt to write to them.
Rate limits: Webflow's CMS API enforces rate limits. Trellis batches writes and respects backoff headers automatically. A full sync of 500 items typically completes in under two minutes.
Schema evolution
What happens when things change
Schemas aren't static. Content models evolve. Trellis handles the messy reality of structural drift without silent breakage.
You add a field in Webflow
Trellis detects the new field on the next sync or audit cycle. For synced collections, it proposes an Airtable field mapping. For audited collections, it checks the new field against best practices. No manual re-configuration needed.
You delete a field in Webflow
Trellis marks the corresponding Airtable field as orphaned but does not delete it. Your Airtable data is preserved. You get a notification with the option to archive, keep, or delete the orphaned field.
You rename a collection
Trellis tracks collections by internal ID, not display name. Rename as much as you want — the sync mapping, audit history, and field associations remain intact.
You change a field type
This is the hardest case. Trellis detects the type change, pauses sync for that field, and presents you with a migration plan. It will not silently coerce data between incompatible types.
Airtable schema changes
Same logic, opposite direction. If you add columns in Airtable, Trellis offers to map them to Webflow fields. If you delete columns, the Webflow field is flagged as unsynced — not deleted.
Reference targets change
If a referenced collection is renamed, deleted, or restructured, Trellis flags the broken reference chain and pauses dependent syncs until you resolve it. No cascading silent failures.
FAQ
Common questions
Does Trellis touch my live site?
No. Trellis interacts exclusively with the Webflow CMS API — collections, fields, and items. It does not modify your Designer layout, your published pages, your hosting configuration, or your custom code. CMS structure changes (adding fields, creating collections) are reflected in the Designer but do not affect your published site until you bind those fields to elements and publish.
Can I use just the audit without the sync?
Yes. Every operation is independent. You can run audits on every collection in your site without ever connecting Airtable. The audit reads your schema, checks it against Trellis's rule set, and returns a report. That's it. Many teams start with audit-only to understand their current CMS health before deciding whether they need structure changes or sync. See pricing for audit-only plans.
Can I use just the sync without the audit?
Yes. If your CMS structure is already solid, you can skip the audit entirely and go straight to Airtable sync. Trellis will still validate field type compatibility during the mapping phase — it's not going to sync a rich text field into a checkbox column — but it won't opine on your naming conventions or structural choices.
What Webflow plans does Trellis support?
Trellis works with any Webflow plan that includes CMS API access. That's the CMS plan and above. Workspace plans with Sites also work. If your site has CMS collections and API access enabled, Trellis can connect to it.
Is there a limit on collections or fields?
Trellis respects Webflow's own limits: 40 collections per site, 60 fields per collection. Within those constraints, there are no Trellis-imposed caps on the number of collections you can audit, build, or sync. Check pricing for plan-specific details.
How does Trellis compare to building CMS manually?
A typical 8-collection Webflow site with proper field types, help text, and reference architecture takes 2-4 hours to set up manually in the Designer. Trellis does it in under a minute. More importantly, it doesn't forget the help text, doesn't mistype a field name, and doesn't accidentally create a plain text field where rich text was needed. For a detailed breakdown, see our comparison page.
Can Trellis delete my collections or data?
Not without explicit, per-action confirmation. Trellis separates read operations (audit, schema analysis) from write operations (create, update, delete). Delete actions require a dedicated confirmation step and are logged with full audit trails. There is no bulk-delete-everything button.
What happens if the sync breaks mid-run?
Every sync operation is idempotent. If a sync fails partway through — network error, rate limit, API timeout — the next run picks up where it left off. Records already synced stay synced. Records not yet processed get processed on the next cycle. No partial writes, no corrupted state.