> 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/rewst-documentation/documentation/integrations/integration-guides/kaseya-bms-integration-setup.md).
# Kaseya BMS integration
This document outlines the requirements and setup for the Kaseya BMS integration.
{% hint style="info" %}
If you’re new to integrations in Rewst, read through our introductory integration documentation [here](https://docs.rewst.help/documentation/integrations).
{% endhint %}
## What does the Kaseya BMS integration do?
Our Kaseya BMS integration enables the automation of ticket creation, updates, and management directly from workflows, ensuring seamless synchronization between service requests and business operations. It allows for automated time entry and billing updates, reducing manual effort and improving accuracy. If desired, the integration could trigger Rewst workflows based on ticket events.
### Why use the Kaseya BMS integration?
* Automatically trigger workflows based on specific ticket types, updates, or subjects. By leveraging designated trigger types, you can pass ticket data directly into workflows, ensuring you have access to the necessary information exactly when you need it.
* Log workflow results at key stages, enabling Helpdesk staff to quickly and easily track the progress of workflows, such as onboarding processes.
* Add internal and external notes, allowing you to run automations and show information only to those who need it.
* Integrate seamlessly with AI, Using our AI integrations you can leverage the power of OpenAi and Azure OpenAi to set ticket categories and sentiment or even suggest steps for your team to take.
* Create Ticket Time Entries, eliminating manual data entry, ensuring accurate time tracking, improving billing efficiency, and enhancing SLA compliance—boosting productivity while reducing human error.
* Import all PSA customers into Rewst, streamlining initial setup and saving valuable time.
## Set up the Kaseya BMS integration
{% hint style="warning" %}
Rewst requires an OTP token to access the Kaseya BMS API. You’ll need to create a regular user account, as Kaseya doesn't allow OTP Tokens to be generated on API users.
{% endhint %}
### Set up steps in Kaseya BMS
1. Log in to Kaseya BMS with an administrative account.
2. Navigate to **Admin > HR > Employees**.
3. Click +**New**.\
4. Create your new user with an easily identifiable name. Set the user type to **Employee**. Use the **Administrator** security role to ensure that the API has the necessary permissions for Rewst to integrate seamlessly. Note that you must use a valid email address to set up this account. That email will be used for further setup steps later in the process.
5. Log out of your current Kaseya sessions. Log in as the newly created user.
6. Navigate to **My Profile**. As this is your first time logging in, Kaseya should display this page at login.
7. Click **Enable MFA**.
8. Click **Show secret key for manual configuration** in the dialog that appears. Copy and save this code, which you’ll need to finish setup in Rewst.\
\
.png)
9. Configure MFA with your preferred app.
10. Click **Enable**.
### Set up steps in Rewst
1. Navigate to **Integrations** in the left side menu of your Rewst platform.
2. In the Integrations page, search for the `Kaseya BMS` integration.
3. Click on the integration tile to launch the configuration setup dialog.
4. Choose from either Production or Demo Mode for the setup of your integration:
1. **Production**: Connect with real credentials for live data
2. **Demo Mode**: Explore the integration with simulated mock responses
5. Click **Next: Configure and Authenticate**.
6. Select **+ Create New Credential from the Credential** drop-down selector.
7. Enter the information copied from Kaseya into the relevant fields:
1. **Hostname -** This is the hostname of your BMS instance preceded by `api`, found in the browser's address bar
2. **API Key**
8. Click **Save Credential**.
9. Click **Next: Confirm**.
10. Click **Install Integration**. The integration will now appear in the top Connected section of your Integrations page.
11. Click on the installed integration. Scroll down to the Org Mappings section of the configuration page and complete organization mapping as needed.
{% hint style="success" %}
Got an idea for a new Integration? Rewst is constantly adding new integrations to our integrations page. Submit your idea or upvote existing ideas here in our [Canny feedback collector](https://rewst.canny.io/integrations).
{% endhint %}
## Triggers for Kaseya BMS integration
| Trigger type name | Type | Description |
| ----------------- | ------- | ----------------------------------------------------------------------------------------------- |
| New Ticket Record | Polling | Trigger which returns an object containing the count of tickets, and an array of ticket objects |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.rewst.help/rewst-documentation/documentation/integrations/integration-guides/kaseya-bms-integration-setup.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
.png)
.png)
.png)