BuddyBoss Integration: Triggers, Actions, and Automation Examples
The BuddyBoss integration connects Krom Automation Pro to your BuddyBoss Platform or BuddyPress community.
It gives you 14 triggers, 8 actions, BuddyBoss-specific condition fields, and 8 ready-to-import workflow templates, so you can automate onboarding, engagement, and moderation without writing code.
Krom Automation detects BuddyBoss automatically. There is nothing to configure to enable the integration itself.
Requirements
Krom Automation (lite version) and Krom Automation Pro must both be active, alongside BuddyBoss Platform or BuddyPress. Individual triggers and actions also need their related BuddyBoss component active, such as Groups, Activity, Connections, Messages, Forums, or Extended Profiles.
How Component Detection Works #
Krom Automation always registers the full set of BuddyBoss triggers and actions, even if a component is temporarily switched off. This keeps saved workflows and imported templates valid rather than breaking when you toggle a component.
- A trigger simply does not fire if its required component is disabled.
- An action fails gracefully and writes a clear error to your execution logs if its component is unavailable.
- Every BuddyBoss trigger supports conditions and delays like any other trigger.
- Every BuddyBoss action supports merge tags.
BuddyBoss Triggers in Krom Automation #
| Trigger | Required component | What it fires on |
|---|---|---|
| Member Activated | Member activation | A new account is activated |
| Profile Updated | Extended Profiles | A member edits their profile |
| Avatar Updated | Extended Profiles | A member uploads a new avatar |
| Connection Requested | Connections | One member sends a connection request |
| Connection Accepted | Connections | A connection request is accepted |
| New Follower | Activity Follow | One member follows another |
| Group Joined | Groups | A member joins a group |
| Group Left | Groups | A member leaves a group |
| Group Created | Groups | A new group is created |
| Forum Topic Created | Forums | A new forum topic is posted |
| Forum Reply Created | Forums | A reply is posted to a topic |
| Activity Posted | Activity | A status update is posted, on the main feed or in a group |
| Activity Comment Posted | Activity | A comment is added to an activity post |
| Private Message Sent | Messages | A member sends a private message |
A note on filtering. Group Joined, Group Left, Forum Topic Created and Forum Reply Created all support an optional ID filter, so a workflow can target one specific group or forum rather than every one on your site. Activity Posted can be filtered to member-only activity or group-only activity.
Who Counts as the Primary User
Most BuddyBoss events involve two people, and Krom Automation needs to know which one is “the user” for merge tags and run-once behavior. The rule is:
- Connection requested: the member who sent the request
- Connection accepted: the member who accepted it
- New follower: the member doing the following
- Private message sent: the sender
- Forum reply created: the person who wrote the reply
This matters if you are using {{user_id}} in an action, since it always resolves to the person on this list, not the other party in the interaction.
BuddyBoss Actions in Krom Automation #
| Action | What it does |
|---|---|
| Add User to Group | Adds a member to a group. Adding someone already in the group succeeds silently |
| Remove User from Group | Removes a member from a group |
| Post Activity Update | Posts to a member’s activity feed, or to a group feed if a group is specified |
| Send Private Message | Sends a private message to one or more recipients |
| Set Profile Field | Updates a single Extended Profile field for a member |
| Set Member Type | Assigns a member type. Replaces existing types unless you choose to append |
| Create Connection | Creates a connection between two members and force-accepts it immediately |
| Follow Member | Makes one member follow another |
Two behaviors worth knowing before you build with these
- Create Connection skips the pending-request step and force-accepts immediately, so it does not send the usual “someone wants to connect” notification.
- And Set Member Type expects the registered member-type slug, not the label shown in the admin, so check your BuddyBoss member type settings if the action fails silently.
Every action here defaults to {{user_id}} when a user field is left empty, so a workflow that starts on a BuddyBoss trigger can usually chain straight into one of these actions without manually mapping the ID.
Merge Tags for BuddyBoss Workflows #
The primary member from any trigger is available as {{user_id}}, {{user_email}}, and {{user_display_name}}, the same fields used across every Krom Automation trigger. Beyond that, BuddyBoss triggers expose role-specific tags depending on the event:
- Groups:
{{group_id}},{{group_name}},{{group_url}},{{group_description}} - Connections:
{{initiator_id}},{{friend_id}},{{friendship_id}} - Follows:
{{follower_id}},{{leader_id}},{{leader_profile_url}} - Forums:
{{topic_id}},{{topic_title}},{{forum_id}},{{topic_author_email}} - Activity:
{{activity_id}},{{activity_content}}(a 200-character plain-text excerpt) - Profiles:
{{profile_completion_percentage}},{{profile_complete}}
One privacy boundary to know about
Private Message Sent never exposes the message body as a merge tag. This is deliberate. If your workflow needs to send a message, use the Send Private Message action with content you write directly into the workflow rather than trying to relay the original message.
Profile completion has a similar honesty rule
BuddyBoss can only calculate profile completion percentage accurately when a member edits their own profile. If an admin or an API call updates someone else’s profile, {{profile_complete}} correctly returns no rather than guessing.
BuddyBoss Conditions in Krom Automation #
BuddyBoss triggers unlock a dedicated condition category alongside the standard user and custom conditions:
| Condition field | Type | Example use |
|---|---|---|
| Group ID | Number | Only continue for a specific group |
| Group Name | Text | Filter by a group’s display name |
| Member Type | Text | Branch based on a registered member type |
| Activity Component | Select | Separate member-feed posts from group posts |
| Forum ID | Number | Only continue for a specific forum |
| Profile Completion | Number | Branch at a completion threshold |
| Profile Complete | Select | Check whether a profile is fully filled in |
Not every field is available on every trigger. Group ID only makes sense on a group-related trigger, for instance. The workflow builder only shows the condition fields that are actually meaningful for whichever trigger you have selected.
Ready-to-Import Templates #
Eight BuddyBoss workflow templates ship with Krom Automation Pro, on top of the 101 templates already included:
| Template | What it does |
|---|---|
| Welcome New Member | Member activates, gets a welcome email, and gets a profile activity update |
| Friendship Accepted Message | A connection is accepted, and the requester gets a private message |
| Profile Complete Congratulations | A profile hits 100% completion and the member gets a congratulations email |
| New Follower Notify | A member gets followed and receives an email notification |
| Group Left Winback | A member leaves a group, waits 3 days, then gets a win-back email |
| Forum Reply Notify Author | A reply is posted and the original topic author is emailed |
| Activity Keyword Moderation | A status update matching flagged keywords alerts an administrator |
| Group Join Welcome | A member joins a group and gets a welcome email plus a group activity post |
Templates are a starting point, not a finished workflow. Before activating one on a live site, review the recipient fields, the email wording, group permissions, any moderation keywords, and the delay timing.
See Testing Workflows with the Simulator for how to dry-run a template against real data before it touches real members.
Preventing Automation Loops #
Some BuddyBoss actions can trigger the exact same event they respond to. Add User to Group, for example, calls the same BuddyBoss function that fires the Group Joined trigger. Without protection, a workflow could accidentally trigger itself in an endless loop.
Krom Automation prevents this automatically. Every BuddyBoss action carries a lineage marker through the API call, so if it generates a BuddyBoss event synchronously, the automation engine recognizes that the workflow is already running and refuses to fire it again for the same chain.
This protects against direct action-to-trigger loops. If you are chaining multiple separate workflows together in a way that could create a longer cycle across workflows, still add explicit conditions to break the chain deliberately.
Setup #
- Activate Krom Automation, Krom Automation Pro, and BuddyBoss Platform or BuddyPress.
- Enable every BuddyBoss component your planned workflow needs. Groups for group workflows, Forums for forum workflows, and so on.
- If you are building a follower workflow, enable BuddyBoss Activity Follow specifically. The Activity component alone does not cover following.
- Open the workflow builder and select a BuddyBoss trigger to get started, or import one of the eight templates above and adjust it to your community.
Frequently Asked Questions #
Does the BuddyBoss integration work with regular BuddyPress, or only BuddyBoss Platform?
Both. Krom Automation detects either the BuddyPress class or BuddyBoss Platform’s implementation of it, so the integration works on a standard BuddyPress install as well as BuddyBoss Platform.
What happens to a saved workflow if I disable a BuddyBoss component?
The workflow stays intact. The trigger simply stops firing, and any action that needs the disabled component fails cleanly with a log entry instead of breaking the workflow. Re-enable the component and the workflow resumes working immediately.
Can I see the actual message content in a Private Message Sent trigger?
No. Message body content is intentionally excluded from that trigger’s merge tags as a privacy protection. The Send Private Message action can still send content you write yourself.
Why did Create Connection not send a connection request notification?
Create Connection force-accepts the relationship immediately rather than sending a pending request, so the usual “wants to connect” notification never fires. If you need the standard request flow, that has to happen through BuddyBoss directly rather than through this action.
Is BuddyBoss included in the free version of Krom Automation?
No. BuddyBoss triggers, actions, and templates are part of Krom Automation Pro. See the Free vs Pro comparison for the full breakdown.
Related Documentation #
- How Krom Automation Works: Triggers, Actions, and Workflows
- Merge Tags in Krom Automation
- MemberPress Integration
- Testing Workflows with the Simulator
- Krom Automation Pro Templates
Also from wpRigel #
Pollify: Gutenberg native polls, surveys and quizzes, built as real editor blocks with no shortcodes to paste.
Commandify: a command palette for the WordPress admin. Cmd or Ctrl plus K to jump anywhere and run admin actions, including deep WooCommerce order and customer management, without clicking through menus.
Ready to automate your BuddyBoss community? Check pricing plans and grab your deal now.
