Menu
Mattering Automations connector

A Paddle MCP where every money node can prove itself in the sandbox first

Connect one API key and Paddle Billing becomes workflow steps for visual automations and AI agents: catalog, customers, subscriptions, transactions, refunds, and events. Every one of the 39 nodes carries a use_sandbox switch to Paddle's free sandbox, so the five nodes that move real money or change real billing can be rehearsed end to end without a cent leaving anyone's account.

39 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Paddle MCP connector does

The Paddle connector for Mattering Automations is 39 nodes across Paddle Billing: the catalog (products and prices), customers with their addresses, businesses, and credit balances, the subscription lifecycle (update, pause, resume, cancel), transaction reads with invoice PDF links, adjustments for refunds and credits with credit note PDFs, the account event feed, and the webhook delivery log. It targets Paddle Billing at api.paddle.com, not the legacy Paddle Classic vendors API, and pins every request to Paddle-Version 1 so response shapes never depend on a per-account default.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer which subscriptions are past due, what a customer has been billed, and whether a refund has cleared review, without anyone opening the Paddle dashboard.

Because Mattering is a work platform rather than middleware, billing work lands somewhere useful by default: a scheduled sweep over past due subscriptions can open tasks in Mattering Productivity with the customer and the failed transaction attached, and churn signals like scheduled cancellations can log to a Mattering database, all on one canvas next to the rest of the work.

The money boundary is explicit. Five nodes are flagged destructive: Paddle: Create Adjustment (Refund or Credit) moves real money (a refund returns money to the customer's payment method, and an adjustment cannot be edited or deleted once created), Paddle: Cancel Subscription run in immediate mode is permanent, Paddle: Pause Subscription stops real billing, Paddle: Resume Subscription charges the customer immediately by default, and the immediate proration modes on Paddle: Update Subscription bill right away. Flip any node's use_sandbox switch and it talks to sandbox-api.paddle.com instead, where refunds auto-approve about every ten minutes, so the whole destructive set can be rehearsed with zero real money.

One connection, three surfaces

  • Visual automations. Drag Paddle nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Paddle node, ready to drop on the canvas

39 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 24

Paddle: Get Address

Retrieve one address for a customer by id.

Paddle: Get Business

Retrieve one business for a customer by id.

Paddle: Get Credit Note PDF Link

Get a temporary link to the credit note PDF for a refund or credit adjustment (data.url; the link expires, so use it in the same run). Available once the adjustment is approved.

Paddle: Get Customer

Retrieve one customer by id.

Paddle: Get Invoice PDF Link

Get a temporary link to the invoice PDF for a transaction (data.url; the link EXPIRES after one hour, so use it in the same run, do not store it). Available for completed automatically-collected transactions and billed or completed manually-collected ones; zero-value transactions have no invoice.

Paddle: Get Notification

Retrieve one notification by id, including the full event payload that was (or should have been) delivered and its attempt history.

Paddle: Get Notification Setting

Retrieve one notification destination by id, including its subscribed events and destination URL or email.

Paddle: Get Price

Retrieve one price by id, optionally embedding its product.

Paddle: Get Product

Retrieve one product by id, optionally embedding its prices.

Paddle: Get Subscription

Retrieve one subscription by id, including items, billing period, any scheduled_change (pending cancel, pause or resume) and customer-facing management URLs.

Paddle: Get Transaction

Retrieve one transaction by id with line items, calculated totals and payment attempts, optionally embedding the customer, address, business, discount or adjustments.

Paddle: List Addresses

List a customer's addresses. Paddle uses the address country and postal code to work out the right tax rate.

Paddle: List Adjustments

List adjustments (refunds, credits, chargebacks and their reversals), filtered and paginated. Page size defaults to 10, max 50, on this endpoint. Track refund approval here: live refunds start at pending_approval.

Paddle: List Businesses

List a customer's businesses: the B2B billing details (company name, tax and company numbers) attached to transactions and subscriptions. Optional; consumers have none.

Paddle: List Customer Credit Balances

List a customer's credit balances per currency: available (usable at checkout), reserved (held for drafts) and used. Amounts are strings in the lowest denomination.

Paddle: List Customers

List customers, filtered and paginated. Supports exact email match and a free-text search over name, email and id.

Paddle: List Event Types

List every event type Paddle can emit (for example transaction.completed, subscription.canceled), with descriptions and available API versions. Use it to pick events for a webhook destination.

Paddle: List Events

List events that occurred on the account, newest first: every create, update and billing lifecycle change, each with the changed entity under data. The polling alternative to webhooks for driving automations.

Paddle: List Notification Settings

List notification destinations (webhook endpoints and email addresses) with their subscribed events, active flag and pinned API version. Read-only here: create and edit destinations in the Paddle dashboard, where the signing secret is issued.

Paddle: List Notifications

List notifications sent (or attempted) to your webhook and email destinations, with delivery status and attempt counts. The debugging surface for missed webhooks.

Paddle: List Prices

List prices, filtered and paginated. Price ids from here feed subscription item changes and transaction lines.

Paddle: List Products

List products in the catalog, filtered and paginated. Needs no parameters (an empty catalog returns an empty list), so this is also the credential health check. Product ids from here feed the price nodes.

Paddle: List Subscriptions

List subscriptions, filtered and paginated: by customer, price, status (active, canceled, past_due, paused, trialing) or pending scheduled change (cancel, pause, resume).

Paddle: List Transactions

List transactions (Paddle's revenue records: checkouts, renewals, invoices), filtered and paginated. Amounts are strings in the lowest denomination. Page size defaults to and caps at 30 on this endpoint.

Action nodes 15

Paddle: Cancel Subscription

END a real subscription and its recurring revenue. With the default next_billing_period, Paddle schedules the cancel for the end of the current period, and you can still undo it via Paddle: Update Subscription with scheduled_change null. With immediately, the subscription is canceled on the spot and that is PERMANENT: Paddle cannot reinstate a canceled subscription; the customer would have to sign up again.

Paddle: Create Address

Create an address for a customer. Only country_code is required; Paddle uses country and postal code for tax calculation. Reversible: archive with Paddle: Update Address.

Paddle: Create Adjustment (Refund or Credit)

MOVES REAL MONEY. A refund sends money from your balance back to the customer's payment method (works on completed automatically-collected transactions; live refunds go to pending_approval for Paddle review, some auto-approve). A credit reduces what a manually-collected customer owes on a billed or past_due transaction and needs no approval. Adjustments CANNOT be edited or deleted once created. In the sandbox, refunds auto-approve about every ten minutes, so test there.

Paddle: Create Business

Create a business for a customer, holding company details for B2B billing (shown on invoices; the tax identifier can reverse-charge VAT where applicable). Reversible: archive with Paddle: Update Business.

Paddle: Create Customer

Create a customer. Email must be unique: Paddle returns a conflict error if a customer with the email already exists (archived included). Reversible: archive with Paddle: Update Customer.

Paddle: Create Price

Create a price for a product: how much and how often it is billed. Omit billing_cycle for a one-time price; include it for a recurring one. Creating a price moves no money. Reversible: archive it with Paddle: Update Price.

Paddle: Create Product

Create a product in the catalog. Products hold the what (name, tax category); attach one or more prices for the how much. Reversible: archive it with Paddle: Update Product.

Paddle: Pause Subscription

STOP BILLING on a real subscription. By default the pause takes effect at the end of the current billing period (a scheduled_change you can still remove via Paddle: Update Subscription with scheduled_change null); immediately pauses on the spot. While paused the customer is not billed. Undo by resuming, which by default charges them immediately.

Paddle: Resume Subscription

RESTART BILLING on a paused subscription (or one scheduled to pause). By default this starts a new billing period and CHARGES the customer immediately; set on_resume to continue_existing_billing_period to avoid a charge when their paid period has not ended. Billing dates are recalculated from the resume date.

Paddle: Update Address

Update an address (sparse). Also the archive path: set status to archived to retire the address (Paddle has no address delete), or active to restore it.

Paddle: Update Business

Update a business (sparse). Also the archive path: set status to archived to retire the business (Paddle has no business delete), or active to restore it.

Paddle: Update Customer

Update a customer (sparse). Also the archive path: set status to archived to retire the customer record (Paddle has no customer delete), or active to restore it.

Paddle: Update Price

Update a price (sparse). Changing unit_price affects what NEW checkouts and renewals bill, not past transactions. Also the archive path: set status to archived to retire the price (Paddle has no price delete), or active to restore.

Paddle: Update Product

Update a product (sparse: only fields sent are changed). Also the archive path: Paddle has no product delete, so set status to archived to retire a product (and active to restore it).

Paddle: Update Subscription

Change a REAL customer's billing: swap plans, change quantities, reschedule billing or apply a discount. Changing items, next_billed_at or the discount requires proration_billing_mode, and the prorated_immediately and full_immediately modes create a transaction that CHARGES the customer right away. Sending scheduled_change as null is the undo for a pending scheduled cancel or pause.

Connecting Paddle takes one credential

Paddle issues API keys from Developer tools, under Authentication, in the dashboard. The key is sent as a bearer credential on every request and carries granular permissions chosen when it is created: a key missing a permission still authenticates but is refused with a 403 on the surfaces it cannot touch. Sandbox accounts are free and issue their own keys, and the environment is baked into the key, so a sandbox key only works against the sandbox host and a live key only against production.

1

In the Paddle dashboard, open Developer tools, then Authentication, and create an API key with read and write permissions on the entities your automations will touch.

2

In Mattering Automations, open Connectors, click Add Connector, choose Paddle, and create a credential with that key.

3

Click Test Connection. Mattering lists products with the key, a read that succeeds even on an empty catalog.

4

All 39 Paddle nodes appear in the canvas palette. For anything that touches money, start with use_sandbox enabled and a sandbox key, and only point the workflow at production once it behaves.

Common uses for the Paddle MCP

Subscription health an agent can watch

Paddle: List Subscriptions filters by status (active, past_due, paused, trialing, canceled) and by pending scheduled change, and Paddle: Get Subscription shows a subscription's items, billing period, and any scheduled cancel or pause. A morning sweep over past_due renewals is the earliest honest churn signal in the data.

Catalog managed from the canvas

Paddle: Create Product and Paddle: Create Price define what you sell and how it bills; creating either moves no money. Paddle: Update Product and Paddle: Update Price handle edits, and retiring is a status flip to archived on those same update nodes, because Paddle archives instead of deleting.

Customer records without the dashboard

Paddle: List Customers supports exact email match and free text search, Paddle: Create Customer adds one (the email must be unique, archived customers included), and the address and business nodes carry the tax location and B2B billing details Paddle uses on transactions. Paddle: List Customer Credit Balances shows what a customer holds per currency.

Refunds with a paper trail

Paddle: Create Adjustment (Refund or Credit) issues a refund or credit against a transaction. Live refunds go to pending approval for Paddle review, and Paddle: List Adjustments tracks them through it; once approved, Paddle: Get Credit Note PDF Link fetches the credit note. An adjustment cannot be edited or deleted once created, so gate this node behind a condition, an approval step, or a manual run.

Revenue reads and invoice delivery

Paddle: List Transactions and Paddle: Get Transaction expose Paddle's revenue records with line items, calculated totals, and payment attempts, and Paddle: Get Invoice PDF Link returns a temporary link to the invoice PDF. The link expires after about one hour, so fetch it in the same run that uses it rather than storing it.

Event polling instead of guesswork

Paddle: List Events returns everything that happened on the account, newest first, with the changed entity attached, and Paddle: List Event Types documents what can fire. Paddle: List Notifications is the debugging surface for webhook deliveries to the destinations you configure in the Paddle dashboard.

Example: Past due subscriptions become tasks before they become churn

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a daily schedule starts the sweep.

2

Paddle: List Subscriptions filters to status past_due and returns every subscription whose renewal payment has failed.

3

Paddle: Get Customer resolves each one to a name and email, and Paddle: Get Transaction pulls the failed renewal's line items and payment attempts.

4

A task opens in Mattering Productivity with the customer, the amount, and the attempt history attached, assigned to whoever owns billing follow-up.

5

A row lands in a Mattering database so the past due list trends over time instead of vanishing into a dashboard nobody checks.

6

The next morning's sweep sees what recovered. Anything still past due after the grace window is a decision for a person, with Paddle: Cancel Subscription left on its default scheduled mode so an immediate, permanent cancel never happens by accident.

Paddle MCP questions, answered

What Paddle operations are supported?

39 nodes on Paddle Billing: products and prices (create, read, update, archive), customers with addresses, businesses, and credit balances, the subscription lifecycle (list, get, update, pause, resume, cancel), transaction reads with invoice PDF links, adjustments for refunds and credits with credit note PDFs, the account event feed and event type catalog, and read access to notification destinations and deliveries. Deliberately not shipped: creating or updating transactions (that is billing a real customer, deferred until invoice automation demand shows up), subscription activation and one-time charges, discounts, payment method management, reports, and the legacy Paddle Classic API.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Can this connector move real money?

Yes, and it says so loudly. Five nodes are flagged destructive. Paddle: Create Adjustment (Refund or Credit) is the money mover: a refund sends money from your balance back to the customer's payment method, live refunds go to pending approval for Paddle review, and an adjustment cannot be edited or deleted once created, so it fires once. Paddle: Cancel Subscription in immediate mode is permanent, because Paddle cannot reinstate a canceled subscription. Paddle: Resume Subscription starts a new billing period and charges the customer immediately by default, and the immediate proration modes on Paddle: Update Subscription create a transaction that bills right away. Gate all five behind conditions, approval steps, or manual runs, and rehearse them in the sandbox first.

How do I test without spending real money?

Every node has a use_sandbox switch that points it at sandbox-api.paddle.com. A Paddle sandbox account is free, separate from production, and issues its own API keys, and it supports the whole surface including the money flows: sandbox refund adjustments auto-approve about every ten minutes, so even the refund lifecycle, credit note included, runs end to end with zero real money. Remember the environment is baked into the key: a sandbox key only works against the sandbox host and a live key only against production.

Why is there no delete node for products or customers?

Because Paddle has no delete endpoints for them. Products, prices, customers, addresses, and businesses archive instead: the update nodes accept a status of archived, which hides the entity from default lists and blocks new use while preserving history, and setting status back to active restores it. The connector models this honestly rather than pretending an archive is a delete.

Can a Paddle event trigger a workflow?

Not as a trigger node in this connector. Notification destinations are dashboard configuration in Paddle, where the signing secret is issued, so the connector reads them rather than creating them. The honest pattern today is polling: run Paddle: List Events on a schedule, newest first, and act on what changed; each event carries the changed entity in its payload. Paddle: List Notifications and Paddle: Get Notification cover debugging deliveries to destinations you have configured.

Is this Paddle Billing or Paddle Classic?

Paddle Billing, the current platform at api.paddle.com, with every request pinned to Paddle-Version 1 so response shapes stay stable as Paddle evolves. Paddle Classic, the legacy vendors API with different auth and different entities, is deliberately not built and shares nothing with these nodes.

Why did a node return a 403 when Test Connection passed?

Paddle API keys carry granular permissions chosen at creation, and the connection test only lists products, so a narrowly permissioned key can pass the test while the surfaces it lacks are refused with a 403. Create a new key with read and write permissions on the entities your automations touch and update the credential on the connector.

39 nodes waiting on the canvas

Put Paddle to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Paddle is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products