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.
Automation platformsZapierMake
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.
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.
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.
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.
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.
| NetSuite | Direction | Krokul | When |
|---|---|---|---|
| Customer record | Krokul → NetSuite | Client company | A client company is created or changed |
| Item record | NetSuite → Krokul | Product | Scheduled SuiteQL read |
| Sales order record | Krokul → NetSuite | Won deal with its lines | The deal is won |
| Invoice record | NetSuite → Krokul | Invoice status on the deal | SuiteQL read or the User Event script |
| Customer payment record | NetSuite → Krokul | Payment fact on the deal | SuiteQL read or the User Event script |
| Internal ID | NetSuite → Krokul | External key of the Krokul record | Right after each create |
Yes. Krokul integrates with Oracle NetSuite through the Krokul app in Zapier and Make, and through its API and 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.
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.
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.
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.
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.
Oracle and NetSuite are trademarks of Oracle and its affiliates. Krokul is not affiliated with Oracle.