Retain Other Fields In Automations | Voters

Retain Other Fields In Automations

Ryan Luevano

Sometimes, I need to change the trigger for automation; however, when a trigger is changed, I lose all my work in the prefilled "Then Do This" section. It would be better to retain the remaining fields of the automation.

January 15, 2025

Ryan Luevano

Hi Jon,

I use automation to send emails to my roster of clients. Sometimes, the process for a trigger changes (often if I update a procedure), and then I have to rewrite or paste an entirely new email with fields. This process becomes extremely time-consuming. If the trigger changes and the "Then Do This" sections also need to be reset, then it's essentially a brand-new automation, which is not what I need when I just need to alter the trigger. I hope that makes sense.

Jon Darbyshire

Hiya Ryan Luevano, thanks for this post! I have a few more questions for you:

Can you provide examples of specific fields that you would like to retain when changing the trigger?
How frequently do you need to change the trigger in your automations?
Are there any specific scenarios or use cases where retaining the fields would be particularly beneficial?