Resources · Make integration

Mamo Make integrationAutomate Mamo with Make.

Can Make react when a Mamo payment goes through or fails? Yes: the Mamo Make integration gives you 9 modules, 5 triggers and 4 actions. This guide is for finance and operations people who already use Mamo, and it walks you from the API key to a working scenario.

Try the Mamo integration on Make See the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Mamo Make integration do for you?

The Mamo Make integration links your Mamo account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger or an action. Mamo events like a payment, a subscription or a new payment link can then start work in your other tools, with no code.

Recover a sale after a declined card. Put Watch Failed Payments first, then Create a New Payment Link, and the customer gets a fresh chance to pay without anyone on your team rebuilding the request by hand.

Keep your books in step with real revenue. Watch Successful Payments hands each confirmed payment to the next module, and Get Transaction Details fetches the full record so your accounting sheet or CRM receives complete data rather than a partial note.

Spot subscription problems early. Watch Failed Subscriptions and Watch Successful Subscription split renewals into two paths: a friendly reminder for the first, a welcome or access update for the second. Send a New Payout covers the outgoing side when money has to leave your account.

Know the limits before you start. All 5 Mamo triggers are scheduled: Make checks Mamo on the scenario's schedule, every 15 minutes by default, so nothing is instant. The Mamo documentation lists the modules without describing them, and there is no Make an API Call module for this app. The Make pricing page explains what each plan allows, the n8n vs Make comparison helps if you hesitate between the two tools, and Make training is there if you want to go further.

Connect

How do you connect your Mamo account to Make?

01
Copy your API key from Mamo
In Mamo, open the developer page from the main dashboard and copy the API key shown there. You need an active Mamo account to reach this page, so set that up first.
02
Add a Mamo module and start the connection
In your Make scenario, add any Mamo module and click Create a connection. A connection is your Mamo account linked to Make once; every Mamo module in your scenarios reuses it afterward.
03
Name it and paste the key
The Connection name field is optional, but a clear name helps when you run a test account and a live one. Paste the API key, or follow the instructions on screen, then save.

First scenario

Build your first Mamo scenario

GoalWhen a payment fails in Mamo, Make creates a new payment link so the customer can try again.

01
Create the scenario
On the Scenarios page, create a new scenario and click the big + to add the first module. That first module decides when everything else runs.
02
Pick Watch Failed Payments
Search for Mamo, choose Watch Failed Payments, then click Create a connection and paste your API key. Make can now read your Mamo account.
03
Add Create a New Payment Link
Click the + on the right of the trigger and pick Create a New Payment Link. Fill its fields by mapping data from the failed payment, which Make shows once the connection works.
04
Test with Run once
Click Run once. Make runs the scenario a single time and shows the bundles each module received; a bundle is one item passing from module to module, here one failed payment.
05
Schedule and switch it on
Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a Mamo scenario?

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

Mamo1Watch Failed Payments

Watch Failed Payments

triggerIn the docs only

Brings every payment that did not go through into your scenario, so a declined card becomes a task instead of a silent loss. Each failed payment arrives as its own bundle, ready for the next module.

How it fires

scheduled, Make checks Mamo on the scenario's schedule, which is every 15 minutes on a new scenario.

When to use it

when your team wants to follow up on unpaid orders, for instance by creating a new payment link or alerting whoever owns the customer.

Watch out

because the check is scheduled, a failed payment reaches Make at the next run, not the moment it fails.

Mamo2Watch Failed Subscriptions

Watch Failed Subscriptions

triggerIn the docs only

Catches recurring charges that failed, which is where churn often starts without anyone noticing. You get one bundle per failed subscription and can decide what happens next.

How it fires

scheduled, Make checks Mamo on the scenario's schedule instead of being called by Mamo.

When to use it

when a subscriber's renewal fails and you want a reminder, a note in your CRM or an alert to customer success before access lapses.

Watch out

keep it apart from one-off payments; Watch Failed Payments covers those, and mixing both in one flow makes filters harder to read.

Mamo3Watch New Payment Links

Watch New Payment Links

triggerIn the docs only

Picks up payment links as they are created in Mamo, whether someone on your team made them by hand or another scenario did. Useful when you need a trace of every request for money you send out.

How it fires

scheduled, Make looks for new links each time the scenario runs.

When to use it

when sales creates links in Mamo and finance wants each one logged in a sheet or shared in a team channel.

Watch out

if a scenario of yours also runs Create a New Payment Link, this trigger sees those links too, so filter them out to avoid a scenario that feeds itself.

Mamo4Watch Successful Payments

Watch Successful Payments

triggerIn the docs only

Turns each confirmed payment into the start of your follow-up work: a receipt, an order update, a row in your accounting sheet. It suits any business that wants paid orders handled the same way every time.

How it fires

scheduled, Make queries Mamo at the rhythm you set on the first module.

When to use it

when a paid invoice should unlock something elsewhere, such as marking the order as paid or granting access to a service.

Watch out

the trigger may not carry every detail you need; add Get Transaction Details after it when the next step requires the full record.

Mamo5Watch Successful Subscription

Watch Successful Subscription

triggerIn the docs only

Signals that a subscription went through, so you can treat recurring customers differently from one-time buyers. Each successful subscription reaches Make as one bundle.

How it fires

scheduled, Make checks Mamo each time the scenario's schedule comes around.

When to use it

when a new or renewed subscriber should get onboarding content, a seat in a tool or a tag in your mailing list.

Watch out

the name is singular in Make, unlike its failed counterpart, so search for the exact wording when you look for it in the module list.

Modules

What can Make do in Mamo?

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

Mamo1

Create a New Payment Link

ActionIn the docs only

Produces a Mamo payment link from inside your scenario, so asking a customer for money no longer means opening Mamo and filling the form yourself.

When to use it

after a failed payment, a signed quote or a form submission, when the next move is to send the customer somewhere to pay.

Watch out

Watch New Payment Links will also see these links, so plan a filter if both sit in your account.

Mamo2

Get Transaction Details

ActionIn the docs only

Fetches the full record of one transaction, which helps when a trigger or another app only gives you part of the story and the next step needs everything.

When to use it

right after Watch Successful Payments, before writing to your accounting sheet, or when a support ticket mentions a payment and you want its details.

Watch out

each call counts as one operation, so skip it when the trigger already carries what you map.

Mamo3

Mamo Base Request

ActionIn the docs only

Listed as an action in the Mamo documentation, with no description. Its name suggests a generic request to Mamo for cases the other modules do not cover, but the documentation does not confirm what it accepts.

When to use it

when none of the named modules does what you need and you are comfortable testing a module step by step.

Watch out

run it with Run once on test data first and read the bundle it returns before trusting it in a live scenario.

Mamo4

Send a New Payout

ActionIn the docs only

Sends money out of your Mamo account from a scenario, which moves payouts from a manual chore to a step that follows your own rules.

When to use it

when a payout should follow a clear event, such as an approved expense or a validated supplier invoice in another tool.

Watch out

money that leaves the account is hard to pull back, so add a filter or an approval step before this module and test with care.

Need help

Need help automating Mamo with Make?

A person reads every message.

FAQ

Mamo and Make: frequent questions

01Is the Mamo Make integration free?

Yes, on the Make side. Mamo is a standard app, available from the Free plan. That plan lets you run 2 active scenarios, with at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations per month. Your Mamo subscription is a separate matter, handled on Mamo's side.

02What do you need to connect Mamo to Make?

An active Mamo account and its API key. In Mamo, go to the developer page from the main dashboard and copy the key shown there. In Make, add any Mamo module, click Create a connection, optionally give it a name, then paste the key. The connection is stored once and every Mamo module in your scenarios reuses it, so you only repeat this step if you want to link a second Mamo account, for example a test one next to your live account.

03Do Mamo triggers in Make work in real time?

No. All 5 Mamo triggers are scheduled, a type read from their names since the documentation gives no detail: Make checks Mamo on the scenario's schedule rather than Mamo calling Make. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans let you go down to 1 minute. For payment follow-ups this is usually fine, but if a customer expects an instant reaction, tell them what delay to expect or run the scenario more often on a paid plan.

04What if a Mamo module is missing in Make?

Start by checking the full list: 5 triggers and 4 actions, including Mamo Base Request, which the documentation lists without describing. There is no Make an API Call module for Mamo, so you cannot fall back on a free-form call the way some apps allow. If what you need is not there, route the data through another app your scenario already uses, or ask the Hack'celeration team to look at your case and suggest a workable path.

05Should you use Make or n8n for Mamo?

It depends on where your other automations already live. This page covers the Make side: 9 Mamo modules, all triggers scheduled, a connection made with one API key. Many apps also have an n8n node, so check n8n's own list for Mamo before choosing. Neither tool is ranked here. Compare which one already hosts your accounting, CRM and messaging flows, since keeping payment scenarios next to them makes maintenance simpler for your team.

Copy your API key from Mamo

Add a Mamo module and start the connection

Name it and paste the key

Create the scenario

Pick Watch Failed Payments

Add Create a New Payment Link

Test with Run once

Schedule and switch it on

Need help automating Mamo with Make?