Wiresk

Wiresk

NetSuite – Connection & Settings

Estimated reading time: 9 min
wiresk NetSuite NetSuite - Connection & Settings

NetSuite is the leading integrated cloud business software suite, including business accounting, ERP, CRM and e-commerce software.

Integrating NetSuite with Wiresk empowers businesses to unlock advanced data management and automation capabilities.

Wiresk offers a comprehensive suite of actions for managing records, files, and custom queries within NetSuite. With features like retrieving saved search results, executing RESTlets, performing SuiteQL queries, and attaching or managing files and folders, users gain full control over their NetSuite environment.

Wiresk’s capabilities also include creating, updating, deleting, and upserting records, making it easier to maintain accurate and up-to-date data.

To use NetSuite in your Flows, you must have a NetSuite account. You can create an account at NetSuite.com. Your account must have admin or system administration permissions. 
For developers, you can refer to the API endpoint official documentation here. 

A connection to your NetSuite account is needed so we can sync it with our platform.

There are two ways to connect your app to Wiresk:

  • In “My apps” section, where you can manage your connections (select or create your group first to get access to this section, refer to the Group system ).
  • While building your Flow, you can easily establish a connection to your app directly within the Flow builder. This can be done during the setup of either a Trigger or a Method.

This guide explains how to set up a connection in “My apps” section, which is essentially the same process as creating one on-the-go.

Prerequisite:
 
The following steps are required before creating the connection in Wiresk:

▪️ Create a Token-Based Authentication.
▪️ Get your Consumer Key and Consumer Secret.
▪️ Create an Access Token.
▪️ Get your Token ID and Token SECRET.
▪️ Get your account ID and SuiteTalk URL.
  • Login to NetSuite with Administrator account.
  • Go to Setup -> Integration -> Manage Integrations -> New
Screenshot of NetSuite website page. Red arrows show where to click to reach the integration page. Click on setup, integration, then manage integrations and new.
  • On the integration creation page, provide a name and a description, then in the Authentication Tab, select TOKEN-BASE AUTHENTICATION.
  • Save your Integration.
Screenshot of NetSuite new integration page. Red arrows show the field name, also pointing to field token-based authentication to be check. Another arrow point to the button Save.
After saving your new integration, find your Consumer Key and Consumer Secret at the bottom of the page. This information is shown only once, so make sure to save it somewhere safe for your Wiresk connection.
Screenshot of NetSuite page Showing the Consumer Key and the Consumer secret.
  • Go to your NetSuite dashboard, and select “Manage Access Token”.
Screenshot of NetSuite Dashboard. Red arrows point to Manage Access Token.
  • Then click on “New My Access Token”
  • On the new page, select the integration that you have previously created in Create a Token-Based Authentication step, then click save. 
Screenshot of the Token creation page, showing the primary information of the token.
Once you save, you’ll find the Token ID and Token Secret at the bottom of the page. This information is shown only once, so make sure to save it somewhere safe for your Wiresk connection.
  • In NetSuite, go to Setup Tab -> Company -> Company Information.
  • Find Your Account ID and SuiteTalk URL as shown in the screenshot below.
Screenshot of NetSuite Company Information page. It shows important information like Account ID and SuiteTalk URL to be keep for Wiresk connection.
  • Save the information for Wiresk Connection.
  • On your Wiresk’s Dashboard, select your Group.
  • On the left panel, go to “My apps” and select Screenshot 2025 04 08 at 9.58.41 in the morning NetSuite - Connection & Settings
  • Search “NetSuite” in the search field or scroll down the list of apps and choose the NetSuite icon.
Animated image GIF, showing the step of how to create an app connection. First, select the group then select My Apps tab, and click on the "+ create" button.
Screenshot of Wiresk Add Apps screen. This Screen show the connection for NetSuite app. There is different fields to provide such as : SuiteTalk URL, Consumer Key, Consumer secret, Access token, Token secret, account ID.

Voila! Your NetSuite app connection is ready. You can now use it to build your Flows.

Now that your app is linked to Wiresk, you’re ready to start building Flows.

Simple steps to create a Flow ↓
  • Select your Group, then on the Flow management screen click on “Create Flow”.
  • On the new screen, name the new Flow.
GIF animated screen of Wiresk, showing the way to create a new Flow.

Add a Trigger that will start your Flow

Flows can be executed by multiple Triggers, depending on the desired workflow. For example, you could use scheduled Triggers with different recurrence rules alongside a Webhook Trigger for immediate, event-driven runs of the Flow. If you choose to “Run Once“, the Flow will execute using only one Trigger and its sample data.
  • Click on the (+) button to open the Trigger settings side panel.
  • On the settings side panel, click on the “+ Add” button.
Screenshot of the Wiresk side panel titled “Trigger.” The panel shows a section labeled “All Triggers” with a blue “+ Add” button for inserting a new Trigger.
  • On the Trigger selection screen, search your app or select it from the list below the screen.
Screenshot of Wiresk Trigger setting screen. Red arrows shows that you can wether search your app in the search or or select it in the list below.
  • Select your preferred Trigger on the next screen and customize its settings.
As mentioned in “How to connect your app to Wiresk” above, during your Trigger settings, you can create a new connection to your apps at this stage.

Add a Method that will execute a task

The Method will perform a specific task on a particular app or service you’ve connected to Wiresk like get info or send emails.

You can add at least 1 or multiple Methods for complex Flows (a maximum of 255 Methods).
  • On the Flow builder, select the (+) plus button next the Trigger button.
  • Search or scroll down to select the app that will perform a task.
  • Configure the Methods settings, refer to it documentation in our Help Center.
Screenshot of Wiresk Flow Builder with a Flow named “Flow Example.” The canvas shows a Gmail Trigger on the left connected to an empty step placeholder marked with a plus icon in the center. On the right, the panel lists available apps and tools. A search bar is displayed at the top of the panel for filtering apps. Red arrows highlight the empty step placeholder, the search bar, and items in the app list.

Add Wiresk Tools to your Flow

If you want to build a complex Flow, Wiresk offers a selection of tools at your disposal. Refer to Wiresk’s Tools

To add Tools in your Flow, Follow the same step as adding the Methods.

  • On the Flow builder screen, click on the plus button (+) then just click on the “Tool” tab and select the Tool that you want to add.
Screenshot of Wiresk Flow Builder showing a Gmail Trigger connected to an empty Method placeholder. A red arrow points to the empty step circle with a plus sign where the next action will be added. On the right side, the “Tool” tab is selected in the panel. Another red arrow highlights the “Tool” tab label at the top. A search bar is shown above a list of available tools.
You can refer to “How to Create a Flow” tutorial for more detailed instructions, including step-by-step guidance on mapping and configuration.

What will start your automation…

Run Once Tab: This tab allows you to schedule a Flow to execute a single time at a specific date and time. This is ideal for one-time operations such as data syncs, cleanups, or initial configuration steps. After execution, the schedule will be automatically cleared unless rescheduled manually.

Run Tab: This tab is used to set up repeating schedules:

  • Repeat feature: This dropdown determines how long the automation will continue repeating based on the selected frequency (Minutely or Hourly). You can choose from:
    • Repeat Forever
      • The automation will continue to run indefinitely at the defined interval (e.g. every 15 minutes).
      • No end condition is specified.
    • Repeat for (x) Times
      • You set a specific number of repetitions.
      • Requires the field Number (x) of Repeat Times to be filled (e.g. 10 times).
    • Repeat Between Start & End Dates
      • The automation will run only within a defined date range.
      • Additional fields will appear to select start and end dates.
      • Useful for limited-time schedules like campaigns or batch jobs.
  • Daily at Multiple Times: Sets the Flow to run several times per day based on a minutely or hourly interval.
  • Daily: This allows a Flow to run x times per day at a specific time.
  • Weekly: This allows you to run a Flow weekly by selecting the days and time.
  • Monthly: This will monitor your Trigger every month on a defined date and hour.
  • Yearly: This will monitor your Trigger on a specific date and hour every year.
  • Specific dates: This will start your Trigger on specific dates and time.

For more details, see Wiresk Scheduler – The Fundamentals.

After configuring your Trigger, you can load sample data into the Example Input panel in Flow Builder. This gives you a preview of what the Trigger returns and prepares the data for mapping.

How to get it:

  • Enter manually: Add your own sample data in the JSON editor, plain JSON string, or form view.
  • Use predefined Trigger samples: Triggers provide ready-made sample data that can be pulled directly into the Example Input panel.
  • Capture Example Input: Enable this option to record real data the next time the Flow runs. The captured sample will automatically appear in the panel.

With Sample Input in place, you can review the field structure and connect Trigger outputs to Method parameters with confidence.

For more details, refer to Example Input – How it Works.

These Triggers will start your Flow automatically at a specific time or intervals instead of being triggered real-time event (Webhooks).

NETSUITE LOGO NetSuite - Connection & Settings
Retrieve records information from your account. Narrow down the results with a search.

Configuration Table:

Name*Retrieve Record List
Connection*Select your connection or create one.
Time outYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence rule/scheduler*Set up your recurrence rule.
Parameters
Entity*Select the Entity to retrieve records from.
Search You can filter the results with a search
LimitSpecify the number of results on a single page. Default value is 10.
Preview DataIn this tab, you can preview the retrieved data.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available”, or “Cannot read properties of null ” will be displayed.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings

In NetSuite, create and save custom search queries as ‘Saved Searches.’ These searches allow you to quickly find specific data like customers, transactions, or inventory items within your NetSuite account.

This Trigger is used to retrieves data from a pre-defined Saved Search within your NetSuite account.

Configuration Table:

Name*Get Saved Search
Connection*Select your connection or create one.
Time outYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence rule/scheduler*Set up your recurrence rule.
Parameters
Saved Search Type*Select the Saved Search type in a dynamic list.
Saved Search ID*Choose the specific Saved Search you want to retrieve data from.
Number of RecordsSpecify the number of results on a single page. Default value is 100, max 1000.
Preview DataIn this tab, you can preview the retrieved data.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available”, or “Cannot read properties of null ” will be displayed.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings

A RESTlet is a custom SuiteScript that allows external applications or other NetSuite scripts to interact with NetSuite data and functionality. It executes upon request and may return data to the calling source.

This Trigger allows you to trigger the execution of a specific RESTlet by Script ID and deployment ID, within your NetSuite account directly from Wiresk.
 
How to get the Script ID and deployment ID:
Go to Customization > Scripting > Script Deployments in your NetSuite account.

Script ID:
In the Script Deployments list, locate the deployment associated with your RESTlet.
The Script ID is typically a unique identifier for the SuiteScript code itself (e.g., “customscript_myrestlet”).

Deployment ID:
This is the unique identifier for the specific deployment of the script.
If you have enabled “Show Internal IDs” in your NetSuite preferences, the Deployment ID will be visible in the list.  
If not, you can hover over the deployment name in some cases, and a tooltip might display the internal ID.
Obtaining Deployment ID (Alternative Method)
Record Browser: Navigate to Lists > Records in NetSuite.
Search for “scriptdeployment” in the record type field.
This will open the Record Browser where you can search for your script deployment using its name or other criteria.
The internal ID (Deployment ID) will be displayed for each record.

Important Notes:
Show Internal IDs: Enabling “Show Internal IDs” in your NetSuite preferences is highly recommended as it makes finding these IDs much easier. You can usually enable this under Home > Set Preferences.  

Deployment Purpose: Ensure that the deployment you select is the correct one for the specific RESTlet you want to execute. Deployments can be used to manage different versions and environments (e.g., development, test, production) of your SuiteScript code.

Configuration Table:

Name*Execute RESTlet
Connection*Select your connection or create one.
Time outYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence rule/scheduler*Set up your recurrence rule.
Parameters
Script ID*This is the unique identifier assigned to the SuiteScript code that defines your RESTlet. You’ll need to provide the correct Script ID to specify which RESTlet you want to execute.
Deployment ID*This ID links the Script ID to a specific deployment within your NetSuite account. Deployments allow you to manage different versions and configurations of your SuiteScript code.
Method*Specify the HTTP method used to invoke the RESTlet.
GET – POST – PUT – DELETE
Request BodyThis is an optional field and would be used to include any data or parameters that need to be sent to the RESTlet in the request body. This is applicable with the method “POST” or “PUT”.
Preview DataIn this tab, you can preview the retrieved data.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available”, or “Cannot read properties of null ” will be displayed.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings

SuiteQL is a powerful query language within the NetSuite platform, designed to help users extract and analyze data stored within their NetSuite accounts.

Core Concepts:

▪️SQL-based: SuiteQL is heavily influenced by SQL (Structured Query Language), a widely-used standard for querying relational databases. This familiarity makes it easier for users with SQL experience to learn and use SuiteQL.  
▪️NetSuite-specific: While similar to SQL, SuiteQL is specifically tailored to the NetSuite data model and schema. It includes features and functions that are unique to NetSuite objects and relationships.  
▪️Data Access: SuiteQL allows users to query various data sources within NetSuite, including:

  • Standard NetSuite records: Customers, sales orders, inventory items, employees, and more.
  • Transaction data: Sales orders, purchase orders, invoices, etc.  
  • Custom records: Records created by users to store specific business data.  
  • Analytics data: Aggregated data from various sources within NetSuite.
This Trigger will execute a provided SuiteQL Query. See more details about SuiteQL.

Configuration Table:

Name*Execute SuiteQL
Connection*Select your connection or create one.
Time outYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence rule/scheduler*Set up your recurrence rule.
Parameters
SuiteQL*Enter your SuiteQL query.
Preview DataIn this tab, you can preview the retrieved data.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available”, or “Cannot read properties of null ” will be displayed.

(*) required field

What your automation will do…

NETSUITE LOGO NetSuite - Connection & Settings
This Method is used to create records from a selected Entity.
 
▪️ Common Entities:
Customers: Create new customer records in NetSuite, including individual customers and companies.
Vendors: Add new vendors to your NetSuite account.
Contacts: Create new contact records associated with customers, vendors, or other entities.
Sales Orders: Generate new sales orders in NetSuite, potentially triggered by events in other systems connected through Wiresk.
Purchase Orders: Create purchase orders for procuring goods or services.
Invoices: Generate invoices for customers or receive invoices from vendors.
Inventory Items: Add new items to your inventory management system in NetSuite.
Employees: Create new employee records.
 
▪️ Other Entities:
Cases: Create support cases or tickets in NetSuite.
Opportunities: If you’re using NetSuite for CRM, you might be able to create new sales opportunities.
Journal Entries: Create journal entries for financial transactions.
Custom Records: Create records for custom record types defined in your NetSuite account.
 
⚠️ Remember that the availability of specific entities also depend on your NetSuite version, edition, and any industry-specific modules you have enabled.

Configuration Table:

Name*Create
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Map Fields [+ Add Field] you can add extra fields to populate.
Available Fields*Default displayed fields to populate depending on the selected Entity.

For example: From Entity “Account”, the default displayed fields are “Name”, “Number”, “Currency”.

(*) required field

This Method is used to delete a record from a selected Entity by providing it Record ID and ID Type.
 
⚠️ Make sure that in your NetSuite account -> home -> Set Preferences -> you have have checked “SHOW INTERNAL IDS.

Configuration Table:

Name*Delete
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Matching Criteria
Record ID*Enter or map it from the Trigger, or a previous step responses.
ID Type*Select Internal ID or External ID.

(*) required field

This Method is used to retrieve the details of an existing record within an Entity.
 
⚠️ Make sure that in your NetSuite account -> home -> Set Preferences -> you have have checked “SHOW INTERNAL IDS.

Configuration Table:

Name*Get
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Matching Criteria
Record ID*Select the ID in a dynamic list (can take time to load if there are too many records) or map it from the Trigger, or a previous step responses.
ID Type*Select Internal ID or External ID if you’re manually entering or mapping the Record ID.
Refer to Using External IDs.
Not Found Option*Success – When the record is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

This Method is used to retrieve the details of an existing record within an Entity.

Configuration Table:

Name*List
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Matching Criteria
Number of RecordsDefine the Number of records to be shown in the result. Default 100, max 1000.

(*) required field

This Method is used to update a record by providing it record ID.
 
▪️ Common Entities:
Customers: Update customer records in NetSuite, including individual customers and companies.
Vendors: Update vendors in your NetSuite account.
Contacts: Update contact records associated with customers, vendors, or other entities.
Sales Orders: Update sales orders in NetSuite, potentially triggered by events in other systems connected through Wiresk.
Purchase Orders: Update purchase orders for procuring goods or services.
Invoices: Update invoices for customers.
Inventory Items: Update items from your inventory management system in NetSuite.
Employees: Update employee records.
 
▪️ Other Entities:
Cases: Update support cases or tickets in NetSuite.
Opportunities: If you’re using NetSuite for CRM, you might be able to Update sales opportunities.
Journal Entries: Update journal entries for financial transactions.
Custom Records: Update records of custom record types defined in your NetSuite account.
 
⚠️ Remember that the availability of specific entities also depend on your NetSuite version, edition, and any industry-specific modules you have enabled.

Configuration Table:

Name*Update
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Matching Criteria
Record ID*Enter the ID or map it from the Trigger, or a previous step responses.
ID TypeSelect Internal ID or External ID if you’re manually entering or mapping the Record ID.
Refer to Using External IDs.
Map Fields [+ Add Field] you can add extra fields to populate.
Available Fields*Default displayed fields to populate depending on the selected Entity.

For example: From Entity “Account”, the default displayed fields are “Name”, “Number”, “Currency”.

(*) required field

This Method is used to update an existing record by matching it External ID, If the record doesn’t exist, a new record will be created with the provided information.
 
▪️ Common Entities:
Customers: Update or create customer records in NetSuite, including individual customers and companies.
Vendors: Update or create vendors in your NetSuite account.
Contacts: Update or create contact records associated with customers, vendors, or other entities.
Sales Orders: Update or create sales orders in NetSuite, potentially triggered by events in other systems connected through Wiresk.
Purchase Orders: Update or create purchase orders for procuring goods or services.
Invoices: Update or create invoices for customers.
Inventory Items: Update or create items in your inventory management system in NetSuite.
Employees: Update or create employee records.
 
▪️ Other Entities:
Cases: Update or create support cases or tickets in NetSuite.
Opportunities: If you’re using NetSuite for CRM, you might be able to Update or create sales opportunities.
Journal Entries: Update or create journal entries for financial transactions.
Custom Records: Update or create records of custom record types defined in your NetSuite account.
 
⚠️ Remember that the availability of specific entities also depend on your NetSuite version, edition, and any industry-specific modules you have enabled.

Configuration Table:

Name*Upsert
Connection*Select your connection or create one.
Entity*Select the Entity to create records within.
Matching Criteria
External ID*Enter the ID or map it from the Trigger, or a previous step responses (Method “List” or “Get“).
Refer to Using External IDs.
Map Fields [+ Add Field] you can add extra fields to populate.
Available Fields*Default displayed fields to populate depending on the selected Entity.

For example: From Entity “Account”, the default displayed fields are “Name”, “Number”, “Currency”.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings
This Method allows you to link a file to a specific record in the system by referencing their unique File ID and Record ID.
 
⚠️ Remember that the availability of specific records (entities) also depend on your NetSuite version, edition, and any industry-specific modules you have enabled.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Attach File
Connection*Select your connection or create one.
Map Fields
File ID*Enter the ID or map it from the Trigger, or a previous step responses.

Alternative method:
– Get The File ID Within the NetSuite Record
– Using NetSuite Search
– Using SuiteQL
– Using NetSuite’s REST API
File ID TypeSelect Internal ID or External ID if you’re manually entering or mapping the ID.
If not specified, the Internal ID is used.
Refer to Using External IDs.
Record Type (Entities)*Select the record type in a dynamic list.
Record ID*Enter the ID or map it from the Trigger, or a previous step responses.

(*) required field

This Method is used to create a new folder in NetSuite.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Create Folder
Connection*Select your connection or create one.
Map Fields
Folder Name*Name of the folder to create.
External IDOptionally define an External ID. If not provided, the system will use the Internal ID.
Refer to Using External IDs.
Parent FolderSelect a parent folder if needed.

(*) required field

This Method allows you to detach a file from a specific record in the system by referencing their unique File ID and Record ID.
 
⚠️ Remember that the availability of specific records (entities) also depend on your NetSuite version, edition, and any industry-specific modules you have enabled.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Detach File
Connection*Select your connection or create one.
Map Fields
File ID*Enter the ID or map it from the Trigger, or a previous step responses.

Alternative method:
– Get The File ID Within the NetSuite Record
– Using NetSuite Search
– Using SuiteQL
– Using NetSuite’s REST API
File ID TypeSelect Internal ID or External ID.
If not specified, the Internal ID is used.
Refer to Using External IDs.
Record Type (Entities)*Select the record type in a dynamic list.
Record ID*Enter the ID or map it from the Trigger, or a previous step responses.

(*) required field

This Method allows you to download an existing file from NetSuite.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Get File
Connection*Select your connection or create one.
Map Fields
File ID*Enter the ID or map it from the Trigger, or a previous step responses.

Alternative method:
– Get The File ID Within the NetSuite Record
– Using NetSuite Search
– Using SuiteQL
– Using NetSuite’s REST API
ID TypeSelect Internal ID or External ID.
If not specified, the Internal ID is used.
Refer to Using External IDs.

(*) required field

This Method is used to update a folder by it Folder ID.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Update Folder
Connection*Select your connection or create one.
Map Fields
Folder ID*Select the folder to update.
ID TypeSelect Internal ID or External ID if you’re manually entering or mapping the Folder ID.
If not specified, the Internal ID is used.
Refer to Using External IDs.
Folder NameChange the folder name.
Parent FolderChange the parent folder if needed.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings
This Method is used to retrieves data from a pre-defined Saved Search within your NetSuite account.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Get Saved Search
Connection*Select your connection or create one.
Map Fields
Saved Search Type*Select the Saved Search type in a dynamic list.
Saved Search ID*Choose the specific Saved Search you want to retrieve data from.
Number of RecordsSpecify the number of results on a single page. Default value is 100, max 1000.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings
This Method allows you to trigger the execution of a specific RESTlet by Script ID and deployment ID, within your NetSuite account directly from Wiresk.
 
⚠️ Before you can use a RESTlet, you must follow the guidelines from NetSuite, see more details here.
 
How to get the Script ID and deployment ID:
Go to Customization > Scripting > Script Deployments in your NetSuite account.

Script ID:
In the Script Deployments list, locate the deployment associated with your RESTlet.
The Script ID is typically a unique identifier for the SuiteScript code itself (e.g., “customscript_myrestlet”).

Deployment ID:
This is the unique identifier for the specific deployment of the script.
If you have enabled “Show Internal IDs” in your NetSuite preferences, the Deployment ID will be visible in the list.  
If not, you can hover over the deployment name in some cases, and a tooltip might display the internal ID.
 
Obtaining Deployment ID (Alternative Method)
Record Browser: Navigate to Lists > Records in NetSuite.
Search for “scriptdeployment” in the record type field.
This will open the Record Browser where you can search for your script deployment using its name or other criteria.
The internal ID (Deployment ID) will be displayed for each record.

Important Notes:
Show Internal IDs: Enabling “Show Internal IDs” in your NetSuite preferences is highly recommended as it makes finding these IDs much easier. You can usually enable this under Home > Set Preferences.  

Deployment Purpose: Ensure that the deployment you select is the correct one for the specific RESTlet you want to execute. Deployments can be used to manage different versions and environments (e.g., development, test, production) of your SuiteScript code.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*RESTlet
Connection*Select your connection or create one.
Map Fields
Script ID*This is the unique identifier assigned to the SuiteScript code that defines your RESTlet. You’ll need to provide the correct Script ID to specify which RESTlet you want to execute.
Deployment ID*This ID links the Script ID to a specific deployment within your NetSuite account. Deployments allow you to manage different versions and configurations of your SuiteScript code.
Method*Specify the HTTP method used to invoke the RESTlet.
GET – POST – PUT – DELETE
URL Parameters[+ Add Field] add an URL parameters.
Request BodyThis is an optional field and would be used to include any data or parameters that need to be sent to the RESTlet in the request body. This is applicable with the method “POST” or “PUT”.

(*) required field

NETSUITE LOGO NetSuite - Connection & Settings
This Method allows you to execute a REST API call.
 
⚠️ You can only access Beta endpoints if you are enrolled in a NetSuite Beta program.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*REST API Call
Connection*Select your connection or create one.
Map Fields
API Record Path*
Method*Specify the HTTP method to use:
GET – POST – PUT – PATCH – DELETE
Header[+ Add Field] add a Header.
URL Parameters[+ Add Field] add an URL parameters.
Request Body TypeSelect Mapping or JSON

(*) required field

This Method will execute a dynamic SuiteQL Query. See more details about SuiteQL.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*SuiteQL
Connection*Select your connection or create one.
Map Fields
SuiteQL*Enter your SuiteQL query.

(*) required field

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.

Important 01 NetSuite - Connection & Settings

Going further Copy Link

Explore the full Wiresk User Guide to learn more.

Looking for an integration that’s not yet available? Submit a request to our team, we’ll do our best to support your needs.