Skip to content
Birdhouse

Sync Verticals

Vertical sync pulls all published Vertical entries from Strapi and generates TypeScript files used throughout the app.

Command

Section titled “Command”
Terminal window
yarn sync:verticals

What it generates

Section titled “What it generates”
Generated artifact Purpose
InsuranceTypes enum TypeScript enum of all insurance type values
Lookup functions Functions to get vertical metadata by insurance type
Policy modal files Modal content definitions for each vertical
Plan mapping data Plan name to display name mappings

What gets synced

Section titled “What gets synced”

Content fields

Section titled “Content fields”
Strapi field What it powers in the app
Content -> Title Display name of the product (e.g. “Dental”)
Content -> Excerpt Short description in product cards
Content -> Description Full product description
Content -> Label Label shown in policy modal
Image Product icon/image used everywhere
Color Code Banner/accent color for the product

Policy modals

Section titled “Policy modals”
Strapi field What it powers
Policy Modal Sections Content blocks (text, lists) in policy detail modal
Policy Modal Buttons Action buttons in policy detail modal

Plan mapping and metadata

Section titled “Plan mapping and metadata”
Strapi field What it powers
Plan Mapping Display name overrides (e.g. “Basic” -> “Starter”)
Subtitle Metadata Fields shown as subtitle on policy card

Other fields

Section titled “Other fields”
Strapi field What it powers
Translation Key Base key for translations
Legacy Vertical ID Backwards compatibility mapping
Has Automated Cancel Process Whether cancel flow is self-serve
Finance Ads Lookup Tracking category per locale

When to sync

Section titled “When to sync”

Run vertical sync when:

  • A new Vertical is created in Strapi
  • Vertical metadata changes (name, color, regions, plan mappings)
  • Policy modal content is updated
  • Plan or add-on mappings change

After syncing

Section titled “After syncing”
  1. Review the generated files for correctness
  2. Commit and open a PR
  3. The app will use the updated vertical definitions after deployment

Important notes

Section titled “Important notes”
  • Verticals are synced all at once (not individually like questionnaires).
  • Synced files are auto-generated — manual changes get overwritten on the next sync.
  • Only published content is synced (drafts are ignored).
  • Translation keys derive from the vertical name — renaming a vertical changes all its translation keys.
  • The vertical sync process is still manual (no n8n automation yet).

See also

Section titled “See also”