BuddyBoss registation Form to Fluent CRM on Subdomain

Hi @ozarc ,

Yes, this should work fine, but I will warn you that it would require our Pro version on both the BuddyBoss site and the FluentCRM site.

On the BuddyBoss trigger side for site 1, we do offer a few registration-based Pro triggers that would let you capture profile data. You would then send this data to site 2 via a webhook action, where there would be another recipe with an incoming webhook trigger and actions to add the FluentCRM data, maybe create a user and add profile data.

Still, if you’re adding any extra custom fields to the BuddyBoss registration, that may be something that needs to be explored further, in which case you may want to open a ticket on our website if you do run into any challenges with any specific field types.

Alright, thanks Ive been digging around since my post.

Any reason your core automations lack many basics triggers such as “User registers to the site”, “User logs in to the site” etc that AutomatorWp offers?

https://www.buddyboss.com/integrations/automatorwp/

Id think that these would be the first automations that you’d put into your core?

It’s because we consider them WordPress functions.

Have a look at https://automatorplugin.com/integration/wordpress-core/. That’s where you’ll see triggers like logging in, a user being created, etc. Certainly we wouldn’t miss basics like those!

Haha, yeah i found them ??

Its confusing because i was looking under the “Everyone” section and not “Logged-In” section.

In my mind a non-logged in user (everyone) would need the “User registers to the site” trigger, not a user that is already logged in? Seems to be the same with AutoWp as well.

Anyway, they seem to offer the registration trigger for free, so will play with theirs until I gain more knowledge and understand all of this better.

Thanks or the replies.

Yeah, agreed, “Logged In” is a bit misleading, but we needed something short and simple to try to capture “Recipes involving WordPress user account data or user activity in some way when they’re initiated”. That recipe type doesn’t mean a user is actually logged in when they run or to run them, just that they always involve WP accounts in some way (vs. something like a form submission that can be trigged by a visitor with no WordPress account and never involving a WordPress account). We try to explain this a bit in the recipe selection screen, but on our integration pages it lacks that context–and can be confusing.

We have some ideas about how to address this in a future release with a pretty big overhaul, but that initiative is probably ~6 months away.

Thanks for the feedback!