Yes. Krokul CRM integrates with Paddle Billing. A won deal creates the Paddle customer and a transaction with the agreed prices, and Paddle then reports completed payments, failed charges, subscription changes and refunds back to the deal and the client company in Krokul. Paddle acts as the merchant of record and issues the invoice to the buyer, so Krokul keeps the sale and the payment history without a second invoice. The link runs through the Krokul app in Make and n8n or through the Krokul API and webhooks.
Automation platformsMaken8n
When a deal is won in the pipeline you mapped to Paddle, Krokul creates the Paddle customer from the client company and a transaction with the price IDs and quantities from the deal lines. The deal UUID travels in custom_data. For a sales-assisted contract the transaction uses manual collection, and Paddle sends its own invoice once the transaction is billed. Self-serve buyers get the checkout link instead.
Paddle sends transaction.completed after it processes the payment. Krokul reads the deal UUID from custom_data, records a payment fact on that deal and stores the Paddle transaction ID as an external key. The client company debt drops, and invoice.paid follows when the plan is covered.
A transaction.payment_failed event adds a comment on the deal with the amount and the Paddle transaction ID. When a subscription moves to past due, subscription.past_due creates a task for the owner of the client company. Paddle keeps retrying the card on its side.
The events subscription.created, subscription.updated, subscription.paused and subscription.canceled update a read-only copy of the Paddle subscription on the client company. The Krokul MRR movements report counts the change with the amount Paddle holds. One billing owner per client keeps a Krokul contract and a Paddle subscription from charging the same company twice.
Paddle records refunds and credits as adjustments. On adjustment.created, Krokul finds the payment by the transaction ID and books a refund linked to it. The deal shows the net amount afterwards.
| Paddle | Direction | Krokul | When |
|---|---|---|---|
| Customer (ctm_) | Krokul → Paddle | Client company, external key | First transaction for the client |
| Transaction with price IDs and custom_data | Krokul → Paddle | Won deal with its lines | The deal is won |
| transaction.completed | Paddle → Krokul | Payment fact on the deal | Paddle processes the payment |
| transaction.payment_failed | Paddle → Krokul | Comment on the deal | A charge is declined |
| subscription.created, .updated, .canceled | Paddle → Krokul | Read-only subscription and MRR movement | The subscription changes |
| subscription.past_due | Paddle → Krokul | Task for the account manager | A renewal stays unpaid |
| adjustment.created | Paddle → Krokul | Refund linked to the payment | A refund or credit is approved |
Yes. Krokul integrates with Paddle Billing through the Krokul app in Make and n8n and through its API and webhooks, for customers, transactions, subscriptions and refunds.
Paddle. Paddle sells to the buyer and issues the invoice, and Krokul records the deal, the payment and the subscription for the client company without issuing its own invoice for that sale.
Krokul writes the deal UUID into custom_data of the Paddle transaction. The transaction.completed event returns that value, so Krokul records the payment on the right deal.
Yes. Paddle subscriptions appear in the MRR movements report with the amounts Paddle holds, next to contracts that Krokul bills itself.
Prices, checkout, tax calculation, invoices to buyers and payouts stay in Paddle. Manually collected Paddle transactions accept USD, EUR and GBP only.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Paddle is a trademark of Paddle.com Market Limited. Krokul is not affiliated with Paddle.
