Choose your integration below for its setup steps, required credentials, permissions and supported data. Connections have different purposes: collecting provider data, retrieving live information in Ask Lex, or running an automation through Lexful’s API.
PSA integrations
ConnectWise PSA (Manage) — companies, contacts, sites and configurations.
Autotask PSA — companies, contacts, locations and configuration items.
HaloPSA — customers, contacts, sites and assets.
RMM integrations
ConnectWise RMM (Asio) — companies, sites and endpoint inventory. This is not ConnectWise Automate.
Datto RMM — sites, devices and audit/software inventory. Datto sites form the customer mapping groups.
NinjaOne — organizations, locations, contacts and device inventory using Monitoring access.
N-able N-central — customers, sites, devices and lifecycle information using the N-central REST API.
Other data and credential connections
ScalePad Lifecycle Manager — ScalePad Core and Lifecycle Manager data, with subscription requirements explained in the guide.
Microsoft 365 — partner-tenant connection, GDAP customer discovery and customer-consent requirements. Available when enabled for your Lexful account.
CyberQP — synced credential records with on-demand secret access. Available when enabled for your Lexful account.
How data reaches your documentation
Connect the provider. Open Platform → Integrations → Data sources and follow its guide. Use the credentials and API addresses for that specific product.
Check collection. A connection test confirms a limited API request. Review Sync logs to confirm the source tables collected successfully.
Review mapping. Translate source types, statuses and other values into the shared Lexful values.
Configure data sync. Select your primary organization, enable the customers you want and review record filters. Run a sync and inspect a sample result.
Configure mappings and data sync walks through the shared workflow. Not every collected dataset becomes a document or asset: the available mappings and record types determine what is synced.
Ask Lex and automation
Liongard in Ask Lex — query Liongard through an MCP connector during a conversation. This is a live query connection, separate from documentation sync.
Custom integrations — build against Lexful’s API using a dedicated API key.
Third-party integrations
These integrations are developed and operated by the partner and configured in its product using Lexful API credentials. They do not use Lexful’s data-source collection and sync workflow above. Each guide explains the direction of data access and links to the partner’s setup instructions.
Rewst — automate reads and writes through workflows.
NeoAgent — index documentation and configure optional agent API access.
MSP Process — store rotated passwords in mapped Lexful records.
Liongard inspector — read Lexful documentation inventory into Liongard, separate from Liongard in Ask Lex.
Imports and sign-in
Moving documentation and configuring sign-in are separate setup tasks. See IT Glue migration, Hudu migration or Microsoft Entra SSO.
Availability and help
The catalog shown in your account determines which connections you can configure. An early-access or coming-soon entry is not confirmation that data sync is active. If a provider is not available, contact Lexful support; do not use another product’s credentials or setup guide as a substitute.
For a failed connection or missing records, include the provider, failed table or sync stage, approximate run time and visible error. Keep API keys and tokens out of messages and screenshots.