This KB is specific to Escalation Triggers where Autotask will send a webhook message to Rocketship. If you are looking to send webhook messages from Rocketship to a 3rd party application, e.g., MS Teams, refer to the Outbound Webhooks KBs.
The Autotask Ticket Callout is one of the ways that Autotask can notify a 3rd party app that a ticket has been created/updated. It greatly reduces how often we have to “poll” Autotask for data, reducing our consumption of your Autotask API hourly cap and speeding up data updates across-the-board.
Before you begin, you need to get the personalized webhook URL we provide for your tenant. (Note, for inbound webhooks, i.e., webhooks coming from a 3rd party like Autotask into Rocketship, we call those “triggers” to differentiate between outbound webhooks.)
To access your trigger URL:
The “Ticket Callout” is what Autotask uses to “call out” to a 3rd party. In this situation, that’s us!
The Autotask Ticket Callout is a configuration, but it doesn’t actually execute on its own. Rather, it is executed by the Autotask Workflow Rule (WFR) system. For our needs, we need two very simple Autotask WFRs that fire when a ticket is created and one that fires when a Ticket Status is changed, respectively.
We recommend not placing any other conditions in the WFR. Rocketship will properly handle whether a change to a ticket should trigger an escalation — you do not need to encode this in your WFRs directly.
In the two following sections, we create the two needed Autotask WFRs:
Follow these steps:
Follow these steps: