# Zoho Books + Krokul CRM

Yes. Krokul CRM integrates with Zoho Books, the accounting app. Client companies become Zoho Books customers and Krokul quotes become estimates. Issued invoices go to Zoho Books, and customer payments recorded there settle the invoice on the deal. The path runs through the Krokul app in Zapier, Make, n8n and Albato, or through the Krokul API and webhooks.

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

## What your team gets

### Customer created once, reused on every invoice

A new client company in Krokul becomes a Zoho Books contact of type customer, with billing address, email and currency. The Zoho Books contact ID stays on the client company, so every estimate and invoice for that client goes to the same customer.

### Quote in Krokul, estimate in Zoho Books

A quote issued in Krokul is written to Zoho Books as an estimate with the same items and rates. If your team emails documents from Zoho Books, the client receives the estimate from there, and the Krokul quote keeps the estimate number.

### Invoice from the won deal

Once the deal is won and the invoice is issued, the connector creates the Zoho Books invoice for the linked customer. Any item that Zoho Books lacks is created first from the Krokul catalogue with the same name and rate.

### Invoice changes posted back to Krokul

A Zoho Books workflow rule on invoices calls the Krokul webhook URL from the connector page, with a secret token. When an invoice is edited, voided or paid, Krokul reads it through the API and updates the invoice status on the deal.

### Customer payments on the deal

Krokul reads customer payments from Zoho Books and records each one against the invoices it was applied to. The client company debt in Krokul matches Zoho Books, and `invoice.paid` fires when an invoice is covered.

## What moves between Zoho Books and Krokul

| Zoho Books | Krokul | Direction | When |
|---|---|---|---|
| Contact (customer) | Client company | Krokul → Zoho Books | A client company is created or changed |
| Item | Product or service | Krokul → Zoho Books | Before the first line that uses it |
| Estimate | Quote (document) | Krokul → Zoho Books | A quote is issued in Krokul |
| Invoice | Invoice (document) | Krokul → Zoho Books | An invoice is issued in Krokul |
| Invoice (workflow rule webhook) | Invoice status on the deal | Zoho Books → Krokul | The invoice is edited, voided or paid |
| Customer payment | Payment fact on the invoice | Zoho Books → Krokul | A payment is recorded in Zoho Books |

## How to connect today

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

1. Connect the Krokul app with a Krokul API key.
2. Use a Krokul trigger such as Company Created or Document Created with a Zoho Books action such as Create Customer, Create Item or Create Sales Invoice.
3. Start the other way from New Estimate or New Sales Invoice in Zoho Books when a document made there should appear as an activity on the Krokul deal.

### Custom flow through the Krokul API and webhooks

1. Give your integration a Krokul API key scoped to client companies, documents and payments.
2. Subscribe a webhook to clientCompany.created and document.created, and check the x-crm-signature header of every delivery with your secret.
3. Write the customer, estimate or invoice through the Zoho Books API in the data center of your organisation, then link each Zoho Books ID to its Krokul record with externalRef/api-upsert.
4. When a Zoho Books workflow rule reports a payment, call payment/api-create with the cardUuid of the deal so the invoice in Krokul closes.

**Triggers:** New Customer; New Estimate; New Sales Invoice; New Item; New Expense.

**Actions:** Create Customer; Create Estimate; Create Sales Invoice; Create Item.

### For integrators

Zoho Books webhooks support POST, PUT or DELETE, a JSON default payload and a secret token, and Zoho Books retries a failed call. The Krokul webhook door checks that token before it queues anything. For your own code, Krokul offers a public API with a Bearer key, signed outgoing webhooks with a delivery log, and `externalRef/api-upsert`, which writes a record by its Zoho Books ID without a lookup first.

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

## Questions and answers

### Does Krokul integrate with Zoho Books?

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

### Does it matter which Zoho Books data center my account uses?

Zoho Books runs separate API domains per region, for example .com, .eu or .in. The connector detects the region at sign-in and calls the matching domain, so you do not set it by hand.

### Why does Zoho Books need a workflow rule?

Zoho Books sends webhooks from workflow rules that you create in its settings. The rule on invoices tells Krokul about edits right away, and customer payments are also read on a schedule, so nothing depends on one channel.

### Which records does Krokul send to Zoho Books?

Customers, items, estimates and invoices. Customer payments and invoice status go the other way, from Zoho Books to Krokul.

## Limits

Bills, expenses, banking and tax filing stay in Zoho Books. The connector calls the Zoho Books API in the data center where your organisation lives, so your accounting data stays in the region you chose in Zoho.

## Related services

- [Xero](https://krokul.com/en/integrations/xero/index.md)
- [QuickBooks Online](https://krokul.com/en/integrations/quickbooks-online/index.md)
- [FreshBooks](https://krokul.com/en/integrations/freshbooks/index.md)
- [Sage Accounting](https://krokul.com/en/integrations/sage-accounting/index.md)
- [NetSuite](https://krokul.com/en/integrations/netsuite/index.md)

[Accounting](https://krokul.com/en/integrations/category/accounting/index.md)

Zoho Books is a trademark of Zoho Corporation. Krokul is not affiliated with Zoho Corporation.

Updated: 2026-10-12

---

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