> For the complete documentation index, see [llms.txt](https://docs.rewst.help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rewst.help/documentation/automations/subworkflows/rewst-master-v2-psa-kaseya-get-issuetypes.md).

# \[Rewst Master v2] PSA-Kaseya: Get IssueTypes

This workflow pulls the full list of issue types from Kaseya BMS via an authenticated API call, making it essential for ticket categorization and routing automation. MSPs can use it to build dynamic ticket creation flows, trigger actions based on issue types, or populate forms without hardcoding values. It ensures downstream processes always reference up-to-date issue classifications, helping maintain consistent, accurate ticket handling across the service desk.

This workflow contains 1 task.

### Inputs

* **choose\_variable** - string

### Outputs

* **options**: Array of issue types.

### Key tasks

* **kaseya\_get\_issues**: Data retrieval

### Jinja example

```jinja
{{
    [
        {
            "label": issue.name,
            "id": issue.id,
            "default": true if issue.id == ORG.VARIABLES[CTX.choose_variable]|d|int else false
        }
        for issue in TASKS.kaseya_get_issues.result.result
        if issue.isActive == true
    ] | unique(attribute='id')
}}
```

This is used in defining the issueType data alias.


---

# 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.rewst.help/documentation/automations/subworkflows/rewst-master-v2-psa-kaseya-get-issuetypes.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.