NetSuite REST Azerion icon

NetSuite REST Azerion

Call NetSuite SuiteTalk REST operations.

Actions981

Contact Category → Update record

AI-generated

Summary

Updates a contact category record in NetSuite via PATCH /contactCategory/{id}.

Inputs

  • id (required) — Internal identifier of the contact category to update.
  • isDebugMode — Whether to include full request and response info in the output.
  • authMethod — Authentication method for the request. Defaults to OAuth1. OAuth2 is also supported.
  • additionalFields — Collection of additional fields to include in the update. Supports name, externalId, isInactive, id (internal ID), Prefer (including respond-async), private, refName, replace (sublist names comma-delimited), replaceSelectedFields, X-NetSuite-Idempotency-Key, X-NetSuite-PropertyNameValidation, and X-NetSuite-PropertyValueValidation.
  • customFields — Fixed collection of custom fields to assign to the contact category. Each entry specifies a fieldName (required, loaded via loadCustomFields), fieldType (required, options: boolean/dateTime/multiSelect/number/select/string), and a value matching the selected type.

Output shape

The updated contact category record as returned by the NetSuite API. Exact field shape depends on the provided parameters and API response.

Authentication defaults to OAuth1; switch to OAuth2 via authMethod if required. Idempotency keys and property validation headers are supported for fine-grained NetSuite API control. Debug mode includes full request/response details in the node output.

Examples

Example 1: Update a contact category's name and mark it inactive.

Set id to the target category's internal ID, name to the new name within additionalFields, and isInactive to true.

Example 2: Update custom fields on a contact category.

Use customFields to specify fieldName, fieldType, and corresponding value. Multiple custom field entries are supported.

Links

Discussion