Prerequisites and HaloPSA Integration Process Overview

Before you start the integration, make sure N-central and HaloPSA are fully configured, including downloading and setting up the HaloPSA client.

Prerequisites

N-central readiness

  • N-central release with native HaloPSA support:

    • 2025.4 GA or later, or

    • 2025.2.1 to 2025.3 (early access with HaloPSA feature flag enabled)

  • Valid SSL certificate on the N-central server

  • Successful DNS resolution of the N-central server

HaloPSA readiness

  • Access to a live HaloPSA instance URL (e.g., https://<tenant>.halopsa.com)

  • Valid SSL certificate on the HaloPSA server

  • Successful DNS resolution of the HaloPSA server

  • Ability to download and install the HaloPSA client

  • Permissions to configure an application in HaloPSA and generate Client ID and Client Secret

Network and security

  • N-central host can reach HaloPSA API endpoints (DNS, firewall, proxy rules validated)

  • Add N-central host to HaloPSA CORS whitelist if required

Operational readiness

N-central

  • Ensure customers, sites, and devices are correct and follow a consistent structure and naming convention.

  • Align Discovery Job auto-import settings with the device classes under management.

  • Verify that the user role includes Manage permission for PSA integration and ticketing before starting the integration.

  • Complete notification profiles, including:

    • Accurate notification recipients

    • Escalation paths

    • Acknowledgement settings

    • Trigger details

  • Plan device class mapping for accurate ticket routing.

  • Link notification profiles to ticketing recipients for automated ticket creation.

HaloPSA

  • Ensure customers and sites in HaloPSA align with the structure and naming used in N-central. When creating a customer, set the Customer level to Main.

  • Review ticket types and ticket category groups to ensure they support automatic assignment of:

    • Team

    • Agent

    • Workflow

    • Response template

    • End-user actions

  • Verify that billing settings and templates are configured correctly and included in ticket automation settings.

  • Prepare a customer mapping strategy (customers/sites to accounts).

In addition to these prerequisites, you should have a solid understanding of N-central configuration, notifications, templates, and APIs, as well as thorough knowledge of HaloPSA.

Integration Process Overview

After HaloPSA is set up, integrate N-able N-central with HaloPSA through the PSA Configuration feature in N-able N-central.

  1. Set up the HaloPSA integration in N-able N-central.
  2. Map customers.
    • Before exporting devices or creating tickets, map N-central customers to their corresponding HaloPSA accounts.
    • The HaloPSAdatabase automatically populates the list of available HaloPSA customers.
  3. Map device classes.
    • Associate N-central device classes to HaloPSA asset types to ensure accurate ticket routing and reporting.
  4. Export Devices.
    • Create an export profile in N-able N-central to allow devices to be exported to HaloPSA for ticketing.
  5. Set up a Ticketing Recipient.
    • Configure a ticket recipient so HaloPSA tickets to appear in N-able N-central.
  6. Set up N-able N-central Notifications to update ticket status.
    • Configure notifications in N-able N-central to update the ticket status when the status of a service returns to Normal.