Notification templates control the content format of incident notifications. The system uses templates to render incident information and send notifications when assigning incidents.
Plan requirement: This feature requires an On-call Pro or higher subscription. Learn more
If you need a unique identifier inside a template, use incident variables such as {{.IncidentID}} or {{.LabelsMD5}}. If you need environment-specific values, pass them in via alert labels or field mappings instead of reading host environment variables from the template.
Auto-created incidents have labels, same as the first merged alert’s labels
Go to Incident List → view incident details to see all label information.
Configured custom template but default template was used instead?
When creating custom templates, the system uses mock data to check syntax. Mock data covers limited scenarios; rendering may fail at runtime, and system falls back to default template.
Recommend checking if variable exists before referencing:
// Escape HTML characters{{toHtml .Title}}// Render with first non-empty value{{toHtml .Title .TitleEnglish}}
How to convert time format?
// date function: Convert timestamp to readable format{{date "2006-01-02 15:04:05" .StartTime}}// ago function: Convert time difference to readable format (e.g., "5 minutes ago"){{ago .StartTime}}
How to reference external variable inside for loop?
How to extract field value with . (like obj.instance)?
Use index function:
{{index .Labels "obj.instance"}}
How to extract labels from associated alerts and deduplicate?
// alertLabels: Get deduplicated array{{alertLabels . "resource"}}// joinAlertLabels: Deduplicate and join with delimiter as string{{joinAlertLabels . "resource" ", "}}
Use jsonGet function to extract values by path from valid JSON. Syntax reference at gjson.dev.
// Extract detail_url field from rule_note label{{jsonGet .Labels.rule_note "detail_url"}}// Extract name field of first element in JSON array{{jsonGet .Labels.slice "0.name"}}// Iterate array, match instanceId field where userId==7777{{jsonGet .Labels.rule_note "#(userId==7777)#.instanceId"}}
How to get image URL?
imageSrcToURL: Convert image_key or URL to accessible address (for Dingtalk/Slack App)
{{ $root := . }}{{ range $i, $v := .Images }} {{ $imageURL := imageSrcToURL $root $v.Src }} {{ if $imageURL }}{{ end }}{{ end }}
transferImage: Upload image to third-party platform (for Feishu/Lark App)
{{ $root := . }}{{ range $i, $v := .Images }} {{ $transferURL := transferImage $root $v.Src }} {{ if $transferURL }}{{ end }}{{ end }}
When editing a Feishu/Lark app template, the Additional info tab next to the Content tab provides a card-fields switch panel (“These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message.”), which controls whether 7 system fields — channel, snooze deadline, severity, aggregated alert count, responders, the details button, and AI analysis — are rendered at the bottom of the card.Create war room can be configured on Feishu/Lark app, Dingtalk app, and Slack app templates (backed respectively by the feishu_app_war_room_enabled, dingtalk_app_war_room_enabled, and slack_app_war_room_enabled fields, off by default; save the template to apply the change). The switch itself is labelled Create war room, and the panel describes it as “Once enabled, a dedicated Create War Room button is shown at the bottom of the card when the group-creation conditions are met.”
On: when the incident is not closed, has no war room yet, and has responders, the card for that channel shows a dedicated 👥 Create War Room button at the bottom; clicking it starts group creation
Off: no such button is shown
Keep custom actions after incident closure is offered on Feishu/Lark app, Dingtalk app, Slack app, and Microsoft Teams templates; the WeCom app template does not offer it (the panel does not render the switch for that channel). It is backed by the incident_card_closed_action_apps field — an array of the channel keys for which the capability is enabled (e.g. ["feishu_app"]), off by default (an empty array means off); save the template to apply the change.
On (panel description: “Enabled. Configured custom actions can be run from the message card for 3 days after the incident is closed. After that, run them from the incident details.”): configured custom actions can still be run directly from the message card for 3 days after the incident is closed; after that, run them from the incident details page
Off (panel description: “Disabled. Custom actions are hidden from the message card after the incident is closed. You can still run them from the incident details.”): the message card no longer shows the custom actions entry once the incident is closed; they can still be run from the incident details page
Together with the 7 card-field switches above, the Additional info panel holds 9 switches on Feishu/Lark app, Dingtalk app, and Slack app templates, 7 on Microsoft Teams, and 6 on WeCom app (see the channel template tabs below).The card’s bottom action area has changed as well: More Actions (that placeholder is its label) is now a dropdown select menu holding custom actions, snooze durations, and unacknowledge — the war room button is no longer one of its entries.
{{if .Description}}**description** :{{toHtml .Labels.body_text .Description}}{{end}}{{if .Labels.resource}}**resource** : {{toHtml (joinAlertLabels . "resource" ", ")}}{{end}}{{range $k, $v := .Labels}}{{if not (in $k "resource" "body_text")}}**{{$k}}** : {{toHtml $v}}{{end}}{{end}}{{ $root := . }}{{ range $i, $v := .Images }}{{ $imageURL := imageSrcToURL $root $v.Src }}{{ if $imageURL }}{{ end }}{{ end }}
Dingtalk App Notification Effect
As with the Feishu/Lark app, the Additional info tab next to the Content tab provides a card-fields switch panel (“These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message.”), controlling whether 7 system fields — channel, snooze deadline, severity, aggregated alert count, responders, the details button, and AI analysis — are rendered at the bottom of the card; the Dingtalk app template also offers the Create war room switch (backed by the dingtalk_app_war_room_enabled field, off by default; save the template to apply the change) and the Keep custom actions after incident closure switch (recorded in the incident_card_closed_action_apps channel-key array, off by default), so the Additional info panel holds 9 switches.
As with the Feishu/Lark app, the Additional info tab next to the Content tab provides a card-fields switch panel (“These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message.”), controlling whether 6 system fields — channel, snooze deadline, severity, aggregated alert count, responders, and the details button — are rendered at the bottom of the card. The WeCom app template does not offer the AI Analysis, Create war room, or Keep custom actions after incident closure switches, so its Additional info panel holds 6 switches.
Requires Slack integration configured first. Max message length ~15000 characters, truncated if exceeded.
When displaying images, separate images from other content with ---, format starts with  {{ end }}{{ end }}
Slack App Notification Effect
As with the Feishu/Lark app, the Additional info tab next to the Content tab provides a card-fields switch panel (“These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message.”), controlling whether 7 system fields — channel, snooze deadline, severity, aggregated alert count, responders, the details button, and AI analysis — are rendered at the bottom of the card; the Slack app template also offers the Create war room switch (backed by the slack_app_war_room_enabled field, off by default; save the template to apply the change) and the Keep custom actions after incident closure switch (recorded in the incident_card_closed_action_apps channel-key array, off by default), so the Additional info panel holds 9 switches.
Requires Teams integration configured first. Max message ~28KB, errors if exceeded.Default Template:
As with the Feishu/Lark app, the Additional info tab next to the Content tab provides a card-fields switch panel (“These fields are rendered by the system. Use the switches to show or hide them at the bottom of the message.”), controlling whether 6 system fields — channel, snooze deadline, severity, aggregated alert count, responders, and the details button — are rendered at the bottom of the card, plus a Keep custom actions after incident closure switch (recorded in the incident_card_closed_action_apps channel-key array, off by default), so its Additional info panel holds 7 switches. The Microsoft Teams template does not offer the AI Analysis or Create war room switches.
WeCom bots support both Markdown v1 and Markdown v2. Existing templates continue to use v1 by default. You can enable v2 per template without affecting other templates.
Open Template Management, then create a custom template or copy an existing template.
2
Select the WeCom bot template
Select WeCom Bot under template content and enable Use Markdown v2.
3
Edit and save the template
Edit the content using standard Markdown and save it. The setting is stored with this template and affects only notifications that use it.
Disabling the toggle switches the template back to Markdown v1. Existing v1 template content and delivery behavior remain unchanged.
Markdown v2 uses the UTF-8 byte length and allows up to 4096 bytes. Dynamic fields can cause the final notification to exceed this limit. In that case, Flashduty sends a compact message marked “The original message was too long and has been shortened” instead of dropping the notification. The compact message retains the incident number, title, channel, severity, trigger time, resource, responders, details link, and acknowledge link.
You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Severity: {{.IncidentSeverity}}{{if gt .AlertCnt 1}}, {{.AlertCnt}} alerts grouped{{end}}
Default Template:
You have a pending incident: {{toHtml .Title}}, Channel: {{.ChannelName}}, Severity: {{.IncidentSeverity}}{{if gt .AlertCnt 1}}, {{.AlertCnt}} alerts grouped{{end}}
Supports full HTML format. Default template provides professional email layout including incident title, severity, channel, trigger time, responders, plus “Acknowledge Now” and “View Details” buttons.
