> For the complete documentation index, see [llms.txt](https://docs.cow.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cow.tech/inputs/psa-integrations/halopsa.md).

# HaloPSA

## Introduction

Integrating HaloPSA with COW allows you to seamlessly synchronize your device and warranty data, ensuring that your information is up-to-date and accurately managed. This guide will walk you through the steps required to set up and configure your HaloPSA integration.

### Prerequisites

Before you begin the integration process, ensure you have the following information ready:

* **HaloPSA URL**: Enter the URL of your HaloPSA instance.
* **HaloPSA Tenant**: Provide the tenant information for your HaloPSA account.
* **HaloPSA Client ID**: Enter the client ID for authentication.
* **HaloPSA Secret**: Enter your API secret securely.

### Setup

{% embed url="<https://app.storylane.io/share/tqn8d1cxid6k>" %}


---

# 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.cow.tech/inputs/psa-integrations/halopsa.md?ask=<question>&goal=<endgoal>
```

`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.
