Connect a tool
Open Platform → Integrations.
Find your tool under Available. Use Search integrations or the category filters to narrow the catalog.
Click Connect on its card. A card marked Coming soon does not offer a connection action.
Enter the credentials and URLs requested for that provider. Use the provider setup notes below to prepare them.
Click Test Connection and resolve any reported credential, URL, or permission errors.
Click Connect [provider] to create the connection. Lexful starts collecting data automatically after connection.
The connection form changes with the provider. The example below shows the fields for ConnectWise Manage; the fields are intentionally empty.
Prepare your provider credentials
Use credentials created for the integration, and keep their secrets in your password manager. Copy the API endpoint for your own region or instance; a URL from another customer's setup may not work.
ConnectWise Manage / PSA
Obtain a Client ID from the ConnectWise Developer Portal.
Find your Company ID and create an API member with a public/private key pair. Follow the ConnectWise security-role setup guide for the Lexful integration.
In Lexful, enter Company Id, Public Key, Private Key, Client Id, and Api Url.
Use the API URL for your ConnectWise region or self-hosted instance, including its API path. A North American cloud example is
https://na.myconnectwise.net/v4_6_release/apis/3.0/; use your own regional host when different.
ConnectWise RMM
Prepare the Client ID and Client Secret from your ConnectWise RMM API setup. Enter the API URL, authentication URL, and scope requested by the connection form. Use the endpoints and scope supplied for your RMM environment.
Autotask
In Autotask, create or select an API user under Admin → Resources/Users → API User.
Record its username, secret, and API tracking identifier. The tracking identifier is the Integration Code in Lexful.
Find your Autotask webservices zone using the Autotask API zone guidance.
Enter API URL, API User Name, API Secret, and Integration Code in Lexful. The URL must match your zone—for example,
https://webservices5.autotask.net/ATServicesRest/V1.0uses zone 5.NOTE: You must include the version info in the URL as seen in the above example
Datto RMM
Enable API access in your Datto RMM account and generate API credentials for the integration user. Prepare the API key, secret, and the API endpoint for your Datto platform.
The connection form uses Client ID and Client Secret for these credentials. The API host follows https://[platform]-api.centrastage.net; use the platform assigned to your account. The authentication endpoint uses the same host with /auth/oauth.
HaloPSA
Create a dedicated, active API-only Agent in HaloPSA. Give it the read access needed for the records you intend to sync. Exclude it from automatic ticket assignment where applicable.
Open Configuration → Integrations → HaloPSA API → View Applications and create an application.
Choose Client ID and Secret (Services), set the login type to Agent, and select the API agent.
Save the application and securely retain its Client ID and Client Secret.
Enter those credentials and your instance's API URL, Auth URL, and authorized scope in Lexful. Check the application's permissions as well as the agent's permissions if the connection reports an access error.
Use Halo's API documentation for the endpoints and application settings for your instance.
NinjaOne
Create an API Services application with the Client Credentials grant type in NinjaOne. Enable Monitoring access for the data Lexful reads and retain the Client ID and Client Secret. Lexful's NinjaOne connector requests the lowercase monitoring scope.
Enter the credentials and API/Auth URLs for your NinjaOne region. Follow NinjaOne's machine-to-machine application guidance rather than adding an arbitrary redirect URL or extra Management/Control permissions.
Other catalog providers
For other providers with a Connect action, prepare the credentials described in their connection form. Catalog availability and required fields can differ by provider; do not reuse another provider's keys or endpoints.
Rewst
Rewst connects to Lexful through its own integration setup. Follow the Rewst Lexful integration guide; it is separate from the PSA/RMM data-source cards described here.
Review an existing connection
Open its card under Connected. The connection page has three tabs:
Sync logs: review collection status and timestamps by source table. Use All tables and All statuses to narrow the history.
Mapping: translate source values, such as customer and device types, into Lexful values. Review each table and click Save after changes.
Settings: inspect the stored connection settings and use Test Connection to check access. This view is read-only; it is not a credential-editing form.
Choose what reaches Lexful
A successful connection collects source data. Mapping and sync configuration determine how that data becomes records in Lexful. Continue with Configure mappings and data sync to map values, select the primary organization, and choose customers and record types.
If something is missing
Connection test fails: check the provider, region, endpoint, credentials, and API permissions. Do not share secrets in a support message or screenshot.
Mapping is empty: allow the initial collection to finish, then check Sync logs and return to Mapping.
Connected, but records are missing: check the relevant table's collection result, saved mappings, primary organization, customer sync selection, and record filters. A connected source alone does not mean every record is included.