> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/avo-integrator-extension.md).
# Prerequisites
## Avo Integrator Extension
It is used as an intermediary between Avo Assure and third-party tools. Earlier, we used Avo Assure Client, which took time to communicate and load client requests. With Avo Integrator, loading time and overall platform efficiency have improved.
{% hint style="info" %}
**Note:** Avo Integrator supports **Jira**, **Azure DevOps**, **Zephyr Scale** and **Xray Integration** and it is available on the Chrome.
{% endhint %}
### Adding Avo Integrator extension in browser
To add Avo Integrator in browser, perform the following actions:
1. Select Browser.
2. Select **Extension** icon.
3. From **Extensions** dialog, select **Manage extensions**.
2. From **Extensions** page, Select **Chrome Web Store** link.
3. In **Chrome Web Store**, search **Avo Integrator** and select the extension.
5. Select **Add to chrome** button. The **Add "Add Integrator"** dialog appears.
6. Select **Add Extension**. Avo Integrator gets added in **My extension** page.
---
# 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.avoautomation.com/avo-assure/integrations-in-avo-assure/avo-integrator-extension.md?ask=&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.
