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

# SetAssigneeInput

SetAssigneeInput Input Type

Audience: Programmer

Input type for the `setAssignee` mutation that updates the assignee of a running workflow instance.

## Fields

| Field           | Type      | Required | Description                                                                                           |
| --------------- | --------- | -------- | ----------------------------------------------------------------------------------------------------- |
| `workflowID`    | `String!` | Yes      | The unique identifier of the workflow instance to update                                              |
| `workflowRunID` | `String!` | Yes      | The run ID of the workflow instance to update                                                         |
| `assigneeID`    | `ID`      | No       | The user ID to assign to the workflow. If null or omitted, defaults to the current authenticated user |

## Usage

This input type is used with the `setAssignee` mutation to specify which workflow instance to update and who should be assigned to it.

### Example with specific assignee

```graphql
{
  workflowID: "picking-workflow-12345",
  workflowRunID: "abc123de-f456-7890-ghij-klmnopqrstuv",
  assigneeID: "user_456789"
}
```

### Example with current user (omit assigneeID)

```graphql
{
  workflowID: "receiving-workflow-67890",
  workflowRunID: "xyz987fe-d321-6543-mnop-qrstuvwxyzab"
  # assigneeID omitted - will default to current user
}
```

## Field Details

### workflowID

The workflow instance identifier in Temporal. This is typically a business-meaningful ID that uniquely identifies a workflow execution along with the `workflowRunID`.

### workflowRunID

The run ID of the workflow instance. This is a UUID generated by Temporal that, combined with the `workflowID`, uniquely identifies a specific workflow execution.

### assigneeID

Optional field that specifies the user to assign to the workflow. When not provided:

* The mutation will automatically use the current authenticated user's ID
* This ensures that a workflow always has an assignee after the operation

## Related

* Mutation: [`setAssignee`](/graphql-api/mutations/setassignee.md)
* Response Type: [`SetAssigneeResponse`](/graphql-api/types/setassigneeresponse.md)
* Query: [`workflowAssignee`](/graphql-api/queries/workflowassignee.md)


---

# 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/setassigneeinput.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.