1. Problem
When making an agent public, the Send Email block currently either uses the agent owner’s email connection or requires the user to select a connection dynamically at runtime. The latter introduces an unnecessary checkpoint/approval step, which disrupts the smooth flow of the agent.
2. Use Case
Public agents that send personalized outputs via email. Each user should receive the email directly at their own address, without requiring repetitive confirmations.
3. Requested Functionality
Add a new option in the Send Email block called “Runner’s Default Email Connection”.
-
For public runs, the block automatically uses the default email account of the runner (the person executing the agent).
-
For the agent owner running the agent, it defaults to the owner’s email connection.
-
No extra checkpoint/approval should be required, ensuring a seamless experience.
4. Additional Notes
This feature would isolate the agent owner’s account, avoid interruptions for users, and make public-facing agents much more practical.