Show retargetable connectors
well_show_retargetable_connectorsDraw the connector-follow card so the USER moves a bank (or other ledger) connection from their personal workspace to this company workspace.
A connection made in a personal workspace syncs its transactions there, where they cannot post. This card lists each such connection the person may move here (they run both workspaces; this workspace may be a child or a sibling of the personal one), with how strongly it was proved to belong here and how much history moves with it, pre-ticks the strong matches, and on Confirm moves the ones the user keeps: the connection and every transaction it already synced change workspace, so nothing is pulled twice.
Draw it to SHOW the user the connectors they can bring across, let them pick which, and CONFIRM the bring-across: on the close-books bank step once at least one candidate carries a proof tier other than "no_match" and a transaction count above zero, or when the user asks to move a connection and its data to this workspace, whatever the tier and whether or not this workspace already holds transactions. Drawing the card IS that step, and it waits for the user's Confirm. ONLY when a step needs the candidate count WITHOUT the user seeing a card (a silent gate check that decides whether to offer the card at all) call well_list_retargetable_connectors instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | No | Heading for the connector-retarget card, OVERRIDING the default wording. Use it to frame the step in its flow (e.g. "Bring your bank across for the close"). At most 120 characters. Omit for the default wording. | |
| subtitle | No | Supporting line under the card's heading. At most 240 characters. Omit for the default. | |
| 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 | ||
| success | Yes | ||
| next_step | No | What to do with the card this result renders. Added by the dispatcher when the card asks for a click. | |
| candidates | 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. |