# One workflow and its draft's problems

One automation rule in full — its trigger, its steps, its status — plus the problems its CURRENT DRAFT has, so a builder can flag the canvas the moment it opens. Those problems are the same ones a publish refuses on. Reading changes nothing; the frozen words a run is actually executing are in `get_workflows_id_versions`.

Access class: `workspace`.

## Endpoint

`GET /v1/workflows/{id}`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| id | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```