NetSuite Configuration
The superglue agent can create NetSuite customizations for you, such as custom fields, record types, forms, workflows, saved searches, and scripts. It uses the same NetSuite sign-in as the rest of your connection.
This guide walks you through the one-time setup, which takes about five minutes.
What to expect
Section titled “What to expect”- Preview first. The agent shows you each change before it deploys, and in ask mode it waits for your approval.
- Runs as you. Changes run as the NetSuite user and role you pick when you sign in. The agent can only change what that role allows.
Let the agent set it up
Section titled “Let the agent set it up”This is the recommended way. The agent does the setup in its own browser, which you watch in the side panel.
- Tell the agent: “Connect our NetSuite sandbox and set it up for SuiteCloud deploys.”
- Select Do it in the browser when the agent offers it, and approve the browser permission if the agent asks for it.
- Sign in to NetSuite in the browser yourself, as an administrator. Open the browser full screen to complete single sign-on or multi-factor prompts.
- The agent turns on the features and creates the integration record. NetSuite shows the client ID and the client secret only once, so the agent saves them to the connection right away. You do not copy any values.
- Sign in once more when the connect card asks, choose a role that can change account structure, such as Developer, and approve superglue’s access.
Use the steps below when the client does not allow this, or to check what the agent changed.
Set up NetSuite
Section titled “Set up NetSuite”To set it up by hand, follow these steps.
-
Turn on the features in NetSuite
- Go to Setup > Company > Enable Features > SuiteCloud.
- Check SuiteCloud Development Framework, Custom Records, OAuth 2.0, and REST Web Services.
- For scripts, also check Client SuiteScript and Server SuiteScript.
- For workflows, also check SuiteFlow.
- Click Save.
-
Create the integration record in NetSuite
- Go to Setup > Integration > Manage Integrations and create a new integration record, for example “superglue”.
- Under OAuth 2.0, keep Authorization Code Grant checked.
- Check REST Web Services and RESTlets.
- Enter
https://app.superglue.cloud/api/auth/callbackas the Redirect URI. - Click Save.
- Copy the Client ID and the Client Secret. NetSuite shows them only once.
If you already connected NetSuite in superglue, open that integration record instead and make sure RESTlets is checked.
-
Connect NetSuite in superglue
- On the Connections page, add a NetSuite connection, or open the one you have. Enter the client ID and the client secret, and start the OAuth sign-in.
- In the NetSuite sign-in window, choose a role that can change account structure. The standard Developer role works. A custom role needs the permissions Log in using OAuth 2.0 Access Tokens, REST Web Services, and SuiteCloud Development Framework.
If NetSuite was already connected, reconnect it once so the sign-in includes the RESTlets scope.
-
Test the setup in superglue
- Tell the agent: “List the custom objects in my NetSuite account.” If you get a list back, everything works.
- Try a small change in a sandbox account, for example: “Add a date field ‘Contract end date’ to customers.”
Renew or remove access
Section titled “Renew or remove access”Renew the sign-in
Section titled “Renew the sign-in”How long a NetSuite sign-in lasts depends on the integration record. We have seen seven and thirty days.
Reconnect NetSuite in superglue when the agent reports an expired sign-in. A sandbox refresh also removes the sign-in, so reconnect after each refresh.
Remove access
Section titled “Remove access”To remove access right away:
- Go to Setup > Integration > Manage Authentication > OAuth 2.0 Authorized Applications Management.
- Revoke the superglue entry.
Clean up temporary scripts
Section titled “Clean up temporary scripts”When the agent needs a script only for one job, such as reading a preference or creating a saved search, it removes the script when the job is done. It deletes every deployment and inactivates the script, so the script can no longer run.
NetSuite does not let any API delete a script record or its file. The agent lists the inactive scripts and files it leaves. You delete them under Customization > Scripting > Scripts and in the File Cabinet.
The agent only cleans up scripts owned by the connected user.
Can the agent set preferences?
Section titled “Can the agent set preferences?”Yes. A deploy cannot set preferences, for example accounting preferences. For these, the agent deploys a small script and runs it. This works with the same setup.
Can the agent read existing scripts?
Section titled “Can the agent read existing scripts?”Yes. The agent can list and read existing SuiteScript source with the same sign-in. Reading source does not deploy or run a script.
Importing a script object also retrieves its referenced source file. Files protected by an installed SuiteApp remain unavailable.