NetSuite Connector Reference

Whether you are using NetSuite as a data source (take a new NetSuite contact and copy it to Salesforce, for example) or a data target (when a Salesforce opportunity closes, create a NetSuite sales order), the details of how to work with data in a flow are specific to the data source or data target.

Connection Details

When connecting to NetSuite via MuleSoft Composer, in NetSuite:

  • Ensure that token-based authentication is enabled by navigating to Setup > Integration Management > Manage Integration > Authentication.

  • Ensure that the role used in the integration is not using two-factor authentication by navigating to Setup > User/Roles > Two-Factor Authentication Roles.

To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.

This system requires the following credential information for its connections:

Connection Name

Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.

Only you can see the connection. Other users in your Composer app must create their own connections.

You must connect to NetSuite as a regular user (WSU), not a concurrent user (cWSU).

Connection Display Name

The connection display name is a unique name that you choose to identify the connection.


The account ID as listed in your NetSuite instance by accessing Setup > Integration > SOAP Web Services Preferences. The value is a string of letters and numbers, for example: TESTME1234567.

Always enter the letters in upper case.

Consumer Key

The consumer key generated in NetSuite by accessing Setup > Integration > Manage Integrations

Consumer Secret

The consumer secret generated in NetSuite along with the consumer key

Token ID

The token ID generated in NetSuite

Token Secret

The token secret generated with the token ID in NetSuite


The value can’t be edited at this time.

Establish a NetSuite Connection

To use MuleSoft Composer to establish a NetSuite connection, you must have:

  • The MuleSoft Composer User permission set to perform integration tasks.

  • An account in Salesforce to store the internal ID of the associated customer in NetSuite. You must ensure that a custom field, NetSuite ID, has been created for the Account object in the organization.

Run Server SuiteScript to Trigger Workflows

If your NetSuite configuration preferences are set to run server SuiteScript and trigger workflows, the following criteria are required:

  • The Audience field must have all roles selected.

  • The Execute As Role field must be set to Administrator.

  • The Log Level field must be set to Debug.


Each flow starts with a scheduler that specifies a time span for how frequently the flow starts or with a trigger that you define, such as "each time a new record is created." Triggers provide multiple options related to the data in your system.

Triggers execute every ten minutes.

This system provides the following trigger options:

On Updated Records

A record is created, or an existing record is updated.

On New Records

A new record is created in NetSuite.


After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs, such as copying a record from Workday to Salesforce. The actions you can perform depend on which system you are connected to.

This system provides the following actions:

Update Record

A record is changed.

Create Record

A record is created.

Upsert Record

A record is created or updated.

Delete Record

A record is deleted

Get Records

Returns a list of up to 500 records based on specific search criteria. The following fields are required:

  • Object type

  • Filter records

Record Types

The following record types are supported.

  • Triggers

    • Contact

    • Customer

    • Employee

    • Inventory Item

    • Invoice

    • Sales Order

    • Support Case

    • Custom Record Types

  • Actions

    The following record types are valid for all actions:

    • Contact

    • Customer

    • Customer Refund

    • Employee

    • Inventory Item

    • Invoice

    • Payment Item

    • Sales Order

    • Support Case

    • Custom Record Types

  • Objects

    • CreditMemo

    • CustomerDeposit

    • CashSale

    • CashRefund

    • CustomerPayment

    • CustomerRefund

    • Journal Entry

    • Opportunity

    • Estimate

    • NonInventoryPurchaseItem

    • NonInventoryResaleItem

    • NonInventorySaleItem

Custom Fields

Using MuleSoft Composer, you can access custom field values for actions and triggers that you set in the NetSuite record.

List Objects

List objects are supported.

Custom Picklists

You can map values to custom picklists using the value name. Internal IDs are not required to map values to custom picklists.

Was this article helpful?

💙 Thanks for your feedback!

Give us your feedback!
We want to build the best documentation experience for you!
Help us improve with your feedback.
Take the survey!