> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Autotask PSA

> Connect Autotask PSA to Triggr with an API-only user, then map your clients to Autotask companies.

Triggr works with Autotask tickets, ticket notes, companies, contacts and other entities, including their fields and picklist values. It appears in Triggr as Autotask.

## Set up Autotask

**1. Create an API user**

Go to **Admin > Admin Categories > Organization Settings & Users**, open Resources/Users (HR) > Resources/Users, click New and select New API User.

**2. Fill in the user**

Set Security Level to API User (system) (API-only), or API User (system) Can't Read Costs (API-only) to hide your internal costs. Email Address receives Autotask's notifications about the integration, and Primary Internal Location sets the user's timezone.

**3. Generate the credentials**

Under Credentials, click Generate Key and Generate Secret. Copy the full Username (Key), including the `@` and domain, and the Password (Secret).

**4. Create a tracking identifier**

Under API Tracking Identifier, select Custom (Internal Integration), enter `Triggr` as the Internal Integration Name and copy the Tracking Identifier.

**5. Save the API user**

Leave Line of Business without associations and click Save & Close. Autotask won't show the secret again.

**6. Find your API zone**

Open this address in a browser (no sign-in needed), replacing `USERNAME` with the API user's full username:

```text theme={null}
https://webservices.autotask.net/atservicesrest/v1.0/zoneInformation?user=USERNAME
```

Your API host is the `url` in the response up to `/atservicesrest/`, such as `https://webservices5.autotask.net`.

See Autotask's guide to [adding an API user](https://autotask.net/help/Content/4_Admin/1CompanySettings_Users/ResourcesUsersHR/Resources/API_User_Add_Edit.htm).

## Connect it in Triggr

**1. Open the integration**

Go to **Integrations > Autotask** and click **Configure** on the Base Configuration card.

![The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/base-configuration.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=bb81acb082055015f91beda7b4876f35)

**2. Enter the credentials**

Enter the Password (Secret) as Secret, your API host as Hostname (without `/atservicesrest`), the full username as UserName and the Tracking Identifier as ApiIntegrationCode, then click **Save Configuration**.

![The Autotask configuration window with Secret, Hostname, UserName and ApiIntegrationCode fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/autotask/configure.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=8eac59d42699ef5cfb57ec5471aa7007)

## Map your clients

On the Client Mapping card, click **Apply 100% Matches**, then choose the Autotask company in Mapped to for anyone left. Only active companies of type Customer or Partner are listed. Triggr saves each match as the client's `autotaskId` variable, which steps such as Create Ticket use to pick the company.

![The Client Mapping card with All, Mapped and Unmapped filters, Acme Corp mapped to Acme Corp with a 75% suggested mapping, and Globex unmapped with a Select ConnectWise Manage clients dropdown.](https://mintcdn.com/triggr/nyuVXZ1rouDTTEvu/images/integrations-common/client-mapping.png?fit=max\&auto=format\&n=nyuVXZ1rouDTTEvu\&q=85\&s=da797e78dc917005df8e55c6b6cb166b)

The Client Mapping card, shown here for ConnectWise Manage as an example.

Ticket steps run against the PSA set as Default PSA: in Triggr Core, Settings > General; in Studio, Settings > Org Variables > Setup Wizard. See [Connect your PSA](https://kb.mspprocess.com/core/get-started/connect-your-psa.md).

## Troubleshooting

> [accordion] Authentication errors (401)
>
> Check UserName is the full username and ApiIntegrationCode is the same user's Tracking Identifier. In Autotask, check the API user is Active; Autotask locks it after failed sign-ins, so clear Locked if it's ticked.

> [accordion] Requests fail with correct credentials
>
> Hostname must start with `https://`, must not end in `/atservicesrest` and must be your own zone's host.

> [accordion] Lost or rotated secret
>
> Click Generate Secret on the API user and Save & Close. In Triggr, click Edit on the Base Configuration card and paste it into Secret.

> [accordion] Companies are missing from Client Mapping
>
> Check the company is active and a Customer or Partner, and that the API user's security level doesn't hide it. Then click Refresh on Client Mapping.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.