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

# SetWorkflowTargetsResponse

Response containing the updated target surfaces of a workflow execution

Audience: Programmer

Response type returned by the `setWorkflowTargets` mutation. Contains the list of target surfaces declared on the workflow execution after the update has been applied.

## Fields

| Field     | Type                 | Required | Description                                                                        |
| --------- | -------------------- | -------- | ---------------------------------------------------------------------------------- |
| `targets` | `[WorkflowTarget!]!` | Yes      | The list of target surfaces after the update. Empty when the targets were cleared. |

## Description

This type confirms the result of a `setWorkflowTargets` mutation. The returned `targets` list reflects the new authoritative state of the workflow's `pyck_workflow_targets` KeywordList search attribute, allowing callers to verify the operation succeeded as intended.

## Example Response

### Successful Replacement

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

### Targets Cleared

When an empty list is supplied to clear the search attribute:

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

## Notes

* The mutation has **replace** semantics — the returned list always matches the input list.
* The `targets` list is non-nullable but may be empty.
* Each entry is a `WorkflowTarget` enum value (`WEB`, `MOBILE`, or `SETUP`).
* The mutation return type itself (`SetWorkflowTargetsResponse`) is nullable, so callers should check for null before reading `targets`.

## Related Documentation

* Mutation: [setWorkflowTargets](/graphql-api/mutations/setworkflowtargets.md)
* Input: [SetWorkflowTargetsInput](/graphql-api/inputs/setworkflowtargetsinput.md)
* Type: [GetWorkflowTargetsResponse](/graphql-api/types/getworkflowtargetsresponse.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/setworkflowtargetsresponse.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.