Autotask PSA

Autotask PSA

This connector uses the Autotask REST API (/ATServicesRest/V1.0) of Autotask PSA by Datto (Kaseya): companies, contacts, tickets, notes, time entries, projects, tasks, resources, contracts and configuration items.

Setup

1. In Autotask create an API-only resource (Admin, Resources/Users, New API User) with the API User (API-only) security level. On its Security tab, under API Tracking Identifier, pick your integration vendor or let Autotask generate a custom (internal integration) identifier. The username (an email such as [email protected]), the generated secret and the tracking identifier are the three credentials.
2. AUTOTASK_USERNAME = the API user's username, AUTOTASK_SECRET = its secret, AUTOTASK_INTEGRATION_CODE = the API tracking identifier.
3. AUTOTASK_ZONE_HOST: every Autotask database lives in one zone with its own host. Open https://webservices.autotask.net/atservicesrest/v1.0/zoneInformation?user=<API username> in a browser; the url field shows the host, for example webservices5.autotask.net. Enter only the host.

The three values travel as the ApiIntegrationCode, UserName and Secret headers. A wrong zone answers 500 or 401 even with correct credentials.

Querying

Read tools are POST /<Entity>/query searches (marked read-only). filter is an array of conditions, AND-combined: {"op": "eq", "field": "status", "value": 1}. Operators: eq, noteq, gt, gte, lt, lte, beginsWith, endsWith, contains, exist, notExist, in, notIn; nest with {"op": "or", "items": [...]}; user-defined fields need "udf": true. A query must have at least one condition; the default {"op": "gte", "field": "id", "value": 0} matches everything. Field names are camelCase as in the answers (companyID, assignedResourceID, dateWorked).

Picklists

Status, priority, queue, issue type, note type and similar fields are numeric ids that differ per database. Call autotask_get_entity_fields (for example entity Tickets) to read the allowed values and labels before filtering or writing them. Ticket status 5 is Complete in a default setup.

Paging and limits

A query returns at most 500 records (max_records). To read more, sort by id: repeat the query with an extra condition {"op": "gt", "field": "id", "value": <last id>} until fewer records come back. pageDetails also carries nextPageUrl. Use include_fields to keep answers small. Autotask allows 10,000 requests per hour per database and slows responses above half of that; use autotask_count_tickets for counts instead of reading every ticket.

Start here

autotask_query_companies to find a company id, then autotask_query_tickets with companyID, then autotask_get_ticket and autotask_query_ticket_notes. For time reports, autotask_query_resources gives the resource id for autotask_query_time_entries.

Writes

Creating and updating tickets, adding ticket notes and logging time change data and can trigger customer notifications through workflow rules. Nothing is deleted by this connector.