GLPI
App · 9 actions
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.
Actions
| Action | What it does |
|---|---|
| Add follow-up | Add a follow-up to a ticket: one the requester can see, or a private one only technicians see. |
| Add solution | Add a solution to a ticket, which marks it solved. |
| 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. |
| Find assets | Find computers or other assets by name, serial or inventory number, or the person they're assigned to. |
| Find users | Find GLPI users by name, login or email address, with their location and groups. |
| Get asset | Get a computer's or other asset's details, with who it's assigned to. |
| Get ticket | Get a ticket's details, and its follow-ups and solution if you ask. |
| Search tickets | Find tickets by words, status, type, category, group, technician, requester or when they were opened, newest first. |
| Update ticket | Change a ticket's title, status, urgency, priority, type, category or location, or assign it to another technician or group. |
Add follow-up
Add a follow-up to a ticket: one the requester can see, or a private one only technicians see.
Inputs
- Ticket
tickettextRequired - The ticket's ID, from a trigger or an earlier step, or its link.
- Message
messagetextRequired - What to write, as plain text or HTML.
- Private
privatetrue/false - Only technicians can see a private follow-up.Default:
false.
Outputs
authortext- Who wrote it: the person whose API token connected GLPI
contenttext- What it says, as plain text
created_attext- When it was added, in GLPI's time zone
idnumber- The follow-up's ID
linktext- A link to the ticket in GLPI
privatetrue/false- True when only technicians can see it
ticket_idnumber- The ticket's ID
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, or its link.
- Solution
messagetextRequired - How it was solved, as plain text or HTML.
Outputs
contenttext- The solution, as plain text
idnumber- The solution's ID
linktext- A link to the ticket in GLPI
solved_attext- When it was solved, in GLPI's time zone
statustext- The ticket's status now: Solved, or Closed if GLPI closes solved tickets at once
ticket_idnumber- The ticket's ID
Example output
{
"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
titletextRequired - What the ticket is about, such as Printer on the 2nd floor jams.
- Description
descriptiontextRequired - The ticket's description, as plain text or HTML.
- Type
ticket_typetext - An incident is something broken; a request is something asked for.One of:
incident,request. Default:incident. - Requester
requestertext - 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
categorytext - The ticket's category, such as Hardware > Printers.
- Urgency
urgencytext - 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
locationtext - Where the problem is.
- Technician
techniciantext - The technician to assign it to, or their login or email address.
- Group
grouptext - The group to assign it to, such as IT Support.
Outputs
categorytext- Its category, with the categories above it, such as Hardware > Printers
closed_attext- When it was closed; empty if it isn't
descriptiontext- Its description, as plain text
grouptext- The groups it's assigned to
idnumber- The ticket's ID, for other GLPI steps
linktext- A link to it in GLPI
locationtext- Its location
opened_attext- When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
prioritytext- Its priority, such as Medium or Major
requestertext- Who asked: the requesters' names, or an email address
requester_emailtext- The requesters' email addresses
solved_attext- When it was solved; empty if it isn't
statustext- Its status, such as New, Processing (assigned) or Solved
techniciantext- The technicians it's assigned to; empty if nobody
technician_emailtext- The technicians' email addresses
titletext- Its title
typetext- Incident or Request
updated_attext- When it last changed, in GLPI's time zone
urgencytext- Its urgency, such as Medium or High
Example output
{
"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_typetext - What kind of asset. Defaults to a computer.One of:
Computer,Monitor,Printer,NetworkEquipment(Network device),Phone,Peripheral(Device). Default:Computer. - Name
nametext - Part of the asset's name, such as LAPTOP-0042.
- Serial or inventory number
serialtext - Part of its serial number, or of its inventory number (asset tag).
- Assigned to
usertext - Only assets assigned to this person: their email address or login.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
assetslist- The assets found, by name
Example output
{
"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
querytext - A name, login or email address. Leave blank to list active users.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
totalnumber- How many users match in all
userslist- The users found, by last name
Example output
{
"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_typetext - What kind of asset. Defaults to a computer.One of:
Computer,Monitor,Printer,NetworkEquipment(Network device),Phone,Peripheral(Device). Default:Computer. - Asset
assettextRequired - The asset's ID, from an earlier step, or its link.
Outputs
asset_typetext- What it is: Computer, Monitor, Printer, Network device, Phone or Device
commenttext- Comments on it
grouptext- The groups it's assigned to
idnumber- The asset's ID
inventory_numbertext- Its inventory number (asset tag)
kindtext- Its type in GLPI, such as Laptop
linktext- A link to it in GLPI
locationtext- Where it is
manufacturertext- Its manufacturer
modeltext- Its model
nametext- Its name
serialtext- Its serial number
statustext- Its status, such as In use
techniciantext- The technician in charge of it
updated_attext- When it last changed, in GLPI's time zone
usertext- The person it's assigned to
user_emailtext- That person's email address
user_logintext- That person's GLPI login
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, or its link.
- Include follow-ups and solution
include_followupstrue/false - Also get every follow-up, oldest first, and the latest solution.Default:
false.
Outputs
categorytext- Its category, with the categories above it, such as Hardware > Printers
closed_attext- When it was closed; empty if it isn't
descriptiontext- Its description, as plain text
followupslist- Its follow-ups, oldest first, when asked for
grouptext- The groups it's assigned to
idnumber- The ticket's ID, for other GLPI steps
linktext- A link to it in GLPI
locationtext- Its location
opened_attext- When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
prioritytext- Its priority, such as Medium or Major
requestertext- Who asked: the requesters' names, or an email address
requester_emailtext- The requesters' email addresses
solutiontext- Its latest solution, when asked for; empty if it has none
solved_attext- When it was solved; empty if it isn't
statustext- Its status, such as New, Processing (assigned) or Solved
techniciantext- The technicians it's assigned to; empty if nobody
technician_emailtext- The technicians' email addresses
titletext- Its title
typetext- Incident or Request
updated_attext- When it last changed, in GLPI's time zone
urgencytext- Its urgency, such as Medium or High
Example output
{
"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
querytext - Words in the title or description, or a ticket's ID. Leave blank to match every ticket.
- Status
statustext - 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_typetext - Only incidents, or only requests.One of:
incident,request. - Category
categorytext - Only tickets in this category or the ones under it.
- Group
grouptext - Only tickets assigned to this group.
- Technician
techniciantext - Only tickets assigned to this technician, or their login or email address.
- Requester
requestertext - Only tickets from this person: their email address or login.
- Opened on or after
opened_afterdate - Only tickets opened on or after this day.
- Opened before
opened_beforedate - Only tickets opened before this day.
- How many
limitnumber - The most to list. Defaults to 25.From 1 to 100.
Outputs
ticketslist- The tickets found, newest first
totalnumber- How many tickets match in all
Example output
{
"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
tickettextRequired - The ticket's ID, from a trigger or an earlier step, or its link.
- Title
titletext - A new title. Leave blank to keep it.
- Status
statustext - A new status. Leave blank to keep it.One of:
new,assigned(Processing (assigned)),planned(Processing (planned)),pending,solved,closed. - Urgency
urgencytext - A new urgency. Leave blank to keep it.One of:
very_low(Very low),low,medium,high,very_high(Very high). - Priority
prioritytext - 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_typetext - Incident or Request. Leave blank to keep it.One of:
incident,request. - Category
categorytext - A new category. Leave blank to keep it.
- Location
locationtext - A new location. Leave blank to keep it.
- Technician
techniciantext - The technician to assign it to instead of whoever has it, or their login or email address. Leave blank to keep it.
- Group
grouptext - The group to assign it to instead of the one it's in. Leave blank to keep it.
Outputs
categorytext- Its category, with the categories above it, such as Hardware > Printers
closed_attext- When it was closed; empty if it isn't
descriptiontext- Its description, as plain text
grouptext- The groups it's assigned to
idnumber- The ticket's ID, for other GLPI steps
linktext- A link to it in GLPI
locationtext- Its location
opened_attext- When it was opened, in GLPI's time zone (YYYY-MM-DD HH:MM:SS)
prioritytext- Its priority, such as Medium or Major
requestertext- Who asked: the requesters' names, or an email address
requester_emailtext- The requesters' email addresses
solved_attext- When it was solved; empty if it isn't
statustext- Its status, such as New, Processing (assigned) or Solved
techniciantext- The technicians it's assigned to; empty if nobody
technician_emailtext- The technicians' email addresses
titletext- Its title
typetext- Incident or Request
updated_attext- When it last changed, in GLPI's time zone
urgencytext- Its urgency, such as Medium or High
Example output
{
"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"
}