Dashboard test surface: invoke a tool by slug (VENDOR_API)

Fire a real VENDOR_API invocation from the Integrations dashboard.

Verifies the parent connection is owned by the caller’s org (404 otherwise), then dispatches invoke_tool_by_slug so the operator can confirm the backend action path end-to-end. Emits an integration_tool_call Tinybird row with mode=vendor_api and reason="ui_slack_test_send". An unresolved/disabled slug surfaces as ToolUnavailableError (400).

The backend result stays raw (the backend path is never narrowed). For the field-picker UI we also compute narrowed here (ENG-631) — what the agent would actually receive — using the shared :func:narrow_result. Effective field map: request.response_field_map → the saved tool’s response_field_map → none (narrowed=None).

POST

integrations

connections

{connection_id}

test-invoke

Dashboard test surface: invoke a tool by slug (VENDOR_API)

curl --request POST \
  --url https://api-sandbox.featherhq.com/v1/integrations/connections/{connection_id}/test-invoke \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "slug": "<string>",
  "input": {},
  "response_field_map": {}
}
'

{
  "result": {},
  "narrowed": null
}

Authorizations

x-api-key

string

header

required

Path Parameters

connection_id

string<uuid>

required

Body

application/json

Body for the dashboard VENDOR_API test surface (Step 10).

Lets an operator fire a real invoke_tool_by_slug from the Integrations page to confirm the backend action path end-to-end. input matches the resolved tool's input_schema.

slug

string

required

input

Input · object

response_field_map

Response Field Map · object

Response

Successful Response

Raw vendor result echoed back to the dashboard test surface.

narrowed previews the agent-facing result after applying the effective field map (request override → saved field map); None when no field map applies (ENG-631).

result

Result · object

required

narrowed

unknown

Dashboard test surface: invoke an MCP tool by slug (FEATHER_MCP_CLIENT)Fire a real ``FEATHER_MCP_CLIENT`` invocation from the Integrations dashboard. Verifies the parent connection is owned by the caller's org (404 otherwise), resolves the slug to ``(connection, tool)`` via ``ToolService.resolve_by_slug``, then dispatches through our MCP client → the customer's MCP server (decrypt creds → open session → ``call_tool``). This is the only non-agent way to exercise ``FEATHER_MCP_CLIENT``, so a green result here is strong evidence the whole custom-MCP invoke path works end-to-end. Returns the raw MCP result and emits an ``integration_tool_call`` Tinybird row with ``mode=feather_mcp_client`` / ``reason="ui_mcp_test_call"``. An unresolved/disabled slug surfaces as ``ToolUnavailableError`` (400).

⌘I

Dashboard test surface: invoke a tool by slug (VENDOR_API)

curl --request POST \
  --url https://api-sandbox.featherhq.com/v1/integrations/connections/{connection_id}/test-invoke \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "slug": "<string>",
  "input": {},
  "response_field_map": {}
}
'

{
  "result": {},
  "narrowed": null
}