I was recently asked for help determining to determine the correct ContractServiceID when creating a new Ticket using the Autotask API.
This video explains Autotask concepts related to recurring services contracts, services, and how they are associated. It then demonstrates the steps to use MSPinetgrations to query for the Contract and the Service to then locate the correct ContractService.
Timestamps:
- How to create a ticket in AutoTask [00:26]
- How to associate a contract service to the ticket [00:49]
- How to add New Service within a contract in Autotask [1:41]
- How to identify the association of a Service to a Contract using the ID in the URL. [4:15]
- How to Create Steps and Rules in MSPintegrations
- How to create rule for ticket creation in the API [5:16]
- How to create rule to query for the account associated with the ticket [5:49]
- How to create rule to associate the ticket with the account [6:39]
- How to create a rule for Query for Contracts. [7:31]
- How to edit Contract Category in Autotask [7:38]
- How to associate the Contact ID to the ticket created [8:44]
- How to associate Contact Service ID to the ticket created [9:25]
- How to create a rule for Query for Service[9:43]
- Pro tip: Ways on how to query for the service required for the ticket, either by searching for the name or using a hardcoded ID. [10:09]
- How to create rule to Query Autotask for the ContractService [10:32]
- How to create rule to Create Ticket with Account ID, Contract ID and Contract Service ID [12:08]