Skip to main content
Connect CloudGate to KODE OS for reservations data integration

Overview

Use this integration to connect CloudGate visitor identity and access workflows to KODE OS. REST pulls and webhooks feed reservation and visitor-related data into the platform, including where actions are enabled for your connector.

Supported Capabilities

  • Collect Sensor Data
  • Receive Webhook Data

Prerequisites

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

Generate API Credentials

  1. Log in to the CloudGate 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 CloudGate 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 CloudGate
  3. Click + Add Datasource
  4. Fill in the fields below and complete the three-page setup flow

Devices and Points

What Data You Get

Bookings

Space reservation records including attendees, check-in/out times, confirmation status, and room/space details KODE OS maps CloudGate data to these standard fields:

Polling Schedule

  • Booking
For more details on collection modes, see the Data Collection guide.

Available Actions

Create Booking

Type: Write Creates a new visitor booking in CloudGate

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

Update Booking

Type: Write Updates an existing visitor booking in CloudGate

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

Cancel Booking

Type: Write Cancels an existing visitor booking in CloudGate

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

Mark Attendance

Type: Write Records check-in/check-out for a visitor booking

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

Update Booking Status

Type: Write Updates the status of a visitor booking in CloudGate

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
For more details on how actions work, see the Actions guide.

Use Cases

Once connected, this integration enables you to:
  • Centralize space and resource booking data across platforms
  • Track no-show rates and actual utilization versus bookings
  • Coordinate meeting room conditions (HVAC, lighting) with reservation schedules

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 CloudGate developer portal.
Verify the webhook URL is correctly registered in the CloudGate platform. Check that the authentication header matches the value from the KODE OS connector detail page. Ensure the CloudGate system can reach the KODE OS webhook endpoint over the network.
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 CloudGate API.
Last modified on March 29, 2026