Reuse templates in campaigns, workflows, and one-off emails

A template only pays off once it's actually being reused — pulled into campaigns and workflows instead of rebuilt from scratch every time. This article covers the three places a saved template shows up, plus a set of design habits that make any template hold up better across the many different ways people actually read email.

#Using a template in a broadcast campaign

When building a one-time or scheduled broadcast campaign, the email content step lets you select an existing template instead of starting blank. Pick a saved template, and it loads into the campaign's editor pre-populated — you can still make campaign-specific tweaks (like a one-time promo detail) without altering the saved template itself, since editing inside a campaign only affects that send unless you explicitly choose to update the saved template too.

This is the right approach for anything recurring in structure but changing in specifics — a monthly newsletter that always uses the same layout but features different content each time.

#Using a template in a workflow

Workflow email actions (the ones that fire automatically based on a trigger — a new lead, a form submission, an appointment booked) also let you select a saved template rather than building the email inline within the workflow builder. This matters more than it might first seem: a template used across multiple workflow steps or multiple workflows stays consistent, and updating the template updates every place it's used, rather than requiring you to hunt down and edit the same email content in three different automations.

Tip: For a template used inside a workflow, double-check every merge field against the trigger context — a template built for a "new lead" trigger might reference fields that don't exist yet on a contact who hasn't completed onboarding, so verify with a real contact from that specific workflow's audience, not just any contact.

#Using a template for a one-off email

Outside of campaigns and workflows, a saved template can also be the starting point for a single manual send to an individual contact or a small selected group — useful for something like a personalized outreach email that still needs your standard branding and footer, without building that structure from nothing each time.

#Design tips for templates that hold up everywhere

A template gets viewed across dozens of different email clients, screen sizes, and settings you don't control. These habits keep it looking right (or at least acceptable) across nearly all of them.

#Keep width around 600px

Email clients have historically rendered a fixed content width well and struggled with anything wider, and while modern clients are more flexible, 600–640px remains the safe standard for the main content column. Wider layouts risk horizontal scrolling or awkward reflow in older or stricter clients (particularly some desktop apps like Outlook).

#Write real alt text

Every image needs descriptive alt text — not the filename, not left blank. Alt text matters for two real situations: a recipient using a screen reader, and a recipient whose email client has images blocked by default (a common default setting, not an edge case). An email that makes sense with images off is a well-built email; one that's just blank space and a broken-image icon isn't.

#Write a preheader

The preheader is the short snippet of text that appears next to (or below) your subject line in an inbox list view, before the recipient opens the email. If you don't set one deliberately, most email clients default to pulling the first line of body text — which is often something unhelpful like "View this email in your browser." A deliberately written preheader is free real estate to extend your subject line's pitch and improve open rates.

#Design for dark mode

A meaningful share of recipients read email with dark mode enabled on their device, and email clients handle this inconsistently — some invert colors automatically, some respect your original design, some do something in between that can produce odd results (a white logo on a white background that was originally dark-on-light). Test your template with dark mode toggled on in at least one major client, and avoid relying on pure white backgrounds with dark-only logo assets that could disappear if inverted.

#Provide a plain-text fallback

Every marketing email should have a plain-text version alongside the designed HTML version — not just for spam-filter reasons (though a missing plain-text part is a mild negative signal to some filters), but because some recipients' clients or settings genuinely render plain text instead of HTML. Most builders generate a reasonable plain-text version automatically from your HTML content; it's worth a quick review to confirm it reads sensibly rather than assuming it's fine unchecked.

#What done looks like

You know which of the three contexts (campaign, workflow, one-off) a given send belongs in and you've reused a saved template rather than rebuilding, and any template you consider "final" has been checked against the five design habits above — width, alt text, preheader, dark mode, and plain-text fallback — not just visually reviewed in the builder at default settings.

#Related articles

• Email templates overview
• Build an email template with the drag-and-drop builder
• Email marketing overview
• Email deliverability best practices

#Frequently asked questions

#If I edit a template while building a campaign, does it change the saved template everywhere else it's used?

Usually not automatically — campaign-level edits typically apply only to that send unless you explicitly save the changes back to the original template. If you want a change to propagate everywhere the template is used, edit the saved template directly rather than editing it from within one specific campaign or workflow.

#How long should a preheader be?

Roughly 40–100 characters is a safe range — long enough to add real value beyond the subject line, short enough that it isn't cut off in most inbox list views, which vary in how much preheader text they display.

#Do I need a different template for every workflow, or can one template serve multiple workflows?

One well-built, sufficiently generic template can absolutely serve multiple workflows, especially if the structure (header, message, call-to-action, footer) is similar and only the specific merge-field content differs based on the trigger. Building a separate template for every single workflow often creates unnecessary maintenance overhead — reserve separate templates for genuinely different purposes or audiences.