> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clustr-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Record Activity

> What Clustr did to a record, and who asked

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

| Kind                                                                   | When                                                                                                                                |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| `tags_set`                                                             | [Tags](/tags) changed — including what used to be a status                                                                          |
| `tier_set`                                                             | A tier changed                                                                                                                      |
| `owner_set`                                                            | An owner changed                                                                                                                    |
| `status_set`                                                           | Historical. Nothing writes it since a status became a tag; entries written before that still render, with the tag the status became |
| `list_added` / `list_removed`                                          | Added to or removed from a list                                                                                                     |
| `dismissed` / `restored`                                               | Dismissed or brought back                                                                                                           |
| `pushed_to_crm`                                                        | Pushed to a connected CRM                                                                                                           |
| `intro_requested` / `intro_sent` / `intro_accepted` / `intro_declined` | An [intro request](/intro-requests) moved                                                                                           |
| `workflow_fired`                                                       | A Workflow fired on this record                                                                                                     |
| `workflow_action`                                                      | One action a Workflow took on this record                                                                                           |

## 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.