NetSuite Restlet icon

NetSuite Restlet

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

NetSuite Restlet

AI-generated

Overview

This node allows users to connect their n8n instance with a NetSuite Restlet using a single node. It supports making HTTP requests (GET, POST, PUT, PATCH, DELETE) to a specified NetSuite Restlet URL with optional query parameters or request body. This is useful for integrating NetSuite data and processes into n8n workflows, such as retrieving records, updating data, or triggering custom NetSuite scripts.

Use Case Examples

  1. A user wants to fetch customer data from NetSuite by making a GET request with query parameters.
  2. A user needs to update a record in NetSuite by sending a PATCH request with a JSON body.
  3. A user wants to delete a record in NetSuite using a DELETE request with query parameters.

Properties

Name Meaning
Restlet URL The full URL of the NetSuite Restlet to which the request will be sent. This is required.
Method The HTTP method to use for the request. Supported methods are DELETE, GET, PATCH, POST, and PUT.
Query Parameters Key-value pairs to be appended as query parameters to the URL. Only shown and used for GET and DELETE requests.
Request Body The JSON body to send with the request. Only shown and used for POST, PUT, and PATCH requests.

Output

JSON

  • headers - HTTP response headers from the NetSuite Restlet.
  • statusCode - HTTP status code of the response.
  • * - The JSON response body returned by the NetSuite Restlet, merged into the output object.

Dependencies

  • An API key credential for NetSuite Restlet authentication including consumer key, consumer secret, token ID, token secret, and realm.

Troubleshooting

  • If the node returns an HTTP status code 400 or above, it indicates an error from the NetSuite Restlet. The error message and status code are included in the output.
  • Ensure the Restlet URL is correct and accessible.
  • Verify that the API credentials (consumer key, consumer secret, token ID, token secret, and realm) are valid and have the necessary permissions.
  • If the node is set to continue on fail, errors will be returned as part of the output instead of stopping execution.

Discussion