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

# Get Workflow Structure

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

Read only

Returns all nodes and edges currently in a workflow's graph — use this to see the workflow's steps and how they connect, and to check it is complete before it is activated in the dashboard (confirm START has one outgoing edge and no incoming edges, every other node is reachable from START, and a CONVERTED and DROPPED node both exist and are connected).

## Parameters

| Name | Type | Required | Description |
| - | - | - | - |
| `workflow_id` | `string` | Yes | The workflow ID, e.g. workflow\_abc123 |

## Complete input schema

```json theme={null}
{
  "type": "object",
  "properties": {
    "workflow_id": {
      "type": "string",
      "description": "The workflow ID, e.g. workflow_abc123"
    }
  },
  "required": [
    "workflow_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
```

## Registered output schema

```json theme={null}
{
  "type": "object",
  "properties": {
    "nodes": {
      "type": "array",
      "description": "All nodes in the workflow graph, each with a prefixed node_ id, node_type, label, and config"
    },
    "edges": {
      "type": "array",
      "description": "All directed edges in the workflow graph, each with prefixed edge_/node_ ids and an optional label"
    }
  },
  "required": [
    "nodes",
    "edges"
  ],
  "additionalProperties": true,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
```

## 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`.
* If your OAuth grant covers several workspaces, also pass `organization_id` with the workspace to act in, from [List My Organizations](https://dialnexa.com/docs/mcp-tools/organization/list-my-organizations.md).

## 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": "get_workflow_structure",
    "arguments": {
      "workflow_id": "workflow_abc123"
    }
  }
}
```

Successful results include `structuredContent` and a text content block containing the same JSON. Check `isError` first, then read `structuredContent` or parse `content[0].text`. See [MCP responses and errors](https://dialnexa.com/docs/mcp-tools/errors.md) for the full envelope and failure behavior.

## Verify the result

Confirm the response is not marked `isError`, parse `content[0].text` as JSON, and verify that returned IDs and workspace data match the request.

## Retry safety

This tool does not change workspace data. Retrying after a transient transport failure is safe.

## Related guides

* [Connect to the DialNexa MCP server](https://dialnexa.com/docs/mcp-tools/overview.md)
* [Workflows MCP tools](https://dialnexa.com/docs/mcp-tools/workflows/overview.md)
* [MCP responses and errors](https://dialnexa.com/docs/mcp-tools/errors.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.