Automatically Close Ticket using the API Extension Callout - Original Integration

Autotask includes the option to setup an Extension Callout to automatically close the ticket on the Dashboard when the ticket is marked as complete in Autotask.

You must refresh the South-pane Outages tab of the Dashboard to display the updated ticket state.

To utilize this feature we have created an Autotask Extension Callout API service call, which uses your Dashboard API Key to validate the closure request.

Note, changing the ticket's status does not affect the Check's failure state. This only changes the next time the Check passes.

Dashboard API Key

The API key{apikey} is created in your N-sight RMM Dashboard:

The API Key is used to authenticate against the Public API. If you generate a new key, anything that uses the existing key to authenticate against the Public API will stop working.

  1. Log in to the N-sight RMM Dashboard as a Superuser or (non-Classic) Administrator level access, or using a login with the required General permissions enabled, or using the Agent Key (if Dashboard access is enabled)
  2. Go to Settings > General Settings > API
  3. Click Generate (or Regenerate when you are creating a new API Key)

    You can generate the API Key as often as required. Each regeneration overwrites the existing key.

  4. Enter the recipient email address in the Email API Token to (optional) field and click Email Token (Optional)

    The sent email includes the API Key and the respective server URL to query.

  5. Select OK to apply

Setup Extension Callout

After you create the API key, login to your Autotask instance, hover over the Autotask button in the top left corner then navigate to:

  1. Admin
  2. Extensions & Integrations
  3. Expand Other Extensions & Tools
  4. Extension Callout (Tickets)
  5. New Extension Callout
  6. In the Extension Callout dialog:
    1. Specify a Name to identify the extension in Autotask
    2. Ensure the Active checkbox is selected
    3. Enter the Callback URL in the following format
    4. (Please refer to Callback URL Notes at the bottom of this section for information on the SERVER and {apikey} substitution strings.)
    5. https://SERVER/api/?service=autotask_ticket_update&apikey={apikey}
    6. Choose POST as the HTTP Transport Method
    7. Select Name Value Pair from the Data Format drop-down
  7. Save & Close

The Username, Password, Ticket User-Defined Fields, Method Name and SOAPAction fields are not required for this callout.

autotask_callback

Create a Workflow Rule

Workforce Rules are used to trigger an action when a specific event is met and are used in conjunction with the Extension Callout to issue the command to close the ticket on the Dashboard when the ticket is marked as complete in Autotask.

  1. Admin
  2. Features & Settings
  3. Expand Application-wide (Shared) Features
  4. Workflow Rules
  5. Navigate to Service Desk
  6. New
  7. In the New Workflow Rule dialog:
  8. Specify a Name to identify the rule in Autotask
  9. Ensure the Active checkbox is selected
  10. Events: for When a/an Ticket is select Created by, Edited by,  Added by and Time Added by
  11. Actions: select the Extension Callout created above from the Then Execute Extension Callout list
  12. Save & Close
  13. Conditions, Updates and Actions: Create To-Do(s) are not required for this workflow.

Please note, when Autotask moved control of Extension Callouts to Workflow Rules the automatically created basic Workflow Rules to ensure continuity of existing functionality.

autotask_rules

Further information on setting up these Autotask modules is available from Set Up Automatic Ticket Closure with Extension Callouts in Autotask’s help system.

Callback URL Notes

Replace {apikey} with your Dashboard API key.

The database server to query is dependent on the territory your account is registered under. The current territories and respective URLs are:

Territory URL
Americas https://www.am.remote.management/
Asia https://wwwasia.system-monitor.com/
Australia https://www.system-monitor.com/
Europe https://wwweurope1.systemmonitor.eu.com/
France (FR) https://wwwfrance.systemmonitor.eu.com/
France1 https://wwwfrance1.systemmonitor.eu.com/
Germany https://wwwgermany1.systemmonitor.eu.com/
Ireland https://wwwireland.systemmonitor.eu.com/
Poland https://wwwpoland1.systemmonitor.eu.com/
United Kingdom https://www.systemmonitor.co.uk/
United States https://www.systemmonitor.us/

Based on the above, a user in the United Kingdom uses the URL https://www.systemmonitor.co.uk/ and their query would be:

https://www.systemmonitor.co.uk/api/?apikey=1234567890abcdefg&service=list_servers&siteid=123

Determine API Server URL from Dashboard URL

If you are unsure of your Dashboard account territory:

  • Look at the URL used to access your Dashboard as this may include a region reference, or
  • If the URL does not mention a region, for example a custom domain, append /dashboard to one of above URLs and attempt login to your Dashboard at the prompt. Based on the United Kingdom this would look like: https://www.systemmonitor.co.uk/dashboard
  • Where problems are still experienced determining the region from a custom Dashboard URL. Open a command prompt or terminal on the device. Then perform an nslookup on the custom Dashboard URL:
nslookup dashboard.custom.domain
...
Non-authoritative answer:
Name: dashboard.systemmonitor.co.uk
...

When requesting the API Key is sent from the Dashboard, the respective server URL is included in the email.