notes.update
Change a note. Only the writer changes body or media_ids (each earlier wording is kept, up to 50 edits). Owner or office can pin or unpin it and change audience. A removed note cannot change.
| Who | Agents can call this |
| REST | POST /v1/notes/update |
| MCP tool | notes_update |
| Writes | yes, send an Idempotency-Key |
| Area | Field work (checklists, forms, time, notes, change orders, subcontractors) |
When to use it
Keep the shop's own notes on a job or one visit (notes.add). For a voice memo, transcribe it with your own speech-to-text and save the words with notes.addVoiceMemo (transcript, duration_seconds, and optionally recorded_at, transcribed_with and language); core runs no speech model and does not store the audio.
What to tell the owner
Say what you did in plain words and what happens next.
Input
| Field | Type | Required |
|---|---|---|
note_id | string (uuid) | yes |
body | string | no |
media_ids | array | no |
pinned | boolean | no |
audience | string (one of team, office) | no |
Example
POST https://doingwork.work/v1/notes/update
content-type: application/json
Idempotency-Key: 3f1c...
{
"note_id": "00000000-0000-4000-8000-000000000000"
}Output
JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are {code, message, status}.
Errors
| Code | Status | What to do |
|---|---|---|
invalid_input, invalid_token, rate_limited | Can happen on any call. See errors. |