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

# GetAssigneeResponse

Response containing workflow assignee information

Audience: Programmer

Response type returned by the `workflowAssignee` query containing the assignee information for a workflow run.

## Fields

| Field      | Type      | Required | Description                                      |
| ---------- | --------- | -------- | ------------------------------------------------ |
| `assignee` | `String!` | Yes      | The ID of the user assigned to this workflow run |

## Description

This type represents the response from querying a workflow's assignee. The assignee value is retrieved from the workflow's search attributes in Temporal under the key `pyck_workflow_assignee`.

## Example Response

```json
{
  "data": {
    "workflowAssignee": {
      "assignee": "user-12345"
    }
  }
}
```

### Empty Assignee

If no assignee is set for the workflow, the field returns an empty string:

```json
{
  "data": {
    "workflowAssignee": {
      "assignee": ""
    }
  }
}
```

## Notes

* The assignee ID typically corresponds to a user in the system's identity management (Zitadel)
* The assignee can be set or updated using the `setWorkflowAssignee` mutation
* An empty string indicates no assignee is currently assigned to the workflow

## Related

* Query: [workflowAssignee](/graphql-api/queries/workflowassignee.md)
* Input: [GetAssigneeInput](/graphql-api/inputs/getassigneeinput.md)
* Input: [SetAssigneeInput](/graphql-api/inputs/setassigneeinput.md)
* Type: [SetAssigneeResponse](/graphql-api/types/setassigneeresponse.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/getassigneeresponse.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.