Resources · Make integration

Paddle Make integrationAutomate Paddle with Make.

Paddle can run from a Make scenario without a line of code. A scenario is the automation you build in Make. The Paddle Make integration gives you 19 modules: 14 actions and 5 searches on customers, products, prices and reports. Here is how to build your first one.

Try the Paddle integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Paddle Make integration actually cover?

It links your Paddle account to Make so a scenario can read and write your billing data on its own. Make talks to Paddle through 19 modules, and a module is one brick you drop in the scenario: create a customer, fetch a price, pull a report. Nothing here watches Paddle by itself, so a scenario starts on a schedule, Make's own clock, or on another app placed in front.

Three shapes come back over and over. Onboarding a buyer: a signup lands, Create a Customer opens the record in Paddle, Create a Transaction turns it into a billable line. Keeping a catalog straight: List all Products walks your offer, Update a Product fixes what drifted, Create a Price adds the new tier. Getting numbers out: Create a Report asks Paddle for the figures, Get a CSV File for a Report hands back a download link your finance folder can pick up.

What Make will not do for Paddle is react on its own. The app ships no trigger module, the kind of module that watches an app and wakes a scenario up, so nothing on the Paddle side announces that a payment landed. You start the run yourself, from Make's clock or from a trigger sitting in another app, and the Paddle modules work behind it. One more thing worth knowing: Make's help page for Paddle is written by an AI from Paddle's own documentation and can carry mistakes, so anything that touches money gets checked against Paddle itself.

Paddle also exists as a node in n8n, the other automation tool the team works with. Which one fits depends on how much you want to host and script yourself: the n8n vs Make comparison lays out the criteria, and the Paddle n8n integration page covers the same ground on that side. When a scenario stalls halfway, Make troubleshooting collects the usual suspects.

Connect

How do you connect your Paddle account to Make?

  1. 01

    Drop a Paddle module first

    There is no settings screen for this. Log in to Make, put any Paddle module on the canvas, then click Create a connection. A connection is your Paddle account linked to Make once, and every other Paddle module you add later reuses it.

  2. 02

    Name the connection

    The Connection name field is optional, and skipping it costs you later. Write the Paddle account it belongs to: the picker on every module you add next shows this label and nothing else.

  3. 03

    Paste your API key

    Make asks for the credentials that come from the Paddle side. In your Paddle dashboard, open Developer tools, click Authentication, and copy the API key shown there. Paste it back in Make, or follow the on-screen instructions the module gives you, and the connection is live.

First scenario

Your first scenario: a report you can download

GoalWhen the schedule fires, Make asks Paddle for a report and comes back with a CSV link.

  1. 01

    Create the scenario

    From the Scenarios page, start a new scenario and click the + to place the first module. With no Paddle trigger available, Make's own clock is what will start this one.

  2. 02

    Place Create a Report

    Search Paddle by name, pick Create a Report, and choose the connection you just made. This module is the one that asks Paddle to build the figures you are after.

  3. 03

    Add Get a CSV File for a Report

    Click the + on the right of the first module and add Get a CSV File for a Report. In its field, map the report the previous module produced instead of typing anything by hand.

  4. 04

    Run it once

    Click Run once. Each module shows the bundles it received, a bundle being one item that travels from a module to the next, so you watch the report go in and the link come out.

  5. 05

    Set the clock and switch it on

    Open Scheduling on the first module, pick the interval that matches how fresh you need the figures, then flip the scenario on. A new scenario runs every 15 minutes until you change it.

Modules

What each Paddle module does

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

Paddle1

Create a Customer

Action

In Make“Creates a new customer.”

Opens a new customer record in Paddle from data your scenario already holds, so the buyer exists before any money moves.

When to use it
a free trial turns paid and you want the billing side ready without anyone retyping the details.
Watch out
the module creates, it does not check first. Run List all Customers ahead of it when duplicates would hurt.
Paddle2

Create a Price

Action

In Make“Creates a new price.”

Adds a price to your Paddle catalog, the amount a buyer actually gets charged for one of your products.

When to use it
you open an annual tier and it has to be live in Paddle without anyone touching the dashboard.
Watch out
a price hangs off a product, so the product has to exist first. Chain it after Create a Product or after a lookup.
Paddle3

Create a Product

Action

In Make“Creates a new product.”

Registers a new product in Paddle, the thing you sell, before any price gets attached to it.

When to use it
your team ships an add-on and the catalog has to follow the same day, straight from your own tooling.
Watch out
nothing stops you creating the same product twice. Two passes of the same scenario leave you two entries.
Paddle4

Create a Report

Action

In Make“Creates a new report.”

Asks Paddle to build a report, which is how figures leave the platform instead of staying on a screen someone has to read.

When to use it
the month closes and accounting would rather receive the numbers than go and fetch them.
Watch out
building the report and getting the file are two separate modules. This one only starts the job.
Paddle5

Create a Transaction

Action

In Make“Creates a new transaction.”

Records a transaction in Paddle, the billable line that ties a customer to what they bought.

When to use it
a deal closes in your CRM and billing has to reflect the sale without a second entry by hand.
Watch out
money is involved. Test on one line with Run once and read what Paddle sends back before you let the scenario loop.
Paddle6

Get a CSV File for a Report

Action

In Make“Returns a link to a CSV file for a report.”

Hands back a link to the CSV file of a report you already created, which is the thing you forward or store.

When to use it
the figures have to land in a shared drive or an email, in a format a spreadsheet opens without a fight.
Watch out
it needs a report that exists. Pair it with Create a Report, or with a lookup of one made earlier.
Paddle7

Get a Customer

Action

In Make“Retrieves a customer by its ID”

Pulls one customer back from Paddle using its ID, so the rest of the scenario works on real data rather than a guess.

When to use it
a support ticket arrives with an account reference and you want the Paddle side of the story attached to it.
Watch out
one ID in, one customer out. To start from a name or a filter, go through List all Customers.
Paddle8

Get an Auth Token

Action

In Make“Generate an authentication token for a customer”

Produces an authentication token tied to one customer, the credential a page uses to act on that customer's behalf.

When to use it
your app opens a billing screen for a logged-in user and needs that token before the screen loads.
Watch out
a token is a key. Keep it inside the scenario, never in a log line or a team message on the way through.
Paddle9

Get a Price

Action

In Make“Retrieves a price by its ID”

Reads one price by its ID and brings the detail into the scenario, where another module can act on it.

When to use it
a quote gets assembled automatically and the amount has to come from Paddle, not from a value frozen in a spreadsheet.
Watch out
reading is all it does. The app lists an update module for products only, so a price change goes through Paddle or through Make an API Call.
Paddle10

Get a Product

Action

In Make“Retrieves a product by its ID”

Fetches one product from Paddle by its ID and drops its detail into the scenario for the next module to use.

When to use it
a sales page gets generated and the wording has to match what Paddle holds, not a copy that drifted months ago.
Watch out
without the ID at hand, start from List all Products and pick the right one there.
Paddle11

Get a Report

Action

In Make“Retrieves a report by its ID”

Retrieves a report you already asked Paddle to build, by its ID, so the scenario can come back and check on it.

When to use it
an earlier run created a report and a second scenario picks the thread back up.
Watch out
it returns the report, not the file. The download link comes from Get a CSV File for a Report.
Paddle12

List Credit Balances for a Customer

Action

In Make“Returns a list of credit balances for each currency for a customer.”

Returns the credit sitting on one customer's account, currency by currency, in a single pass.

When to use it
a refund or a goodwill gesture is on the table and someone needs to know what credit is already there.
Watch out
several currencies mean several items coming out. The next module runs once per item unless you group them first.
Paddle13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends a request of your own to the Paddle API through the same connection, which covers whatever the listed modules leave out.

When to use it
what you need sits somewhere in Paddle's API but not in the list above, and you would rather stay inside the scenario.
Watch out
you are handling the raw API, so the errors are yours. Keep Paddle's own reference open while you build the call.
Paddle14

Update a Product

Action

In Make“Updates a product using its ID.”

Changes a product already in Paddle, found by its ID, instead of creating a second one next to it.

When to use it
a wording change or a catalog cleanup has to reach Paddle without anyone retyping it there.
Watch out
an update writes over what was there. Read the product first with Get a Product when you want a trace of the old value.
Paddle15

List all Customers

Search

In Make“Returns a paginated list of customers”

Walks through your customers page by page and sends each one down the scenario as a separate item.

When to use it
a sync with your CRM, or a mailing list that has to match the people who actually pay you.
Watch out
a search can come back with nothing, with one, or with a long run of customers. Cap the volume while you test, or a single run eats through your operations, the tally Make keeps of every module execution.
Paddle16

List all Prices

Search

In Make“Returns a paginated list of prices”

Runs through the prices in your catalog, page after page, one item per price.

When to use it
you want to see what is really live before a pricing change, or feed a comparison table on your own site.
Watch out
the internal key behind this module still says discounts while what comes out is prices. Do not go hunting for a discount list here.
Paddle17

List all Products

Search

In Make“Returns a paginated list of products”

Pages through your product catalog and pushes each product forward as an item of its own.

When to use it
a bulk edit is coming and you would rather the scenario walked the catalog than you scrolling it.
Watch out
paired with Update a Product, the whole catalog gets rewritten. Filter first, or a cleanup turns into a rewrite.
Paddle18

List all Reports

Search

In Make“Returns a paginated list of reports”

Brings back the reports sitting in your Paddle account, one item per report.

When to use it
you are looking for a report a colleague generated and would rather not open the dashboard to find it.
Watch out
it lists, and that is it. Getting the numbers out still takes Get a Report and then Get a CSV File for a Report.
Paddle19

List all Transactions

Search

In Make“Returns a paginated list of transactions.”

Goes through your transactions page by page and sends each one into the scenario on its own.

When to use it
a reconciliation, where every line has to be matched against what your own system recorded.
Watch out
a busy account means a lot of items, and each one costs an operation. Narrow the search before you let it run wide.
Need help

Need help automating Paddle with Make?

A person reads every message.

FAQ

Questions that come up next

01Is the Paddle Make integration free to use?
Yes, from the Free plan, within what that plan allows. Paddle counts as a standard app in Make, so it costs nothing extra and the standard catalog ships with every plan. What gets capped is the scenario, not the app: 2 active scenarios at a time, 15 minutes minimum between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of transfer. Paid plans bring the interval down to one minute and stretch execution to 40 minutes. What Paddle itself costs is a separate matter, settled on Paddle's side.
02What do you need to connect Paddle to Make?
A Paddle account and an API key taken from it. Make asks for the key from inside the scenario: you drop a Paddle module, click Create a connection, and paste the credentials. The key lives in your Paddle dashboard, under Developer tools and then Authentication, where you copy it. Make's help page is upfront that it does not know which Paddle plan or which permissions the key needs, and points you back to Paddle for that. So create the key, test it on one module, and build the rest around it afterwards.
03Does Paddle trigger a Make scenario in real time?
No, because the app ships no trigger module at all. None of the 19 modules watches Paddle and waits, so nothing on the Paddle side wakes a scenario up when a payment lands. The start comes from Make instead. The common route is scheduling: the clock on the first module fires the scenario at the interval you choose, 15 minutes apart on a new scenario. The other route is a trigger sitting in a different app placed in front of the scenario. The Paddle modules then work once the scenario is already moving.
04What if a Paddle module is missing from Make?
Reach for Make an API Call. The app ships that module, and it sends the request you want to the Paddle API over the connection you already set up, which brings back within reach whatever the ready-made modules do not cover. The request and the response are on you, so keep Paddle's documentation next to you. Worth knowing too: Make's help page for Paddle is written by an AI from the official documentation and can contain mistakes, so anything that moves money gets verified on Paddle before you switch a scenario on.
05Make or n8n for Paddle?
It depends on who will maintain the automation. Make gives you 19 ready modules for Paddle and a visual editor, which suits a team that wants to build and change things without a developer on hand. n8n has a Paddle node too, and appeals when you want to host the tool yourself or write code inside the flow. Neither wins in the abstract, and plenty of teams run both side by side. Look at who will open the editor in six months, what you are allowed to host, and how much of the logic needs code, then pick.
Hack'celeration Lab

Get our weekly automation tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations