In the ‘Add user to group through User Custom Field’ automation script, there was an inconsistency in how the ‘User Custom Field name’ input is interpreted depending on the trigger: for ‘User first logged in’, it expects the friendly name (e.g., ‘Native Language’), while for ‘Recurring’, it requires the internal ID (e.g., ‘user_field_5’). simon identified this UX issue and proposed a fix to unify behavior using the friendly name for both triggers, referencing the relevant code. JammyDodger noted this was already mentioned in the walkthrough and that broader alignment with other settings (like ‘public user custom fields’ and ‘poll groupable user fields’) was planned but not prioritized. simon submitted a PR to resolve the issue. The fix has since been merged, introducing a dropdown to select existing User Custom Fields by friendly name, making the input consistent across both triggers JammyDodger.
Looking at the “Add user to group through User Custom Field” script, there seems to be a bit of an issue. If the “User first logged in” trigger is selected, the “User Custom Field name” input should be set to the name of the User Field, for example “Native Language.” But if the “Recurring” trigger is selected, the “User Custom Field name” input needs to be set based on the User Field’s id. For example “user_field_5”.
Just to note, this is mentioned in the walkthrough:
I’ve mentioned about reworking the script for consistency, though it’s not been prioritised yet. There’s also the public user custom fields and staff user custom fields admin settings that would be nice to bring into line with it as well.
(And there’s also poll groupable user fields too, which uses the ‘friendly name’)
