> 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-task-halo-psa-update-ticket.md).

# \[REWST- TASK] Halo PSA: Update Ticket

This workflow serves as a fundamental building block that enables the programmatic updating of tickets within Halo PSA, allowing MSPs to incorporate ticket modifications into larger automation sequences without manual intervention. It's particularly valuable for scenarios requiring consistent ticket documentation during automated remediation workflows, standardizing ticket quality control processes, and maintaining detailed audit trails when multiple systems interact with a single ticket. Technically, the workflow accepts a ticket ID and update parameters, adds private notes to document automated actions, performs the requested ticket updates with quality control checks, and verifies time tracking compliance – streamlining what would otherwise be time-consuming manual documentation tasks in the PSA.

This workflow contains 8 tasks.

### Inputs

* **ticket\_id** - string
* **work\_minutes** - string
* **external\_note** - string
* **internal\_note** - string
* **complete\_workflow** - string
* **set\_ticket\_status** - string

### Outputs

* **automation\_log**: Standardized Rewst automation log

### Key tasks

* **failed**: Core integration: noop
* **complete\_workflow**: Core integration: noop
* **add\_private\_note**: HaloPSA integration: Add or Update Actions
* **update\_ticket\_qc**: Data modification
* **check\_time**: Validation/verification

### Jinja examples

#### Example 1

```jinja
{{- CTX.halo_psa_ticket.id | d(None) -}}
```

Used in publishing 'ticket\_number'

#### Example 2

```jinja
{{- CTX.halo_psa_ticket | d(None) -}}
```

Used in publishing 'ticket\_data'


---

# 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-task-halo-psa-update-ticket.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.