buddyboss/manage-profile-data writes one member’s answers to profile fields, or clears them.
Read buddyboss/list-profile-fields first — for the IDs, and just as importantly for the types.
At a glance
| Ability | buddyboss/manage-profile-data |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Profiles |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
The silent failure
A value that does not match the field type is accepted without complaint. No error, no warning; the write succeeds and the field displays as empty.
That is the failure to design around, because it is indistinguishable from a field nobody filled in. A date written in the wrong format, a value not in a select field’s options, a string in a number field — all of them produce the same nothing.
So the schema read is not optional diligence here, it is how you know the write will stick.
Several fields can be written at once with the values array, which is the efficient shape for importing or correcting a member’s profile in one call.
action=clear empties an answer for this member only. The field itself and everyone else’s answers are untouched — clearing a field for the whole community is buddyboss/delete-profile-field, which is a different and much larger operation.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | Yes | Whose profile to write. |
action | string | No — defaults to set | set or clear. |
values | array | For set | One entry per field: its ID and the value, matching the field’s type. |
field_id | integer | For clear | Which field to empty. |
What comes back
| Name | Type | What it is |
|---|---|---|
written | array | The fields written. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Set this member’s job title and location.
It resolves to one call:
{
"ability": "buddyboss/manage-profile-data",
"parameters": {
"user_id": 44,
"values": [
{ "field_id": 12, "value": "Head of Support" },
{ "field_id": 15, "value": "Bristol" }
]
}
}Worth knowing
- A type mismatch is accepted and shows as empty. There is no error.
- Read the schema for types and options before writing.
- Clearing affects this member only.
- Idempotent.
Related abilities
- BuddyBoss List Profile Fields — required before this
- BuddyBoss Get Member — read the current values
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category