> ## 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 Details
> Fetch one workflow by ID.
Read only
**Recommended.** This endpoint is part of the public `/v1` API reference and is the supported path for new integrations. See the [migration guide](/docs/api-reference/v1/migrating-to-v1) for versioning guidance.
Returns the complete record for a single workflow: the display `name`, `description`, current `status` (such as `active`, `paused`, or `cancelled`), the totals of nodes and edges in the graph, the enrolled-lead count, and creation/update timestamps. This endpoint does not return the nodes or edges themselves, fetch those separately through [List Nodes](/docs/api-reference/workflow-nodes/list) and [List Edges](/docs/api-reference/workflow-edges/list) when you need the full graph structure.
## When to use this
* **Workflow dashboards**: render the workflow's header summary (name, status, lead count) before lazy-loading the graph.
* **Pre-update checks**: confirm the workflow status is `paused` or `inactive` before applying structural edits.
* **Reporting**: pull live counts of enrolled leads alongside historical call logs from [List Call Logs](/docs/api-reference/call-logs/list).
To enumerate every workflow on the workspace, use [List Workflows](/docs/api-reference/v1/workflows/list).
## Path parameters
| Parameter | Description |
| --------- | ------------------------------------------------ |
| `id` | The workflow ID, for example `wfl_m3v7zb9rk2px`. |
## Errors
* `404 Not Found` is returned when the workflow does not exist or has been deleted.
* `403 Forbidden` is returned when the API key cannot read workflows on this workspace.
## Related endpoints
* [List Nodes](/docs/api-reference/workflow-nodes/list): retrieve the workflow's node set.
* [List Edges](/docs/api-reference/workflow-edges/list): retrieve the transitions between nodes.
* [Update Workflow Status](/docs/api-reference/v1/workflows/status): activate, pause, deactivate, or resume the workflow.
* [List Workflow Leads](/docs/api-reference/v1/workflow-leads/list): see which leads are enrolled.
## OpenAPI
````yaml GET /v1/workflows/{id}
openapi: 3.0.0
info:
title: DialNexa API
description: >-
Public REST API for the DialNexa voice AI platform. Versioned endpoints are
under /v1; unversioned endpoints are legacy and deprecated.
version: 1.0.0
servers:
- url: https://api.dialnexa.com
description: DialNexa production API
security:
- bearer: []
tags:
- name: API Keys
- name: Agent Functions
- name: Agents V1
- name: Agents2
- name: Batch Calls
- name: Batch Calls V1
- name: Call Logs
- name: Calls
- name: Calls V1
- name: Campaign Leads
- name: Campaigns
- name: External Webhooks
- name: Knowledge Base
- name: Knowledge Base V1
- name: LLMs
- name: LLMs V1
- name: Languages
- name: Languages V1
- name: Organization Phone Numbers
- name: Organization Phone Numbers V1
- name: Phone Number Pricing
- name: Phone Number Pricing V1
- name: Transcribers
- name: Transcribers V1
- name: User Webhooks
- name: User Webhooks V1
- name: V1
- name: Voices
- name: Voices V1
- name: Webcall
- name: Workflow Leads
- name: Workflow Leads V1
- name: Workflows
- name: Workflows V1
paths:
/v1/workflows/{id}:
get:
tags:
- Workflows V1
- V1
summary: Get Workflow Details
description: Returns one workflow and its current lifecycle state.
operationId: WorkflowsV1Controller_findOne
parameters:
- name: id
required: true
in: path
description: Workflow ID
schema:
type: string
example: workflow_abc123
responses:
'200':
description: Workflow fetched successfully.
content:
application/json:
schema:
type: object
properties:
statusCode:
type: number
example: 200
message:
type: string
example: Workflow fetched successfully
data:
type: object
properties:
id:
type: string
example: workflow_abc123
title:
type: string
example: Q3 Outreach Workflow
status:
type: string
enum:
- draft
- active
- paused
- completed
- cancelled
example: active
description:
type: string
nullable: true
example: Automated follow-up sequence
createdAt:
type: string
format: date-time
updatedAt:
type: string
format: date-time
examples:
success:
summary: Successful response
value:
statusCode: 200
message: Workflow fetched successfully
data:
id: workflow_abc123
title: Q3 Outreach Workflow
status: active
description: Automated follow-up sequence
createdAt: '2026-07-03T10:30:00.000Z'
updatedAt: '2026-07-03T10:45:00.000Z'
'400':
description: Invalid workflow ID format.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 400 Bad Request
value:
statusCode: 400
message: Workflow validation failed
error: Bad Request
'401':
description: Unauthorized - missing or invalid API key.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 401 Unauthorized
value:
statusCode: 401
message: API key is missing or invalid
error: Unauthorized
'404':
description: Workflow not found
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 404 Not Found
value:
statusCode: 404
message: Workflow not found
error: Not Found
'500':
description: Internal Server Error
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
error:
summary: 500 Internal Server Error
value:
statusCode: 500
message: Internal server error
error: Internal Server Error
security:
- bearer: []
components:
schemas:
ErrorResponse:
type: object
properties:
statusCode:
type: integer
example: 400
message:
oneOf:
- type: string
- type: array
items:
type: string
example: phone_number must be a valid E.164 phone number
error:
type: string
example: Bad Request
required:
- statusCode
- message
- error
securitySchemes:
bearer:
scheme: bearer
bearerFormat: JWT
type: http
````