# Recurly + Krokul CRM

Yes. Krokul CRM integrates with Recurly. A won deal creates the Recurly account and subscription with the agreed plan, and Recurly then reports renewals, cancellations, paid and past due invoices and failed payments back to the client company in Krokul. Each client has one billing owner, so a contract billed by Recurly never gets a second invoice from Krokul. The link runs through the Krokul app in Zapier, Make or Albato, or through the Krokul API and webhooks.

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

## What your team gets

### The signed deal opens a Recurly subscription

A deal won in the subscription pipeline sends one purchase to Recurly. It carries the account, coded with the Krokul client company, and a subscription with the plan code and quantity from the deal. Recurly returns the account code and subscription ID. Krokul stores both as external keys, so a second save of the same deal changes nothing in Recurly.

### Subscription changes land on the client company

Recurly JSON webhooks carry only the object type, the event type and IDs. On a subscription event such as renewed, paused, canceled or expired, Krokul fetches the subscription from the Recurly API and updates its read-only copy on the client company. The Krokul MRR movements report then counts the change with the amount Recurly holds.

### Paid and past due invoices

When Recurly sends charge_invoice.paid, Krokul records a payment fact against the deal that started the subscription. A charge_invoice.past_due event goes to the account manager as a task with the invoice number and balance. Recurly keeps collecting through its own dunning.

### A failed card payment reaches the account owner

A payment notification with the failed event type adds an activity to the client company. The account manager sees the failed charge next to open deals and recent calls. That context matters before an upsell.

## What moves between Recurly and Krokul

| Recurly | Krokul | Direction | When |
|---|---|---|---|
| Account (account code) | Client company, external key | Krokul → Recurly | First subscription for the client |
| Subscription with plan code | Won deal in the subscription pipeline | Krokul → Recurly | The deal is won |
| Subscription events (renewed, paused, canceled, expired) | Read-only subscription and MRR movement | Recurly → Krokul | Recurly changes the subscription |
| Charge invoice paid (charge_invoice.paid) | Payment fact on the deal | Recurly → Krokul | An invoice is paid |
| Charge invoice past due (charge_invoice.past_due) | Task for the account manager | Recurly → Krokul | An invoice passes its due date |
| Payment failed | Activity on the client company | Recurly → Krokul | A charge is declined |

## How to connect today

### Krokul app in Zapier, Make or Albato

1. Connect the Krokul app with a Krokul API key.
2. From the Krokul trigger Deal Won, call Create Account in Zapier or Create an Account in Make, or use Create subscription in Albato for the plan of the deal.
3. In the other direction, start from New Subscription, New Invoice or New Transaction in Zapier, or Watch Transactions in Make, and finish with the Krokul actions Record Payment or Add Activity.

### Custom flow through the Krokul API and webhooks

1. Create a Recurly private API key and a JSON webhook endpoint. In Krokul, issue an API key scoped to deals, client companies and payments.
2. Subscribe a Krokul webhook to card.won with a pipelineUuid filter on the subscription pipeline, and verify x-crm-signature on each delivery.
3. Create the Recurly purchase for that deal and save the account code and subscription ID through externalRef/api-upsert.
4. On each Recurly webhook, check recurly-signature, fetch the object by its ID, find the deal with externalRef/api-resolve and write payment/api-create with its cardUuid or activity/api-create.

**Triggers:** New Account; New Subscription; New Invoice; New Transaction; Push Notification; Watch Accounts; Watch Transactions; Invoice paid.

**Actions:** Create Account; Update Account; Create an Account; Create subscription; Create Invoice.

### For integrators

Recurly signs JSON webhooks with an HMAC-SHA256 value in the recurly-signature header, using a secret per endpoint, and also supports HTTP Basic credentials. XML payloads carry no signature. Recurly retries a failed delivery up to ten times with growing intervals. On the Krokul side, externalRef/api-upsert ties the account code to the client company, signed webhooks keep a delivery log, and a sandbox company carries test subscriptions.

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

## Questions and answers

### Does Krokul integrate with Recurly?

Yes. Krokul integrates with Recurly through the Krokul app in Zapier, Make and Albato and through its API and webhooks, for accounts, subscriptions, invoices and payments.

### Krokul bills subscriptions too. Which system invoices a client?

One of them, set per client company. When Recurly owns billing, Krokul reads the subscription and its invoices. When Krokul owns billing, the Krokul contract issues the period invoices and no Recurly subscription exists for that client.

### Why does Krokul call Recurly after each webhook?

Recurly JSON notifications contain the object type, event type and IDs only. Krokul reads the current subscription, invoice or payment from the Recurly API before it changes anything.

### Do Recurly subscriptions count in the Krokul MRR report?

Yes. Recurly subscriptions appear in the MRR movements report with the amounts Recurly holds, next to contracts Krokul bills itself.

## Limits

Recurly keeps plans, payment gateways, card data and dunning. Charge invoice webhooks arrive only on Recurly sites with the Credit Invoices feature turned on.

## Related services

- [Chargebee](https://krokul.com/en/integrations/chargebee/index.md)
- [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)

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

Recurly is a trademark of Recurly, Inc. Krokul is not affiliated with Recurly.

Updated: 2026-10-15

---

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