Yes. Krokul CRM integrates with GoCardless. A won deal sends the client a mandate request, each line of the payment plan is collected as a Direct Debit payment against that mandate, and a confirmed GoCardless payment closes the line in Krokul. It runs through the Krokul app in Zapier and Make, or through the Krokul API and webhooks.
Automation platformsZapierMake
Recurring B2B contracts often run on Direct Debit. When a deal is won, Krokul creates a GoCardless mandate authorisation request for the client company and puts the authorisation link on the deal. The manager sends it with the contract, and the client approves the mandate on the GoCardless page.
GoCardless reports the mandate as active once the client bank accepts it. Krokul saves the Mandate ID on the client company and marks the company as ready for collection, so the next invoice does not wait for paperwork.
Each payment plan line with a date and the method Direct Debit becomes a GoCardless Payment against the active mandate, with the line as reference. Krokul shows the GoCardless state next to it, so the accountant sees what is pending before the charge date.
When GoCardless confirms that the bank collected the money, Krokul records a payment fact on the plan line and fires payment.received. A failed Payment or a cancelled Mandate creates a task for the account manager. If GoCardless says it will retry the charge, Krokul waits for the retry before it creates the task.
| GoCardless | Direction | Krokul | When |
|---|---|---|---|
| Mandate authorisation request | Krokul → GoCardless | Won deal and its client company | The deal is won |
| Mandate (active, cancelled) | GoCardless → Krokul | Mandate state on the client company | GoCardless events for mandates |
| Payment | Krokul → GoCardless | Payment plan line with the method Direct Debit | The plan line is saved with a date |
| Payment confirmed | GoCardless → Krokul | Payment fact closing the line | GoCardless event for payments with the action confirmed |
| Payment failed | GoCardless → Krokul | Task on the deal | GoCardless event for payments with the action failed |
| Refund | GoCardless → Krokul | Refund linked to the payment | A refund is made in GoCardless |
Yes. Krokul integrates with GoCardless through the Krokul app in Zapier and Make, and through its API and webhooks.
GoCardless marks a payment confirmed when the bank has collected it and paid out when the money is on its way to you. You choose one of the two in your flow, and Krokul uses it for every client.
On the client company, as an external key with the mandate state. Every Direct Debit line of that client uses it.
Krokul creates a task for the account manager on the deal. When GoCardless plans a retry, Krokul waits for its result first.
Mandates are authorised by the client on the GoCardless page, and payouts to your bank account stay in GoCardless. Krokul keeps the mandate state on the client company and the collected money on the deal.
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.
GoCardless is a trademark of GoCardless Ltd. Krokul is not affiliated with GoCardless.
