plan-change-scheduled

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

Quick facts

Domain	Channels	Recipients
—	—	—

Trigger sites

No triggerWorkflow calls found in the scanned source paths.

Payload — PlanChangeScheduledData

interface PlanChangeScheduledData {
  /** Human label of the plan taking over, e.g. "Premium" or "Equipos Premium · 10 asientos". */
  newPlan: string;
  /** Already formatted in the recipient's locale by the caller. */
  effectiveDate: string;
  billingUrl: string;
}

Channel steps

Trigger step

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

See also

• Notifications overview — the workflow grid, source-of-truth file map.
• Configuration — env vars, dashboard checklist, channel mapping.