Light
Dark
All diagrams Technical architecture →
Candid Leap · WF-Algolia

How content becomes searchable

From a CMS publish in Webflow to instant search on the live site — end to end.

Webflow

Content published

An editor publishes or updates CMS content in Webflow — no export, no manual steps.

Source of truth
1
Signed webhook
(HMAC verified)
Cloudflare

Received at the edge

The event is authenticated and placed on a durable queue. Retries and a dead-letter safety net are built in.

Nothing gets lost
2
Queued, delivered
at-least-once
Railway

Sync engine

Fetches the changed items from Webflow, applies the customer's field mapping, and writes records in batches.

Idempotent · auto-retry · resumable
3
Records indexed
in batches
Algolia

Search index

The customer's own Algolia index holds the live records — typically searchable within seconds of publish.

Customer-owned index
4
Query and results,
directly from the browser
Live site

Visitor searches

Our script on the published site renders search, filters and browse UI — talking to Algolia directly for millisecond results.

Our backend is never in the search path
Other ways a sync starts
Manual — one click in the Designer extension·Scheduled — per-collection cron, hourly to monthly·Recovery — failed events replayed automatically from the dead-letter queue every 5 minutes
Security model
Webhooks are HMAC-signed·API credentials are stored encrypted (AES-256-GCM) and never leave the backend·the browser only ever sees a public search-only key