---
title: "N-Able Integration: Overview "
url: "https://help.psarev.io/en/article/n-able-integration-overview"
language: "en"
last_updated: "2026-06-04T22:00:42.310Z"
---

# N-Able Integration: Overview 

N-Able is a cloud-based IT management and cybersecurity solution designed specifically for managed service providers and IT service providers. Integrating Rev.io with N-Able allows you to keep your customer data, devices, and alerts synchronized between the two platforms, reducing manual data entry and keeping your systems aligned.

You can integrate Rev.io with N-Able using the Integrations Library in the Admin module. The integration supports the following synchronization between Rev.io and N-Able:

-   **Customer Sync:** Bidirectional sync between N-Central customers and Rev.io customers. Rev.io pushes customer updates to N-Central on a scheduled basis, and new N-Central customers can be linked to Rev.io accounts during initial setup.
-   **Asset Sync:** One-way sync of N-Central devices to Rev.io assets. Devices are automatically matched to existing assets by serial number or name, and new assets are created when no match is found. Runs hourly.
-   **Alert-to-Ticket Sync:** Active N-Central monitoring alerts are polled every 5 minutes and automatically create Rev.io tickets. When an alert clears in N-Central, the corresponding Rev.io ticket is automatically closed. Alert tickets are linked to the associated Rev.io asset when available.

| **NOTE:** Alert sync is disabled by default. You can enable it in the integration configuration. Before enabling, review your N-Central monitoring policies to ensure only the alerts you want to generate tickets are active, as all active alerts will create tickets once sync is turned on. |
| --- |

* * *

## Sync Details

### Customer Sync

Customer data synchronizes automatically on a scheduled basis. Rev.io is the primary system of record for customer information. During initial setup, N-Central customers are matched to Rev.io customers by name, and you can review and approve matches before the sync begins.

### Asset Sync

N-Central devices sync to Rev.io assets every hour. The integration uses a three-tier matching strategy to avoid duplicates.

-   **Serial number match:** If an N-Central device's serial number matches an existing unlinked Rev.io asset, the two are linked automatically.
-   **Name match:** If no serial number match is found, the integration compares device names using fuzzy matching.
-   **Create new:** If no match is found, a new Rev.io asset is created.

Synced asset fields include device name, serial number, MAC address, IP address, operating system, model, processor, and memory. Assets linked to a different RMM integration are not overwritten.

### Alert-to-Ticket Sync

When enabled, the integration polls N-Central for active monitoring alerts every 5 minutes. For each new alert, a Rev.io ticket is created with the following details.

| **Field** | *Value* |
| --- | --- |
| **Title** | *Alert service name and device name.* |
| **Type** | *RMM Alert (or EDR Alert for EDR-related services).* |
| **Priority** | *High.* |
| **Status** | *New.* |
| **Description** | *Alert details including category, device, notification state, and timestamps.* |

When an alert clears in N-Central, the integration automatically sets the corresponding Rev.io ticket status to "auto-closed" and adds an activity note recording the closure. If the alerting device has a linked Rev.io asset, the asset is automatically attached to the ticket.

To configure the N-Able integration for your environment, see the [**N-Able Integration: Configuration**](https://help.psarev.io/en/article/n-able-integration-configuration) article.