> 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-psa-kaseya-bms-update-ticket.md).

# \[REWST- TASK] PSA-Kaseya BMS: Update Ticket

This workflow automates key ticket operations in Kaseya BMS—like adding notes, updating fields, and logging time—making it a powerful tool for managing tickets beyond just creation. MSPs can use it to handle RMM-triggered updates, enforce documentation standards, track time accurately, and meet compliance requirements. It checks that the ticket exists, applies the requested changes, and uses system roles and work types to keep data clean. This helps build full automation chains that keep tickets up to date with little manual effort.

This workflow contains 16 tasks.

### Inputs

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

### Outputs

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

### Key tasks

* **begin**: Core integration: noop
* **kaseya\_create\_external\_note**: Creation/initialisation
* **check\_time**: Validation/verification
* **kaseya\_bms\_list\_tickets**: Kaseya BMS integration: List Tickets
* **check\_notes**: Validation/verification

### Jinja example

```jinja
{{ CTX.ticket_id }}
```

This is used in input for kaseya\_bms\_update\_ticket.


---

# 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-psa-kaseya-bms-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.