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
Role → Update
AI-generatedSummary
Update an existing role in LLW CRM by ID, sending a PUT to /roles/{id} with the selected field values (currently only the role name).
Inputs
- resourceId (required) — ID of the role to update. It is placed in the request path (/roles/{id}).
- fieldsToUpdate — Repeatable list of field/value pairs. Field Name is a dropdown whose only choice is 'name'. Field Value is a string. Entries with an empty value are skipped. Each value is first parsed as JSON and falls back to the raw string if that fails, so a value like 123 or true is sent as a number or boolean.
Output shape
A single item whose json is the API's response to the PUT request, normally the updated role record. The item is paired with its input item.
If no fields are added, the PUT body is empty. If the API returns an array, each element becomes a separate item. With 'Continue on Fail' enabled, errors are returned as {error: message} instead of stopping the workflow. The node's Manage Associations option does not apply to roles.
Examples
Example 1: Rename a role
ID = 5; Fields to Update: add one field with Field Name = name and Field Value = 'Sales Manager'.
Example 2: Rename a role using an ID from a previous node
ID = {{$json.id}}; Field Name = name; Field Value = {{$json.newName}}.