Manage customers, subscriptions, and recurring billing with Paddle Billing.
Paddle currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
New Active Subscription
Triggers when a subscription activates — a trial converts or the first payment succeeds.
Subscription Canceled
Triggers when a subscription is canceled — revoke access or notify support.
Subscription Past Due
Triggers when a subscription goes past due — start dunning flows or restrict features.
Transaction Completed
Triggers when a transaction completes successfully — send a receipt or update records.
Payment Failed
Triggers when a transaction payment fails — trigger retry logic or alert the customer.
List Customers
Lists customers from your Paddle account.
Get Subscription
Retrieves a Paddle subscription by ID.
Update Subscription
Updates a Paddle subscription. Send the full recurring item list you want the subscription to keep.
Cancel Subscription
Cancels a Paddle subscription immediately or at the next billing period.
Create Transaction
Creates a Paddle transaction. When you use recurring prices, completing the transaction starts the subscription.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Paddle event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Active Subscription
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Paddle action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
List Customers
Combine Paddle with another integration and Coherence records to connect customer and order activity to the relationship record behind it.
Starts with
New Active Subscription
Finishes with
List Customers, then preserve the outcome in Coherence
The exact authentication fields depend on Paddle. The workflow structure stays straightforward:
Authorize the Paddle account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Paddle or provide a complementary trigger or action.
Paddle currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect customer and order activity to the relationship record behind it.
Paddle currently lists 5 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Paddle triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
