DemandFlow Support Centre

SALEMTG: Meeting

The SALEMTG entity: A sales meeting record capturing which market, product, roles, pains, and collateral were discussed, along with an AI-computed meeting score.

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

Entity properties

Property	Value
Entity code	`SALEMTG`
Display name	Meeting
Plural	Meetings
Level	30000

Use cases

SALEMTG stores completed meeting records from the live Sales Meeting function. The meeting function guides reps through a meeting with chip-based toggles for roles, pains, and collateral, computing a weight-based score in real-time. On end, the meeting state is saved here for history and analytics.

Fields like rolesPresent, painsDiscussed, and collateralPresented store JSON arrays of the toggled items.

Fields

Meeting

Field	Type	Required	Notes
`name`	text	Yes	Meeting name
`meetingDate`	date		Date
`company`	reference → `COM`		Company
`contacts`	text (multi-line)		Read-only. Contacts

Details

Field	Type	Notes
`market`	reference → `SALEMARKET`	Market
`product`	reference → `PROD`	Product
`outcome`	enum	Outcome Valid ids: `followUp` (Follow-up booked), `quote` (Quote requested), `demo` (Demo requested), `won` (Won), `lost` (Lost), `noOutcome` (No outcome).
`score`	number	Read-only. Meeting score (%)

Notes

Field	Type	Required	Notes
`meetingNotes`	text (multi-line)		Meeting notes

Roles Present

Field	Type	Required	Notes
`rolesPresent`	text (multi-line)		Read-only. Roles present

Pains Discussed

Field	Type	Required	Notes
`painsDiscussed`	text (multi-line)		Read-only. Pains discussed

Collateral Presented

Field	Type	Required	Notes
`collateralPresented`	text (multi-line)		Read-only. Collateral presented

Additional panels

Activity timeline panel attached.

Relationships

Lookups: company points at a COM record; market points at a SALEMARKET record; product points at a PROD record.

Creating a Meeting via the API

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

{
  "entity":   "SALEMTG",
  "level":    30000,
  "comboKey": "SUB:|ENT:",
  "name":    "Example name",
  "meetingDate":    "2026-01-01",
  "company":    "",
  "market":    ""
}

Listing Meetings records

GET /v1/entities/SALEMTG/SUB

DemandFlow Support Centre

SALEMTG: Meeting

SALEMTG: Meeting

Entity properties

Use cases

Fields

Relationships

Creating a Meeting via the API

Listing Meetings records

See also

Was this article helpful?