Connect Impak to KODE OS for work orders data integration
Overview
Use this integration to connect Impak to KODE OS. You can collect sensor and non-sensor work order data over REST with hybrid snapshot collection and use supported connector actions from Data Sources.Supported Capabilities
- Collect Sensor Data
- Collect Non-Sensor Data
Prerequisites
- An active account with Impak and access to their API or developer portal
- API key or token from the Impak platform
- KODE OS environment with access to Data Sources
Generate API Credentials
- Log in to the Impak platform or admin console
- Navigate to the API settings, developer section, or account settings
- Generate a new API key or token
- Copy the key and store it securely — you will need it 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 Impak
- Click + Add Datasource
- Fill in the fields below and complete the three-page setup flow
Devices and Points
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 Impak data to these standard fields:Polling Schedule
- WorkOrder — Default polling: 30 minutes (min: 30 minutes, max: 1 hours)
Available Actions
Create Work Order
Type: Write Creates a new work order in ImpakExample 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 API key or token is valid and has not been revoked or expired in the Impak platform.
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 Impak API.