Allow Tag Renaming Without Breaking Smart Lists, Workflows, and Integrations
A
Ashleigh Cole
Right now tags are referenced in the system by name, not by a persistent internal ID. This causes major issues when we rename a tag — Smart Lists, workflows, filters, and even Zapier steps continue looking for the old tag name and break silently when they can’t find it.
This can be solved by referencing tags on the backend by Tag ID across the entire system. This allows users to rename tags freely without disrupting automations or external integrations, because everything still points to the same backend ID.
Please change the way tags are referenced across the platform so that:
- Tags are identified and stored using a unique, internal Tag ID, not the tag name
- Renaming a tag in the UI does not affect automations, Smart Lists, workflows, filters, or integrations
- All tag-based logic continues to function correctly after renaming
Log In
P
Paul Kunad
Workflows are working fine for me. But the other stuff would be great!
Also, same goes for Custom Fields. Give them an internal ID! 🙏�
E
Eli Ferry
Yes! Thank you for articulating this. It drives me crazy, as we use tags extensively. It would also be great to see something along the lines of tag categories. This isn't as much of a priority as we can do it ourselves with a naming convention, but it would still be a nice quality of life upgrade.