Skip to content

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.

  • 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.
  1. Turn on the features in NetSuite

    1. Go to Setup > Company > Enable Features > SuiteCloud.
    2. Check SuiteCloud Development Framework, Custom Records, OAuth 2.0, and REST Web Services, then click Save. For scripts, also check Client SuiteScript and Server SuiteScript. For workflows, also check SuiteFlow.
  2. Create the integration record in NetSuite

    1. Go to Setup > Integration > Manage Integrations and create a new integration record, for example “superglue”.
    2. Under OAuth 2.0, keep Authorization Code Grant checked and check REST Web Services and RESTlets.
    3. Enter https://app.superglue.cloud/api/auth/callback as the Redirect URI.
    4. Click Save. NetSuite shows a Client ID and a Client Secret once. Copy both.

    If you already connected NetSuite in superglue, open that integration record instead and make sure RESTlets is checked.

  3. Connect NetSuite in superglue

    1. Open your NetSuite system in superglue and start the OAuth sign-in with the client ID and client secret.
    2. 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.

  4. Test the setup in superglue

    1. Tell the agent: “List the custom objects in my NetSuite account.” If you get a list back, everything works.
    2. Try a small change in a sandbox account, for example: “Add a date field ‘Contract end date’ to customers.”

A NetSuite sign-in lasts seven days. Reconnect NetSuite in superglue when the agent reports an expired sign-in. The Refresh Token Validity field on the integration record does not change this; it only applies to public clients. A sandbox refresh also removes the sign-in, so reconnect after each refresh. To remove access right away, go to Setup > Integration > Manage Authentication > OAuth 2.0 Authorized Applications Management and revoke the superglue entry.

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.