Newsletter Templates and the Tools That Send Them
Copy-ready layouts for digests, essays and curated link issues, plus a clear view of which tools can assemble and schedule them, what each plan costs and where the limits sit.
The short answer
If you want a newsletter template that fills itself from a content source, such as a spreadsheet of links, an RSS feed or a form of submissions, start with Make. It is a visual automation builder that connects those sources to a draft step and then to the email platform you already use. Its Free plan includes 1,000 credits a month and two active scenarios, which is enough for a weekly digest. The paid Core plan is $9 a month billed annually, or $10.59 a month billed monthly, for 10,000 credits. Those credits are the reason the price moves with your workload, not with your subscriber count.
Make does not design your email for you, and it is not a newsletter sender in its own right. The template itself is still your job: a stable structure with slots for the changing content. The rest of this page gives you those structures as copyable skeletons, explains how to choose a sending platform for them, and shows what a Make-based workflow costs at realistic volumes.
Four newsletter structures you can copy
Most newsletters fall into one of four structures. Pick the one that matches how much original writing each issue contains, not the one that looks most impressive in a gallery. A template is only useful if you can fill it on a deadline, so choose the structure your current output can sustain.
1. The weekly digest
A digest is a short, repeatable issue: a brief intro, three to five items with a one-line context each, and a closing note. It suits teams that curate news, product updates or industry links and want a predictable send day. Because every item has the same shape, the template can be filled by a script or an automation without a writer rewriting the layout each week.
Subject: [Newsletter name] #[issue number]: [lead item in five words]
Preheader: [one sentence that adds to the subject, not repeats it]
[Header: logo left, issue date right, "View in browser" link]
Hi [first name or "there"],
[Two to three sentences: what this issue covers and why it matters this week.]
1. [Item headline]
[One sentence on why it matters to the reader.]
Read more: [link]
2. [Item headline]
[One sentence on why it matters to the reader.]
Read more: [link]
3. [Item headline]
[One sentence on why it matters to the reader.]
Read more: [link]
[Closing line: one question or one action the reader can take.]
[Footer: company name, postal address, unsubscribe link, preferences link] 2. The long-form essay
An essay issue is one piece of writing with a single subject, set in a single column. The template does very little: a header, the body, a sign-off and a footer. Its value is consistency of tone and layout, so readers know what they are getting. Keep images to a minimum, because a long essay that opens with a banner image pushes the first sentence below the fold on many phones.
Subject: [Specific claim or question the essay answers]
Preheader: [the opening sentence of the essay, shortened]
[Header: newsletter name in plain text, no banner]
[Title of the essay]
[Opening paragraph: the problem in the reader's words.]
[Body: three to five sections with subheadings. Each section ends with one takeaway sentence.]
[Closing paragraph: what to do next or what to watch for.]
Reply to this email with your view. I read every reply.
[Sign-off: first name only]
[Footer: company name, postal address, unsubscribe link] 3. The curated links issue
A curated issue groups links into categories. Each link gets a sentence of context, because bare URLs in a list teach readers to skip the block. This structure works well for analysts, researchers and niche communities that want a reading list rather than original analysis. It is also the easiest structure to automate, since each category is a separate source.
Subject: [Number] things worth reading on [topic] this week
Preheader: [the category with the strongest link this issue]
[Header: newsletter name, issue number]
[One-sentence framing of the week.]
[Category one]
- [Link headline]: [one sentence of context]
- [Link headline]: [one sentence of context]
[Category two]
- [Link headline]: [one sentence of context]
- [Link headline]: [one sentence of context]
[Optional recurring block: one question from readers, answered in two sentences]
[Footer: company name, postal address, unsubscribe link] 4. The hybrid announcement
A hybrid issue puts one news item at the top of a standing format, such as a product launch or a policy change, followed by the regular digest or essay below it. Keep the news block short and clearly labeled, so readers who only want the standing content can find it quickly. The hybrid is the only structure that needs an event-driven trigger rather than a fixed calendar.
Subject: [News item in plain words]: [what it means for the reader]
Preheader: [the date or deadline, if there is one]
[NEWS block: label "News", headline, two sentences, one link]
[Standing format: follow the digest or essay template above from this point] Subject lines and preheaders for each structure
Subject lines should match the structure. A digest can name its lead item, because readers expect a list. An essay should state the claim or question it answers, because readers choose it for the argument. A curated issue can use a count of links, since the reader is looking for a reading list. Avoid generic labels such as "This week's newsletter", which give readers no reason to open.
The preheader is the short line that email clients show after the subject. Use it to add information, not to repeat the subject. If your subject names the lead item, the preheader can name the second item or a deadline. Keep both short enough to show in full on a phone, and write them yourself for each issue rather than leaving the template default in place.
Header and footer rules that every template needs
Headers should be compact. Readers scan the top of an issue to decide whether to keep reading, so the logo, the newsletter name and the issue number are enough. A "View in browser" link is useful for readers whose email client breaks the layout. Keep the header in the same position and size every issue, because recognition depends on sameness.
Footers carry the rules you must follow. Include your company name and postal address, a clear unsubscribe link and a preferences link if readers can choose their topics or frequency. Put these in the template once, so they are never forgotten when an issue is assembled in a hurry. Do not hide the unsubscribe link in small grey text on a light grey background; it should be easy to find.
The tools that send these templates
A newsletter template needs two things from its tools: a way to build the layout and a way to send it. Some platforms do both. Others handle only one part, and you connect the rest yourself. The table below compares the options by what they are best for, their starting price and the limitation that matters most in practice. Prices are the ones shown on each vendor's pricing page at the time we checked it.
| Tool | Best for | Starting price | Key limitation |
|---|---|---|---|
| Make (Free plan) | Assembling digests and curated issues from a sheet or feed, at low volume | $0, 1,000 credits a month | Two active scenarios and runs no more often than every 15 minutes |
| Make (Core plan) | Daily digests, scheduled to the minute, with more than two workflows | $9 a month billed annually ($10.59 a month billed monthly), 10,000 credits | Credits are used per module action, so loops over many items use them quickly |
| Make (Pro and Teams plans) | Teams that need priority execution, custom variables or shared scenario templates | Pro: $16 a month billed annually ($18.82 monthly). Teams: $29 a month billed annually ($34.12 monthly). Both for 10,000 credits | Costs more per credit allowance than Core; choose it only for the extra features |
| Your current email platform | Sending the issue to your list, managing subscribers and unsubscribes | Pricing on request | Template editing ranges widely; confirm HTML import before you commit |
Make: what it does well and where it falls short
Make is a no-code visual workflow builder with more than 3,000 apps. For newsletters, its main use is the work around the send: pulling new items from a spreadsheet, feed or form into a draft, applying the same template every week, and passing the result to the email platform that actually delivers the issue. Each step is a module on a canvas, so you can see the whole flow at a glance and change one step without rebuilding the rest.
The Free plan is a good place to prove a digest workflow. It includes 1,000 credits a month with no time limit, two active scenarios, a five-minute maximum execution time and seven days of execution log storage. A weekly digest uses very few credits, so the free allowance is rarely the constraint. The limits that matter are the two active scenarios and the rule that a scenario can run at most every 15 minutes. Those are fine for a digest, but they rule out a workflow that must react to every new form submission in real time.
The Core plan removes the active scenario limit and adds scheduling down to the minute, increased data transfer limits and access to the Make API. It is the plan most newsletter teams need once they move from a weekly digest to a daily one, or once they run more than one issue on the same account. Pro adds priority scenario execution, custom variables and full-text execution log search. Teams adds team roles and the ability to create and share scenario templates, which helps when several editors maintain the same newsletter. Enterprise, with custom functions, enterprise app integrations, 24/7 support and advanced security features, is priced on request.
The main limitation is that Make is not an email editor or a subscriber database. You still need an email platform to store subscribers and deliver the issue, and you still need to design the template in that platform or in HTML. Make also counts every module action as a credit, so a workflow that loops over many items can use the allowance faster than expected. Model the loop before you choose a plan, as shown in the cost table below.
Pricing link: Make pricing page.
What a Make-based newsletter actually costs
Make is priced by credits, not by subscribers, so the cost of a newsletter workflow depends on how many module actions a run uses and how many runs happen each month. The table below multiplies a realistic number of runs by a realistic number of actions. The arithmetic is shown so you can swap in your own numbers. Your email platform's cost is separate and is not included here.
| Workload | Credits per month | Plan that covers it | Price |
|---|---|---|---|
| Weekly digest: 4 runs × 6 actions | 24 | Free | $0 |
| Daily digest: 30 runs × 6 actions | 180 | Free | $0 |
| Daily digest with a 40-action loop over items: 30 runs × 40 actions | 1,200 | Core, 10,000 credits | $9 a month billed annually, or $10.59 billed monthly |
| Same loop, with custom variables and priority execution needed: 30 runs × 40 actions | 1,200 | Pro, 10,000 credits | $16 a month billed annually, or $18.82 billed monthly |
| Per-subscriber trigger: 5,000 sign-ups × 3 actions | 15,000 | Above 10,000, so a larger allowance from the pricing slider | Pricing on request (set by the credit allowance you choose) |
Two patterns follow from the table. First, a digest that runs on a fixed schedule almost never needs a paid plan. Second, the cost jumps when a single run touches each item or each subscriber, because the credits multiply. If you need per-subscriber logic, such as sending a welcome issue to every new sign-up, design the workflow so one run handles a batch rather than one contact at a time. That keeps the credit count predictable.
Choosing a sending platform for your templates
Your email platform decides how the template looks in the inbox, how subscribers are managed and how unsubscribes are handled. Before you choose one, check four things: whether it accepts HTML templates or a template import, whether it keeps unsubscribe links working automatically, whether it lets you schedule a send and whether its pricing is based on subscribers, sends or both. Pricing for these platforms varies, and the figures are not quoted on this page, so take the number from each provider's pricing page for your list size.
If you already have a list in a platform that works for you, keep it. Moving subscribers is a larger risk than changing the template. If you are starting from nothing, choose the platform that makes your structure easiest to build, then add Make only when the manual assembly becomes the bottleneck.
Which structure and tool combination to choose
The decision depends on two questions: how much original writing each issue contains, and how often you publish. The table below turns those answers into a starting point. It is a guide, not a rule, so adjust it to your content and team.
| If you need | Pick | Because |
|---|---|---|
| A fixed weekly send built from a list of links | Weekly digest, with Make on the Free plan | Four runs a month use about 24 credits, far inside the free allowance |
| Thoughtful writing with one subject per issue | Long-form essay, sent from your email platform | The template is simple, so no automation is needed beyond scheduling |
| Daily issues assembled from many items | Digest with Make on Core | Loops over items cost credits quickly, so the 10,000-credit allowance is the working minimum |
| A reading list that changes by category | Curated links issue, with one source per category | Each category can be filled separately, which keeps each run small |
| Launch news inside a regular newsletter | Hybrid announcement, triggered by hand | Event-driven news does not follow a calendar, so a manual trigger avoids sending the wrong block |
Setup checklist for a template and workflow
Set up the template and the workflow in this order. Each step should be finished before you start the next, because a broken link or a missing unsubscribe link is much harder to fix once a workflow is sending automatically.
| Step | What to set up | Done when |
|---|---|---|
| 1. Structure | Choose one of the four structures and write its skeleton in your own words | You can fill the skeleton from a blank page in under an hour |
| 2. Footer | Add the company name, postal address, unsubscribe and preferences links | A test send shows every footer link working |
| 3. Content source | Create a sheet, feed or form with one row or item per block | Each block has a headline, a sentence of context and a link |
| 4. Make scenario | Connect the source, a draft step and the send step, on a schedule | One manual run produces a complete draft without editing |
| 5. Review | Read the draft, check links and the subject and preheader | A human approves each issue before the scheduled send |
| 6. Migration (if you have an existing list) | Import subscribers only with consent records; keep the old unsubscribe status | No unsubscribed contact is re-added to the list |
A workflow for building and maintaining the template
Build the template as modules, not as one long document. The intro, the main content slot, the link block and the footer should each be a separate piece that you can change without touching the others. This is what makes automation possible, and it also makes manual editing faster.
Keep a single source document for the template's rules: the section order, the word limits for each block, the required footer links and the subject line pattern. When a new editor takes over, this document tells them what must stay the same and what can change. Review the template once a quarter, not once an issue, so that changes are deliberate.
Do not redesign the template every issue. Readers learn where the lead item sits and where the links are, and a redesign can disrupt that habit for several issues. Change one visual slot at a time, such as the header art or a recurring feature, and note the change so you can see its effect on clicks.
Measuring whether the template works
Judge the template by what readers do, not by how it looks. Track the open rate across several issues rather than one, because a single issue can be affected by the subject or the day. Look at which blocks get clicks, since a template with five items should show which of the five readers actually use. Watch the unsubscribe rate after a template change, because a layout that buries the footer or changes the sender name can raise it quickly.
Replies are a useful signal for essay and curated issues. If readers reply to a question at the end of an issue, the closing block is doing its job. If replies stop, check whether the question is still relevant or whether the issue has become a list readers skim past.
Newsletter Templates FAQ
Can I build a newsletter template in Make alone?
No. Make assembles content, applies a structure and passes the result to a send step. It does not store subscribers or deliver email on its own. You need an email platform that accepts your HTML or template to send the issue and manage unsubscribes.
Is the Make Free plan enough for a weekly newsletter?
For a weekly digest, usually yes. Four runs of six actions use about 24 of the 1,000 monthly credits. The limits to check are the two active scenarios and the rule that a scenario can run at most every 15 minutes. If you need more than two workflows, or a run more often than that, the Core plan is the next step at $9 a month billed annually or $10.59 billed monthly.
Why does the cost of a Make workflow change so much between two similar newsletters?
Make counts each module action as a credit. A digest that handles a short list of links uses few actions per run. A digest that loops over forty items on every run multiplies that count by forty, and the monthly total follows. Count the actions per run and the runs per month before you choose a plan.
How often should a newsletter publish?
The cadence you can sustain at quality matters more than the cadence you can promise. A weekly digest has a rhythm most readers can rely on. A biweekly essay works when depth matters more than frequency. Whatever you choose, protect the send day, because irregular delivery erodes trust faster than less frequent, regular delivery.
How do I keep a template fresh without redesigning every issue?
Keep the structure stable and vary the content. Rotate one visual slot, such as the header art or a guest quote, and change which block leads. Save larger redesigns for a planned moment, because readers build a scanning habit around the layout and a sudden change can cost engagement for several issues.
What is the best way to handle link curation?
Give every link a sentence of context explaining why it matters. Bare links teach readers to skip the block, and the newsletter loses its voice. Test a curated-links block against a single lead story over several issues and compare the clicks, so the choice rests on your own readers rather than on a general rule.
Do I need consent records before I import subscribers?
Yes, you should be able to show how each subscriber joined your list. Import only contacts with a clear opt-in, keep their unsubscribe status and never re-add someone who has opted out. The rules depend on where your readers live, so check the requirements that apply to your list before you migrate.
Should the newsletter and the template live in the same tool?
Not necessarily. Many teams keep the content source in a spreadsheet, assemble the draft in an automation tool and send from an email platform. This separation makes each part easier to change. It becomes a problem only when the handoffs are unclear, so document which step owns the draft, the review and the send.