BuddyPress
Overview
AFI captures community-membership events from BuddyPress and forwards them to any receiver. Push every new community signup to your CRM, add new members to a Mailchimp audience for an onboarding series, or notify a Slack channel.
Available triggers
AFI listens for the following events from BuddyPress. Each event runs as its own integration — you can have several integrations on the same plugin firing on different events.
- BuddyPress Registration
Mappable fields
Every field on the BuddyPress signup form is available for mapping — first name, last name, email, username, plus every custom profile field you’ve defined in the xProfile component. Profile field groups are exposed individually so you can map them to specific receiver fields.
Requirements
- BuddyPress installed and activated.
- Registration enabled in BuddyPress > Settings.
Quick start
- In WordPress admin, go to AFI > New Integration.
- Trigger > Sender: pick BuddyPress.
- Event / Form: pick the specific event you want this integration to listen on (e.g. BuddyPress Registration).
- Pick a Receiver (e.g. Mailchimp, HubSpot, Google Sheets, Slack) and the desired task.
- Map BuddyPress fields onto the receiver’s fields. Use special tags (
{{_date}},{{_user_ip}}, etc.) for values not present in the form. - Optional: add Conditional Logic to control when the receiver is called.
- Save and run a test event to confirm the integration. Check AFI > Log if anything looks off.
Notes & caveats
- Activation events: BuddyPress fires the AFI trigger at signup, not at email-activation. If your installation requires email activation, the receiver will see the user before they confirm — segment downstream if needed.
- xProfile field names appear with their human label; if you rename a field, update the mapping.
- BuddyBoss users should use the dedicated BuddyBoss sender instead — different plugin, different schema.