All articles › Automations

Saving an Automation as a Template

Save your automation as a reusable template

Once you have built an automation that works well, you can save it as a reusable template. Templates let you or your team quickly deploy the same workflow structure for new use cases without rebuilding from scratch.

How to save as a template

  1. Navigate to Automations in the sidebar.
  2. Open the automation you want to save as a template.
  3. Click the actions menu and select Save as Template.
  4. Give the template a descriptive name (e.g., "Product Launch Drip - 5 Emails").
  5. Optionally add a description explaining when and how to use the template.
  6. Click Save.

What gets saved in the template

The template captures the complete structure of the automation:

  • All nodes: triggers, email sends, delays, conditions, and tag actions.
  • The visual layout and connections between nodes.
  • Step configuration (delay durations, condition types, tag names).
  • Email content within send email steps (subject lines, body content, preheaders).

What is not saved

  • Run history and statistics.
  • The active/inactive state (templates are always deployed as inactive).
  • Contact-specific data or enrollments.

Using your saved templates

  1. Go to Automations and click Create Automation.
  2. In the template selection, look for the Your Templates section below the pre-made templates.
  3. Select your saved template.
  4. A new automation is created with all the template's steps and configuration pre-loaded.
  5. Customize the content, timing, and triggers for your specific use case.
  6. Save and activate when ready.

Managing templates

Your saved templates appear in the Templates tab of the Automations page, in a separate section below the built-in Mailnaptic templates. From here you can:

  • Preview the template to see its structure.
  • Delete templates you no longer need.
  • See when the template was created.

Template vs. duplication

Both templates and duplication create copies of automations, but they serve different purposes:

Feature Template Duplicate
Purpose Reusable blueprint for future automations One-off copy for iteration or testing
Persistence Saved permanently in your template library Creates a regular automation
Team access Available to all team members Just another automation in the list
Content Snapshot at time of save Copy at time of duplication

Best practices

  • Save templates for automation patterns you use repeatedly (e.g., product launches, event sequences, seasonal campaigns).
  • Write a clear description so team members understand when to use the template.
  • Update templates periodically to reflect your latest best practices.
  • Use templates to enforce consistency across your organization's automations.
  • Keep template names descriptive and organized — a naming convention like "[Category] - [Name] - [Step Count]" helps.
Was this helpful?

Copy for AI (Markdown)

Related articles

Mailnaptic · Help center