saving Email parameters on FME flow

This scenario is a great reason to use topics and subscriptions - I'm not that up to speed on Automations (but my colleague @Todd Davis​ is) so i'm talking more from a workbench side (where the same/similar issue arises) You can use a topic notifier to send the email body to the topic, which then passes it through to the subscription(s) listening to that topic. When your email server details change, all you need to do is update the details in the subscription. As none of the details are stored in the workbench (or automation) then you don't need to make any changes there

As Hamish mentioned, we utilise Notifications (Topic/Subscribers) to handle emails because it gives you one location to set the email settings, rather than setting them in every automation and, as you have discovered, having to update them all when something changes, . There are also several ideas that relate to this, that I provided in 2019 being:

https://community.safe.com/s/bridea/a0r4Q00000HbrmFQAR/fme-server-automations-update

https://community.safe.com/s/bridea/a0r4Q00000HbqugQAB/fme-server-automation-templates

To fix your current issue, I have attached a workspace that will go through your automations and get there content. You can use that to find your emailers, and if necessary, you can add to the process to update the content.