Overview
This node allows users to make raw HTTP requests directly to the NetSuite REST API, providing maximum flexibility for interacting with NetSuite resources beyond predefined operations. It supports various request types such as Record, SuiteQL, Workbook, and Dataset, enabling users to perform custom queries, data retrieval, updates, or deletions.
Common scenarios include:
- Executing custom SuiteQL queries to retrieve complex datasets.
- Accessing or manipulating specific NetSuite records via direct REST endpoints.
- Performing operations on workbooks or datasets that are not covered by standard node operations.
- Sending any HTTP method (GET, POST, PATCH, DELETE, etc.) to a specified NetSuite API path.
Practical example:
- A user wants to run a custom SuiteQL query to fetch sales orders with specific criteria not available in standard nodes. They can use this node with
Request Typeset to "SuiteQL", specify the HTTP method as POST, provide the SuiteQL query in the body, and get the results directly.
Properties
| Name | Meaning |
|---|---|
| Request Type | The type of NetSuite resource or API to target. Options: Record, SuiteQL, Workbook, Dataset. |
| HTTP Method | The HTTP method to use for the request. Options: DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT. |
| Path | The API endpoint path relative to the NetSuite REST base URL (e.g., services/rest/record/v1/salesOrder). Can also be a full URL. |
| Body | The request payload as a string, used for methods like POST, PATCH, PUT. Optional. |
| Options | Additional options: |
| Concurrency | Maximum number of concurrent REST requests sent to NetSuite. Default is 1. |
| Full Response | If true, returns the full HTTP response including status code and headers instead of just the body. |
Output
The output JSON structure depends on the response from the NetSuite API:
- By default, the node outputs the parsed JSON body of the HTTP response under the
jsonfield. - If the "Full Response" option is enabled, the output includes an object with:
statusCode: HTTP status code of the response.headers: HTTP response headers.body: Parsed JSON body of the response.
The node does not explicitly handle binary data output.
Dependencies
- Requires valid NetSuite API credentials configured in n8n to authenticate requests.
- Uses the
@fye/netsuite-rest-apipackage internally to make REST API calls. - Supports concurrency control via the
p-limitpackage to limit simultaneous requests.
Troubleshooting
- Invalid Credentials or Authentication Errors: Ensure that the API key or token credentials are correctly configured and have sufficient permissions.
- Incorrect API Path or Method: Verify the
PathandHTTP Methodvalues match the NetSuite REST API specification. Using unsupported paths or methods will result in errors. - Malformed Request Body: When sending a body payload, ensure it is valid JSON or the expected format for the API endpoint.
- Rate Limiting or Concurrency Issues: If you encounter rate limiting errors, reduce the concurrency setting to send fewer simultaneous requests.
- Error Responses from NetSuite: The node surfaces error messages returned by NetSuite. Check the error details in the output to diagnose issues.
- Continue On Fail Behavior: If enabled, the node will continue processing other items even if some fail, returning error objects instead of stopping execution.