Yes. Krokul CRM integrates with Chargebee and keeps one billing owner per client. When Chargebee owns the subscription, a won deal creates it in Chargebee and Krokul reads status, renewals, cancellations and payments. When Krokul owns it, the Krokul contract issues the period invoices and Chargebee collects them from the stored card. The link runs through the Krokul app in Zapier, Make, n8n or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
A deal won in a subscription pipeline creates the Chargebee customer and the subscription with the item prices agreed in the deal. From then on Chargebee owns the plan, and Krokul shows it on the client company as read-only, with its status and next billing date.
Chargebee webhooks such as subscription_changed, subscription_renewed and subscription_cancelled update the Krokul copy of the subscription. When Chargebee schedules a cancellation, Krokul creates a task for the account manager before the end date, and the Krokul MRR report counts it with the amounts Chargebee holds.
When the subscription lives in Krokul, the contract issues an invoice for each period. The connector creates a matching one-off copy in Chargebee for the same customer, Chargebee charges the stored card, and the payment lands on the Krokul invoice as a payment fact.
In both variants, payment_succeeded becomes a payment fact in Krokul, and payment_failed adds an activity for the person who owns the client. Chargebee keeps its own dunning, and the manager sees in Krokul why a renewal may be at risk.
| Chargebee | Direction | Krokul | When |
|---|---|---|---|
| Customer | Krokul → Chargebee | Client company | First billing for the client |
| Subscription | Krokul → Chargebee | Won deal with the agreed plan | The deal is won (Chargebee owns billing) |
| Subscription status, renewal, cancellation | Chargebee → Krokul | Read-only subscription and MRR on the client | subscription_changed, subscription_renewed, subscription_cancelled |
| Invoice | Krokul → Chargebee | Period invoice of the Krokul contract | The contract issues a period invoice (Krokul owns billing) |
Payment (payment_succeeded) | Chargebee → Krokul | Payment fact on the invoice and deal | A charge succeeds |
Payment failure (payment_failed) | Chargebee → Krokul | Activity for the client owner | A charge fails |
Yes. Krokul integrates with Chargebee through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.
You choose per client. With Chargebee as owner, Chargebee runs the subscription and Krokul reads it. With Krokul as owner, the Krokul contract issues invoices and Chargebee only collects payment. A client never has both.
Yes. Subscriptions owned by Chargebee count in the Krokul MRR report with the amounts Chargebee holds, next to the contracts that Krokul bills itself.
Yes, at the end of a billing period. The connector closes the subscription on one side and starts it on the other, so the client is not charged twice for the same period.
A client is never billed by both systems. The connector does not start a Chargebee subscription for a client whose Krokul contract is active, and the reverse. Dunning and payment retries stay in Chargebee in both variants.
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.
Chargebee is a trademark of its owner. Krokul is not affiliated with Chargebee.
