Using automations to react to column value changes is difficult and indirect to set up and slow for the user. I suggest adding a column configuration option to select/define an action to run whenever that column’s value is changed. This would allow the docmaker to think about and define their post-edit action in the context of the table/column where it matters, and this approach would limit the “real-time-iness” of automations to only those defined in the column context (as opposed to updating all automations to be more responsive, which I’d imagine is a huge PiTA).
Another way to approach this could be to add an option to button column configurations to select another column in the table which would trigger a press of that button in that row whenever the value in that other column is changed.