Connect Claude & ChatGPT to TOPdesk

25 tools for TOPdesk

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• create_incidentChanges dataCreate an incident. In `body` set caller (email or id), briefDescription, request, and optionally category, subcategory, callType, priority, operator/operatorGroup and an initial action.
• create_operational_activityChanges dataCreate an operational activity with a brief description, planned start/end dates, type, category, operator or operator group.
• create_personChanges dataCreate a person. In `body` set surName, and optionally firstName, email, phoneNumber, jobTitle, branch (by id) and department.
• get_current_operatorGet the operator account the connection is logged in as.
• get_incidentGet one incident by its ID (`contact_id` is the incident UUID), with caller, request, status, operator and dates.
• get_incident_by_numberGet one incident by its incident number (e.g. "I 2409 123").
• get_operational_activityGet one operational activity by `task_identifier` (ID or number).
• get_personGet one person by ID (`contact_id` is the person UUID).
• list_call_typesList incident call types (e.g. question, complaint, disruption).
• list_categoriesList incident categories.
• list_incident_actionsList the actions (progress trail entries) of an incident by `id_id` (incident UUID).
• list_incident_requestsList the request texts of an incident by `id_id` (incident UUID).
• list_operator_groupsList operator groups, optionally filtered with a FIQL `query`.
• list_operatorsList operators, optionally filtered with a FIQL `query`, to find an operator ID for assigning incidents.
• list_prioritiesList incident priorities.
• list_processing_statusesList incident processing statuses.
• list_subcategoriesList incident subcategories and the category each belongs to.
• log_incident_timeChanges dataRegister time spent on an incident (`id_id` is the incident UUID): `time_spent` in minutes, with optional notes, operator and reason.
• search_branchesSearch branches (sites), optionally with a FIQL `query`; needed for creating persons and incidents.
• search_incidentsSearch incidents with a FIQL `query` (e.g. status==firstLine;caller.dynamicName=="Jane*"), with `sort`, `page_start` and `limit`. Use this to find incident IDs.
• search_operational_activitiesSearch operational activities (planned tasks) with a FIQL `query`, sort and paging.
• search_personsSearch persons (callers) with a FIQL `query` such as email=="[email protected]", with sort and paging.
• update_incidentChanges dataUpdate an incident by ID (`contact_id` is the incident UUID). In `body` set fields such as status, operator, priority, category, closed/completed, or add an `action` text to the progress trail.
• update_operational_activityChanges dataUpdate an operational activity by `task_identifier`: status, dates, operator, resolved/skipped and other fields.
• update_personChanges dataUpdate a person by ID (`contact_id`). In `body` pass only the fields to change.

Questions