[SOLVED] Auto action trigger

We have a script that updates user profiles with marketing data from a third party application. The intention is to provide transparency to users by including all the info we have on them in their profiles, whether they have provided it directly or not. The script runs and performs the update as expected, but trying to trigger it from an auto action has no visible effect.

I've tried the triggers AfterLogin, BeforeFrontendProfileUpdate, BeforeProfileRequest, and BeforeProfileEditDisplay.

Can you help me identify what might be missing?

Trigger it how? Using a Request auto action or just using PHP directly? Does it need anything from the user (e.g. user id, username, etc..)? Does it need to store anything in CB or is it just supposed to supply the results of the request?

CB Version 2.1.0, Auto Actions v. 6.2.2

Using a request action. The setup is very similar to two other auto actions we have that collect info from the CB database and send to the marketing app (it just goes the opposite direction). Those two trigger on registration confirmation and on after update profile. Could it be conflicting with the update profile action?

It uses the user id and checks against the info in the db to update if blank or different.

If you're needing to pull that information and display it to the user then you'll probably need to use a Code action and the necessary PHP to parse out its display. If the URL you're requesting already provides it well formatted then your Request action can be configured to output the results of its HTTP request, which you can display to the user by creating a Joomla menu item to your auto action after setting Triggers to None. You will not be able to display that information to the user using a trigger.

You could also use a CB Code Field and the necessary PHP to request that information and format it for display to display it as a field on their profile.

Thanks for your reply. The information relates to fields that are already in the profile, and what the script is supposed to do is update those fields in the database so they display when a user opens the "Edit profile" view. Is there anything in CB or AA that impedes writing to the DB?