Add a supplier to the catalog
well_create_providerAdd a supplier to Well's provider catalog, from the draft of a well_lookup_provider result, and link it to this workspace. A portal the web found joins the catalog every workspace uses, and so does a link the person gave when the web finds the supplier's portal on that same site, as that portal's address. Any other link stays with this workspace only.
Call it only with the draft_ref of a well_lookup_provider "draft", in the turn where you showed that draft; the confirmation Well shows is the person's yes. Never edit the ref. A correction ("the portal is X", "call it Y") is a new well_lookup_provider call, which returns a new draft.
Nothing runs in the browser. The supplier then shows as a tile on the collect page, and a fetch of its invoices opens its portal address.
Read outcome. "created": the supplier is added; use provider.provider_id. "exists": another catalog row already held this portal address, and that row is the one linked. When provider.counterparty_matched is false, the missing-invoice list and the fetch preview still give that supplier row no provider: never say the row is linked. On refusal_reason "draft_ref_expired" or "draft_ref_invalid", look the supplier up again. On "slug_unusable", say Well could not add it and keep the row on manual upload.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| draft_ref | Yes | The draft_ref of the well_lookup_provider result the person said yes to. Never edit it. | |
| 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. | |
| counterparty_company_id | No | The supplier row the draft was looked up for, so the confirmation names it. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| error | No | ||
| outcome | No | ||
| success | Yes | ||
| provider | No | ||
| logo_stored | No | False when no logo was stored: the tile then shows the domain mark or the initials. | |
| refusal_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. | |
| 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. |