> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/ai/avoma.md).

# Avoma

The Avoma integration connects your Avoma account to Harmony as an AI category integration. Once connected, Harmony pulls license and organizational data directly from Avoma, giving you visibility into your Avoma usage alongside your other tools.

### Prerequisites

Before setting up the integration, make sure you have access to Avoma's developer settings so you can generate the required API credentials. You will need an Avoma account with permission to manage organization-level settings.

### Credentials

The Avoma integration uses a bearer-token model in the format `CLIENT_KEY:CLIENT_SECRET`. You will need to provide two values when connecting:

* **Client Key** - A text identifier generated in Avoma. This acts as the username component of the credential pair.
* **Client Secret** - A masked password credential paired with the Client Key. This value is hidden after entry and cannot be retrieved once saved.

To generate these credentials in Avoma, navigate to **Settings → Organization → Developer → Add API Key**.

### Connecting Avoma to Harmony

1. In Harmony, go to **Settings → Integrations → AI**.
2. Locate the **Avoma** tile and click it to begin setup.
3. Enter your **Client Key** in the provided field.
4. Enter your **Client Secret** in the provided field.
5. Save the integration.

Once connected, Harmony will begin pulling license and organizational data from your Avoma account.

### Data Collected

After the integration is active, Harmony retrieves the following from Avoma:

* **License data** - Information about the seats and licenses associated with your Avoma account.
* **Organizational data** - Details about your Avoma organization, used to map usage and ownership within Harmony.

### Troubleshooting

If the integration fails to connect or stops syncing, check the following:

* Confirm that the Client Key and Client Secret were copied correctly from Avoma with no extra spaces or characters.
* Verify that the API key in Avoma has not been deleted or rotated. If it has, generate a new key pair and update the credentials in Harmony.
* Ensure your Avoma account has the necessary permissions to access organization and developer settings.


---

# 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.harmony.io/integrations/ai/avoma.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.