# Chargebee + Krokul CRM

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.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### Chargebee owns billing: subscription from the won deal

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.

### Renewals, changes and cancellations read from Chargebee

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.

### Krokul owns billing: Chargebee collects the period invoice

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.

### Payments and failures on the deal

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.

## What moves between Chargebee and Krokul

| Chargebee | Krokul | Direction | When |
|---|---|---|---|
| Customer | Client company | Krokul → Chargebee | First billing for the client |
| Subscription | Won deal with the agreed plan | Krokul → Chargebee | The deal is won (Chargebee owns billing) |
| Subscription status, renewal, cancellation | Read-only subscription and MRR on the client | Chargebee → Krokul | `subscription_changed`, `subscription_renewed`, `subscription_cancelled` |
| Invoice | Period invoice of the Krokul contract | Krokul → Chargebee | The contract issues a period invoice (Krokul owns billing) |
| Payment (`payment_succeeded`) | Payment fact on the invoice and deal | Chargebee → Krokul | A charge succeeds |
| Payment failure (`payment_failed`) | Activity for the client owner | Chargebee → Krokul | A charge fails |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with a Krokul API key.
2. Pair a Krokul trigger such as Deal Won with a Chargebee action such as Create Subscription, or Deal Status Changed with Pause Subscription.
3. Start the other way from a Chargebee trigger such as New Payment or Payment Failure and finish with a Krokul action such as Record Payment or Add Activity.

### Custom flow through the Krokul API and webhooks

1. Issue a Krokul API key whose scopes cover deals, client companies and payments.
2. Register a webhook for card.won with webhook/api-upsert, filtered by the subscription pipeline. Check the x-crm-signature header of each delivery against your secret.
3. On that event, create the Chargebee customer and subscription, and keep the Chargebee IDs on the client company and the deal through externalRef/api-upsert.
4. Point the Chargebee webhook at your receiver: send payment_succeeded to payment/api-create with the cardUuid of the deal, and payment_failed to activity/api-create.

**Triggers:** New Subscription; Subscription Activation; Subscription Cancellation; Subscription Cancellation Scheduled; New Invoice; New Payment; Payment Failure; New Customer.

**Actions:** Create Customer; Update Customer; Create Subscription; Update Subscription; Pause Subscription; Record Offline Payment for an Invoice.

### For integrators

Chargebee events follow the pattern resource and event name, for example `subscription_created`, `invoice_generated` or `payment_succeeded`, and Chargebee retries a failed webhook delivery. The connector treats the event ID as a deduplication key. On the Krokul side, `card/api-create` accepts `externalId` and `externalSystem`, so a repeated event returns the deal it already created, and a sandbox call gives you an empty test company with an API key.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Chargebee?

Yes. Krokul integrates with Chargebee through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.

### Krokul has its own subscriptions. Which one bills the client?

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.

### Does Chargebee MRR appear in Krokul?

Yes. Subscriptions owned by Chargebee count in the Krokul MRR report with the amounts Chargebee holds, next to the contracts that Krokul bills itself.

### Can a client move from one billing owner to the other?

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.

## Limits

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.

## Related services

- [Stripe](https://krokul.com/en/integrations/stripe/index.md)
- [PayPal](https://krokul.com/en/integrations/paypal/index.md)
- [GoCardless](https://krokul.com/en/integrations/gocardless/index.md)
- [QuickBooks Online](https://krokul.com/en/integrations/quickbooks-online/index.md)
- [Xero](https://krokul.com/en/integrations/xero/index.md)
- [Avalara](https://krokul.com/en/integrations/avalara/index.md)

[Payments and banking](https://krokul.com/en/integrations/category/payments/index.md)

Chargebee is a trademark of its owner. Krokul is not affiliated with Chargebee.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs