EMAILTEMP: Email template
A reusable email template with terminology checking for composing consistent outbound emails.
Default definition. This article describes the default
EMAILTEMP definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches EMAILTEMP.Entity properties
| Property | Value |
|---|---|
| Entity code | EMAILTEMP |
| Display name | Email template |
| Plural | Email templates |
| Level | 30100 |
Use cases
Simple CRM entity for email templates. Single-column layout with a name field and a termeditor for the template body. Used to store pre-written email content that can be reused when composing emails.
Fields
Template
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
body | termeditor | Yes | Body. |
Relationships
- No declared relationships in the default definition.
Creating a Email template via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "EMAILTEMP",
"level": 30100,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"body": "Example value"
}Listing Email templates records
GET /v1/entities/EMAILTEMP/SUB:<your-sub-id>