NetSuite setup: pick what you need

You do not have to set up everything. Open Integrations > NetSuite and choose only what you want. Each item is its own short setup, you can do them in any order, and you can leave and come back. Nothing is changed until you confirm.

Which credential is used

The page shows "Using: ..." for the credential in use. If machine-to-machine is set up it takes priority; old consumer key and token stay stored but unused (shown only as "set", never the value) until you remove them. If the connection still uses the old credentials you can switch to machine-to-machine and switch back, because nothing is deleted when you switch.

Who is connected

The connection belongs to your Velaro site, not to individual agents. The screen pop finds the agent by matching their NetSuite user email to their Velaro agent email (not case sensitive). If they differ, that agent sees no calls and cannot save notes; fix it by making the emails match.

The API secret (screen pop and Velaro inside NetSuite)

1. NetSuite: Setup > Company > Preferences > API Secrets > Create New.

2. ID velaro_api_key (becomes custsecret_velaro_api_key). Paste your Velaro key into Password.

3. Restrictions tab: leave Available to SuiteApp unchecked.

4. Allow For All Scripts, or Restrict to Scripts and choose customscript_velaro_screenpop.

5. Restrict to Domains: your Velaro API host only (for customers api-messaging-us-east.velaro.com). List several hosts separated by commas only if you test more than one environment.

If the secret is missing or wrong, the Velaro Screen Pop page in NetSuite shows these steps instead of an error.

Bot using a RESTlet

A RESTlet is optional. Standard record types work without one. For RESTlet operations, save the RESTlet URL on the connection; Velaro calls it with the same credentials as the rest of the connection.