When you create an email action in an automation, you have to choose which email to send from in the automation. This is a serious limitiation. If you have multiple users, you would often want them to be able to send emails individually, and not all rely on the same shared account.

Only way around this is to create individual automations for each user. If you have 10 users, that means 10 automations! Also, you have to figure out a way to know which automation to trigger.

Back in piloting I created a button on a task type that neatly did this:

Voila: one button to create an email from within clickup, all based on dynamic data.

Except it wouldn't work for multiple users, as I found out the hard way when adding more user emails.

The AI Brain actually suggested this clunky solution: create one button for each automation, ie: "Send email (Ken)", "Send email (Dave)" and so on. Then link the buttons to different automations.

Of course I'll have none of that, so now the button is triggering Make, which in turn finds out who pressed the button, writes this back to a custom field on the task, which in turn triggers one of those 10 automations. Yes, it's even more clunky, but at least the users won't see 10 buttons, and accidentally hit the wrong one (which does nothing)...

Today the only practical use case I can see for the send email action, is when you have a shared account like support@ or sales@. But not all use cases involve shared email accounts.