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

# Update Workflow Status

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

<span data-api-safety-label="changes-state"><Badge color="yellow" size="sm" shape="pill">Changes state - verify before retry</Badge></span>

Changes the execution status of a workflow. This is NOT a read-only action. Valid actions: activate (start, must be in draft status; blocking validation errors fail the call — common causes: multiple or zero entry nodes, unreachable nodes, missing CONVERTED/DROPPED nodes, call get\_workflow\_structure first to catch these before activating) and resume (continue a paused workflow) both return non-blocking warnings in the response when present — e.g. the agent bound to a call node changed since this workflow was last configured — relay these to the user rather than ignoring them. pause/deactivate (halt new leads entering, in-progress ones continue) has no such warnings.

## Parameters

| Name          | Type                                                    | Required | Description                            |
| ------------- | ------------------------------------------------------- | -------- | -------------------------------------- |
| `workflow_id` | `string`                                                | Yes      | The workflow ID, e.g. workflow\_abc123 |
| `action`      | enum: `activate` \| `deactivate` \| `pause` \| `resume` | Yes      | The status transition to apply         |

## 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`, `action`.

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

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

## Related MCP tools

* [Get Workflow Structure](/docs/mcp-tools/workflows/get-workflow-structure): `get_workflow_structure`
* [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)