NetSuite connector

The NetSuite connector gives a Neblex workflow or agent access to a NetSuite account through SuiteTalk REST: read records with SuiteQL and SuiteAnalytics datasets, write and update any record type the role permits, and use NetSuite's own record transformation 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, one connection each
• Describe a record type and List record types read the metadata on demand, including custom records and custom fields
• Upsert by external ID makes a write safe to repeat: a re-fired trigger updates the record instead of creating a second one
• One connector powers deterministic workflows, agent tool calls, and scheduled sync jobs, all in the same run history

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

• Run order-to-cash without rekeying. A won deal or a paid order becomes a NetSuite customer, sales order, and invoice, with large orders approved by a person first.
• Get NetSuite data out on a schedule. SuiteQL queries load transactions and balances into a warehouse incrementally, on the last modified date.
• Give finance an assistant with guardrails. An AI agent answers questions from SuiteQL reads, while anything that writes waits for a person to approve it.

A real flow finance teams turn on early, with the actual step-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. 1
   Trigger: the CRM opportunity trigger fires on a new or changed opportunity, and a Filter continues only when it is Closed Won.
2. 2
   Customer: Upsert a customer keyed on an external ID from the CRM account, mapping account.name → companyName, account.billing_country → addressbook.country, account.terms → terms, account.subsidiary_code → subsidiary.
3. 3
   Gate: if Amount is 50,000 or more, a Wait for form step sends the controller an approval task with the order summary. On reject, stop and post the reason back to the opportunity.
4. 4
   Order: Upsert a sales order keyed on the opportunity ID, mapping entity from the customer, otherRefNum → PO number, and each opportunity line to an item line with line.sku → item, line.quantity → quantity, line.unit_price → rate.
5. 5
   Invoice: Transform a record from the sales order to invoice, so NetSuite carries the lines and tax forward under its own rules.
6. 6
   Close the loop: write the NetSuite invoice internal ID and number 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, 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 sent to a person 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, through typed operations for the common records and generic record operations for the rest.

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 work through the generic record operations, SuiteQL joins, and the transform operation where NetSuite defines a transformation.

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

• OAuth 2.0 machine to machine. The connection uses your account ID, the integration's client ID, and a certificate ID with its private key. No password is stored.
• Role and restriction aware. Reads and writes respect the role's permission level per record type, plus subsidiary, department, and class restrictions.
• Encrypted credentials. The private key is stored encrypted and never shown again after you save the connection.
• Run history. Every run shows each step's status and errors; record data from successful runs is kept when the flow is set to keep run data for replay.

The shape of NetSuite's limits, as published at the time of writing. Verify the exact figures for your account; they change without notice.

• Concurrent requests are capped by your account's concurrency governance, which varies by service tier and SuiteCloud licenses. Use Process in chunks for large loads, and turn on Retry on failure so a step rejected for concurrency tries again with backoff
• SuiteQL 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