Resources · n8n integration

Paddle n8n integrationAutomate Paddle with n8n.

Paddle takes the checkout, n8n takes everything that happens after it. The Paddle n8n integration exposes 9 operations across 5 resources: coupons, payments, plans, products and users. No trigger node ships for Paddle, so a Schedule Trigger opens the workflow. Built for teams on Paddle Classic.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Paddle n8n integration cover?

The Paddle n8n integration is the Paddle node plus a Paddle credential, sitting inside an n8n workflow. n8n is the automation tool where you chain steps together; a credential is the stored login n8n keeps once and reuses everywhere. With both in place, the node reads plans, products, payments and users out of your Paddle account, and creates or updates coupons, without a line of code.

Coupons are the obvious starting point, because they are the only objects this node writes. A release goes out, and the same workflow creates the coupon, then hands the generated code to the channel that announces it. The template library already carries a Create a coupon on Paddle workflow under number 659, which is a fair skeleton to copy before adapting it.

Reporting is the second pattern. Get many payments, filtered on a date window and a state, lands a clean list in Google Sheets every Monday morning, and a short summary in Slack for whoever watches revenue. Nobody logs into a dashboard to copy rows.

The third pattern points outward. Get many users returns subscription users filtered by plan, subscription or state, which is exactly the shape a CRM wants. Push that into HubSpot so a sales rep sees the plan on the record. If part of your revenue also runs through another processor, the Stripe node has its own page on this site.

When an endpoint you need sits outside these 9 operations, the HTTP Request node calls any endpoint of the Paddle API and reuses the same credential through predefined authentication. Same secrets, same workflow, one extra node.

Two things to know before you build. Paddle has no trigger node in n8n, so the workflow starts on a Schedule Trigger at a fixed interval, on an n8n Webhook called by another service, or on another tool's trigger. And on the list operations, Return All walks through the API pages until everything is in, while leaving it off means Limit decides how many items come back. If n8n itself is new to the team, the n8n training covers the workflow basics this page assumes.

Connect

How do you connect Paddle to n8n?

  1. 01

    Check which Paddle API your account uses

    The n8n credential is built for the Paddle Classic API. Paddle's own documentation is blunt about it: if you joined Paddle after August 2023, your account runs on the Paddle Billing API and this credential may not work for you. Settle that question first, because every step after it depends on the answer.

  2. 02

    Generate a Vendor Auth Code

    In Paddle, open Developer Tools, then Authentication, then Generate Auth Code. Select Reveal Auth Code to display it on screen. Your Vendor ID appears at the same moment, when you generate the API key. Copy both values somewhere safe: the auth code is the secret half of the pair, the vendor ID identifies the account it belongs to.

  3. 03

    Create the credential in n8n

    In n8n, open the Credentials menu and create a Paddle credential. Paste the Vendor Auth Code and the Vendor ID into their two fields. Turn on Use Sandbox Environment API and nodes using that credential hit the Sandbox API endpoint instead of the live one. A credential is set up once and reused across workflows; the Paddle node then offers it in its dropdown.

Actions

What can the Paddle node do?

The Paddle node exposes 9 operations across 5 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetGet ManyUpdateReschedule
Coupon✓✓✓
Payment✓✓
Plan✓✓
Product✓
User✓

Coupon

3 operations
01

Create a coupon

coupon.create

What you see in n8n

Notes & use cases

Creates a discount coupon in Paddle and hands back the code. A single call mints one code or a batch of them.

Key parameters

  • Product Names or IDs: the products the coupon applies to, required when Coupon Type is set to Product; pick them from the dropdown or pass IDs through an expression.
  • Discount Type: flat or percentage, read together with Discount Amount Currency for the amount and Currency, which has to match the balance currency of your account.
  • Coupon Code: left empty, the code is generated randomly; Allowed Uses sits at 999,999 redemptions unless you set it.
Use cases
a release ships, and the workflow creates the launch code before the announcement email goes out.
02

Get many coupons

coupon.getAll

What you see in n8n

Notes & use cases

Lists the coupons attached to one product or subscription, so an audit runs from a workflow instead of the Seller Dashboard.

Key parameters

  • Product ID: the specific product or subscription ID whose coupons you want, required; a fixed value, or {{ $json.field }} when the ID arrives from an earlier node.
  • Return All: on, n8n chains the API pages until every coupon of that product is in the output; off, Limit caps the number of items returned.
Use cases
a weekly export of the codes live on one product, dropped into a sheet the marketing team actually opens.
03

Update a coupon

coupon.update

What you see in n8n

Notes & use cases

Edits coupons that already exist, one precise code or a whole group at a time. Nothing here is mandatory: what you fill in is what changes.

Key parameters

  • Update By: Coupon Code targets a single coupon, Group targets every coupon in a named group.
  • Coupon Code or Group: the value that identifies the target, depending on that choice.
  • Additional Fields: New Coupon Code renames a code, New Group Name moves it, Expires ends it on a date at 00:00:00 UTC, and Product IDs takes a comma-separated list such as 499531,1234,123546, or drops the associated products when left blank.
Use cases
a promotion has to stop today. One call moves the expiry date of the whole group.

Payment

2 operations
04

Get many payments

payment.getAll

What you see in n8n

Notes & use cases

Pulls payments out of Paddle, with filters that cut the list down to the slice a report needs.

Key parameters

  • Date From and Date To: the window the payments fall into, both inside Additional Fields.
  • State: keeps only active, past_due, trialing or paused subscription plans; left unset, all four come back.
  • Is Paid, Plan ID and Subscription ID: narrow to paid rows, to one plan, or to one user subscription.
Use cases
every Monday, last week's payments land in the finance sheet before anyone asks for them.
05

Reschedule a payment

payment.reschedule

What you see in n8n

Notes & use cases

Moves an upcoming subscription payment to a different date, which is the polite answer when a customer asks for a few more days.

Key parameters

  • Payment Name or ID: the upcoming subscription payment to move, required; the dropdown lists them, and an expression works when the ID comes from a previous step.
  • Date: the date you want the payment moved to.
Use cases
a support request to push a renewal back turns into a dated reschedule, with no one opening Paddle by hand.

Plan

2 operations
06

Get a plan

plan.get

What you see in n8n

Notes & use cases

Fetches a single subscription plan from its identifier. Handy when an item carries a plan ID and nothing else readable.

Key parameters

  • Plan ID: the subscription plan ID, required; usually an expression such as {{ $json.field }} pointing at the ID already on the item.
Use cases
a support ticket arrives with a plan ID buried in it, and the workflow resolves the plan before routing the ticket to the right queue.
07

Get many plans

plan.getAll

What you see in n8n

Notes & use cases

Returns the subscription plans of the account in one shot, which is what you want when a downstream step needs the full list rather than one lookup.

Key parameters

  • Return All: on, the node keeps paging until every plan is returned; off, Limit sets how many plans come back.
Use cases
a nightly run rebuilds the plan reference table other workflows read, so no one hardcodes a plan ID in three different places.

Product

1 operation
08

Get many products

product.getAll

What you see in n8n

Notes & use cases

Reads the products of the account. This is the list to call first when another operation asks for product IDs and you only know product names.

Key parameters

  • Return All: on, every product comes through the API pages; off, Limit stops the node at a number you choose.
Use cases
a catalogue check compares what exists in Paddle against the pricing page, and flags anything that only lives in one of the two.

User

1 operation
09

Get many users

user.getAll

What you see in n8n

Notes & use cases

Lists subscription users, with filters for the segment you care about rather than the whole base.

Key parameters

  • Limit: required here, it sets the maximum number of users returned; Return All overrides it and pages through everything.
  • Plan ID and Subscription ID: restrict the list to one subscription plan, or to one specific user subscription.
  • State: filters on active, past_due, trialing or paused; unset, all four statuses are returned.
Use cases
a daily sync of users on one plan feeds the CRM so the sales side stops asking who upgraded.
Need help

Need help automating Paddle with n8n?

A person reads every message.

FAQ

Paddle and n8n, the questions that come up

01Is the Paddle n8n integration free?
Yes, on the n8n side. The Paddle node ships with n8n: nothing to install, no extra cost, and it behaves the same on n8n Cloud, the hosted offer run by n8n, as on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use licence. A workflow built in one place runs in the other. What your Paddle account itself costs is a separate matter, and this page has no figures on it. The only thing you need on the Paddle side is the ability to generate an API key, since that is where the Vendor Auth Code and the Vendor ID come from.
02What credentials do you need to connect Paddle to n8n?
One credential, with one supported authentication method: API access token (Classic). It holds a Vendor Auth Code, created when you generate an API key, and a Vendor ID, displayed at that same moment. Both come from Paddle under Developer Tools, then Authentication, then Generate Auth Code, with Reveal Auth Code to show the value. A third setting, Use Sandbox Environment API, sends every node using that credential to the Sandbox API endpoint instead of the live one. Important detail: this credential works with the Paddle Classic API, and if you joined Paddle after August 2023 your account is on the Paddle Billing API, where it may not work.
03What are the limits of the Paddle node in n8n?
It depends on what you are trying to reach. The node covers 9 operations over 5 resources, and for anything outside that catalogue, the HTTP Request node calls any endpoint of the Paddle API while reusing the same credential through predefined authentication, so you are not stuck. On list operations, watch Return All: enabled, n8n chains the API pages and brings everything back; disabled, Limit caps the number of items. The other constraint is the credential itself, built for the Paddle Classic API. Accounts created after August 2023 sit on the Paddle Billing API, and the documentation warns the credential may not work there.
04Does Paddle have a trigger node in n8n?
No. Paddle has no trigger node in n8n, so nothing starts a workflow from the Paddle side on its own. A Paddle workflow begins with another starting point: a Schedule Trigger firing at a fixed interval, which fits reporting runs like get many payments each morning; an n8n Webhook, meaning a URL n8n exposes that a third-party service calls; or the trigger of another tool already in your stack, a form, a CRM, a helpdesk. Pick the Schedule Trigger for anything periodic and the Webhook when an outside system already knows how to notify you.
05n8n or Make for Paddle?
It depends on four criteria, and both tools are honest options. Hosting: n8n runs self-hosted with Docker or npm, or on n8n Cloud, while Make is a hosted platform with no self-hosting option. Data control follows from that, since a self-hosted instance keeps payment data on infrastructure you own. Cost model: Make bills per operation, which is worth simulating against a workflow that lists every payment every day. Visual logic: both draw the flow on a canvas, and the choice there is mostly a matter of habit. For Paddle specifically, the deciding factor is usually the second one.