Last Modified : 08 August 2026
JSON Event Data Template
The JSON Event Data Template parses the raw data from a trigger as a JSON object. Each top-level key-value pair in the JSON becomes a separate field in the resulting event data.
How It Works
- The trigger produces a byte array (e.g., from a web checker or custom trigger).
- The JSON template attempts to parse the bytes as a JSON object.
- Each key in the JSON object becomes an event data field name.
- Each value becomes the corresponding field value, stored as a string.
Example
Given the following JSON output from a trigger:
{
"status": "changed",
"name": "Abs",
"version": "1.3.0",
}
The resulting event data would contain four fields:
| Field Name | Value |
|---|---|
| status | changed |
| name | Abs |
| version | 1.3.0 |
If the trigger output is not valid JSON, parsing will fail and the
event data will be empty.