This guide describes how to integrate your Zabbix installation with TOPdesk using the Zabbix webhook feature. This guide will provide instructions on setting up a media type, a user and an action in Zabbix.
1. Please create an application password according to the original instruction https://developers.topdesk.com/tutorial.html#show-collapse-usage-createAppPassword.
2. Copy the application password of your new integration to use it in Zabbix.
The configuration consists of a media type in Zabbix, which will invoke the webhook to send alerts to TOPdesk through the TOPdesk Rest API.
3. Change in the imported media the values of the variables topdesk_api (URL), topdesk_password, topdesk_user. The topdesk_status is the default status for creating a new TOPdesk ticket.
For more information about the Zabbix Webhook configuration, please see the documentation.
To utilize the media type, we recommend creating a dedicated Zabbix user to represent TOPdesk. The default settings for TOPdesk User should suffice as this user will not be logging into Zabbix. Please note, that in order to be notified about problems on a host, this user must have at least read permissions for the host.
When configuring alert action, add this user in the Send to users field (in Operation details) - this will tell Zabbix to use TOPdesk webhook when sending notifications from this action. Use the TOPdesk User in any action of your choice. Text from "Action Operations" will be sent to "TOPdesk First Line Call Request" field when the problem happens. Text from "Action Recovery Operations" and "Action Update Operations" will be sent to "TOPdesk First Line Call Action" field when the problem is resolved or updated.
To receive notifications about internal problem events in TOPdesk: in the internal action configuration mark the Custom message checkbox and specify custom message templates for problem operations. Internal event recovery actions are not supported. If an internal action operation is configured without a custom message, the notification will not be sent. Note, that this step is required only for notifications about internal events; for other event types specifying a custom message is optional.
Zabbix 6.2, TOPdesk RestApi 3.1.4.