Resources · Make integration

MangoPay Make integrationAutomate MangoPay with Make.

Can Make open MangoPay users and wallets for you? Yes. The MangoPay Make integration gives you 13 modules: one instant trigger, ten actions and two searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the MangoPay integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the MangoPay Make integration do?

The MangoPay Make integration links your MangoPay account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. Once linked, Make can create users and wallets, read them back and react to MangoPay events without a line of code.

A payment account ready at signup. A marketplace can take a new seller from its signup form, run Create a Natural User, then Create a Wallet for that user. Add Create a Bank Account when the seller gives an IBAN, a US, CA or GB account, or one of the OTHER type.

A reaction the moment something happens. Watch Events is an instant trigger: MangoPay calls Make through a webhook as soon as the event occurs, so the next modules run without waiting for a schedule.

A quick lookup for support. Get a Wallet, Get a User or List Wallets pull the current record, which helps a support team answer a seller without opening the MangoPay dashboard.

Anything the listed modules do not cover goes through Make an API Call, which reuses the same connection. The MangoPay docs in Make also carry a warning: the page is AI-generated from the official documentation, so check anything critical with MangoPay. For a wider view of the tool, read the Make review, and if you are weighing both platforms, the n8n vs Make comparison sets out the criteria. A team that prefers to delegate the build can talk to the Make agency.

Connect

How do you connect MangoPay to Make?

  1. 01

    Copy your Client ID and API key

    In the MangoPay dashboard, open the Developers section, click API accounts and choose Sandbox or Production. Copy the Client ID and the API key shown on screen. You need an active MangoPay account for this.

  2. 02

    Open the connection window in Make

    Add any MangoPay module to your scenario and click Create a connection. A connection is your MangoPay account linked to Make once, then reused by every MangoPay module. The Connection name field is optional but helps tell Sandbox from Production.

  3. 03

    Paste the credentials and save

    Enter the Client ID and API key you copied, or follow the on-screen instructions. If MangoPay asks for a callback URI during setup, use https://www.integromat.com/oauth/cb/mangopay. Make then lists what it can read from your account.

First scenario

Your first scenario with MangoPay

GoalWhen a new seller signs up in another app, Make creates a MangoPay natural user and a wallet for them.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where sellers sign up, such as your form tool or your CRM.

  2. 02

    Add Create a Natural User

    Click the + on the right of the first module, search for MangoPay and choose Create a Natural User. Select your connection, then map the seller's details from the previous module into the fields.

  3. 03

    Chain Create a Wallet

    Add Create a Wallet after it. Map the user ID returned by the previous module, so each new wallet belongs to the person that was just created and not to someone else.

  4. 04

    Test with Run once

    Click Run once and submit a test signup, ideally with a Sandbox connection. Open each module to read the bundle it received, a bundle being one item passed from module to module.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

Which MangoPay trigger starts a scenario?

1 module starts a scenario when something happens in MangoPay. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by MangoPay as soon as it happens.

MangoPay1Watch Events

Watch Events

Instant trigger

In Make“Triggers when an specified event occurs.”

Watch Events starts your scenario when a chosen MangoPay event takes place, so the rest of the flow runs on real activity instead of on a timer.

How it fires
instant: the app calls Make through a webhook as soon as it happens. The lightning badge on the module marks it.
When to use it
you want Make to react to a MangoPay event, then pass what it received to another tool, such as your helpdesk or a spreadsheet.
Watch out
the setup starts with Create a webhook, then Create a connection. Test it with Run once while you trigger the event in Sandbox, otherwise nothing reaches Make.
Modules

What can the MangoPay modules do in Make?

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

MangoPay1

Create a Bank Account

Action

In Make“Creates one of the selected bank accounts (IBAN, US, CA, GB or OTHER).”

Attach a bank account to a MangoPay user straight from your scenario, without typing the details again in the dashboard. You pick the account type: IBAN, US, CA, GB or OTHER.

When to use it
right after a seller gives banking details in your onboarding form, chained behind the module that created the user.
Watch out
pick the type that matches the account the seller actually gave you, and map the user ID from the step that created that user.
MangoPay2

Create a Natural User

Action

In Make“Creates a natural user.”

Opens a MangoPay user for a private person from data your scenario already holds, with no manual entry in the dashboard.

When to use it
it is usually the first MangoPay step of an onboarding flow, since wallets and bank accounts hang off a user.
Watch out
run it once per person. A scenario that fires twice for the same signup will create two users, so check with List Users first if duplicates worry you.
MangoPay3

Create a Wallet

Action

In Make“Creates a new wallet.”

Gives a MangoPay user a brand new wallet, created from inside the scenario rather than by hand.

When to use it
straight after Create a Natural User, mapping the user ID it returns, so every new seller gets a wallet at signup.
Watch out
map the owner from the previous bundle, not a fixed value, or every wallet will land on the same user.
MangoPay4

Deactivate a Card

Action

In Make“Deactivates a card by ID.”

Switches off a card saved on MangoPay, using its ID, so it can no longer be used on your platform.

When to use it
when a customer asks to remove a card or closes their account in another tool, and you want MangoPay to follow.
Watch out
the module acts on whatever ID you map. Check the mapping with Run once on Sandbox before pointing it at Production.
MangoPay5

Get a Card Registration

Action

In Make“Retrive information about card registration by ID.”

Reads one card registration by its ID and returns its details as a bundle that later modules can use.

When to use it
when a card setup seems stuck and you want the scenario to check where that registration stands before it notifies your team.
Watch out
the module expects the ID of the card registration itself, so map it from the step that stored it rather than typing it by hand.
MangoPay6

Get a User

Action

In Make“Retrevie information about specific user.”

Fetches a single MangoPay user by ID, so the rest of the scenario works with up-to-date details instead of what an older system stored.

When to use it
after Watch Events, or before an update, when you hold an ID and need the full record.
Watch out
it returns one user only. To browse or find someone without the ID, reach for List Users instead.
MangoPay7

Get a Wallet

Action

In Make“Retrivie information about specific wallet.”

Pulls one wallet by its ID and hands its current details to the next module, so a message or a sheet row shows fresh data.

When to use it
when a support request names a wallet and you want its details pushed to your helpdesk automatically.
Watch out
for all wallets of one user, List Wallets is the better pick; Get a Wallet needs the exact ID.
MangoPay8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the MangoPay API with the connection you already set up, which covers what the twelve other modules leave out.

When to use it
when the MangoPay API offers something that has no dedicated module in the list above.
Watch out
you write the path and body yourself from the MangoPay API reference. Try the call on a Sandbox connection before reusing it on live data.
MangoPay9

Update a Natural User

Action

In Make“Updates a natural user by ID.”

Changes the details of an existing natural user, found by ID, so MangoPay stays in line with your CRM or your own database.

When to use it
when a seller edits their profile elsewhere and the change should reach MangoPay with no copy and paste.
Watch out
the module needs the user's MangoPay ID. Map it from an earlier step, such as Get a User or List Users, rather than typing it.
MangoPay10

Update a Wallet

Action

In Make“Updates a description of the wallet.”

Rewrites the description of a wallet, handy to keep a readable label that your team recognizes at a glance.

When to use it
when a shop is renamed in your back office and the wallet label should follow it.
Watch out
the module is described as changing the wallet description; for anything beyond that, look at Make an API Call.
MangoPay11

List Users

Search

In Make“Retrieves a list of users.”

Returns your MangoPay users as a list, each user becoming its own bundle for the modules that follow.

When to use it
for a sync or an export toward a spreadsheet, or to check whether someone exists before creating them.
Watch out
a search can return zero, one or many bundles, and every later module then runs once per bundle, which adds operations to your plan.
MangoPay12

List Wallets

Search

In Make“Returns a list of wallets for a user.”

Lists the wallets owned by one user, so you can see in a single step everything tied to that account.

When to use it
before creating a wallet, to avoid a second one, or to send a seller a summary of their wallets.
Watch out
it works per user, so map a user ID first; one wallet comes out as one bundle, and each costs operations further down.
Need help

Need help automating MangoPay with Make?

A person reads every message.

FAQ

MangoPay and Make: frequent questions

01Is the MangoPay Make integration free?
Yes, on the Make side. MangoPay is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and lift the active scenario cap. MangoPay itself is a separate subscription, described on its own pricing page, and this page gives no price for it.
02What do you need to connect MangoPay to Make?
An active MangoPay account and two credentials: a Client ID and an API key. You find them in the MangoPay dashboard under Developers, then API accounts, after choosing Sandbox or Production. In Make, add a MangoPay module, click Create a connection, give it a name if you like and paste both values. If a callback URI is requested, the MangoPay docs in Make give the Integromat address to use. Start on Sandbox, it keeps tests away from real money.
03Does the MangoPay trigger in Make work in real time?
Yes. Watch Events is an instant trigger: MangoPay calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for. The module shows a lightning badge in the editor. Setup differs a little from other modules: click Create a webhook first, then Create a connection. The rest of the scenario then runs as soon as the event arrives, with no need to wait for the next scheduled check.
04What if the MangoPay module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the MangoPay API with the connection you already have, so what sits outside the 13 listed modules stays within reach. You will need the MangoPay API reference to write the request. Keep in mind the warning in the Make docs for this app: the content is AI-generated from official documentation, so confirm critical details with MangoPay before you rely on them.
05Should you use Make or n8n for MangoPay?
It depends on how your team works. In Make, MangoPay comes with 13 ready modules, an instant Watch Events trigger and Make an API Call for everything else, all set up in a visual editor. n8n often offers a node for the same apps, so the choice comes down to your criteria: the tool your team already uses and the modules each one offers for MangoPay. The comparison page on this site walks through those criteria without ranking the two.
Same platform

Other docs you might need on this stack.

Browse all integrations