Send the brief of today now
well_send_brief_nowSend the person their brief of today now, the same brief their scheduled routine sends.
Call it when the person asks for the point or for the brief of the day now: "fais-moi le point", "on fait le point ?", "fais-moi mon brief du matin", "give me my morning brief", "catch me up on today", "send me my brief now". It takes no argument and acts only on the caller's own brief routine.
Do not call it for a question about one invoice or one client, such as "fais-moi le point sur la facture 42": that is a read about one item, not the brief.
Reply in one line per status: the brief is on its way, a brief is already on its way, or every brief routine is off. In that case say a brief turns back on with well_update_schedule, status "active", on its routine. When the call fails, say the brief could not be started and to try again later; never say a brief is on its way and never say the briefs are off.
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 |
|---|---|---|---|
| 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 |
|---|---|---|---|
| error | No | ||
| status | No | `started`: the brief is on its way. `already_running`: a brief of this routine is still in flight. `brief_off`: every brief routine of the person is off. | |
| success | Yes | True when the call ran, whether the brief started or not. | |
| variant | No | The brief that runs: morning, afternoon or end of day. Null when every brief routine is off. | |
| 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. |