From 0e56de5504300bdce0a825cad98de302959d1809 Mon Sep 17 00:00:00 2001 From: Esther Kim Date: Mon, 16 Mar 2026 12:39:51 -0400 Subject: [PATCH] [DOCS-13661] Document triple curly brace syntax for raw/unencoded output Co-Authored-By: Claude Sonnet 4.6 --- content/en/monitors/notify/variables.md | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/content/en/monitors/notify/variables.md b/content/en/monitors/notify/variables.md index bc337d60ce8..6505d09f7d5 100644 --- a/content/en/monitors/notify/variables.md +++ b/content/en/monitors/notify/variables.md @@ -475,7 +475,20 @@ For instance, assume your composite monitor has a sub-monitor `a`, which is a Lo ### Character escape -Variable content is escaped by default. To prevent content such as JSON or code from being escaped, use triple braces instead of double braces, for example: `{{{event.text}}}`. +Variable content is HTML-encoded by default. For example, special characters like `&` and `'` are converted to `&` and `'` in the rendered output. To output raw, unencoded content, use triple curly braces instead of double curly braces: + +| Syntax | Output | +|--------|--------| +| `{{variable}}` | HTML-encoded (default) | +| `{{{variable}}}` | Raw, unencoded | + +For example, to render the check message without HTML encoding: + +```text +{{{check_message}}} +``` + +This is particularly relevant when `{{check_message}}` contains auto-generated URLs with query parameters (for example, on HTTP Check monitors). The `&` characters in those URLs are HTML-encoded by default, which can break clickable links in notifications. Use `{{{check_message}}}` to preserve the URLs as-is. ## Template variables