NetSuite connector installation guide

This guide will walk you through setting up the NetSuite connector in Windsor.ai to sync your NetSuite data.

Before you begin, ensure you have:

• A NetSuite account with administrator access
• Access to the NetSuite Setup menu
• Permission to create integrations, roles, and access tokens

If you don’t already have a NetSuite account:

1. Sign up for a NetSuite account at NetSuite.com.

2. Complete the account setup process.

3. Note your Realm (Account ID) – this can be found in your NetSuite URL or account settings:

• Production accounts: Numeric ID (e.g., 2344535)
• Sandbox accounts: Numeric ID with suffix (e.g., 2344535_SB1)

Step 2.1: Enable token-based authentication

1. Log in to your NetSuite account.

2. Navigate to Setup → Company → Enable Features.

3. Go to the SuiteCloud tab.

4. Enable Token-Based Authentication.

5. Save your changes.

Step 2.2: Create integration

1. Go to Setup → Integrations → Manage Integrations → New.

2. Fill in the following fields:

• Name: Enter a descriptive name (e.g., windsor-ai-integration)
• State: Select Enabled.
• Token-based authentication: Check this box.

3. Click Save.

4. After saving, you will see:

• Consumer Key – Copy this value (you’ll need it later)
• Consumer Secret – Copy this value (you’ll need it later)

Important: Store these credentials securely – the Consumer Secret will only be shown once.

Step 2.3: Note your Realm (Account ID)

Your Realm (Account ID) can be found in several ways:

1. From URL: Look at your NetSuite URL – it will contain your account ID:

• Production: https://[ACCOUNT_ID].app.netsuite.com
• Sandbox: https://[ACCOUNT_ID]-SB1.app.netsuite.com

2. From Setup Menu: Go to Setup → Company → Company Information → Company ID.

3. Format:

• Production: Numeric only (e.g., 2344535)
• Sandbox: Numeric with suffix (e.g., 2344535_SB1)

Step 2.4: Create Integration Role

1. Go to Setup → Users/Roles → Manage Roles → New.

2. Fill in the role details:

• Name: Enter a descriptive name (e.g., windsor-ai-integration-role)
• ID: Enter a unique ID (e.g., WINDSOR_AI_INTEGRATION_ROLE)

3. Scroll down to the Permissions tab:

• (REQUIRED) Click on Transactions and manually add all the dropdown entities with either full or view access level
• (REQUIRED) Click on Reports and manually add all the dropdown entities with either full or view access level
• (REQUIRED) Click on Lists and manually add all the dropdown entities with either full or view access level
• (REQUIRED) Click on Setup and manually add all the dropdown entities with either full or view access level

4. Save changes.

Important notes:

– Make sure you’ve completed all REQUIRED steps correctly to avoid sync issues;

– If you rename or customize any Object in NetSuite, you must edit these permissions again for the integration role to reflect such changes.

Step 2.5: Set up User

1. Go to Setup → Users/Roles → Manage Users.

2. In the Name column, click on the user’s name you want to give access to the integration role.

3. Click the Edit button under the user’s name.

4. Scroll down to the Access tab at the bottom.

5. Select from the dropdown list the integration role you created in Step 2.4 (e.g., windsor-ai-integration-role).

5. Save changes.

Step 2.6: Create Access Token for Role

1. Go to Setup → Users/Roles → Access Tokens → New.

2. Select an Application Name (the integration you created in Step 2.2).

3. Under User, select the user you assigned the integration role to in Step 2.5.

4. Inside Role, select the role you gave to the user in Step 2.5.

5. Under Token Name, enter a descriptive name (e.g., windsor-ai-rest-integration-token).

6. Save changes.

7. After saving, Token ID and Token Secret will be displayed once – copy them to a safe place immediately.

Important: The Token Secret will only be shown once. If you lose it, you’ll need to create a new access token.

Log in to your Windsor.ai account.

2. Navigate to Data Sources in the left-hand bar.

3. Find NetSuite in the list.

4. Fill in the connector configuration form with the following fields.

NetSuite configuration fields:

Realm (Account ID)

• Enter your NetSuite Realm (Account ID)
• Production example: 2344535
• Sandbox example: 2344535_SB1
• Format: Numeric for production, or numeric with _SB1, _SB2, etc. for sandbox

Consumer Key

• Enter the Consumer Key from Step 2.2
• Format: 32-64 alphanumeric characters
• Example: a123b456c789d0e1f2g3h4i5j6k7l8m9n0

Consumer Secret

• Enter the Consumer Secret from Step 2.2
• Format: 32-64 alphanumeric characters
• Example: a123b456c789d0e1f2g3h4i5j6k7l8m9n0

Token Key (Token Id)

• Enter the Token ID from Step 2.6
• Format: 32-64 alphanumeric characters
• Example: a123b456c789d0e1f2g3h4i5j6k7l8m9n0

Token Secret

• Enter the Token Secret from Step 2.6
• Format: 32-64 alphanumeric characters
• Example: a123b456c789d0e1f2g3h4i5j6k7l8m9n0

Record Types

• Enter the NetSuite record types you want to sync
• Format: Comma-separated list of record type names
• Examples: customer, salesorder, invoice, item, transaction
• You can find available record types in the NetSuite Records Browser

Common record types include:

• customer – Customer records
• salesorder – Sales orders
• invoice – Invoices
• item – Items/products
• transaction – General transactions
• employee – Employee records
• vendor – Vendor records

5. Click Save or Connect to complete the setup.

The available NetSuite record types depend on:

• Your NetSuite account configuration
• The permissions granted to the integration role
• The record types enabled in your NetSuite account

To find available record types:

1. Log in to NetSuite.
2. Navigate to Customization → Scripting → Script Records → New.
3. Or visit the NetSuite Records Browser.

Common record types that can be synced include:

• account
• contact
• customer
• employee
• invoice
• item
• salesorder
• transaction
• vendor

Note: Ensure your integration role has the necessary permissions for the record types you want to sync (as configured in Step 2.4).

• The connector is subject to NetSuite’s API rate limits and concurrency restrictions
• NetSuite enforces concurrency limits per integration
• Large data sets may take longer to sync
• Consider syncing record types during off-peak hours for better performance

• NetSuite SuiteTalk REST Web Services Documentation
• NetSuite Records Browser
• NetSuite Token-Based Authentication Guide
• Windsor.ai Documentation