Skip to main content

Set up a connection to NetSuite

Tom Santiago
  • Updated
Follow

Contents

Authentication Type: Token Based Auth (Automatic)

TokenBasedAuthAutomatic.png
  1. Name: Required: Name the connection.
  2. Connection type: Required: The form will automatically select NetSuite.
  3. Authentication Type: Required: Select Token Based Auth (Automatic).
  4. Environment: Required: Enter the NetSuite environment that you want to connect with. NetSuite supports production, sandbox, and beta environments. Note: Sandbox NetSuite accounts must be provisioned by NetSuite, and beta environments are typically only available in the weeks prior to a large NetSuite upgrade.
  5. Account ID: Required: Enter the account ID. Use the following steps to get an account ID.
    1. Log in to your NetSuite account.
    2. Click Setup > Integration
    3. Click Web Services Preferences to get your account ID.
    4. If this does not work, contact NetSuite support.
  6. iClient: If left blank, you are indicating that integrator.io has your permission to access your NetSuite account via Celigo’s developer keys. Otherwise, if you want to connect with your own developer keys, select an iClient from the list.
  7. Borrow concurrency from (optional): Select another connection from the list....
NOTE: Selecting another app changes form...
  1. Concurrency level (optional): Up to 25 allowed....

Authentication Type: Token Based Auth (Manual)

TokenBasedAuthManual.png
  1. Name: Required: Name the connection.
  2. Authentication Type: Required: Select Token Based Auth (Manual) to use NetSuite's token-based manual authentication.
  3. Environment: Required: Enter the NetSuite environment that you want to connect with. NetSuite supports production, sandbox, and beta environments. Note: Sandbox NetSuite accounts must be provisioned by NetSuite, and beta environments are typically only available in the weeks prior to a large NetSuite upgrade.
  4. Account ID: Required: Enter the account ID. Use the following steps to get an account ID.
    1. Log in to your NetSuite account.
    2. Click Setup > Integration
    3. Click Web Services Preferences to get your account ID.
    4. If this does not work, contact NetSuite support.
  5. Token ID: Enter the required token ID. Before creating an Access Token in NetSuite for integrator.io, verify that you have installed the Celigo integrator.io SuiteApp (i.e. the Bundle with id 20038) in your NetSuite account. This will create the Celigo integrator.io Full Access Role w/o 2FA [Locked] detailed below.
    1. In NetSuite, go to Setup > Users/Roles > Manage Roles; then click Customize corresponding to the Celigo Salesforce Connector TBA Enabled Role role and save the role (clone) with a different name.

      Note: "Celigo Salesforce Connector TBA Enabled Role" is a locked custom Celigo role. When cloning the role, you can add additional permissions to the role to fit your requirements. This role is a part of the Celigo Salesforce Integration App (SmartConnector) version 2.8.0 and above.

    2. Go to Manage Roles to make sure you see the Celigo integrator.io Full Access w/o 2FA [Locked] role.
    3. Go to Manage Users, select user, then click Edit to modify the user. Click the Access subtab at bottom of screen, then Roles subtab. Add that custom role you just created, then Save.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. Copy Token ID and Token Secret to a safe place as you will not be able to get to them again.
  6. Token Secret: Required: Important: before creating an Access Token in NetSuite for integrator.io, verify that you have installed the Celigo integrator.io SuiteApp (i.e. the Bundle with id 20038) in your NetSuite account. You must reference integrator.io in the Application field for all access tokens used by integrator.io.
  7. iClient: If left blank, you are indicating that integrator.io has your permission to access your NetSuite account via Celigo’s developer keys. Otherwise, if you want to connect with your own developer keys, select an iClient from the list.
  8. Borrow concurrency from (optional): Select another connection from the list....
NOTE: Selecting another app changes form...
  1. Concurrency level (optional): Up to 25 allowed....

Authentication Type: Basic

TokenAuthBasic.png
  1. Name: Required: Name the connection.
  2. Authentication Type: Required: Select Basic to use your NetSuite email and password for this connection.
  3. Email: Required: Enter the registered email address of the NetSuite account.
  4. Password: Required: The password is created on account setup.
Read more about this connector:

Related articles

Comments

8 comments

Date Votes
  • Kenneth Welling

    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).

    1
    Comment actions Permalink
  • Tom Santiago

    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

    0
    Comment actions Permalink
  • METER Group

    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.

    0
    Comment actions Permalink
  • METER Group

    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?

    0
    Comment actions Permalink
  • Tom Santiago

    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.

    0
    Comment actions Permalink
  • Docs Support

    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.

    2
    Comment actions Permalink
  • kj semikian

    Im doing a basic connection, When i test the connection it works but when i save and close it logs out 

    0
    Comment actions Permalink
  • Stephen Brandt

    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. 

    0
    Comment actions Permalink

Please sign in to leave a comment.