ACTIVITY: Activity
A sales activity record (call, meeting, email, task) linked to a deal and contact.
Default definition. This article describes the default
ACTIVITY 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 ACTIVITY.Entity properties
| Property | Value |
|---|---|
| Entity code | ACTIVITY |
| Display name | Activity |
| Plural | Activities |
| Level | 232 |
Use cases
ACTIVITY tracks sales touchpoints. Child of DEAL via comboKey SUB|DEAL. Links to PPL (contact) via objectLookup. Activity types include call, meeting, email, task, demo, and proposal sent. Each has a subject, date/time, duration, status, and notes.
Fields
General: Activity Details
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Subject. |
activityType | enum | Yes | Type. Valid ids: call (Call), meeting (Meeting), email (Email), task (Task), demo (Demo), proposal (Proposal Sent). |
activityDate | datetime | Date & Time. | |
duration | number | Duration (mins). | |
activityStatus | enum | Status. Valid ids: planned (Planned), completed (Completed), cancelled (Cancelled). | |
contact | reference → PPL | Contact. |
General: Notes
| Field | Type | Required | Notes |
|---|---|---|---|
activityNotes | text (multi-line) | Notes. | |
nextStep | text (multi-line) | Next Steps. |
Relationships
- Lookups:
contactpoints at aPPLrecord.
Creating a Activity via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "ACTIVITY",
"level": 232,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Subject",
"activityType": "call",
"duration": 0,
"activityStatus": "planned"
}Listing Activities records
GET /v1/entities/ACTIVITY/SUB