price-drop

Source of truth: packages/notifications/src/translations.ts

Quick facts

Domain	Channels	Recipients
alerts	in-app + email + push	Every user who favorited the property

Trigger sites

No triggerWorkflow calls found in the scanned source paths.

Payload — `PriceDropData`

interface PriceDropData {
  propertyAddress: string;
  oldPrice: string;
  newPrice: string;
  listingUrl: string;
}

Channel steps

Trigger step

The caller invokes triggerWorkflow('price-drop', recipientIds, data) where data is the PriceDropData shape above. The server pre-translates the payload via getTranslatedPayload('price-drop', recipientLocale, data) from @repo/notifications before sending, producing { inAppBody, emailSubject, emailBody } for the dashboard templates to render.

In-app feed

Knock dashboard template body: {{ inAppBody }}.

Locale	Preview source
`es`	`📉 Bajó el precio en ${p.propertyAddress}: ${p.oldPrice} → ${p.newPrice}`
`en`	`📉 Price dropped on ${p.propertyAddress}: ${p.oldPrice} → ${p.newPrice}`

Email

Subject: {{ emailSubject }}. Body: {{ emailBody }} (HTML mode, dashboard escaping OFF — every user-supplied string is escaped server-side via escapeHtml from @repo/notifications).

Locale	Subject preview
`es`	`Bajó el precio en ${p.propertyAddress}`
`en`	`Price dropped on ${p.propertyAddress}`

Email body is composed by emailBody.es in packages/notifications/src/translations.ts via the layout components in packages/notifications/src/email-layout.ts (wrapEmailLayout, ctaButton, calloutBox, quoteBlock, propertyCard, detailTable / detailRow). Body source is not inlined here because it spans tens of lines per locale — open the source file for the full template.

Push (Android FCM)

Push delivery is configured at the Knock dashboard level for this workflow (FCM channel step with {{ inAppBody }} as the notification body). iOS APNs is deferred until the dashboard p8 key is wired — see Configuration → mobile push.