Connect HaloPSA to collect customers, contacts, sites and assets for Lexful. The default collection also reads asset types, customer types/statuses, asset statuses, suppliers and country, currency and tax lookups. It does not collect tickets, contracts or invoices by default.
Prepare a Halo API application
Open Configuration → Integrations → HaloPSA API → View Applications and create an enabled application for Lexful.
Choose Client ID and Secret (Services). Use a dedicated API agent with suitable read access. On versions supporting an application identity, its assigned roles must provide the same access.
In the application’s permissions, allow reading customers, users/contacts, sites, assets, suppliers and the supporting lookup data. Both the application scopes and the agent/identity’s permissions apply.
Securely copy the Client ID and Client Secret. Copy the resource-server and authorization-server addresses from Halo’s API settings.
Follow Halo’s Creating API Applications guide for your version’s options. Lexful uses the client-secret flow; a JWT-assertion requirement is not supported by this connection form.
Connect in Lexful
Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Data sources.
Find HaloPSA 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 HaloPSA.
Lexful field | What to enter |
Client Id / Client Secret | The enabled application’s credentials. |
API URL | Halo’s resource-server address, normally |
Auth Url | Halo’s authorization-server address, normally |
Scope | The form defaults to |
Check the first sync
The connection test checks the Halo client-list endpoint. 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 token can be valid while the agent or application cannot read an asset or lookup. Check both permission layers and the failed table. Use the addresses displayed by your Halo instance, rather than copying another customer’s host.
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.