Resources · Make integration

Pagar.me Make integrationAutomate Pagar.me with Make.

Know about every new chargeback without refreshing the Pagar.me dashboard. The Pagar.me Make integration gives you 15 modules: 4 triggers, 5 actions and 6 searches. This guide shows finance and ops teams how to connect the account and run a first scenario.

Try the Pagar.me integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pagar.me Make integration do for you?

The integration lets Make read your Pagar.me account and pass what it finds to your other tools. You build a scenario, which is the automation itself, out of modules: each module is one step, such as watching for new transactions or fetching your balance. No code is involved, only a Pagar.me API key.

A chargeback never sits unnoticed. Watch Chargebacks picks up each new dispute, Get Transaction pulls the payment behind it, and the next module in your scenario posts both to the channel your support team reads.

Your finance sheet follows the money. For a finance lead reconciling payouts, Watch Balance Operations spots each movement on the account balance, and Get Payable or List Transaction Receivables adds the receivable details before a row lands in the sheet.

New buyers reach your CRM. Watch Customers catches every customer created in Pagar.me, and Search Customers lets you line up the existing base against the CRM before a sales rep follows up.

Keep the scope in mind. All four triggers are scheduled, so Make checks Pagar.me on your scenario's clock rather than hearing from it the moment something happens. Apart from Make an API Call, the other modules only read data and none of them creates anything in Pagar.me; for any endpoint they skip, Make an API Call reuses the same connection. The official Make documentation for this app also warns that it was AI-generated from Pagar.me sources, so verify anything critical with Pagar.me directly.

Many apps also have an n8n node, and the n8n vs Make comparison helps you pick a tool. Before you build, the Make pricing page explains how operations are counted, and Make training covers the editor from scratch.

Connect

How do you connect Pagar.me to Make?

  1. 01

    Copy your API key

    In Pagar.me, open your Dashboard, click your account name or profile icon, then Settings and API Keys. Copy the key shown on screen. You need an active Pagar.me account to get one.

  2. 02

    Add a Pagar.me module

    Log in to Make, add any Pagar.me module to your scenario and click Create a connection. A connection is your Pagar.me account linked to Make once, then reused by every Pagar.me module you add later.

  3. 03

    Paste the key and save

    Give the connection a label in Connection name if you run several accounts (the field is optional). Paste the API key you copied, confirm, and Make starts listing what it can read from Pagar.me.

First scenario

Your first scenario with Pagar.me: flag each chargeback

GoalWhen a new chargeback is registered in Pagar.me, Make fetches the disputed transaction so your team sees the full picture.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module. Everything you add from here runs left to right.

  2. 02

    Pick Watch Chargebacks

    Search for Pagar.me, choose Watch Chargebacks and select the connection you created. If it does not exist yet, click Create a connection and paste your API key.

  3. 03

    Add Get Transaction

    Click the + on the right of the trigger and add Get Transaction. Map the transaction the chargeback refers to; Run once shows you what the chargeback bundle carries, so pick it there.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles, the items each module received. Open them to check that the chargeback and its transaction match.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on, each new chargeback reaches Make on the next check.

Triggers

Pagar.me triggers in Make

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

Pagar.me1Watch Balance Operations

Watch Balance Operations

Scheduled trigger

In Make“Triggers when new balance operation occurred in your account balance.”

Starts your scenario each time a new movement appears on your Pagar.me account balance, so every credit or debit can flow into a sheet or an accounting tool without anyone exporting it by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up the operations recorded since the previous check.
When to use it
you want a running ledger of balance movements that your finance lead can reconcile.
Watch out
every balance movement becomes a bundle, and each module after the trigger uses one Make operation per bundle.
Pagar.me2Watch Chargebacks

Watch Chargebacks

Scheduled trigger

In Make“Triggers when new chargeback are registered for your company.”

Hands you every new chargeback registered for your company, one bundle per dispute, so the people who answer disputes hear about it from Make instead of discovering it later in the dashboard.

How it fires
scheduled. Make checks the app on the scenario's schedule, which means a new dispute shows up at the next check, not at the second it opens.
When to use it
your support or risk team needs a ticket or an alert for each dispute.
Watch out
the bundle is about the chargeback; chain Get Transaction if your alert needs the payment details.
Pagar.me3Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when new customers are created.”

Fires on each customer newly created in Pagar.me and passes that customer to the rest of your scenario, which is the simplest way to keep a CRM or mailing list in step with the people who pay you.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the customers added since it last looked.
When to use it
a sales rep should get a new CRM record as soon as Pagar.me holds a new customer.
Watch out
it only sees new customers, so an edit to an existing one will not start the scenario.
Pagar.me4Watch Transactions

Watch Transactions

Scheduled trigger

In Make“Triggers when new transaction are created.”

Brings each newly created transaction into Make, which gives you a starting point for receipts, order updates or a sales log that fills itself instead of waiting on a manual export from Pagar.me.

How it fires
scheduled. Make checks the app on the scenario's schedule, so transactions arrive in batches at each check.
When to use it
an online shop wants every payment copied into its order sheet or reporting tool.
Watch out
on a busy store this trigger can return many bundles per check, and every module after it runs once per bundle.
Modules

Every Pagar.me module in Make

Pagar.me gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pagar.me1

Get Balance

Action

In Make“Returns the balance of your account or a specified recipient.”

Tells you how much money sits in your Pagar.me account, or in the account of a recipient you name, at the moment the scenario runs. It is one figure you can drop into a report or a message.

When to use it
after a large payout lands, your finance channel gets the current balance posted automatically.
Watch out
it gives the total, not the movements; use Search Balance Operations to see what changed.
Pagar.me2

Get Balance Operation

Action

In Make“Returns a specific operation that occurred on your account balance.”

Opens one specific operation from your account balance so you can read its full detail. Picture a single line of a bank statement, expanded into everything Pagar.me knows about it.

When to use it
after Watch Balance Operations, when a following module needs more detail on the movement that just arrived.
Watch out
it works on one operation you point it to; for a batch, reach for Search Balance Operations.
Pagar.me3

Get Payable

Action

In Make“Returns a specific payable movement.”

Fetches one payable movement, the money Pagar.me will settle to you for a sale, so your books show what is still expected rather than just what was charged.

When to use it
a controller wants the expected payout next to each sale in the finance sheet.
Watch out
it reads a single payable; to get all receivables of one transaction, List Transaction Receivables is the better fit.
Pagar.me4

Get Transaction

Action

In Make“Returns a specific transaction information.”

Pulls the full record of one transaction into your scenario. It is the module you chain after a chargeback or a balance movement to see which payment it concerns.

When to use it
a dispute alert should show the original payment next to the chargeback.
Watch out
map the transaction reference from the previous module; typing a fixed one returns the same payment on every run.
Pagar.me5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Covers whatever the listed modules skip. With the same connection, this module calls any endpoint of the Pagar.me API and returns the answer as a bundle you can map downstream.

When to use it
you need a Pagar.me feature that none of the other modules exposes.
Watch out
you describe the request yourself, so keep the Pagar.me API reference open while you set it up.
Pagar.me6

List Recipients

Search

In Make“Searches for recipients created by your company.”

Returns the recipients your company has created in Pagar.me, one bundle each. Marketplaces that split payments between sellers get a clean list to sync or audit.

When to use it
you want every seller account copied into a sheet, then checked with Get Balance.
Watch out
a search can return zero, one or many bundles, and each bundle runs the next modules once.
Pagar.me7

List Transaction Receivables

Search

In Make“Searches for transaction payment information.”

Lists the receivables tied to one transaction, meaning the pieces of that payment Pagar.me will settle. Installment sales and split payments become readable line by line.

When to use it
after Watch Transactions, to log when and how each sale will be paid out.
Watch out
it needs a transaction to look at, so map one from the module before it rather than typing a fixed value.
Pagar.me8

Search Balance Operations

Search

In Make“List all the operations that occurred on your account balance.”

Brings back the operations recorded on your account balance, which lets you rebuild the movement history in a spreadsheet when you did not have a trigger running.

When to use it
you are setting up reconciliation and want past movements before Watch Balance Operations takes over.
Watch out
the result can be long, and every operation found becomes a bundle that the next modules process.
Pagar.me9

Search Chargebacks

Search

In Make“List all chargebacks that occur on your account.”

Gathers the chargebacks on your account in one pass, handy when a risk manager wants a full picture of disputes rather than an alert for each new one.

When to use it
building a dispute review sheet, or catching up on chargebacks opened before your scenario existed.
Watch out
for new disputes only, Watch Chargebacks is lighter on operations than repeating this search.
Pagar.me10

Search Customers

Search

In Make“List all registered customers.”

Looks through the customers registered in Pagar.me, so a scenario can compare them with your CRM and spot who is missing on either side.

When to use it
you are cleaning up a CRM and want the Pagar.me customer list next to it.
Watch out
if nothing matches, the search returns no bundle and the following modules simply do not run for that buyer.
Pagar.me11

Search Transactions

Search

In Make“List all transactions that occurred on your account.”

Returns the transactions that occurred on your account, which is the module for sales reports or for filling a dashboard with past payments in bulk.

When to use it
you are loading history into a new reporting tool and Watch Transactions only covers what comes next.
Watch out
each transaction found costs an operation downstream, so check the bundle count in Run once before you schedule it.
Need help

Need help automating Pagar.me with Make?

A person reads every message.

FAQ

Pagar.me and Make: common questions

01Is the Pagar.me Make integration free?
Yes, Pagar.me is a standard app, so it works on the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the minimum interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle. Your Pagar.me subscription is separate and billed by Pagar.me.
02What do you need to connect Pagar.me to Make?
You need an active Pagar.me account and its API key. In Pagar.me, go to the Dashboard, click your account name or profile icon, open Settings, then API Keys, and copy the key. In Make, add any Pagar.me module, click Create a connection, optionally name it, and paste the key. That single connection then serves all 15 Pagar.me modules, so you only do this once per account. Name it clearly if you manage more than one account.
03Do Pagar.me triggers in Make fire instantly?
No. All 4 Pagar.me triggers are scheduled: Make checks Pagar.me on the scenario's schedule and collects what appeared since the last check. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval you can set; paid plans go down to 1 minute. If you need a faster reaction, a shorter schedule on a paid plan is the only documented lever.
04What if a Pagar.me module is missing in Make?
Use Make an API Call. It reuses your Pagar.me connection and can reach any endpoint of the Pagar.me API, so a feature absent from the other modules is still within reach. You write the request yourself with the Pagar.me API reference at hand. Keep in mind that the Make documentation for this app says it was AI-generated from Pagar.me sources and may contain mistakes, so confirm details with Pagar.me when they matter.
05Should you use Make or n8n for Pagar.me?
It depends on where the rest of your automations live. On the Make side, Pagar.me brings 15 modules, runs on the Free plan, and Make an API Call covers the endpoints the list leaves out. Many apps also have an n8n node, so check whether one exists for Pagar.me and which operations it offers before you decide. If your team already builds in Make, staying there keeps every scenario and connection in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations