Save a file to the drive folder
well_save_file_to_driveSave one Well document (a receipt, an invoice, a statement) in the Well folder of the workspace's connected Google Drive. Call it when the user asks to save, copy or put a document in Drive.
Pass document_id: the Well document, never an invoice id. Pass file_name only when the user names the file; it defaults to the document's file name. The user confirms on a card before the save.
Well writes only in the Well folder it created in the user's Drive. When an earlier save of the same document made a file there, the call replaces its content and keeps its link (outcome: "updated"): it never makes a duplicate. A file of another document is never replaced, even when the names match. Only the member who connected Google Drive can save 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 failed or unconfirmed, never say the file is in Drive.
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 |
|---|---|---|---|
| file_name | No | The file name in Drive, only when the user names it. | |
| document_id | Yes | The Well document to save in Google Drive. | |
| 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 save to, only when several Drive accounts are connected. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| message | No | ||
| outcome | No | ||
| success | Yes | ||
| file_name | No | ||
| drive_file_id | No | ||
| web_view_link | 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 |