Search my mailbox for a receipt
well_search_mailbox_for_receiptSearch the caller's own connected Gmail, now, for one supplier's mail in a date window: the sender name or domain, from from to to inclusive, sent mail excluded. Use it for a missing receipt or invoice, one call per supplier, with the window widened by about a week on each side of the payment date because a receipt often arrives before or after the charge. It returns up to max_results messages, newest first, each with from, subject, sent_at, a short snippet, already_in_well and an open_url to the message in Gmail. Compare the snippet and subject against the gap's amount and date yourself: a message from the supplier is a find only when it fits that charge. already_in_well: true means Well's mail sync already turned that message into documents, so the receipt can be matched in Well rather than fetched. It only reads: it attaches nothing, imports nothing and contacts no one, so it needs no confirmation. mailbox is the address of the Gmail account searched, so an answer can name it. status: searched (the search ran; empty matches is a real "not in the mailbox"), no_mailbox (the caller has no connected Gmail in this workspace; another member's mailbox is never searched), needs_reconnect (the Gmail grant expired: offer to reconnect Gmail), unavailable (Gmail did not answer: say the mailbox could not be searched, never "not found").
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 |
|---|---|---|---|
| to | Yes | Last day of the window, YYYY-MM-DD, inclusive. | |
| from | Yes | First day of the window, YYYY-MM-DD, inclusive. | |
| max_results | 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. | |
| counterparty_name | Yes | The supplier's name as the missing-invoice row names it. | |
| counterparty_domain | No | The supplier's email domain when known, e.g. the matched provider's domain. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| status | Yes | ||
| mailbox | Yes | ||
| matches | Yes | ||
| success | 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. |