The Autotask integration collects companies, contacts, configuration items and company locations. Lexful maps these into organizations, contacts, configurations and locations after you configure data sync.
What Lexful reads
The default collection includes companies (including vendor records), contacts, configuration items, company locations, categories and supporting country, currency, tax, billing-term and internal-location data. Service tickets, projects and invoices are not part of the default collection. This is an inbound integration; it does not edit Autotask records.
Create the API user
In Autotask, open Admin → Resources/Users and create a dedicated API User. Assign an API User (API-only) security level. A normal sign-in user is not sufficient for the REST API.
Set and securely retain the API username and secret. Record the user’s API tracking identifier from its Security settings; Lexful calls this Integration Code.
Check that the API user can read companies, contacts, configuration items, locations and the reference data listed above. A restricted copy of the API security level can hide records even when authentication succeeds.
Find the REST API zone for this API user. Include /ATServicesRest/V1.0 in the API URL.
See Autotask’s REST authentication requirements and zone lookup instructions.
Connect in Lexful
Sign in to the intended Lexful account as an administrator. Open Platform → Integrations → Data sources.
Find Autotask 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 Autotask.
Lexful field | What to enter |
API URL | Your zone’s REST root, for example |
API User Name | The dedicated API user’s username. |
API Secret | That user’s API secret. |
Integration Code | The tracking identifier assigned to that API user. |
Check the first sync
The connection test checks the Autotask API version endpoint using your credentials. 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
For authentication errors, check the username, secret and tracking identifier together. For URL errors, check both the zone and the version path. Empty results can also reflect the API user’s restricted security level.
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.