> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect HOPR by RoomChecking

> Connect HOPR to give Operator read-only access to hotel operations data such as rooms, tasks, inventory, messages, and tags.

## Overview

The HOPR by RoomChecking integration gives Conduit live, read-only access to
hotel operations data. Operator can look up hotels, rooms, tasks, room
inventory, room messages, priority rooms, tags, and hotel settings without
changing anything in HOPR.

<Note>
  This connection provides live tools. It does not import HOPR data into
  Knowledge or sync reservations into Conduit.
</Note>

## What you need

Ask your RoomChecking account administrator for the following values:

| Field in Conduit      | What to enter                                                              |
| --------------------- | -------------------------------------------------------------------------- |
| **Environment URL**   | The root URL for your HOPR environment, without an app page or API path    |
| **Client ID**         | Your RoomChecking API client identifier                                    |
| **Client Key**        | The secret key for that API client                                         |
| **Hotel Group Key**   | The key for the hotel group the API client can access                      |
| **Default time zone** | The IANA time zone used for task date defaults, such as `America/New_York` |

<Warning>
  Keep the Client Key private. Do not paste it into chat messages, Knowledge,
  Skills, or other agent instructions.
</Warning>

## Connect HOPR

<Steps>
  <Step title="Open Connections">
    In Conduit, go to **Settings > Connections** and select **Add connection**.
  </Step>

  <Step title="Choose HOPR by RoomChecking">
    Search for **HOPR** and select **HOPR by RoomChecking**.
  </Step>

  <Step title="Enter the connection details">
    Enter the Environment URL, Client ID, Client Key, Hotel Group Key, and
    default time zone. You do not need a Hotel ID to connect the hotel group.
  </Step>

  <Step title="Connect">
    Select **Connect**. Conduit validates that the credentials can list hotels
    in the group before saving the connection.
  </Step>

  <Step title="Review Operator access">
    Open **Operator > Settings > Tools**. Confirm that **HOPR by RoomChecking**
    and the tools Operator needs are enabled.

    New HOPR connections enable the available tools for Operator by default.
  </Step>
</Steps>

## Available tools

All HOPR tools are read-only.

| Tool                         | What it reads                                                    |
| ---------------------------- | ---------------------------------------------------------------- |
| **List HOPR Hotels**         | Hotels available to the connected client and hotel group         |
| **Get HOPR Hotel Settings**  | Configuration and operational settings for a hotel               |
| **List HOPR Rooms**          | Rooms and their HOPR IDs, names, locations, categories, and tags |
| **List HOPR Tasks**          | Operational tasks for a hotel                                    |
| **List HOPR Room Inventory** | Physical and consumable inventory assigned to a room             |
| **List HOPR Room Messages**  | Operational messages attached to a room                          |
| **List HOPR Priority Rooms** | Rooms currently marked as priority                               |
| **List HOPR Tags**           | Tags configured for the hotel group                              |

Hotel-specific tools use the Hotel ID returned by **List HOPR Hotels**.

If no date range is provided, **List HOPR Tasks** returns tasks created today
in the connection's default time zone.

## Use HOPR with Operator

Open Operator and ask for the HOPR data you need. For example:

* "List today's HOPR tasks."
* "Show the rooms currently marked as priority."
* "Find the inventory and messages for room 204."
* "Show the settings for the connected HOPR hotel."

Operator can combine the tools when a lookup needs more than one step. For
example, it can find a room's HOPR ID before reading that room's inventory.

## Troubleshooting

<AccordionGroup>
  <Accordion title="RoomChecking rejects the credentials">
    Confirm that the Client ID and Client Key belong to the environment in the
    Environment URL. If they were rotated, reconnect using the current values.
  </Accordion>

  <Accordion title="The hotel group cannot be validated">
    Confirm that the Hotel Group Key belongs to the selected environment and
    that the connected API client can list hotels in that group.
  </Accordion>

  <Accordion title="Operator cannot see the HOPR tools">
    Open **Operator > Settings > Tools**, expand **HOPR by RoomChecking**, and
    enable the connection or the individual tools Operator needs.
  </Accordion>
</AccordionGroup>