> 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-halo-get-company-type.md).

# \[Rewst Master v2] PSA-Halo: Get Company Type

This building block workflow retrieves a list of company types from Halo PSA through an authenticated API request, providing standardized client classification data that can be consumed by parent workflows. MSPs can leverage this component in automation scenarios requiring client type distinction, such as customizing onboarding processes, applying different SLA rules based on company categories, or routing tickets according to client classification. Technically, the workflow executes a single API call to Halo PSA's company types endpoint, returns the standardized list, and makes it available for conditional logic in more complex workflows. This reusable function eliminates redundant API calls across multiple workflows while ensuring consistent company type data is available for decision-making throughout your automation ecosystem.

This workflow contains 1 task.

### Inputs

* **choose\_variable** - string

### Outputs

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

### Key tasks

* **list\_company\_types**: HaloPSA integration: HaloPSA API Request

### Jinja example

```jinja
{{ [
    {
        "id": companytypes.id,
        "name": companytypes.name,
        "default": true if companytypes.id|string in ORG.VARIABLES[CTX.choose_variable]|d else false
    }
    for companytypes in TASKS.list_company_types.result.result
    ]
}}
```

The above Jinja is used for building out the options for the options output.


---

# 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-halo-get-company-type.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.