Actions34
- Alert Actions
- Asset Actions
- Client Actions
- Requester Actions
- Ticket Actions
- Worklog Actions
Requester → Update
AI-generatedSummary
Updates an existing SuperOps requester using a numeric User ID, allowing partial updates to fields such as contact details, email, and role associations.
Inputs
- userId (required) — Numeric SuperOps user ID of the requester (e.g. 7928838372746166272).
- updateFields — A collection of fields to update. Fields are optional; providing an empty object results in a no-op update request. Includes Contact Number, Email, First/Last Name, Reporting Manager User ID, Role ID, and Site ID. Custom Fields (JSON) can also be included.
Output shape
A single record containing the updated requester's data (userId, firstName, lastName, name, email, contactNumber, site, role, client, and customFields).
The operation returns the updated requester object. If no fields are provided, it still returns the current requester data. The node handles input pruning, removing empty strings and undefined values before sending the GraphQL mutation.
Examples
Example 1: Update a requester's email and contact number.
Set userId to the target user's ID and provide updateFields with email and contactNumber.
Example 2: Update a requester's role and site assignment.
Set userId and provide updateFields with roleId and siteId.
Example 3: Update custom fields via JSON.
Set userId and provide updateFields with customFields as a JSON object mapping custom field names to values.