Skip to main content
Every account, person, and path has an activity timeline. Alongside CRM activity and engagements, it logs every write Clustr itself makes to the record — whether a person made it by hand or a Workflow made it.

What gets logged

Where to read it

  • In the app: the Clustr activity column on a person’s or account’s Activity tab, the History section of a warm intro’s drawer, and the hover on a warm intro’s owner and status (“since 24 Sep, by Alice”).
  • In the API: List Account Activity, List Person Activity and List Warm Intro Activity. Warm intro rows also carry owner_set_at, owner_set_by, status_set_at and status_set_by, and connector rows carry added_at and added_by.
  • Over MCP: list_record_activity, with entity set to account, person or path.
History from before 28 September 2026 was filled in from the dates Clustr already had: when each connector was added (and by whose import), when each connector’s owner was set, and each warm intro’s current status. Those entries carry "backfilled": true, and say system when Clustr does not know who made the change.

Reading it

Each entry names the actor: a person’s email, system, or the Workflow that did it. A Workflow’s actions on one record are grouped into a single expandable entry — “Workflow Hot accounts alerted #sales, set Tier A” — rather than one line per action, so a Workflow with three actions doesn’t flood the timeline with four lines per fire.

Why every action writes here

Pushing a contact to HubSpot by hand and a Workflow pushing the same contact look identical on the record: both leave a pushed_to_crm entry with who or what did it. Nothing you or a Workflow does to a record disappears the moment the toast does.