List mail senders
well_list_mail_sendersList the member's newsletter senders from live email records in the requested window. It returns counts, the last received date, a recent subject, the member's own saved choice and observed coverage. Each sender row carries person, the id of the single live person of the workspace holding the sender address, or null when no person or more than one holds it; never present a null person as a known person. To name that person, open it with well_get_entity on root "people" and its person_id, and never show the id itself as the person. It never reads a live mailbox. It covers list mail marked by the provider; Promotions, Social and Forums are not ingested. mailbox is the address of the member's own connected Gmail in this workspace, or null when none is connected, so an answer can name the account. status says whether the read ran: read (it ran, so an empty senders is a real "nothing there"), unavailable (it did not run: say the mail could not be read and offer to look again, never "no newsletters"). error holds the underlying text for a log, never for the person. 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 |
|---|---|---|---|
| limit | No | ||
| window_days | No | ||
| 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 |
|---|---|---|---|
| error | No | ||
| status | Yes | ||
| mailbox | Yes | ||
| senders | Yes | ||
| success | Yes | ||
| coverage | Yes | ||
| truncated | Yes | ||
| window_days | Yes | ||
| total_senders | Yes | ||
| 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. |