Skip to content

feat(Paddle Node): Rename node to Paddle Classic - #43042

Merged
Joffcom merged 1 commit into
masterfrom
rename-paddle-node-to-paddle-classic
Nov 4, 2026
Merged

Joffcom merged 1 commit into
masterfrom
rename-paddle-node-to-paddle-classic

Conversation

@Joffcom

@Joffcom Joffcom commented Nov 4, 2026 •

Copy link
Copy Markdown
Member

Summary

Paddle has two platforms: Paddle Classic and Paddle Billing. The existing Paddle node uses the Paddle Classic API. This PR renames the node to "Paddle Classic" and renames its credential to "Paddle Classic API". It also adds a notice to the node and to the credential. The notice tells Paddle Billing users to use the Paddle Billing node.

The internal identifiers do not change (n8n-nodes-base.paddle, paddleApi). Existing workflows and credentials continue to work. Existing nodes keep their names. Only new nodes get the default name "Paddle Classic".

Why

The name "Paddle" does not tell users which Paddle platform the node supports. Paddle Billing users can select this node and get errors, because the node only works with Paddle Classic.

Paddle Billing is an official verified community node managed by the team at Paddle and will be approved and available before this is released.

How to test

  1. Open the node panel and search for "Paddle". Make sure that "Paddle Classic" shows.
  2. Add the node to a workflow. Make sure that the notice shows at the top of the parameters.
  3. Create a new credential for the node. Make sure that the credential is "Paddle Classic API" and that the notice shows.
  4. Open a workflow that has an existing Paddle node. Make sure that the node and its credential still load and run.

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/CE-3798

Review / Merge checklist

  • I have seen this code, I have run this code, and I take responsibility for this code.
  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)

🤖 Generated with Claude Code

View guided diff Turn on auto-fix

Rename the node and its credential to Paddle Classic. Add a notice that
tells Paddle Billing users to use the Paddle Billing node.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@n8n-assistant

n8n-assistant Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

PR review overview

Based on ownership of the 2 changed files in this PR:

Ownership Files owned Share Source code Test files Misc
@n8n-io/nodes 2 100% +18 / -4 +0 / -0 +0 / -0
Total 2 100% +18 / -4 +0 / -0 +0 / -0

@n8n-assistant n8n-assistant Bot added cla-signed n8n team Authored by the n8n team node/improvement New feature or request labels Nov 4, 2026
@codecov

codecov Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
...es/nodes-base/credentials/PaddleApi.credentials.ts 0.00% 1 Missing ⚠️

📢 Thoughts on this report? Let us know!

@Joffcom
Joffcom marked this pull request as ready for review November 4, 2026 13:31

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 2 files

Shadow auto-approve: would not auto-approve because issues were found.

View guided diff | Turn on auto-fix | Re-trigger cubic

@Joffcom
Joffcom added this pull request to the merge queue Nov 4, 2026
Merged via the queue into master with commit ddabd54 Nov 4, 2026
144 checks passed
@Joffcom
Joffcom deleted the rename-paddle-node-to-paddle-classic branch November 4, 2026 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed n8n team Authored by the n8n team node/improvement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants