MailMergic Zapier integrationAutomate MailMergic with Zapier.
The MailMergic Zapier integration gives you 2 actions, and no trigger or search. It runs on the free plan. Your Zap starts in another app, then MailMergic builds the personalised document and, if you want, emails it. Here is how each action works and where it trips up.
Verified Trustpilot reviews · AI, automation & growth agency
What the MailMergic Zapier integration does for you
The MailMergic Zapier integration lets another app order a mail merge from MailMergic, the tool that fills PDF and Word documents with your data. A Zap (the automation you build on Zapier) starts on an event elsewhere, then asks MailMergic to produce the document, every time that event happens again.
Three results people build first. A document that answers a form: someone submits a form, and Run Mail Merge & Send Email produces their personalised document and sends it to the address they typed, attached to an email you wrote once. A batch of files without the copy and paste: each new record in another tool launches Run Mail Merge, and the merged document gets the file name you built from the record. A sender that looks like you: the email goes out from your own verified address and sender name, not from a generic one.
What Zapier does not do here is just as clear. MailMergic has no trigger, so nothing that happens inside it can start a Zap: the starting point is always another app. It has no search either, so a Zap cannot look up a past merge. And a Zap never replays history: records that existed before you switched it on get no document.
Still choosing the tool itself? Start with our Zapier review, then Make vs Zapier.
Zapier vocabulary in one minute
Seven words carry this page. Each one is explained here once, then used as is.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. With MailMergic, it always comes from another app, since MailMergic has none.
- Action
- What the Zap does once started: here, the step that asks MailMergic to merge a document, and maybe email it.
- Task
- The unit Zapier bills. One task is one action your Zap completed successfully, and your plan counts those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by its app the moment the event happens.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your MailMergic account linked to Zapier once, then reused by every MailMergic step in every Zap.
What MailMergic costs you in Zapier tasks
MailMergic is not a premium app, so it works from the free plan. Zapier bills in tasks, and only successful actions count.
- Free plan100 tasks per month, unlimited Zaps
- Free plan limitTwo steps: one trigger, one action
- Premium appNo, MailMergic runs on the free plan
- MailMergic operations2 actions, 0 triggers, 0 searches
The trigger of the other app never costs a task. A merge that fails is not counted either. Each successful action counts on its own, so a Zap with three actions uses three times what a one-action Zap uses. The free plan stops at two steps, one trigger and one action: that fits a simple merge exactly. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. MailMergic has no trigger of its own, so the interval grid below applies to the trigger of the app that starts your Zap, when that trigger is a polling one.
Connect MailMergic to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a MailMergic account first, plus access to anything in it you do not own yourself but want a Zap to use.
- 02
Pick MailMergic
Type MailMergic in the search box of the dialog, select it, then click Add connection. A new tab opens on the MailMergic side, where you sign in to your account.
- 03
Sign in and grant access
Log in to MailMergic in that tab and let Zapier use the account. The connection then appears on the Apps page, and every later Zap reuses it without asking.
Your first MailMergic Zap
GoalEach new form response produces a personalised document in MailMergic and emails it to the address the person entered in the form.
- 01
Create the Zap
Start a new Zap. Since MailMergic has no trigger, the Zap starts in your form app: pick it and choose the event for a new response.
- 02
Test the trigger
Run the test and pick a real response among those that come back. You will map the merge on that one, so choose a response with every field filled in.
- 03
Add the MailMergic action
Add Run Mail Merge & Send Email, select your connection, then fill Output Filename, To, From Email, From Name, Subject and Content from the response.
- 04
Turn on sending
Set Enable Email Sending to true, otherwise nothing is sent. Put a single address in To, since the action accepts only one recipient.
- 05
Test, then publish
Run the action test with your own address in To and open the email. If the document is attached and correct, click Publish to switch the Zap on.
MailMergic actions
MailMergic gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Run Mail Merge & Send Email
ActionIn Zapier“Performs a mail merge using MailMergic and automatically sends an email with the personalized document attached.”
Does the merge, then sends an email with the personalised document attached, from your own sender address and name, to one recipient.
Run Mail Merge
ActionIn Zapier“Run a mail merge in MailMergic.”
Launches a mail merge in MailMergic from your Zap and names the output file the way you set it, with no email sent to anyone.
When the MailMergic Zap breaks
Zapier links no help article to MailMergic and no app-specific limit is documented. The traps below come from the action fields and from the rules every Zap follows.
Most surprises come from what the Zap cannot see, or from a Zap that feeds itself. If a Zap still misbehaves, open our Zapier troubleshooting page next.
Sender address not verified
From Email must be created and verified in your MailMergic account before the Zap runs. An address typed only in Zapier gives the action no sender it accepts.Several recipients in To
The To field takes one address only. A list of addresses from the trigger app will not fan out to several people; one email means one recipient.Older records get no document
A Zap only reacts to what happens after it is switched on. Records that existed before are never merged; producing those documents is a separate job.A bulk import held back
If the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back instead of merging them all.
Need help automating MailMergic with Zapier?
A person reads every message.
