tour-rescheduled
Source of truth:
packages/notifications/src/translations.ts
Quick facts
Section titled “Quick facts”| Domain | Channels | Recipients |
|---|---|---|
| tours | in-app + email + push | Other party (customer or agent, whichever did not initiate) |
Trigger sites
Section titled “Trigger sites”| Source | Context |
|---|---|
packages/api/src/services/tours.ts:533 | updateTourStatus |
Payload — TourRescheduledData
Section titled “Payload — TourRescheduledData”interface TourRescheduledData { actorName: string; propertyAddress: string; scheduledAt: string; calendarUrl: string;}Channel steps
Section titled “Channel steps”Trigger step
Section titled “Trigger step”The caller invokes triggerWorkflow('tour-rescheduled', recipientIds, data) where data is the TourRescheduledData shape above. The server pre-translates the payload via getTranslatedPayload('tour-rescheduled', recipientLocale, data) from @repo/notifications before sending, producing { inAppBody, emailSubject, emailBody } for the dashboard templates to render.
In-app feed
Section titled “In-app feed”Knock dashboard template body: {{ inAppBody }}.
| Locale | Preview source |
|---|---|
es | 🔄 ${p.actorName} propuso un nuevo horario para el recorrido en ${p.propertyAddress}: ${p.scheduledAt} |
en | 🔄 ${p.actorName} proposed a new time for the tour at ${p.propertyAddress}: ${p.scheduledAt} |
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 | Cambio de horario para recorrido en ${p.propertyAddress} |
en | Tour rescheduled at ${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)
Section titled “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.
See also
Section titled “See also”- Notifications overview — the workflow grid, source-of-truth file map.
- Configuration — env vars, dashboard checklist, channel mapping.