buddyboss/manage-connection handles both kinds of link between members: friendships, which are mutual and need accepting, and following, which is one-way and immediate.
A site may have either component enabled without the other, and each action reports which it used.
At a glance
| Ability | buddyboss/manage-connection |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Members & Connections |
| 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 |
A default that reads as its own inverse
action=list shows confirmed friendships by default. BuddyBoss’s own default is the opposite — it returns only pending requests — which reads as an answer to “who are this member’s connections” while being very nearly the inverse of one.
That is the kind of default worth changing deliberately, and it is changed here. Pass state=pending for outstanding requests.
The two features are genuinely different. A friendship is a negotiation: request sends one, accept and reject answer it, remove ends an established one. Following is a decision one person makes: follow and unfollow take effect at once and the other member is not consulted.
Accepting a request on somebody’s behalf consumes a decision that was theirs. It is occasionally the right administrative action and it is worth being aware that it is one.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
action | string | Yes | list, request, accept, reject, remove, follow or unfollow. |
user_id | integer | Yes | Whose connections these are. |
target_user_id | integer | For the write actions | The other member. |
state | string | For list | Defaults to confirmed friendships. Pass pending for outstanding requests. |
What comes back
| Name | Type | What it is |
|---|---|---|
connections | array | The connections, for list. |
feature | string | Whether friendships or following was used. |
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:
Who is this member connected to?
It resolves to one call:
{
"ability": "buddyboss/manage-connection",
"parameters": {
"action": "list",
"user_id": 44
}
}Worth knowing
- Listing shows confirmed friendships, not pending ones — the opposite of BuddyBoss’s default.
- Friendships are mutual; following is not.
- Accepting on somebody’s behalf takes a decision that was theirs.
- Either component can be off independently.
Related abilities
- BuddyBoss Get Community Overview — which components exist
- BuddyBoss Search Message Recipients — connections can gate messaging
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category