Set up a manual token-based auth connection to NetSuite

1. Sign into your NetSuite account.
2. Click Setup.
3. Navigate to Company > Integration > SOAP web services preferences > Primary information.
4. Copy Account ID.

Token ID (required): Enter the required token ID. Before creating an access token in NetSuite for integrator.io, verify that you have installed Celigo integrator.io SuiteApp (ID 20038) in your NetSuite account, which creates the role Celigo integrator.io Full Access Role w/o 2FA [Locked].

1. In NetSuite, go to Setup > Users/Roles > Manage roles; then click Customize corresponding to the role Celigo integrator.io Full Access Role w/o 2FA [Locked]; and save the role (clone) with a different name.

Note: Celigo integrator.io Full Access Role w/o 2FA [Locked] is a locked custom Celigo role. When cloning the role, you can add additional permissions to the role to fit your requirements.

2. Navigate to Manage roles to verify the presence of Celigo integrator.io Full Access w/o 2FA [Locked].
3. Go to Manage users, select a user, then click Edit to modify the user.
4. Click the Access subtab at bottom of the screen, then the Roles subtab.
5. Add the custom role that you just created, then click Save.
6. Go to Setup > Access tokens > Create access token. You must reference integrator.io in the Application field for all access tokens used by integrator.io.
7. Copy the Token ID and Token secret to a safe place, since they will not be shown again.

Token secret (required): Enter the value retrieved with your Token ID, above. Multiple layers of protection are in place, including AES 256 encryption, to keep your connection’s Token ID and Secret safe. When editing this form later, you must enter this value again; it is stored only for a saved connection.

iClient (required): Select the iClient pair that stores the client ID and client secret provided to you by NetSuite. To add an iClient and configure your credentials, click the plus (+) button. Click the edit ( ) button to modify a selected iClient. Be sure to give the iClient a recognizable name for use in any other connections.

D. Edit advanced NetSuite settings

Before continuing, you have the opportunity to provide additional configuration information, if needed, for the NetSuite connection.

Link SuiteScript integrator (optional): This setting appears only when you edit a NetSuite connection. Prior to integrator.io, NetSuite integrations built by Celigo ran directly inside your NetSuite account via a managed bundle. If you are still running any of these older integrations, check this box to link integrator.io to your NetSuite account. 

Borrow concurrency from (optional): Select another connection from the list....

Concurrency level (optional): Up to 25 allowed....

WSDL version: New Web Services Description Language (WSDL) versions are available when creating or editing a NetSuite connection. A WSDL is simply an XML document describing the latest versions of a web service. By choosing a WSDL you are choosing to upgrade to a new or older version of NetSuite’s web services.

You can choose between versions 2020.2; 2018.1; and 2016.2. Versions 2018.1; 2020.2; and later support both manual and automatic token-based auth connections. Switching versions for an existing connection might have an impact on running flows, and we recommend reviewing NetSuite’s release notes prior to making a change. We recommend using the latest WSDL version.

Note: Version 2016.2 is the only version that supports a basic auth connection (not recommended).

E. Save and test the connection

Once you have configured the NetSuite connection, you have a few options for continuing:

• Save – click this button to test the connection, commit the new connection so that it will be available to all integrations for your account
• Save & close – click to test and save the connection and exit the Create connection pane
• Cancel – click to exit without saving any new changes
• Test connection – click this button to verify that your new connection is free of errors

When you test or save the connection, it is verified before continuing. 

The new connection is now successfully added to your account. It will be applied to the current source or destination app, if you created it within a flow. Otherwise, you may proceed to register the connection with an integration.