# NetSuite + Krokul CRM

Yes. Krokul CRM integrates with Oracle NetSuite. Client companies become customer records, won deals become sales orders, and invoices and customer payments posted in NetSuite update the deal in Krokul. The link works through the Krokul app in Zapier and Make, or through NetSuite REST web services paired with the Krokul API and webhooks.

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

## What your team gets

### Customer record keyed by external ID

When a client company is created in Krokul, the connector upserts a NetSuite customer record keyed by an external ID, so a repeated sync updates the same customer. The NetSuite internal ID returns to the Krokul company as its external key.

### Won deal becomes a sales order

A won deal with its lines creates a sales order record in NetSuite with the items, quantities and prices agreed in Krokul. NetSuite then runs fulfilment and billing under your own approval rules.

### Invoices and payments read with SuiteQL

On a schedule, the connector runs SuiteQL queries for invoice and customer payment records changed since the last read. Each invoice links back to its Krokul deal, and each customer payment becomes a payment fact, so sales sees what NetSuite has billed and collected.

### Script push for near real time

Accounts that want faster updates deploy the Krokul User Event script. Its afterSubmit entry point runs when an invoice or payment record is saved and sends the record ID to the Krokul webhook URL through the N/https module. The connector then reads that record at once.

### Item records kept in step

The connector reads NetSuite item records into the Krokul catalogue by internal ID, so every sales order line that Krokul creates points at an item NetSuite already has.

## What moves between NetSuite and Krokul

| NetSuite | Krokul | Direction | When |
|---|---|---|---|
| Customer record | Client company | Krokul → NetSuite | A client company is created or changed |
| Item record | Product | NetSuite → Krokul | Scheduled SuiteQL read |
| Sales order record | Won deal with its lines | Krokul → NetSuite | The deal is won |
| Invoice record | Invoice status on the deal | NetSuite → Krokul | SuiteQL read or the User Event script |
| Customer payment record | Payment fact on the deal | NetSuite → Krokul | SuiteQL read or the User Event script |
| Internal ID | External key of the Krokul record | NetSuite → Krokul | Right after each create |

## How to connect today

### Krokul app in Zapier or Make

1. Connect the Krokul app with a Krokul API key. On Zapier the NetSuite app needs the Zapier Automation SuiteApp, and on Make the NetSuite app needs the Make Enterprise plan.
2. Outbound: the Krokul trigger Company Created runs the NetSuite action Upsert (Create or Update) Record for the customer, and Deal Won runs Create Record for the sales order.
3. Inbound: New Record (Saved Search) on invoices or customer payments ends in a Krokul action such as Record Payment or Create Task.

### Custom flow through the Krokul API and webhooks

1. Give your integration a Krokul API key scoped to client companies, deals and payments, and in NetSuite enable REST Web Services with OAuth 2.0.
2. Subscribe a Krokul webhook to clientCompany.created and card.won, and verify the x-crm-signature header on every delivery before you write to NetSuite.
3. After each NetSuite create, store the internal ID on the Krokul record through externalRef/api-upsert.
4. Read changed invoices and customer payments with SuiteQL on a schedule and post each payment to payment/api-create with the cardUuid of its deal.

**Triggers:** New Record; New Record (Saved Search); New Or Updated Record.

**Actions:** Create Record; Update Record; Upsert (Create or Update) Record; Transform Record; Find Record; Run SuiteQL Query.

### For integrators

NetSuite REST web services cover record CRUD, record transformation, SuiteQL queries and metadata, and Oracle points new integrations to REST with OAuth 2.0. Krokul answers rate limits with 429 and `Retry-After`, signs its webhooks with HMAC-SHA256, and `externalRef/api-upsert` lets a NetSuite script write to Krokul by NetSuite ID without checking first.

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

## Questions and answers

### Does Krokul integrate with Oracle NetSuite?

Yes. Krokul integrates with Oracle NetSuite through the Krokul app in Zapier and Make, and through its API and webhooks.

### Does NetSuite have webhooks?

NetSuite REST web services do not offer a general webhook subscription. Krokul reads changes with SuiteQL, and the optional Krokul User Event script sends a notice to Krokul when a record is saved.

### Should Krokul or NetSuite own the invoice?

NetSuite usually owns invoices, because it posts them to the ledger. Krokul keeps the deal and receives the payment status, so sales sees what is paid without NetSuite access.

### What does the NetSuite administrator need to do?

Enable REST Web Services and OAuth 2.0, create the integration record and give Krokul a role with access to the synced record types. Deploying the optional User Event script needs a role with SuiteScript permissions.

## Limits

NetSuite stays the system of record for fulfilment, invoicing, revenue and the general ledger. NetSuite offers no general webhook subscription, so changes reach Krokul through SuiteQL reads on a schedule or through a Krokul User Event script that you deploy in your account.

## Related services

- [Business Central](https://krokul.com/en/integrations/dynamics-365-business-central/index.md)
- [QuickBooks Online](https://krokul.com/en/integrations/quickbooks-online/index.md)
- [Xero](https://krokul.com/en/integrations/xero/index.md)
- [Sage Accounting](https://krokul.com/en/integrations/sage-accounting/index.md)
- [Avalara](https://krokul.com/en/integrations/avalara/index.md)

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

Oracle and NetSuite are trademarks of Oracle and its affiliates. Krokul is not affiliated with Oracle.

Updated: 2026-10-12

---

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