Actions126
- Account Actions
- City Actions
- Contact Actions
- Contact Line of Business Actions
- Contact Number of Employees Actions
- Contact Origin Actions
- Contact Product Actions
- Contact Relationship Actions
- Contact Status Actions
- Contact Type Actions
- Country Actions
- Currency Actions
- Deal Actions
- Deal Loss Reason Actions
- Deal Pipeline Actions
- Deal Stage Actions
- Deal Status Actions
- Department Actions
- Document Actions
- Document Template Actions
- Field Actions
- Field Entity Actions
- Field Options Table Actions
- Field Options Table Option Actions
- Field Type Actions
- Interaction Record Actions
- Operation Actions
- Order Actions
- Order Stage Actions
- Phone Type Actions
- Product Actions
- Product Family Actions
- Product Group Actions
- Product Part Actions
- Quote Actions
- Quote Approval Status Actions
- Relative Date Actions
- Role Actions
- State Actions
- Tag Actions
- Task Actions
- Task Email Reminder Actions
- Task Repeat Interval Unit Actions
- Task Type Actions
- Team Actions
- User Actions
- User Profile Actions
- Webhook Actions
- Webhook Action Actions
User → Update
AI-generatedSummary
Update an existing Ploomes CRM user by sending a PATCH request to /Users(ID) with the user properties supplied in a JSON body.
Inputs
- resourceId (required) — ID of the user to update.
- body — JSON containing the user properties to update. Defaults to {}; JSON strings are parsed before sending. The node does not define or validate individual user fields.
Output shape
Success, Error, and Timeout outputs containing JSON items.
Success returns the API response directly, or one item per entry if the response contains a value array. An empty response produces {success: true, resource, operation, timestamp}. Errors include error, statusCode, isTimeout, resource, operation, and timestamp. HTTP 408 and 504 go to Timeout; other errors go to Error when Continue On Fail is enabled, otherwise execution throws.