Send a task's documents as one zip file
well_send_browser_task_documentsSend every PDF a finished documents task filed, as one ZIP file in this WhatsApp conversation (more ZIP files only when the PDFs pass WhatsApp's file size).
Call it when the person asks for the PDFs of a documents task Well already reported, such as "envoie-les moi", "envoie-moi les PDF", "send them to me", after Well's report gave the count and the link instead of the PDFs. Omit task_id for the task Well reported last in this conversation; name it when the person means another one.
Say in one line what went out: one ZIP with the count of PDFs, or the count of ZIP files. When too_big is above 0, say that many PDFs are too large for WhatsApp and stay in Well. When the status is not sent, say so plainly; never say a file went out that did not.
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 | No | The Well task (a browser task) whose documents go out. Omitted, the documents task of this conversation that Well reported last. | |
| 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 |
|---|---|---|---|
| sent | No | How many of those ZIP files reached the person. | |
| error | No | ||
| parts | No | How many ZIP files the documents make; one unless they pass WhatsApp's size. | |
| status | No | `sent`: the ZIP files went out. `no_reported_task`: this conversation holds no documents task Well reported for the person. `nothing_filed`: the task filed no document Well can read back. `not_whatsapp`: the call ran outside a WhatsApp conversation. | |
| success | Yes | True when the call ran, whether files went out or not. | |
| too_big | No | How many PDFs are larger than one WhatsApp file and went in no ZIP. | |
| documents | No | How many PDFs the ZIP files hold. | |
| 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. | |
| 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. |