The Lifecycle Manager connection reads ScalePad Core data and Lifecycle Manager data. It is separate from the ControlMap and Quoter connections, and from a custom integration that writes to Lexful’s API.
What Lexful reads
Core clients, contacts, members and hardware/SaaS inventory, plus supporting opportunity, service and integration data.
Lifecycle Manager hardware lifecycle records, assessments, initiatives, action items, meetings, notes, client groups and deliverables.
Collection makes source data available to Lexful. The standard documentation sync creates or updates supported records such as organizations, contacts and configurations; it does not turn every initiative, assessment or meeting into a document automatically.
Prepare ScalePad
Use an active ScalePad user with Administrator permission. In the user’s personal API keys page, select New API key, choose a name and expiration, and securely save the key.
Confirm your subscription: Core API access requires a paid ScalePad product; Lifecycle Manager API access requires Lifecycle Manager Pro or higher.
Plan key rotation before expiration. Removing the owner’s Administrator permission or deactivating the owner stops that key from working.
See ScalePad’s API-key instructions and product API subscription requirements.
Connect in Lexful
Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Data sources.
Find Lifecycle Manager and choose Connect. If it is already connected, open the existing connection instead.
Enter the values below. Where the form displays https:// separately, enter the hostname and path without repeating it.
Select Test Connection. Resolve any error, then select Connect Lifecycle Manager.
Lexful field | What to enter |
API Key | The active administrator’s personal ScalePad API key. |
API URL | Keep |
Check the first sync
The connection test checks the ScalePad Core client list. It does not prove that every source table is readable or that records have reached your documentation.
Open the connection’s Sync logs and check that the relevant source tables finish successfully.
Review Mapping for source types, statuses and other values. Save any changes.
Open Data sync → Configure sync, save your primary organization, enable the customers you want, and review the available record filters.
Run Sync now on Data sync, review the result, then check a sample organization and its records.
Configure mappings and data sync explains these steps in detail. Collection from the provider and syncing records into Lexful are separate stages.
If something is missing
A successful client-list test does not prove your subscription can access Lifecycle Manager endpoints. If Core collection works but Lifecycle Manager tables fail, check the Pro subscription and key owner’s access. Review imported clients before enabling their documentation sync.
A successful test followed by a failed table usually means that table needs additional read access. A successful collection followed by missing records usually means organization matching, customer selection or record filters need review. Include the provider, failed table and visible error when contacting support; never include credentials.