Bitte beachten Sie, dass dies nur eine Übersicht der verfügbaren Variablen ist. Manche Variablen können in bestimmten Funktionen inkompatibel oder nicht verfügbar sein. Wenn Sie Variablen vermissen oder sich nicht sicher sind, ob diese wie erwartet funktionieren, fragen Sie sehr gern in unserer Community nach.

Variables can be called by typing :: (just like text modules in the frontend), as long as you’re in a supported text field within the Backend. Zammad will show display all variables being available within this context and replace it to the variable as soon as you selected an entry.


You have an empty field which you referenced and it appears as -? That’s currently working as designed - you might want to ensure that these fields always have a value (in text fields `` `` is a value!).

Wait, what about custom objects?

Good point! Of course, we can’t predict what objects you might create, but we can give you a hint on how to put the puzzle together to get your custom values.

For this, we’ll talk about the inner part of the variable (so everything within #{}), please put the outer part around to have a valid variable. The first part of the variable name consist of the object type. Currently these are:

  • Ticket (ticket)

  • Benutzer (user)

  • Organisation (organization)

  • Gruppe (group)

The second part is the name of the object. This is the name you define during object creation and can be found within the object menu at any time. The first and second part of a variable is divided by a point, e.g.: ticket.number which will in total be #{ticket.number}.

Now, in some situations it’s possible that you’ll need to use a third part. The best example for such a situation would be a select or tree-select field which will by default return the key value, not it’s display name. For this, just extend your variable with .value. This will result in #{}.