Skip to main content
Saves a long-form artifact onto a person or company so it stays on their record: a meeting brief you wrote, a transcript, pre-meeting prep, research, or a plain note. Notes are append-only and dated, so a contact accumulates a record across meetings — later you can read the last few and see what changed, or pull a passage with search_notes.
Not the same as record. record logs that an interaction happened (an email was sent, a call was held) and Nous derives claims from it. save_note keeps the document itself. After a meeting, do both: record the meeting, save_note the notes. For the user’s own GTM profile, use update_gtm_profile, not this.

​
Parameters

NameTypeRequiredDescription
focusstring✓Who to attach it to — an email, LinkedIn URL, domain, or entity UUID. Not a bare name.
contentstring✓The full note or document text. Kept in full for agents to read.
typeenumnote (default), meeting_brief, transcript, meeting_notes, pre_meeting, research
titlestringA short name, e.g. Pre-meeting brief — renewal or Transcript — Jun 1.
datestringThe relevant date (e.g. the meeting date), ISO or plain. Defaults to now.
Put the full text in content — it’s kept whole for agents to read. The UI shows the title and date, not the whole body.

​
Returns

Saved Pre-meeting brief — renewal to sarah@acme.com.

​
When to call it

  • After writing a meeting brief → save it to the contact so the next meeting can reference it
  • After a call → keep the transcript or your notes on the record
  • When you produce durable research about a specific contact worth keeping for next time

​
When NOT to call it

  • An interaction happened (email sent, meeting held) → record with an interaction.* event
  • A change to the user’s own GTM (repriced, moved upmarket) → update_gtm_profile

​
Backed by

POST /v2/notes — see the HTTP reference for the raw JSON shape.