Uncanny Automator

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.

Excellent, thanks for confirming! And good question, this thread will probably help other users too.

Hi @nward85 ,

One of our developers took a look at this and suggested that you whitelist the following URI from WAF:

wp-json/uap/*

He also noted that rules that are triggering false alarms can probably be disabled by entering the rule showing up in the logs linked to wp-json/uap/ in the Disable Rule ID field.

Hi @nward85 , sorry to hear about the issue.

Is there a specific plugin you’re using for the firewall, and if so, what specific URL is returning the 403? Do you have REST API calls blocked? While we know disabling the WAF features entirely seem to work, have you tried changing individual settings to try to trace it?

Thanks

Hi @rsioncke , thanks so much for the review!

Hi @wpwebsites , thanks for the suggestion!

We have tentatively added an action to send a notification with the PeepSo “on-site” notification system to our feature request board. That does seem like a useful addition, so we’ll try to include that in an upcoming release.

We’ll mark this as closed for now since the request has been captured.

The developers were thrilled too. ?? Thanks again!

Hi @manni02 , thanks so much for the kind review! Our support team was especially appreciative of your feedback and they were pleased that they were able to make a positive impression.

Hi @michael1986dan , we don’t seem to have any tickets for you and it would be great to get more details about what you experienced. What specifically broke on your site? Are there any details from the PHP error logs you can provide that might be related to the issue? We’re happy to investigate and provide feedback if you’re able to provide more details.

Thanks so much for the review! Yours was definitely an interesting and useful ticket; we’ll be able to use the findings to add some additional exclusions and detections for WP Rocket settings in particular.

Hi @ipweanz , thanks so much for the review and feedback!

Hi @aziamethyst , thanks so for much for taking the time to leave a review.

The 4.2 update was released last week and it should correct this for you. If you are seeing any remaining issues, please let us know.

Since it has been almost 3 weeks since the last reply, we’ll go ahead and close this ticket. Feel free to open this back up if you’re having any issues.

Hi @adewebdev , your recipe 2 does seem a bit strange. It sounds like you’re matching based on status, but don’t you want to target a specific order and update based on that order’s status? If that’s the case, it seems like the “Match” value should be changed to the order number. The rest seems okay at a glance.