How does NetSuite data reach a dashboard?
A scenario reads the records on a schedule or when something changes, shapes them, and writes them to the tool your reports are built on. NetSuite stays the source of truth; the destination is a copy that is checked against it.
- Choose the questions the dashboard answers, and name the person who owns each number's definition.
- Read the data with the module that fits: Run a SuiteQL Query for a joined question, Search Records (Saved Search) to reuse a search your team already trusts, or Watch Records to update when a record changes.
- Load it into the destination: a Google Sheet, an Airtable base, or a database such as Snowflake that a BI tool like Tableau or Power BI reads. Make lists Google Sheets, Airtable, Snowflake and Tableau as apps; a BI tool can read from any database we load.
- Check the load: compare row counts and a control total with NetSuite, and alert when they differ.
- Stamp the dashboard with the last successful refresh so a stale number looks stale.
Which module reads which data?
Make lists ten ways to read NetSuite: two triggers, five searches and three Get or Download actions. Choose by the shape of the question.
| Make module | Type | Good for |
|---|---|---|
| Watch Records | Trigger | Reacting when a record is created or updated. |
| Watch Records (Saved Search) | Trigger | Reacting when a record enters a saved search you already maintain. |
| Search Records | Search | Lists of records by type and filter. |
| Search Records (Saved Search) | Search | Reusing a saved search so the dashboard matches the one finance already trusts. |
| Run a SuiteQL Query | Search | One question that spans several record types. |
| Search Custom Records, Bulk Get Custom Records (Advanced) | Search | Custom record types, including larger pulls. |
| Get a Record, Get a Custom Record | Action | Reading one record in full. |
| Download a File | Action | Pulling a document, such as an invoice PDF, with its record. |
Module names are Make's. The Good for column is our guidance, not a statement from Make or NetSuite.
What makes a reporting feed trustworthy?
Five habits, built into every feed so a wrong number is caught by the feed, not by the board.
- One written definition per metric, with an owner.
- A row count and a control total checked against NetSuite on every load.
- A visible last-refreshed time on the dashboard.
- An error alert to a named person when a load fails or a check differs.
- History kept, so last quarter's number does not change when a record is edited.
What do you not do?
We do not replace NetSuite's own reports, saved searches or dashboards. If NetSuite can already produce the report your team needs, use it.
We add a feed only when the answer has to live somewhere else: combined with CRM or ecommerce data, shared with people who do not use NetSuite, or kept as history.
Frequently asked questions
Does the feed change anything in NetSuite?
No. Reporting feeds read only. We use a role that can read what the report needs and nothing else.
How fresh will the numbers be?
As fresh as the schedule you choose, and the dashboard shows when the last load succeeded. We agree the schedule after we see how much data each load moves.
Do you build the dashboards too?
We build the feed and the checks, and we can set up the dashboard in the tool you already use. We start from the questions your team asks.
Want us to look at your NetSuite processes?
We build and run automations and integrations around your existing NetSuite account; we do not replace it. See our NetSuite guides and services, and the Make Enterprise NetSuite page, and the workflow automation page.





