I’ve seen several workarounds for this use case, but they all depend on an internal email address associated with one of the registered tenants. These workflows also have the potential to break due to their dependencies.
That’s why I would like to see an extension of the Email Bridge that allows external email addresses to be whitelisted, enabling them to use Asana without requiring middleware or additional user workflows.
We have many use cases where system-generated emails need to be turned into Asana tasks. Currently, this is handled through user-created workflows that can only be monitored and managed by the users themselves. As administrators, we have no control over these workflows.
I initially requested this feature in the Email Bridge release topic, but I was asked by @Phil_Seeman to open a separate topic here as a development request.
I think—and hope—that our company is not the only one that would benefit from this feature.