Overview
This node integrates with the NetSuite REST API to perform various record management operations. Specifically, the "Update Record" operation allows users to modify existing records in their NetSuite account by specifying the record type and internal ID along with the updated data fields.
Common scenarios where this node is beneficial include:
- Automating updates to customer or sales order records based on external triggers.
- Synchronizing data changes from other systems into NetSuite.
- Bulk updating inventory items or financial records programmatically.
For example, a user could update a Sales Order record's status or add notes to a Customer record automatically when certain conditions are met in their workflow.
Properties
| Name | Meaning |
|---|---|
| Record Type | The type of NetSuite record to update. Options include many standard record types such as Assembly Item, Billing Account, Calendar Event, Cash Sale, Contact, Customer, Invoice, Sales Order, Vendor, and more. |
| Custom Record Script ID | Required if the Record Type is "Custom". This is the internal identifier (script ID) of the custom record type, typically starting with "customrecord". |
| ID | The internal identifier of the specific record to update. Can be prefixed with eid: to use an external identifier instead. |
| Replace Sublists | (Optional) Comma-separated names of sublists on the record that should be fully replaced with the provided lines. Sublists not listed will have lines added rather than replaced. |
| Replace Selected Fields | If true, all fields that should be deleted must be included in the replace query parameter. This controls whether the update replaces only specified fields or deletes unspecified ones as well. |
| API Version | The version of the NetSuite REST API to use. Currently only "v1" is supported. |
| Options | Additional options including: - Concurrency: Maximum number of simultaneous REST requests sent to NetSuite (default 1). - Full Response: Whether to return the full HTTP response or just the body content. |
Output
The output is a JSON object representing the response from the NetSuite REST API after attempting to update the record. It includes:
- The updated record data if successful.
- Metadata such as property validation errors, operation IDs, job IDs, and links if available.
- A success flag indicating if the update was successful.
- In case of failure, an error message describing the issue.
No binary data output is produced by this operation.
Dependencies
- Requires valid NetSuite API credentials including authentication tokens and account details.
- Uses the NetSuite REST API endpoint configured via these credentials.
- Supports concurrency control for managing multiple simultaneous requests.
- Requires n8n environment to have network access to NetSuite services.
Troubleshooting
- Invalid Record Type or ID: Errors occur if the specified record type or internal ID does not exist or is incorrect. Verify the record type selection and ensure the internal ID is accurate.
- Authentication Failures: Ensure that the API key or token credentials are correctly configured and have sufficient permissions to update records.
- Concurrency Limits: Setting concurrency too high may cause rate limiting or throttling by NetSuite. Adjust concurrency to a lower value if encountering request failures.
- Replace Sublists Misconfiguration: Incorrectly specifying sublist names in the "Replace Sublists" property can lead to partial updates or unintended data loss. Confirm sublist names match NetSuite definitions.
- Error Messages: The node surfaces error messages returned by NetSuite. Common messages include permission denied, invalid field values, or missing required fields. Review the error details and adjust input accordingly.
- Continue On Fail: If enabled, the node will continue processing remaining items even if some fail, returning error objects in output for failed items.