NetSuite SOAP Setup Guide

Overview

This connector uses NetSuite SOAP web services with token-based authentication (TBA) to sync saved searches: reusable search definitions that can include advanced filters and result layout. A user may save a search while running it or define it independently; NetSuite stores it the same way in either case.

---

Prerequisites

• A NetSuite administrator (or delegated admin) who can enable SuiteCloud features, create integrations and roles, and issue access tokens.
• SuiteTalk (SOAP Web Services) available for the account, and Token-Based Authentication enabled at the company level.
• A role that can use Web Services and Log in using Access Tokens, plus permissions for the record types and saved searches you intend to sync.

---

Setup Guide

1. Confirm SOAP web services and gather Account ID

1. In NetSuite, go to Setup > Integration > SOAP Web Services Preferences (or your account’s documented equivalent).
2. Note your Account ID for Matia.

2. Enable Token-Based Authentication

1. Go to Setup > Company > Enable Features.
2. Open the SuiteCloud tab.
3. Under SuiteScript, enable Client SuiteScript and Server SuiteScript as required by your account policies; accept terms if prompted.
4. Under Manage Authentication, enable Token-Based Authentication and accept terms if prompted.
5. Click Save.

3. Create an integration record

1. Go to Setup > Integration > Manage Integrations > New.

2. Name the integration (for example MatiaSoapSavedSearch).

3. Set State to Enabled.

4. Open the Authentication tab, enable Token-based Authentication, and disable other authentication mechanisms you do not intend to use.

5. Save and copy the Consumer Key and Consumer Secret immediately.

   IMPORTANT: Treat consumer credentials like passwords. After you leave the page you cannot view the consumer secret again.

4. Create a role for Web Services and saved searches

1. Go to Setup > Users/Roles > Manage Roles > New.
2. Name the role (for example MatiaSoapRole).
3. On the Permissions tab, under Setup, include at least:
   • Log in using Access Tokens
   • Web Services
4. Add Lists, Reports, Transactions, or other subtabs your saved searches touch (match the record types and reports users can run interactively). Under-granting permissions causes saved searches to return partial or empty results.
5. Save the role and note its Internal ID from Manage Roles—this is the Role ID Matia needs.

5. Assign the role to a user

1. Go to Setup > Users/Roles > Manage Users and open the user that will own the integration token.
2. Ensure Give Access is checked on the Access tab.
3. Add the role you created under Roles.
4. Save.

6. Create an access token

1. As an administrator or a user with Access Token Management, go to Setup > Users/Roles > Access Tokens > New.

2. Select your integration, user, and the role created above.

3. Save and copy Token ID and Token Secret.

   IMPORTANT: Store token secrets securely; they cannot be retrieved later.

7. Finish configuration in Matia

1. Enter Account ID, Role ID, Consumer Key, Consumer Secret, Token ID, and Token Secret.
2. Enter an Asset Name to identify this NetSuite SOAP source.
3. (Optional) Enter a Description.
4. (Optional) Assign Tags.
5. (Optional) Select an Owner.
6. Verify your connection is working by clicking Test Connection.
7. Click Connect.