Skip to main content

Connect Syncro to Lexful

Connect Syncro customers, contacts and device inventory using an API token.

Connect Syncro to collect customer, contact and device inventory for use in Lexful.

Early access: This integration supports syncing, but is still being tested and data may be incomplete. Saving credentials alone does not enable syncing; opt in when you are ready.

Prepare your Syncro API token

Create a Syncro API token with read access to customers, contacts, assets and the settings needed to interpret asset types and fields. Keep the token secure and note your Syncro instance address. See the official Syncro API documentation for the available API permissions and resources.

Connect in Lexful

  1. As a Lexful administrator, open Platform → Integrations → Sources, find Syncro, and choose Connect. Open the existing connection if you have already added it.

  2. Enter Syncro Instance URL, for example https://your-subdomain.syncromsp.com. Do not append /api/v1; Lexful adds it. Where the form shows https:// separately, do not repeat it.

  3. Paste the token into API Token.

  4. Choose Test Connection and resolve any errors. Select Enable early-access syncing when available if you want to start collecting data, then choose Save credentials. If you save without opting in, use Start syncing on the connection when ready.

What syncs

  • Customers, including disabled customers returned by Syncro.

  • Contacts.

  • Devices and their asset-type information, including available name, serial number, model, manufacturer, operating system, CPU, memory and network addresses.

Customers, Contacts and Devices are selectable source objects. Required device settings are included as dependencies. Purchase and warranty dates are not currently mapped by this integration. It does not recover permanently deleted records or import historical versions of every asset.

Check the first sync

Open the connection’s Activity and check the relevant source tables. A successful connection test checks a limited API request; it does not confirm a complete sync.

Collected source data does not automatically become a document or asset for every source object. Review the available mappings, customer selection and filters before syncing supported records into your organizations. See Map integration categories and clients and Choose what to import.

If the connection or inventory fails

Check the instance address, token validity and read permissions. The connection test reads customers only; collecting contacts or devices can still fail if the token cannot read those resources or their settings. If collection succeeds but an expected record is absent in Lexful, check customer selection, mappings and filters.

If an error remains, use Support in Lexful or contact us. Include the provider, failed source table and visible error. Do not send API keys, secrets or passwords.

Did this answer your question?