Request Integration Access - DialNexa Documentation

Changes state - verify before retry Requests access to an integration that’s currently disabled by admin — posts a notification for the team to review, it does not enable the integration itself. Use list_integrations first to check whether the tool is actually disabled (this fails if it’s already enabled).

Parameters

Name	Type	Required	Description
`tool_key`	`string`	Yes	The tool key being requested, e.g. “gmail” — from list_integrations
`usage_context`	`string`	No	Optional: what the org wants to use this integration for

Before you call

Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
Provide the required parameters: tool_key.

Example MCP request

Send tools/call after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "request_integration_access",
    "arguments": {
      "tool_key": "VALUE"
    }
  }
}

The server returns one text content block. Parse content[0].text as JSON when the tool succeeds. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Confirm the response is not marked isError. Call List Integrations to read the affected resource. Verify that the intended state is visible before making another change.

Retry safety

This tool changes workspace state. After a timeout, read the affected resource before retrying so you do not create duplicate or conflicting changes.

List Integrations: list_integrations