DemandFlow Support Centre

ACCOUNT: Account

A CRM account representing a sales or commercial relationship with a company.

Default definition. This article describes the default ACCOUNT 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 ACCOUNT.

Entity properties

Property	Value
Entity code	`ACCOUNT`
Display name	Account
Plural	Accounts
Level	11100
Extends	`COM`. See Entity Extension.

Use cases

ACCOUNT is a CRM/sales overlay of COM. While COM is the canonical company record used across the platform, ACCOUNT captures the sales relationship: who owns the account, what stage it's at, how it was sourced, revenue targets, and engagement history. An ACCOUNT always links back to a COM record via df_extendObject. Multiple overlays can exist for the same COM - e.g. a company could be both an ACCOUNT and a CLIENT simultaneously. Key CRM fields include accountOwner (singleuser), accountStatus, leadSource, annualRevenue, lastContactDate, and nextFollowUp.

Fields

Because this entity extends COM, some fields may actually be stored on the linked base record rather than on this record directly. See Entity Extension.

General: Account Details

Field	Type	Required	Notes
`name`	text	Yes	Account Name.
`df_extendObject`	reference → `COM`		Parent company.
`description`	text (multi-line)		Description.
`accountOwner`	reference → user		Account Owner.
`accountStatus`	enum		Status. Valid ids: `prospect` (Prospect), `qualified` (Qualified), `active` (Active), `nurture` (Nurture), `churned` (Churned), `dormant` (Dormant).
`accountType`	enum		Account Type. Valid ids: `newBusiness` (New Business), `existing` (Existing Customer), `strategic` (Strategic), `partner` (Partner).

General: Sales Information

Field	Type	Notes
`leadSource`	enum	Lead Source. Valid ids: `inbound` (Inbound), `outbound` (Outbound), `referral` (Referral), `event` (Event), `website` (Website), `partner` (Partner), `other` (Other).
`annualRevenue`	number	Annual Revenue Target.
`currency`	text	Currency. Placeholder: GBP.
`industry`	reference → `IND`	Industry.

General: Engagement

Field	Type	Notes
`lastContactDate`	date	Last Contacted.
`nextFollowUp`	date	Next Follow-up.
`engagementScore`	number	Engagement Score.
`website`	text (URL)	Website.

Relationships

Lookups: df_extendObject points at a COM record; industry points at a IND record.
Extends: this entity extends COM. See Entity Extension.
Related lists: PPL (format SUB|ACCOUNT|PPL), DEAL (format SUB|ACCOUNT).
Activity: activity timeline panel attached.

Creating a Account via the API

POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json

{
  "entity":   "ACCOUNT",
  "level":    11100,
  "comboKey": "SUB:<your-sub-id>|ENT:",
  "name": "Account Name",
  "description": "Description",
  "accountStatus": "prospect",
  "accountType": "newBusiness"
}

Listing Accounts records

GET /v1/entities/ACCOUNT/SUB

DemandFlow Support Centre

ACCOUNT: Account

ACCOUNT: Account

Entity properties

Use cases

Fields

Relationships

Creating a Account via the API

Listing Accounts records

See also

Was this article helpful?