Skip to main content

Connect ScalePad CS

Connect ScalePad with a personal API key and understand which data is collected and synced.

The ScalePad CS 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 service contracts, contract items and supporting integration data.

  • Lifecycle Manager hardware lifecycle records, assessments, initiatives, goals, 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

  1. 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.

  2. Confirm your subscription: Core API access requires a paid ScalePad product; Lifecycle Manager API access requires Lifecycle Manager Pro or higher.

  3. Plan key rotation before expiration. Removing the owner’s Administrator permission or deactivating the owner stops that key from working.

Connect in Lexful

  1. Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Sources.

  2. Find ScalePad CS and choose Connect. If it is already connected, open the existing connection instead.

  3. Enter the values below. Where the form displays https:// separately, enter the hostname and path without repeating it.

  4. Select Test Connection and resolve any errors. Follow the setup shown for your connection. If you see Save + Configure, save the draft, complete client mapping, choose objects and review the setup before final approval. Other connections use Start import after object selection. Early-access connections also require an explicit syncing opt-in.

Lexful field

What to enter

API Key

The active administrator’s personal ScalePad API key.

API URL

Keep https://api.scalepad.com unless Lexful support directs otherwise. This may appear under advanced settings.

Review the available objects before starting: the list is specific to this integration. Required dependencies are included automatically. Your API credentials must have read access to every selected object and its dependencies. See Choose what to import for selection controls and how to change an existing connection.

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.

  1. Open the connection’s Activity and check that the relevant source tables finish successfully.

  2. Open Mapping → Categories to review provider categories and save any changes.

  3. Open Mapping → Clients to review target clients and Edit rules. Save your decisions, preview the changes, then complete Apply mappings or the setup confirmation. If your connection still uses a separate Sync → Configure sync workflow, review the primary organization, enabled customers and record filters there.

  4. Check a sample organization and its records after syncing. Source collection and writing supported records into Docs are separate stages.

Map integration categories and clients 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. If an expected table is absent, check Objects first. After successful collection, check organization matching, customer selection and record filters. Include the provider, failed table and visible error when contacting support; never include credentials.

Did this answer your question?