Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Paddle

Manage customers, subscriptions, and recurring billing with Paddle Billing.

CategoryCommerce
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Paddle with Flows360

Manage customers, subscriptions, and recurring billing with Paddle Billing.

Use the Paddle connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 5 triggers.

Available actions

  • List Customers
  • Get Subscription
  • Update Subscription
  • Cancel Subscription
  • Create Transaction
  • Custom API Call

Available triggers

  • New Active Subscription
  • Subscription Canceled
  • Subscription Past Due
  • Transaction Completed
  • Payment Failed

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Paddle
  • Package: @activepieces/piece-paddle@0.1.0
  • Exact artifact digest: sha256:cb81419859da59adcb81e010a4dfc5598fa0962403e246e7cc3cf919a629fc9e
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • List Customers (list-customers), Lists customers from your Paddle account. Classification: read.
  • Get Subscription (get-subscription), Retrieves a Paddle subscription by ID. Classification: read.
  • Update Subscription (update-subscription), Updates a Paddle subscription. Send the full recurring item list you want the subscription to keep. Classification: read.
  • Cancel Subscription (cancel-subscription), Cancels a Paddle subscription immediately or at the next billing period. Classification: read.
  • Create Transaction (create-transaction), Creates a Paddle transaction. When you use recurring prices, completing the transaction starts the subscription. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Active Subscription, webhook.
  • Subscription Canceled, webhook.
  • Subscription Past Due, webhook.
  • Transaction Completed, webhook.
  • Payment Failed, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actions6
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Customers Yes No Lists customers from your Paddle account.
Get Subscription Yes No Retrieves a Paddle subscription by ID.
Update Subscription Yes No Updates a Paddle subscription. Send the full recurring item list you want the subscription to keep.
Cancel Subscription Yes No Cancels a Paddle subscription immediately or at the next billing period.
Create Transaction Yes No Creates a Paddle transaction. When you use recurring prices, completing the transaction starts the subscription.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Active Subscription Yes No webhook trigger declared by the pinned package.
Subscription Canceled Yes No webhook trigger declared by the pinned package.
Subscription Past Due Yes No webhook trigger declared by the pinned package.
Transaction Completed Yes No webhook trigger declared by the pinned package.
Payment Failed Yes No webhook trigger declared by the pinned package.

Supported actions

List Customers · Read

Lists customers from your Paddle account.

list_customers · Risk: low · Retry: safe

Inputs

  • email · string · Optional, Optionally filter customers by exact email address.
  • status · string · Optional, Optionally filter customers by status.
  • limit · number · Optional, Maximum number of customers to return.
Get Subscription · Read

Retrieves a Paddle subscription by ID.

get_subscription · Risk: low · Retry: safe

Inputs

  • subscriptionId · string · Required, Select the Paddle subscription to use.
Update Subscription · Read

Updates a Paddle subscription. Send the full recurring item list you want the subscription to keep.

update_subscription · Risk: low · Retry: safe

Inputs

  • subscriptionId · string · Required, Select the Paddle subscription to use.
  • priceId · string · Required, Select an active recurring Paddle price.
  • quantity · number · Optional, Optional quantity for the recurring price.
  • prorationBillingMode · string · Optional, How Paddle should bill for the subscription change.
  • customData · object · Optional, Optional JSON object to store on the subscription.
Cancel Subscription · Read

Cancels a Paddle subscription immediately or at the next billing period.

cancel_subscription · Risk: low · Retry: safe

Inputs

  • subscriptionId · string · Required, Select the Paddle subscription to use.
  • effectiveFrom · string · Optional, Choose when Paddle should apply the cancellation.
Create Transaction · Read

Creates a Paddle transaction. When you use recurring prices, completing the transaction starts the subscription.

create_transaction · Risk: low · Retry: safe

Inputs

  • customerId · string · Required, Select the Paddle customer to use.
  • addressId · string · Required, Select the Paddle address to bill against.
  • priceId · string · Required, Select an active recurring Paddle price.
  • quantity · number · Optional, Optional quantity for the recurring price.
  • customData · object · Optional, Optional JSON object to store on the transaction.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Active Subscription · Webhook

Triggers when a subscription activates u2014 a trial converts or the first payment succeeds.

Subscription Canceled · Webhook

Triggers when a subscription is canceled u2014 revoke access or notify support.

Subscription Past Due · Webhook

Triggers when a subscription goes past due u2014 start dunning flows or restrict features.

Transaction Completed · Webhook

Triggers when a transaction completes successfully u2014 send a receipt or update records.

Payment Failed · Webhook

Triggers when a transaction payment fails u2014 trigger retry logic or alert the customer.

Setup

Setup

  1. Add the Paddle connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-paddle@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Paddle connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-paddle@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com