# Webhook Template Editor
Click **+Add** or **Edit** to create or modify webhook payload templates.
The template list includes both the built-in **EnGenius Standard** template and administrator-created custom templates.
Administrators can:
* Create a new template by clicking **+Add**
* Modify an existing template by clicking **Edit** from the Actions field
The editor includes the following sections
Editor
## **Liquid Body**
The **Liquid Body** section defines the **HTTP request body** using **Liquid template syntax**.
Webhook event data is automatically mapped into the template during webhook generation.
The rendered output must produce valid JSON compliant with [**RFC 8259**](https://datatracker.ietf.org/doc/html/rfc8259)**.**
Edit Liquid Body
## **Generate Preview**
Click **Generate Preview** to preview the final webhook content based on the selected sample alert data.
During preview generation, EnGenius Cloud applies the selected sample alert values to the Liquid template and displays the rendered result.
If there are any **JSON format errors** or **Liquid syntax errors**, they will be detected during preview generation.
## Liquid Headers
The **Liquid Headers** section allows administrators to add custom **HTTP headers** to webhook requests.
Each header is configured using a **name/value pair.**
Header values support **Liquid syntax** and can dynamically reference webhook event data.
All configured headers are included in the final webhook HTTP request.
Liguid Headers
## **Webhook Data Sample**
The Webhook Data Sample section displays an example webhook JSON structure based on the selected **Sample Alert Type**.
Administrators can use the displayed property names as **Liquid variables** in the Liquid Body or Liquid Headers template configuration.
For example, if the sample webhook data contains the following property:
```
{
"alertType": "Device offline"
}
```
The property name **alertType** can be referenced in the template using the following Liquid syntax:
```
{{alertType}}
```
When the webhook request is generated, the variable will be automatically replaced with the actual event value: `Device offline`
This feature helps administrators:
* Understand the webhook event data structure
* Identify available Liquid variables
* Preview the rendered webhook content before deployment
Webhook Data Sample
## **Toolbox**
The Toolbox provides several helpful resources for exploring **EnGenius Standard templates** and **alert data.**
### **Sample Templates**
Select **EnGenius Standard** to view and export a reference **Liquid template example**.
This helps administrators quickly understand the default webhook payload format and Liquid syntax usage.
### **Sample Alert Types**
The **Sample Alert Types** section allows administrators to test **payload template** using different webhook alert events.
This helps preview and validate the rendered webhook content before deployment.
The default sample alert type is:
* **AP Offline**
### **Test Webhook**
Enter the HTTPS URL of the webhook receiver. The rendered webhook request, including the sample alert data and configured HTTP headers, will be sent to the destination webhook server.
This helps administrators validate webhook integration and preview the final webhook request before deployment.
Test Webhook
In this example, a test webhook was sent to the free test service, requestbin, where we can examine the final results.
### **Free testing webhook receivers**
Two of these free testing webhook receivers are:
*
*
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://doc.engenius.ai/webhook/webhook-template-editor.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.