I have essentially the same problem described here:

https://knowledge.safe.com/questions/30724/in-fme-server-how-to-pass-parameters-to-the-subscr.html

The solution described there about running a workspace from a parent isn't all that scalable and it seems like there must be a better way. I thought I had a solution when I added a published parameter called nm_email_to to the job. I tested a failure and success condition and they had worked, but I had manually triggered those tests. It doesn't appear that the scheduled jobs pass the email_to to the subscriber in the same way that a manual run does.

I can see the data in the scheduled job under Request Data > Notification Manager Directives in the directives parameter. It looks like this:

[{"name":"email_to","value":"email@example.com"}]

Is there any way to get this data into the subscriber such that it'll send to the email set up in the workspace?

Also, I want to do this in a consistent manner for the failure case and success case. So one parameter email address set once in a workspace that is then visible to the subscribers to use in the subsequent email. This is really important for our context because we have a highly federated environment where the customers that need the notifications may differ across workspaces, but we want to send standardized template emails.

Currently there's a subscriber for every job failure and success condition with emails placed in each and this is error prone and unnecessary overhead for managing ETLs at scale.

P.S. I'm already aware of the tutorial and setting up emailer data in a workspace, but the problem is that doesn't pass along the data in the failure case.