buddyboss/delete-profile-field-group deletes a profile field group together with every field inside it, and every member’s answer to every one of those fields.
The primary field group cannot be deleted at all.
Before you run it
This is much larger than deleting a single field: the group goes, every field inside it goes, and every member’s answer to every one of those fields goes with them — permanently, with no option to keep the values. It asks a different question for that reason: confirm_field_count must equal the number of fields in the group and confirm_name must match its name. Call buddyboss/list-profile-fields first to see what the group contains.
At a glance
| Ability | buddyboss/delete-profile-field-group |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Profiles |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive and permanent — deletes the group, every field in it, and every answer. Requires confirm_name and confirm_field_count. |
| Repeatable | Not idempotent — each call changes the row set, so re-running is not a no-op |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The confirmation asks for the field count rather than an answer count, because that is the number that describes the scale here. A group holding one field and a group holding twelve are very different deletions, and the ID tells you nothing about which you have.
Unlike the single-field deletion, there is no option to keep the answers. Group deletion takes everything.
The primary field group is protected outright. It holds the member name that every profile on the site depends on, and deleting it would break every profile rather than emptying them.
Reading the group first is the only way to know what is in it. buddyboss/list-profile-fields returns the fields nested under their groups, which is exactly the shape needed to make this decision.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
group_id | integer | Yes | The field group to delete. |
confirm_name | string | Yes | Must match the group name exactly. |
confirm_field_count | integer | Yes | Must equal the number of fields in the group. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
group_id | integer | The group removed. |
fields_deleted | integer | How many fields went with it. |
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:
Delete the old onboarding profile group.
It resolves to one call:
{
"ability": "buddyboss/delete-profile-field-group",
"parameters": {
"group_id": 4,
"confirm_name": "Onboarding questions",
"confirm_field_count": 6
}
}Worth knowing
- Every field and every answer goes. There is no keep-the-values option.
- The primary group is protected — it holds the member name.
- The field count is the confirmation because it describes the scale.
- Read the group contents first.
Related abilities
- BuddyBoss List Profile Fields — see what is in the group
- BuddyBoss Delete Profile Field — the smaller version
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category