The fields of one pipeline, in column order. A field's source says where its value lives:
ENTRY fields are stored on the entry — their fieldIds are the keys entry values accept —
while RECORD fields read (and write through to) an attribute of the company or contact and
arrive on entries as recordValues. type, unit and calculation say how to render a value
and what the stage footers total.
Bearer <token>.Ok
TEXT or NUMBER for pipeline-created fields; a record attribute keeps its own type.
Where a field's value lives.
Footer totals the lane-stats aggregation supports. Numbers only.
RECORD only: dotted path on the company/session document (value, customData.seats).
SELECT-style attributes carry their options for rendering and validation.
RECORD only: the attribute cannot be written (e.g. last-seen device type).