Resources · Make integration

Easypay Make integrationAutomate Easypay with Make.

What if every paid link could move the rest of your process on its own? The Easypay Make integration gives you 6 modules: one instant trigger, four actions and one search. This page shows finance and ops teams how to connect Easypay and run a first scenario.

Try the Easypay integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Easypay Make integration do for you?

The Easypay Make integration links your Easypay account to Make, a visual tool where you chain modules into a scenario, the automation you build. Easypay then reports payment events to Make and lets it create, extend, read and list Pay by links without a line of code.

Payment links that appear on their own. When an order or a quote is approved in another tool, Create a Pay by link produces the link for it, and the next module can pass it along to the customer or to your records.

Follow-up that starts when money moves. Watch Payment Events wakes your scenario as soon as Easypay reports a payment event, so the billing step, the team alert or the spreadsheet update happens right after it.

More time for late payers. Extend a Pay by link pushes back the expiration date of a link that is about to lapse, and List Pay by links lays out all your links so you can decide which ones to extend.

What Make does not cover here: only 6 modules exist, so anything outside payment links and payment events goes through Make an API Call. The Easypay doc page itself warns that it was written with AI help, so check important details against the Easypay documentation. If you are still choosing a tool, read our Make review and the n8n vs Make comparison; the Make training covers the editor from scratch.

Connect

How do you connect your Easypay account to Make?

  1. 01

    Create your API key in Easypay

    In Easypay, open the Developers section from the configuration menu, then Configuração API 2.0, Chaves and Nova. Name the key, click Salvar, and copy both the API key and the Account ID shown on screen.

  2. 02

    Open the connection window in Make

    Add any Easypay module to your scenario and click Create a connection. A connection is your Easypay account linked to Make once, then reused by every Easypay module. The Connection name field is optional.

  3. 03

    Paste your credentials and save

    Enter the API key and Account ID you copied, or follow the instructions Make shows on screen. Once saved, the module can reach your Easypay account and you can fill in its other fields.

First scenario

Your first scenario: a payment link for every new order

GoalWhen a new order shows up in another app, Make creates an Easypay Pay by link for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It will come from the app where your orders live, such as your shop or your form tool.

  2. 02

    Set up the first module

    Pick that app, connect it, and fill in its fields. Each order it returns becomes a bundle, one item that travels from one module to the next.

  3. 03

    Add Create a Pay by link

    Click the + on the right of the first module, search for Easypay and choose Create a Pay by link. Connect your account, then map the order data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received and check that the link was created in Easypay.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on so each new order gets its link without you.

Triggers

What can start an Easypay scenario?

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

Easypay1Watch Payment Events

Watch Payment Events

Instant trigger

In Make“Triggers when a payment event has occured.”

This trigger starts your scenario the moment Easypay reports a payment event, so whatever comes after a payment no longer waits for someone to check the dashboard. It is the only trigger of the app and the natural first module for any follow-up.

How it fires
instant, Easypay calls Make through a webhook as soon as the event happens, shown by the lightning badge on the module.
When to use it
a customer pays a link and you want the invoice, the thank-you message or the internal alert to follow right away.
Watch out
click Create a webhook before Create a connection, then run the scenario once with a test payment to see what the bundle contains.
Modules

What can Make do in Easypay?

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

Easypay3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Easypay API to your scenario, using the same connection as the other modules. Any endpoint the listed modules do not cover can be called from here.

When to use it
you need an Easypay feature beyond payment links and payment events, and no dedicated module exists for it.
Watch out
you write the request yourself, so keep the Easypay API documentation open while you write it.
Need help

Need help automating Easypay with Make?

A person reads every message.

FAQ

Easypay and Make: common questions

01Is the Easypay Make integration free?
Yes, on the Make side. Easypay is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Paid plans go down to a 1 minute interval with unlimited active scenarios. Make counts usage in operations, one per module per bundle. Your Easypay subscription is separate and handled on the Easypay side.
02What do you need to connect Easypay to Make?
An active Easypay account with API credentials. In Easypay, go to the Developers section of the configuration menu, open Configuração API 2.0, then Chaves and Nova, name the key and save it with Salvar. Copy the API key and the Account ID shown on screen. In Make, add an Easypay module, click Create a connection and paste both values. For the instant trigger, click Create a webhook first, then create the connection as usual.
03Does the Easypay trigger in Make work in real time?
Yes. Watch Payment Events is an instant trigger: Easypay calls Make through a webhook as soon as a payment event happens, and the scenario starts right away instead of waiting for a schedule. The module carries the lightning badge in the editor. Remember to click Create a webhook before creating the connection, then send a test payment and use Run once to see the bundle the trigger receives before you build the rest.
04What if an Easypay action is missing in Make?
Use Make an API Call. It calls any endpoint of the Easypay API with the same connection as the other modules, so you are not limited to the 6 listed ones. It asks for more care, since you build the request yourself from the Easypay API documentation. Also note that the Easypay doc page on Make states it was written with AI help, so verify key details with Easypay directly.
05Should you use Make or n8n for Easypay?
It depends on the tool your team already knows. On Make, Easypay comes with an instant payment trigger, four actions, one search and Make an API Call for the rest. Many apps also have an n8n node, so check whether Easypay has one and which operations it covers before deciding. Pick the tool whose editor your team will maintain with ease, and compare the modules you actually need on each side.
Same platform

Other docs you might need on this stack.

Browse all integrations