
Autotask Integration In this document Overview Configurations in Autotask Creating an API-Only Resource And Generating Keys Configurations in DefensX Creating The Integration Company Mapping Ticket Integration Billing Integration Synchronization Generating Ticket Extension Callout and Workflow Finding Extension Call URL Creating a Ticket Extension Callout Creating a Workflow Rule Overview If you’re using Autotask, you can integrate DefensX to: Receive service tickets in real time. Sync subscription usage for each product into your billing agreements. The integration process involves creating an API-only resource, generating API keys in Autotask, and configuring the DefensX backend. Configurations in Autotask Creating an API-Only Resource And Generating Keys To set up the API-Only Resource: Navigate to Admin → Account Settings & Users → Resources/Users (HR) → Resources/Users Click the arrow in the next of New button, and select the New API User Under General tab: Enter a First Name and Last Name like "DefensX Resource" Give an e-mail address And set the Security Level as API User (System) Set Primary Internal Location as the location where the team is responsible for the DefensX Tickets. Under Credentials tab, click Generate Key and Generate Secret. Copy the both credentials in the boxes. Under API Tracking Identifier tab, select Integration Vendor as DefensX. Click Save & Close at the top of the page. Configurations in DefensX Creating The Integration Switch into DefensX Backend, and navigate to Integrations in the partners console. Then click to ADD button at the line of Autotask. Paste the Credentials you copied from Creating an API-Only Resource And Generating Keys. Click Test Connection button below. You should see “Connection successful” message. Then, you should be able to click the button Create Integration. Company Mapping Autotask Companies (or accounts) are your customers in DefensX. You need to map the companies to your DefensX customers. Click the box at the line of customer. At the triggered drop-down menu, you can see your Autotask Companies. The customers with most similar name will be displayed with green background. When you finish the mapping, click Save Client Mapping to proceed. Ticket Integration Click the toggle button at the line of Ticket Integration. Fill the form to set the default settings Default Queue: This queue will be assigned to the tickets created by DefensX. Initial Status: This will be the initial status of the tickets created by DefensX. Closing Status: This will be the final status of your tickets. When ticket reached the closing status, the associated user request will also be closed at DefensX. Also, when a user request is closed at DefensX, this will be the status of the associated ticket at Autotask. Do not forget to scroll down to see more statuses. Click Save Ticket Configuration. Billing Integration Click the toggle button next to Billing Integration. Set the Default Billing Code. This will be assigned to the services which will be created by DefensX Integration. Select the recurring contract for the customer that is already mapped. If your contract does not appear, please check the following: What is the contract type? Only contracts with the type "Recurring Services" will be displayed here. Is the contract assigned to the mapped company? Make sure to verify the "Account Name" of the contract in Autotask to ensure it matches the mapped company. Click on the Save Recurring Contract Mapping button. Synchronization Your integration has been set, and it will be periodically synchronized. However, you might want to trigger the first synchronization manually to speeding integration up and be able to create Extension Callout. The synchronization will take a while. Also, do not forget to copy the Extension Callout URL. Generating Ticket Extension Callout and Workflow After creating your integration, you need to create an Extension Callout for the informing DefensX Backend when tickets are closed. Finding Extension Call URL After finalizing the Autotask Extension, you will be able to see the Callout URL. Click the `Copy` button at the left bottom of the box to copy the Callout URL to your system clipboard. This will be needed for creating Ticket Extension Callout. Creating a Ticket Extension Callout Navigate to Admin → Extension & Integrations → Other Extensions & Tools → Extension Callout (Tickets). Click New Set a name like you want. Copy the Extension Callout URL from the Status page. Set Ticket User-Defined Field as “Is DefensX Ticket?”. If you can not see this option, please make a synchronization at DefensX first. Set HTTP Transport Method as POST. Click Save & Close at the top of the page. Creating a Workflow Rule Navigate to Admin → Automation → Workflow Rules → Workflow Rules. Click New on the page. In General Section, give a name like "Close DefensX User Requests". In Events section, click the checkbox of Edited by and set it to Anyone. In Conditions section, set first Attribute as Status, set operator as Equal To and set value as the Closing Status you have chosen in DefensX. In Actions section, set Then Execute Extension Callout as the created extension callout. Click Save & Close to create the workflow.

Autotask Integration

In this document

Overview
Configurations in Autotask
- Creating an API-Only Resource And Generating Keys
Configurations in DefensX
Generating Ticket Extension Callout and Workflow

Overview

If you’re using Autotask, you can integrate DefensX to:

Receive service tickets in real time.
Sync subscription usage for each product into your billing agreements.

The integration process involves creating an API-only resource, generating API keys in Autotask, and configuring the DefensX backend.

Configurations in Autotask

Creating an API-Only Resource And Generating Keys

To set up the API-Only Resource:

Navigate to Admin → Account Settings & Users → Resources/Users (HR) → Resources/Users
Click the arrow in the next of New button, and select the New API User
Under General tab:
- Enter a First Name and Last Name like "DefensX Resource"
- Give an e-mail address
- And set the Security Level as API User (System)
- Set Primary Internal Location as the location where the team is responsible for the DefensX Tickets.
Under Credentials tab, click Generate Key and Generate Secret. Copy the both credentials in the boxes.
Under API Tracking Identifier tab, select Integration Vendor as DefensX.

Click Save & Close at the top of the page.

Configurations in DefensX

Creating The Integration

Switch into DefensX Backend, and navigate to Integrations in the partners console. Then click to ADD button at the line of Autotask.
Paste the Credentials you copied from Creating an API-Only Resource And Generating Keys.

Click Test Connection button below. You should see “Connection successful” message.
Then, you should be able to click the button Create Integration.

Company Mapping

Autotask Companies (or accounts) are your customers in DefensX. You need to map the companies to your DefensX customers.

Click the box at the line of customer. At the triggered drop-down menu, you can see your Autotask Companies. The customers with most similar name will be displayed with green background.
When you finish the mapping, click Save Client Mapping to proceed.

Ticket Integration

Click the toggle button at the line of Ticket Integration.

Fill the form to set the default settings
- Default Queue: This queue will be assigned to the tickets created by DefensX.
- Initial Status: This will be the initial status of the tickets created by DefensX.
- Closing Status: This will be the final status of your tickets. When ticket reached the closing status, the associated user request will also be closed at DefensX. Also, when a user request is closed at DefensX, this will be the status of the associated ticket at Autotask. Do not forget to scroll down to see more statuses.
Click Save Ticket Configuration.

Billing Integration

Click the toggle button next to Billing Integration.

Set the Default Billing Code. This will be assigned to the services which will be created by DefensX Integration.
Select the recurring contract for the customer that is already mapped. If your contract does not appear, please check the following:
- What is the contract type? Only contracts with the type "Recurring Services" will be displayed here.
- Is the contract assigned to the mapped company? Make sure to verify the "Account Name" of the contract in Autotask to ensure it matches the mapped company.

Click on the Save Recurring Contract Mapping button.

Synchronization

Your integration has been set, and it will be periodically synchronized. However, you might want to trigger the first synchronization manually to speeding integration up and be able to create Extension Callout. The synchronization will take a while. Also, do not forget to copy the Extension Callout URL.

Generating Ticket Extension Callout and Workflow

After creating your integration, you need to create an Extension Callout for the informing DefensX Backend when tickets are closed.

Finding Extension Call URL

After finalizing the Autotask Extension, you will be able to see the Callout URL. Click the Copy button at the left bottom of the box to copy the Callout URL to your system clipboard. This will be needed for creating Ticket Extension Callout.

Creating a Ticket Extension Callout

Navigate to Admin → Extension & Integrations → Other Extensions & Tools → Extension Callout (Tickets).
Click New
Set a name like you want.
Copy the Extension Callout URL from the Status page.
Set Ticket User-Defined Field as “Is DefensX Ticket?”. If you can not see this option, please make a synchronization at DefensX first.
Set HTTP Transport Method as POST.
Click Save & Close at the top of the page.

Creating a Workflow Rule

Navigate to Admin → Automation → Workflow Rules → Workflow Rules.
Click New on the page.
In General Section, give a name like "Close DefensX User Requests".
In Events section, click the checkbox of Edited by and set it to Anyone.

In Conditions section, set first Attribute as Status, set operator as Equal To and set value as the Closing Status you have chosen in DefensX.

In Actions section, set Then Execute Extension Callout as the created extension callout.

Click Save & Close to create the workflow.