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
User → Update
AI-generatedSummary
Updates an existing LLW CRM user by ID, sending only the selected fields (name, email, password, timezone) in a PUT request to /users/{id}.
Inputs
- ID (resourceId) (required) — ID of the user to update. It is used in the request path /users/{ID}.
- Fields to Update (fieldsToUpdate) — Repeatable list of Field Name and Field Value pairs. Field Name is one of name, email, password or timezone. Pairs whose value is empty are skipped. Each value is first parsed as JSON and falls back to the raw string if parsing fails. A value like 123 or true therefore becomes a number or boolean, not a string. If no pairs are added, the PUT body is empty.
Output shape
A single item containing the JSON response from the LLW CRM API, which is normally the updated user record.
With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. The shared Manage Associations options are defined for some resources but not for user, so they aren't offered here. Authentication uses the llwCrmApi credential (domain and API token).
Examples
Example 1: Change a user's timezone and email
ID = 42; Fields to Update: timezone = America/New_York, email = new@example.com
Example 2: Reset a user's password
ID = {{$json.userId}}; Fields to Update: password = a new password string