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
        • Migrating legacy email settings
      • 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 Overview
        • 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 ilert: Create a TOPdesk alert source
  • In TOPdesk
  • Create action sequences
  • Create events
  • FAQ
  • Related articles

Was this helpful?

Edit on GitHub
  1. INTEGRATIONS
  2. Inbound integrations

TOPdesk Inbound Integration

The ilert TOPdesk Integration helps you to easily connect to TOPdesk.

PreviousSysdig IntegrationNextTeamCity integration

Last updated 1 year ago

Was this helpful?

is a modular service management software that helps businesses manage IT support, facilities management, HR, and other services. It provides a centralized platform for ticketing, asset management, and workflow automation.

Through ilert's integration with TOPdesk, incidents in ilert can be automatically generated from TOPdesk tickets while also enhancing TOPdesk with reliable alerting (via phone calls, SMS, push notifications, and more) on-call scheduling and automatic escalations.

With the ilert TOPdesk integration, you can create alerts in ilert based on TOPdesk event such as tickets or calls.

In ilert: Create a TOPdesk alert source

  1. Go to Alert sources --> Alert sources and click on Create new alert source

  2. Search for TOPdesk in the search field, click on the TOPdesk tile and click on Next.

  3. Give your alert source a name, optionally assign teams and click Next.

  4. Select an escalation policy by creating a new one or assigning an existing one.

  5. Select you preference and click Continue setup. You may click Do not group alerts for now and change it later.

  6. The next page show additional settings such as customer alert templates or notification prioritiy. Click on Finish setup for now.

  7. On the final page, an API key and / or webhook URL will be generated that you will need later in this guide.

In TOPdesk

In this guide we will use First Line Ticket service for the integration. You can use any other service to sync with ilert.

Create action sequences

  1. Go to TOPdesk and then to Modules

  1. Click on Action Management and then on Action sequence to add an action sequence

  1. On the modal window, choose a service you are interested in e.g. Ticket Management - First Line Ticket and click on Create new action sequence

  1. In the Name section, enter a name eg. iLert Create Alert Action

  2. In the Available section, ensure that the Active, Apply in the Self-Service Portal and Apply in the Operator's Section checkboxes are checked

  3. In the Step 1 section Name field, enter a name e.g. ilert_create_incident

  4. In the Step 1 section HTTP Method field, choose POST

  5. In the Step 1 section URL field, paste the Webhook URL that you generated in ilert

  6. In the Step 1 section Headers field, add Content-Type: application/json and Accept: application/json

  7. In the Step 1 section Body field, copy and paste the following JSON payload

{
"eventType": "ALERT",
"incidentKey": "${naam}",
"summary": "${korteomschrijving}"
}
  1. Optional: Add more entries to the request body to show custom information in an ilert alert. You can find more TOPdesk variables in the DataDict

For example: to add ticket caller to ilert alert details just add persoonid variable on the top-level of json body

{
"eventType": "ALERT",
"incidentKey": "${naam}",
"summary": "${korteomschrijving}",
"persoonid": "${persoonid}"
}
  1. Click on Save

  2. Go to Modules again

  3. Click on Action Management and then on Action sequence to add an action sequence

  1. On the modal window, choose a service you are interested in e.g. Ticket Management - First Line Ticket and click on Create new action sequence

  1. In the Name section, enter a name eg. iLert Create Alert Action

  2. In the Available section, ensure that the Active, Apply in the Self-Service Portal and Apply in the Operator's Section checkboxes are checked

  3. In the Step 1 section Name field, enter a name eg. ilert_resolve_incident

  4. In the Step 1 section HTTP Method field, choose POST

  5. In the Step 1 section URL field, paste the Webhook URL that you generated in ilert

  6. In the Step 1 section Headers field, add Content-Type: application/json and Accept: application/json

  7. In the Step 1 section Body field, copy and paste the following JSON payload

{
"eventType": "RESOLVE",
"incidentKey": "${naam}",
"summary": "${korteomschrijving}"
}
  1. Click on Save

Create events

  1. Go to Modules

  2. Click on Action Management and then on Event to add a new event

  1. On the modal window, choose a service you are interested in e.g. Ticket Management - First Line Ticket and click on Create new event

  1. In the Details section Name field, enter a name eg. iLert - Create Alert Event

  2. In the Details section Active field, ensure that checkbox is checked

  3. In the Details section Choose type field, choose New card

  4. In the Linked actions section, choose the action sequence iLert - Create Alert Action that you created in the last step

  5. Optional: You can choose another card type (e.g. Edit card) and add conditions or specifications for your use case (e.g. Status changed to "Open"). In this case an ilert alert will be created only if event conditions and specifications match.

  1. Click on Save

  2. Go to Modules again

  3. Click on Action Management and then on Event to add a new event

  1. On the modal window, choose a service you are interested in e.g. Ticket Management - First Line Ticket and click on Create new event

  1. In the Details section Name field, enter a name eg. iLert - Resolve Alert Event

  2. In the Details section Active field, ensure that checkbox is checked

  3. In the Details section Choose type field, choose Edit card

  4. In the Linked actions section, choose the action sequence iLert - Resolve alert that you created in the last step

  5. Optional: You can add conditions or specifications for your use case (e.g. ticket was closed). In this case an ilert alert will be resolved only if event conditions and specifications match.

  1. Click on Save

FAQ

Will alerts in ilert be resolved automatically?

Yes

Can I connect TOPdesk with multiple alert sources from ilert?

Yes, simply create more action sequences in TOPdesk.

Can I customize the alert messages?

Yes, any custom field will be shown in the alert details.

Related articles

TOPdesk Outbound Integration
TOPdesk
Alert grouping

TOPdesk Outbound Integration

Create tickets in TOPdesk based on alerts from ilert