> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Workflow Edge

> Use the delete_workflow_edge MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="destructive"><Badge color="red" size="sm" shape="pill">Destructive</Badge></span>

Removes a single connection between two nodes, and clears the matching entry from the source node's routing config (config.outputs/config.output) so it can't keep silently routing to a node with no structural edge behind it. This is NOT reversible, though re-adding it with add\_workflow\_edge is straightforward if needed. Edges FROM a CONDITIONAL/TIME/APPLICATION node cannot be deleted outright — those node types always require every route to be set (validateNodeConfig rejects clearing it), so removing one would leave the node in a state it can never be saved in again. Use add\_workflow\_edge with a different to\_node\_id to REPLACE where such a route points instead.

## Parameters

| Name          | Type     | Required | Description                                                    |
| ------------- | -------- | -------- | -------------------------------------------------------------- |
| `workflow_id` | `string` | Yes      | The workflow ID, e.g. workflow\_abc123                         |
| `edge_id`     | `string` | Yes      | The edge ID, e.g. edge\_abc123 — from get\_workflow\_structure |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* Provide the required parameters: `workflow_id`, `edge_id`.
* Confirm the exact target and intended effect with the user before calling.

## 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.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "delete_workflow_edge",
    "arguments": {
      "workflow_id": "workflow_abc123",
      "edge_id": "edge_abc123"
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/errors) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`. Call [Get Workflow Structure](/docs/mcp-tools/workflows/get-workflow-structure) to read the affected resource. Verify that the target is removed or disconnected before reporting completion.

## Retry safety

This tool can remove or disconnect a resource. Confirm the exact target first, and do not retry after an uncertain result until you verify the current state.

## Related MCP tools

* [Get Workflow Structure](/docs/mcp-tools/workflows/get-workflow-structure): `get_workflow_structure`
* [Add Workflow Edge](/docs/mcp-tools/workflows/add-workflow-edge): `add_workflow_edge`
* [List Workflows](/docs/mcp-tools/workflows/list-workflows): `list_workflows`
* [Get Workflow](/docs/mcp-tools/workflows/get-workflow): `get_workflow`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Workflows MCP tools](/docs/mcp-tools/workflows/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)