> 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/software-management/zylo.md).

# Zylo

Zylo is an enterprise SaaS management platform that discovers, optimizes, and manages software licenses across the organization. Connecting Zylo to Harmony enriches Harmony's software inventory with the spend, usage, and renewal data already tracked in Zylo - giving IT teams a unified view without duplicating management effort.

Zylo is available as a fully supported application in the Harmony applications catalog.

#### What the Zylo integration enables

| Capability         | Description                                                                 |
| ------------------ | --------------------------------------------------------------------------- |
| Software Inventory | Pull Zylo's application catalog into Harmony's software inventory           |
| License Data       | Enrich asset records with license counts, assignments, and utilization      |
| Spend Visibility   | Surface contract spend and cost-per-seat data tracked in Zylo               |
| Renewal Tracking   | Bring renewal dates into Harmony for proactive license management workflows |

#### Prerequisites

* **Zylo Account**: Access to your organization's Zylo account with API credential generation permissions
* **Harmony Account**: Active Harmony workspace

#### Connect Zylo to Harmony

**Step 1: Generate API Credentials in Zylo**

1. Log in to your Zylo account
2. Go to your account settings
3. Navigate to the **API** section and generate new credentials
4. Copy the **Token ID** and **Token Secret** - the secret will not be shown again

**Step 2: Navigate to Integrations**

1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Zylo** under **Software Management** and click **Connect**

**Step 3: Enter Credentials**

1. Enter your **Token ID**
2. Enter your **Token Secret**
3. Optionally update the **Instance Name** - this field is pre-filled with a default value (for example, "Zylo Instance") to make setup faster
4. Click **Connect**

#### What Harmony Syncs

**From Zylo:**

* Application catalog (discovered and managed apps)
* License data per application (total, assigned, available)
* Spend data (contract value, cost per seat)
* Renewal dates and contract metadata
* Usage signals per application

#### Use Cases

<details>

<summary>Unified Software Inventory</summary>

Combine Zylo's SaaS discovery with Harmony's asset management for a single source of truth on software across the org

</details>

<details>

<summary>Renewal Alerting</summary>

Trigger Harmony workflows ahead of contract renewals to review usage and decide whether to renew, downsize, or cancel

</details>

<details>

<summary>Spend Optimization</summary>

Use Zylo's spend data within Harmony to identify over-provisioned licenses and take action through automated workflows

</details>

<details>

<summary>Shadow IT Management</summary>

Surface apps discovered by Zylo that aren't in Harmony's approved catalog and trigger review workflows

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.harmony.io/integrations/software-management/zylo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.