How to Run a Mail Merge from Airtable (Email + Printed Letters)

Mail merge sounds dated — it's the Word-and-Excel feature your office used in 2005. But the actual workflow is timeless: take a list of recipients, take a template, fill in the personal details, send. In 2026 the tooling has caught up. You can run a mail merge from Airtable without exporting to CSV, opening Word, fighting formatting, or copying back results.

This guide covers three approaches: Airtable's built-in email action for the simple cases, Gmail or Outlook via Make for campaign-style sends, and Page Designer for printed output. Each has its place.

Picking the Right Approach

Two principles cut across all three:

1. The Airtable base is the source of recipients. A view filtered to the people who should receive this round.
2. The template references fields by name. Wherever you put {First Name}, the merge engine substitutes the value from each record.

Approach 1: Native Airtable Email

The fastest setup. Built into Airtable automations, no other tools needed.

Setup Walkthrough

Use case: notify each task owner about their open tasks every Monday morning.

1. Create an automation with Trigger: At scheduled time (Monday 9am).
2. Add a Find Records action to find all Tasks where Status != Done and Owner is not empty.
3. Add a Run Script step to group tasks by owner (one email per owner with their list of tasks).
4. For each owner, add a Send Email action:
   • To: {Owner Email}
   • Subject: Your open tasks for the week of {Today}
   • Body: a templated message with the list of tasks inserted

Field substitution uses Airtable's "+" button in the email composer — pick the field from earlier steps, and it inserts as a token in the template. When the automation runs, the token gets replaced with the actual field value per record.

Limits

The native email action has limits worth knowing:

• Plain text or basic HTML (no rich design)
• Sent from Airtable's shared email service — not from your own domain by default
• No open or click tracking
• Limited to your plan's automation run quota
• Subject to Airtable's anti-abuse rules — no large external blasts

Use native email for internal team workflows and transactional sends (a confirmation email after a form submission). For outbound campaigns, move to Make.

Approach 2: Gmail or Outlook via Make

When you need real mail merge — campaign-style sends from your own email address, personalized at scale.

The Setup

The Airtable structure:

• A Recipients view filtered to the people who should receive this campaign
• An Emails table (optional but useful) where each record is one email send: linked to the recipient, with sent date, status, opens, clicks

The Make scenario:

1. Trigger: Airtable Watch Records on the Recipients view, or Schedule for a campaign you launch manually.
2. Iterator if you're processing all records in a single run.
3. Filter: ensure the recipient has an email and hasn't been emailed in this campaign (check the Emails table or a campaign-specific field on the contact).
4. Gmail/Outlook Send Email with a templated subject and body referencing recipient fields.
5. Airtable Create Record on the Emails table (linked to the recipient) for the audit trail.
6. Airtable Update Record on the recipient: set Last Emailed = today.

The Make scenario can throttle sends — add a Sleep module between sends to keep the rate under what Gmail will accept (about 100/hour for a personal account, 2000/day total).

Template Structure

A good outbound email template has three layers:

Layer 1: Personalized opener. First 1-2 sentences specific to the recipient. Reference their role, their company, or something recent in their world.

Hi {{First Name}},

I came across {{Company}}'s recent {{Achievement}} —
{{Personalized comment}}.

Layer 2: Body. The pitch or message itself. Same for everyone, or branched by recipient segment.

Layer 3: Personalized close. Optional, but signing off with something specific helps.

If you're at {{Recent Event}} next month, let me know —
happy to grab a coffee.

— {{Sender First Name}}

The personalization fields ({Achievement}, {Recent Event}, etc.) live in dedicated fields on the recipient record. Populating them takes work — either manual research per recipient before launching the campaign, or an AI-powered enrichment step (a Make scenario that calls an LLM to summarize the recipient's LinkedIn or company page into the field).

Either way, the campaign quality depends on the personalization quality. A campaign that's 80% identical and 20% genuinely specific to each recipient outperforms one that's 100% identical by orders of magnitude.

Reply Detection and Stopping

When a recipient replies, the campaign should stop sending them more. Set up a second Make scenario:

1. Trigger: Gmail/Outlook Watch Emails (filtered to reply patterns or specific labels).
2. Search Records on Contacts by sender email.
3. Update Contact: set Status to Replied.
4. The main campaign scenario filters out anyone with Status = Replied.

This is the single biggest deliverability win — never email someone who already replied. They've engaged; treat the conversation as a real human one from there.

Throttling and Deliverability

Three rules that keep sends out of spam:

1. Throttle. 100 sends per hour max from a personal Gmail/Outlook. Higher rates flag the account.
2. Vary content. Even the templates should produce different-enough body content per recipient. Identical body across 500 sends is a spam signal.
3. Authenticate your domain. SPF, DKIM, and DMARC records on your sending domain dramatically improve inbox placement.

For sends over 500 per campaign or weekly volume in the thousands, the right tool is a cold-email or marketing automation platform (Mailshake, Lemlist, ConvertKit, ActiveCampaign, etc.). Connect them to Airtable via Make and continue using Airtable as the recipient database, but offload the sending and tracking to a tool built for it.

Approach 3: Page Designer for Printed Letters

For physical mail — letters, certificates, address labels, name badges — Airtable's Page Designer extension is the tool.

What Page Designer Does

Page Designer is a layout extension. You add it to a base, design a page layout once with text and field placeholders, and Airtable generates one page per record (or one per filtered record).

You can:

• Print directly to a printer
• Export to PDF (single record or batch)
• Embed images, logos, and field values
• Use formula fields for computed content (e.g., a formatted address block)

Page sizes include letter, A4, label sheets (Avery), and custom dimensions.

Setup Walkthrough

Use case: print 200 holiday cards with names and addresses.

1. Open the base with your contacts. Filter to the 200 contacts who should receive a card.
2. Click Extensions in the top-right, add Page Designer.
3. Set the page size to your card dimensions.
4. Drag a Text element onto the canvas. Type a greeting like "Dear {First Name}," — the field placeholder part references the field, which Page Designer will replace per record.
5. Add more text elements for the body of the message.
6. For addresses, drag a Text element and use a formatted address formula field (or concatenate Address, City, Zip in a multi-line block).
7. Add your logo as an Image element.
8. Preview by clicking through records — each card updates with the right person's details.
9. Export to PDF: choose Export → All Records to get one multi-page PDF.

The PDF is now ready to send to a print shop or run through your printer.

When Page Designer Shines

Page Designer is purpose-built for printed output, which means it handles edge cases the average no-code tool ignores:

• Multi-record-per-page label sheets (3-per-row, 10-per-column Avery labels)
• Conditional content based on fields (show the holiday message only for contacts tagged "Send Card")
• Image placement that respects field values (logo varies by company)
• Bleed and margin settings for professional printing

When It Falls Short

Page Designer's layout engine isn't as rich as InDesign. If you need:

• Complex typographic layouts (varied font weights, kerning, justified columns)
• Vector graphics overlaying field data
• Variable image sizing per record

…you'll want to either flatten the design to a static template (PDF or InDesign export) and use a service like Lob to print and mail at scale, or use a no-code document tool like Docupilot or PandaDoc instead (better for letters and certificates, less good for label sheets).

Combining Approaches

A common scenario: a year-end mailing where most contacts get an email but a key segment gets a printed letter.

The combined flow:

1. Recipients view filtered to all year-end contacts.
2. Field on each contact: Preferred Outreach (Email / Printed).
3. Make scenario for emails: filter to Preferred Outreach = Email, send via Gmail.
4. Page Designer for letters: filter to Preferred Outreach = Printed, export PDF, mail.
5. Single audit trail: an Activity record per contact regardless of channel.

This is more work than either alone but uses each tool for its strength.

Reporting and Iteration

After a campaign, the data you collected is gold:

• Send rate: how many emails actually went out?
• Reply rate: how many people responded?
• Open rate (if tracked): how many opened?
• Click rate: how many clicked your link?

Build a dashboard view on the Emails table grouped by Campaign showing these aggregates. Compare campaign variants to learn what works.

Even without tracking, the most useful metric is reply rate per template version. Run A/B tests by sending two different subject lines or openers to different segments, and measure which generated more replies. Personalization, brevity, and specificity almost always win.

Common Mistakes

A few patterns that go wrong in mail merge campaigns.

Empty fields in templates. A template that uses {Company Name} will produce an awkward "Hi John, I came across 's recent..." if the Company Name is empty. Add a fallback: use a formula that returns "your company" if the field is empty, or skip the personalization sentence entirely for those records.

Wrong recipient list. A view filtered to "Newsletter Subscribers" might include unsubscribers you forgot to remove. Run an extra Make filter step to double-check against your unsubscribe list before sending.

Test sends going to real contacts. When testing a campaign, set the recipient view to only include yourself or a test contact. We've seen plenty of "oops" stories from teams forgetting to switch the trigger view back.

Time-zone problems on scheduled sends. A 9am send scheduled in your time zone goes to a recipient on the other side of the world at 3am their time. Use a recipient time zone field and stagger sends accordingly.

Where to Go Next

For the contact data structure that mail merge runs on top of, our contact management system tutorial covers the schema. For the Make patterns powering the multi-record send, the Make automation guide covers iterators and throttling.

For Airtable's official Page Designer documentation, see Page Designer support.