Connect NetSuite to ECA
Give ECA governed access to NetSuite’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add NetSuite to ECA in four steps
Admins approve the server once. Everyone in ECA then gets it through the same governed connection.
- 1
Approve NetSuite in Runlayer
Add NetSuite from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect ECA to Runlayer
Users add the Runlayer Plugin to ECA by following Runlayer’s setup guide. ECA reaches NetSuite’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
ECA setup guide - 3
Sign in to NetSuite
Each user signs in to NetSuite with OAuth. Runlayer keeps the tokens out of the client’s configuration.
- 4
Use NetSuite from ECA
NetSuite’s approved tools appear in ECA. Every call is checked against policy and recorded.
Tools
17 NetSuite tools in ECA
Runlayer policy decides which of these ECA users can call.
Ns create record
Create a new record in NetSuite.
Ns get accounting books
Returns all accounting books available to the user for report execution.
Ns get accounting contexts
Returns all accounting contexts available to the user for report execution.
Ns get nexus IDS
Returns all nexus IDs available to the user for report execution.
Ns get record
Retrieve a record from NetSuite.
Ns get record type metadata
Get metadata information about all record types or from a specific record type including available fields and their types
Ns get subsidiaries
Returns all the subsidiaries available to the user for the report tool.
Ns get suite ql metadata
Retrieves SuiteQL metadata for either all record types list or a specific record type and should be called before runCustomSuiteQL to discover which fields you can safely select, filter, and sort on.
Control
What Runlayer can see and stop in ECA
Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.
Gateway policy (available)
Every NetSuite call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.
Frequently asked questions
Connect more