Resources · Make integration

Mollie Make integrationAutomate Mollie with Make.

Payments, refunds and subscriptions can move on their own once Mollie talks to your other tools. The Mollie Make integration gives you 39 modules, two of them triggers. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Mollie integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mollie Make integration do for you?

The Mollie Make integration links your Mollie account to Make, a no-code tool where you chain apps into a scenario, the automation you build. Once linked, Make can read your payments, create payment links, send refunds and manage subscriptions for you, with no code and no copy-paste between tabs.

Get paid faster on accepted quotes. When a deal closes in your CRM, Create a Payment Link produces the link and the next module emails it. Nobody opens the Mollie dashboard.

Keep your books in sync. Get New Payments picks up fresh payments and Watch Balance Transactions follows every movement on your balance, so a spreadsheet or an accounting tool can receive each line. List Invoices and List Settlements help at closing time.

Run memberships without manual steps. Create Customer, Create Mandate and Create Subscription set up a recurring payer, and Revoke Mandate ends it cleanly when someone leaves.

Two limits to know before you start. Both Mollie triggers are scheduled: Make checks Mollie at an interval, there is no instant trigger. And Create Mandate only handles IBANs and PayPal billing agreements; a card mandate needs a first payment by the customer. If you want to learn the editor step by step, the Make training starts from zero, and Make pricing explains how operations are counted.

Mollie may also have a node in n8n, the other popular automation tool; the n8n vs Make comparison lays out the criteria to choose between them.

Connect

How do you connect Mollie to Make?

  1. 01

    Add a Mollie module

    Log in to Make, open your scenario and add any Mollie module, for example Get New Payments. In the module panel, click Create a connection. A connection is your Mollie account linked to Make once, then reused by every Mollie module.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when you run a live account and a test account side by side. Something like Mollie shop or Mollie test is enough to tell them apart later.

  3. 03

    Paste your credentials

    Enter the credentials copied from Mollie: an API key, an organization access token or an OAuth app access token. Then follow the instructions on screen. Your Mollie account must be active for the connection to work.

First scenario

Your first scenario: a payment link for each accepted quote

GoalWhen a quote is accepted in your sales tool, Make creates a Mollie payment link for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where quotes get accepted, such as your CRM, and its module that spots a new deal.

  2. 02

    Add Create a Payment Link

    Click the + on the right of that first module, search for Mollie and choose Create a Payment Link. Select your Mollie connection, or click Create a connection if you have not linked it yet.

  3. 03

    Map the quote data

    Fill the fields of the Mollie module. Instead of typing values, click a field and pick data from the first module, so each accepted quote brings its own details into its own payment link.

  4. 04

    Test with Run once

    Accept a test quote, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check that the link appears in Mollie before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan you can keep two scenarios active at the same time.

Triggers

What can start a Mollie scenario?

2 modules start a scenario when something happens in Mollie. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Mollie as soon as it happens.

Mollie1Get New Payments

Get New Payments

Scheduled trigger

In Make“Retrieves the new payments.”

Brings every new Mollie payment into your scenario, each one as its own bundle (the Make word for one item passing from a module to the next). From there you can log it, notify your team or update a customer file.

How it fires
scheduled. Make checks Mollie on the scenario's schedule, every 15 minutes by default, so a payment appears at the next check, not the second it is made.
When to use it
a small online shop wants each sale copied into its order sheet and announced in the team chat.
Watch out
every module after the trigger runs once per payment, and each run counts as one operation on your Make plan.
Mollie2Watch Balance Transactions

Watch Balance Transactions

Scheduled trigger

In Make“Process balance transactions starting from a specific date and time.”

Follows the movements on your Mollie balance from a date and time you choose, so your bookkeeping sees payments, refunds, chargebacks and settlements as they land on the balance.

How it fires
scheduled. Make checks Mollie on the scenario's schedule and passes along the transactions found since the starting point.
When to use it
an accountant wants every balance line pushed into a ledger sheet instead of exporting it by hand at closing.
Watch out
pick the starting date with care, because an early date sends a long history of transactions through the scenario, and each one costs operations.
Modules

What can Make do in Mollie?

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

Mollie1

Cancel Subscription

Action

In Make“Cancel an existing subscription.”

Stops an existing Mollie subscription, so the customer is no longer charged on that plan. Point the module at the subscription and Make sends the cancellation for you.

When to use it
a member ends their plan in your CRM and the matching Mollie subscription has to stop too.
Watch out
Mollie refuses any update on a canceled subscription, so a customer who comes back needs a fresh one made with Create Subscription.
Mollie2

Create an Order

Action

In Make“Creates a new order.”

Opens a new order in Mollie from data mapped out of an earlier module, such as a cart built in your shop tool. That order then becomes the anchor for shipments and order refunds.

When to use it
your sales start outside Mollie and you want each one recorded there as an order rather than a loose payment.
Watch out
keep the order ID; Get an Order, Create a Shipment and Create an Order Refund all work on a specific order.
Mollie3

Create an Order Refund

Action

In Make“Creates a refund for a specific order.”

Returns money on a specific order, so the refund stays attached to the sale it reverses instead of floating on its own.

When to use it
a return gets approved in your helpdesk and the scenario should refund the order behind it without a trip to the dashboard.
Watch out
when the sale was a plain payment and not an order, reach for Create a Payment Refund instead.
Mollie4

Create a Payment

Action

In Make“Creates a new payment.”

Starts a brand new payment in Mollie from details you set or map in the module, and hands it to the next module in the scenario.

When to use it
a booking made in your scheduling app should turn into a Mollie payment without anyone copying the amount across.
Watch out
if all you need is something to paste into an email or a chat, Create a Payment Link is the simpler pick.
Mollie6

Create a Payment Refund

Action

In Make“Creates a refund for a specific payment.”

Sends back money on one specific payment, so the customer is refunded on the exact charge they made. Make only needs to know which payment you mean.

When to use it
your support team marks a ticket as refund approved and the scenario turns that decision into a Mollie refund.
Watch out
for sales recorded as orders, Create an Order Refund keeps the refund tied to the order.
Mollie7

Create a Shipment

Action

In Make“Creates a new shipment for specific order lines of order.”

Records a shipment on a Mollie order for the order lines you pick, so Mollie can see which items of the order are on their way.

When to use it
your logistics tool marks a parcel as sent and the matching lines should be flagged in Mollie at the same moment.
Watch out
it acts on the lines of an order, so the scenario must carry an order ID from Create an Order or List Orders.
Mollie8

Create Customer

Action

In Make“Creates a simple minimal representation of a customer.”

Adds a customer record to Mollie with a minimal set of details. Mandates and subscriptions are then created for that customer.

When to use it
someone signs up through your form tool and should exist in Mollie before their first recurring charge.
Watch out
the module creates a new record every run, so check with List Customers first when the same person might already be there.
Mollie9

Create Mandate

Action

In Make“Create a mandate for a specific customer. Mandates allow you to charge a customer's card, PayPal account or bank account recurrently. It is only possible to create mandates for IBANs and PayPal billing agreements with this module. To create mandates for cards, your customers need to perform a 'first payment' with their card.”

Gives Mollie the right to charge a customer again and again on their bank account or PayPal account, which is what subscriptions and repeat payments rely on.

When to use it
a new gym member hands over an IBAN at sign-up and you want direct debit ready before the first charge.
Watch out
this module only creates mandates for IBANs and PayPal billing agreements; for a card, the customer has to make a first payment with it.
Mollie10

Create Subscription

Action

In Make“With subscriptions, you can schedule recurring payments to take place at regular intervals. Please see the API Docs for examples: https://docs.mollie.com/reference/create-subscription.”

Schedules recurring payments for a customer at a regular interval, so a membership or a retainer is collected without a new request each time.

When to use it
a coaching client signs a retainer and the payment plan should start as soon as the contract is marked signed.
Watch out
the customer must be chargeable again, through Create Mandate for IBAN or PayPal, or a first card payment.
Mollie11

Get an Order

Action

In Make“Retrieves a specific order by its ID.”

Fetches one order by its ID and passes its details to the rest of the scenario, straight from Mollie rather than from an old copy.

When to use it
a customer asks your support desk where their order stands and the reply should quote what Mollie holds.
Watch out
without the ID, begin with List Orders, which can return zero, one or several orders.
Mollie12

Get a Payment

Action

In Make“Retrieves a specific payment by its payment token.”

Reads a single payment from its payment token, so the scenario can check where things stand before it sends a receipt or opens access.

When to use it
your course platform stored the payment token at checkout and needs the latest Mollie data before unlocking a lesson.
Watch out
the module expects that token; if you only know the customer, look through List Payments.
Mollie14

Get a Payment Refund

Action

In Make“Retrieves a specific payment refund by its ID and the payment ID.”

Retrieves one refund using two references at once: the refund ID and the ID of the payment it belongs to. You get the refund's details for the next module.

When to use it
a customer writes in about a refund and your helpdesk wants the Mollie record pasted into the ticket.
Watch out
both IDs are required; List Payment Refunds shows the refunds of a payment when you lack one.
Mollie15

Get a Settlement

Action

In Make“Retrieves a specific settlement by its ID.”

Pulls one Mollie settlement by its ID, so its details can travel to your accounting sheet or your finance channel.

When to use it
a bookkeeper matches a bank line with Mollie and wants the full settlement record next to it.
Watch out
to find the ID first, run List Settlements, which returns every settlement, and keep that ID next to the bank line for later runs.
Mollie16

Get Balance

Action

In Make“Retrieves balance by it's ID.”

Reads one of your Mollie balances by its ID and hands its figures to the following modules, for a report or an alert.

When to use it
a finance lead wants the current balance posted to the team chat whenever a large refund goes out.
Watch out
organizations with several balances need the right ID; List balances shows them all, primary one included.
Mollie17

Get Customer

Action

In Make“Retrieve a single customer by its ID.”

Returns a single Mollie customer from its ID, which lets a later module greet, bill or update the right person.

When to use it
a new payment arrives with a customer ID and your CRM needs the full customer record to match it.
Watch out
the module needs the ID; with only a name or email, go through List Customers and pick the right record.
Mollie18

Get Mandate

Action

In Make“Retrieve a single mandate by its ID. Depending on the type of mandate, the object will contain the customer's bank account details, card details, or PayPal account details.”

Reads one mandate by its ID. Depending on its type, the result holds the customer's bank account, card or PayPal details.

When to use it
before a recurring charge, a scenario confirms which payment method the mandate covers.
Watch out
those details are sensitive, so think twice before mapping them into an email, a chat or a shared spreadsheet.
Mollie19

Get Subscription

Action

In Make“Retrieve a single subscription by its ID and the ID of its parent customer.”

Fetches one subscription, which needs its own ID plus the ID of the customer it belongs to, and returns its details.

When to use it
a subscriber asks about their plan and your support flow reads the live subscription before answering.
Watch out
save both IDs in your CRM at the moment Create Subscription runs, so this lookup never has to guess.
Mollie20

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Mollie API with the connection you already set up, which covers whatever the listed modules leave out.

When to use it
you need a Mollie feature no listed module offers and you still want to stay inside Make.
Watch out
you write the request yourself, so keep the Mollie API reference open and test with Run once first.
Mollie21

Revoke Mandate

Action

In Make“Revoke a customer's mandate. You will no longer be able to charge the customer's bank account or card with this mandate, and all connected subscriptions will be canceled.”

Withdraws a customer's mandate, so you can no longer charge their bank account or card with it, and every subscription connected to it is canceled.

When to use it
a member closes their account and all future charges must stop in one move.
Watch out
the canceled subscriptions go with it; check with Get Mandate and Get Subscription that you target the right customer.
Mollie22

Update Customer

Action

In Make“Update an existing customer.”

Changes the details of an existing Mollie customer, so the record there matches what your CRM or member base now says.

When to use it
a client edits their contact details in your portal and Mollie should follow without a manual edit.
Watch out
you need the customer ID; if your CRM does not store it, find it through List Customers first.
Mollie23

Update Subscription

Action

In Make“Update an existing subscription. Canceled subscriptions cannot be updated.”

Edits a running subscription, so a plan change on your side is reflected in what Mollie collects next.

When to use it
a member moves to a bigger plan in your app and the Mollie subscription should change with it.
Watch out
a canceled subscription cannot be updated; check it with Get Subscription first, or create a new subscription.
Mollie24

List all chargebacks

Search

In Make“Retrieve all chargebacks initiated for all your payments.”

Collects every chargeback raised on your payments and sends each one on as a bundle, ready to log or to flag.

When to use it
a risk review needs all disputed payments in one sheet to spot a pattern by product or by customer.
Watch out
the list can be empty or long, and each chargeback triggers the following modules once, which counts as operations.
Mollie25

List balances

Search

In Make“Retrieve all the organization’s balances, including the primary balance, ordered from newest to oldest.”

Returns all the balances of your organization, primary balance included, sorted from newest to oldest.

When to use it
a business with several balances wants one overview in a dashboard or a sheet, each balance on its own row.
Watch out
the newest balance comes first, so do not assume the first bundle is the primary one; pick it by ID with Get Balance if needed.
Mollie26

List Balance Transactions

Search

In Make“With the List balance transactions endpoint you can retrieve a list of all the movements on your balance. This includes payments, refunds, chargebacks, and settlements.”

Lists every movement on your balance: payments, refunds, chargebacks and settlements, one bundle per movement.

When to use it
you rebuild a full ledger once, for an audit or a migration to a new accounting tool.
Watch out
for new movements only, Watch Balance Transactions is the better fit, since this search returns the whole list each time.
Mollie27

List Customers

Search

In Make“Retrieve a list of all customers.”

Returns all your Mollie customers, one bundle each, so the scenario can match, clean or copy them elsewhere.

When to use it
you sync your Mollie customers into a CRM for the first time and want every record in one pass.
Watch out
a large customer base means many bundles and many operations; keep the modules after it as few as possible.
Mollie28

List Invoices

Search

In Make“Retrieve a list of all your invoices, optionally filtered by year or by invoice reference.”

Retrieves the invoices Mollie issued to you, with an optional filter by year or by invoice reference.

When to use it
your accountant asks for the Mollie invoices of a fiscal year, and the scenario files them in a shared folder.
Watch out
use the year or reference filter to keep the run small, rather than pulling every invoice and sorting later.
Mollie29

List Mandates

Search

In Make“Retrieve a list of all mandates.”

Shows the mandates Mollie holds, so you can see who can be charged again and by which method.

When to use it
before launching a new recurring offer, you check which existing customers already have a valid mandate.
Watch out
the search may return nothing; decide what the next steps should do when no mandate is found, before switching the scenario on.
Mollie30

List Order Refunds

Search

In Make“Retrieves a list of all refunds created for a specific order.”

Gathers the refunds created for one specific order, so you see at a glance what has already gone back to the customer.

When to use it
before refunding a return, the scenario checks that the order was not refunded already.
Watch out
it works on a single order ID; for refunds across all sales, List Refunds is the one.
Mollie31

List Orders

Search

In Make“Retrieves all orders.”

Retrieves all your Mollie orders as separate bundles, a good base for reports, exports or a sweep for orders left unshipped.

When to use it
you move your order history into a data warehouse or a sales sheet.
Watch out
every order found runs the later modules once, so keep the chain after this search short.
Mollie33

List Payment Refunds

Search

In Make“Retrieves a list of all refunds created for a specific payment.”

Lists the refunds made on one specific payment, which tells you how much of it has already been returned.

When to use it
a customer claims they were never refunded and support needs the history of that one charge.
Watch out
you need the payment ID; refunds on orders show up in List Order Refunds instead.
Mollie34

List Payments

Search

In Make“Retrieves all payments.”

Pulls every payment from your account, one bundle per payment, for a full export or a one-time sync.

When to use it
you set up a revenue dashboard and need the past payments loaded before new ones stream in.
Watch out
for payments that arrive from now on, Get New Payments avoids reading the whole history on each run.
Mollie35

List Refunds

Search

In Make“Retrieves all refunds.”

Brings back all refunds across your account, whatever payment or order they came from.

When to use it
a margin review needs every refund in one table, sorted by product, with the scenario started by hand through Run once.
Watch out
it returns zero, one or many refunds; test the empty case with Run once so later modules do not fail.
Mollie36

List Settlements

Search

In Make“Retrieves all settlements.”

Returns all your settlements, so finance can line up what Mollie paid out with what reached the bank.

When to use it
a bookkeeper reconciles bank statements and wants each settlement as a row to tick off.
Watch out
to dig into one settlement, pass its ID to Get a Settlement rather than rereading the full list.
Mollie37

List Subscription Payments

Search

In Make“Retrieve all payments of a specific subscription.”

Shows every payment collected on one specific subscription, the easiest way to see how a subscriber has paid over time.

When to use it
a member disputes a charge and support pulls the full payment history of their plan into the ticket.
Watch out
it is scoped to a single subscription, so the scenario needs that subscription's ID first.
Need help

Need help automating Mollie with Make?

A person reads every message.

FAQ

Mollie and Make: common questions

01Is the Mollie Make integration free?
Yes. Mollie is a standard app in Make, so it works on the Free plan. That plan has limits: two active scenarios, at least 15 minutes between two scheduled runs, five minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to one minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your Mollie subscription is a separate matter, handled on Mollie's side.
02What do you need to connect Mollie to Make?
An active Mollie account and one of three credentials: an API key, an organization access token or an OAuth app access token. In Make, add a Mollie module, click Create a connection, give it a name if you like, then paste the credentials. For the OAuth route, create an application in Mollie under More, Developers, Your apps, set the callback URI given in the Make documentation, and copy the Client ID and Client secret it shows.
03Does the Mollie trigger in Make react in real time?
No. Both Mollie triggers, Get New Payments and Watch Balance Transactions, are scheduled. Make checks Mollie on the scenario's schedule, every 15 minutes by default, and at most once every 15 minutes on the Free plan. On a paid plan the interval can go down to one minute. A payment made right after a check is picked up at the next one, which suits bookkeeping and follow-ups but not a live checkout screen.
04What if the Mollie module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Mollie API with the same connection as the other modules, so nothing new needs linking. You write the request yourself, following the Mollie API reference, and test it with Run once before switching the scenario on. The Make documentation for this app also warns that part of its content is AI-generated from Mollie's own documentation, so double-check important details with Mollie.
05Should you pick Make or n8n for Mollie?
It depends on where your other automations already run. In Make, Mollie comes with 39 ready modules: two scheduled triggers, 23 actions and 14 searches, plus Make an API Call for the rest. n8n often offers a node for the same app, so check its catalog for Mollie and compare the operations you actually need. Pick the tool your team already uses and can maintain; a second platform only for payments adds another place to debug.
Same platform

Other docs you might need on this stack.

Browse all integrations