Automation Variables and Templates in GLPI 11

Complete list of variables available in GLPI for ticket templates, notifications and forms. Automate dynamic text without writing code.

Automation variables transform generic templates into personalized messages. Instead of "Your ticket has been updated", the email says "Your ticket #12345 – Printer out of toner was updated by technician John".

Where to use variables in GLPI

  • Notification templates: emails for new ticket, follow-up, resolution, satisfaction survey
  • Ticket templates: pre-filled title and description
  • Task templates: description with dynamic data from the parent ticket
  • Forms (GLPI 11): calculated fields and conditional text

Most used variables

Ticket

VariableDescription
##ticket.id##Ticket number
##ticket.title##Ticket title
##ticket.description##Full description
##ticket.url##Direct link to the ticket
##ticket.status##Current status (New, In progress, etc.)
##ticket.priority##Priority (Very low to Very high)
##ticket.category##Ticket category
##ticket.creationdate##Opening date
##ticket.solvedate##Resolution date

Requester

VariableDescription
##user.name##Requester name
##user.email##Requester email
##user.phone##Requester phone

Technician and Group

VariableDescription
##ticket.assigntousers##Assigned technician(s)
##ticket.assigntogroups##Assigned group(s)

Follow-ups and Tasks

VariableDescription
##followup.description##Follow-up text
##followup.author##Follow-up author
##task.description##Task text
##task.author##Task author

Notification template example

Hello ##user.name##,

Your ticket ##ticket.id## - ##ticket.title## has been updated.

Current status: ##ticket.status##
Assigned technician: ##ticket.assigntousers##

Access it here: ##ticket.url##

Best regards,
Support Team

Tip

To see the complete list of variables available for each notification type, edit the template and click on the "Available tags" tab. The list is contextual and varies according to the item type.

Frequently Asked Questions

GLPI offers variables for ticket data (##ticket.title##, ##ticket.description##, ##ticket.url##), the requester (##user.name##, ##user.email##), the technician, the entity and more.

Partially. Ticket templates accept variables in text fields, but with a more limited scope than notification templates.

Not natively. Variables are predefined by GLPI. For custom logic, use business rules or the NexTool Automations module.

In Configuration > Notifications > Templates, when editing a template, click on the 'Available tags' tab to see all variables available for that notification type.

Need help?