> 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/pro/automation/connectors/autotask.md).

# Autotask connector

The Autotask connector for providers: sync customers as companies, tickets and configuration items per customer, ticket charges and contracts between Equipme Pro and your PSA.

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

With the **Autotask connector**, you connect Equipme Pro in [workflows](https://hub.equipme.io/pro/automation/workflows.md) with your **Autotask** PSA. Your customers from Pro become companies in Autotask, orders and deliveries become tickets with charges, and changes to configuration items in Autotask flow back to the service instances in Pro.

## What for?

* **Manage customers as companies:** Create new customers from Pro as a company in Autotask and store the Autotask ID in Pro.
* **PSA tickets for orders:** Create a ticket with a checklist for the right customer for every new fulfillment position.
* **Bill material and services:** Record delivered devices as a charge ("ticket charge") on the ticket so they are included in billing via Autotask.
* **Configuration items per customer:** Match devices from Autotask with the service instances in the customer tenants.
* **Check contracts and services:** Read a customer's contracts and services in Autotask, e.g. to assign tickets to the right contract.

## Prerequisites

* The activated [Automation module](https://hub.equipme.io/pro/automation.md)
* An **API user** in your Autotask instance with username, secret and **API Tracking Identifier**
* Sufficient permissions of the API user for companies, contacts, tickets, configuration items, contracts and products
* For the triggers: the API user must be allowed to create webhooks in Autotask
* For the Pro side of the flows: a connection of the [equipme connector](https://hub.equipme.io/pro/automation/connectors/equipme-pro.md) with an API key from Pro

## 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 (customer) is changed |
| WatchContacts    | a contact is changed            |
| WatchAssets      | a configuration item is changed |

All triggers have the same settings:

* **"Trigger fields"** – the fields whose change fires the flow (e.g. status 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 Pro 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"; "Company number", address, "Company category", "Parent company", "Currency", "Invoice template", "Tax region", "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", "Contact", "Configuration item", "Contract", "Contract service", "Billing code", "Assigned resource", "Purchase order number", "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 on a ticket      | Required: "Ticket ID", "Name", "Charge type", "Cost type", "Date purchased", "Unit quantity"; "Product ID", "Unit cost", "Unit price", "Billing code ID", "Contract service ID", "Is billable to company", "Purchase order number"                                                            |

### Configuration items, contracts, products and services

| Component                                 | Purpose                                    | Key options                                                                                                                     |
| ----------------------------------------- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| ListConfigurationItems                    | List configuration items, e.g. per company | "Filters"                                                                                                                       |
| ListContracts                             | List contracts                             | "Filters"                                                                                                                       |
| GetService / ListServices / UpdateService | Read and change services                   | "Service" (ID); name, prices, "SKU", "Invoice description", "Is active", "User defined fields"                                  |
| GetProduct / ListProducts / UpdateProduct | Read and change products                   | "Product" (ID); name, manufacturer, "SKU", "Vendor product number", 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

### Create new customers from Pro as companies

1. **Trigger:** *Equipme Pro › New Customer*.
2. **Autotask › ListCompanies** with filter "Company name" "equal to" customer name; only continue if no match is found.
3. **Autotask › AddCompany** with company name, "Company type" (customer), account manager, phone and address.
4. **Equipme Pro › Update Customer Metadata:** store the Autotask ID on the customer.

### PSA ticket for every fulfillment position

1. **Trigger:** *Equipme Pro › New Fulfillment Order*, filtered on the desired transaction types (e.g. "Order", "Return").
2. **Equipme Pro › Get Customer Metadata:** read the customer's Autotask ID.
3. **Autotask › AddTicket** with "Company" (Autotask ID), title from service and order number, queue, status, priority and due date.
4. **Autotask › AddTicketChecklistItem** for the work steps, e.g. "Prepare device", "Shipping", "Confirm handover".
5. After completion: **Autotask › AddTicketCharge** with product, quantity and price so the device is billed via Autotask.

### Assign configuration items to service instances

1. **Trigger:** *Autotask › WatchAssets* with "Trigger fields" e.g. on serial number or status.
2. **Equipme Pro › List Service Instances** with the customer to find the matching service instance (see [Service instances](https://hub.equipme.io/pro/operations/service-instances.md)).
3. **Equipme Pro › Set Service Instance Metadata Entry:** store the Autotask ID and serial number on the service instance.

## 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 for the entire instance. The connector observes at most 10,000 requests per hour per connection and queues further requests. Spread large syncs across all customers over time.
* You maintain the mapping customer in Pro ↔ company in Autotask yourself, ideally as metadata on the customer.

## 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 ends up with the wrong company | Check the Autotask ID on the customer in Pro (metadata).                                                       |
| Charge is rejected                    | Check required fields, especially "Charge type", "Cost type" and "Date purchased", as well as the "Ticket ID". |
| Sync aborts or becomes slow           | Autotask's request limit has been reached. Set filters and spread flows over time.                             |

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

## Frequently asked questions

**Do I need a separate Autotask connection per customer?**

No. One connection to your Autotask instance is enough; you select the customer in each action via the company ID.

**Does Autotask replace the tickets in Equipme Pro?**

No, both can run side by side. The [tickets](https://hub.equipme.io/pro/operations/tickets.md) in Pro remain unchanged; the connector only transfers what you define in the flow.

**Can I list tickets from Autotask?**

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/pro/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.
