> 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/getworkflowtargetsresponse.md).

# GetWorkflowTargetsResponse

Response containing the target surfaces of a workflow execution

Audience: Programmer

Response type returned by the `workflowTargets` query. Contains the list of target surfaces currently declared on a workflow execution.

## Fields

| Field     | Type                 | Required | Description                                                                                           |
| --------- | -------------------- | -------- | ----------------------------------------------------------------------------------------------------- |
| `targets` | `[WorkflowTarget!]!` | Yes      | The list of currently declared target surfaces. Empty when the workflow has not declared any targets. |

## Description

This type wraps the contents of the `pyck_workflow_targets` KeywordList search attribute for a workflow execution. The `targets` field is always present and non-nullable, but the list itself may be empty.

## Example Response

### Workflow with Multiple Targets

```json
{
  "data": {
    "workflowTargets": {
      "targets": ["WEB", "MOBILE"]
    }
  }
}
```

### Workflow with a Single Target

```json
{
  "data": {
    "workflowTargets": {
      "targets": ["SETUP"]
    }
  }
}
```

### Workflow Without Targets

```json
{
  "data": {
    "workflowTargets": {
      "targets": []
    }
  }
}
```

## Notes

* The `targets` list is non-nullable but may be empty.
* Each entry is a `WorkflowTarget` enum value (`WEB`, `MOBILE`, or `SETUP`).
* The response reflects the current state of the search attribute at the time of the query.
* Targets can be modified using the [setWorkflowTargets](/graphql-api/mutations/setworkflowtargets.md) mutation.

## Related Documentation

* Query: [workflowTargets](/graphql-api/queries/workflowtargets.md)
* Input: [GetWorkflowTargetsInput](/graphql-api/inputs/getworkflowtargetsinput.md)
* Type: [SetWorkflowTargetsResponse](/graphql-api/types/setworkflowtargetsresponse.md)
* Enum: [WorkflowTarget](/graphql-api/enums/workflowtarget.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/getworkflowtargetsresponse.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.