PPLLIST: People list
The PPLLIST entity represents a curated list of people/contacts built from PPL records for targeting, outreach, or segmentation.
Default definition. This article describes the default
PPLLIST 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 PPLLIST.Entity properties
| Property | Value |
|---|---|
| Entity code | PPLLIST |
| Display name | People list |
| Plural | People lists |
| Level | 210 |
Use cases
PPLLIST lets users build named lists of PPL contacts for bulk operations like email campaigns, event invitations, or sales outreach. The entity itself holds list metadata (name, description, status). PPL records are associated via LINK objects with comboKey relationships, displayed as a relatedlist on the Members panel.
Fields
General
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Name. |
description | text (multi-line) | Description. | |
status | enum | Status. Valid ids: active (Active), archived (Archived). | |
memberCount | number | Members. Read-only. |
Additional panels
- Activity timeline panel attached.
Relationships
- Related lists:
PPLvia formatSUB.
Creating a People list via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "PPLLIST",
"level": 210,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Example",
"description": "Long description text.",
"status": "active"
}Listing PPLLIST records
# All people lists in your tenant
GET /v1/entities/PPLLIST/SUB