Free requirements preview

Catch wrong links and wrong business data.

Protect the action, amount, role and expiry your customer relies on. Define what must be true for each rendered email, then run the same rules in your project and CI.

Example workflow

Open your projects

Loading an example replaces the HTML and rule draft with synthetic fixtures. Use the matrix to check all its scenarios together.

Rendered email HTML

Preview sends HTML for a static check without saving the source. Use synthetic data when trying examples.

Email release requirements

Protect the links and content your email needs to work. Preview for free; save shared project rules with Pro or Enterprise.

Saved requirements block failed releases, even when lint warnings are allowed. Preview does not save rules. Checks inspect HTML source; they do not test delivery, visual visibility, redirects or destination availability.

Required links

Every matching link must have a text or image label and the specified HTTPS host/path. Selectors support a, a#id and a.class; paths match whole segments.

Rule nameLink selectorExact HTTPS hostPath prefix

Allowed web link hostsComma-separated. *.example.com allows subdomains only; add example.com separately for the root. Empty disables this check. Mail and phone links are excluded.Require fully rendered HTMLReject remaining {{…}}, {%…%}, <%…%>, ${…}, *|…|* tokens, including comments. Leave off if your email provider replaces merge tags after this check.

Business content checks

Check amounts, names, translated copy and conditional sections against synthetic fixtures. Text checks require at least one matching element, and every match must pass.

Selectors: #total, .recipient, td.total or a tag. Case-sensitive text; whitespace is collapsed and Unicode normalized. Script, style, template and head content is excluded. Broad or deeply nested matches can exceed the analysis limit; use specific selectors. CSS visibility and delivery are not tested.

Named scenarios become required matrix coverage automatically. Removing a named branch cannot make a release pass. Use synthetic expected values: saved policies and their exports include configured rule text.

Check several template scenarios together →Inspect source-based client compatibility →

Save requirements in your project Workbench to enforce them in release checks and GitHub CI. Each release keeps its rule snapshot and results so later edits do not rewrite its history.