FCRM > Triggers > Custom Field Updated ---> We really need this 🙈
Now that we can finally display custom fields to users, it feels like the missing piece in FluentCRM is obvious: a “Custom Field Updated” trigger.
Yes, I know there’s a workaround with a custom plugin (or even building our own), and of course we could rely on external tools to simulate this. But honestly, for something so fundamental to any CRM, it makes no sense that FluentCRM’s Automations don’t already include it.
Here’s the vision:
- Start an automation whenever a Custom Field is updated.
- Pass into the workflow which data was changed.
- Even better: allow conditions for multi-choice fields, like triggering when any option is selected — or only when specific choices are.
This would be a real game-changer. Especially now that FCRM lets users update their own profiles — the trigger would unlock a whole new level of personalization and automation.
#featurerequest
you have it here by wpfusion
Ramsis Kasis thank you!
Really appreciate it Ramsis 🙏🏼
However, as I said in the post... I am already aware of:
- this tools (I have licenses).
- Custom snippet, custom plugin…etc
Yup!
Already aware 👍
But, as I said, I wrote this post, because I think, after last update of FCRM, this should be on the core :)
Ramsis Kasis Is there a similar tool, though, that allows an automation to trigger when a user profile is updated?
Or allows us to write data to either the CRM fields or to the User profile fields?
Shane Skwarek maybe , but not somrthing i know about , sorry
Jorge de los Reyes Would you mind checking something for me? Can you try to export data from a user on a system that has a custom field active in Fcrm? I had trouble with that the other day and it would be helpful to know if it was just a fluke.
J V sure! Just let me know: are you referring to checking if the custom field is also exported ? (Eg.: CSV?)
Jorge de los Reyes In my case I had a custom field in Fcrm, and I had the export fail. After some testing I found the custom field was the cause of the fail. I have no absolute need for it so in order to be compliant (user being able to export data) I removed the field.
To be clear, in WP under tools --> export personal data