Resources · Make integration

Notifications for Mercado Pago Make integrationAutomate Notifications for Mercado Pago with Make.

Can every accredited Mercado Pago payment start work in your other tools? The Notifications for Mercado Pago Make integration gives you 4 modules: 3 scheduled triggers and 1 API call. This guide links your account and walks you through a first scenario.

Try the Notifications for Mercado Pago integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Notifications for Mercado Pago Make integration do?

The Notifications for Mercado Pago Make integration links your Notifications for Mercado Pago account to Make, so a scenario (the automation you build in Make, a chain of modules) can start when a payment is accredited or a subscription is authorized or cancelled. A module is one brick of that chain, and you build it all without code.

Confirm paid orders. For an online shop, Watch Accredited Payments picks up each accredited payment, and the next module can pass it to your order sheet or your team chat.

Welcome new subscribers. A membership site can rely on Watch Authorized Subscriptions to start its onboarding once a subscription is authorized.

Hear about cancellations. Watch Cancelled Subscriptions gives a support lead the chance to follow up with each customer who leaves. When you need more than these triggers, Make an API Call reaches any endpoint of the app's API with the same connection.

Know the limits before you start: the three triggers are scheduled, so Make looks for news on the scenario's schedule rather than instantly, and the Make documentation for this app says its content is AI-generated and asks you to verify important details with the vendor. The same app may also exist as an n8n node, and the n8n vs Make comparison helps you choose. For plans, see Make pricing; if a run fails, start with Make troubleshooting.

Connect

How do you connect Notifications for Mercado Pago to Make?

  1. 01

    Copy your API key

    Log in to your Notifications for Mercado Pago account, open your profile section and copy the API key shown on screen. You need an active account there first; the app's own pricing page covers the subscription.

  2. 02

    Add a module and create the connection

    In a Make scenario, add any Notifications for Mercado Pago module and click Create a connection. A connection is your account linked to Make once, then reused by every module of this app.

  3. 03

    Paste the key and confirm

    Type a name in Connection name if you want to tell accounts apart; the field is optional. Paste the API key you copied, or follow the on-screen instructions, and confirm to save the connection.

First scenario

Build your first scenario with Notifications for Mercado Pago

GoalWhen Notifications for Mercado Pago reports an accredited payment, Make sends a request to the app's API endpoint you pick.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas to add the first module.

  2. 02

    Add the payment trigger

    Search for Notifications for Mercado Pago, pick Watch Accredited Payments and select your connection, or click Create a connection if this is your first module from the app.

  3. 03

    Add the API call

    Click the + on the right of the trigger and add Make an API Call. Choose the endpoint you need and map values from the payment bundle, the item the trigger hands over.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time; open the bubble above each module to read the bundles it received and check that the request looks right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module. A new scenario runs every 15 minutes by default, which is also the Free plan minimum. Then switch the scenario on so it keeps watching.

Triggers

Triggers: what starts your scenario

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

Notifications for Mercado Pago1Watch Accredited Payments

Watch Accredited Payments

triggerIn the docs only

Accredited payments land in your scenario one by one, each as a bundle (a single item passed to the next module), so you can log the sale or alert whoever ships the order.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so a payment appears at the next check rather than the moment it clears.
When to use it
a shop that prepares an order only once the money is confirmed.
Watch out
the Make doc lists this module without a description and its type comes from its name, so look for the clock badge when you add it.
Notifications for Mercado Pago2Watch Authorized Subscriptions

Watch Authorized Subscriptions

triggerIn the docs only

Here the starting point is a subscription rather than a single charge: each authorized subscription reaches the scenario as its own bundle, ready to feed a welcome email or a member record in another app.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the authorized subscriptions it finds.
When to use it
a paid community or course that opens access once a plan is approved.
Watch out
pick Watch Accredited Payments instead if what you follow is each payment, not the status of the subscription.
Notifications for Mercado Pago3Watch Cancelled Subscriptions

Watch Cancelled Subscriptions

triggerIn the docs only

No cancellation goes unnoticed with this trigger. Each subscription that ends becomes a bundle you can route to a support queue, a spreadsheet of churned accounts or a win-back offer.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the news arrives at the next check, not instantly.
When to use it
a service team that wants to reach out after a customer leaves.
Watch out
every module run on a bundle counts as an operation, the unit Make bills on your plan, so a scenario with many steps per cancellation uses more of your monthly credits.
Modules

Actions: what else Make can do with the app

Notifications for Mercado Pago gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Notifications for Mercado Pago1

Make an API Call

ActionIn the docs only

Make an API Call takes you past the three triggers: it sends a request to any endpoint of the Notifications for Mercado Pago API, using the connection you already set up.

When to use it
your scenario needs something none of the listed modules offers, after a trigger or on its own.
Watch out
you choose the endpoint and its values yourself, so keep the vendor's API documentation open while you fill it in.
Need help

Need help automating Notifications for Mercado Pago with Make?

A person reads every message.

FAQ

Questions about Notifications for Mercado Pago and Make

01Is the Notifications for Mercado Pago Make integration free?
Yes on the Make side: it is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits per month. On the app side, you still need an active Notifications for Mercado Pago account, and its own pricing page covers that subscription.
02What do you need to connect Notifications for Mercado Pago to Make?
An active Notifications for Mercado Pago account and its API key. Log in to the app, open your profile section and copy the key displayed there. In Make, add any module of the app, click Create a connection, give it a name if you like, then paste the key. The connection is saved once and reused by all 4 modules, so you do not repeat the step for each trigger. There is no webhook to create: the doc keeps that step for instant modules, and this app has none.
03Do Notifications for Mercado Pago triggers fire in real time?
No. All 3 triggers are scheduled: Make checks the app on the scenario's schedule instead of waiting for the app to call it. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan, while paid plans can go down to 1 minute. A payment accredited just after a check therefore waits for the next one. If your process needs a faster reaction, a paid plan with a shorter interval is the setting Make gives you to act on.
04What if a Notifications for Mercado Pago module is missing in Make?
Use Make an API Call. It reaches any endpoint of the app's API with the connection you already have, so you are not limited to the three Watch triggers. You choose the endpoint and fill in the request yourself, so keep the vendor documentation at hand. Also note that the Make doc page for this app says its content is AI-generated and may contain mistakes. When something does not match what you see, check with Notifications for Mercado Pago directly before building on it.
05Make or n8n for Notifications for Mercado Pago?
It depends on the tool your team already uses. On Make, this app offers 3 scheduled triggers and an API call module, available from the Free plan, in a visual editor where you test the whole chain with Run once. The same app may also have an n8n node, so check its catalog before you decide. Neither tool is ranked above the other here: compare the modules each side offers for your payment and subscription flows, then build where your team is most at ease.
Same platform

Other docs you might need on this stack.

Browse all integrations