Goal
Drive immediate, safe action while reducing confusion during urgent incidents.
Template Hedgehog
Open navigation
Security notification
Alert users about critical account events with clear actions and support escalation paths.
Workflow assembly
Trigger to production output
01
Trigger
Real send event
02
Workflow
Message journey
03
Layout
Complete structure
04
Components
Reusable blocks
05
Production output
Workflow structure
Sent when security events or high-priority account alerts are detected.
Layout
Security Alert System
Pro archive
This workflow is part of the Pro archive. Use it when this send is recurring enough that source ownership, QA notes, variants, and handoff context matter more than a one-off template.
Workflow pages expose the production shape before purchase: trigger, goal, required fields, variants, QA risks, handoff steps, and linked layout. The paid archive adds the editable source and compiled output for the workflows included in your tier.
What the production package needs.
A workflow is useful when the implementation contract is visible before anyone starts editing markup.
event.timestamp_utc
Time of the detected event.
event.location_hint
Approximate location or device context.
security.review_url
Destination to confirm or deny the event.
Variant routes
- Confirmed safe: Reassurance variant when the user approves the event.
- Access blocked: Escalation variant when account lock or reset is triggered.
Package access
- Public workflow page: intent, trigger, required fields, variants, QA risks, handoff steps, and linked layout.
- Full MJML source for this workflow
- Compiled HTML output ready for ESP upload
- Variant-ready workflow pack files
- Versioned workflow updates inside Template Hedgehog Pro
Linked production layout
Security Alert System
Security alert email with a high-signal alert card, direct support route, and a darker operational footer.
Component stack
Header Dark Brand, Security Alert Card, Telephone Support Highlight, Footer Minimal Dark
Source file
security-alert.mjml
QA and handoff.
The value is not only the rendered email. It is knowing what has to be checked before the ESP takes over.
QA risks to review
- Urgency copy can read as phishing-like if sender identity markers are weak.
- Action links must remain visible in dark mode, especially in mobile clients.
Handoff steps
- Edit copy and block order in MJML, keeping utility and footer sections unchanged unless requirements demand it.
- Compile MJML to HTML and run client checks in Gmail, Outlook Desktop, and Apple Mail before handoff.
- Import compiled HTML into the ESP, map merge variables, and send an internal seed round for QA sign-off.
Template Hedgehog prepares the source, compiled output, preview, QA notes, and handoff context. Mailchimp, HubSpot, Salesforce, NetSuite, Klaviyo, Customer.io, or your ESP still handle audiences, consent, unsubscribe, automation, sending, delivery, and reporting.
Use this workflow inside Pro.
Pro is the archive for teams that keep rebuilding production emails and need repeatable workflows, editable MJML, compiled HTML, QA notes, implementation guidance, and updates.