Sync Modes: Scheduled vs Webhook vs Manual

Three ways to sync

Trellis supports three sync modes, each suited to different use cases. The right choice depends on how often your content changes, how many items you manage, and which Trellis tier you are on.

Manual sync

Manual sync is the simplest mode. You click a button on the Trellis dashboard and the sync runs immediately. Nothing happens until you trigger it.

When to use manual sync:

• One-time imports — migrating content from a spreadsheet or another CMS into Webflow for the first time.
• Testing — verifying that your field mappings produce the right output before turning on automation.
• Low-volume sites — if your content changes a few times a month, clicking a button is faster than configuring automation.
• Staging workflows — syncing to a staging site on demand before publishing.

Manual sync is available on every Trellis tier, including free trials. It is the best way to validate your setup before committing to a paid plan.

Scheduled sync

Scheduled sync runs automatically at a fixed interval. Trellis checks your source for changes and pushes updates to Webflow on a timer.

How it works:

1. Trellis polls your source (Airtable, Notion, etc.) on a schedule.
2. It compares the current data against what was last synced using content hashes.
3. Only changed, added, or deleted items are pushed to Webflow — unchanged items are skipped.

Interval by tier:

• Starter — every 15 minutes.
• Pro — every 5 minutes.

When to use scheduled sync:

• Content that updates throughout the day but does not need to appear on the site within seconds.
• Teams where multiple editors are making changes and you want a predictable cadence.
• Budgets that do not justify the Scale tier for real-time updates.

Scheduled sync is reliable, simple, and handles most use cases well. The 5-15 minute delay is invisible to site visitors in the vast majority of scenarios.

Webhook sync (real-time)

Webhook sync is event-driven. When a record changes in your source platform, it sends a notification directly to Trellis, which processes the update immediately.

How it works:

1. Trellis registers a webhook with your source platform (e.g., Airtable's webhook API).
2. When a record is created, updated, or deleted, the source sends a payload to Trellis.
3. Trellis processes the change and pushes the update to Webflow within seconds.

Important: Airtable webhook expiration.

Airtable webhooks automatically expire after 7 days of inactivity. Trellis handles this transparently — a background job refreshes webhook registrations before they expire, so you never need to re-create them manually.

When to use webhook sync:

• Time-sensitive content — inventory counts, event RSVPs, pricing changes, or availability calendars where a 15-minute delay matters.
• High-volume updates — sites with hundreds of changes per day where polling would be wasteful.
• Interactive workflows — when editors expect to see changes on the live site within seconds of saving in Airtable.

Webhook sync requires the Scale tier.

Choosing the right mode

Factor	Manual	Scheduled	Webhook
Update speed	On demand	5-15 min	Seconds
Setup effort	None	Minimal	Minimal
Best for	Testing, one-time imports	Daily content updates	Real-time, high-volume
Trellis tier	All	Starter+	Scale
Cost	Lowest	Moderate	Highest

Rules of thumb:

• If you update content less than once a day, manual is fine.
• If you update content daily but do not need instant updates, scheduled is the sweet spot.
• If you update content multiple times per day and visitors need to see changes immediately, webhook is worth the investment.

You can always start with manual, move to scheduled, and upgrade to webhook later — your field mappings and configuration carry over between modes.

Further reading

• Pricing — compare tier features and sync intervals.
• Airtable Connector — how Trellis connects to Airtable, including webhook setup.