Email and SMS template entity Defines email and SMS notification templates.Documentation Index
Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Fields
Field Registry (from workspace/sources/entity-registry.csv)
| Field | Input Type | Required | Notes |
|---|---|---|---|
| Name | - | - | model: name, rel: string |
| Type | - | - | email, sms; model: type, rel: string |
| Subject | - | - | model: subject, rel: string |
| Body | - | - | model: body, rel: text |
| Is Active | - | - | model: isActive, rel: boolean |
| Slug | - | - | model: slug, rel: string |
| Client | - | - | model: client, rel: ManyToOne ClientProfile |
Merge Tags
Available merge tags for personalization:| Tag | Description |
|---|---|
{FirstName} | Member first name |
{LastName} | Member last name |
{FullName} | Full name |
{Email} | Email address |
{DOB} | Date of birth |
{City} | City |
{State} | State |
{Country} | Country |
{MembershipPlan} | Plan name |
{MembershipExpiryDate} | Expiry date |
Features
Notification Template
Acceptance Criteria
Frontend
- Admin/client UI can view and manage
Notification Templaterecords where applicable.
Backend / API
- CRUD operations exist for
Notification Template(create, read, update, delete/archive).
Permissions
- Access is restricted to appropriate roles (tenant-scoped).
Business Rules
- Fields and relationships documented on this page are enforced for
Notification Template.
Error Handling
- Invalid payloads return field-level validation errors.