Issue Summary

This is a suggestion to add a smart value function to read and base64-encode attachment content directly. For example:

{{{{issue.attachments.first.content.asBase64}}}}

Or, alternatively, include an option on the "Send web request" action to treat non-JSON responses as base64 and expose them. For example:

{{{{webResponse.bodyAsBase64}}}}

If this is implemented, please provide information regarding any limitations or security considerations our customers should be aware of (max attachment size Automation could handle, execution time limits, response size caps).

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available