> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alumio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Airfocus

> Connect Alumio to Airfocus.

## Extra information

System documentation: \[Airfocus API Reference]

**Airfocus**

**Connector Package Documentation**

# Setting up HTTP Client Airfocus

## Steps

* In Alumio Dashboard, go to Clients > HTTPS Client. Create a new HTTP Client and select Airfocus HTTP Client as the prototype of the HTTP Client.
* Fill in the Base URI, and Api Key.
* Save the Client for use later.

# Subscribing to Entities from Airfocus

## Steps

* Go to Connections -> Incoming and create a new incoming configuration and select Airfocus Subscriber as the subscriber.
* Select the entity you want to subscribe from Airfocus .
* Add any request parameters needed to subscribe to the entity (optional).
* You can optionally add a transformer to transform the request parameters into something you need.
* Select the Airfocus HTTP Client to use.

## General Concept

We follow Airfocus documentation on building this connector so you can easily use the connector based on Airfocus API Reference.

**Method**

It’s the Method you want to subscribe from Airfocus. Based on the Method, the Entity will change. Please refer to the entities in Management APIs from Airfocus API Reference page.

**Entity**

It’s the entity you want to subscribe from Airfocus . Please refer to the entities in Management APIs from Airfocus API Reference page.

**Request Parameters**

These are the parameters you can provide to get the needed entity based on Airfocus API Reference. Please look at the example below on how to fill the Request Parameters field when subscribing Retrieve a single field.

<img src="https://mintcdn.com/alumio/99mrwtB8nAsdGlI9/images/connectors/airfocus-01.png?fit=max&auto=format&n=99mrwtB8nAsdGlI9&q=85&s=845ef80bcdfebee2e7136f8d5cf52bff" alt="Airfocus connector screenshot 1" width="690" height="401" data-path="images/connectors/airfocus-01.png" />

<img src="https://mintcdn.com/alumio/99mrwtB8nAsdGlI9/images/connectors/airfocus-02.png?fit=max&auto=format&n=99mrwtB8nAsdGlI9&q=85&s=69b8724db742f9417d841995935eb479" alt="Airfocus connector screenshot 2" width="690" height="183" data-path="images/connectors/airfocus-02.png" />

That’s why we need to define the **fieldId** property inside the path property in the Request Parameters field. The properties inside query parameters will be parsed as query parameters. Here is the final URL that will be called when using such Request Parameters field on Retrieve a single field.

/api/fields/abc123

**Input Transformer**

Any transformer’s set here will be executed after the Request Parameters are loaded. So, you basically can add any transformer to provide and transform the request parameters into anything you need either as path parameters and/or as query parameters of an entity.

**HTTP Client**

It’s the HTTP Client configuration or prototype you will use to access Airfocus .

# Publishing Entity to Airfocus

## Steps

* Go to Connections -> Outgoing, create a new outgoing configuration, and select Airfocus Publisher as the publisher.
* Select the action that you want the publisher to do with the data.
* Select the Airfocus entity you want the data to be published.
* You can optionally add any query parameters to the request.
* You can also optionally add any transformers to transform the data into anything you need before submitting it to Airfocus .
* Select the HTTP Client to use.
  <img src="https://mintcdn.com/alumio/99mrwtB8nAsdGlI9/images/connectors/airfocus-03.png?fit=max&auto=format&n=99mrwtB8nAsdGlI9&q=85&s=97078d3187c234b3014f505650a9372f" alt="Airfocus connector screenshot 3" width="690" height="323" data-path="images/connectors/airfocus-03.png" />

## General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

**Method**

Currently, we support Post (HTTP POST method), Patch (HTTP PATCH method), Put (HTTP PUT method), and Delete (HTTP DELETE method).

**Entity**

We support publishing to most Airfocus endpoints. Please refer to the entities in Management APIs from the Airfocus API Reference page. Based on the documentation, some endpoints may need one or more path parameters.

For endpoints that require an object as the request payload, please look at the example below. For example, we want to Update a workspace. Please select “Put” as the action and “Update an existing workspace” as the entity of the publisher.

<img src="https://mintcdn.com/alumio/99mrwtB8nAsdGlI9/images/connectors/airfocus-04.png?fit=max&auto=format&n=99mrwtB8nAsdGlI9&q=85&s=aacb4f20c9d2c0d98b468a58ff7980c4" alt="Airfocus connector screenshot 4" width="690" height="323" data-path="images/connectors/airfocus-04.png" />

<img src="https://mintcdn.com/alumio/99mrwtB8nAsdGlI9/images/connectors/airfocus-05.png?fit=max&auto=format&n=99mrwtB8nAsdGlI9&q=85&s=97c9812a0782dce9450f095d93f79f47" alt="Airfocus connector screenshot 5" width="690" height="216" data-path="images/connectors/airfocus-05.png" />

You can put the payload you want to send to Airfocus into the payload property in the data.

Alumio will send an API request to Airfocus with URL /api/workspaces/workspace123

**HTTP Client**

It’s the HTTP Client configuration or prototype you will use to access Airfocus .
