NetSuite connector

The NetSuite connector gives a Neblex workflow or agent governed access to a NetSuite account: read records with SuiteQL and saved searches, write and update any record type the role permits, and use NetSuite's own record transformation model to turn a sales order into an invoice or an item fulfillment without rebuilding the record by hand.

• Works against production, sandbox, and Release Preview accounts, switched per connection
• Reads the record and field metadata catalog at connection time, so custom records, custom fields, and custom segments appear with no manual mapping file
• Every call is queued against the account's concurrency limit, so a burst of workflow steps does not trip governance for the rest of the account
• One connector powers deterministic workflows, agent tool calls, and scheduled sync jobs, all in the same run log

The three jobs this connector is picked for most often, and what each one gets you.

• Run order-to-cash without rekeying.
• Get NetSuite data out on a schedule.
• Give finance an assistant with guardrails.

A real flow finance teams turn on early, with the actual field-level detail.

Approved CRM opportunity to a posted NetSuite invoice, with a value gate

A closed-won opportunity in the CRM becomes a NetSuite customer, sales order, and invoice. Orders above a threshold pause for controller approval before anything posts.

1. 1Trigger: CRM Opportunity moves to Closed Won, passing the account, contact, line items, and Amount.
2. 2Customer: Upsert record on customer, keyed on external ID crm_account_id, mapping account.name → companyName, account.billing_country → addressbook.country, account.terms → terms, account.subsidiary_code → subsidiary.
3. 3Gate: if Amount is 50,000 or more, send an approval to the controller with the order summary. On reject, stop and post the reason back to the opportunity. On approve, continue.
4. 4Order: Create record on salesOrder, mapping entity from the upserted customer, otherRefNum → PO number, and each opportunity line to an item sublist line with line.sku → item, line.quantity → quantity, line.unit_price → rate.
5. 5Invoice: Transform record from the sales order to invoice, so NetSuite carries the lines and tax forward under its own rules.
6. 6Close the loop: write the NetSuite invoice internal ID and tran ID back to the opportunity, and post the invoice link to the deal channel in Slack.

Common patterns other teams start from with this connector.

• Quote-to-cash sync. Closed-won opportunities flow from the CRM to CPQ to NetSuite billing automatically, with no rekeying between systems. (Sales and RevOps)
• Store order to ERP. Paid Shopify orders become NetSuite sales orders, with new shoppers created as customers and fulfillment status flowing back to the store. (E-commerce ops)
• Payment reconciliation. Every paid Stripe invoice is matched to its open NetSuite invoice and recorded as a customer payment, with unmatched items queued for review. (Finance)
• ERP to warehouse. Transactions, balances, and custom records sync into Snowflake on a schedule, with an incremental filter on the last modified date. (Data)

All standard record types the connected role can access are supported. Custom records, custom fields, and custom segments are picked up from the metadata catalog at connection time.

Commonly used standard records

Customer, Contact, Vendor, Sales Order, Invoice, Cash Sale, Estimate, Item Fulfillment, Purchase Order, Vendor Bill, Credit Memo, Customer Payment, Journal Entry, Inventory Item, Non-Inventory Item, Assembly Item, Subsidiary, Employee

Custom records (any

customrecord

type) and custom fields behave identically to standard records across every operation above, including SuiteQL joins and the transform action where NetSuite defines a transformation.

The connection runs as a NetSuite role, so access is exactly what that role's permissions and restrictions allow, and no more.

• OAuth 2.0 or Token-Based Auth. OAuth 2.0 for interactive setup, Token-Based Authentication for unattended server-to-server connections. No password storage.
• Role and restriction aware. Reads and writes respect the role's permission level per record type, plus subsidiary, department, and class restrictions on the employee behind the role.
• IP and token controls. Compatible with NetSuite IP address rules and per-integration token management, so a connection can be revoked without touching the others.
• Full audit trail. Every record read, write, and transform, with the payload and the NetSuite internal ID, flows into the same Neblex audit trail as every other connector.

The shape of the vendor's limits, as published at the time of writing. Verify the exact figures for your plan; they change without notice. Neblex honors the vendor's own rate-limit and retry signals and backs off within them.

• Concurrent requests are capped by your account's concurrency governance, which varies by service tier and SuiteCloud licenses. The connector queues and paces calls to stay under it
• SuiteQL and saved-search reads return up to 1,000 rows per page before pagination
• RESTlet calls are bounded by SuiteScript governance units per script execution
• File attachments through REST are capped around 10 MB inline, with larger files routed through the File Cabinet
• Exponential backoff and retry are applied automatically on SSS_REQUEST_LIMIT_EXCEEDED and concurrency rejections