> 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-priorities.md).

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

This workflow pulls all ticket priority levels from Halo PSA, making it a key tool for automations that rely on priority-based decisions. MSPs can use it for triage, SLA enforcement, or custom ticket creation where priority matters. It runs a single API call to fetch all configured priorities and their details, so parent workflows get the data they need without extra auth steps or duplicate logic, helping streamline complex automations through simple, reusable components.

This workflow contains 1 task.

### Inputs

* **sla\_id** - string
* **choose\_variable** - string

### Outputs

* **options**: Array of priorities.

### Key tasks

* **list\_priorities**: HaloPSA integration: HaloPSA API Request

### Jinja examples

#### Example 1

```jinja
{{ CTX.sla_id }}
```

Used in input parameter 'url\_path' of list\_priorities action

#### Example 2

```jinja
{{ TASKS.list_priorities.result.result }}
```

Used in publishing 'all\_priority\_info'


---

# 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-priorities.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.