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

# Workflows MCP Tools

> Use DialNexa workflows MCP tools through the remote MCP server.

DialNexa workflows MCP tools let an MCP-compatible AI client build workflow graphs and manage workflow execution. Each tool page includes its exact server description, input schema, safety level, request shape, and retry guidance.

## Available Workflows MCP Tools

| Tool                                                                                      | Safety                              | What it does                                                                                                                                                                                                              |
| ----------------------------------------------------------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [`list_workflows`](/docs/mcp-tools/workflows/list-workflows)                                   | Read only                           | Returns the organization's automation workflows (multi-step call/WhatsApp sequences), each with an id and name.                                                                                                           |
| [`get_workflow`](/docs/mcp-tools/workflows/get-workflow)                                       | Read only                           | Returns details for a single workflow by ID (e.g. workflow\_abc123).                                                                                                                                                      |
| [`list_workflow_leads`](/docs/mcp-tools/workflows/list-workflow-leads)                         | Read only                           | Returns the leads enrolled in a workflow along with their current execution status (which step they're on, when they entered, when they completed).                                                                       |
| [`get_workflow_lead_variable_keys`](/docs/mcp-tools/workflows/get-workflow-lead-variable-keys) | Read only                           | Returns the distinct dynamic variable names (from the uploaded lead CSV columns) available for a workflow's leads, e.g. to know what personalization fields exist.                                                        |
| [`get_workflow_lead_history`](/docs/mcp-tools/workflows/get-workflow-lead-history)             | Read only                           | Returns the full execution history for one lead within a workflow, every step it passed through, timestamps, and current status.                                                                                          |
| [`update_workflow_status`](/docs/mcp-tools/workflows/update-workflow-status)                   | Changes state - verify before retry | Changes the execution status of a workflow.                                                                                                                                                                               |
| [`remove_workflow_lead`](/docs/mcp-tools/workflows/remove-workflow-lead)                       | Destructive                         | Removes a single lead from a workflow.                                                                                                                                                                                    |
| [`create_workflow`](/docs/mcp-tools/workflows/create-workflow)                                 | Changes state - verify before retry | Creates a new, empty workflow shell (status: draft) for the organization.                                                                                                                                                 |
| [`get_workflow_structure`](/docs/mcp-tools/workflows/get-workflow-structure)                   | Read only                           | Returns all nodes and edges currently in a workflow's graph, use this to see the current build state before deciding what to add next, to find node ids to connect with add\_workflow\_edge, and as a final self-check... |
| [`add_workflow_node`](/docs/mcp-tools/workflows/add-workflow-node)                             | Changes state - verify before retry | Adds a single node to an existing workflow.                                                                                                                                                                               |
| [`update_workflow_node`](/docs/mcp-tools/workflows/update-workflow-node)                       | Changes state - verify before retry | Updates an existing node's label and/or config (e.g. to fill in outputs once the target nodes exist, or fix a mistake).                                                                                                   |
| [`delete_workflow_node`](/docs/mcp-tools/workflows/delete-workflow-node)                       | Destructive                         | Permanently deletes a node from a workflow AND any edges connecting to or from it (cascades automatically), also clearing the matching routing entry on any node that pointed to it.                                      |
| [`add_workflow_edge`](/docs/mcp-tools/workflows/add-workflow-edge)                             | Changes state - verify before retry | Connects two existing nodes in a workflow with a directed edge, this is the recommended way to connect nodes, since it automatically keeps the source node's routing config (config.outputs/config.output, what the...    |
| [`delete_workflow_edge`](/docs/mcp-tools/workflows/delete-workflow-edge)                       | Destructive                         | 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...  |

## Before you call a tool

Connect with OAuth or a workspace API key and complete MCP initialization first. Use IDs exactly as another DialNexa tool returned them, including prefixes such as `agent_`, `call_`, and `workflow_`.

For operations that change data, verify the target and current state before the call. Billable and destructive tools require extra care because retrying an uncertain result can spend money or repeat an irreversible action.

## Related guides

* [MCP quickstart](/docs/mcp-tools/quickstart)
* [MCP responses and errors](/docs/mcp-tools/errors)
* [MCP connection and authentication](/docs/mcp-tools/overview)