Connect NetSuite to GitHub Copilot
Give GitHub Copilot governed access to NetSuite’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add NetSuite to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot 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 GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches NetSuite’s 17 tools through the plugin’s search and execute tools.
GitHub Copilot 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 GitHub Copilot
NetSuite’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
17 NetSuite tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot 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 GitHub Copilot
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.
Gateway policy (available)
Every NetSuite call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.
Frequently asked questions
Connect more