buddyboss/delete-thread removes a message thread from one participant’s mailbox.
The other participants keep theirs.
Before you run it
This removes the thread from one participant’s mailbox. The other participants keep their copies, so the conversation is not erased from the site — which means this is not a way to retract anything. For the member it does affect there is no trash and no undo. confirm_message_count must match the number of messages in the thread, because a subject line says nothing about how much correspondence it covers.
At a glance
| Ability | buddyboss/delete-thread |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Messages |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Destructive — removes a thread from one participant’s mailbox. Requires confirm_message_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
That asymmetry is worth stating clearly because it defeats the most common reason somebody would reach for this: retracting a message. The recipients still have it.
What it does do is clear a mailbox, permanently, for the member named. There is no trash and no undo for them.
The message-count confirmation exists because a thread is opaque from outside. A subject line reading “Quick question” can cover two messages or two hundred, and the ID conveys nothing either way.
buddyboss/list-threads reports the count, and it is checked live so a message arriving between the read and the write is caught.
Archiving through buddyboss/manage-thread gets a thread out of the way reversibly and is almost always the better answer.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
thread_id | integer | Yes | The thread. |
user_id | integer | Yes | Whose record this is. Required rather than defaulting, so an administrator’s own account is never acted on by accident. |
confirm_message_count | integer | Yes | Must match the number of messages in the thread. |
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 |
|---|---|---|
thread_id | integer | The thread. |
removed_for | integer | Whose mailbox it was removed from. |
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:
Remove that thread from this member’s inbox.
It resolves to one call:
{
"ability": "buddyboss/delete-thread",
"parameters": {
"thread_id": 512,
"user_id": 44,
"confirm_message_count": 18
}
}Worth knowing
- Other participants keep their copies. This is not a retraction.
- No trash for the member affected.
- The message count is checked live.
- Archiving is the reversible alternative.
Related abilities
- BuddyBoss Manage Message Thread — archive it instead
- BuddyBoss List Message Threads — get the message count
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category