Product documentation
Updated July 17, 2026

Email Templates: Notification Content

Manage the templates behind notifications: summary, detailed, and custom; categories for reports, system alerts, and test notifications; search and edit.

Overview

Email Templates define what your notifications actually say. The mail profile in Email settings decides how mail is sent; templates decide what lands in the inbox.

Nav path: Settings → Email → Email Templates. Requires Administrator access.

Template types

TypeWhat it's for
Summary TemplatesThe short version — outcome and headline numbers.
Detailed TemplatesThe long version — per-test breakdown and evidence.
Custom TemplatesTemplates you've written yourself.

The choice between summary and detailed is really a choice about who's reading and when.

Summary suits a recurring notification people see constantly — a nightly run that usually passes. It has to be skimmable in two seconds, because that's all it will get. If your nightly email is a wall of detail, people filter it, and then nobody sees the night it goes red.

Detailed suits notifications that fire on something worth reading — a failure, a threshold breach. Here the recipient has a reason to engage, so give them enough to act without opening the product.

A good default: summary for scheduled successes, detailed for failures.

Categories

Templates are organized by category, and All Categories shows everything:

CategoryUsed for
ReportsScheduled report delivery.
System AlertsPlatform-level notifications.
Test NotificationsRun outcomes.

Search Templates filters the list. With nothing matching, you'll see No templates found.

Editing and deleting

Edit Template opens a template for changes; Delete Template removes it.

Before deleting, check what uses it. A scheduled report or a pack's notification step pointing at a deleted template is a notification that quietly stops arriving — and a notification that stops is invisible by nature. Nobody reports missing email.

Writing a template that works

The failure mode with notification email isn't ugliness — it's being ignored. Some things that help:

  • Put the outcome in the subject. People triage from the inbox list. Orders smoke — 3 failed earns a click; Test run complete does not.
  • Say which environment. A failure in staging and a failure in production want different reactions, and the reader can't tell them apart without being told.
  • Link back rather than inlining everything. The detailed test report holds the request and response evidence; a link keeps that intact and the mail readable.
  • Make success quiet and failure loud. If both look the same, the reader learns to skip both.

Previewing

Preview before saving, and prefer previewing to discovering the format from a real 3am alert. The template that reads fine in an editor is the one that arrives with an empty subject when the run has zero failures.

Preview against the cases you don't expect, not the one you designed for:

  • A run with zero failures — does the template still make sense, or does it read as though something is missing?
  • A run with everything failing — does it become an unreadable wall, or does it summarize?
  • A run that errored rather than failed — the two aren't the same, and a template that says "3 tests failed" when the truth is "the API was unreachable" sends people to debug the wrong thing entirely.

That last distinction is worth encoding in the template itself. Failed means your API answered and the answer was wrong; Error means the request never completed. A notification that blurs them costs someone an hour. See High level test report.

Where templates get used

Templates are referenced from several places, which is why deleting one has a wider effect than it appears:

None of these will warn you that their template has gone.

Troubleshooting

  • "No templates found" — the search or category filter is excluding everything. Reset to All Categories.
  • Notifications aren't arriving at all — that's usually the mail profile, not the template. See Email settings.
  • Notifications arrive but look wrong — that's the template. Preview it against a real run rather than guessing.
  • A scheduled report stopped delivering — check its template still exists. Deleting a template doesn't disable what references it.
  • Everyone ignores your notification email — it's probably a detailed template on a job that almost always passes. Switch to summary for the routine case.

Related articles

Next steps

Still stuck?

Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.