Always set up and test Netsuite integration in a sandbox environment first before moving to production. Apply all steps in the sandbox and only move to production if all expected results are achieved and errors are fixed.

 

Step 1. Enable Web Services access in your NetSuite instance

Start by enabling API Access and Token-based Authentication in NetSuite. Go to Setup > Company > Enable Features > SuiteCloud

Under the SuiteCloud tab, check the Client SuiteScript and Server SuitScript checkboxes.

Under the SuiteTalk (Web Services) section, check the SOAP Web Services and REST Web Services checkboxes. Under the Manage Authentication section, check the Token-based Authentication and OAuth 2.0 checkboxes.

You can also refer to the NetSuite documentation on enabling the Token-based Authentication feature.

 

Step 2. Install SuiteApp

Head over to the NetSuite SuiteApp Marketplace to install “Workato” SuiteApp. You must be an administrator of the NetSuite account or have the SuiteApp Marketplace permission to complete this step.

After you have installed the Workato SuiteApp, you should see two new integration records appear in your account, Workato-Production  and Workato-Preview

These represent integration records for Workato's two environments where Workato-Production is what you should always use.

Step 3. Create an integration role with required permission levels for your integration

We recommend that you create a separate integration role just for your integrations. This integration role must have permission to read and write to the records relevant to your integrations. This integration role also must have the ability to log in through REST or SuiteTalk (web services).

In NetSuite, create an integration role by navigating to

Setup > Users/Roles > Manage Roles > New

Please find below the necessary permissions we need to have available for the integration:

 

Make sure that in the “Subsidiary Restrictions” section you have “All” selected from the options provided.

 

 

Assign token-based authentication permissions to the integration role

• Access Token Management
• User Access Tokens
• Log in using Access Tokens

Rydoo requires the login using Access Tokens permission at a minimum to enable the user to authenticate through token-based authentication. If you plan for the integration user to be able to create and revoke access tokens for their use, you can give the role the User Access Tokens permissions. We recommend that the integration user not have the Access Token Management permissions for better security maintenance.

Under Permissions > Setup, add the Login using Access Tokens permission with a Full level.

Step 4. Set up an integration user

After you set up our integration role, we need to assign this role to our integration user. We recommend creating a separate user for your integrations.

In NetSuite, go to Setup > Users/Roles > Manage Users to edit an existing user or create a new user.

 

 

When editing a user, under the Access tab, ensure you assign this user the integration role you created/edited in the preceding step.

 

Step 5: Create an access token

You can now create an access token for the integration user. Go to Setup > Users/Roles > Access Tokens > New.

In NetSuite, go to Setup > Users/Roles > Access Tokens > New

For the various inputs:

1. Application Name - Workato-Production
2. User - The user you created in Step 4
3. Role - The role you created in Step 3, and where you assigned the user in Step 4.
4. Token Name - You can use NetSuite's default name or provide one that suites your needs.

After clicking save, record the token ID and token secret somewhere and keep it confidential - these
will not be retrievable again from NetSuite. These will be used for connecting to NetSuite.

Step 6: Configure your Rydoo account and share requested information with Rydoo

To Continue please follow the steps from the next article by clicking on the bellow link: 

NetSuite 2.0 - Rydoo Setup