ilert Documentation
WebsiteAPI ReferenceLoginStart for Free
  • Getting Started
    • Core concepts
    • FAQ
      • Renaming of Incidents to Alerts
    • Import from PagerDuty
    • Import from StatusPage.io
  • Alerting
    • Dashboard
    • Alert sources
    • Notification settings
      • Mute notifications
    • Support hours
    • Maintenance windows
    • Heartbeat monitoring
      • Prometheus Heartbeat Example
      • CLI Heartbeat Examples
    • Deployment events
    • 🏛️Understanding event flows
    • ilert sender IDs, domains and IPs
      • SMS and voice alerts in China
  • On-call management & Escalations
    • Escalation policies
    • On-call schedules
      • My on-call shifts
      • Recurring schedules
      • Static schedules
    • Coverage requests
  • ChatOps
    • Overview
    • Integration for Slack
      • Receive and respond to alerts in Slack
      • Create a dedicated Slack channel for an existing alert
      • Create alerts in Slack
      • Look up who is on-call
    • Microsoft Teams Integration
      • Microsoft Teams Chat Integration
        • Microsoft Teams Integration via Incoming Webhook
        • Microsoft Teams Integration via Workflows
      • Microsoft Teams Meeting Integration
      • Create a channel for an existing alert in Microsoft Teams
      • Create alerts in Microsoft Teams
      • Look up who is on-call in Microsoft Teams
  • Incident comms & status pages
    • Getting started
    • Services
    • Incidents
    • Status pages
      • Public vs private status pages
      • Audience-specific status page
    • Metrics
      • Import metrics from Datadog
      • Import metrics from Prometheus
  • 🪄ilert AI
    • Introduction
    • Using ilert AI for efficient incident communication
    • Using ilert AI for post-mortem creation
    • Using ilert AI for schedule generation
    • Using ilert AI for alert grouping
    • Global Search enhanced by ilert AI
      • Bulk resolving similar alerts
  • Call Routing
    • Getting started with call routing
    • Routing calls using call flows
    • Call routing (legacy)
      • Routing calls based on support hours
      • Voicemail only mode
      • Managing call routing alerts
      • Adding webhooks and outbound chat messages
      • Uploading custom audio responses
  • User Administration
    • User roles and permissions
    • Team-based organisation
    • Single sign on
      • Setting up SSO with GSuite
      • Setting up SSO with Microsoft Azure Active Directory
      • Setting up SSO with Okta
      • Setting up SSO with Auth0
      • Auto provisioning users & teams
    • 🔐Two-factor authentication / MFA
  • Reports
    • Overview
    • Alerts
  • Mobile App
    • Getting started with ilert mobile app
    • Mobile app notification settings
    • Critical push notifications and DND overrides
      • iOS critical alerts configuration
      • Android Push Notification DND Configuration
    • On-call widget
  • INTEGRATIONS
    • Types of integrations
    • Inbound integrations
      • 4me Integration
      • Ansible Automation Platform AWX Integration
      • Amazon CloudWatch Integration
      • Amazon SNS Integration
        • Amazon SNS Inbound Integration
        • Amazon SNS Outbound via AWS Lambda
      • Azure Alerts Integration
        • Azure Activity Logs
        • Azure Metric
        • Azure Logs
        • Azure Service Health
        • Azure Sentinel
        • Budget Alert
      • Apica Integration
      • AppDynamics Integration
      • AppSignal Integration
      • AWS Budgets Integration
      • AWS Cloudtrail Integration
      • AWS DevOps Guru Integration
      • AWS GuardDuty Integration
      • AWS Personal Health Dashboard Integration
      • AWS Security Hub Integration
      • Autotask Inbound Integration
      • Auvik Integration
      • Catchpoint Integration
      • Checkly Integration
      • Checkmk Integration
        • Checkmk Integration (v 1.x)
        • Checkmk Integration (v 2.0+ )
      • Cisco Meraki Integration
      • Cisco ThousandEyes Integration
      • Cisco Webex
      • Cloudflare Integration
      • ClusterControl Integration
      • Connectwise Manage Integration
      • Cortex Integration
      • Cortex XSOAR (formerly Demisto) Integration
      • CrowdStrike Integration
      • Dash0 Integration
      • Datadog Integration
      • Dynatrace Integration
      • Elastic Watcher Integration
      • Email Inbound Integration
        • Email Key Extraction and Resolve Examples
        • Automatically resolve Alerts with Emails
      • FreshService Integration
      • Gatus Integration
      • GitHub Integration
        • GitHub Advanced Security Integration
        • GitHub Inbound Check Run (Actions) Integration
        • GitHub Inbound Issue Integration
        • GitHub advanced settings
      • GitLab Integration
      • Google Cloud Monitoring (formerly Stackdriver) Integration
      • Google Security Command Center
      • Grafana Integration
        • Grafana Integration
        • Grafana Integration (v 9.x)
      • Graylog Integration
      • HaloITSM Integration
      • HaloPSA Integration
      • HashiCorp Consul
      • Healthchecks.io Integration
      • HetrixTools Integration
      • Honeybadger Integration
      • Honeycomb Integration
      • Hyperping Integration
      • CrowdStrike Falcon LogScale Integration
      • IBM Cloud Functions Integration
      • Icinga Integration
      • InfluxDB Integration
      • Instana Integration
      • IT-Conductor Integration
      • IXON Cloud Integration
      • Jira Inbound Integration
      • JumpCloud Integration
      • Kafka Integration
      • Kapacitor Integration
      • Kentix AlarmManager
      • Keep Integration
      • Kibana Integration
      • Kubernetes Integration
      • LibreNMS Integration
      • Lightstep Integration
      • Loki integration
      • Mezmo Integration
      • Microsoft SCOM
      • Mimir Integration
      • MongoDB Atlas Integration
      • MXToolBox Integration
      • MQTT Integration
      • Nagios Integration
      • N-central Integration
      • Netdata Integration
      • New Relic Integration
        • New Relic Integration (deprecated)
        • New Relic Workflow Integration
      • Oh Dear Integration
      • PandoraFMS Integration
      • Panther Integration
      • Particle Integration
      • Pingdom Integration
      • PostHog Integration
      • Postman Monitors Integration
      • Prometheus Integration
      • PRTG Network Monitor Integration
      • Prisma Cloud Integration
      • Push Notifications
      • RapidSpike Integration
      • Raygun Integration
      • Rollbar Integration
      • Salesforce Integration
      • Samsara Integration
      • Search Guard Integration
      • Sematext Integration
      • Sensu Integration
      • Sentry Integration
      • Server Density Integration
      • ServerGuard24 Integration
      • ServiceNow Inbound Integration
      • SignalFx Integration
      • Site24x7 Integration
      • SMS Integration
      • SolarWinds Integration
      • Splunk Integration
      • StatusCake Integration
      • StatusHub Integration
      • StatusPage Integration
      • Sumo Logic Integration
      • Sysdig Integration
      • TOPdesk Inbound Integration
      • TeamCity integration
      • Terraform Cloud / Terraform Enterprise
      • Tulip Integration
      • Twilio Alarms Integration
      • Twilio Errors Integration
      • Ubidots Integration
      • Uptime Kuma Integration
      • UptimeRobot Integration
      • VictoriaMetrics Integration
      • Zabbix Integration
        • Zabbix 4.4+ Integration
        • Zabbix 2.2 – 4.3 Integration
      • Zammad Inbound Integration
      • Zapier Inbound Integration
      • Zendesk Inbound Integration
    • Outbound integrations
      • Autotask Outbound Integration
      • DingTalk Integration
      • Discord Integration
      • Email Outbound Integration
      • Jira Outbound Integration
      • GitHub Outbound Issue Integration
      • Mattermost Integration
      • ServiceNow Outbound Integration
      • Telegram Integration
      • TOPdesk Outbound Integration
      • Webhook Integration
      • Zammad Outbound Integration
      • Zapier Outbound Integration
      • Zendesk Outbound Integration
      • Zoom Integration
        • Zoom Chat Integration
        • Zoom Meeting Integration
    • Deployment integrations
      • API deployment pipeline
      • Argo CD deployment pipeline
      • Github deployment pipeline
      • GitLab deployment pipeline
  • API
    • API Reference
    • API Version History
      • API user preference migration 2023
      • Discontinuation of Uptime Monitoring
    • Rate Limiting
    • Client Libraries
      • ilert Agent - ilagent
      • Go Client
      • Rust Client
      • Javascript / Node.js Client
    • Terraform
      • Importing ilert UI resources into Terraform state
    • 👩‍💻ICL - ilert condition language
    • ➿ITL - ilert template language
    • API endpoints / samples
      • Creating alerts through events
      • Importing public status page subscribers
    • 🔥Developing ilert Apps
      • Get started with ilert Apps
      • Understanding OAuth2
      • Developing a Backend App with OAuth2
      • Developing a web or native App with OAuth2 and PKCE
      • Token lifetimes, error codes, app verification, etc.
  • Contact us
  • ilert Release Notes
Powered by GitBook
LogoLogo

Product

  • Alerting & Notification
  • On-call Management & Escalations
  • Call Routing
  • Status Pages

Resources

  • Blog
  • Case Studies
  • Security
  • API Reference

Legal

  • Privacy policy
  • Imprint

Increase Your Uptime

  • Start for Free
  • Get a Demo

(c) 2011 - 2025 ilert GmbH

On this page
  • In Autotask: Create an API user
  • In ilert: Create an Autotask alert source
  • In Autotask: Create an Extension Callout
  • In Autotask: Create a Workflow Rule
  • Autotask Alert Lifecycle
  • Mapping Autotask ticket priority to ilert alert priority
  • Bidirectional alert synchronisation
  • Setting up multi workflows in Autotask
  • FAQ
  • Related articles

Was this helpful?

Edit on GitHub
  1. INTEGRATIONS
  2. Inbound integrations

Autotask Inbound Integration

The ilert Autotask integration helps you to easily connect ilert with Autotask.

PreviousAWS Security Hub IntegrationNextAuvik Integration

Last updated 1 year ago

Was this helpful?

Professional Services Automation (PSA) is a powerful and intuitive cloud-based PSA platform providing a singular view of the entire business — enabling MSPs to centralize business operations and make data-driven decisions to improve service, productivity, and profitability. With the ilert's Autotask integration, you can create alerts in ilert based on tickets from Autotask.

In Autotask: Create an API user

  1. Sign in to Autotask and then go to Admin -> Resources (Users)

  1. Click the New button and then navigate to New API User

  1. In the First Name section, enter a first name eg. ilert

  2. In the Last Name section, enter a last name eg. API

  3. In the Email section, enter an email

  4. Click the Generate key button to generate a username and then the Generate Secret button to generate a password. You will need Username and Secret below when setting up the alert source.

  5. In the Integration Vendor section, choose iLert - Alerts

Please make sure that the Integration Vendor is selected properly.

In ilert: Create an Autotask alert source

  1. Go to the "Alert sources" tab and click on "Create new alert source"

  1. In the Name section, enter a name eg. ilert

  2. In the Integration Type section, choose "Autotask"

  3. In the Autotask Settings -> Username section, paste the API user username generated above

  4. In the Autotask Settings -> Secret section, paste the API user secret generated above

  5. Select your desired escalation policy and click the Save button

  1. On the next page, a Webhook URL is generated. You will need this URL below when setting up the extension callout in Autotask.

In Autotask: Create an Extension Callout

  1. Go to Autotask and then to Admin -> Extensions & Integrations

  1. Click the Other Extensions & Tools panel and then click on the Extension Callout (Tickets) link

  1. Click on New Extension Callout

  1. In the Name section, enter a name eg. ilert

  2. In the URL section, paste the Webhook URL that you generated in ilert

  3. Ensure that Active is selected and click the Save & Close button

In Autotask: Create a Workflow Rule

  1. Go to Autotask and then to Admin -> Workflow Rules

  1. Click the New button

  1. In the General -> Workflow Rule Name section, enter a name eg. ilert

  2. Ensure that Active is selected

  3. In the Events -> CREATED/EDITED section, activate the Created by and the Edited by fields and choose Anyone

  1. Scroll down to the Actions panel and in the Then Execute Extension Callout section choose the iLert Callout that you created above

  2. Click on the Save & Close button

Autotask Alert Lifecycle

When Autotask creates a ticket with status ...

... then an ilert alert ...

New or In Progress

is created

Complete or

Denied or

Waiting Customer or

Waiting Materials or

Scheduled or

Escalate or

Waiting Vendor or

Waiting Approval or

Waiting Dispatch or

Approved

will not be created and a

400 (bad request) error occurs

any other status

is created

When Autotask updates a ticket with status ...

... and the ilert alert ...

... then the/an ilert alert ...

New or In Progress

does not exist

is created

Complete or

Denied or

Waiting Customer or

Waiting Materials or

Scheduled or

Escalate or

Waiting Vendor or

Waiting Approval or

Waiting Dispatch or

Approved

does not exist

will not be created and a

400 (bad request) error occurs

any other

does not exist

is created

New

exists

doesn't change

Complete or

Denied

exists

change status to Resolved if not already resolved

Waiting Customer or

In Progress or

Waiting Materials or

Scheduled or

Escalate or

Waiting Vendor or

Waiting Approval or

Waiting Dispatch or

Approved

exists

change status to Accepted if not already accepted

any other status

exists

doesn't change

Mapping Autotask ticket priority to ilert alert priority

Autotask ticket priority
ilert alert priority

1 - Low

Low

2 - High 3 - Medium 4 - Critical

High

Bidirectional alert synchronisation

When providing credentials you may choose to activate bidirectional mode on the Autotask ticket source. This will cause your alert source to be automatically linked with an outbound connector and alert action. This way status changes to ilert alerts will synchronize to Autotask ticket.

When saving the Autotask alert source with bidirectional setting enabled, it will automatically create an outbound connector for you and take you to the creation page of the necessary alert action, please make sure to continue with the setup of the action to finish your bidirectional alert source setup.

Setting up multi workflows in Autotask

To use Autotask workflows combined with holiday calendars to manage on-call availability, you will need to set up following 2 workflows:

  1. Go to Autotask and then to Admin -> Workflow Rules

  2. In the General -> Workflow Rule Name section, enter a name eg. ilert (business hours)

  3. Ensure that Active is selected

  4. In the Events -> CREATED/EDITED section, activate the Created by and the Edited by fields and choose Anyone

  1. In the Conditions section, select Status Equal to New.

  1. Scroll down to the Actions panel and in the Then Execute Extension Callout section choose the iLert Callout that you created above

  2. Click on the Save & New button

  1. Enter a name eg. ilert (no business hours)

  2. Ensure that Active is selected

  3. In the Events -> CREATED/EDITED section, activate the Created by and the Edited by fields and choose Anyone

  1. In the Conditions section, select Status Not equal to New.

  2. Tick the Time Sensitive checkbox and select Outside Business Hours of.

  1. Scroll down to the Actions panel and in the Then Execute Extension Callout section choose the iLert Callout that you created above

  2. Click on the Save & New button

FAQ

Will alerts in ilert be resolved automatically?

Yes, as soon as an Autotask Ticket is completed, the alert in ilert will be resolved automatically.

Can I connect Autotask with multiple alert sources from ilert?

Yes, simply create more Extension Callouts in Autotask.

Can I customize the alert messages?

No.

Related articles

Autotask Outbound Integration
Datto's Autotask