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

# save_note

> Keep a meeting brief, transcript, prep, or plain note on a contact's record — append-only and dated, so a contact builds a history across meetings.

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`](/mcp/tools/search-notes).

<Note>**Not the same as `record`.** [`record`](/mcp/tools/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 [`set_workspace_profile`](/mcp/tools/set-workspace-profile), not this.</Note>

## Parameters

| Name      | Type   | Required | Description                                                                                   |
| --------- | ------ | -------- | --------------------------------------------------------------------------------------------- |
| `focus`   | string | ✓        | Who to attach it to — an email, LinkedIn URL, domain, or entity UUID. **Not a bare name.**    |
| `content` | string | ✓        | The full note or document text. Kept in full for agents to read.                              |
| `type`    | enum   |          | `note` *(default)*, `meeting_brief`, `transcript`, `meeting_notes`, `pre_meeting`, `research` |
| `title`   | string |          | A short name, e.g. `Pre-meeting brief — renewal` or `Transcript — Jun 1`.                     |
| `date`    | string |          | The 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`](/mcp/tools/record) with an `interaction.*` event
* A change to the user's own GTM (repriced, moved upmarket) → [`set_workspace_profile`](/mcp/tools/set-workspace-profile)

## Backed by

`POST /v2/notes` — see the [HTTP reference](/public-api/notes) for the raw JSON shape.