list_user_attributes, and
the user’s current values with get_user.
Every value is checked before the first write, so a call writes all of its
values or none; sending values the user already holds changes nothing, so the
same call can be sent twice.
An amount keeps the currency the user holds it in, as in the Qobra web app.
Changing a unique attribute re-matches, in the background, the data table
records matched to users on it.
On an attribute synced from an HRIS, a value you write is kept as an overwrite:
later syncs leave it in place, and Qobra keeps the synced value beside it.
Sending the synced value back, or null, cancels the overwrite.
Statements are not recalculated by this call, as after an edit in the web app:
a calculation reading these attributes picks the change up the next time it
runs.
The call is refused, with a message naming the problem, when the user is
archived, when an attribute is unknown or sent twice, when a value does not
match its attribute’s type or picklist options, or when a unique attribute is
given a value another user already holds.
Requires write permission on users. Every write is recorded in the audit trail
as the Qobra MCP agent.
Example arguments
Parameters
Body
Body