buddyboss/delete-activity permanently deletes an activity item together with every comment beneath it.
The confirmation requirement varies by how much is attached.
Before you run it
Deleting an item deletes every comment under it, and a comment thread is frequently far larger than the post that started it. Items with comments require confirm_comment_count to match the live number, which buddyboss/get-activity reports; items with none do not, so the confirmation stays meaningful instead of becoming a reflex. To hide spam rather than destroy it, use buddyboss/act-on-activity with spam=true.
At a glance
| Ability | buddyboss/delete-activity |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Activity |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive and permanent — deletes the item and every comment beneath it. Items with comments require confirm_comment_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
An item with no comments needs no count. An item with comments requires confirm_comment_count matching the live number.
That asymmetry is deliberate. A confirmation demanded on every call becomes a reflex that gets typed without reading, and a reflex is not a check. Asking only when there is something to lose keeps the question live.
The count is checked against the record at delete time, so it also catches the case where somebody commented between your read and your write.
buddyboss/get-activity is where the count comes from, and reading it is the planning step rather than an obstacle — it is also where you see what the comments actually are.
Marking as spam is the reversible alternative, and it is the right move for anything being removed for moderation rather than for correctness.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
activity_id | integer | Yes | The activity item. |
confirm_comment_count | integer | When the item has comments | Must match the live comment count. |
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 |
|---|---|---|
activity_id | integer | The item deleted. |
comments_deleted | integer | How many comments 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 that activity post and its thread.
It resolves to one call:
{
"ability": "buddyboss/delete-activity",
"parameters": {
"activity_id": 9102,
"confirm_comment_count": 14
}
}Worth knowing
- Every comment beneath the item goes with it.
- The count is only required when there is something to lose.
- Checked live, so it catches comments added since your read.
- Spam-marking is the reversible alternative.
Related abilities
- BuddyBoss Get Activity — get the comment count
- BuddyBoss Act On Activity — hide it instead
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category