NetSuite Restlet icon

NetSuite Restlet

This package allows for a "single-node" method of connecting your n8n instance with your NetSuite Restlet
Join our community

Overview

This node enables seamless integration between n8n and NetSuite Restlets by allowing users to send HTTP requests directly to a specified NetSuite Restlet URL. It supports all common HTTP methods (GET, POST, PUT, DELETE) and handles OAuth 1.0a authentication with HMAC-SHA256 signature, which is required by NetSuite for secure API access.

Typical use cases include:

  • Retrieving data from NetSuite via GET requests with query parameters.
  • Creating or updating records in NetSuite using POST or PUT requests with JSON bodies.
  • Deleting records or triggering actions via DELETE requests.
  • Any custom business logic exposed through NetSuite Restlets that requires programmatic interaction.

For example, a user might configure this node to call a Restlet that returns customer information filtered by certain criteria or to update inventory levels by sending JSON payloads.

Properties

Name Meaning
Restlet URL The full URL of the NetSuite Restlet endpoint to call. Example: https://1234567.restlets.api.netsuite.com/app/site/hosting/restlet.nl?script=1&deploy=1
Method The HTTP method to use for the request. Options: GET, POST, PUT, DELETE.
Query Parameters (Shown only for GET and DELETE) A collection of key-value pairs appended as URL query parameters.
Request Body (Shown only for POST and PUT) A JSON object representing the body of the request sent to the Restlet.

Output

The node outputs an array of JSON objects corresponding to the response received from the NetSuite Restlet. The entire response JSON is returned as the json field of each output item.

If the Restlet returns binary data, it would be handled as part of the response, but this node primarily expects JSON responses and does not explicitly handle binary output.

Dependencies

  • Requires valid OAuth 1.0a credentials for NetSuite API access, including consumer key/secret and token ID/secret.
  • The node uses OAuth 1.0a with HMAC-SHA256 signature method for authentication.
  • Requires the user to provide the correct Restlet URL and ensure the Restlet script is deployed and accessible.
  • No additional external services beyond NetSuite are needed.

Troubleshooting

  • Authentication errors: If the OAuth credentials are incorrect or expired, the node will fail to authenticate. Verify that the consumer key, consumer secret, token ID, and token secret are correctly configured.
  • Invalid URL or deployment: Ensure the Restlet URL is correct and the script is properly deployed in NetSuite.
  • Empty or malformed request body: For POST and PUT methods, if the request body is empty or invalid JSON, the Restlet may reject the request. Provide valid JSON input.
  • Query parameter issues: For GET and DELETE methods, ensure query parameters have both name and value set; empty names or values are ignored.
  • Unexpected response format: The node expects JSON responses. If the Restlet returns non-JSON data, parsing errors may occur.

Links and References

Discussion