What does Make list for NetSuite?
Make lists 22 NetSuite modules and labels the app Enterprise, supported and maintained by Make. Module names and counts are copied from Make's NetSuite page as read on November 17, 2026. Make updates its apps, so treat this as a snapshot and check the page before you scope work.
- Triggers (2): Watch Records, Watch Records (Saved Search).
- Searches (5): Bulk Get Custom Records (Advanced), Run a SuiteQL Query, Search Custom Records, Search Records, Search Records (Saved Search).
- Actions (15): Attach a File, Create a Custom Record, Create or Update a Folder, Create or Update a Record, Delete a Custom Record, Delete a Record, Detach a File, Download a File, Get a Custom Record, Get a Record, Make a REST API Call, Make a RESTlet API Call, Make a SOAP API Call, Update a Custom Record, Upload a File.
Make's Enterprise label matters for scoping: check which Make plan includes the app before you commit. Our Make Enterprise page explains how we scope against it.
Which systems connect to NetSuite?
Any app in Make's app list can sit on the other side of a NetSuite scenario. Make's own page says you can integrate over 3,500 apps. The table is a sample of the kinds of system finance and IT teams ask us to connect, with the hand-off we usually build.
| App in Make | Kind of system | Typical hand-off with NetSuite |
|---|---|---|
| CRM | A won deal creates the customer and sales order in NetSuite; the order number and status go back to the CRM. | |
| CRM | A won deal creates the customer and sales order in NetSuite; the order number and status go back to the CRM. | |
| Ecommerce | Web orders become NetSuite sales orders; fulfilment and tracking updates go back to the store. | |
| Ecommerce | Web orders become NetSuite sales orders; fulfilment and tracking updates go back to the store. | |
| Payments | Payment and payout records are matched to open invoices; anything that does not match goes to a person. | |
| Payments | Payment and payout records are matched to open invoices; anything that does not match goes to a person. | |
| Payroll and HR | Payroll or HR results are checked, then posted to NetSuite after a named person approves them. | |
| Payroll and HR | Payroll or HR results are checked, then posted to NetSuite after a named person approves them. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in NetSuite; exceptions wait in a queue with an owner. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in NetSuite; exceptions wait in a queue with an owner. | |
| Expenses and procurement | Approved expenses and purchase orders are created or matched in NetSuite; exceptions wait in a queue with an owner. | |
| Tax | Tax lookups for a transaction are made and stored; a failed lookup stops the write and alerts an owner. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Support | Order and customer context shows up in the ticket; credits and refunds are raised for approval, not posted automatically. | |
| Chat, email and files | Approvals, alerts and attachments move between NetSuite and the places your team already works. | |
| Chat, email and files | Approvals, alerts and attachments move between NetSuite and the places your team already works. | |
| Chat, email and files | Approvals, alerts and attachments move between NetSuite and the places your team already works. | |
| Spreadsheets and BI | Saved-search and SuiteQL results load on a schedule, with a row-count check against NetSuite. | |
| Spreadsheets and BI | Saved-search and SuiteQL results load on a schedule, with a row-count check against NetSuite. | |
| Spreadsheets and BI | Saved-search and SuiteQL results load on a schedule, with a row-count check against NetSuite. | |
| Spreadsheets and BI | Saved-search and SuiteQL results load on a schedule, with a row-count check against NetSuite. | |
| SFTP, FTP and HTTP | Partner and EDI files | Partner files arrive by SFTP or an API call; a scenario validates each one, creates the records, and rejects bad files with a reason. |
We build partner and EDI hand-offs around whatever your EDI provider exposes: file drops over SFTP or FTP, or API calls over HTTP. Make lists apps for all three. Being listed does not mean every module suits your job; we scope against the modules.
Which NetSuite module fits which job?
Pick the narrowest module that does the job: watch for changes, search for lists, query for joined data, and use a raw API call only when no dedicated module covers the case.
- Watch Records starts a scenario when a record is created or updated; Watch Records (Saved Search) starts one when a record in a saved search is created (Make's descriptions).
- Search Records, Search Records (Saved Search) and Search Custom Records return lists to work through. Run a SuiteQL Query returns data from one query, which suits a question that spans several record types.
- Create or Update a Record writes by Internal ID or External ID (Make's description). An External ID lets a scenario update a record it created earlier instead of creating a second one.
- Attach a File, Upload a File and Download a File move documents such as invoice PDFs.
- Make a REST API Call, Make a RESTlet API Call and Make a SOAP API Call reach NetSuite endpoints the other modules do not cover. A RESTlet is a script deployed in NetSuite, so someone has to own that script.
What do you settle before the first scenario goes live?
A short list, agreed before we build, so the first scenario is safe to turn on and someone is accountable for it.
- Pick one process, and name the person who owns it.
- Decide what the scenario may read and what it may write. We start read-only and add writes one at a time.
- Create a dedicated integration role in NetSuite with the narrowest access that works, never a person's login.
- Name who receives the error alert and who fixes the problem.
- Test against a sandbox or a copy of your data first, if you have one.
- Decide how long run history must be kept for audit.
Frequently asked questions
Does connecting NetSuite through Make replace or change our NetSuite setup?
No. Scenarios read and write NetSuite records through Make's modules. Your configuration, customizations and users stay yours, and we ask for a dedicated integration role with the narrowest access that works.
Can we connect a system that has no Make app?
Often, yes. Make lists an HTTP app for calling web APIs and FTP and SFTP apps for file drops. We confirm the other system's API or file options before we promise anything.
Which Make plan do we need?
Make labels the NetSuite app Enterprise on its page. Make describes its plans on its own pages and our Make Enterprise page explains how we scope against them. This page does not quote Make's prices or ours.
Where do we start?
Book a 15-minute call and bring the one NetSuite process that takes your team the most hours. We will review it with you.
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.





