Save a Note
Notes
Save a Note
Attach a meeting brief, transcript, prep, or plain note to a contact’s record. Append-only and dated, so a contact builds a history across meetings.
POST
Save a Note
Saves a long-form artifact onto a person or company so it stays on their record. This is for documents you keep on a contact — a meeting brief, a transcript, pre-meeting prep, research, or a plain note — not for logging that an interaction happened. For “an email was sent / a meeting happened”, use
POST /v2/observations.
Notes are append-only and dated, so a contact accumulates a record across meetings. Retrieve the relevant passage later with POST /v2/notes/search.
Request
Body
string
required
Entity UUID, email, domain, or LinkedIn URL. Not a bare name — writes need a precise identifier so the entity can be created if it doesn’t exist yet.
string
required
The full note or document text — a short note or a complete brief/transcript. Kept whole for agents to read.
string
default:"note"
One of
note, meeting_brief, transcript, meeting_notes, pre_meeting, research.string
A short name, e.g.
Pre-meeting brief — renewal or Transcript — Jun 1. Shown in the UI.string
The relevant date (e.g. the meeting date), ISO or plain. Defaults to now.
Response
201 Created
Notes vs observations
After a meeting, use both: record the meeting via
/v2/observations, keep the notes via /v2/notes.