EMAILLIMITTRACK: Email limit tracker
Tracks email send counts against a defined limit over a rolling period, used for throttling automated email notifications.
Default definition. This article describes the default
EMAILLIMITTRACK 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 EMAILLIMITTRACK.Entity properties
| Property | Value |
|---|---|
| Entity code | EMAILLIMITTRACK |
| Display name | Email limit tracker |
| Plural | Email limit trackers |
| Level | 250 |
Use cases
EMAILLIMITTRACK is a simple lookup entity at level 250. Uses a flat definition array with fields for name, email count, period start/end dates, a link to the EMAILLIMIT definition, and a readonly Dynamics ID. Grid-only view.
Fields
Email limit tracker
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
emailCount | number | Email Count. | |
periodStart | date | Period Start. | |
periodEnd | date | Period End. | |
emaillimitdefinition | reference → EMAILLIMIT | Email Limit Definition. | |
_dynamics_id | text | Dynamics ID. Read only. |
Relationships
- Lookup:
emaillimitdefinition(reference →EMAILLIMIT).
Creating a Email limit tracker via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "EMAILLIMITTRACK",
"level": 250,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example name",
"emailCount": 0,
"periodStart": "2026-01-15",
"periodEnd": "2026-01-15"
}Listing Email limit trackers records
GET /v1/entities/EMAILLIMITTRACK/SUB:<your-sub-id>