Hi there!
I’d like to suggest a small but important improvement to ManyChat custom fields, the ability to save a field as truly empty.
Right now, Clear User Field is not the same as setting a field to an empty value. This becomes a problem in workflows that use AI actions like Claude or OpenAI, where custom field values are passed as inputs. When a field is cleared, ManyChat may still send something like {{cuf_14394590}} instead of sending an actual empty value. That can confuse the AI and lead to wrong or inconsistent responses.
Because of this, I’ve had to use a workaround by saving an invisible character in the field instead of leaving it empty. It works to some extent, but it is not a proper solution.
You could fix this in any one of these ways:
- add a new Empty User Field action to save field as truly empty
- or allow Set User Field action to save a truly empty value by removing the validation that currently prevents empty values from being saved.
The goal is simple, when a field is meant to be empty, ManyChat should send an actual empty value, not a field placeholder like {{cuf_14394590}}. This would make AI automations much more accurate and reliable.
Thanks!
