Backup, network, and licensing integrations

Connect backup, network monitoring, licensing, remote access, and automation tools to pull client and device data into MSP Recapp for unified visibility.

Beyond your PSA, RMM, and endpoint security stack, MSP Recapp integrates with a broad range of additional tools — from backup and disaster recovery platforms to licensing, network monitoring, and remote access. Each integration follows the same lifecycle: connect with credentials, sync companies or accounts, then sync devices.

Backup & Recovery

Axcient x360Recover

Syncs: Clients, Devices

Axcient x360Recover is a backup and disaster recovery platform for MSPs. Recapp connects via the Axcient API using a single API token. The same token also works for x360Cloud (Microsoft 365 backup).

Required credentials

Field	Description
API Token	Your Axcient API token — found in Settings → API in the Axcient x360Recover portal

Network Monitoring

Auvik

Syncs: Tenants, Devices

Auvik is a network monitoring and infrastructure management platform. Recapp authenticates using an API key (used as a username) and an API secret (used as a password), and supports multiple regional endpoints.

Required credentials

Field	Description
Region	Your Auvik region: US1, US2, US3, EU1, or AU1
API Key (Username)	Your Auvik API key — generate credentials under Admin → API in the Auvik portal
API Secret (Password)	Your Auvik API secret from the same location

Domotz

Syncs: Accounts, Devices

Domotz is a network monitoring and management platform. Recapp connects via the Domotz API using a single API key, with support for US, EU, and APAC regional endpoints.

Required credentials

Field	Description
Region	Your Domotz region: US East (N. Virginia), EU Central (Frankfurt), or Asia Pacific (Sydney)
API Key	Your Domotz API key — found under Settings → API in the Domotz portal

RMM & Automation

ImmyBot

Syncs: Tenants, Computers

ImmyBot is an automated software deployment and endpoint management platform built on Azure AD. Recapp connects using your ImmyBot instance subdomain and an Azure AD app registration with a client ID and client secret.

Required credentials

Field	Description
Instance Subdomain	The subdomain from your ImmyBot URL, e.g. acme from acme.immy.bot
Azure Tenant ID	Your Microsoft Entra ID (Azure AD) tenant ID (GUID)
Application (Client) ID	The Client ID from your Azure AD app registration
Client Secret	A client secret created in Azure AD → App registrations → Certificates & secrets

Licensing & Billing

Microsoft 365

Syncs: Users, Licenses, Mailboxes, Groups

The Microsoft 365 integration connects to a single Microsoft 365 tenant using an Azure AD app registration. Use this when you want to pull license and user data from one specific tenant — for example, your own MSP tenant or a single client’s environment.

Required credentials

Field	Description
Azure Tenant ID	The Azure AD tenant ID (GUID) for the tenant you want to pull data from
Client ID	Your Azure AD app registration Client ID
Client Secret	Your Azure AD app registration Client Secret

Required Microsoft Graph application permissions (admin consent required):

• User.Read.All — Read all users’ profiles
• Organization.Read.All — Read organization info
• Directory.Read.All — Read directory data
• DeviceManagementManagedDevices.Read.All — Intune managed devices

This integration connects to a single tenant. If you manage multiple Microsoft 365 tenants through a CSP or GDAP relationship, use the Microsoft CSP integration instead.

Microsoft CSP

Syncs: Tenants

The Microsoft CSP integration connects to your Microsoft Partner Center account and uses GDAP (Granular Delegated Admin Privileges) to access your customer tenants — eliminating the need for per-customer admin consent.

Required credentials

Field	Description
Azure Tenant ID	Your MSP’s Azure AD partner tenant ID (GUID)
Client ID	Your Azure AD app registration Client ID
Client Secret	Your Azure AD app registration Client Secret
Partner Refresh Token	A long-lived SAM (Secure Application Model) refresh token — captured via the self-service onboarding wizard or pasted from a tool like CIPP

Authentication method

Recapp defaults to the SAM (Secure Application Model) / GDAP-delegated path, which requires a one-time sign-in by your SAM service account to capture a long-lived refresh token. After that, every sync uses your GDAP role assignments — no per-customer consent is ever needed.

1. Enter app registration details

   Fill in your Azure Tenant ID, Client ID, and Client Secret.

2. Run the onboarding wizard (recommended)

   Click Run Self-Service Onboarding Wizard to sign in as your SAM service account and capture the refresh token automatically.

3. Or paste a pre-generated refresh token

   If you already have a SAM refresh token from CIPP or another tool, paste it into the Partner Refresh Token field and click Test SAM Token to validate it.

4. Save

   Once the SAM token is validated, click Save to store the integration.

A legacy per-tenant client_credentials fallback is available for environments without GDAP relationships. This path requires each customer admin to grant consent individually and is not recommended for MSPs managing many tenants.

The app registration requires the following permissions with admin consent in your partner tenant:

Microsoft Graph — Application: Device.ReadWrite.All, User.ReadWrite.All, Directory.ReadWrite.All, Organization.ReadWrite.All, DelegatedAdminRelationship.ReadWrite.All, DeviceManagementManagedDevices.Read.All

Microsoft Graph — Delegated: AppCatalog.Read.All, DelegatedAdminRelationship.ReadWrite.All, Device.Read.All, Directory.ReadWrite.All, Organization.ReadWrite.All, User.ReadWrite.All

Microsoft Partner Center — Delegated: user_impersonation

Office 365 Exchange Online: Exchange.ManageAsApp (Application), Exchange.Manage (Delegated)

Office 365 Management APIs — Delegated: ActivityFeed.Read, ServiceHealth.Read

Partner Customer Delegated Administration — Delegated: PartnerCustomerDelegatedAdministration.ReadWrite.All

Pax8

Syncs: Companies, Subscriptions

Pax8 is a cloud marketplace platform for MSP licensing and subscription management. Recapp connects via the Pax8 API using a client ID and client secret.

Required credentials

Field	Description
Client ID	Your Pax8 Client ID — found in Settings → Integrations → API Keys in the Pax8 portal
Client Secret	Your Pax8 Client Secret from the same location

Remote Access

ScreenConnect

Syncs: Sessions, Devices, Access Groups

ScreenConnect (ConnectWise Control) tracks remote access sessions and the devices associated with them. Configuration for this integration is handled through the integration settings dialog after adding it.

ScreenConnect setup requires additional configuration steps after the initial connection. Use the Settings option on the integration card after adding it to complete the setup.

Other

Tier2Tickets

Syncs: Agents (via CSV)

Tier2Tickets is a help-desk button and diagnostic tool. Because Tier2Tickets does not expose a live API, Recapp imports agent data via CSV file upload.

Setup steps

1. Export from Tier2Tickets

   Generate a device/agent export from your Tier2Tickets account. The expected CSV columns include: macAddress, machineName, lastSeen, domain, tags, and others.

2. Add the integration in Recapp

   Go to Integrations → Add Integration and select Tier2Tickets.

3. Upload the CSV

   In the setup dialog, upload your CSV export. Recapp parses the file, merges duplicates, and imports device records.

Because Tier2Tickets uses CSV import, there is no live API sync. To refresh device data, upload a new CSV export. You can also upload a CSV later by opening the Settings for the existing Tier2Tickets integration.