Skip to main content
Connect Service Channel to KODE OS for work orders data integration

Overview

Use this integration to connect Service Channel to KODE OS. You can discover devices and points, sync work order data with hybrid snapshot collection, create work orders from KODE OS workflows and automations, and use supported connector actions where enabled.

Supported Capabilities

  • Discover Devices & Points
  • Collect Non-Sensor Data
  • Collect Historical Data
  • Collect Historical Multi-Entity Data

Prerequisites

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

Generate API Credentials

  1. Log in to the Service Channel 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
  5. Note the Auth URL for OAuth token exchange

Configure Connector in KODE OS

  1. Navigate to Data Sources in your building
  2. Click API Catalog and search for Service Channel
  3. Click + Add Datasource
  4. 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 Service Channel 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 Service Channel, KODE OS maps them to the following device types and data points:

Connected Device

Canonical Type: default

What Data You Get

Point History

Time-series readings including connection_status, collected at regular intervals from connected devices

Work Orders

Maintenance and service requests including title, description, status, priority, assignee, due dates, vendor response, resolution details, and cost estimates KODE OS maps Service Channel data to these standard fields:

Polling Schedule

  • Point History — Default polling: 15 minutes (min: 15 minutes, max: 1 hours)
  • WorkOrder — Default polling: 15 minutes (min: 15 minutes, max: 1 days)
For more details on collection modes, see the Data Collection guide.

Available Actions

Create Service Channel Work Order

Type: Write Creates a work order in Service Channel (Lowes) with status Open. ScheduledDate is not a form field. KODE OS sets it from the created time plus the maximum hours for the selected priority. When the event is linked to a device, Description is filled and locked. It starts with the asset tag, then the event name, KODE event ID, description, and URL. The asset tag is the last segment of the device display name. AssetId is sent from that device and is not a form field. Trade Name is locked to the linked trade. When the event is not linked, Description is an editable text box, Location and Trade Name are drop-downs, and Provider is filtered by the selected trade. Problem Type loads from the retail facilities issue list. Asset Type depends on the selected location and problem.

Expected Result

  • KODE OS creates the work order in Service Channel (Lowes) with status Open
  • Problem Code on the new work order is KODE FDD
For more details on how actions work, see the Actions guide.

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

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 Service Channel developer portal.
Verify the connector credentials have sufficient permissions in the Service Channel system to list devices. Run a test connection first to confirm connectivity. Some systems require specific API scopes or roles for device discovery.
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 Service Channel API.
Last modified on November 2, 2026