Custom notification templates
Customize Qubeforms Business email notifications with HTML templates and form field tokens. Review template limits, attachment handling, and test email formatting.
1. Customize Business notifications
Business owners can change the body of submission notification emails sent to verified recipients. Open Settings → Delivery & spam, find Custom notification HTML, paste a template, and select Save delivery settings. This replaces the default table of submitted fields within the Qubeforms email layout. It does not change the autoresponder, email subject, or service From address.
2. Start with a small template
Use simple headings, paragraphs, and tables. The example assumes the form collects name, email, and message. Token values are HTML-escaped when inserted into the notification. Keep tokens in text content instead of constructing links from untrusted submitted values. The form name and submission ID are provided by Qubeforms.
<h2>New enquiry: {{form_name}}</h2>
<p>Reference: <strong>{{submission_id}}</strong></p>
<table role="presentation" cellpadding="8">
<tr><th align="left">Name</th><td>{{name}}</td></tr>
<tr><th align="left">Email</th><td>{{email}}</td></tr>
<tr><th align="left">Message</th><td>{{message}}</td></tr>
</table>3. Know the template limits
Templates may contain up to 100,000 characters. Supported markup includes common headings, paragraphs, lists, tables, links, and images. The sanitizer removes unsupported tags and attributes, including inline styles, classes, and event handlers. Do not rely on scripts, embedded forms, or custom CSS. Links and image URLs are checked. Missing or non-scalar token values render as empty text, and tokens are exact top-level field names rather than a programming language.
4. Account for attachments and plain text
Secure attachment links are appended separately when a submission has files; you do not need to create those links in your template. They remain temporary links, not attached file bytes. The service also generates a plain-text alternative from submission data. Your HTML template changes the notification body but does not redefine that plain-text alternative or every element of the surrounding email layout.
5. Preview through a real test submission
There is no dedicated preview control. Save, submit non-sensitive sample data from your form, and inspect the email in the clients your recipients use. Include values containing quotes, ampersands, line breaks, and missing optional fields. If formatting disappears, simplify the template to supported markup. Check that tokens match actual field names and that recipients are verified.
6. Restore the default
Clear Custom notification HTML and save to return to the default field table. The template is used only while the form’s current plan supports it. Custom sending-domain support is not available yet; do not expect this template to change sender-domain verification, From addresses, or email authentication. See Autoresponders for submitter-facing text and Verified recipients for notification destinations.
Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.