Export NetSuite reports and saved searches to Google Sheets from the browser, with no Token-Based Authentication, no integration record and no admin approval.
Most guides to getting NetSuite data into Google Sheets open with Token-Based Authentication: create an integration record, generate a Consumer Key and Secret, issue an access token, add Web Services permission to a role. All of it requires an administrator, and that is where the project usually stops. This page covers the route that skips all of it, what it genuinely does, and the two things it cannot do.
Why it needs no credentials
An API integration has to prove who it is, because it connects to NetSuite from somewhere else entirely. That proof is what TBA constructs, and building it is an administrative task by design.
A browser extension is in a different position. It runs inside the NetSuite tab you already have open, after you have already signed in. The session is established, the role is resolved, the report is on screen. There is nothing left to authenticate, which is why the setup step other methods spend hours on simply does not exist here.
The practical consequence: if you can open the report in NetSuite, you can export it. No ticket, no waiting.
Installing it
- 1Install the NetSuite Reports & Saved Searches extension from the Chrome Web Store.
- 2Pin it, so the icon stays visible while you work in NetSuite. Chrome hides unpinned extensions behind the puzzle-piece menu, which is the most common reason people think it did not install.
- 3Open NetSuite and sign in as normal. You will not be asked for NetSuite credentials anywhere in the extension.
NetSuite Reports & Saved Searches
Free, about a minute to install, and works with the NetSuite role you already have.
Add to Chrome, free →Your first export
Run the report, saved search or dataset you want, and apply whatever filters you need. Wait for results to finish rendering: the extension reads what is on the page, so a still-loading results grid gives it nothing to work with.
Then click the extension icon and choose to export to Google Sheets. The data arrives as a sheet directly. There is no CSV in between, which removes the step where a downloaded file lands in Downloads, gets imported with the wrong delimiter, and turns transaction IDs into scientific notation.
Because it reads the current view, the export reflects the filters you applied on screen rather than the saved search's stored defaults. That distinction matters more than it sounds: a saved search opened with "use available filters" behaves differently through the API than it does in front of you, which is a recurring source of "the numbers do not match" confusion.
What it can export
- Standard NetSuite reports, including financial statements and the report views finance teams live in
- Saved searches, with the filters currently applied rather than their saved defaults
- SuiteAnalytics datasets and workbook results
Permissions and what it can see
It operates as you. Every restriction on your role, subsidiary, department, class, record-level permissions, applies to the export exactly as it applies on screen. It cannot reach data you could not already open, which is worth stating plainly if someone in finance or IT asks what a browser extension is doing near the general ledger.
It also stores no credentials, because there are none to store. It never sees a password and never creates a token. Access lasts exactly as long as your NetSuite session; sign out, or uninstall, and it ends.
What it cannot do
The same design that removes the setup also sets the ceiling, and it is better to know this now than after building a process on it.
- It cannot run on a schedule. It exports when you click it, in a browser you are signed in to. Nothing refreshes overnight.
- It cannot write back to NetSuite. It is a read-and-export tool, not a sync.
- It is Chrome-only, and installed per user. Ten people who need it means ten installs.
- It stops when your session does. A NetSuite timeout interrupts it exactly as it interrupts you.
When to use the add-on instead
If a report has to rebuild itself with nobody present, the extension is the wrong tool and no amount of configuration will change that. The Google Sheets add-on authenticates to NetSuite server-side, so it refreshes on a schedule, supports write-back for objects such as journal entries and customers, and handles multi-entity consolidation. It does require the TBA setup this page exists to avoid, so it is a genuine trade: administrative effort once, in exchange for a report that maintains itself.
Plenty of teams run both, and that is a reasonable end state rather than a compromise: the extension for the ad-hoc pull someone needs before a meeting, the add-on for the month-end pack that must be ready whether anyone remembers it or not.
How the routes compare
| Route | Setup | Admin needed | Effort per export | Scheduled |
|---|---|---|---|---|
| Manual CSV export | None | Not needed | Export, download, open, import, reformat | No |
| Chrome extension | ~1 minute | Not needed | One click | No |
| Apps Script + REST API | 4 to 6 hours | Required (TBA + role) | One click after build | Yes |
| Sheets add-on | Under 15 minutes | Required (TBA) | None after setup | Yes |
For the full walkthrough of the credentialed routes, including the TBA setup itself, SuiteQL and SuiteAnalytics Connect, see How to Connect NetSuite to Google Sheets.
Troubleshooting
Related Articles
- How to Connect Stripe to Google Sheets
- How to Connect Sage Intacct to Google Sheets
- How to Consolidate Multiple QuickBooks Companies in One Google Sheet
Frequently asked questions
Do I need Token-Based Authentication to use the extension?
No, and that is the point of it. Every API route into NetSuite needs TBA: an integration record, a Consumer Key and Secret, an access token, and a role carrying Web Services permission. The extension needs none of that because it works inside the NetSuite tab you are already signed in to, reusing the session your browser already holds.
Does it need an administrator to approve anything?
No. Installing a Chrome extension is a decision for you and, in a managed environment, your IT policy. Nothing is created inside NetSuite, so there is no integration record for an administrator to set up and no role to modify. This is usually the difference between reporting this week and reporting next quarter.
Can it see data my NetSuite role cannot?
No. It operates as you, through your own session, so every subsidiary, department, class and record-level restriction on your role applies exactly as it does on screen. If a saved search shows you 400 of 3,000 rows in the NetSuite UI, the export contains those same 400 rows.
What can it export?
Standard NetSuite reports, saved searches, and SuiteAnalytics datasets. It respects the filters active on screen rather than the object's saved defaults, so an export matches the view you were actually looking at.
Can it refresh a sheet on a schedule?
No, and it is worth being clear about that. It runs when you click it, in a browser you are signed in to. It cannot rebuild a dashboard at 6am while you are asleep. For unattended refresh you want the Google Sheets add-on, which authenticates to NetSuite server-side and runs on a schedule.
Does it store my NetSuite credentials?
No. There is nothing to store: it never sees a password and never creates a token. It reads the report your browser is already displaying, within the session you established by logging in normally. Ending that session, or uninstalling the extension, ends its access.
Is it free?
Yes. The extension is free from the Chrome Web Store. The Google Sheets add-on has a free tier of 100 imports a month, with Pro at $29 per user per month for scheduled refresh, write-back and the AI analyst.
Export NetSuite reports without touching TBA.
Free from the Chrome Web Store. Or see the full NetSuite integration for scheduled refresh and write-back.
Add to Chrome, free →
