Skip to content

tour-rescheduled

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

DomainChannelsRecipients
toursin-app + email + pushOther party (customer or agent, whichever did not initiate)
SourceContext
packages/api/src/services/tours.ts:533updateTourStatus
interface TourRescheduledData {
actorName: string;
propertyAddress: string;
scheduledAt: string;
calendarUrl: string;
}

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.

Knock dashboard template body: {{ inAppBody }}.

LocalePreview 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).

LocaleSubject preview
esCambio de horario para recorrido en ${p.propertyAddress}
enTour 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 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.