> 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-datto-list-ticket-types.md).

# \[Rewst Master v2] PSA-Datto: List Ticket Types

This workflow retrieves all available ticket types and their definitions from Datto Autotask PSA, serving as a fundamental building block for more complex automation workflows that need to reference or manipulate ticket categories. MSPs would find this valuable when creating ticket automation that requires type validation, implementing conditional workflows based on ticket classifications, or standardizing ticket categorization across client organizations. Technically, the workflow executes a single API call to Datto PSA using the "tickets\_query\_field\_definitions" action, which fetches field definitions including the picklist values containing available ticket types and their configurations. This data becomes essential for downstream automations that need to programmatically create, update, or route tickets with the correct type designation, ensuring data consistency and proper ticket handling in your PSA system.

This workflow contains 1 task.

### Inputs

* **choose\_variable** - string

### Outputs

* **options**: Array of ticket type objects.

### Key tasks

* **list\_ticket\_types**: Datto Autotask PSA integration: List Ticket Fields with Picklists

### Jinja example

```jinja
{%- set all_issues = [] -%}

{%- for item in TASKS.list_ticket_types.result.result.fields -%}
  {% if item.isPickList == true and item.name == "issueType" %}
    {%- set tmp = item.picklistValues | list -%}
    {% for issues in tmp %}
      {%- set is_default = issues.value in ORG.VARIABLES[CTX.choose_variable]|d -%}
      {%- set tmp2 = all_issues.append({"label": issues.label, "id": issues.value, "default": is_default}) -%}
    {% endfor %}
  {% else %}
  {% endif %}
{% endfor %}

{{- all_issues | list -}}
```

This is used in publishing 'ticket\_types'.


---

# 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-datto-list-ticket-types.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.