Hi! What is your use case for this? I don't completly understand when one would want one static image attached to every email. What do you think about adapting the change to consume what we call a "file pointer". There are already a few Agents that can emit such a pointer. One example is the LocalFileAgent

I like the idea of the LocalFileAgent but it isn't that useful for the intended use cases.

One use case is invoice generation: ShellCommandAgent that generates a local PDF invoice file that leads to the email agent being able to attach the invoice to be sent to the customer.

Regardless agent scenario, not being able to attach files to outgoing emails is a blocker in all cases.

I'd be interested in hearing your thoughts. I started the move off of Freshbooks specifically for this feature. Unfortunately in the last mile, I find that Huginn doesn't support email attachments... which is a glaring feature hole IMO - hence the PR. :-)

I like the general idea, my main concern is that the approach of only supporting files from local storage might be too limited, I might be missing something but I believe you should be able to pass the path to the file your ShellCommandAgent generated to a LocalFileAgent (which then emits a "file pointer" and then have the EmailAgent consume that pointer. The main benefit of that approach would be that the EmailAgent could use attachments from all Agents that can emit file pointers.