Provides integration into NetSuite via its SOAP API.

Revision History Initial Release

2020.1.0.1 Updated signature method

2020.1.0.2 Updated signature algorithm

2020.1.0.3 Added MaxReceivedMessageSize on request



Type: Connection Input
The Connection Property

Type: String
The location of your NetSuite, for example

Type: String
NetSuite account number. Note that for sandbox accounts, the account number should usually end with _SB1 (case sensitive and using an underscore rather than a dash) and should not be specified as -sb1 as may be assumed from the URL.

Type: Password
NetSuite consumer key

Type: Password
NetSuite consumer secret

Type: Password
NetSuite token ID

Type: Password
NetSuite token secret


Type: String Input
The name of the operation to be performed. This will be set automatically when you load a Node Sample.


Type: String Input
The type of record that will be used for the operation. This will be set automatically when you load a Node Sample.


Type: String Input
Specifies preferences for handling the request. Although this Property will be set automatically when a Node Sample is loaded, it can be left blank unless the default preferences need to be customised.


Type: String Input
The Request Property
The primary request payload for the operation. A sample of this document will be set automatically when you load a Node Sample. To prepare it for use, either hardcode values into the document or generate using QuickMap.


Type: String Output
The result returned by NetSuite.

Custom Inputs

Loading certain Node Samples will cause Custom Input Properties to be added to the Node.


This Node is a wrapper around the NetSuite SOAP API and makes it possible to interact with NetSuite without additional code. Refer to for detail on the specific calls that are implemented.

When querying data from Netsuite, the Preferences value indicates the number of records to be returned in a page. In order to get the next page of data, one has to execute the "SearchMoreWithId" function of the Netsuite node, passing it the next page number, and the searchId returned by the initial call, as shown in the paging sample below.

MaxReceivedMessageSize will be set on the request and will be the same value as the Max Data Size on the Connection under the advanced properties.


See for a set of examples.

See for an example of paging a result set.

Did this answer your question?