Skip to main content

How to configure Lexful integrations

What integrations are currently supported and what do I need to know

Written by Jeremiah Hendrickson

ConnectWise PSA

Get clientId from CW Developer Portal:

https://developer.connectwise.com

Steps to Get a Client ID

  • Go to the ConnectWise Developer Portal.

  • Sign in or register using your corporate email address associated with ConnectWise PSA.

  • Navigate to the ClientID section or go directly to ConnectWise Developer Client ID.

  • Click on Create new integration (if you do not already have one created).

  • Fill out the integration name, description, type, and your technical contact email, then submit the form.

  • Copy the generated Client ID string to use in your third-party application or integration configuration

Get Company ID from Connectwise

  • How to find a Company ID in ConnectWise

  • this is your internal company ID - also if you have a whitelabeled url it’s usually part of your domain slug (like how lexful url’s are [slug].[pod].lexful.app…

Create an API user in ConnectWise and retrieve public key and private key

In Lexful

  • Navigate to Platform > Integrations > Click + Connect for ConnectWise Manage

  • Fill out each field in the UI


API URL:

Cloud-Hosted Instances

If you use ConnectWise cloud hosting, your API base URL depends directly on your region:

  • North America: https://na.myconnectwise.net

  • Europe: https://eu.myconnectwise.net

  • Australia & New Zealand: https://aus.myconnectwise.net

  • Africa: https://za.myconnectwise.net

IMPORTANT: append /v4_6_release/apis/3.0/ to your regional URL (e.g., https://na.myconnectwise.net/v4_6_release/apis/3.0/)

On-Premises Instances

If you self-host your server, your base API URL is your custom domain or Fully Qualified Domain Name (FQDN) used to access the web platform:

  • Format: https://[your-subdomain].[your-domain].com

How to Find Your URL

If you are unsure of your exact hosting domain, you can verify it during login:

  • Open your ConnectWise Manage desktop client or web portal interface.

  • Look at the Site or Server field on the login screen to copy your exact domain address.

After connection is established

Configure Mappings and Data Sync settings

ConnectWise RMM

You will need your Client ID and Client Secret from ConnectWise RMM API Portal

In Lexful

  • Click Connect ConnectWise RMM

After connection is established

Configure Mappings and Data Sync settings

Autotask and Datto RMM

Connecting Autotask PSA

Before You Begin

You'll need an API user configured in Autotask with an integration code, username, and secret key. If you haven't set one up yet, go to Autotask Admin > Resources/Users > API User.

If required, give a custom name to the API Tracking Identifier (i.e. Lexful) and save the Tracking ID somewhere safe, you will need this number in the Lexful settings.

In Lexful

  • Navigate to Platform > Integrations > Click + Connect for datto Autotask PSA

  • Fill out the required fields

  • Your API URL should match your webservices zone number, see example below and replace "5" with your zone as needed

  • API Username - The username associated with your Autotask API user (e.g., your-api-username@company.com)

  • API Secret - The secret key generated for your Autotask API user


​Integration Code = Your Tracking ID

Once all fields are filled in, click Test Connection to validate your credentials and settings. Once green - click Connect Autotask PSA.

After connection is established

Configure Mappings and Data Sync settings

Connecting to datto RMM

Prerequisites

Before configuring the Datto RMM integration in Huntress, ensure the following:

  • You have an active Datto RMM account with administrative access.

  • API Access must be enabled in your Datto RMM account (Setup > Global Settings > Access Control).

  • You have generated an API Key and API Secret Key for a user in your Datto RMM account.

  • You know which platform (cluster) your Datto RMM account is hosted on (e.g., Pinotage, Merlot, Concord, etc...).

Enabling API Access in datto

  • Global Switch: Go to Setup > Global Settings (or Access Control) and turn Enable API Access to On.

  • Generate Keys: Go to Setup > Users, click your API user, and select Generate API Keys

In Lexful

  • Navigate to Platform > Integrations > Click + Connect for datto RMM

  • Enter your Client ID and Client Secret for your API user in datto RMM

  • The Datto RMM API URL is unique to your specific regional platform server and follows the format https://[platform]-api.centrastage.net (replacing [platform] with your assigned server name like merlot, vidal, or concord). You can find your exact API URL inside your Datto RMM instance on your User Details or API configuration page

  • Platform Names: Common server codes include merlot, vidal, concord, pinotage, zinfandel, and syrah.

  • API URL - https://[platform]-api.centrastage.net/

  • Auth URL - https://[platform]-api.centrastage.net/auth/oauth

Once all fields are filled in, click Test Connection to validate your credentials and settings. Once green - click Connect Datto RMM.

After connection is established

Configure Mappings and Data Sync settings

Rewst

HaloPSA

NOTE: We only receive organizations, sites, contacts, assets

Connecting HaloPSA to Lexful

Before You Start

You'll need admin access in both HaloPSA and Lexful to complete this setup.

Part 1: HaloPSA Configuration

Create a Dedicated API Agent

Start by creating a dedicated agent account in HaloPSA that Lexful will use to authenticate.

  • Go to Agents in HaloPSA and create a new agent

  • Give it a clear, identifiable name (e.g., "Lexful Integration")

  • Set a username and password

  • Ensure Account Active is checked

  • Check Is an API-only Agent

⚠️ If you use load balancing or automated ticket assignment, enable Exclude from Automatic Assignment on this agent to prevent it from being assigned tickets.

Click Save.

Configure Agent Permissions

After saving, open the agent and modify its permissions.

  • Set Is a Halo Administrator to No

  • Scroll through the full permissions list and enable only the access levels Lexful requires (we need read only access)

  • Review carefully — some permissions may not be needed depending on your environment and integration configuration

💡 Granting only the permissions you need is a good security practice. You can always adjust these later as your integration evolves.

Click Save.

Create the API Application in Halo

Next, set up the API application that Lexful will connect to.

  • Navigate to Configuration > Integrations > HaloPSA API

  • Click View Applications, then click + New

  • Give the application a clear, identifiable name (e.g., "Lexful")

  • Verify that Active is checked

  • Set the authentication method to Client ID and Secret (Services)

Once you select Client ID and Secret (Services), the Client ID and Client Secret will appear on screen.

📝 Copy both the Client ID and Client Secret — you'll need them in the next step.

  • Set Login Type to Agent

  • Set Agent to Login As to the API agent you created in the previous step

Click Save.

Part 2: Lexful Configuration

With your HaloPSA credentials ready, complete the connection in Lexful.

  • In Lexful, go to Platform > Integrations > Click + Connect for HaloPSA

  • Enter your HaloPSA Client ID, Client Secret key, API URL, and Auth URL

  • Scope should be "all" or "all:standard" but check with Halo directly if you are unsure

  • Click "Test Connection" to verify credentials and permissions have be configured properly, then Connect HaloPSA

After connection is established

Configure Mappings and Data Sync settings

NinjaOne RMM

Connecting NinjaOne RMM to Lexful

Before You Start

You'll need admin access in both NinjaOne and Lexful to complete this setup.

Part 1: NinjaOne Configuration

Create a Client App

  • In NinjaOne, go to Administration > Apps > API

  • Click Client app IDs, then create a new client app

  • Set the Application Platform to API Services

  • Set the Name to something identifiable (e.g., "Lexful")

  • For Redirect URIs, if one isn't provided by your NinjaOne platform, then using localhost should work perfectly fine.

  • Under Scopes, enable Monitoring and Management

  • Leave Control unchecked unless your environment requires it

  • Select Client Credentials for allowed grant types

  • Leave Refresh token unchecked

💡 Lexful only needs Monitoring and Management scopes for standard device sync. Only enable Control if you have a specific use case that requires it.

Click Update to save. NinjaOne will display the Client ID on the app list.

Retrieve Your Credentials

  • Click into the app to open the Edit client app panel

  • Copy the Client ID displayed in the panel

  • Click Generate new secret to create a new secret key if needed

  • Copy the Client Secret immediately - it will not be shown again

⚠️ The Client Secret is only visible once. If you lose it, you'll need to generate a new one, which will break any existing connections using the old secret.

Part 2: Lexful Configuration

Connect NinjaOne

  • In Lexful, go to Platform > Integrations

  • Locate NinjaOne RMM and click Configure

  • Enter your Client ID, Client Secret, API URL, Auth URL, and Scope

  • Scope should be set to monitoring (case sensitive, all lowercase)

  • Test Connection to validate your credentials and settings

📝 The API and Auth URLs must match where your NinjaOne instance is hosted. Check your NinjaOne URL — i.e. app.ninjarmm.com, us2.ninjarmm.com, ca.ninjarmm.com (Canada).

Example:
​

Click Connect NinjaOne RMM.

After connection is established

Configure Mappings and Data Sync settings

Related Articles
Did this answer your question?