Template Generator Help

🛠 Help & Usage Guide: Zabbix Template Generator from Excel CSV

This tool allows you to generate valid Zabbix JSON templates directly from Excel-like CSV content.
Paste your data into the input field, click Generate, and the resulting Zabbix template will appear in the output area.

📥 Download Starter File

📄 Download a base Excel CSV as start

📄 CSV Format & Supported Types

Each line must contain a Type column to define the type of Zabbix object. Different types use different fields.

🔷 Supported Types & Fields

✅ VALUEMAP

Defines value mappings for items (e.g. 0 → Down, 1 → Up).

Fields: Type, Name, Value, NewValue

VALUEMAP, one, 0, Down
VALUEMAP, one, 1, Up

✅ MACRO

Defines template-level macros, such as {$MACRO1}.

Fields: Type, Name, Value

MACRO, {$MACRO1}, 1
MACRO, {$MACRO2}, 2

✅ MODBUS

Creates items and optional triggers for Modbus-based monitoring.

Fields: Type, Name, Key, Description, Units, Multiplier, ValueType, TriggerType, TriggerCondition, TriggerName, Endpoint, Slave ID, Function, Address, Count, Data Type, Endianness, Offset

Supports: trigger conditions (see below), macros in endpoints like tcp://{$MODBUSIP}:{$MODBUSPORT}

✅ SNMP

Defines SNMP-based item and trigger entries.

Fields: Type, Name, Key, Description, Units, Multiplier, ValueType, TriggerType, TriggerCondition, TriggerName, OID

✅ API

Defines trapper items that receive values via API or external scripts.

Fields: Type, Name, Key, Description, Units, Multiplier, ValueType, TriggerType, TriggerCondition, TriggerName

🧠 TriggerType: Options & Meaning

TriggerType	Description
`auto`	Auto-generates a trigger using `TriggerCondition` and the item key.
`raw`	Full Zabbix expression is provided (e.g., `last(/template/item)>30`).
`x`	Disabled or placeholder. No trigger will be created.

🔥 TriggerCondition: Supported Expressions

These are used with TriggerType = auto and are applied to the current item key. They're transformed into Zabbix expressions like last(/template/key) <condition>.

Format	Meaning	Example	Translates To
`>X`	Greater than X	`>30`	`last(...) > 30`
`<X`	Less than X	`<10`	`last(...) < 10`
`between(X,Y)=1`	Between X and Y	`between(20,22)=1`	`last(...) >= 20 and last(...) <= 22`
`between(X,Y)=0`	Not between	`between(20,22)=0`	`last(...) < 20 or last(...) > 22`
`in(A,B,C)=1`	Value is one of A, B, C	`in(20,21,22)=1`	`last(...)=20 or last(...)=21 or last(...)=22`
`in(A,B,C)=0`	Value is NOT A, B, or C	`in(20,21,22)=0`	`last(...)≠20 and last(...)≠21 and last(...)≠22`
`<X or >Y`	Outside range	`<20 or >22`	`last(...) < 20 or last(...) > 22`
`>X and <Y`	Inside range (strict)	`>19 and <23`	`last(...) > 19 and last(...) < 23`
`between(...) or in(...)`	Combined logic	`between(20,22)=1 or in(30,31)=1`	Logical OR combination
`in("a","b")=1`	Text match	`in("OK","READY")=1`	`str(...)="OK" or str(...)="READY"`

📌 Tips

Use macros like {$MODBUSIP} to keep templates reusable.
Leave unused fields blank — they will be ignored.
Use TriggerType = raw to manually write full Zabbix expressions for advanced use cases.
In trigger conditions using raw, you can use these special variables:
- $this – full item reference (e.g. last(/Template/ItemKey))
- $template – resolved template name only
- $key – item key (e.g. vibration.avg)
For item keys, you can also use $name – this will be replaced with the resolved item name.
When generating item keys, the following automatic transformations are applied:
- $name is replaced with the item name
- All spaces are removed
- Umlauts like ä, ö, ü are replaced (e.g., ä → ae)
- Only alphanumeric characters are retained (non-letters/digits are stripped)
This ensures the final Zabbix key is clean and valid.
Decimal numbers must use a dot . as the separator (e.g. 0.01 not 0,01).
Zabbix does not support commas as decimal separators in preprocessing steps or trigger expressions.