Update transaction category rule
well_update_transaction_category_ruleSave one category rule for the current workspace. This changes the written rule for the category and changes the context hash read by Well's category rule reader.
Use this only when a workspace member directly tells Well how to file one named category. Do not use it to answer a question about a rule, or when the person says not to change anything; read the rule with well_get_column_rule instead. Use the exact short category name the person gave, in English or French, and keep the rule to what they said. If the name is not an exact category name, ask which category they mean.
REQUIRED: category, the exact short category name; rule, one line stating what belongs or does not belong in it.
The call asks for confirmation in chat. On WhatsApp, a complete direct typed order may save at once. Say it was saved only after a successful result. Returns the category key and saved rule, or { success: false, error } when nothing changed.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rule | Yes | One line with the rule the person stated, without adding an assumption. | |
| category | Yes | The exact short category name shown by Well, in English or French. | |
| 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 | ||
| rule | No | ||
| error | No | ||
| success | Yes | ||
| category | No | ||
| reply_lines | No | ||
| category_key | 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 |