Resources · Make integration

GoPay Make integrationAutomate GoPay with Make.

Can GoPay payments run themselves once an order or a request lands somewhere else? The GoPay Make integration gives you 14 modules, 13 actions and 1 search, for pre-authorized, recurring and refunded payments. This page shows how to connect the account and build a first working scenario.

Try the GoPay integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GoPay Make integration do for you?

The GoPay Make integration links your GoPay account to Make, a no-code tool where you chain bricks called modules into a scenario, the automation you build. Once linked, Make can hold a customer's funds, charge them, start or stop a recurring payment and refund a customer, all without code.

Refunds without the back office. A customer asks for a refund through a form or a support tool. Get a Payment reads the payment in GoPay so you can check it, then Make a Payment Refund sends the money back. Nobody has to log in to GoPay for a routine case.

Hold now, charge when the order ships. For a shop that only takes money once goods leave the warehouse, Create a Pre-Authorized Payment reserves the amount at checkout. When the shipping tool confirms the parcel, a charge module captures it, in full or in part; if the order is cancelled, a cancel module releases the hold.

Recurring payments driven by your own events. Create a Recurring Payment sets up the recurrence, Make a Recurring Payment on Demand collects the next payment when your system says so, and Cancel a Recurring Payment stops it when a customer leaves.

GoPay has no trigger module in Make: it cannot start a scenario by itself. The scenario opens on another app or on a schedule, and GoPay acts inside it. For anything the listed modules skip, Make an API Call reaches the rest of the GoPay API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison lays out both tools, and our Make review covers the editor in depth. If a module returns an error you do not understand, start with Make troubleshooting.

Connect

How do you connect GoPay to Make?

  1. 01

    Add a GoPay module

    In your scenario, add any GoPay module and click Create a connection. A connection is your GoPay account linked to Make once, then reused by every GoPay module you add later. You can type a label in Connection name if you manage several accounts.

  2. 02

    Paste the client credentials

    Fill Client ID and Client Secret with the client credentials GoPay sent you by SMS. You need an existing GoPay account for this; if you do not have one yet, register through the GoPay registration guide first.

  3. 03

    Save and confirm access

    Click Save. If GoPay asks you to authenticate, sign in and confirm access. The connection now appears in the dropdown of every GoPay module, so you will not repeat these steps for the next ones.

First scenario

Your first scenario with GoPay

GoalWhen a refund request reaches another app, Make reads the GoPay payment and sends the refund.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where refund requests arrive, such as your form or helpdesk tool, and choose its trigger module.

  2. 02

    Add Get a Payment

    Click the + on the right of that first module, search GoPay and choose Get a Payment. Create the connection, then map the payment identifier sent by the first app into the module.

  3. 03

    Add Make a Payment Refund

    Add a third module, GoPay again, this time Make a Payment Refund. Map the payment from the previous module so the refund lands on the right customer payment.

  4. 04

    Test with Run once

    Click Run once and send a test request. Each module shows the bundles it received, a bundle being one item passed along, here one payment. Check them before you let real refunds go out.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. From then on, each new request runs through the same three steps.

Modules

What each GoPay module does

GoPay gives you 14 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Payments

10 modules
GoPay1

List Payment Methods

Search

In Make“Retrieves a list of available payment methods.”

Returns the payment methods available on your GoPay account, so a scenario can know what a customer may pay with before it builds a payment.

When to use it
ahead of a payment module, to show or check the options a checkout form should offer.
Watch out
it is a search, so it can return several bundles; each one counts as its own item for the next module.
GoPay2

Get a Payment

Action

In Make“Retrieves an existing payment.”

Reads one existing payment from GoPay and hands its details to the next module, so you can decide what happens next based on where that payment stands.

When to use it
before a refund or a charge, to confirm you act on the right payment.
Watch out
it only reads; nothing changes in GoPay until an action module follows it.
GoPay3

Create a Pre-Authorized Payment

Action

In Make“Creates a new pre-authorized payment.”

Reserves an amount from the customer without taking it yet. You get breathing room: the money is held, and you capture it once the order is really ready.

When to use it
for goods made to order or items shipped later, where charging at checkout would be premature.
Watch out
a hold is not a payment; plan a charge or cancel module later in the flow, or the funds stay blocked.
GoPay4

Charge of Pre-Authorized Payment

ActionIn the docs only

Captures the full amount that a pre-authorized payment is holding. This is the version listed in the Payments group of the GoPay documentation, where it comes without an official description.

When to use it
when the shipping or fulfilment step confirms that the whole order went out.
Watch out
Make also lists Charge of Pre-Authorization Payment, a near twin; run both once on a test payment before you settle on one.
GoPay5

Partial Charge of Pre-Authorized Payment

ActionIn the docs only

Takes only part of the held amount, which fits orders that shrink between checkout and delivery. The documentation lists it under Payments without describing it.

When to use it
one item of a basket turns out to be out of stock, and you charge only what actually ships.
Watch out
a near twin sits outside the groups under the name Partial Charge of Pre-Authorization Payment; test both on a sample before choosing.
GoPay6

Cancel a Pre-Authorized Payment

ActionIn the docs only

Releases a hold so the customer gets back access to the reserved funds. The GoPay documentation shows it in the Payments group, with no official description attached.

When to use it
the order is cancelled in your shop before anything was charged.
Watch out
Cancel a Pre-Authorization Payment does a similar job under a slightly different name; confirm which one your editor offers.
GoPay7

Create a Recurring Payment

Action

In Make“Creates a new recurring payment.”

Sets up a payment that can repeat, the starting point for subscriptions or instalments handled through GoPay rather than by hand.

When to use it
a customer signs up for a plan in your app or CRM and the first payment needs to open the recurrence.
Watch out
choose the mode here; Make a Recurring Payment on Demand only accepts recurrences created in ON_DEMAND mode.
GoPay8

Make a Recurring Payment on Demand

Action

In Make“Allows you to recur the payment based on previously established recurring payment "ON_DEMAND" mode.”

Collects the next payment of a recurrence created in the on-demand mode, at the moment your own process decides it is due.

When to use it
usage-based billing, where another app records the consumption and tells Make when to charge.
Watch out
it only works on a recurring payment that was set up in ON_DEMAND mode; any other recurrence will not accept it.
GoPay9

Cancel a Recurring Payment

Action

In Make“Cancels recurrence of previously created payment.”

Stops the recurrence of a payment you created earlier, so the customer is not charged again after leaving.

When to use it
a cancellation form is submitted, or a CRM record switches to churned, and billing has to end with it.
Watch out
it ends future charges; payments already made stay as they are and need Make a Payment Refund if money must go back.
GoPay10

Make a Payment Refund

Action

In Make“Allows recovering funds for already made payment to the customer.”

Sends money back to the customer for a payment that already went through. Support can close a refund request without opening GoPay.

When to use it
after a return is accepted in your shop or a ticket is approved in your helpdesk.
Watch out
money leaves your account for real; place Get a Payment before it and test with Run once on a sample.

Other

1 module
GoPay11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the GoPay API with the connection you already have, which fills the gap when none of the listed modules covers what you need.

When to use it
a GoPay feature appears in their API but has no dedicated module in Make.
Watch out
you write the request yourself, so keep the GoPay API reference open next to the editor.

Other modules

3 modules
GoPay12

Cancel a Pre-Authorization Payment

Action

In Make“Cancels previously created​ pre-authorized payment.”

Cancels a pre-authorized payment created earlier and frees the held funds. This one appears outside the documentation groups and carries an official description.

When to use it
a customer withdraws a booking or a quote before the capture happens.
Watch out
it shares its purpose with Cancel a Pre-Authorized Payment; keep one of the two across your scenarios to avoid confusion later.
GoPay13

Charge of Pre-Authorization Payment

Action

In Make“Enables charging of pre-authorized funds previously created by pre-authorized payment.”

Charges the funds a pre-authorized payment reserved earlier, turning the hold into a real payment. It sits outside the documentation groups, next to its near twin.

When to use it
a service is delivered in full and the final invoice matches the held amount.
Watch out
the Payments group lists Charge of Pre-Authorized Payment for the same idea; pick one and stay consistent.
GoPay14

Partial Charge of Pre-Authorization Payment

Action

In Make“Enables partial charging of pre-authorized funds previously created by pre-authorized payment.”

Captures only a portion of the pre-authorized funds, leaving the rest uncharged. It fits jobs whose final price ends up lower than the estimate.

When to use it
a rental or repair was held at an estimate and the final bill comes in below it.
Watch out
its twin in the Payments group is Partial Charge of Pre-Authorized Payment; run each once on a test hold before choosing.
Need help

Need help automating GoPay with Make?

A person reads every message.

FAQ

GoPay and Make: common questions

01Is the GoPay Make integration free?
Yes. GoPay is a standard app in Make, so its modules work on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, one operation being one module run on one bundle. GoPay's own fees are a separate matter between you and GoPay.
02What do you need to connect GoPay to Make?
A GoPay account and the client credentials GoPay sends by SMS. In any GoPay module, click Create a connection, optionally name it, paste the Client ID and Client Secret, then click Save. If GoPay asks you to authenticate, sign in and confirm access. Without an account, register with GoPay first through its registration guide. The connection is then shared by every GoPay module in all your scenarios, so this setup happens once per account.
03Can GoPay start a Make scenario instantly?
No. GoPay has no trigger module in Make, so it never starts a scenario by itself. You open the scenario with another app's trigger, such as a form, a shop or a helpdesk, or with Make's own schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans. GoPay modules then run as actions inside that flow, reading payments, charging holds or sending refunds.
04What if the GoPay module you need is missing?
Use Make an API Call. It reaches any endpoint of the GoPay API with the same connection, so features without a dedicated module stay within reach. You will need the GoPay API reference to write the request. The GoPay documentation in Make gives no numbered limits for these modules. If a feature lies outside GoPay entirely, add a module from another app to the same scenario and pass the data along with mapping.
05Should you use Make or n8n for GoPay?
It depends on the tool you already use. Make offers GoPay as 14 native modules, 13 actions and 1 search, plus Make an API Call for the rest, all through a visual editor where each brick is a module. The same app often has an n8n node too. Compare the nodes and modules each side offers for the exact payments you run, pre-authorized, recurring or refunds, and pick the tool your team already builds in.
Same platform

Other docs you might need on this stack.

Browse all integrations