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

# SetWorkflowTargetsInput

Input for replacing the target surfaces of a running workflow execution

Audience: Programmer

Input type for the `setWorkflowTargets` mutation. Identifies the running workflow execution and supplies the complete list of target surfaces that should replace the existing ones.

## Fields

| Field                 | Type                 | Required | Description                                                                        |
| --------------------- | -------------------- | -------- | ---------------------------------------------------------------------------------- |
| `workflowId`          | `String!`            | Yes      | The unique identifier of the workflow                                              |
| `workflowExecutionId` | `String!`            | Yes      | The specific run ID of the workflow execution                                      |
| `targets`             | `[WorkflowTarget!]!` | Yes      | The full list of targets to set. Pass an empty list to clear the search attribute. |

## Usage

This input type is used with the `setWorkflowTargets` mutation to update the `pyck_workflow_targets` KeywordList search attribute on a running workflow execution.

The semantics are **replace**, not merge — the supplied list becomes the new authoritative set.

### Example: Set Multiple Targets

```graphql
mutation {
  setWorkflowTargets(input: {
    workflowId: "picking-order-12345"
    workflowExecutionId: "run-abc-123"
    targets: [WEB, MOBILE]
  }) {
    targets
  }
}
```

### Example: Clear All Targets

```graphql
mutation {
  setWorkflowTargets(input: {
    workflowId: "picking-order-12345"
    workflowExecutionId: "run-abc-123"
    targets: []
  }) {
    targets
  }
}
```

## JavaScript Example

```javascript
const variables = {
  input: {
    workflowId: "picking-order-12345",
    workflowExecutionId: "run-abc-123",
    targets: ["WEB", "MOBILE"]
  }
};
```

## Validation

The mutation will validate that:

* `workflowId` is not empty
* `workflowExecutionId` is not empty
* Each entry in `targets` is a valid `WorkflowTarget` enum value (`WEB`, `MOBILE`, or `SETUP`)
* The workflow exists, is running, and is accessible in the Temporal workflow engine
* The workflow's state object implements the `WorkflowTargetsSetter` SDK interface
* The caller has appropriate permissions and tenant access

## Related Documentation

* Mutation: [setWorkflowTargets](/graphql-api/mutations/setworkflowtargets.md)
* Type: [SetWorkflowTargetsResponse](/graphql-api/types/setworkflowtargetsresponse.md)
* Input: [GetWorkflowTargetsInput](/graphql-api/inputs/getworkflowtargetsinput.md)
* Enum: [WorkflowTarget](/graphql-api/enums/workflowtarget.md)

## Service

This input type is defined in the **workflow** service.


---

# 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/inputs/setworkflowtargetsinput.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.