Your Lexful records, powering every ticket.
Neo indexes every asset type in your Lexful account, custom ones included, and reads the right record before acting. Passwords and secured fields never leave Lexful.
What Neo does with Lexful.
Custom types included
Neo reads your asset types from Lexful on every run instead of a fixed list, so a type you add is picked up on the next sync.
Policy-aware resolutions
Neo looks up per-client 2FA rules, onboarding templates, and approved software before it acts.
Passwords are never indexed
The password asset type and every field Lexful types as secret or TOTP are excluded from the index. Neo records that a credential exists, never the value.
Concrete work Neo handles in Lexful.
Per-client onboarding
Neo reads the client's onboarding record, then applies the right groups, licenses, device profile, and signature.
Asset-aware tickets
When a ticket names a device, domain, or contact, Neo pulls that record for context before acting.
Keeps records current
With write permission, Neo updates the related Lexful asset after a change, so your documentation does not drift.
Live in under an hour.
Connect, configure, go. No code, no long implementation.
Create an API key
In Lexful, generate a key under Settings, Platform, APIs. Neo needs the Key ID, the secret, and your Account ID.
Connect Lexful
Add the four values in Neo. Each one is verified against Lexful before it is saved, so a wrong value is refused at setup.
Map your organizations
Neo matches Lexful organizations to your PSA companies by name, domain, then AI. Review each match and correct it by hand where you want to.
Questions about the Lexful integration.
Are our Lexful passwords synced?+
No. The password asset type is excluded whole, and any property Lexful types as secret or TOTP is excluded on every asset type, including custom ones.
Can an agent still read a credential when it has to?+
Only if you allow it. That runs live through the Lexful API tool, where it needs its own permission group and technician approval.
Does Neo pick up our custom asset types?+
Yes. Neo reads your schema at the start of each sync, so a custom type is indexed the same way as the built-in ones.
How often does it sync?+
Daily, with the first run starting within about 15 minutes of connecting. Trigger sync starts a run straight away.
How is the API key stored?+
In Azure Key Vault, encrypted at rest, and never shown back in the dashboard in plaintext.
Ready to wire up Lexful?
14-day free trial. No credit card. Live in under an hour, right inside your stack.