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 sales orders, invoices, or customer records based on external triggers.
- Synchronizing data changes from other systems into NetSuite without manual entry.
- Bulk updating multiple records programmatically within workflows.
For example, a user could update the status of a sales order or change contact details for a customer automatically when certain conditions are met in another system.
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 Record". 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 new lines added rather than replaced. |
| Replace Selected Fields | If true, all fields that should be deleted must be included in the replace query parameter. Controls whether the update replaces only specified fields or deletes omitted fields 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 operation ID, job ID, property validation info if available.
- Success status indicated by HTTP status codes (204 means success with no content).
- Error information if the update failed, including error code, message, and details.
No binary data output is produced by this operation.
Dependencies
- Requires valid NetSuite API credentials with appropriate permissions to update records.
- Uses the NetSuite REST API endpoint configured via these credentials.
- Supports concurrency control to limit parallel API calls.
- Requires n8n environment to have network access to NetSuite services.
Troubleshooting
- Invalid Record Type or ID: Errors occur if the record type or internal ID does not exist or is incorrect. Verify the exact record type and ID before running.
- Permission Denied: Insufficient API permissions can cause authorization errors. Ensure the API key/token has rights to update the specified record type.
- Replace Sublists Misuse: Incorrectly specifying sublist names in the replace parameter may lead to partial updates or unintended data loss. Use carefully.
- API Rate Limits: Exceeding concurrency limits or API quotas may result in throttling errors. Adjust concurrency option accordingly.
- Malformed Data: Sending invalid field values or missing required fields can cause validation errors. Check the error messages returned for details.
- Continue On Fail: If enabled, errors will be returned as part of the output instead of stopping execution, useful for bulk operations.