Netsuite documentation: Authentication
One additional NetSuite authentication type is available: token-based (manual). However, if you are installing an integration app or adding a connection to one, you must establish your connection to NetSuite according the integration app’s instructions. For example, see Install Salesforce - NetSuite (IO).
A. Set up a NetSuite connection
Start establishing a connection to NetSuite in either of the following ways:
- From the Resources menu, select Connections. Then, click + Create connection at the top right.
– or – - While working in a new or existing integration, you can add an application to a flow simply by clicking Add source or Add destination/lookup.
In the resulting Application list, select NetSuite.
The Create connection pane opens with required and advanced settings.
B. Describe your NetSuite connection
First, name your connection in the General settings:
Name (required): Provide a clear and distinguishable name. Throughout integrator.io imports and exports, you will have the option to choose this new connection, and a unique identifier will prove helpful later when selecting among a list of connections that you’ve created.
Application (required, non-editable): A reminder of the app you’re editing.
C. Supply required NetSuite account information
At this point, you’re presented with options for providing NetSuite authentication.
Authentication type (required): Select Token Based Auth (Automatic).
- Enable the Token-based authentication feature
- Create a copy of the Administrator or Celigo integrator.io Full Access Role w/o 2FA [Locked] roles. 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.
Account ID (required): Enter your account ID. Contact NetSuite support to obtain the ID if it’s not exposed in the following steps:
Note: Make sure you use underscore (_) instead of dash (-) while you enter your account ID. For example, 12345_SB1.
- Sign into your NetSuite account.
- Click Setup.
- Navigate to Company > Integration > SOAP web services preferences > Primary information.
- Copy Account ID.
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 2023.1; 2020.2; and 2018.1. Versions 2018.1 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.
E. Save and test the connection
Once you have configured the NetSuite connection, click Save & authorize. You will then be asked to sign into your NetSuite account to complete the connection.
If NetSuite authorizes your login, the new connection is now successfully added to your account in Online status. 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.
-
The Leader in NetSuite Integrations
Complete Integration Platform (iPaaS) for NetSuite and Beyond
Comments
8 comments
It doesn't work. I had to go into the integrator on the netsuite side in order to get the first connection to work, and then I have to follow instructions from https://cdn2.hubspot.net/hubfs/5812834/Product/SmartConnectors/salesforce-tba.pdf In order to complete step 4 (and these instructions are also outdated - the UI has changed since they were written).
Hi Kenneth Welling, We've got a ticket to revise this and also add other authentication methods for NetSuite connections currently in progress. Sorry for the delayed response.
Tom
Can I use the same tokens for the Integration app NS Connection that I use for a standalone flow NS connection? I would have thought so but when I test the connection it fails.
OK, I learned that there are Integrator.io tokens separate from High Tech Connectors, so that answered my prior question.
Now a better question. The Help Desk staff all (in my experience of 2 times) told me to use the Manual option when I set up the connection for the IA. The V1.6 integration App release notes recommend we use the Automatic option. How do I know which to use, or when to use which one? What are the benefits and desirable situations for the 3 Authentication types you present here?
Hi METER Group, I've passed your question on to some subject matter experts, and when we receive the response, we will notify you of the answer and revise the article. Thanks.
Hi Meter Group,
Token based authentication is preferred over basic authentication as it is more secure. Between the two token based types, we recommend Token based (automatic) as it is both secure and faster (in terms on time to install).
Prior to v1.6 Salesforce NetSuite (IO) integration App release, the recommendation was to create a basic connection, install and verify the NetSuite bundle and then change the authentication type to Token based (manual). This was the recommended path because manual creation of token required the bundle to be installed in NetSuite.
With v1.6, we have an additional option for Token based (automatic). With this option, you can create the token prior to NetSuite bundle installation and verification.
Im doing a basic connection, When i test the connection it works but when i save and close it logs out
Hi, kj semikian. I hope that by now your connection has proved stable after the initial creation and committing the saved changes. If you're still running into problems, I'd invite you to submit a support ticket, so that we can try to reproduce the problem, address the variables, and offer alternative solutions for the authentication type and verifying your NetSuite connection. Thanks.
Please sign in to leave a comment.