buddyboss/get-member fetches a single member: their name, login, registration date, last activity and avatar, plus their xProfile field values.
The profile section depends on a component being active.
At a glance
| Ability | buddyboss/get-member |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Members & Connections |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
Profile fields are returned only when the Profile Fields component is on. When it is off the member record still comes back and the profile section says so — rather than being absent, which would read as a member who has filled nothing in.
That distinction matters when auditing: “no profile data” and “no profile system” are different findings.
The login is worth noting alongside the display name. Display names are not unique on BuddyBoss, and several destructive abilities in this suite confirm against the login for exactly that reason.
Last activity is the field most reporting hangs off, and it depends on activity being recorded — a community with the activity component off has members with no last-activity value at all.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
user_id | integer | Yes | The member ID. |
What comes back
| Name | Type | What it is |
|---|---|---|
member | object | Name, login, registration date, last activity, avatar and profile field values. |
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:
Tell me about member 44.
It resolves to one call:
{
"ability": "buddyboss/get-member",
"parameters": {
"user_id": 44
}
}Worth knowing
- Profile fields need the Profile Fields component active. Absence is reported, not implied.
- The login is unique; the display name is not.
- Last activity depends on the activity component recording anything.
- Read-only.
Related abilities
- BuddyBoss List Profile Fields — the schema behind the values
- BuddyBoss Manage Member — change their type or display name
- BuddyBoss List Members — find the ID
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category