> 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-contact-types.md).

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

This workflow retrieves all contact type classifications from Kaseya BMS, serving as a critical reference data component for larger client management automations. MSPs can leverage this building block when developing client onboarding processes, creating custom forms that require contact type selections, or building integrations that synchronize contact data between systems. Technically, the workflow executes a single API call to Kaseya BMS that returns the standardized contact type identifiers and descriptions available in your instance. This fundamental data retrieval function enables consistent contact categorization across your automation ecosystem, ensuring contacts are properly classified as primary, billing, technical, or other custom types your organization utilizes.

This workflow contains 1 tasks.

### Inputs

* **choose\_variable** - string

### Outputs

* **options**: Array of contact types.

### Key tasks

* **kaseya\_bms\_list\_contact\_types**: Kaseya BMS integration: List Contact Types

### Jinja example

```jinja
{{
    [
        {
        "id": contact_type.id,
        "name": contact_type.name,
        "default": true if contact_type.id|string in ORG.VARIABLES[CTX.choose_variable]|d else false
        }
        for contact_type in TASKS.kaseya_bms_list_contact_types.result.result
        if contact_type.isActive == true
    ] | sort(attribute="name") | unique(attribute="id")
}}
```

This is used for building the contact\_types 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-contact-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.