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.
Automation platformsZapierMakeAlbato
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.
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.
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 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.
| Recurly | Direction | Krokul | When |
|---|---|---|---|
| Account (account code) | Krokul → Recurly | Client company, external key | First subscription for the client |
| Subscription with plan code | Krokul → Recurly | Won deal in the subscription pipeline | The deal is won |
| Subscription events (renewed, paused, canceled, expired) | Recurly → Krokul | Read-only subscription and MRR movement | Recurly changes the subscription |
| Charge invoice paid (charge_invoice.paid) | Recurly → Krokul | Payment fact on the deal | An invoice is paid |
| Charge invoice past due (charge_invoice.past_due) | Recurly → Krokul | Task for the account manager | An invoice passes its due date |
| Payment failed | Recurly → Krokul | Activity on the client company | A charge is declined |
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.
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.
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.
Yes. Recurly subscriptions appear in the MRR movements report with the amounts Recurly holds, next to contracts Krokul bills itself.
Recurly keeps plans, payment gateways, card data and dunning. Charge invoice webhooks arrive only on Recurly sites with the Credit Invoices feature turned on.
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.
Recurly is a trademark of Recurly, Inc. Krokul is not affiliated with Recurly.
