Paddle automations
Finance · 11 integrations
Billing events like subscription upgrades, failed payments, and cancellations need to trigger actions across CRMs, support tools, and provisioning systems — which is why teams automate Paddle heavily. Common workflows include syncing new subscribers to HubSpot or Salesforce, provisioning SaaS access on payment success, and alerting Slack on churn events. The platform's webhook-first architecture makes it well-suited to automation, but its tight response windows and account-level limits require careful design.
What it costs to automate Paddle
Platform pricing at different volumes. Annual billing shown.
| Platform | Free tier | 100 tasks/mo | 1K tasks/mo | 10K tasks/mo |
|---|---|---|---|---|
| Zapier | 100 tasks/mo | Free | $69/mo | $69+/mo |
| Power Automate | 750 runs/mo | Free | $15/mo | $15/mo |
| Make | 1,000 credits/mo | Free | Free | $10.59/mo |
| Pipedream | 100 credits/mo | Free | $29/mo | $79/mo |
| n8n | Yes | $20/mo | $20/mo | $50/mo |
Paddle integrations
Each page compares all five platforms for that pair.
Paddle triggers & actions by platform
Which capabilities each platform supports for Paddle.
| Capability | Zapier | Make | n8n | Pipedream | Power Automate |
|---|---|---|---|---|---|
| Triggers | |||||
| HTTP Request | — | ✓ | ✓ | — | — |
| HTTP Webhook | — | — | ✓ | ✓ | — |
| New Paddle Subscription | ✓ | — | — | ✓ | — |
| Paddle Webhook | — | — | ✓ | ✓ | — |
| Paddle Webhook Trigger | — | — | ✓ | ✓ | — |
| Payment Succeeded | ✓ | ✓ | — | — | — |
| Schedule Trigger | — | — | ✓ | ✓ | — |
| Subscription Created | ✓ | ✓ | — | — | — |
| Webhook Received | — | ✓ | ✓ | — | — |
| API Polling | — | — | ✓ | — | — |
| When a record is created | — | — | — | — | ✓ |
| When a record is modified | — | — | — | — | ✓ |
| Actions | |||||
| Create Contact | ✓ | ✓ | ✓ | — | — |
| Create Event | ✓ | — | ✓ | ✓ | — |
| Create Record | ✓ | ✓ | — | ✓ | — |
| Create Page (Notion) | — | — | ✓ | ✓ | — |
| Create Salesforce Record | ✓ | ✓ | — | — | — |
| HTTP Request | — | — | ✓ | ✓ | — |
| Update deal | ✓ | — | ✓ | — | — |
| Update Record | ✓ | — | ✓ | — | — |
| Update Spreadsheet Row in Google Sheets | ✓ | — | — | ✓ | — |
| Add a Row in Google Sheets | — | ✓ | — | — | — |
| Create a record | — | — | — | — | ✓ |
| Update a record | — | — | — | — | ✓ |
Things to know about automating Paddle
Webhook Response Window
Paddle requires an HTTP 200 response within 5 seconds or it marks delivery as failed and retries. Handlers that verify signatures, update a database, and send a confirmation email can easily breach this limit — offload heavy processing to a background queue and respond immediately.
API Rate Limits
Standard endpoints allow 240 requests per minute per IP, returning HTTP 429 with a 60-second block if exceeded. Price preview and transaction preview endpoints have a higher limit of 1,000 requests per minute, and client-side Paddle.js calls to those same methods are not rate limited at all.
Webhook Endpoint Cap
Paddle enforces a hard limit of 5 webhook notification endpoints per account. On Zapier or Make, this forces all event types into a single endpoint, requiring filter or Paths logic to route subscription.cancelled, payment.failed, and other events in one workflow rather than separate dedicated ones.
API Key Rotation Risk
Paddle API keys expire after 90 days of inactivity by default, and once expired they cannot be revalidated — you must create and rotate to a new key. Keys created before May 6, 2025 are now classified as legacy keys; Paddle recommends migrating to the new enhanced key format, which affects authentication setup in n8n, Pipedream, Power Automate, and Make.
Idempotency and Deduplication
Paddle uses at-least-once delivery semantics, meaning the same webhook event can arrive multiple times. Without idempotency checks keyed on the event ID, workflows on any platform — Zapier, Make, n8n, Power Automate, or Pipedream — risk double-provisioning access, duplicate CRM records, or multiple fulfilment triggers.
Subscription Charge Sub-limits
Immediate charges on a subscription are capped at 20 per hour and 100 per day per subscription, enforced at the account level rather than per IP or API key. Automated upgrade or proration workflows that batch-process many subscriptions in a short window will hit HTTP 429 errors silently if retry logic is not built in.
What breaks at scale
Paddle's per-subscription immediate charge limit of 20 per hour and 100 per day is enforced account-wide, not per API key or IP. If you're running automated proration, mid-cycle upgrade, or dunning workflows that touch the same subscription repeatedly, you will hit HTTP 429 errors without any warning in the Paddle dashboard. Make and n8n workflows that lack exponential backoff retry logic will silently drop those operations, leaving subscriptions in inconsistent billing states.
The 5-second response timeout is the most common failure point at scale. When a product launch or discount event triggers a surge of simultaneous Paddle webhooks, handlers running on serverless runtimes — including those invoked by Zapier, Pipedream, or Make's cloud infrastructure — can experience cold starts that consume 2-4 seconds before any code runs, reliably causing timeout failures. Paddle then retries those events into a low-priority queue, creating a backlog of retried events that arrive hours later and look like fresh activity, causing deduplication failures if event IDs aren't stored persistently.
If your account predates August 8, 2023, your existing API keys, webhook schemas, and SDK calls are all Paddle Classic — and none of that data or configuration migrates automatically to Paddle Billing. Any workflow in Zapier, Make, n8n, Power Automate, or Pipedream built against the Classic API will break silently after migration, as the Billing API uses a completely different structure for subscriptions, transactions, and events. Teams have been burned by assuming webhook field names carry over; they do not, and every downstream field mapping must be rebuilt from scratch.
Frequently asked questions
How do I connect Paddle webhooks to Zapier, Make, or n8n?
Zapier, Make, n8n, Power Automate, and Pipedream all support Paddle via webhook triggers — you create a webhook URL in the automation platform and register it as a notification endpoint in Paddle's developer dashboard. The critical constraint is Paddle's 5-endpoint-per-account limit, so you may need to funnel all event types through a single endpoint and use routing logic inside your workflow. Always verify the Paddle-Signature HMAC-SHA256 header on incoming requests to confirm authenticity.
What Paddle events can I use to trigger automations?
Key automatable events include subscription.created, subscription.updated, subscription.cancelled, transaction.completed, and payment.failed, among others. These fire reliably but without guaranteed ordering — a subscription.updated event can arrive before subscription.created if an earlier delivery attempt timed out and retried. Platforms like n8n and Pipedream make it easier to implement ordering checks using the occurred_at timestamp field compared to simpler tools like Zapier.
Does n8n have a native Paddle integration?
n8n has a legacy Paddle node built for Paddle Classic, which requires a Vendor ID and Auth Code from the Classic developer tools — a different authentication pattern from the new Paddle Billing API key format (prefixed pdl_live_ or pdl_sdbx_). For Paddle Billing workflows, most n8n users build with the HTTP Request node and webhook trigger node directly rather than relying on the legacy node. Zapier, Make, Power Automate, and Pipedream similarly require HTTP-level configuration for full Paddle Billing API coverage.
How do I prevent duplicate processing when Paddle retries webhooks?
Paddle's retry schedule sends up to 60 attempts over 3 days for live accounts, using exponential backoff, which means the same event ID can arrive multiple times. The standard approach is to store processed event IDs in a database or cache layer and check for existence before executing any action — this applies regardless of whether you're using Zapier, Make, n8n, Power Automate, or Pipedream. Platforms with native datastore features like Pipedream or n8n with an attached database make this deduplication pattern easier to implement inline.