> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/mdm/fleetdm.md).

# FleetDM

The FleetDM integration connects Harmony to your FleetDM instance, bringing device management context directly into your support workflows. When agents handle customer queries, they can access relevant fleet and device data without leaving the platform, reducing tool-switching and helping your team resolve issues faster.

### Prerequisites

Before configuring the FleetDM integration, make sure you have:

* A Fleet user with the global admin role, to create an API-only user for Harmony
* Admin or appropriate permissions in Harmony to manage integrations
* Your FleetDM API credentials or token available

### Creating an API key in Fleet

1. In Fleet, go to **Settings** > **Users**. Only global admins can open this page.
2. Click **Add user** and select **API-only user**.
3. Enter a **Name** (for example, Harmony) and set **Role** to **Observer**, Fleet's read-only role. On Fleet Premium the role starts as **GitOps**, which cannot view hosts, so change it.
4. Click **Add** and copy the **API key**. Fleet shows it only once. Keys of API-only users do not expire.

### Connecting FleetDM to Harmony

To set up the FleetDM integration:

1. In Harmony, navigate to **Settings** and open the **Integrations** section.
2. Find **Fleet** under **MDM** (or search for it by name) and click its card. If a Fleet instance is already connected, click **+ Create instance**.
3. Enter an **Instance name** (required) and your Fleet **API Key**.
4. Click **Connect** to establish the connection.

Once connected, Harmony will be able to pull fleet and device data from your FleetDM instance and surface it within the platform.

### Using FleetDM Data in Support Workflows

After the integration is active, agents can access device management context directly while handling customer queries. This means:

* Relevant fleet and device information is available within the conversation view, without needing to open FleetDM separately.
* Agents can reference device status, ownership, and other fleet details to better understand customer issues.
* Support workflows become more efficient by reducing the need to switch between tools during active interactions.

### Managing the Integration

You can review and update your FleetDM connection at any time through the **Integrations** settings in Harmony. From there you can:

* Replace your API credentials if they change. The API key of a connected Fleet instance cannot be edited, so delete the instance and connect it again with the new key.
* Delete the instance (trash icon) if the integration is no longer needed.
* Review the current connection status to confirm the integration is active.

### Troubleshooting

If the integration does not connect or fleet data is not appearing as expected, consider the following:

* Confirm that the API credentials you entered are correct and have not expired.
* Verify that the API key belongs to an API-only user with the **Observer** role, or another role that can view hosts.
* Check that your FleetDM instance is reachable and operational.
* If issues persist, contact Harmony Support for further assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/integrations/mdm/fleetdm.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
