> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/autotask.md).

# Autotask Outbound Integration

Create tickets in Autotask PSA based on alerts from ilert.

## In Autotask: Create an API user <a href="#create-api-user" id="create-api-user"></a>

1\. Sign in to Autotask and then go to **Admin -> Resources (Users)**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MBYQvoYwpZeeKCJVGEa%2F-MBYR67US6Ko7Cujld-8%2Fautotask1.png?alt=media\&token=7080884d-398e-4989-82bf-ea7eede0ebd8)

2\. Click the **New** button and then navigate to **New API User**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MBYQXWv4Jb9sKeU1LBQ%2F-MBYQsN8924XyZDN0Wx0%2Fautotask2.png?alt=media\&token=97ef50ad-e337-47e0-963c-12e30618ce3c)

3\. In the **First Name** section, enter a first name eg. ilert

4\. In the **Last Name** section, enter a last name eg. API

5\. In the **Email** section, enter an email

6\. Click the **Generate key** button to generate a username and then the **Generate Secret** button to generate a password. You will need **Username** and **Secret** below when setting up the connector.

7\. In the **Integration Vendor** section, choose ilert or your custom internal integration

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MNeZ3K95Zv0rNo_m_n8%2F-MNeZ9o7z7fXzl2d0Svt%2Fautotask3.png?alt=media\&token=e42d3105-1efd-4207-914c-3512ef7a94d5)

## In ilert: Create an Autotask Connector and Link to alert source

1\. Click on the gear icon and then on **Connectors** button

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MNeZ3K95Zv0rNo_m_n8%2F-MNecsxf5KFdg793d-OM%2FiLert.png?alt=media\&token=baedb829-8e5a-4a12-88ab-60ef2c20997e)

2\. Click on **Add Connector**

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MNeZ3K95Zv0rNo_m_n8%2F-MNedQ8-Emz1PC3v7KGp%2FiLert.png?alt=media\&token=7287012b-2dd7-4f4a-ae85-c8ca5d0dc61b)

3\. Select **Autotask** as **type** and fill in all fields. Enter a name and the username/password pair that you created in the last step.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-MNeZ3K95Zv0rNo_m_n8%2F-MNedrDXxDv-hph4ghjv%2FiLert.png?alt=media\&token=7f74db96-5f45-452b-bde7-701bb2f054af)

4\. Go to the alert sources tab and open the alert source whose alerts you want to publish in Autotask. Click on **Alert actions** and then on **Create alert action**.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-9887e1978c30c61025f427813bcf148b4a9d8282%2Fnew_incident_action%20\(3\).png?alt=media)

5\. Select **Autotask** as the **type**, select the connector created in step 3, fill in all fields. In the **Label** field, specify the alert action name.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-Ma3ijw5XTTXWtB7xnch%2F-Ma3jzezdvB0iGNipN-T%2FiLert.png?alt=media\&token=b9fe40cd-bfc1-4efe-a326-2e9abff84316)

6\. Finished! You can now test the alert action by clicking on the button **Test this connection**. Then a test ticket will be created in Autotask.

![](https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M76ygPnS4HUcFSX8ulm%2F-Ma3ijw5XTTXWtB7xnch%2F-Ma3kVG4KnSv8s_qXd58%2FiLert.png?alt=media\&token=45ed956a-705e-4d6f-a8ca-937c7afcfcf0)

## FAQ <a href="#faq" id="faq"></a>

**Are updates to an alert published in Autotask?**

Yes.

**Can Autotask alert sources use Autotask connections?**

No, please create a different alert source or create a bi-directional Autotask alert source.

**My API user gets blocked**

Please ensure that you have correctly chosen "iLert " as Integration Vendor in Autotask when setting up your API user.

## **Related articles**

{% content-ref url="/pages/-MBYQ55qc4A6gcwDttKv" %}
[Autotask Inbound Integration](/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/autotask.md)
{% endcontent-ref %}


---

# 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://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/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.
