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

# Gridium

> Connect Gridium to KODE OS for work orders data

> Connect Gridium to KODE OS for work orders data integration

## Overview

Use this integration to connect Gridium to KODE OS. You can ingest work order and building operations data over REST and webhooks with snapshot collection so occupant, vendor, and staff activity stays visible in your portfolio.

| Property            | Value          |
| ------------------- | -------------- |
| **System Type**     | Work Orders    |
| **Communication**   | REST + Webhook |
| **Collection**      | Pull           |
| **Collection Mode** | SNAPSHOT       |

## Supported Capabilities

* Collect Sensor Data
* Receive Webhook Data

## Prerequisites

* An active account with Gridium and access to their API or developer portal
* KODE OS environment with access to Data Sources

## 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 Gridium 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 **Gridium**
3. Click **+ Add Datasource**
4. Fill in the fields below and complete the three-page setup flow

| Field               | Required | Type | Description                                              |
| ------------------- | -------- | ---- | -------------------------------------------------------- |
| **API Building ID** | Yes      | text | The building or source identifier in the external system |
| **External URL**    | No       | text | An additional external URL for the integration           |

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

| KODE Field        | Source Field                                        | Notes |
| ----------------- | --------------------------------------------------- | ----- |
| **id**            | `request.id`                                        | --    |
| **woNumber**      | `request.workOrder`                                 | --    |
| **title**         | `request.title`                                     | --    |
| **description**   | `request.description`                               | --    |
| **status**        | `request.status`                                    | --    |
| **priority**      | `request.priority`                                  | --    |
| **category**      | `requestType(`                                      | --    |
| **location**      | `location(`                                         | --    |
| **createdBy**     | `originator(`                                       | --    |
| **assignedTo**    | `owner(`                                            | --    |
| **createdAt**     | `GridiumWorkOrder.formattedDateUtc(request.created` | --    |
| **updatedAt**     | `GridiumWorkOrder.formattedDateUtc(request.updated` | --    |
| **dueDate**       | `GridiumWorkOrder.formattedDateUtc(request.due`     | --    |
| **lastComment**   | `lastComment(`                                      | --    |
| **lastCommentBy** | `lastCommentBy(`                                    | --    |
| **externalUrl**   | `externalUrl`                                       | --    |

### Polling Schedule

* **WorkOrder**

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

## 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. Double-check all credential fields match the values from the Gridium platform.
  </Accordion>

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