Resources · Make integration

NetSuite Make integrationAutomate NetSuite with Make.

Can NetSuite records move on their own, without anyone retyping them? The NetSuite Make integration gives you 22 modules (2 triggers, 15 actions, 5 searches) to read, write and file ERP data. This page walks you through the connection and a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the NetSuite integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the NetSuite Make integration do for you?

The NetSuite Make integration links your NetSuite account to Make, a visual tool where you chain modules (one brick each: a trigger, an action or a search) into a scenario, the automation Make runs for you. It watches and searches records, creates or updates them, handles files and custom records, and sends raw SOAP, REST or RESTlet calls. It is reserved to the Make Enterprise plan.

Follow every change on a customer or an order. Watch Records spots each created or updated record, and Create a Custom Record writes a trace into a custom record type your admins designed, so reviewers find the history in one place.

Keep documents next to the right record. Upload a File brings a supplier PDF into NetSuite from an external URL, then Attach a File hooks it to the purchase order it belongs to.

Answer a precise question with a query. Run a SuiteQL Query or Search Records (Saved Search) pulls the rows you need and hands them to a spreadsheet or a chat tool further down the scenario.

What Make does not do here: both triggers are scheduled, there is no instant trigger, and some fields show their internal API names instead of NetSuite labels. Plan access is covered in Make pricing. Weighing tools? Read n8n vs Make. For a project built with you, see Make agency.

Connect

How do you connect NetSuite to Make?

  1. 01

    Enable token access in NetSuite

    Sign in to NetSuite with an account that has admin or system administration permissions. Enable token-based authentication, then create the Consumer Key and Consumer Secret credentials. Keep both at hand for the last step.

  2. 02

    Create and assign roles

    Still in NetSuite, create the roles the doc asks for and assign them. Think of this as the badge Make will wear inside your account: without it, the connection has nothing to stand on.

  3. 03

    Establish the connection in Make

    In a scenario, add any NetSuite module and click Create a connection. Enter what you prepared in NetSuite and save. This connection, your NetSuite account linked to Make once, is reused by every NetSuite module.

First scenario

Your first scenario: a change log for NetSuite records

GoalWhen a record is created or updated in NetSuite, Make writes a matching custom record as a change log.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. The empty canvas is where the chain takes shape.

  2. 02

    Add Watch Records

    Search for NetSuite, pick Watch Records and click Create a connection if none exists yet. Fill the fields: once connected, Make lists the objects it can read.

  3. 03

    Add Create a Custom Record

    Click the + on the right of the trigger and choose Create a Custom Record. Map data from the watched record, such as its Internal ID, into the custom record.

  4. 04

    Test with Run once

    Edit a test record in NetSuite, then click Run once. Open each module to read the bundles it received: a bundle is one item passing from a module to the next, here one record.

  5. 05

    Schedule and switch on

    Open the clock on the first module and set the schedule; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a NetSuite scenario

2 modules start a scenario when something happens in NetSuite. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by NetSuite as soon as it happens.

NetSuite1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a record is created or updated.”

Watch Records hands your scenario every NetSuite record created or updated since its previous check, one bundle per record. It is the most direct way to react to changes on customers, orders or invoices without opening NetSuite.

How it fires
scheduled. Make checks NetSuite on the scenario's schedule, every 15 minutes by default, so a change waits for the next run.
When to use it
a sales order is edited and the warehouse team should hear about it, whether the order is new or changed.
Watch out
some fields reach Make under their internal API names, not their NetSuite labels; on Account records, the Parent field shows up as Subaccount of.
NetSuite2Watch Records (Saved Search)

Watch Records (Saved Search)

Scheduled trigger

In Make“Triggers when a record in a saved search is created.”

Here the watch follows a saved search you already built in NetSuite: each newly created record that matches it arrives in Make as a bundle. Your filters stay in NetSuite, where your admins maintain them.

How it fires
scheduled. Make checks NetSuite on the scenario's schedule and picks up the new matches at each run.
When to use it
finance keeps a saved search of vendor bills waiting for approval, and each new entry should open an approval request in your chat tool.
Watch out
its description covers created records only; to catch updates to existing records, Watch Records is the better pick.
Modules

What the NetSuite modules do

NetSuite gives you 20 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Standard Record

5 modules

Some entity fields describing a record type are displayed with their internal API names instead of their NetSuite labels. For example, in Account record types where the entity field is called Parent, the internal ID label refers to Subaccount of. For more information, refer to NetSuite SOAP API documentation.

NetSuite1

Search Records

Search

In Make“Retrieves a list of records filtered by a query.”

Need every customer from one region, or all orders on hold? Search Records returns the standard records matching a query you set, each one as its own bundle for the next module.

When to use it
before a mailing, pull the contacts with a given status and pass them to your email tool.
Watch out
a search can return zero, one or many bundles, and the modules after it run once per result, consuming operations each time.
NetSuite2

Search Records (Saved Search)

Search

In Make“Retrieves a list of records filtered by a saved search.”

Your saved searches become reusable inputs: this module runs one of them and returns its results as bundles. Complex criteria stay where your admins already keep them.

When to use it
a search already feeds a NetSuite dashboard and you want the same list in a spreadsheet, without rebuilding the criteria in Make.
Watch out
editing the saved search in NetSuite changes what the scenario receives, so tell whoever owns it.
NetSuite3

Create or Update a Record

Action

In Make“Creates or updates a record by its Internal ID or External ID.”

One module covers both cases: it adds a standard record, or updates the one matching the Internal ID or External ID you pass. No need to check first whether the record exists.

When to use it
a buyer signs up on your web shop; use the shop's customer number as External ID so a second order updates the same NetSuite customer.
Watch out
some fields carry internal API names rather than NetSuite labels, so check the mapping with Run once.
NetSuite4

Get a Record

Action

In Make“Retrieves the details of a record by its Internal ID or External ID.”

With an ID in hand, Get a Record fetches the full details of one standard record, by Internal ID or External ID. It fills the gap when a previous module only gave you a reference.

When to use it
a form in another app carries an order number stored as External ID, and the next step needs the order details from NetSuite.
Watch out
it expects one precise ID; if all you have is a name, start with Search Records.
NetSuite5

Delete a Record

Action

In Make“Deletes a record by its Internal ID or External ID.”

Removing one standard record, found by Internal ID or External ID, takes this single module. It keeps NetSuite tidy when a record created by a scenario turns out to be a mistake.

When to use it
a test customer created while you built the scenario has to go.
Watch out
treat every delete as final and try it on a throwaway record with Run once before the scenario runs unattended.

Custom Record

6 modules
NetSuite6

Search Custom Records

Search

In Make“Retrieves a list of custom records filtered by a query.”

Custom record types your admins built are searchable too. Search Custom Records filters them with a query and returns each match as a bundle, ready for the next module.

When to use it
a custom record tracks equipment loans, and the loans still open should feed a reminder email.
Watch out
results can be zero, one or many; read the bundle count in Run once before mapping anything after it.
NetSuite7

Bulk Get Custom Records (Advanced)

Search

In Make“Retrieves multiple custom records by their IDs.”

Already holding a list of IDs? Bulk Get Custom Records (Advanced) retrieves all those custom records from one module, instead of chaining a lookup per ID.

When to use it
a spreadsheet lists the IDs of project records to review, and the next module needs their current values.
Watch out
it only works from IDs; to find custom records by criteria, Search Custom Records is the right tool.
NetSuite8

Create a Custom Record

Action

In Make“Creates a new custom record.”

Data that NetSuite has no standard record for still gets a home: Create a Custom Record adds a new entry to one of your custom record types.

When to use it
each approval request coming from an online form becomes a custom record your controllers review.
Watch out
unlike Create or Update a Record, it only creates; to change an existing entry, use Update a Custom Record.
NetSuite9

Get a Custom Record

Action

In Make“Retrieves the details of a custom record by its Internal ID or External ID.”

Reading one custom record in full is the job of Get a Custom Record: give it the Internal ID or External ID and it returns the details to the rest of the scenario.

When to use it
a support ticket carries the External ID of a custom record, and the next module needs its current values before replying.
Watch out
for several IDs at once, Bulk Get Custom Records (Advanced) saves you a chain of single lookups.
NetSuite10

Update a Custom Record

Action

In Make“Updates a custom record by its Internal ID or External ID.”

Changes land on an existing custom record, identified by Internal ID or External ID, through Update a Custom Record. Your custom data stays current without manual edits.

When to use it
a contract gets signed in your e-signature tool and the matching custom record should switch to signed.
Watch out
it creates nothing; if the entry may not exist yet, look for it first with Search Custom Records.
NetSuite11

Delete a Custom Record

Action

In Make“Deletes a custom record by its Internal ID or External ID.”

Delete a Custom Record erases one custom record, picked by Internal ID or External ID. It cleans up entries that no longer reflect anything real.

When to use it
a booking is cancelled in your scheduling tool and its custom record should disappear with it.
Watch out
treat the delete as final: a Get a Custom Record on the same ID just before confirms you target the right one.

Files and Folders

5 modules
NetSuite12

Upload a File

Action

In Make“Uploads a file by an external URL or binary data.”

Files from outside reach NetSuite through Upload a File, either from an external URL or from binary data produced by a previous module.

When to use it
a supplier emails a PDF invoice, and the attachment picked up by your mail module should land in NetSuite without a manual download.
Watch out
an uploaded file is not tied to any record yet; add Attach a File to link it to the vendor bill.
NetSuite13

Download a File

Action

In Make“Download an existing file by its internal ID or external ID.”

Download a File gets a file stored in NetSuite, by Internal ID or External ID, so the next module can send it, archive it or read its content.

When to use it
each purchase order PDF should go to an OCR tool that extracts the lines for your accounting team.
Watch out
the module needs the file ID, not the ID of the record the file is attached to.
NetSuite14

Attach a File

Action

In Make“Attaches a file to a record by its ID and the record ID.”

A file sitting in NetSuite becomes part of a record once Attach a File links the two, using the file ID and the record ID. People then find the document on the record itself.

When to use it
right after Upload a File, attach the supplier PDF to its purchase order.
Watch out
both IDs are required; map the file ID from the upload and the record ID from the trigger or a search.
NetSuite15

Detach a File

Action

In Make“Detaches a file from a record by its ID and the record ID.”

Detach a File is the reverse move: from the file ID and the record ID, it separates a file from the record it was attached to.

When to use it
an outdated quote sits on a customer record and the new version should replace it.
Watch out
the module only undoes the link; chain Attach a File after it when a replacement document has to take its place.
NetSuite16

Create or Update a Folder

Action

In Make“Creates or updates a folder by its Internal ID or External ID.”

Folders get the same create or update logic as records: this module makes a folder, or updates the one matching an Internal ID or External ID.

When to use it
each new customer gets a contracts folder, with the customer number as External ID so later runs reuse it.
Watch out
passing the same External ID every time is what points the module to the existing folder instead of a new one.

Other

4 modules

The opening and closing tags should contain the action name. In the example, the action is Search. The tags contain platformMsgs:search.

Before using a module, upload your script file to your File Cabinet and create a script record and a script deployment record for it in your NetSuite account. Read more here.

NetSuite17

Make a SOAP API Call

Action

In Make“Performs an arbitrary authorized SOAP API call.”

When no ready-made module covers the need, Make a SOAP API Call sends an authorized request to the NetSuite SOAP API through the connection you already set up.

When to use it
an operation the other modules do not offer, and that someone on your team knows how to write in SOAP.
Watch out
in the doc example, the opening and closing tags carry the action name, so a search sits between platformMsgs:search tags.
NetSuite18

Make a REST API Call

Action

In Make“Performs an arbitrary authorized REST API call.”

Same escape hatch, other API: Make a REST API Call sends an authorized request to the NetSuite REST API, and you write the request yourself.

When to use it
your developers already rely on a NetSuite REST endpoint and want its answer inside a scenario.
Watch out
the request is yours to build, so for everyday record work the ready-made modules above stay easier to maintain.
NetSuite19

Make a RESTlet API Call

Action

In Make“Performs an arbitrary authorized RESTlet API call.”

Scripts deployed in your NetSuite account become reachable from Make: Make a RESTlet API Call sends an authorized call to a RESTlet.

When to use it
a RESTlet already holds business logic, such as a pricing rule, and a scenario should reuse it rather than rebuild it.
Watch out
the doc for this group asks you to upload the script file to the File Cabinet, then create a script record and a script deployment record, before using a module.
NetSuite20

Run a SuiteQL Query

Search

In Make“Executes a SuiteQL query.”

Run a SuiteQL Query executes a query you write in SuiteQL and returns the results as bundles. It suits questions that a plain search expresses badly.

When to use it
a finance lead wants overdue invoices listed together with customer details in a sheet.
Watch out
each returned row becomes a bundle, and every module after it runs once per row, so narrow the query before switching the scenario on.
Need help

Need help automating NetSuite with Make?

A person reads every message.

FAQ

Questions about the NetSuite Make integration

01Is the NetSuite Make integration free?
No. NetSuite is an enterprise app in Make, available on the Make Enterprise plan only. The Free plan opens 3,000+ standard apps with 2 active scenarios, a 15-minute minimum between scheduled runs and 5 minutes of execution per run, but enterprise apps stay outside it. Paid plans (Core, Pro, Teams and Enterprise) count usage in credits, meaning operations per month. This page says nothing about your NetSuite license itself; check that with whoever manages your NetSuite contract.
02What do you need to connect NetSuite to Make?
A NetSuite account with admin or system administration permissions, and a Make organization on the Enterprise plan. In NetSuite, enable token-based authentication, create the Consumer Key and Consumer Secret credentials, then create and assign roles. Only then do you open Make, add a NetSuite module and click Create a connection. The connection is stored once and reused by every NetSuite module in your scenarios, so this setup does not repeat for each new scenario.
03Does the NetSuite Make trigger fire in real time?
No. Both NetSuite triggers, Watch Records and Watch Records (Saved Search), are scheduled: Make checks NetSuite on the scenario's schedule instead of NetSuite calling Make. A new scenario runs every 15 minutes by default, and paid plans, Enterprise included, allow an interval down to 1 minute. The app has no instant trigger. If the delay between a change and the scenario matters, shorten the schedule on the first module and keep an eye on the operations it consumes.
04What if a NetSuite module is missing in Make?
It depends on what is missing. NetSuite has no generic Make an API Call module, but it offers three direct routes: Make a SOAP API Call, Make a REST API Call and Make a RESTlet API Call, plus Run a SuiteQL Query for custom reads. RESTlets need a script file uploaded to the File Cabinet, with a script record and a script deployment record. If none of that fits your team, the agency can study the case with you.
05Should you use Make or n8n for NetSuite?
It depends on your criteria rather than on a winner. On Make, NetSuite comes with 22 ready-made modules, a visual editor where every change can be tested with Run once, and access tied to the Enterprise plan. n8n is another automation tool, and many apps exist on both; check whether it covers the NetSuite operations you need before choosing. Then compare the plan your company already pays for, who will maintain the scenarios and which modules your case really requires.
Same platform

Other docs you might need on this stack.

Browse all integrations