This document shows an example of what needs to be done in Autotask to make it integration-ready with ONEiO. The document also describes what ONEiO needs to be able to send messages to the Autotask instance.
Currently the integration supports two processes: Ticket & Attachments.
For any questions related to setting up the integration, please send mail to firstname.lastname@example.org.
You can sign up for a free trial of ONEiO from the following link: ONEiO Free Trial
Sending messages from ONEiO to Autotask
ONEiO accesses Autotask by using the Integration Center
Creating an integration user in Autotask
Add an API user to Autotask.
Admin -> Resources (User)
New -> New API user
Fill in the needed user details
- First Name (Integration Specific)
- Last Name (Integration Specific)
- Email Address (Integration Specific)
- Security Level - API User (system)
- Primary Internal Location (Integration Specific)
Generate a Key and Secret pair. These are used in the Username and Password fields in the ONEiO UI.
Adjust the. ONEiO is an official Integration Vendor for Autotask and can be found under "ONEiO - middleware" in the dropdown list.
Depending on your integration you might adjust the Line of Business. We are not doing it in this example.
Press "Save & Close"
Next we need to get the Resource ID of the integration user. This is used in the endpoint to prevent echos in messaging.
Go to Admin -> Resources (User) and search for you integration user under "Resource Name". This brings up the integration user and shows its Resource ID.
With this information we can now create our endpoint in ONEiO.
In the ONEiO endpoint UI we have to set following information.
- Autotask Base URL
- Integration User (Key)
- Password (Secret)
- Integration User Resource ID
Sending messages from Autotask to ONEiO
Autotask is a poller based system and we poll information from Autotask by its base URL and a preset query. To start receiving tickets from Autotask please activate the poller and if needed adjust the query, in the "Entity types" tab of the endpoint UI.