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

# Nuvolo

> Connect Nuvolo to KODE OS for work orders data

> Connect Nuvolo to KODE OS for work orders data integration

## Overview

Use this integration to connect Nuvolo to KODE OS. You can collect work order and workplace operational data with hybrid historical collection over REST and use supported actions to align facilities work across your sites.

| Property            | Value                |
| ------------------- | -------------------- |
| **System Type**     | Work Orders          |
| **Communication**   | REST                 |
| **Collection**      | Hybrid (Pull + Push) |
| **Collection Mode** | HISTORICAL           |
| **Actions**         | Supported            |

## Supported Capabilities

* Collect Sensor Data
* Collect Non-Sensor Data

## Prerequisites

* An active account with Nuvolo and access to their API or developer portal
* Username and password credentials for the Nuvolo system
* KODE OS environment with access to Data Sources

## Configure Connector in KODE OS

1. Navigate to **Data Sources** in your building
2. Click **API Catalog** and search for **Nuvolo**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field        | Required | Type     | Description                                              |
| ------------ | -------- | -------- | -------------------------------------------------------- |
| **Room**     | No       | text     | The specific room this connector is associated with      |
| **URL**      | Yes      | text     | The base URL or IP address of the external system        |
| **Username** | Yes      | text     | The username for authenticating with the external system |
| **Password** | Yes      | password | The password for authenticating with the external system |

## What Data You Get

### Work Orders

Maintenance and service requests including title, description, status, priority, assignee, due dates, vendor response, resolution details, and cost estimates

KODE OS maps Nuvolo data to these standard fields:

| KODE Field            | Source Field                                   | Notes |
| --------------------- | ---------------------------------------------- | ----- |
| **id**                | `workOrderId`                                  | --    |
| **title**             | `title`                                        | --    |
| **description**       | `description`                                  | --    |
| **status**            | `state`                                        | --    |
| **priority**          | `priority`                                     | --    |
| **category**          | `work_order_type`                              | --    |
| **location**          | `location`                                     | --    |
| **createdBy**         | `created_by`                                   | --    |
| **assignedTo**        | `assigned_to`                                  | --    |
| **createdAt**         | `NuvoloWorkOrder.formattedDate(created_at`     | --    |
| **updatedAt**         | `NuvoloWorkOrder.formattedDate(updated_at`     | --    |
| **startedAt**         | `NuvoloWorkOrder.formattedDate(opened_at`      | --    |
| **completedAt**       | `NuvoloWorkOrder.formattedDate(resolutionDate` | --    |
| **assignmentGroup**   | `assignmentGroup`                              | --    |
| **serviceProvider**   | `service_provider`                             | --    |
| **problemCause**      | `problem_cause`                                | --    |
| **resolutionDetails** | `resolution_detail`                            | --    |
| **estimatedCost**     | `estimated_cost`                               | --    |
| **lastComment**       | `comments`                                     | --    |
| **assetName**         | `asset`                                        | --    |
| **assetType**         | `assetType`                                    | --    |

### Polling Schedule

* **WorkOrder** -- Default polling: 30 minutes (min: 30 minutes, max: 1 days)

For more details on collection modes, see the [Data Collection guide](/products/integrations/capabilities/data-collection).

## Available Actions

### Create Work Order

**Type:** Write

Creates a new work order in Nuvolo

| Field                 | Type   | Required | Input    | Options / Default |
| --------------------- | ------ | -------- | -------- | ----------------- |
| **Short Description** | STRING | Yes      | Text Box | --                |
| **Description**       | STRING | Yes      | Text Box | --                |
| **Priority**          | STRING | Yes      | Text Box | --                |
| **Asset Location**    | STRING | Yes      | Text Box | --                |
| **Asset Tag**         | STRING | Yes      | Text Box | --                |

#### Example Request

```json theme={null}
{
  "short_description": "example-value",
  "description": "example-value",
  "priority": "High",
  "asset_location": "example-value",
  "asset_tag": "example-value"
}
```

#### Expected Result

* KODE OS sends the action to the external API using the configured connector credentials
* The external system returns success (typically HTTP 2xx) and processes the requested operation

For more details on how actions work, see the [Actions guide](/products/integrations/capabilities/actions).

## Use Cases

Once connected, this integration enables you to:

* Centralize maintenance requests and work order status from facility management systems
* Create and update work orders directly from KODE OS when issues are detected
* Track maintenance KPIs including response time, completion rate, and cost

## Troubleshooting

<AccordionGroup>
  <Accordion title="Authentication or connection error">
    Verify that the credentials are correct and have not expired. Check that the URL is reachable from the KODE OS environment. Verify the username and password are correct and the account has not been locked in the Nuvolo system.
  </Accordion>

  <Accordion title="Data collection stops or gaps appear">
    Check the connector status on the Data Sources page. If the status shows an error, review the error logs on the connector detail page. Common causes include expired credentials, network changes, or rate limiting by the Nuvolo API.
  </Accordion>
</AccordionGroup>