Skip to main content
A note is what your team knows about a record that no field holds: “Patrick is an investor, ask Anaïs before requesting an intro through him”, “renewal talks start in March”, “met at the offsite, warm”. Every record your team looks at can carry one.

​
One note per record, shared by the workspace

Each record has one note, not a thread. Any member of the workspace can read and edit it, and everyone sees the same text. Notes stay in Clustr: they are not synced to your CRM. A write replaces the note. To add a line, read the note first and send the combined text. That is also what an assistant does over MCP: set_person_note and set_account_note say so in their descriptions.

​
Clearing a note

An empty or whitespace-only note clears it, on every record and every surface: the app, the API and MCP. Emptying the box in the app, a PUT with an empty body or notes, and set_person_note with an empty note all remove the note. The explicit routes still work too: DELETE /v2/persons/{person_id}/note, clear_notes: true on an intro, and the clear_*_note tools.

​
A dismissal is not a note

Dismissing an account can record why (the suggested dismissal does, and dismiss_account takes a reason). That reason is the account’s dismiss_reason, a field of its own, and it never overwrites the account’s note.

​
A person’s note belongs to the person

A person can be a connector (someone who introduces you), a prospect (someone you want to reach), or both. Their note is on the person, not on either role, so the note you write on a connector’s page is the one shown when a colleague requests an intro through them, and the one get_person_note returns. A person’s note is keyed on their LinkedIn id. When Clustr learns that two LinkedIn ids are the same person, the note moves with them. You can write a note on anyone who is one of your connectors or appears in one of your warm intros. Anyone else answers 404.

​
Who edited it, and when

Every note carries its last edit, and the app shows it as “Edited by X, date”:
  • a person note: updated_at, updated_by and updated_by_name;
  • an account note: notes_updated_at, notes_updated_by and notes_updated_by_name. These move only when the note does. The account’s own updated_at moves on every change to it, a new tier included;
  • a warm intro’s note: notes_updated_at and notes_updated_by_name in the tracking block of Get Opportunity. They too move only when the text changes.
The name is the member’s name in your owner directory. A note written with an API key has no author, so these fields are null. Every edit is also on the record’s activity timeline as a notes_set event, which says that the note was added, changed or cleared. It never quotes the note.

​
Limits

A note is up to 10,000 characters in the app. The person-note API enforces the same cap.