> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/types/getworkflowactionsresponse.md).

# GetWorkflowActionsResponse

Response containing the queries and updates available on a workflow execution

Audience: Programmer

Response type returned by the [`workflowActions`](/graphql-api/queries/workflowactions.md) query. It contains the queries and updates that are registered on a workflow execution together with each action's current `enabled` state.

## Fields

| Field     | Type                   | Required | Description                                      |
| --------- | ---------------------- | -------- | ------------------------------------------------ |
| `queries` | `[ActionDefinition!]!` | Yes      | The queries registered on the workflow execution |
| `updates` | `[ActionDefinition!]!` | Yes      | The updates registered on the workflow execution |

Both lists are non-nullable. When no matching actions are registered, the respective list is empty (`[]`).

## Description

* `queries` are Temporal workflow **queries**: side-effect-free handlers that inspect workflow state and return a value without changing it.
* `updates` are Temporal workflow **updates**: handlers that can validate input and mutate workflow state.

Each entry is an [`ActionDefinition`](/graphql-api/types/actiondefinition.md) that describes a single handler. Because workflows register and deregister handlers as they progress, the content of this response reflects the state of the workflow at the time the query was executed.

## Example Response

```json
{
  "data": {
    "workflowActions": {
      "queries": [
        {
          "name": "getStatus",
          "description": "Returns the current status of the workflow",
          "enabled": true
        }
      ],
      "updates": [
        {
          "name": "confirmPick",
          "description": "Confirm that a pick has been completed",
          "enabled": true
        },
        {
          "name": "cancelPick",
          "description": "Cancel the current pick and release the reservation",
          "enabled": false
        }
      ]
    }
  }
}
```

### Empty Response

When a workflow has no registered handlers, or all actions are filtered out by the `where` argument, both lists are empty:

```json
{
  "data": {
    "workflowActions": {
      "queries": [],
      "updates": []
    }
  }
}
```

## Notes

* The `enabled` flag on each entry indicates whether the action is currently callable. A handler may be registered but temporarily disabled depending on the workflow's current state.
* To retrieve only currently callable actions, pass `where: { enabled: true }` to the query.

## Related

* Query: [workflowActions](/graphql-api/queries/workflowactions.md)
* Input: [GetWorkflowActionsInput](/graphql-api/inputs/getworkflowactionsinput.md)
* Input: [WorkflowActionsWhereInput](/graphql-api/inputs/workflowactionswhereinput.md)
* Type: [ActionDefinition](/graphql-api/types/actiondefinition.md)

## Service

This type is defined in the **workflow** service as part of the federated GraphQL schema.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/types/getworkflowactionsresponse.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.