> ## 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 Lead History

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

Read only

Returns the full execution history for one lead within a workflow — every step it passed through, timestamps, and current status. Use list\_workflow\_leads first to find the lead\_id.

## Parameters

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

## Complete input schema

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

## Registered output schema

```json theme={null}
{
  "type": "object",
  "properties": {
    "lead": {
      "description": "The lead record (id prefixed lead_...), when present in the history payload"
    }
  },
  "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`, `lead_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_lead_history",
    "arguments": {
      "workflow_id": "workflow_abc123",
      "lead_id": "lead_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 MCP tools

* [List Workflow Leads](https://dialnexa.com/docs/mcp-tools/workflows/list-workflow-leads.md): `list_workflow_leads`

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