PaymentsReal-timeUpdated May 2026

Paddle

Paddle merchant-of-record subscription writes

Paddle is the merchant-of-record billing platform — it handles sales tax, VAT, and chargebacks on behalf of the seller, which makes it the default choice for SaaS companies selling globally without wanting to build a tax compliance team. Tiny Command exposes six actions, no triggers (Paddle's event delivery is via Notification webhooks configured in the Paddle dashboard rather than subscribed via API — point them at a Tiny Command webhook trigger to capture events): Create Customer, Get Customer, List Products, List Subscriptions, List Transactions, and Cancel Subscription. The connection uses a Paddle API key (Server-side) from the Developer Tools section, with the environment toggle (sandbox vs production) set per-key. Cancel Subscription supports effective_from values of immediately or next_billing_period — most retention workflows offer the user a choice and pass it through. List Transactions is the right action for revenue reporting; each transaction includes the customer, the line items, totals, currency, and the tax breakdown Paddle remitted on the seller's behalf.

Connect Paddle

0triggers

6actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Paddle can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Cancel Paddle Subscription	Cancels immediately or at period end. For "customer requested cancel → execute" workflows or for "failed payment after N retries → cancel" dunning workflows.	2 fields	View →
Create Paddle Customer	Creates a customer record with email, name. For "new B2B customer → provision in Paddle for billing" workflows.	3 fields	View →
Get Paddle Customer	Returns customer details by ID. The standard lookup for customer-context workflows or for resolving customer IDs to readable identity.	1 fields	View →
List Paddle Products	Returns the product catalog with pricing variants. Useful for resolving product IDs at workflow setup and for catalog inventory.	1 fields	View →
List Paddle Subscriptions	Paginated subscriptions with filters. For MRR reporting and for "subscriptions ending this month" renewal-management workflows.	2 fields	View →
List Paddle Transactions	Paginated transactions with customer, line items, totals, tax breakdown. For revenue-recognition workflows or for sync to accounting systems.	2 fields	View →

Recipes

Pre-built Paddle workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Paddle → Slack alerts

AI-triage every Paddle event, ping the right channel only when it matters.

Paddle → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Paddle → Notion database

Turn Paddle into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Paddle once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Paddle field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Paddle integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Paddle to Tiny Command?

Open the Tiny Command workflow builder, drop in a Paddle node, and click Connect. Authorize Paddle once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Paddle triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Paddle today. Use Tiny Command's universal Webhook or Schedule trigger to start Paddle workflows, then run any Paddle action you need.

What Paddle actions can I run from a workflow?

6 Paddle actions are available out of the box, covering payments operations like "Cancel Paddle Subscription". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Paddle integration real-time?

Paddle actions execute synchronously inside your workflow. Tiny Command waits for Paddle's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Paddle with Tiny Command?

No. Every Paddle trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Paddle API endpoint directly.

How much does the Paddle integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Paddle integration itself has no per-app surcharge.