Thanks for getting in touch! There is a variable that is only available in a step Octopus.Machine.Name. However you could use this to populate another variable in each step and use that in your email step.
That’s probably the only solution here. We do not keep the machine details around during the deployment.
Email steps do not have the capability to double resolve variables. The only option we have to perform something like this is to iterate through the different machines and values in the array. Below is an example of code to perform this:
#{each machine in Octopus.Action[Set Output Vars].Output}
example #{machine.Notes}
#{/each}
We have a documentation page that briefly covers this in a way, I’ll link it below (See Output from multiple machines)
I will be happy to answer any further questions you may have about this.