buddyboss/manage-reactions handles likes and emoji reactions.
Call action=list first. There is nothing portable to assume here.
At a glance
| Ability | buddyboss/manage-reactions |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Activity |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| 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 |
Two modes, and two kinds of ID
A site runs reactions in either likes mode — a single Like — or emotions mode, with a configurable set. Which mode, and which reactions exist in it, differ per site.
So the available IDs cannot be known in advance, and a hard-coded reaction ID is a call that works on one site and fails on the next.
The second trap is subtler. action=remove needs the user-reaction ID — the record of this person having reacted — returned when the reaction was added or by action=list-user-reactions.
It does not take the reaction type ID, which merely names which reaction it is. The two are both integers and both come back from this ability, which is exactly the shape of a mistake that produces a confusing failure.
Not idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
action | string | Yes | list, add, remove or list-user-reactions. |
item_id | integer | For add and listing user reactions | What is being reacted to. |
item_type | string | For add | What kind of item it is. |
reaction_id | integer | For add | The reaction type ID. |
user_reaction_id | integer | For remove | The user-reaction record ID — not the reaction type ID. |
What comes back
| Name | Type | What it is |
|---|---|---|
reactions | array | The available reactions, for list. |
mode | string | Likes mode or emotions mode. |
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:
What reactions can people leave here?
It resolves to one call:
{
"ability": "buddyboss/manage-reactions",
"parameters": {
"action": "list"
}
}Worth knowing
- Reaction IDs are per site. Nothing is portable.
- Removing needs the user-reaction ID, not the reaction type ID.
- Both are integers, which is why the mistake is easy.
- Not idempotent.
Related abilities
- BuddyBoss Get Activity — the items reactions attach to
- BuddyBoss Act On Activity — favouriting, which is separate
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category