Connect Corrigo to KODE OS for work orders data integration
Overview
Use this integration to connect Corrigo to KODE OS. You can discover devices and points, collect work order and facilities data over REST with hybrid snapshot collection, and use supported actions for maintenance workflows across your portfolio.Supported Capabilities
- Discover Devices & Points
- Collect Sensor Data
- Collect Non-Sensor Data
Prerequisites
- An active account with Corrigo and access to their API or developer portal
- OAuth client credentials (Client ID and Client Secret) from the Corrigo developer portal
- KODE OS environment with access to Data Sources
Vendor Onboarding References
Use these official vendor resources to verify API access, credentials, and permission prerequisites:Generate API Credentials
- Log in to the Corrigo developer portal or admin console
- Navigate to the API or developer settings section
- Create a new API application or client
- Note the Client ID and Client Secret — you will need these when configuring the connector in KODE OS
Configure Connector in KODE OS
- Navigate to Data Sources in your building
- Click API Catalog and search for Corrigo
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
Discover Devices and Points
After configuring the connector, click Discover on the connector detail page. KODE OS will query the Corrigo system and return a list of available devices and their data points. Review the discovered items and select the devices you want to register in KODE OS. For more details on the discovery process, see the Discovery guide.Devices and Points
When you discover devices from Corrigo, KODE OS maps them to the following device types and data points:IO Reader / Controller
Canonical Type:IOREADER
What Data You Get
Point History
Time-series readings including is_online, is_locked, is_restricted, collected at regular intervals from connected devicesWork Orders
Maintenance and service requests including title, description, status, priority, assignee, due dates, vendor response, resolution details, and cost estimates KODE OS maps Corrigo data to these standard fields:Polling Schedule
- Point History — Default polling: 1 hours (min: 1 hours, max: 1 hours)
- WorkOrder — Default polling: 5 minutes (min: 5 minutes, max: 1 hours)
Available Actions
Create Corrigo Work Order
Type: Write Creates a new work order in Corrigo Enterprise. Requires only a comment; work order context (building, device, priority) is auto-populated from the KODE OS alarm or device.Example Request
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
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
Authentication or connection error
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 Corrigo developer portal.
Discovery returns no devices
Discovery returns no devices
Verify the connector credentials have sufficient permissions in the Corrigo system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device enumeration.
Data collection stops or gaps appear
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 Corrigo API.