Add rows to a log sheet
well_append_rows_to_drive_sheetAdd rows at the end of a log sheet that Well keeps in the Well folder of the workspace's connected Google Drive. Call it when the user asks to log, record or add rows to a Google Sheet.
Well can write only to a sheet it created in its own Drive folder. sheet_name names that sheet: the first call with a new name creates it in the Well folder, and every next call with the same name adds rows to the same sheet. Well cannot write to a sheet the user made or picked: say so and offer a Well log sheet instead.
Pass rows: one array of cells per row, in column order. Every cell is stored as typed; a value that starts with "=" stays text. The user confirms on a card before the rows are added.
When each row carries an id that names it, such as a transaction id, pass key_column: the number of the column that holds the id, 1 for column A. Well then reads that column of the sheet and adds only the rows whose id is not in it yet, and a row whose id repeats an earlier row of the same call is added once. So a repeated call, or a call whose window overlaps an earlier one, adds each row once. Two calls at the same moment on the same sheet can both add a row with the same id. The result gives rows_appended and rows_skipped, the rows left out because their id was in the sheet or earlier in the call. outcome: "already_logged" means every row was already in the sheet: it is a success, and no row was added. outcome: "too_many_rows_to_check" means the sheet holds more than 20000 rows, empty rows included, so Well cannot check it: no row was added, so offer a sheet with a new name. Without key_column, each call adds its rows once more, so never repeat a call that returned appended.
Only the member who connected Google Drive can write to it; a call by another member returns outcome: "not_connection_owner". When the caller connected several Drive accounts, the call returns outcome: "connection_choice_needed" with workspace_connector_ids: ask which one, then call again with workspace_connector_id.
Tell the user the message the result carries and give web_view_link when present. On needs_reconnect, ask the user to reconnect Google Drive. On unconfirmed, ask the user to check the sheet before a new try.
When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass workspace_id on the call.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| rows | Yes | The rows to add, each an array of cells in column order. | |
| key_column | No | The column that holds the id of each row, 1 for column A. Only the rows whose id is not in that column of the sheet yet are added. Every row must carry a non-empty id in that column. | |
| sheet_name | Yes | The name of the Well log sheet in the Well Drive folder. A new name creates the sheet. | |
| 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. | |
| workspace_connector_id | No | The Google Drive connection to write to, only when several Drive accounts are connected. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| message | No | ||
| outcome | No | ||
| success | Yes | ||
| rows_skipped | No | With key_column: the rows left out because their id was already in the sheet or earlier in the call. | |
| rows_appended | No | ||
| sheet_created | No | ||
| web_view_link | No | ||
| spreadsheet_id | 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. | |
| 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. | |
| resolved_workspace | No | The workspace that answered, when the caller named none and the token authorizes several. | |
| 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. | |
| workspace_connector_id | No | ||
| workspace_connector_ids | No |