> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/connectors/autotask.md).

# Autotask connector

The Autotask connector: sync tickets, companies, contacts and configuration items between equipme and Autotask – connection, triggers, actions, examples.

**Path:** sidebar → **"Automation" → "Workflows"** → flow designer → connector **"Autotask"**

With the **Autotask connector**, you connect equipme in [workflows](https://hub.equipme.io/dokumentation/automation/workflows.md) with **Autotask**, the PSA and ticketing system used by your IT department or your IT service provider. Events in equipme automatically create tickets in Autotask, and changes to devices or contacts in Autotask reach equipme.

## What for?

* **Onboarding and offboarding:** Create a ticket with a checklist in Autotask for a new or departing employee in equipme.
* **Match device assignments:** Read configuration items (devices) from Autotask and store the serial number or ticket reference on the asset in equipme.
* **Keep employee data up to date:** When an employee changes in equipme, update the matching contact in Autotask.
* **Follow helpdesk tickets:** When tickets change in Autotask, notify the people involved or document the status in equipme.

## Prerequisites

* The activated [Automation module](https://hub.equipme.io/dokumentation/automation.md)
* Access to an **Autotask instance** with an **API user** – with username, secret and **API Tracking Identifier**. An Autotask administrator creates the API user.
* Sufficient permissions of the API user for the areas the flow uses (tickets, companies, contacts, configuration items, contracts, products)
* For the triggers: the API user must be allowed to create webhooks in Autotask

## Setting up the connection

1. Have the API user's username, secret and API Tracking Identifier from Autotask ready.
2. In the flow designer, drag a component of the Autotask connector onto the canvas (e.g. *ListCompanies*).
3. Click **Connect account** and enter:
   * **Username** – username of the API user
   * **Secret** – the API user's secret
   * **API Tracking Identifier** – the integration's tracking identifier
4. The connector automatically determines the correct Autotask data center and checks the credentials. The connection then appears under **"Accounts"** and is available to all Autotask components.

{% hint style="info" %}
In the flow designer, the components carry their technical name (e.g. *AddTicket*). Select fields such as "Priority", "Status", "Queue" or "Company type" load their values directly from your Autotask instance.
{% endhint %}

## Triggers

| Component        | Fires when …                             |
| ---------------- | ---------------------------------------- |
| WatchTickets     | a ticket is changed                      |
| WatchTicketNotes | a ticket note is changed                 |
| WatchCompanies   | a company is changed                     |
| WatchContacts    | a contact is changed                     |
| WatchAssets      | a configuration item (device) is changed |

All triggers have the same settings:

* **"Trigger fields"** – the fields whose change fires the flow (e.g. status or priority of a ticket)
* **"User defined trigger fields"** – additional user-defined fields from Autotask
* **"Notifications email address"** – address to which Autotask sends notices about this notification

Autotask reports the change to equipme immediately; there is no periodic polling. The trigger returns the data of the change, i.e. the ID and the selected fields.

## Actions

### Companies and contacts

| Component                  | Purpose                                | Key options                                                                                                                                                   |
| -------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddCompany                 | Create a company                       | Required: "Company name", "Company type", "Account manager", "Phone"; address, "Company category", "Parent company", "Currency", "Invoice template", "Active" |
| UpdateCompany              | Change a company                       | "Company" (ID) and the fields to change                                                                                                                       |
| GetCompany / ListCompanies | Read companies                         | "Company" or "Filters"                                                                                                                                        |
| ListCompanyLocations       | List company locations                 | "Filters"                                                                                                                                                     |
| GetContact / ListContacts  | Read contacts                          | "Contact" or "Filters"                                                                                                                                        |
| UpdateContact              | Change a contact                       | "Contact" (ID); name, email addresses, phone, address, "Is active", "External ID"                                                                             |
| UpdateCompanyContact       | Change a contact of a specific company | "Company" and "Contact" (IDs) and the same fields as *UpdateContact*                                                                                          |

### Tickets

| Component              | Purpose                                     | Key options                                                                                                                                                                                                                                        |
| ---------------------- | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddTicket              | Create a ticket                             | Required: "Company", "Title", "Status", "Priority", "Due date time"; "Description", "Queue", "Ticket type", "Issue type", "Sub issue type", "Contact", "Configuration item", "Contract", "Assigned resource", "External ID", "User defined fields" |
| GetTicket              | Read a ticket                               | "Ticket" (ID)                                                                                                                                                                                                                                      |
| AddTicketChecklistItem | Add a checklist item to a ticket            | Required: "Ticket ID", "Item name"; "Position", "Is important", "Is completed"                                                                                                                                                                     |
| AddTicketCharge        | Record a charge (e.g. material) on a ticket | Required: "Ticket ID", "Name", "Charge type", "Cost type", "Date purchased", "Unit quantity"; "Product ID", "Unit cost", "Unit price", "Is billable to company"                                                                                    |

### Devices, contracts, products and services

| Component                                 | Purpose                            | Key options                                                                                            |
| ----------------------------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------ |
| ListConfigurationItems                    | List configuration items (devices) | "Filters"                                                                                              |
| ListContracts                             | List contracts                     | "Filters"                                                                                              |
| GetService / ListServices / UpdateService | Read and change services           | "Service" (ID); name, prices, "SKU", "Is active", "User defined fields"                                |
| GetProduct / ListProducts / UpdateProduct | Read and change products           | "Product" (ID); name, manufacturer, "SKU", prices, "Is serialized", "Is active", "User defined fields" |
| ListOpportunities                         | List opportunities                 | "Filters"                                                                                              |
| ListTaxRegions                            | List tax regions                   | "Filters"                                                                                              |

### Filters in list actions

List actions offer **"Filters"** made of conditions: "Field" (field from Autotask, selectable), "Operator" ("equal to", "not equal to", "greater than", "less than", "begins with", "ends with", "contains", "exist", "not exist", "in", "not in" and more) and "Value". Conditions can be combined with AND and OR. With **"Use user defined field"** you filter by a user-defined field – this is possible **once per filter**. Without a filter, the action returns all entries.

## Examples

### Onboarding ticket for new employees

1. **Trigger:** *Equipme › New Employee* (see [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md)).
2. **Autotask › ListCompanies** with a filter on your company name to determine the "Company" ID.
3. **Autotask › AddTicket** with title "Onboarding: first name last name", status, priority, due date (start date) and queue.
4. **Autotask › AddTicketChecklistItem** per task, e.g. "Create user account", "Prepare notebook", "Set up access".

[Offboarding](https://hub.equipme.io/dokumentation/organization/employees/onboarding-and-offboarding.md) works the same way, e.g. triggered by a scheduler and *Equipme › List Employees*, followed by a filter on employees with status "offboarding".

### Take over device information from Autotask

1. **Trigger:** scheduler (e.g. daily).
2. **Autotask › ListConfigurationItems** with a filter, e.g. on changed entries.
3. **Equipme › List Service Instances** to find the matching asset (e.g. via the serial number).
4. **Equipme › Set Service Instance Metadata:** store the Autotask ID of the device – visible in equipme under ["Additional information"](https://hub.equipme.io/dokumentation/organization/additional-information.md).

### Report ticket changes

1. **Trigger:** *Autotask › WatchTickets* with "Trigger fields" = status.
2. **Autotask › GetTicket** to read the title, company and new status.
3. **Email › Send Email** to the requester.

## Notes and limitations

* The triggers react to **changes** to the selected fields. Select at least one "Trigger field", otherwise Autotask reports nothing.
* When the flow is stopped, the notification in Autotask is removed again.
* Update actions only apply **filled-in** fields. A field cannot be cleared this way.
* New contacts, configuration items or ticket notes cannot be created with the connector.
* Autotask limits the number of requests per hour. The connector observes at most 10,000 requests per hour per connection and queues further requests.
* All actions work with the permissions of the API user.

## Troubleshooting

| Problem                  | Cause / solution                                                                                                     |
| ------------------------ | -------------------------------------------------------------------------------------------------------------------- |
| "Connect account" fails  | Check username, secret and API Tracking Identifier. The user must be an API user.                                    |
| Select field stays empty | The connection is missing or the API user may not read the area.                                                     |
| Trigger does not fire    | Is the flow started? Is at least one "Trigger field" selected? May the API user create webhooks?                     |
| Ticket is not created    | Check required fields ("Company", "Title", "Status", "Priority", "Due date time") and whether the company ID exists. |
| List very large or slow  | Set filters; without a filter all entries are loaded.                                                                |

The logs under **"Insights"** help with errors. For assistance, contact [Support](https://hub.equipme.io/dokumentation/help/support.md) and include the flow name, component and error message.

## Frequently asked questions

**Is the Autotask connector the same as the ticketing system in equipme?**

No. The ticketing system in equipme is [Equipme Operate](https://hub.equipme.io/dokumentation/operate.md). You need the Autotask connector if tickets are handled in Autotask, for example by your IT service provider.

**Where do I get the IDs for "Company" or "Contact"?**

From a previous list action (*ListCompanies*, *ListContacts*) or from the trigger. If needed, store them as metadata in equipme so later flows can use them directly.

**Can the connector list tickets?**

You read a single ticket with *GetTicket*. You react to changes with *WatchTickets*.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/automation/connectors/autotask.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
