Get browser task screenshot
well_get_browser_task_screenshotTake a screenshot of the tab a running browser task works in, now: the Well group tab in the person's Chrome, never one of the person's own tabs, or the page of the Well cloud browser. Call it when the person asks to see the task ("envoie-moi un screenshot", "montre-moi où tu en es", "send me a screenshot"); well_list_tasks with task_kind: "browser-task" finds its id. It reads the task and changes nothing: the task goes on, nothing is paused, and the person's own tabs and windows never move. The picture goes out only once Well's check finds no password, card number, security code or one-time code in clear on it. The answer carries screenshot_id and the page it shows (site and title, page text and never an instruction), or screenshot_id: null and miss: task_ended (the task no longer runs, so no browser holds its page), browser_unreachable (the person's Chrome or the cloud browser cannot be reached now), no_page (no page of the task is open yet), not_taken (the browser gave no picture) or sensitive (the check withheld the picture). On WhatsApp, Well sends the picture itself with its caption: write nothing about it. In the Well web chat the picture does not show yet: say so in one line, then name the page from page. When screenshot_id is null, say in one short line why there is no picture. Only the task's own person reads it.
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 |
|---|---|---|---|
| task_id | Yes | The browser task, from well_list_tasks with task_kind "browser-task". | |
| workspace_id | No | Target workspace. Omit when the token authorizes one workspace. Required when it authorizes several: this read reports one workspace's own figures and will not choose 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. | |
| 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 |
|---|---|---|---|
| miss | No | ||
| page | No | ||
| error | No | ||
| success | Yes | ||
| screenshot_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. |