> 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/settings/understanding-integrations.md).

# Understanding Integrations

Learn how Harmony integrations work, how to view and connect them, and how OAuth authentication enables secure connections to third-party systems.

{% hint style="info" %}
**Path:** `/settings/integrations`
{% endhint %}

### Understanding Harmony Integrations

#### What are Integrations?

Integrations connect third-party systems to Harmony. They enable Harmony to sync data, trigger actions, and work with tools like Slack, Okta, Jamf, Confluence, and many others. Each integration brings capabilities such as user sync, ticket creation, device management, knowledge base content, or notifications.

#### Benefits of Integrations

* **Single entry point** - Support and operations from one place instead of switching between tools
* **Unified workflows** - Automate across systems (e.g., create tickets from Slack, provision access via Okta)
* **Data sync** - Keep employees, assets, and applications up to date across your stack
* **AI and automation** - AI agents and workflows use integration data to resolve issues and route work

#### Viewing Available Integrations

1. Go to **Settings** → **Integrations**.
2. The page lists all available integrations, grouped by category.
3. Use **Search** to find a specific integration by name.
4. Use the **Category** filter to narrow by type (Collaboration, Identity Provider, MDM, etc.).
5. The URL supports `?integration-id=...` for deep linking to a specific integration.

Each integration card shows the name, description, category, and connection status.

![Integrations list with category filter and cards](https://3514868215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDXF7jyqNjJ1RPF9oUCnb%2Fuploads%2Fgit-blob-b76a3c6d6cb1de806fdeb377da8718596d19f19b%2Fintegrations-list.png?alt=media)

***

### Understanding Integration Categories

Integrations are organized into categories. Some integrations appear under more than one category.

| Category                  | Description                       | Examples                                                           |
| ------------------------- | --------------------------------- | ------------------------------------------------------------------ |
| **Collaboration**         | Team communication tools          | Slack, Microsoft Teams                                             |
| **Identity Provider**     | Identity and access management    | Okta, Microsoft Entra ID, Google Workspace, JumpCloud (IdP)        |
| **MDM**                   | Mobile device management          | Jamf Pro, Iru (formerly Kandji), Microsoft Intune, JumpCloud (MDM) |
| **IT Service Management** | IT Service Management platforms   | ServiceNow, Jira Service Management, Zendesk, SolarWinds           |
| **IT Operations**         | Incident response and on-call     | PagerDuty, incident.io, FireHydrant                                |
| **HRIS**                  | Human Resources systems           | BambooHR, HiBob, Workday, Ceridian Dayforce, Sage HR, UKG Pro      |
| **ATS**                   | Applicant tracking systems        | Greenhouse (OAuth)                                                 |
| **Learning Management**   | Learning management systems       | Cornerstone OnDemand                                               |
| **Knowledge Base**        | Knowledge base platforms          | Confluence, Notion, Freshservice, SharePoint, Simpplr              |
| **EDR**                   | Endpoint detection and response   | CrowdStrike, SentinelOne, Microsoft Defender for Endpoint          |
| **Security**              | Device posture and access control | Infinipoint                                                        |
| **Asset Management**      | IT asset management               | Workwize, Firstbase                                                |
| **SaaS Procurement**      | Procurement and spend management  | Ramp, Navan, Mesh Payments                                         |
| **SaaS Applications**     | General SaaS apps                 | GitHub, monday.com, Zoom, Salesforce                               |
| **AI**                    | AI platforms                      | ChatGPT, Claude, Cursor, Microsoft Copilot                         |
| **Software Management**   | Software inventory and licensing  | Torii, Zylo                                                        |
| **Networking**            | Network infrastructure            | Cisco Meraki, Juniper Mist                                         |
| **Project Management**    | Project and work management       | Asana, Linear                                                      |

***

### Understanding Integration Status

#### Connected Status

When an integration is connected, the card shows a **Connected** badge (green). For multi-instance integrations (e.g., multiple Slack workspaces), the count of instances is shown. Hover for a tooltip listing the instances.

![Integration card with Connected badge](https://3514868215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDXF7jyqNjJ1RPF9oUCnb%2Fuploads%2Fgit-blob-7b984fef4746aca24b2e828e3baa67a13656dda8%2Fintegration-connected.png?alt=media)

#### Disconnected Status

When no instances exist, the integration is disconnected. There is no explicit "Disconnected" badge; the absence of "Connected" indicates it is not set up. Click the card to start the setup flow.

#### Deprecated Status

Some integrations may be marked **Deprecated**. Deprecated integrations that are already connected can continue to work, but new configuration may be restricted. Plan to migrate to a supported alternative when available.

#### Error and Syncing Status

The UI does not currently display an "Error" or "Syncing" status on integration cards. If an integration stops working, check that integration's guide for troubleshooting. Many OAuth integrations offer **Reconnect**, which authorizes again while keeping the instance and its settings; for other integrations, disconnect and connect again.

***

### Understanding OAuth Authentication

Many integrations use OAuth for secure, delegated access. Harmony supports different auth types:

#### What is OAuth?

OAuth lets Harmony access a third-party service on your behalf without storing your password. You authorize the connection once; Harmony receives tokens to make API calls. Tokens can be refreshed automatically.

#### OAuth Flow Overview

1. Click the integration's card to open its setup window.
2. For a multi-instance integration, enter an **Instance name**. Pick a **Region** if the integration asks for one.
3. Click **Connect**. The provider's authorization page opens in the same browser tab.
4. Log in to the provider (if needed) and approve the requested permissions.
5. The provider sends you back to **Settings** > **Integrations**, and a toast confirms the connection. If the integration needs more settings, fill them in and click **Complete Configuration**.

Slack asks for no instance name: click **Connect**, and its authorization page opens in a popup window (600×700) that closes once you approve. Once a workspace is connected, the card shows **Reauthorize**, which runs the authorization again for that workspace. Accounts set up for more than one Slack workspace see **+ Add workspace** instead.

#### Authorization Process

When you authorize an integration:

* The provider shows the permissions (scopes) Harmony is requesting.
* Review and approve them. Without approval, the connection cannot be completed.
* Some integrations may require admin approval in the provider (e.g., Slack workspace admin).

#### Token Management

Tokens are stored and managed by Harmony. The UI does not expose tokens. Token refresh happens automatically. If a token expires and cannot be refreshed (e.g., revoked in the provider), open the integration and click **Reconnect** (on a multi-instance card, the plug icon on the instance's row) to authorize again. The instance keeps its settings. If the integration has no Reconnect option, disconnect and connect it again.

#### Understanding OAuth Scopes

**Scopes** define what Harmony can do in the connected system (e.g., read users, send messages, list channels). Each integration has predefined scopes. The provider's authorization screen lists them. Harmony requests only the scopes needed for that integration's features.

#### Credentials-Based Integrations

Some integrations use **credentials** (e.g., API keys) instead of OAuth. For these, click the card, enter the credentials in the setup window, and click **Connect**. Credentials are stored securely by Harmony.

![Setup window of a credentials-based integration, with the Connect button](https://3514868215-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDXF7jyqNjJ1RPF9oUCnb%2Fuploads%2Fgit-blob-c38bccff0379ee7650dc63298f0cff9ea3c03832%2Fintegration-connect.png?alt=media)

***

### Related Resources

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Connecting Integrations</strong></td><td>Connect, configure, and disconnect integrations</td><td><a href="https://github.com/harmonyso/public-docs/blob/main/guides/connecting-and-managing-integrations/README.md">https://github.com/harmonyso/public-docs/blob/main/guides/connecting-and-managing-integrations/README.md</a></td></tr><tr><td><strong>Integrations Catalog</strong></td><td>Browse available integrations</td><td><a href="https://github.com/harmonyso/public-docs/blob/main/integrations/overview/README.md">https://github.com/harmonyso/public-docs/blob/main/integrations/overview/README.md</a></td></tr><tr><td><strong>User Management</strong></td><td>Notification destinations use connected integrations</td><td><a href="https://github.com/harmonyso/public-docs/blob/main/guides/managing-user-management/README.md">https://github.com/harmonyso/public-docs/blob/main/guides/managing-user-management/README.md</a></td></tr><tr><td><strong>Knowledge Base</strong></td><td>Connect KB sources (Confluence, Notion, etc.)</td><td><a href="https://github.com/harmonyso/public-docs/blob/main/guides/managing-knowledge-base/README.md">https://github.com/harmonyso/public-docs/blob/main/guides/managing-knowledge-base/README.md</a></td></tr></tbody></table>


---

# 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/settings/understanding-integrations.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.
