Chains has three different NetSuite connectors, each working in a different way. They are not quite as straightforward or flexible as other platforms, so it is very important to know the differences in order to make the right decision for your business and solution.
Prerequisites & Requirements
Before configuring any NetSuite integration, ensure you have the following components ready. Missing these is the most common cause of connection failures.
- SuiteAnalytics Connect: If using the JDBC or Analytics connectors, this feature must be enabled in your NetSuite account. Note that this is often a paid add-on module; check your NetSuite contract.
- SuiteTalk REST Web Services: Required for the modern NetSuite Analytics connector and SuiteQL operations.
- Dedicated Integration User: Workiva strongly recommends creating a specific "Integration Role" and "Integration User" in NetSuite rather than using a personal login. This helps prevent the chain from breaking if an employee's access changes.
NetSuite® Analytics (Recommended)
This recommended approach uses SuiteAnalytics (specifically the `NetSuite2.com` data source) and SuiteQL. This is the modern method and allows for a more sustainable and performant solution. You will need to arrange your data for use in SuiteAnalytics, which can be worth the investment to avoid the performance issues seen with the legacy connectors.
Typical Export Usage
Use the Execute SuiteQL Query command to execute your SuiteQL Query and retrieve records from NetSuite.
Other Usage
You can also list and execute datasets using this connector.
NetSuite® Token Authentication (Legacy)
The token authentication connector currently uses the latest version of NetSuite's SOAP Web Services. While this ensures current stability, SOAP is being phased out by NetSuite in favour of newer protocols.
Roadmap Update: Workiva is planning to migrate this connector to use the REST API version in 2026 to align with NetSuite's deprecation schedule. Until then, the connector remains fully supported on the latest SOAP version, though it's generally recommend using the NetSuite Analytics connector for new projects where possible.
Typical Export Usage
- File Cabinet Method: Within NetSuite, automate the transfer of your files to the file cabinet and then in Chains use the Get file command to retrieve them.
- Saved Search Method: Create any required saved searches in NetSuite and then in Chains use the List saved searches command to get a list of all available searches, followed by the Get saved search data command to extract the data.
Note: The NetSuite API does not support getting data from a saved search that contains summary results (grouping).
Other Usage
You can also search records by type or ID, and retrieve JSON data for a standard record.
NetSuite® JDBC
This connector requires SuiteAnalytics Connect in NetSuite and supports JDBC connectivity, enabling you to query the database using standard SQL. The newer NetSuite Analytics connector (which uses SuiteQL) is generally recommended, as managing JDBC drivers and connection strings can be more complex.
Connector Comparison
| Connector | Underlying Tech | Best Use Case |
|---|---|---|
| NetSuite Analytics | SuiteQL / REST | Most scenarios. The modern standard for querying large datasets cleanly. |
| Token Authentication | SOAP (Legacy) | Legacy support only. Use if you have existing Saved Searches that cannot yet be migrated to SuiteQL. |
| NetSuite JDBC | Java Database Connectivity | If your team prefers writing raw SQL queries over standard API interactions. Requires "Connect" module. |