# ManageEngine ServiceDesk Plus

> IT help desk. Raise, update and close requests, add notes, tasks and time logs, and find requests by status, priority or group.

App · 20 actions. Web page: https://docs.lodol.com/docs/integrations/manageengine-servicedesk-plus

## Actions

### Add note

Add a note to a request. It is private to technicians unless you show it to the requester.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Note (`description`, text, required): What to write.
- Show to requester (`show_to_requester`, true/false): Whether the requester can see the note. Off keeps it private to technicians.
- Notify technician (`notify_technician`, true/false): Whether to tell the request's technician about the note.

**Outputs**

- `note` (object): The new note

**Example output**

```json
{
  "note": {
    "created_by_email": "charles@example.com",
    "created_by_id": "1994035670863379",
    "created_by_name": "Charles",
    "created_time": "2026-10-20T10:00:00.000Z",
    "description": "<div>Called the requester; monitor ordered.</div>",
    "id": "1997129173325228",
    "notify_technician": false,
    "request_id": "2079997951635005",
    "show_to_requester": false
  }
}
```

### Add worklog

Log time spent on a request. The time spent is worked out from the start and end.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Technician (`owner`, text, required): Who did the work, by email address.
- Started (`start_time`, date and time, required): When the work started.
- Ended (`end_time`, date and time, required): When the work ended. Must be after it started.
- Description (`description`, text): What was done.

**Outputs**

- `worklog` (object): The new worklog

**Example output**

```json
{
  "worklog": {
    "created_time": "2026-10-21T10:31:00.000Z",
    "description": "Set up the monitor",
    "end_time": "2026-10-21T10:30:00.000Z",
    "hours_spent": 1,
    "id": "2000000040351",
    "minutes_spent": 30,
    "owner_email": "charles@example.com",
    "owner_id": "1537931074919595",
    "owner_name": "Charles",
    "start_time": "2026-10-21T09:00:00.000Z"
  }
}
```

### Close request

Close a request. Your portal may insist on a resolution or a closure code before it lets a request close.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Closure code (`closure_code`, text): Why it is closed, such as Success.
- Closure comments (`closure_comments`, text): A note on why the request is closed.
- Resolution (`resolution`, text): The resolution text, saved on the request.

**Outputs**

- `request` (object): The closed request

**Example output**

```json
{
  "request": {
    "category": "Hardware",
    "completed_time": null,
    "created_time": "2026-10-20T09:00:00.000Z",
    "description": "<div>Provide me an External Monitor</div>",
    "display_id": "39",
    "due_by_time": "2026-10-27T09:00:00.000Z",
    "group": "Hardware Problems",
    "has_notes": false,
    "id": "2079997951635005",
    "impact": "Affects Business",
    "is_overdue": false,
    "is_service_request": false,
    "item": null,
    "last_updated_time": "2026-10-20T09:00:00.000Z",
    "level": "Tier 1",
    "mode": "Web Form",
    "priority": "High",
    "request_type": "Service Request",
    "requester_email": "lincoln@example.com",
    "requester_id": "1650986973829395",
    "requester_name": "Lincoln",
    "resolution": null,
    "resolved_time": null,
    "site": null,
    "status": "Closed",
    "subcategory": null,
    "subject": "Need an External Monitor",
    "technician_email": "charles@example.com",
    "technician_id": "1537931074919595",
    "technician_name": "Charles",
    "urgency": "Urgent"
  }
}
```

### Create request

Raise a request (ticket). Only the subject is required; ServiceDesk Plus fills in the rest from its defaults.

**Inputs**

- Subject (`subject`, text, required): One line saying what the request is about.
- Description (`description`, text): The details of the request.
- Requester (`requester`, text): Who the request is for, by email address. Leave empty for the connected user.
- Status (`status`, text): The status, such as Open. Pick one or type its name.
- Priority (`priority`, text): The priority.
- Urgency (`urgency`, text): The urgency.
- Impact (`impact`, text): The impact.
- Type (`request_type`, text): The type, such as Incident or Service Request.
- Mode (`mode`, text): How the request was raised, such as E-Mail.
- Level (`level`, text): The support level, such as Tier 1.
- Category (`category`, text): The category.
- Subcategory (`subcategory`, text): The subcategory, typed as named in ServiceDesk Plus. It must belong to the category.
- Item (`item`, text): The item, typed as named in ServiceDesk Plus. It must belong to the subcategory.
- Group (`group`, text): The support group to assign it to.
- Technician (`technician`, text): The technician to assign it to, by email address.
- Due date (`due_by_time`, date and time): When the request is due.

**Outputs**

- `request` (object): The new request

**Example output**

```json
{
  "request": {
    "category": "Hardware",
    "completed_time": null,
    "created_time": "2026-10-20T09:00:00.000Z",
    "description": "<div>Provide me an External Monitor</div>",
    "display_id": "39",
    "due_by_time": "2026-10-27T09:00:00.000Z",
    "group": "Hardware Problems",
    "has_notes": false,
    "id": "2079997951635005",
    "impact": "Affects Business",
    "is_overdue": false,
    "is_service_request": false,
    "item": null,
    "last_updated_time": "2026-10-20T09:00:00.000Z",
    "level": "Tier 1",
    "mode": "Web Form",
    "priority": "High",
    "request_type": "Service Request",
    "requester_email": "lincoln@example.com",
    "requester_id": "1650986973829395",
    "requester_name": "Lincoln",
    "resolution": null,
    "resolved_time": null,
    "site": null,
    "status": "Open",
    "subcategory": null,
    "subject": "Need an External Monitor",
    "technician_email": "charles@example.com",
    "technician_id": "1537931074919595",
    "technician_name": "Charles",
    "urgency": "Urgent"
  }
}
```

### Create task

Add a task to a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Title (`title`, text, required): What the task is.
- Description (`description`, text): The details of the task.
- Owner (`owner`, text): Who does the task, by email address.
- Status (`status`, text): The task's status, such as Open.
- Priority (`priority`, text): The task's priority.
- Scheduled start (`scheduled_start_time`, date and time): When the task is scheduled to start.
- Scheduled end (`scheduled_end_time`, date and time): When the task is scheduled to end.

**Outputs**

- `task` (object): The new task

**Example output**

```json
{
  "task": {
    "created_time": "2026-10-20T10:30:00.000Z",
    "description": null,
    "id": "2174353095375675",
    "owner_email": "charles@example.com",
    "owner_id": "1537931074919595",
    "owner_name": "Charles",
    "percentage_completion": 0,
    "priority": "High",
    "request_id": "2079997951635005",
    "scheduled_end_time": "2026-10-22T09:00:00.000Z",
    "scheduled_start_time": "2026-10-21T09:00:00.000Z",
    "status": "Open",
    "title": "Order the monitor"
  }
}
```

### Delete note

Delete a note from a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Note ID (`note_id`, text, required): The note's id, from 'Add note' or 'List notes'.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `note_id` (text): The note deleted

**Example output**

```json
{
  "deleted": true,
  "note_id": "1997129173325228"
}
```

### Delete request

Delete a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `request_id` (text): The request deleted

**Example output**

```json
{
  "deleted": true,
  "request_id": "2079997951635005"
}
```

### Delete task

Delete a task from a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Task ID (`task_id`, text, required): The task's id, from 'Create task' or 'List tasks'.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `task_id` (text): The task deleted

**Example output**

```json
{
  "deleted": true,
  "task_id": "2174353095375675"
}
```

### Delete worklog

Delete a worklog from a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Worklog ID (`worklog_id`, text, required): The worklog's id, from 'Add worklog' or 'List worklogs'.

**Outputs**

- `deleted` (true/false): Always true once deleted
- `worklog_id` (text): The worklog deleted

**Example output**

```json
{
  "deleted": true,
  "worklog_id": "2000000040351"
}
```

### Get note

Get one note on a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Note ID (`note_id`, text, required): The note's id, from 'Add note' or 'List notes'.

**Outputs**

- `note` (object): The note

**Example output**

```json
{
  "note": {
    "created_by_email": "charles@example.com",
    "created_by_id": "1994035670863379",
    "created_by_name": "Charles",
    "created_time": "2026-10-20T10:00:00.000Z",
    "description": "<div>Called the requester; monitor ordered.</div>",
    "id": "1997129173325228",
    "notify_technician": false,
    "request_id": "2079997951635005",
    "show_to_requester": false
  }
}
```

### Get request

Get one request: its subject, status, people, dates and resolution.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.

**Outputs**

- `request` (object): The request

**Example output**

```json
{
  "request": {
    "category": "Hardware",
    "completed_time": null,
    "created_time": "2026-10-20T09:00:00.000Z",
    "description": "<div>Provide me an External Monitor</div>",
    "display_id": "39",
    "due_by_time": "2026-10-27T09:00:00.000Z",
    "group": "Hardware Problems",
    "has_notes": false,
    "id": "2079997951635005",
    "impact": "Affects Business",
    "is_overdue": false,
    "is_service_request": false,
    "item": null,
    "last_updated_time": "2026-10-20T09:00:00.000Z",
    "level": "Tier 1",
    "mode": "Web Form",
    "priority": "High",
    "request_type": "Service Request",
    "requester_email": "lincoln@example.com",
    "requester_id": "1650986973829395",
    "requester_name": "Lincoln",
    "resolution": null,
    "resolved_time": null,
    "site": null,
    "status": "Open",
    "subcategory": null,
    "subject": "Need an External Monitor",
    "technician_email": "charles@example.com",
    "technician_id": "1537931074919595",
    "technician_name": "Charles",
    "urgency": "Urgent"
  }
}
```

### Get task

Get one task on a request.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Task ID (`task_id`, text, required): The task's id, from 'Create task' or 'List tasks'.

**Outputs**

- `task` (object): The task

**Example output**

```json
{
  "task": {
    "created_time": "2026-10-20T10:30:00.000Z",
    "description": null,
    "id": "2174353095375675",
    "owner_email": "charles@example.com",
    "owner_id": "1537931074919595",
    "owner_name": "Charles",
    "percentage_completion": 0,
    "priority": "High",
    "request_id": "2079997951635005",
    "scheduled_end_time": "2026-10-22T09:00:00.000Z",
    "scheduled_start_time": "2026-10-21T09:00:00.000Z",
    "status": "Open",
    "title": "Order the monitor"
  }
}
```

### List closure codes

List the closure codes a request can be closed with.

**Inputs**: None.

**Outputs**

- `closure_codes` (list): The closure codes
- `count` (number): How many

**Example output**

```json
{
  "closure_codes": [
    {
      "id": "2000000008001",
      "name": "Success"
    }
  ],
  "count": 1
}
```

### List notes

List the notes on a request, oldest first. Returns one page.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Page size (`limit`, number): How many to return, 1 to 100. Defaults to 25. From 1 to 100.
- Start index (`start_index`, number): Where to start, to get a later page. Use 'next_start_index' from the page before. Defaults to 1. At least 1.

**Outputs**

- `count` (number): How many came back in this page
- `has_more` (true/false): Whether there are more after this page
- `next_start_index` (number): Give this as 'Start index' to get the next page
- `notes` (list): The notes

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_start_index": null,
  "notes": [
    {
      "created_by_email": "charles@example.com",
      "created_by_id": "1994035670863379",
      "created_by_name": "Charles",
      "created_time": "2026-10-20T10:00:00.000Z",
      "description": "<div>Called the requester; monitor ordered.</div>",
      "id": "1997129173325228",
      "notify_technician": false,
      "request_id": "2079997951635005",
      "show_to_requester": false
    }
  ]
}
```

### List requests

List requests, newest first, optionally only those whose subject contains some text or that have a given status, priority or group. Gets one page; to see more, run it again with the next page it gives.

**Inputs**

- Subject contains (`subject_contains`, text): Only requests whose subject contains this text.
- Status (`status`, text): Only requests with this status.
- Priority (`priority`, text): Only requests with this priority.
- Group (`group`, text): Only requests assigned to this group.
- Sort by (`sort_by`, text): What to order the requests by. One of: `created_time` (Date created (default)), `last_updated_time` (Date last updated), `due_by_time` (Due date), `subject`, `id`. Default: `created_time`.
- Order (`sort_order`, text): Which end to start from. One of: `desc` (Newest first (default)), `asc` (Oldest first). Default: `desc`.
- Page size (`limit`, number): How many to return, 1 to 100. Defaults to 25. From 1 to 100.
- Start index (`start_index`, number): Where to start, to get a later page. Use 'next_start_index' from the page before. Defaults to 1. At least 1.

**Outputs**

- `count` (number): How many came back in this page
- `has_more` (true/false): Whether there are more after this page
- `next_start_index` (number): Give this as 'Start index' to get the next page
- `requests` (list): The requests

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_start_index": null,
  "requests": [
    {
      "category": "Hardware",
      "completed_time": null,
      "created_time": "2026-10-20T09:00:00.000Z",
      "description": "<div>Provide me an External Monitor</div>",
      "display_id": "39",
      "due_by_time": "2026-10-27T09:00:00.000Z",
      "group": "Hardware Problems",
      "has_notes": false,
      "id": "2079997951635005",
      "impact": "Affects Business",
      "is_overdue": false,
      "is_service_request": false,
      "item": null,
      "last_updated_time": "2026-10-20T09:00:00.000Z",
      "level": "Tier 1",
      "mode": "Web Form",
      "priority": "High",
      "request_type": "Service Request",
      "requester_email": "lincoln@example.com",
      "requester_id": "1650986973829395",
      "requester_name": "Lincoln",
      "resolution": null,
      "resolved_time": null,
      "site": null,
      "status": "Open",
      "subcategory": null,
      "subject": "Need an External Monitor",
      "technician_email": "charles@example.com",
      "technician_id": "1537931074919595",
      "technician_name": "Charles",
      "urgency": "Urgent"
    }
  ]
}
```

### List tasks

List the tasks on a request, oldest first. Returns one page.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Page size (`limit`, number): How many to return, 1 to 100. Defaults to 25. From 1 to 100.
- Start index (`start_index`, number): Where to start, to get a later page. Use 'next_start_index' from the page before. Defaults to 1. At least 1.

**Outputs**

- `count` (number): How many came back in this page
- `has_more` (true/false): Whether there are more after this page
- `next_start_index` (number): Give this as 'Start index' to get the next page
- `tasks` (list): The tasks

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_start_index": null,
  "tasks": [
    {
      "created_time": "2026-10-20T10:30:00.000Z",
      "description": null,
      "id": "2174353095375675",
      "owner_email": "charles@example.com",
      "owner_id": "1537931074919595",
      "owner_name": "Charles",
      "percentage_completion": 0,
      "priority": "High",
      "request_id": "2079997951635005",
      "scheduled_end_time": "2026-10-22T09:00:00.000Z",
      "scheduled_start_time": "2026-10-21T09:00:00.000Z",
      "status": "Open",
      "title": "Order the monitor"
    }
  ]
}
```

### List worklogs

List the time logged on a request, oldest first. Returns one page.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Page size (`limit`, number): How many to return, 1 to 100. Defaults to 25. From 1 to 100.
- Start index (`start_index`, number): Where to start, to get a later page. Use 'next_start_index' from the page before. Defaults to 1. At least 1.

**Outputs**

- `count` (number): How many came back in this page
- `has_more` (true/false): Whether there are more after this page
- `next_start_index` (number): Give this as 'Start index' to get the next page
- `worklogs` (list): The worklogs

**Example output**

```json
{
  "count": 1,
  "has_more": false,
  "next_start_index": null,
  "worklogs": [
    {
      "created_time": "2026-10-21T10:31:00.000Z",
      "description": "Set up the monitor",
      "end_time": "2026-10-21T10:30:00.000Z",
      "hours_spent": 1,
      "id": "2000000040351",
      "minutes_spent": 30,
      "owner_email": "charles@example.com",
      "owner_id": "1537931074919595",
      "owner_name": "Charles",
      "start_time": "2026-10-21T09:00:00.000Z"
    }
  ]
}
```

### Update note

Change a note's text or who can see it. Only the fields you fill in change.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Note ID (`note_id`, text, required): The note's id, from 'Add note' or 'List notes'.
- Note (`description`, text): The new text. Leave empty to keep it.
- Show to requester (`show_to_requester`, true/false): Whether the requester can see the note. Off keeps it private to technicians.
- Notify technician (`notify_technician`, true/false): Whether to tell the request's technician about the note.

**Outputs**

- `note` (object): The note as saved

**Example output**

```json
{
  "note": {
    "created_by_email": "charles@example.com",
    "created_by_id": "1994035670863379",
    "created_by_name": "Charles",
    "created_time": "2026-10-20T10:00:00.000Z",
    "description": "<div>Called the requester; monitor ordered.</div>",
    "id": "1997129173325228",
    "notify_technician": false,
    "request_id": "2079997951635005",
    "show_to_requester": false
  }
}
```

### Update request

Change fields on a request. Only the fields you fill in change.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Subject (`subject`, text): A new subject. Leave empty to keep it.
- Description (`description`, text): The details of the request.
- Requester (`requester`, text): Who the request is for, by email address. Leave empty for the connected user.
- Status (`status`, text): The status, such as Open. Pick one or type its name.
- Priority (`priority`, text): The priority.
- Urgency (`urgency`, text): The urgency.
- Impact (`impact`, text): The impact.
- Type (`request_type`, text): The type, such as Incident or Service Request.
- Mode (`mode`, text): How the request was raised, such as E-Mail.
- Level (`level`, text): The support level, such as Tier 1.
- Category (`category`, text): The category.
- Subcategory (`subcategory`, text): The subcategory, typed as named in ServiceDesk Plus. It must belong to the category.
- Item (`item`, text): The item, typed as named in ServiceDesk Plus. It must belong to the subcategory.
- Group (`group`, text): The support group to assign it to.
- Technician (`technician`, text): The technician to assign it to, by email address.
- Due date (`due_by_time`, date and time): When the request is due.
- Resolution (`resolution`, text): The resolution text, saved on the request.

**Outputs**

- `request` (object): The request as saved

**Example output**

```json
{
  "request": {
    "category": "Hardware",
    "completed_time": null,
    "created_time": "2026-10-20T09:00:00.000Z",
    "description": "<div>Provide me an External Monitor</div>",
    "display_id": "39",
    "due_by_time": "2026-10-27T09:00:00.000Z",
    "group": "Hardware Problems",
    "has_notes": false,
    "id": "2079997951635005",
    "impact": "Affects Business",
    "is_overdue": false,
    "is_service_request": false,
    "item": null,
    "last_updated_time": "2026-10-20T09:00:00.000Z",
    "level": "Tier 1",
    "mode": "Web Form",
    "priority": "High",
    "request_type": "Service Request",
    "requester_email": "lincoln@example.com",
    "requester_id": "1650986973829395",
    "requester_name": "Lincoln",
    "resolution": null,
    "resolved_time": null,
    "site": null,
    "status": "Open",
    "subcategory": null,
    "subject": "Need an External Monitor",
    "technician_email": "charles@example.com",
    "technician_id": "1537931074919595",
    "technician_name": "Charles",
    "urgency": "Urgent"
  }
}
```

### Update task

Change a task. Only the fields you fill in change.

**Inputs**

- Request ID (`request_id`, text, required): The request's id: the long number from 'Create request' or 'List requests', or the request's address in ServiceDesk Plus. It is not the short request number shown on screen.
- Task ID (`task_id`, text, required): The task's id, from 'Create task' or 'List tasks'.
- Title (`title`, text): What the task is.
- Description (`description`, text): The details of the task.
- Owner (`owner`, text): Who does the task, by email address.
- Status (`status`, text): The task's status, such as Open.
- Priority (`priority`, text): The task's priority.
- Scheduled start (`scheduled_start_time`, date and time): When the task is scheduled to start.
- Scheduled end (`scheduled_end_time`, date and time): When the task is scheduled to end.
- Percentage complete (`percentage_completion`, number): How much of the task is done, 0 to 100. From 0 to 100.

**Outputs**

- `task` (object): The task as saved

**Example output**

```json
{
  "task": {
    "created_time": "2026-10-20T10:30:00.000Z",
    "description": null,
    "id": "2174353095375675",
    "owner_email": "charles@example.com",
    "owner_id": "1537931074919595",
    "owner_name": "Charles",
    "percentage_completion": 0,
    "priority": "High",
    "request_id": "2079997951635005",
    "scheduled_end_time": "2026-10-22T09:00:00.000Z",
    "scheduled_start_time": "2026-10-21T09:00:00.000Z",
    "status": "Open",
    "title": "Order the monitor"
  }
}
```
