With the NetSuite® Token Authentication connector, you can use commands in chain to interact with NetSuite. For example, with this connector, you can:
- Download files from NetSuite
- List saved searches in NetSuite
- Retrieve data about a standard NetSuite record or saved search
Note: To interact with a NetSuite RESTlet using OAuth 2.0 authentication, use an HTTP Request connector instead.
To enable the connection, the connector uses the NetSuite REST API. To set up the connector, you'll need:
- NetSuite, with token-based authentication (TBA) enabled
- The ID of the NetSuite account to connect to
Note: To view your account ID in NetSuite, select Setup, Integrations, Web Services Preferences. The ID also typically appears in the first string of the URL, just before
- An integration record and access token created in NetSuite for the connector
- The integration record's consumer key and secret
Note: If you don't have the consumer secret or key, edit the integration record and reset its credentials.
- The access token's ID and secret
Note: If you don't have the access token's ID or password, create a new token.
Enable the integration in NetSuite
To enable the connector to interact with NetSuite, it requires token-based authentication (TBA) and its own integration record.
Step 1. Enable token-based authentication
To enable TBA:
- Select Setup, Company, Enable Features.
- Under SuiteCloud, select Client SuiteScript and Server SuiteScript, and agree to the SuiteCloud terms of service.
- Under Manage Authentication, check Token-based authentication, and agree to the SuiteCloud terms of service.
- Click Save.
Step 2. Create an integration record
After you enable TBA, create an integration record for the connector:
- Select Setup, Integrations, Manage Integrations, and click New.
- To help identify the integration, enter a unique name and description, such as Workiva Integration.
- Under Authentication, select Token-based Authentication (TBA).
- Click Save, and record the consumer key and secret from the confirmation page.
Note: The consumer key and secret appear only on the integration record's confirmation page. Be sure to record these values for the connector's properties, and treat them like a password.
Step 3. Create the access token
After you enable TBA and create the integration record, create the access token for the connector in NetSuite, and record its ID and secret.
Set up the NetSuite Token Authentication connector
Note: To make the connector available for use in your organization's chains, an org security administrator first enables it from Configuration.
- From Chains, click Connections and Add Connection .
- Under BizApp Connection, select NetSuite Token Authentication and the default CloudRunner.
- Enter a unique name and description to help identify the connection.
- Under Properties, enter the connection's details:
Property Details Account ID Enter the ID of the NetSuite account to connect to. Consumer key Enter the consumer key for the connector's integration record. Consumer secret Enter the secret for the Consumer Key property. Token ID Enter the ID of the connector's access token. Token secret Enter the secret for the Token ID property. Sandbox To connect to a sandbox NetSuite account, check this box.
Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.
- Select the environments to use the connection, and click Save.
- To test the connection, create and run a chain with the connector's List Saved Searches command, and verify it returns a valid output.
If the connection to NetSuite fails:
- Check the account ID entered for the connector. To view the account ID in NetSuite, select Setup, Integrations, Web Services Preferences. The ID also typically appears just before
app.netsuite.comin the URL.
- Verify the consumer key and secret of the connector's integration record. If necessary, edit the integration record and reset its credentials to create a new consumer key and secret.
- Verify the ID and secret of the connector's access token. If necessary, create a new token for the connector.