Resources · Zapier integration

Mollie Zapier integrationAutomate Mollie with Zapier.

The Mollie Zapier integration gives you 7 triggers, 3 actions and 4 searches. Every trigger checks Mollie on a timer, the actions create orders, payments and payment links, and the whole thing runs on the free plan as long as each Zap stays at two steps.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mollie Zapier integration actually does

The Mollie Zapier integration links your Mollie account to the other tools you use, so a payment event in Mollie can start work elsewhere, and work elsewhere can create something in Mollie. You set it up once as a Zap, and it keeps running while it is switched on. No line of code, but a few settings that matter.

Three results people build with it. First, a chargeback alert: New Payment Chargeback spots the disputed payment, Find Payment can look up a payment by its ID if the test shows one in the chargeback, and your team chat gets a message. Second, a refund log for bookkeeping: New Refund adds a row to the sheet your accountant already reads, so nobody exports refunds by hand. Third, a payment request on demand: when a record appears in another tool, Create Payment Link produces a Mollie link you can send on.

Now what Zapier does not do here. None of the seven triggers is instant: Zapier goes and checks Mollie at an interval set by your plan, so a payment never shows up in the Zap the moment it happens. The three actions only create. There is no action to refund, cancel or edit an existing payment or order, and each search starts from an ID you already have.

If you are still choosing a tool, see our Make vs Zapier comparison before you build. And if a Mollie Zap already misfires, open our Zapier troubleshooting page.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: 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, like a new refund in Mollie. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or creates something for you, like a Mollie payment link.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer, Zapier asks for new items. An instant one is reported by the app itself. All Mollie triggers poll.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a Mollie Zap really costs

Mollie is not a premium app on Zapier, so it works on the free plan. What you pay for is tasks, not checks.

  • Free plan100 tasks a month, unlimited Zaps of two steps
  • Premium appNo, Mollie works on the free plan
  • What countsEach successful action, never the trigger

The trigger costs nothing, however often Zapier looks at Mollie. Each action that succeeds counts as one task, and an action that fails is not counted. A Zap with three actions uses three times what a one-action Zap uses, and a few apps and actions take more than one task when they complete. The free plan stops at two steps: add a filter or a Find Payment search and the Zap needs a paid plan. The grid below is how often a polling trigger checks, by plan.

Connect

Connect Mollie to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Mollie account first, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Mollie

    Type Mollie in the search box of the dialog, select it, then click Add connection. A new tab opens on the Mollie side so you can sign in with the account the Zaps will use.

  3. 03

    Grant access

    Sign in to Mollie in that tab and give Zapier access to the account. The connection is then saved once and reused by every Mollie step you add, in any Zap.

First Zap

Your first Mollie Zap: a chargeback alert

GoalWhen Mollie records a chargeback, find the original payment and post both in your team chat.

  1. 01

    Create the Zap

    Start a new Zap and pick Mollie as the app that starts it. This Zap has three steps because of the search, so it needs a paid plan.

  2. 02

    Set the trigger

    Choose New Payment Chargeback as the event, select your Mollie connection, and set Live Mode to match the data you want: test or live.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent chargebacks of the account, so you map the next steps on a real one rather than a blank.

  4. 04

    Add the search

    Add Find Payment as the next step and map a payment ID into it, if the trigger test shows one. Check at the test what the search returns.

  5. 05

    Add the message and publish

    Add your team chat step, place the chargeback and payment details in the message, test it once, then publish the Zap to switch it on.

Triggers

Mollie triggers on Zapier

7 events start a Zap when something happens in Mollie. Zapier checks for them at the interval your plan allows.

1

New Customer

Polling trigger

In Zapier“Triggers when a new customer has been created.”

Starts a Zap each time a customer record is added in Mollie, so the person can exist in your other tools without a second entry.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep a contact list outside Mollie and want every new Mollie customer to land there, or to receive a payment link straight after.
Watch out
the Live Mode setting decides whether Zapier reads test or live data, so a Zap left on test never sees your real customers.
2

New Invoice

Polling trigger

In Zapier“Triggers when a new invoice has been created.”

Picks up invoices as Mollie creates them and passes what each one carries to the next step of the Zap; check at the test which details come through.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
your bookkeeping lives in a sheet and you want a line for each new Mollie invoice without copying it by hand.
Watch out
Zapier remembers what it has already seen, so an invoice does not start the Zap twice, but invoices created before the Zap was published are never picked up.
3

New Order

Polling trigger

In Zapier“Triggers when a new order has been created.”

Reacts to a fresh order in Mollie and passes it to the next step, which makes it the starting point for anything that follows an order.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you want each Mollie order copied into the tool that prepares deliveries, then followed later with Search Shipments.
Watch out
Live Mode is required here too, and test orders and live orders never show up in the same Zap.
4

New Payment

Polling trigger

In Zapier“Triggers when a new payment has been created.”

The broadest trigger of the set: any payment Mollie creates on the connected account sets the Zap off once.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you need a running log of payments in a sheet, or a message to the team for each one. If only some payments matter, add a filter after it (paid plan).
Watch out
the trigger reacts to a payment being created, so check at the test what it carries before you treat it as money received.
5

New Payment Chargeback

Polling trigger

In Zapier“Triggers when a new payment chargeback has been created.”

Fires on each new payment chargeback in Mollie. It is the event you least want to discover late, while going through an export.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
someone has to react to disputes, and you want the alert to reach them without logging in to Mollie to check.
Watch out
set Live Mode to live, otherwise the Zap reads test data, not your live chargebacks.
6

New Refund

Polling trigger

In Zapier“Triggers when a new refund has been created.”

Catches each new refund in Mollie and hands it to the rest of the Zap, one run per refund.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
refunds have to be reflected in your bookkeeping, and a row per refund in a sheet beats rebuilding the list at closing time.
Watch out
Live Mode is required, and a Zap tested on test data has to be switched to live before it reports a real refund.
7

New Settlement

Polling trigger

In Zapier“Triggers when a new settlement has been created.”

Watches for new settlements in Mollie and starts the Zap once for each one it has not seen before.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
whoever keeps the books wants a line for every new Mollie settlement, without opening Mollie to look for it.
Watch out
only settlements created after the Zap is published come through; older settlements stay in Mollie and need a separate export.
Actions

Mollie actions on Zapier

Mollie gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Order

Action

In Zapier“This creates a new order in Mollie.”

Builds a new order in Mollie from data that arrives in the Zap, with the payment profile, the language of the payment page and the address to send the customer back to.

When to use it
the purchase starts in another tool and Mollie only has to collect the money.
Watch out
Test mode is required; leave it on while you test, then turn it off or every order stays a test.
2

Create Payment

Action

In Zapier“This creates a new payment in Mollie.”

Opens a single payment in Mollie from data that arrived earlier in the Zap, with its own description and redirect address.

When to use it
a form or a deal in another tool should produce a Mollie payment with the right description.
Watch out
the description is shown to the customer on their statement when possible, so map a reference they will recognise, not an internal code.
Searches

Mollie searches on Zapier

4 search steps look for data that already exists in Mollie, so a later step can use it.

A search step goes and fetches something that already exists in Mollie, so the next steps can use it. Mollie's searches sit at the bottom of the action-event list, under SEARCH. Three settings decide what happens when the result is not what you expected.

1

Search Customer

Search

In Zapier“This searches for a customer in Mollie.”

Looks up a Mollie customer by its customer ID and returns the record to the following steps.

When to use it
an earlier step carried the customer ID but not the details, and the next action needs them.
Watch out
Test mode is required, so match it to the data the rest of the Zap reads.
2

Search Order

Search

In Zapier“This searches for an order in Mollie.”

Retrieves one order from its order ID, so a Zap that started elsewhere can work with the full Mollie order.

When to use it
a message or a sheet row holds an order ID and you need the order behind it.
Watch out
it needs the exact order ID, not a customer name or an amount; check at the test what comes back.
3

Find Payment

Search

In Zapier“This search for payment by ID”

Finds a payment by its ID. In the chargeback Zap above, it is the step that brings the original payment next to the dispute.

When to use it
a trigger or another app hands you a payment ID and the next step needs what that payment says.
Watch out
unlike the other searches it uses Live Mode, so match it to the data the rest of the Zap reads.
4

Search Shipments

Search

In Zapier“This searches for shipments for an order in Mollie.”

Returns the shipments attached to a Mollie order, from that order's ID.

When to use it
after New Order or Search Order, when you want to know what has already been shipped before telling anyone.
Watch out
several shipments can match one order, so the multiple-results setting above decides whether you get the first one or all of them.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on with empty values.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into a find-or-create. None of the Mollie searches offers this box, so a missing customer or order is never created by the search.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Mollie Zap breaks

Zapier lists no Mollie-specific limit or error for this integration. What goes wrong comes from how Zapier itself works.

Four general cases are worth knowing. None of them shows up while you build: they appear once the Zap is live and real payments start flowing.

  • No backlog

    A Zap only reacts to what happens after it is switched on. Payments, refunds or settlements created before are never picked up; moving them is a separate job.

  • A Zap that sets itself off

    A Zap that writes into the very place its own trigger watches can start itself again and again, and burns through your task count fast. Keep the two apart.

  • Flood protection

    If a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.

  • The same item twice

    Zapier keeps track of what it has already seen on a polling trigger, so the same Mollie item does not start the Zap twice.
Need help

Need help automating Mollie with Zapier?

A person reads every message.

FAQ

Mollie Zapier integration: questions people ask

01Is the Mollie Zapier integration free?
Yes, it works on the free plan, because Zapier does not list Mollie as a premium app. The free plan gives you 100 tasks a month and an unlimited number of Zaps, but each Zap stops at two steps: one trigger and one action. So New Refund to a sheet row is free, while the chargeback alert that adds a Find Payment search in the middle needs a paid plan. Before you build, count the steps of the Zap you have in mind; that count, not the app, decides the plan.
02How many tasks does a Mollie Zap use?
One task per action that succeeds, nothing else. The trigger costs nothing, even though Zapier checks Mollie again and again, and an action that fails is not counted. A Zap that creates a payment link and then sends it by email uses two tasks each time it runs. Searches and filters make the Zap multi-step, which is a plan question rather than a task one. A few apps and actions take more than one task, so check what a real Mollie run costs once the Zap is live.
03Does the Mollie Zapier integration work in real time?
No. All seven Mollie triggers are polling triggers: Zapier asks Mollie for new items at an interval set by your plan, and keeps only what it has not seen yet. That interval is 15 minutes on the free plan, 2 on Professional and 1 on Team and Enterprise. On paid plans you can change how often a trigger checks and run a check by hand from the editor. If a chargeback has to reach someone fast, the plan matters more than the Zap design.
04What do you need to connect Mollie to Zapier?
An account on Mollie, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made from the Apps page of your Zapier account with + Add connection, then you sign in to Mollie in the tab that opens and grant access. It is saved once and reused by every Mollie step afterwards. For the actions, also check that the account has the payment profile you want, since each one asks for a Profile ID.
05Why does a Mollie Zap see no data even though payments are coming in?
Check the mode first. Five of the Mollie triggers ask for Live Mode, which decides whether Zapier reads test or live data, and the actions and most searches ask for Test mode. A Zap built and tested on test data keeps reading test data once published, so real payments never appear in it. Before publishing, open each Mollie step and check which mode it is set to. When you test a trigger, Zapier brings back the three most recent items of the account: look at whether they are test or live ones.
06What if the Mollie operation you need is not in Zapier?
Then this integration cannot do it, and no setting adds it. The Mollie page on Zapier shows the current list of triggers, actions and searches, so check there first. Today the actions only create orders, payments and payment links: nothing refunds, cancels or edits. Sometimes the gap closes another way, for instance a search step that fetches the value an action needs. Otherwise the job stays manual in Mollie, or goes to another automation tool whose Mollie connector does cover it.
07Zapier, Make or n8n for Mollie?
It depends on three things rather than on a winner. First, how many steps your flow needs: Zapier's free plan stops at two, so anything with a search or a filter means a paid plan. Second, how quickly a Mollie event must be handled, since every Mollie trigger on Zapier polls on your plan's interval. Third, which operations you need, since the list of what a connector can do is not the same everywhere. Check what the Mollie connector of Make or n8n offers before choosing, because the available operations differ from one tool to another.
Same platform

Other docs you might need on this stack.

Browse all integrations