CRM update — Brightline Health — Pilot
Produced by: Run EXAMPLE-CRM-01 · one approval · document artifact · ledger SALES-204 · demo values
- Proposed changes
- 4 rows, each carrying the value the field held at 2026-09-11T14:06:22Z, the value it would become, and the literal fragment of the message that justifies it — "they're moving to negotiation" against the stage, "new close date 30 Sep" against the close date. The stage's stored value came back from the portal's own stage list, not from a model turning the word Negotiation into one.
- Note recorded in Aestus
- The note the call produced, recorded on the ledger ticket rather than on the deal. The heading says where it went, because the HubSpot toolkit reachable from a workflow step here has no note or engagement tool at all — so there is nothing to write one with, and leaving a reader to assume otherwise is the expensive kind of silence.
- Not changed
- 3 rows the run refused out loud: the amount, because the message named no number; the owner and a blocker field, because neither is in this workspace's list of writable fields. Each one names the reason. A refusal nobody can see is indistinguishable from a step that quietly did nothing.
- Needs you
- Maya Okonjo is not yet associated with this deal. One HubSpot contact matches the words in the message. Approving associates that existing contact; this run never creates a person record.
- Sources
- Every row points at one: the deal read, the message, the pipeline's stage list, the contact search, this run's own field-list setting, and the ledger ticket. A figure with no source is refused before anybody sees it.
- Applied
- Appended after one tap. 3 fields written in a single update call, and 1 skipped — "The primary contact moved between the proposal and the approval, so nothing was written to it." — because the field was read again at the moment of writing and no longer matched what was approved. The skipped row is printed, not dropped.