Message configuration

Email presets control the subject and message content of notification emails. The email message is composed of fixed system-visible fields and optional user-defined fields.

You can customize only the fields exposed in the preset UI. Fixed fields are always included and cannot be modified.

Supported payload types

The Email destination supports a single payload type for notifications.

Payload type	payload_type API value	Description
Email	email	Sends an email notification for alert or case events

Email payload fields

Fixed fields

These fields are always included in the email and are managed by Coralogix.

They are hidden in the UI and cannot be overridden.

UI label	API field name	Rendered output type	Required	Allowed values	Description
Fixed subject	fixedSubject	String	true	N/A	The fixed prefix of the email subject. Includes the Coralogix notification identifier.
Fixed content	fixedContent	String	true	N/A	Default email content containing core alert or case details.

The fixed content includes information such as:

• Name and ID
• Type, priority, and status
• Created and updated time
• Condition and query
• Links to the alert or case in Coralogix

Customizable fields

These fields are available in the Email preset UI and can be customized per preset.

UI label	API field name	Rendered output type	Required	Allowed values	Description
Subject	customSubject	String	false	N/A	Customizable portion of the email subject. Appended to the fixed subject prefix.
Custom content	customContent	String	false	N/A	Additional content included in the email body. Supports templating.

Subject behavior

The final email subject is composed as:

[Coralogix <entity> notification] <customSubject>

Example rendered subject:

[Coralogix alert notification] Triggered P2 – API latency high

If customSubject is empty, only the fixed subject prefix is used.

Custom content behavior

Use Custom content to add contextual or operational information, such as:

• Service or environment details
• Runbook or dashboard links
• Escalation instructions

The custom content appears alongside the fixed content in the email body.

Templating support

Custom fields support strict templating using alert and case objects.

Example:

Service: {{ alert.groups.service }}
Environment: {{ alert.groups.environment }}
Alert type: {{ alertDef.type }}

Example message configuration

{
  "customSubject": "Triggered P1 – checkout service errors",
  "customContent": "Runbook: https://runbooks.example.com/checkout\nOwner: SRE team"
}

Notes

• Fixed fields cannot be removed or overridden
• Email attachments are not supported
• Message content must be plain text or templated text