Connecting NetSuite

Connect a CRM · Last updated 2026-07-29

NetSuite requires per-customer credentials. Your admin creates an Integration Record; you paste three values into our setup form; then Connect.

Why NetSuite is different

Unlike HubSpot and Salesforce, NetSuite does not offer a shared developer app that every customer can authorize into their account. Every NetSuite customer creates their own Integration Record inside their NetSuite instance and hands us three values from it. Those values live server-side only — no client ever sees the Consumer Secret after you enter it.

Note

Corporate plan only. Your organization owner is the one who sees the setup form and can save credentials — teammates cannot.

Step 1: Create the Integration Record in NetSuite

Your NetSuite administrator does this once. They'll need the standard Setup → Integration → Manage Integrations → New permissions.

In NetSuite: Setup → Integration → Manage Integrations → New.
Name: something identifying like Networking Executives — Event Sync.
State: Enabled.
Under Authentication, check OAuth 2.0 and check Authorization Code Grant.
Redirect URI: https://us-central1-network-executive.cloudfunctions.net/netsuiteOAuthCallback
Scope: REST Web Services at minimum. That's what our sync uses.
Save. NetSuite will display the Consumer Key and Consumer Secret once. Copy both.

Watch out

The Consumer Secret is only shown once. If your admin closes the page without copying it, they'll need to reset it from the Integration Record — NetSuite cannot show it again.

Step 2: Find your Account ID

Your NetSuite Account ID is the subdomain your NetSuite lives at — e.g. 123456 for a US account or 123456_SB1 for a sandbox. Your admin can find it in Setup → Company → Company Information, listed as Account ID.

Step 3: Save the three values in Networking Executives

Sign in as the organization owner and go to Organizer dashboard → Integrations.
Find the NetSuite card. On first setup, the card renders a setup form with three inputs instead of the Connect button.
Paste the Consumer Key, Consumer Secret, and Account ID.
Click Save credentials. The form disappears and the Connect button appears.

Step 4: Connect

Click Connect NetSuite.
A NetSuite sign-in window opens at {accountId}.app.netsuite.com. Sign in with a user that has the roles needed to use the REST Web Services integration.
Approve the OAuth request. NetSuite redirects you back to your dashboard.
The card now shows the connected Account ID as the identifier.

Troubleshooting

"OAuth 2.0 must be enabled" on the Integration Record. Your admin needs to check the OAuth 2.0 box on Step 1 and re-save. TBA (Token-Based Auth) is a different mechanism and we don't use it.
"User is not permitted to perform this action." The user signing in doesn't have a role with the Log in using OAuth 2.0 Access Tokens permission and access to REST Web Services. Your admin can grant these via the role editor.
You lost the Consumer Secret. Have your admin reset it from the Integration Record (there's a button on the page), copy the new one, and re-save through our form.