Define a customer
well_define_customerDefine one company or one private individual as a customer of this workspace: records that the workspace's own company bills it.
REQUIRED: entity_id and entity_kind, both from a row of well_list_customers, or from the company or person you just created for the customer. Pass the row's customer_kind too: "person" for a private individual (a person record), "company" for a company record. Call it only after the user chose that row on the card; never pick a customer from a name alone. A registry row's entity_id adds the company to the workspace first, then defines it.
The write is idempotent: defining a customer that is already defined succeeds with created: false. It never edits the company itself, and it refuses the workspace's own company. To bill the customer, pass the returned entity_id as the invoice's receiver company_id when customer_kind is "company", or as the receiver person_id when it is "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 |
|---|---|---|---|
| entity_id | Yes | The `entity_id` of a `well_list_customers` row. | |
| entity_kind | Yes | The row's `entity_kind`, stated rather than inferred. | |
| 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. | |
| customer_kind | No | The record `entity_id` names: "company" or "person". Left out, it names a company record. | |
| 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 | ||
| created | No | ||
| success | Yes | ||
| customer | No | ||
| error_reason | 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. |