Resources · Make integration

Payfunnels Make integrationAutomate Payfunnels with Make.

What happens in your other tools when a Payfunnels payment fails or succeeds? The Payfunnels Make integration offers 10 triggers and 5 modules for payments, refunds and subscriptions. This guide connects your account, then walks you through a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Payfunnels Make integration do for you?

The Payfunnels Make integration links your Payfunnels account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Payfunnels events such as a new customer or a failed payment start the scenario, and Make can then refund a payment, cancel a subscription or list records for you.

Catch failed payments before they turn into churn. Watch Failed Payment starts a scenario each time a charge does not go through. Send the details to your support inbox or your CRM, so someone follows up while the customer still remembers the purchase.

Keep your payment link catalog in order. Watch Created Payment Link, Watch Updated Payment Link and Watch Deleted Payment Link together mirror every change into a shared sheet. Finance always sees which links are live, without logging into Payfunnels.

Handle refunds and cancellations from one request form. A form answer from another app can feed Refund a Payment or Cancel a Subscription, and List Payments helps you check the history first. If you want to see how other form tools plug into Make, the 123FormBuilder Make integration shows the other side of that flow.

The five non-trigger modules do not cover every Payfunnels feature. Make an API Call fills the gap: it reaches any endpoint of the Payfunnels API with the same connection. New to the tool? The Make review covers the basics, and n8n vs Make helps if you are still weighing the two, since the same app often has an n8n node too.

Connect

How do you connect Payfunnels to Make?

  1. 01

    Generate your key in Payfunnels

    In Payfunnels, open Billing in the main dashboard menu, then Integrations and Make Integration. Click Generate and copy the API key and the ID shown on screen. Keep both at hand.

  2. 02

    Add a Payfunnels module in Make

    Log in to Make, open your scenario and add any Payfunnels module. Click Create a connection. A connection is your Payfunnels account linked to Make once, then reused by every Payfunnels module.

  3. 03

    Paste the credentials and save

    Give the connection a name in Connection name if you like (it is optional), then paste the credentials you copied from Payfunnels, or follow the instructions on screen. Save, and Make can now read and act on your account.

First scenario

Your first scenario: cancel a Payfunnels subscription from a request

GoalWhen a customer asks to cancel through a form in another app, Make cancels the matching subscription in Payfunnels.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. This first module is the trigger: here, the form app where cancellation requests land.

  2. 02

    Pick the request trigger

    Search your form app by name, pick its trigger for new answers and create its connection. Make then lists the forms it can read, so you choose the cancellation form from a menu.

  3. 03

    Add Cancel a Subscription

    Click the + on the right of the trigger, search Payfunnels and pick Cancel a Subscription. Select your Payfunnels connection, then map the data from the form answer into the fields Make shows.

  4. 04

    Test with Run once

    Send one test answer through the form, then click Run once. Open each module to read the bundle it received, that is the one item passed along, and check the right subscription was targeted.

  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. Each module run counts as one operation on your Make plan.

Triggers

Which Payfunnels triggers can start a scenario?

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

Payfunnels3Watch Failed Payment

Watch Failed Payment

triggerIn the docs only

A charge that does not go through becomes a task for someone instead of a silent loss. Each failed payment starts the scenario, and you decide who hears about it: support, the account owner, or a follow-up email tool.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
you want a person to contact the customer while the purchase is still fresh.
Watch out
the alert is only as quick as the schedule, so pick an interval your plan allows and that matches how urgent a failed payment is for you.
Payfunnels4Watch First Recurring Payment

Watch First Recurring Payment

triggerIn the docs only

The moment a subscriber pays their first recurring charge, your onboarding can begin. This trigger fires on that first payment only, which makes it a clean signal that a subscription really started.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
you grant access to a course or a member area once the first instalment has cleared, not at signup.
Watch out
later instalments do not start this trigger; use Watch Successful Payment for those.
Payfunnels5Watch New Customer Created

Watch New Customer Created

triggerIn the docs only

Your CRM or mailing list gets every new Payfunnels customer without a manual export. The scenario starts when a customer record is created, so the contact can be added, tagged or welcomed elsewhere.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
your marketing tool needs buyers in a separate segment from newsletter subscribers.
Watch out
a new customer is not the same as a paid order; if you only want paying buyers, start from Watch Successful Payment instead.
Payfunnels6Watch One Time Setup Fee Created

Watch One Time Setup Fee Created

triggerIn the docs only

When a new one-time setup fee appears in Payfunnels, your team hears about it without checking the dashboard. The scenario starts on each fee created, so pricing notes or quotes elsewhere can follow.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
an agency charges onboarding fees and the account managers keep a list of which clients were quoted one.
Watch out
this watches the fee itself, not whether a customer paid it; payments have their own triggers.
Payfunnels7Watch One Time Setup Fee Deleted

Watch One Time Setup Fee Deleted

triggerIn the docs only

A setup fee removed in Payfunnels stops showing up in your internal price list. This trigger starts the scenario on each deletion, which lets you clean the matching line wherever your team keeps its offers.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
you drop an onboarding fee from an offer and do not want sales to keep quoting it.
Watch out
the scenario hears about the deletion after it happened, so record each fee when it is created if you want a trace of it later.
Payfunnels8Watch One Time Setup Fee Updated

Watch One Time Setup Fee Updated

triggerIn the docs only

Edits to an existing setup fee reach your quotes and price sheets on their own. Each update starts the scenario, so the new version replaces the old one in the tools your team reads before talking to a client.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
finance adjusts a fee and the proposal template must reflect it the same day.
Watch out
run a Run once test after an edit to see which details the bundle carries before you map them.
Payfunnels9Watch Successful Payment

Watch Successful Payment

triggerIn the docs only

Every payment that goes through can trigger the next step of the sale: a receipt in your accounting tool, a thank-you message, access to what was bought. It is the natural starting point for anything that follows a sale.

How it fires
scheduled, Make checks the app on the scenario's schedule.
When to use it
an online shop wants each paid order logged in its bookkeeping sheet and the customer tagged as a buyer.
Watch out
each payment is one bundle and every module after it uses operations, so keep the flow short on the Free plan.
Modules

What else can Make do in Payfunnels?

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

Payfunnels1

Cancel a Subscription

ActionIn the docs only

Ends a customer's Payfunnels subscription straight from your scenario, so a cancellation request never waits in an inbox. It acts on one subscription each time it runs.

When to use it
a cancellation form or a support ticket tag should stop billing without anyone opening Payfunnels.
Watch out
nothing in Make undoes a cancellation; test with Run once on a test subscription first.
Payfunnels2

List Payments

SearchIn the docs only

Pulls your Payfunnels payments into the scenario, one bundle per payment, ready to filter, sum or copy into a report. It is a search module, so it can return zero, one or many results.

When to use it
before a refund, to check what a customer actually paid.
Watch out
every payment returned counts as a bundle, and each module after it uses operations for each one.
Payfunnels3

List subscriptions

SearchIn the docs only

Gives you the Payfunnels subscriptions as separate bundles, so you can match a customer to the plan they are on. Handy when a trigger or form brings a name but not the subscription itself.

When to use it
right before Cancel a Subscription, to find which subscription the request is about.
Watch out
a search may return nothing; add a filter so the next module does not run on an empty result.
Payfunnels4

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Payfunnels API from your scenario, using the connection you already created. It covers whatever the other modules on this page do not.

When to use it
you need a Payfunnels action or piece of data that no listed module offers.
Watch out
you work with the raw API here, so keep the Payfunnels API documentation open and check the response with Run once.
Payfunnels5

Refund a Payment

ActionIn the docs only

Sends a refund on a Payfunnels payment from your scenario, which turns an approved request into money back for the customer without manual steps. It works on one payment per run.

When to use it
your support team approves a refund in a helpdesk tool and wants Payfunnels to follow on its own.
Watch out
money leaves your account, so put an approval step or a filter before this module.
Need help

Need help automating Payfunnels with Make?

A person reads every message.

FAQ

Payfunnels and Make: frequent questions

01Is the Payfunnels Make integration free?
Yes, on the Make side. Payfunnels is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month. You still need an active Payfunnels account, which Payfunnels bills on its own terms.
02What do you need to connect Payfunnels to Make?
An active Payfunnels account and its credentials. In Payfunnels, go to Billing, then Integrations, then Make Integration, and click Generate. Copy the API key and the ID that appear. In Make, add a Payfunnels module, click Create a connection, optionally name it, and paste what you copied. The doc also mentions OAuth2 credentials as an option. Once saved, the same connection serves every Payfunnels module in your scenarios, so this is a one-time setup.
03Does the Payfunnels Make integration react in real time?
Not in the strict sense. The Make doc lists the 10 Payfunnels triggers without a type; judging by their Watch names, they are scheduled: Make checks Payfunnels on the scenario's schedule rather than being called the instant something happens. A new scenario checks every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Pick the interval that matches how quickly you need to react, keeping in mind that each check uses operations.
04What if a Payfunnels module is missing in Make?
Use Make an API Call. It is listed for Payfunnels and can reach any endpoint of the Payfunnels API with the connection you already set up, so you are not limited to the 10 triggers, 3 actions and 2 searches. You will need the Payfunnels API documentation to know which endpoint to call. Also note that the Make doc for this app is flagged as AI-generated from Payfunnels material, so check important details with Payfunnels directly.
05Should you use Make or n8n with Payfunnels?
It depends on the tool your scenarios already run on. In Make, Payfunnels offers 15 modules, including a Make an API Call module for anything else, and a connection that takes a key and an ID. The same app often has an n8n node as well, so compare the modules each side lists against the events you need, such as failed payments or refunds. Neither choice changes what Payfunnels itself can do; the question is where your other automations already live.