NetSuite REST Azerion icon

NetSuite REST Azerion

Call NetSuite SuiteTalk REST operations.

Actions981

Customer Category → Remove record

AI-generated

Summary

Delete a customer category record in NetSuite by its internal identifier.

Inputs

  • id (required) — Internal identifier of the customer category to remove. It is the sole required parameter for this operation and maps to the path /customerCategory/{id} in the DELETE request. The display options confirm this: operation: [delete /customerCategory/{id}] with resource: [CustomerCategory].},{
  • authMethod — Authentication method to use for the request. Defaults to OAuth1 if not specified. Only OAuth1 and OAuth2 are supported, expressed as options oauth1 and oauth2. The property has noDataExpression: true, meaning it cannot be dynamically overridden per item.},{
  • isDebugMode — When enabled, full request and response details are included in the operation output. Defaults to false. This is a boolean UI property directly from the node's description properties.
  • additionalFields — Collection of optional request-level fields. Currently supports two named options: Prefer (with value respond-async to execute the request asynchronously, returning Preference-applied: respond-async in the response) and X-NetSuite-Idempotency-Key (a user-defined UUID per RFC 4122 to ensure the request executes only once; ignored for synchronous requests). Defaults to an empty object.

Output shape

The operation returns the n8n item augmented with debug information if isDebugMode is true, otherwise the standard item flow continues. No specific return data shape is declared in the properties or source; the node emits the API response body as the item's data, subject to the chosen authentication and debug configuration.

The operation corresponds to a DELETE request to /customerCategory/{id}. The id parameter is mandatory. Authentication is configured per workflow via authMethod. Additional headers for async execution (Prefer: respond-async) and idempotency (X-NetSuite-Idempotency-Key) are available under additionalFields. All parameter behaviors are derived directly from the operation-scoped UI properties.

Examples

Example 1: Remove a customer category by ID using default OAuth1 authentication.

Set id to the target category's internal identifier. Leave authMethod at its default oauth1. Disable isDebugMode for normal flow.

Example 2: Asynchronously delete a customer category with an idempotency key.

Set id to the target category. In additionalFields, set Prefer to respond-async and provide a unique UUID string for X-NetSuite-Idempotency-Key. Enable isDebugMode if request/response logging is needed.

Links

Discussion