> ## 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.

# QR Connect

> Connect QR Connect to KODE OS for work orders data

> Connect QR Connect to KODE OS for work orders data integration

## Overview

Use this integration to connect QR Connect to KODE OS. You can combine REST and webhooks to capture work orders triggered by your configured events, keep snapshot data current, and use supported actions from KODE OS.

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

## Supported Capabilities

* Collect Sensor Data
* Receive Webhook Data

## Prerequisites

* An active account with QR Connect and access to their API or developer portal
* OAuth client credentials (Client ID and Client Secret) from the QR Connect developer portal
* KODE OS environment with access to Data Sources

## Generate API Credentials

1. Log in to the QR Connect developer portal or admin console
2. Navigate to the API or developer settings section
3. Create a new API application or client
4. Note the **Client ID** and **Client Secret** -- you will need these when configuring the connector in KODE OS

## Configure Webhook

This integration uses webhooks for real-time data delivery. After creating the connector in KODE OS:

1. Copy the webhook URL provided on the connector detail page
2. In the QR Connect platform, navigate to the webhook or notification settings
3. Add a new webhook endpoint using the KODE OS URL
4. Configure the authentication header as specified on the connector detail page
5. Save and enable the webhook

## Configure Connector in KODE OS

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

| Field                 | Required | Type     | Description                                                |
| --------------------- | -------- | -------- | ---------------------------------------------------------- |
| **URL**               | Yes      | text     | The base URL or IP address of the external system          |
| **Client ID**         | Yes      | password | The OAuth client ID from the vendor's developer portal     |
| **Client Secret**     | Yes      | password | The OAuth client secret from the vendor's developer portal |
| **API Building ID**   | Yes      | text     | The building or source identifier in the external system   |
| **API Building Name** | Yes      | text     |                                                            |

## 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 QR Connect data to these standard fields:

| KODE Field          | Source Field          | Notes       |
| ------------------- | --------------------- | ----------- |
| **id**              | `eventGuid`           | --          |
| **description**     | `description`         | --          |
| **status**          | `status`              | --          |
| **category**        | `categoryName`        | --          |
| **subCategory**     | `subcategoryName`     | --          |
| **location**        | `location`            | --          |
| **assignedTo**      | `assignedMember`      | --          |
| **assignmentGroup** | `assignedTeam`        | --          |
| **completedAt**     | `DateUtils.parseDate` | transformed |
| **duration**        | `completionTime`      | --          |
| **lastComment**     | `notes`               | --          |
| **customFields**    | `noOfWorkOrders`      | --          |

### Polling Schedule

* **WorkOrder**

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 QR Connect

| Field           | Type   | Required | Input     | Options / Default                |
| --------------- | ------ | -------- | --------- | -------------------------------- |
| **Title**       | STRING | Yes      | Text Box  | --                               |
| **Description** | STRING | Yes      | Text Box  | --                               |
| **Category**    | STRING | Yes      | Drop Down | Static: predefined categories    |
| **Subcategory** | STRING | Yes      | Drop Down | Static: predefined subcategories |
| **Location**    | STRING | Yes      | Text Box  | --                               |
| **Device Link** | STRING | Yes      | Text Box  | --                               |
| **Priority**    | STRING | Yes      | Text Box  | Smart Device Priority            |

#### Example Request

```json theme={null}
{
  "title": "example-value",
  "description": "example-value",
  "categoryGuid": "predefined categories",
  "subcategoryGuid": "predefined subcategories",
  "location": "example-value",
  "deviceLink": "example-value",
  "priority": "High"
}
```

#### 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. Ensure the Client ID and Client Secret match the values from the QR Connect developer portal.
  </Accordion>

  <Accordion title="Webhook data not arriving">
    Verify the webhook URL is correctly registered in the QR Connect platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the QR Connect system can reach the KODE OS webhook endpoint over the network.
  </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 QR Connect API.
  </Accordion>
</AccordionGroup>