Actions134
- Activity Actions
- Activity Type Actions
- Call Actions
- Call Outcome Actions
- Comment Actions
- Company Actions
- Contact Actions
- Country Actions
- Currency Actions
- Deal Actions
- Document Actions
- Document Type Actions
- Industry Actions
- Note Actions
- Pipeline Actions
- Pipeline Stage Actions
- Product Actions
- Role Actions
- Source Actions
- Team Actions
- Timezone Actions
- Trashed Record Actions
- User Actions
Product → Update
AI-generatedSummary
Updates an existing LLW CRM product by ID, sending only the fields you choose (name, description, unit_price, tax_rate, sku, is_active) via a PUT request to /products/{id}.
Inputs
- resourceId (required) — ID of the product to update. It is placed in the URL path /products/{id}.
- fieldsToUpdate — Repeatable list of Field Name / Field Value pairs. Field Name is one of name, description, unit_price, tax_rate, sku or is_active. Each Field Value is entered as a string. The node tries to parse it as JSON first, so 12.5 becomes a number and true/false become booleans. If parsing fails, it sends the raw string. Pairs with an empty value are skipped, so you can't clear a field this way. If you add the same field twice, the later pair overrides the earlier one.
Output shape
One item per input item. The item's json is the API's response to the PUT request, normally the updated product record. Each item is paired to its input item.
If no valid field pairs are given, the node still sends the PUT with an empty body. Authentication uses the llwCrmApi credential's domain and bearer token. API errors throw a NodeApiError. With Continue On Fail enabled, the output is {error: message} for that item. The Manage Associations option is not shown for Product, so it has no effect here.
Examples
Example 1: Change the price and deactivate a product
ID = 42; Fields to Update: unit_price = 99.95, is_active = false
Example 2: Rename a product using an incoming item's ID
ID = {{$json.productId}}; Fields to Update: name = Premium Plan