MergeMole Zapier integrationAutomate MergeMole with Zapier.
MergeMole Zapier integration: 0 triggers, 1 action, 0 searches. Zapier can ask MergeMole to build a PDF from one of your templates each time something happens in another app. MergeMole never starts the automation itself, so the starting event always comes from elsewhere.
Verified Trustpilot reviews · AI, automation & growth agency
What the MergeMole Zapier integration does for you
The MergeMole Zapier integration is a one-way link: an event in some other app starts the automation, and MergeMole fills one of your templates with the data that event carried. You get a PDF out of it. The trigger always comes from another app, and the output is always a document.
Three results people build with it, all on the single Create PDF action. First, one document per record: a new row lands in a spreadsheet, and MergeMole turns that row into a PDF from the template you picked. Second, a file you can find again: the Document Name field takes values from the earlier step, so each output gets a name that says which record it belongs to. Third, a pair of documents from one event: add Create PDF twice in the same Zap, each pointing at a different template, and one row yields two outputs.
Now the limits. Zapier offers no trigger for MergeMole, so nothing that happens inside MergeMole can start a Zap. There is no search either, which means a Zap cannot look up a MergeMole document that already exists. And Zapier does not design templates: the Template field only lists the ones already set up in your MergeMole account, so that work stays on the MergeMole side.
If you are still choosing a tool, read our Make vs Zapier comparison or our n8n vs Zapier comparison before you commit.
Zapier words in one minute
Eight words come back all over this page. Here is what each one means, without the jargon.
- Zap
- The automation you build on Zapier: one event that starts it, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. MergeMole has none, so yours comes from another app.
- Action
- What the Zap does once it has started: the step that writes, sends or builds something for you. Here, Create PDF is the only one.
- Task
- The unit Zapier bills. One task is one action the Zap completed successfully, and the number on your plan counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens, with no wait.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the next steps can use it. MergeMole offers none on Zapier.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
What a MergeMole Zap really costs
MergeMole is not a premium app, so it works on the free plan. The bill is counted in tasks, and only the PDF step counts.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Billed per run1 task per successful Create PDF
- Trigger checksFree, never counted
The trigger in the other app never costs a task, however often Zapier checks it. Each Create PDF that goes through is one task; a run that fails is not counted. Two Create PDF steps in one Zap means two tasks per run. On the free plan you get 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: add a filter or a second action and you need a paid plan. The interval grid below concerns the starting app only, and only if its trigger is a polling one.
Connect MergeMole to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your MergeMole account linked once, then reused by every step that needs it.
- 02
Pick MergeMole
Type MergeMole in the search box of the dialog, select it, then click Add connection. A new tab opens on the MergeMole side. Keep it open until you have signed in.
- 03
Sign in and allow access
Log in to MergeMole in that tab and grant Zapier access. You need a MergeMole account, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first MergeMole Zap, step by step
GoalProduce a PDF for each new spreadsheet row, but only for rows that pass a condition you choose.
- 01
Create the Zap and set the trigger
Start a new Zap and pick your spreadsheet app with its new-row event. This is where the Zap begins, since MergeMole has no trigger of its own.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent rows from the connected account, so you map fields on real data rather than guesses.
- 03
Add the filter
From the plus icon, add a Filter and fill its three boxes: the field to look at, the rule, and the value. Pick a text rule for text and a number rule for numbers. A filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add Create PDF
Add MergeMole, choose Create PDF, select your template, and build the Document Name from fields of the row so each file is easy to recognise later.
- 05
Test, then publish
Test the MergeMole step and read what came back before going on. When the result looks right, click Publish to switch the Zap on.
The MergeMole action
MergeMole gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create PDF
ActionIn Zapier“Creates a PDF based on your MergeMole template ID”
Fills a MergeMole template with the data your trigger brought in and asks MergeMole to produce the PDF. You choose the template and give the output a name, which you can build from fields of the earlier step.
When a MergeMole Zap breaks
Zapier lists no help article for MergeMole, and no app-specific limit has been recorded. What can go wrong comes from how Zaps work in general.
Here are four general situations to know. None of them is a bug in MergeMole; they come from the trigger side and from Zapier's own rules, so check those first when a document is missing.
Old records are not processed
A Zap only reacts to what happens after you switch it on. Rows that existed before are never turned into PDFs; producing those is a separate job.A Zap that triggers itself
As a general precaution, a Zap that writes into the very place its trigger watches can set itself off again and again, and burn through your tasks.Bulk imports get held back
When the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of running them all.No duplicates from polling
On a polling trigger, Zapier remembers what it has already seen, so the same row does not start the Zap twice.
Need help automating MergeMole with Zapier?
A person reads every message.
