connections

Call connections.resync_custom_connector

Re-read one of this workspace's own connectors' tool list right now — 'refresh our custom connector', 'why aren't the new tools showing up'. Re-read one of this workspace's own registered connectors' tool list, right now. Use it when the operator says they have added or changed something on their own MCP server or API and the new operations are not showing up — this asks the connector again, where the connector card reports the LAST sync. It changes no setting, reads no credential and cannot remove the connector. Read read_ok first: a failed read leaves the connector exactly as it was and must never be reported as a refresh. Not for checking a new address before it is set up — that is connections.probe_connector_address.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/connections.resync_custom_connector

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/connections.resync_custom_connector
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

connector_namestring required

The connector's own name — the namespace segment its tools arrive under, so docs_search in connector.docs_search.search. It is matched against this workspace's own connectors; a name that matches none refuses rather than re-syncing something else.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 7 revisions of this API.