feat(Paddle Node): Rename node to Paddle Classic

Merged
JO
2h ago
+18-4

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