> For the complete documentation index, see [llms.txt](https://witfy.gitbook.io/clowrk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://witfy.gitbook.io/clowrk/connectors/priax.md).

# Priax Connector

## 1. Purpose

Integration with Priax, a system specialized in CMDB (Configuration Management Database) based on Neo4j graphs, enabling synchronization of assets, relationships, and configuration data.

## 2. Where It Is Used

Priax connectors are used in:

* Availability Events Module
* Performance Events Module
* Configuration Item Selection Module
* Service Catalog form fields
* Client linking (will be detailed in the Clients section)

## 3. Instance Configuration

Clowrk supports multiple Priax instances per company, allowing environment segregation (production, staging, development) or different served clients.

**Configuration Parameters:**

* **Instance Name (required):** Descriptive name of the instance (e.g., "Production", "Client XYZ")
* **Instance ID (optional):** Unique identifier of the Priax instance

## 4. Default Instance Concept

When the Instance ID is not provided, the connector is automatically designated as the default instance. This will be the instance used by default in integrations that do not explicitly specify which Priax instance to use.

**Business rule:** Only one default instance is allowed per company.

**Practical example:**

* **Connector 1:** Instance Name = "Production", Instance ID not provided → Becomes the default instance
* **Connector 2:** Instance Name = "Staging", Instance ID = "hml-001" → Specific instance
* **Connector 3:** Instance Name = "Client A", Instance ID = "client-a" → Specific instance

## 5. Authentication

The Priax connector offers authentication flexibility, supporting two distinct methods:

**OAuth 2.0**

* Client ID
* Client Secret

**Basic Authentication**

* Username
* Password

**Additional Data:**

* **API URL:** Priax instance base endpoint