Update note lines
well_update_note_linesAdd one line at the end of a note in the current workspace, now. The text already in the note stays as written.
Use this tool when the user asks to add a fact, an item or a line to a note ("Add to my customer facts: free delivery from €60", "Ajoute à la note Acme : rappel lundi"). A complete order is the yes: the line is saved at once, with no card and no question. Find the note_id first with well_query_records or well_get_entity. When more than one note could be the one meant, ask which one and add nothing.
REQUIRED: note_id, and line, the one line to add, written the way the user said it, without the "Add to …:" part.
This tool never changes or removes the text already in the note: to change or rewrite it, use well_update_note. A note that a connected tool synced in (a meeting recorder, Notion) keeps its text from that tool: the call fails and nothing changes.
Returns { success: true, line, note } on success, or { success: false, error } on failure.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| line | Yes | The one line added at the end of the note. | |
| note_id | Yes | The note the line goes into. | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which. | |
| conversation_id | No | The conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation. | |
| idempotency_key | No | Optional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation. | |
| workspace_scope | No | Restrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ||
| line | No | The line as the note now ends with it. | |
| note | No | ||
| error | No | ||
| success | Yes | ||
| reply_lines | No | ||
| conversation_id | No | The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation. | |
| near_candidates | No | ||
| newly_connected | No | Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later. | |
| conversation_id_note | No | Present only when the server opened a fresh lane, stating that no choice recorded earlier was read. | |
| conversation_id_source | No | Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened. | |
| near_candidates_truncated | No |