Show a tool that is not available yet
well_show_connector_requestShow the person a card for ONE tool Well cannot connect yet: the card names the tool, says where it stands in words (under maintenance, coming soon, not offered, or not in Well), and, except for a tool under maintenance, offers a request button, which asks Well to add it. Never name the button's label: the card writes it in the person's language.
Call it when the person names one tool to connect and a well_list_connectors read with that tool's slug (then q) returned no connectable row. Pass the name as the person wrote it, and the slug when a read returned one. Never offer another tool in its place, and never say Well refuses it.
When status comes back "ai_client_connects_itself", the tool is an AI app (Claude, Codex): nobody adds it to Well and no card or request exists for it. Answer in prose, in the person's language: the app connects to Well from its own settings, by adding Well's MCP server address (mcp_server_url, when set) there and signing in to Well. Never offer a request, the browser or Ajouter moi-même for it.
When status comes back "available", the tool can be connected now: draw the connect card with well_list_connectors and the slug of this result instead, and say nothing about a request. When connected is true, the workspace already holds a connection to the tool: no request card is drawn, so say in one line that it is already connected, and offer no request. When requested is true, say the workspace already asked for it.
When can_do_in_browser is true, the card also offers to do the person's task in the browser instead: its click comes back as the person's next message, and the connect-tools skill hands that task to the browser, starting on site_url when it is set. When it is false, never offer the browser in place of the tool.
When can_add_self is true, the card also offers "Ajouter moi-même": its click comes back as the person's next message, and the add-custom-connector skill adds the tool by the address of its MCP server. When it is false, never offer to add the tool oneself.
Write one line for the person, then stop: the card's button records the request and its click comes back as the person's next message. When no card is drawn and the person asks for the tool in words, call well_request_connector with the same name.
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 |
|---|---|---|---|
| name | Yes | The tool's name as the person wrote it, e.g. "Pipedrive". At most 60 characters: letters, digits, spaces and . & ' + -. Never an address, a link, an email or a domain suffix: write "Monday", not "Monday.com". | |
| slug | No | The catalog slug, when a well_list_connectors read returned one for this tool. Omit otherwise. | |
| 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 |
|---|---|---|---|
| name | No | The tool's name in a form well_request_connector accepts: the catalog name, cleaned, when the catalog carries it. Pass it back unchanged to request the tool. | |
| slug | No | The catalog slug of the matched tool, or null when it has none or the catalog does not carry the tool. Pass it as `slug` to well_list_connectors when status is available. | |
| error | No | ||
| status | No | Where the tool stands: "maintenance" (Well carries it and it is under maintenance: the card offers no request), "coming_soon", "not_offered", "absent" (not in Well), "available" (connectable now: draw the connect card instead), or "ai_client_connects_itself" (an AI app such as Claude or Codex: no card, no request; answer in prose that it connects from its own settings with `mcp_server_url`). | |
| success | Yes | ||
| site_url | No | The https home of the tool's site, from the catalog, or null when the catalog names none. A browser task for this tool may start there. | |
| connected | No | True when this workspace already holds a live connection to the tool, whatever the catalog says. No request card is drawn. | |
| requested | No | True when this workspace already asked for the tool. | |
| service_id | No | The catalog service id, or null for a tool the catalog does not carry. | |
| request_key | No | The key Well records a request for this tool under. Well reads it; never pass it to a tool. | |
| can_add_self | No | True when this person can add the tool themselves as a custom connector: an admin, in a real workspace, in a turn that can run the custom-connect write. The card shows Ajouter moi-même only then. | |
| mcp_server_url | No | Only when status is "ai_client_connects_itself": Well's MCP server address, which the person adds in the AI app's own settings to connect it to Well. Null when the address is unknown. | |
| 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. | |
| can_do_in_browser | No | True when this turn can hand the person's task to a browser instead (their Chrome with the Well extension when it can take it, a Well cloud browser otherwise). The card then offers to do the task in the browser; its pick comes back as the person's next message. | |
| 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. |