# GLPI

> Run your GLPI IT help desk from workflows: open tickets from forms, emails and alerts, add follow-ups and solutions, assign, prioritise and change status, find tickets and users, and look up computers and who they're assigned to. Start a workflow when a ticket is opened, changes or is solved.

App · 9 actions. Web page: https://docs.lodol.com/docs/integrations/glpi

## Actions

### Add follow-up

Add a follow-up to a ticket: one the requester can see, or a private one only technicians see.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, or its link.
- Message (`message`, text, required): What to write, as plain text or HTML.
- Private (`private`, true/false): Only technicians can see a private follow-up. Default: `false`.

**Outputs**

- `author` (text): Who wrote it: the person whose API token connected GLPI
- `content` (text): What it says, as plain text
- `created_at` (text): When it was added, in GLPI's time zone
- `id` (number): The follow-up's ID
- `link` (text): A link to the ticket in GLPI
- `private` (true/false): True when only technicians can see it
- `ticket_id` (number): The ticket's ID

**Example output**

```json
{
  "author": "Tess Tech",
  "content": "I've ordered a new pickup roller.",
  "created_at": "2026-11-05 10:02:13",
  "id": 88,
  "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
  "private": false,
  "ticket_id": 412
}
```

### Add solution

Add a solution to a ticket, which marks it solved.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, or its link.
- Solution (`message`, text, required): How it was solved, as plain text or HTML.

**Outputs**

- `content` (text): The solution, as plain text
- `id` (number): The solution's ID
- `link` (text): A link to the ticket in GLPI
- `solved_at` (text): When it was solved, in GLPI's time zone
- `status` (text): The ticket's status now: Solved, or Closed if GLPI closes solved tickets at once
- `ticket_id` (number): The ticket's ID

**Example output**

```json
{
  "content": "Replaced the pickup roller.",
  "id": 31,
  "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
  "solved_at": "2026-11-05 11:30:00",
  "status": "Solved",
  "ticket_id": 412
}
```

### Create ticket

Open a ticket for someone, by their email address or login, with its category, urgency and location, and assign it to a technician or group.

**Inputs**

- Title (`title`, text, required): What the ticket is about, such as Printer on the 2nd floor jams.
- Description (`description`, text, required): The ticket's description, as plain text or HTML.
- Type (`ticket_type`, text): An incident is something broken; a request is something asked for. One of: `incident`, `request`. Default: `incident`.
- Requester (`requester`, text): Who's asking: their email address or GLPI login. An email address that isn't a GLPI user is recorded as it is. Leave blank for you.
- Category (`category`, text): The ticket's category, such as Hardware > Printers.
- Urgency (`urgency`, text): How urgent it is. Leave blank for GLPI's default, Medium. One of: `very_low` (Very low), `low`, `medium`, `high`, `very_high` (Very high).
- Location (`location`, text): Where the problem is.
- Technician (`technician`, text): The technician to assign it to, or their login or email address.
- Group (`group`, text): The group to assign it to, such as IT Support.

**Outputs**

- `category` (text): Its category, with the categories above it, such as Hardware > Printers
- `closed_at` (text): When it was closed; empty if it isn't
- `description` (text): Its description, as plain text
- `group` (text): The groups it's assigned to
- `id` (number): The ticket's ID, for other GLPI steps
- `link` (text): A link to it in GLPI
- `location` (text): Its location
- `opened_at` (text): When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
- `priority` (text): Its priority, such as Medium or Major
- `requester` (text): Who asked: the requesters' names, or an email address
- `requester_email` (text): The requesters' email addresses
- `solved_at` (text): When it was solved; empty if it isn't
- `status` (text): Its status, such as New, Processing (assigned) or Solved
- `technician` (text): The technicians it's assigned to; empty if nobody
- `technician_email` (text): The technicians' email addresses
- `title` (text): Its title
- `type` (text): Incident or Request
- `updated_at` (text): When it last changed, in GLPI's time zone
- `urgency` (text): Its urgency, such as Medium or High

**Example output**

```json
{
  "category": "Hardware > Printers",
  "closed_at": "",
  "description": "The printer by the clerk's office jams on every job.",
  "group": "IT Support",
  "id": 412,
  "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
  "location": "City Hall",
  "opened_at": "2026-11-05 09:12:44",
  "priority": "High",
  "requester": "Jane Doe",
  "requester_email": "jane.doe@yourcity.gov",
  "solved_at": "",
  "status": "Processing (assigned)",
  "technician": "Tess Tech",
  "technician_email": "tess.tech@yourcity.gov",
  "title": "Printer on the 2nd floor jams",
  "type": "Incident",
  "updated_at": "2026-11-05 10:02:13",
  "urgency": "High"
}
```

### Find assets

Find computers or other assets by name, serial or inventory number, or the person they're assigned to.

**Inputs**

- Asset type (`asset_type`, text): What kind of asset. Defaults to a computer. One of: `Computer`, `Monitor`, `Printer`, `NetworkEquipment` (Network device), `Phone`, `Peripheral` (Device). Default: `Computer`.
- Name (`name`, text): Part of the asset's name, such as LAPTOP-0042.
- Serial or inventory number (`serial`, text): Part of its serial number, or of its inventory number (asset tag).
- Assigned to (`user`, text): Only assets assigned to this person: their email address or login.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `assets` (list): The assets found, by name

**Example output**

```json
{
  "assets": [
    {
      "asset_type": "Computer",
      "comment": "",
      "group": "IT Support",
      "id": 1,
      "inventory_number": "INV-0042",
      "kind": "Laptop",
      "link": "https://glpi.yourcity.gov/front/computer.form.php?id=1",
      "location": "City Hall",
      "manufacturer": "HP",
      "model": "EliteBook 840",
      "name": "LAPTOP-0042",
      "serial": "5CG1234XYZ",
      "status": "In use",
      "technician": "Tess Tech",
      "updated_at": "2026-11-01 08:00:00",
      "user": "Jane Doe",
      "user_email": "jane.doe@yourcity.gov",
      "user_login": "jdoe"
    }
  ]
}
```

### Find users

Find GLPI users by name, login or email address, with their location and groups.

**Inputs**

- Search for (`query`, text): A name, login or email address. Leave blank to list active users.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `total` (number): How many users match in all
- `users` (list): The users found, by last name

**Example output**

```json
{
  "total": 1,
  "users": [
    {
      "active": true,
      "email": "jane.doe@yourcity.gov",
      "firstname": "Jane",
      "groups": [
        "Records Office"
      ],
      "id": 5,
      "lastname": "Doe",
      "link": "https://glpi.yourcity.gov/front/user.form.php?id=5",
      "location": "City Hall",
      "login": "jdoe",
      "name": "Jane Doe",
      "phone": "555-0142"
    }
  ]
}
```

### Get asset

Get a computer's or other asset's details, with who it's assigned to.

**Inputs**

- Asset type (`asset_type`, text): What kind of asset. Defaults to a computer. One of: `Computer`, `Monitor`, `Printer`, `NetworkEquipment` (Network device), `Phone`, `Peripheral` (Device). Default: `Computer`.
- Asset (`asset`, text, required): The asset's ID, from an earlier step, or its link.

**Outputs**

- `asset_type` (text): What it is: Computer, Monitor, Printer, Network device, Phone or Device
- `comment` (text): Comments on it
- `group` (text): The groups it's assigned to
- `id` (number): The asset's ID
- `inventory_number` (text): Its inventory number (asset tag)
- `kind` (text): Its type in GLPI, such as Laptop
- `link` (text): A link to it in GLPI
- `location` (text): Where it is
- `manufacturer` (text): Its manufacturer
- `model` (text): Its model
- `name` (text): Its name
- `serial` (text): Its serial number
- `status` (text): Its status, such as In use
- `technician` (text): The technician in charge of it
- `updated_at` (text): When it last changed, in GLPI's time zone
- `user` (text): The person it's assigned to
- `user_email` (text): That person's email address
- `user_login` (text): That person's GLPI login

**Example output**

```json
{
  "asset_type": "Computer",
  "comment": "",
  "group": "IT Support",
  "id": 1,
  "inventory_number": "INV-0042",
  "kind": "Laptop",
  "link": "https://glpi.yourcity.gov/front/computer.form.php?id=1",
  "location": "City Hall",
  "manufacturer": "HP",
  "model": "EliteBook 840",
  "name": "LAPTOP-0042",
  "serial": "5CG1234XYZ",
  "status": "In use",
  "technician": "Tess Tech",
  "updated_at": "2026-11-01 08:00:00",
  "user": "Jane Doe",
  "user_email": "jane.doe@yourcity.gov",
  "user_login": "jdoe"
}
```

### Get ticket

Get a ticket's details, and its follow-ups and solution if you ask.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, or its link.
- Include follow-ups and solution (`include_followups`, true/false): Also get every follow-up, oldest first, and the latest solution. Default: `false`.

**Outputs**

- `category` (text): Its category, with the categories above it, such as Hardware > Printers
- `closed_at` (text): When it was closed; empty if it isn't
- `description` (text): Its description, as plain text
- `followups` (list): Its follow-ups, oldest first, when asked for
- `group` (text): The groups it's assigned to
- `id` (number): The ticket's ID, for other GLPI steps
- `link` (text): A link to it in GLPI
- `location` (text): Its location
- `opened_at` (text): When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
- `priority` (text): Its priority, such as Medium or Major
- `requester` (text): Who asked: the requesters' names, or an email address
- `requester_email` (text): The requesters' email addresses
- `solution` (text): Its latest solution, when asked for; empty if it has none
- `solved_at` (text): When it was solved; empty if it isn't
- `status` (text): Its status, such as New, Processing (assigned) or Solved
- `technician` (text): The technicians it's assigned to; empty if nobody
- `technician_email` (text): The technicians' email addresses
- `title` (text): Its title
- `type` (text): Incident or Request
- `updated_at` (text): When it last changed, in GLPI's time zone
- `urgency` (text): Its urgency, such as Medium or High

**Example output**

```json
{
  "category": "Hardware > Printers",
  "closed_at": "",
  "description": "The printer by the clerk's office jams on every job.",
  "followups": [
    {
      "author": "Tess Tech",
      "content": "I've ordered a new pickup roller.",
      "created_at": "2026-11-05 10:02:13",
      "id": 88,
      "private": false
    }
  ],
  "group": "IT Support",
  "id": 412,
  "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
  "location": "City Hall",
  "opened_at": "2026-11-05 09:12:44",
  "priority": "High",
  "requester": "Jane Doe",
  "requester_email": "jane.doe@yourcity.gov",
  "solution": "",
  "solved_at": "",
  "status": "Processing (assigned)",
  "technician": "Tess Tech",
  "technician_email": "tess.tech@yourcity.gov",
  "title": "Printer on the 2nd floor jams",
  "type": "Incident",
  "updated_at": "2026-11-05 10:02:13",
  "urgency": "High"
}
```

### Search tickets

Find tickets by words, status, type, category, group, technician, requester or when they were opened, newest first.

**Inputs**

- Words (`query`, text): Words in the title or description, or a ticket's ID. Leave blank to match every ticket.
- Status (`status`, text): Only tickets with this status. Not solved yet means any status before Solved. One of: `open` (Not solved yet), `new`, `assigned` (Processing (assigned)), `planned` (Processing (planned)), `pending`, `solved`, `closed`.
- Type (`ticket_type`, text): Only incidents, or only requests. One of: `incident`, `request`.
- Category (`category`, text): Only tickets in this category or the ones under it.
- Group (`group`, text): Only tickets assigned to this group.
- Technician (`technician`, text): Only tickets assigned to this technician, or their login or email address.
- Requester (`requester`, text): Only tickets from this person: their email address or login.
- Opened on or after (`opened_after`, date): Only tickets opened on or after this day.
- Opened before (`opened_before`, date): Only tickets opened before this day.
- How many (`limit`, number): The most to list. Defaults to 25. From 1 to 100.

**Outputs**

- `tickets` (list): The tickets found, newest first
- `total` (number): How many tickets match in all

**Example output**

```json
{
  "tickets": [
    {
      "category": "Hardware > Printers",
      "closed_at": "",
      "description": "The printer by the clerk's office jams on every job.",
      "group": "IT Support",
      "id": 412,
      "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
      "location": "City Hall",
      "opened_at": "2026-11-05 09:12:44",
      "priority": "High",
      "requester": "Jane Doe",
      "requester_email": "jane.doe@yourcity.gov",
      "solved_at": "",
      "status": "Processing (assigned)",
      "technician": "Tess Tech",
      "technician_email": "tess.tech@yourcity.gov",
      "title": "Printer on the 2nd floor jams",
      "type": "Incident",
      "updated_at": "2026-11-05 10:02:13",
      "urgency": "High"
    }
  ],
  "total": 1
}
```

### Update ticket

Change a ticket's title, status, urgency, priority, type, category or location, or assign it to another technician or group. Blank fields stay as they are.

**Inputs**

- Ticket (`ticket`, text, required): The ticket's ID, from a trigger or an earlier step, or its link.
- Title (`title`, text): A new title. Leave blank to keep it.
- Status (`status`, text): A new status. Leave blank to keep it. One of: `new`, `assigned` (Processing (assigned)), `planned` (Processing (planned)), `pending`, `solved`, `closed`.
- Urgency (`urgency`, text): A new urgency. Leave blank to keep it. One of: `very_low` (Very low), `low`, `medium`, `high`, `very_high` (Very high).
- Priority (`priority`, text): A new priority. Your GLPI profile needs the right to change it. Leave blank to keep it. One of: `very_low` (Very low), `low`, `medium`, `high`, `very_high` (Very high), `major`.
- Type (`ticket_type`, text): Incident or Request. Leave blank to keep it. One of: `incident`, `request`.
- Category (`category`, text): A new category. Leave blank to keep it.
- Location (`location`, text): A new location. Leave blank to keep it.
- Technician (`technician`, text): The technician to assign it to instead of whoever has it, or their login or email address. Leave blank to keep it.
- Group (`group`, text): The group to assign it to instead of the one it's in. Leave blank to keep it.

**Outputs**

- `category` (text): Its category, with the categories above it, such as Hardware > Printers
- `closed_at` (text): When it was closed; empty if it isn't
- `description` (text): Its description, as plain text
- `group` (text): The groups it's assigned to
- `id` (number): The ticket's ID, for other GLPI steps
- `link` (text): A link to it in GLPI
- `location` (text): Its location
- `opened_at` (text): When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
- `priority` (text): Its priority, such as Medium or Major
- `requester` (text): Who asked: the requesters' names, or an email address
- `requester_email` (text): The requesters' email addresses
- `solved_at` (text): When it was solved; empty if it isn't
- `status` (text): Its status, such as New, Processing (assigned) or Solved
- `technician` (text): The technicians it's assigned to; empty if nobody
- `technician_email` (text): The technicians' email addresses
- `title` (text): Its title
- `type` (text): Incident or Request
- `updated_at` (text): When it last changed, in GLPI's time zone
- `urgency` (text): Its urgency, such as Medium or High

**Example output**

```json
{
  "category": "Hardware > Printers",
  "closed_at": "",
  "description": "The printer by the clerk's office jams on every job.",
  "group": "IT Support",
  "id": 412,
  "link": "https://glpi.yourcity.gov/front/ticket.form.php?id=412",
  "location": "City Hall",
  "opened_at": "2026-11-05 09:12:44",
  "priority": "High",
  "requester": "Jane Doe",
  "requester_email": "jane.doe@yourcity.gov",
  "solved_at": "",
  "status": "Processing (assigned)",
  "technician": "Tess Tech",
  "technician_email": "tess.tech@yourcity.gov",
  "title": "Printer on the 2nd floor jams",
  "type": "Incident",
  "updated_at": "2026-11-05 10:02:13",
  "urgency": "High"
}
```
