Skip to main content
The Lexful API tool gives Neo agents direct access to the Lexful REST API — read, create, update, and delete Lexful records during ticket resolution.
Automatically enabled when you configure Lexful permissions in your agent. No manual toggle needed.

​
What It Does

  • Look up customer organizations and the documentation stored against them
  • Read documentation pages, configurations, contacts, and locations — including custom asset types you’ve defined
  • Create and update documentation from ticket resolutions
  • Read asset type schemas to understand what each kind of record holds
  • Download file attachments when the answer lives in an attached diagram or export
  • Access any Lexful API endpoint with permission-group-based access control
For “what do we know about X”, Neo’s own Find Documentation tool is usually the better first stop — Neo syncs your Lexful documentation into its search index daily, and that search spans every documentation source you’ve connected. Reach for the Lexful API tool when you need something the sync doesn’t carry: a live value, a non-document asset type, file attachments, or a write.

​
Permission Groups

Each group has an access level: Disabled, Read Only, or Read/Write. Secure Properties is read-only by design — storing a secret happens through Assets like any other property.

​
Access Profiles

All groups Read Only, except Secure Properties which stays off. The agent can look up any record but cannot modify anything or read a stored secret.
Assets, Asset Files, and Tags at Read/Write — the surfaces where documentation lives. Organizations, Asset Types, and Search stay Read Only. Secure Properties stays off.
Every group Read/Write with delete enabled, except organizations and asset types (which can never be deleted). Secure Properties still stays off — reading credentials in plaintext is always a separate, deliberate decision.

​
Safety Controls

​
How to Configure

1

Connect Lexful

Connect your Lexful account in the Neo Dashboard’s Integrations page with your API key ID, secret, and account ID.
2

Configure permissions

In your agent’s Integrations tab, choose an access profile or customize each permission group.
3

Set approval requirements

Decide which permission groups require technician approval for writes. Writes that set a credential always require approval, whatever you choose here.
Only enable Secure Properties if an agent genuinely needs to read stored credentials — including the historical values of rotated ones. It is in no access profile, so leaving it alone means the capability isn’t there at all.